Re: #! interpreter argument handling in UPDATING ?

From: Garance A Drosehn (gad_at_FreeBSD.org)
Date: 07/13/05

  • Next message: Craig Rodrigues: "Re: Panic in bpf, maybe related to if_xl"
    Date: Wed, 13 Jul 2005 10:58:16 -0400
    To: Marc Olzheim <marcolz@stack.nl>, freebsd-current@FreeBSD.org
    
    

    At 12:45 PM +0200 7/13/05, Marc Olzheim wrote:
    >On Wed, Jul 13, 2005 at 12:21:25PM +0200, Marc Olzheim wrote:
    >> Hi.
    >>
    > > Shouldn't the new (6-STABLE) interpreter argument handling be
    > > in /usr/src/UPDATING ? Or will it be in the release notes ?

    This I don't know about. I thought I had added an entry to
    UPDATING, I have not looked to see what (if anything) happened
    to it.

    >Btw.: Why isn't there some compatibilty mode added to the 4 and
    >5-STABLE /usr/bin/env , so that there's at least a common way to
    >run scripts on different FreeBSD servers that does the multiple
    >argument handling ?
    >
    >Like ignoring a -S or interpreting it as -- ...

    I first wanted to make sure all the bugs were ironed out of the
    version in 6.x. I have a few minor bug fixes yet to commit to
    the 6.x version, for instance. (I'll probably commit them to
    7.x today, now that the code freeze has lifted for that).

    Other than that, it's mainly just the bother of writing up a
    different man page. Since the parsing done by the kernel is
    different in 5.x/4.x (and that parsing is not going to change),
    I suspect that the man page needs a different description for 5.x.
    I also need to do some testing to make sure I stick to examples
    which work the same for both kinds of argument-handling as done
    by the kernel.

    -- 
    Garance Alistair Drosehn     =      gad@gilead.netel.rpi.edu
    Senior Systems Programmer               or   gad@FreeBSD.org
    Rensselaer Polytechnic Institute;             Troy, NY;  USA
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
    

  • Next message: Craig Rodrigues: "Re: Panic in bpf, maybe related to if_xl"

    Relevant Pages

    • cvs-src summary for 21/03/04
      ... You can get old summaries, and an HTML version of this one, at ... As a follow-up to last week's commit of `ICC support for kernel building`, ... Marcel Moolenaar committed code to replace the use of hints ...
      (freebsd-current)
    • Re: bug in 2.6.22-rc2: loop mount limited to one single iso image
      ... > In kernel 2.6.22-rc2 the number of available loop mounts is reduced ... > Kernel 2.6.20.11 does not show that problem. ... sudo mount -o loop cd1.iso m1 ... commit 705962ccc9d21a08b74b6b6e1d3cf10f98968a67 ...
      (Linux-Kernel)
    • Re: more git updates..
      ... With 17,000 files in the kernel, and most commits just changing a small ... commit" in less than one second on the kernel, and 0.75 secs of that is ... says that the uncompressed tree-file is 950,874 bytes. ... I suspect I will have to change the format somehow. ...
      (Linux-Kernel)
    • Re: .version keeps being updated
      ... 8993780a6e44fb4e7ed34e33458506a775356c6e is first bad commit ... depends on getting the kernel version from the kernel binary. ... This just restores "linux_banner" as a static string, ... Reverting this from 2.6.20-rc1 made the build behave again, ...
      (Linux-Kernel)
    • Re: Lockup after logging out of X
      ... and go back to gdm. ... 0dbf7028c0c1f266c9631139450a1502d3cd457e is first bad commit ... Currently __pa_symbol is for use with symbols in the kernel ... das eine Mal als Tragödie, ...
      (Linux-Kernel)