Re: Bug in #! processing - "pear broken on current"

From: Florent Thoumie (flz_at_xbsd.org)
Date: 06/10/05

  • Next message: Poul-Henning Kamp: "Re: simplify disksort, please review." 
    Date: Fri, 10 Jun 2005 10:06:46 +0200
To: Roman Neuhauser <neuhauser@sigpipe.cz>

    On Jun 10, 2005, at 8:24 AM, Roman Neuhauser wrote:

    > # gad@FreeBSD.org / 2005-06-09 12:37:20 -0400:
    >
    >> [moved over from the thread:
    >> Re: cvs commit: src/sys/kern imgact_shell.c
    >> on the cvs-src mailing list...]
    >>
    >> At 11:03 AM -0500 6/9/05, Matthew D. Fuller wrote:
    >>
    >>>
    >>> Well, I dunno what part of it is giving troubles (and I haven't seen
    >>> it myself, since I'm still on RELENG_5 for the moment; just
    >>> keeping my
    >>> eyes open). It doesn't seem like a terribly esoteric line though:
    >>>
    >>> #!/usr/local/bin/php -n -q -dsafe_mode=0 -doutput_buffering=1
    >>>
    >>
    >> It is very likely that the problem which is being seen with this
    >> script is due to the change in parsing I committed on May 28th.
    >> Before the change, php would have been started up with:
    >>
    >> [0] -> /usr/local/bin/php
    >> [1] -> -n
    >> [2] -> -q
    >> [3] -> -dsafe_mode=0
    >> [4] -> -doutput_buffering=1
    >> [5] -> /usr/local/bin/name-of-script
    >> [6...] -> parameters specified by user
    >>
    >> and now php is being started with:
    >>
    >> [0] -> /usr/local/bin/php
    >> [1] -> -n -q -dsafe_mode=0 -doutput_buffering=1
    >> [2] -> /usr/local/bin/name-of-script
    >> [3...] -> parameters specified by user
    >>
    >> Assuming 'php' does not know what to do when all those options are
    >> glommed together in a single argument, then the above script would
    >> not work right on any other operating systems either. The change
    >> I made on the 28th gets FreeBSD to work more like other OS's when
    >> it comes to parsing that #!-line in scripts.
    >>
    >
    > The pear people have hacked around the other OS's limitations.
    >
    > This change makes FreeBSD lose one small but fine competitive
    > advantage over other unix-like systems. Pity.

         FreeBSD needed special handling, no it doesn't anymore.

         I'm not sure that's losing a *competitive* advantage. 

    -- 
Florent Thoumie
flz@xbsd.org
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
  • Next message: Poul-Henning Kamp: "Re: simplify disksort, please review."

    Relevant Pages

    • BSDStats 4.0 - You need to upgrade ...
      ... Apologies for the multi-list post, but I've been receiving several requests from varous *BSD users about this, so figured I'd hit everyone in one fell swoop ... ... First, for those that aren't aware, back in August, after some lengthy discussions on the FreeBSD mailing lists, I built a script that is meant to provide a means of building up usage metrics for the *BSD operating systems ... ...
      (freebsd-questions)
    • Re: Bug in #! processing - "pear broken on current"
      ... > script is due to the change in parsing I committed on May 28th. ... php would have been started up with: ... > not work right on any other operating systems either. ...
      (freebsd-arch)
    • Re: trouble with a script
      ... Your snippet of code doesn't look like sh on FreeBSD. ... Basically, I want my script to prompt me for two inputs, then append to ... The user input would be "domain.com", ... is how we set up a client's site on our servers. ...
      (comp.unix.shell)
    • Re: trouble with a script
      ... Your snippet of code doesn't look like sh on FreeBSD. ... Basically, I want my script to prompt me for two inputs, then append to ... The user input would be "domain.com", ... is how we set up a client's site on our servers. ...
      (comp.unix.shell)
    • Re: trouble with a script
      ... freeBSD servers by writing a script. ... Your snippet of code doesn't look like sh on FreeBSD. ... Basically, I want my script to prompt me for two inputs, then append to ...
      (comp.unix.shell)