Re: Bug in #! processing - One More Time

From: Garance A Drosihn (drosih_at_rpi.edu)
Date: 02/25/05

  • Next message: Poul-Henning Kamp: "[REVIEW/TEST] device liberation patches." 
    Date: Fri, 25 Feb 2005 17:36:38 -0500
To: Gordon Tetlow <gordon@tetlows.org>

    At 1:03 PM -0800 2/25/05, Gordon Tetlow wrote:
    >Garance A Drosihn wrote:
    > >
    > > 3) Change kern/imgact_shell.c to process shebang options the same
    >> way other (non-BSD?) operating systems do. By that I mean:
    >> send the entire string as arg[1], and let the scripting
    >> language sort it out. This is an incompatible change from
    >> FreeBSD 5.3 to 5.4, but would put make us "more consistent"
    > > with other operating systems.

    Additional data point: It seems that both OpenBSD and NetBSD do
    it the same way the other OS's do. Which is to say, I don't think
    there is any OS which matches FreeBSD's present behavior.

    > > Or we could do #1 for now, and plan to do #4 after 5.4-release.
    >> Or do #1 now in 5.3, and go with some incompatible change (#2
    >> or #3) only in 6.x-current.
    >
    >I would say we should stick with #1 for the 5.x release and
    >use #3 for 6.x and further. We have already frozen APIs and
    >ABIs. For people that might have scripts that use this syntax
    >to have problems between minor releases is unacceptable.

    The more I look at this, the more I think we can do #3 without
    breaking much of anything. But I am not confident that I could
    get it done and have it tested-enough in time for 5.4-release.
    I need to write an update to kern/imgact_shell.c and bin/sh,
    and I have to at least check what this means for /usr/bin/env
    (since many scripts use that as the "interpreter" on `!#' lines).

    Other than that, what else in the base system is even *used* as
    an interpreter in this fashion? Would `awk' be? Anything else? 

    -- 
Garance Alistair Drosehn            =   gad@gilead.netel.rpi.edu
Senior Systems Programmer           or  gad@freebsd.org
Rensselaer Polytechnic Institute    or  drosih@rpi.edu
_______________________________________________
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: "[REVIEW/TEST] device liberation patches."

    Relevant Pages

    • Re: Embedding Tcl/Tk in non C language
      ... if you don't initialize Tcl/Tk correctly. ... bare minimum setup requirements for running Tk scripts. ... GOTO error ... ' Initialize Tcl interpreter ...
      (comp.lang.tcl)
    • Re: Tcl bytecode
      ... where several chunks of template scripting may ... Even being able to dump and re-load the state of an interpreter would ... best case, allowing it to fly over the unmodified library scripts, and ... then simply load up the pre-built interpreter state right at the point ...
      (comp.lang.tcl)
    • Re: Looking for advice: supporting multiple embedded interpreters
      ... > Some background first - we have some software that embeds a Python ... > interpreter into a host application. ... But we want to support the ability to edit scripts while the app is ... use the 'reload' builtin to reload your python modules. ...
      (comp.lang.python)
    • Looking for advice: supporting multiple embedded interpreters
      ... Some background first - we have some software that embeds a Python ... But we want to support the ability to edit scripts while the app is ... like multiple "instances" of a Python interpreter to manage this. ... using PyThreadState_Swap, load my built in modules, and swap it back out. ...
      (comp.lang.python)
    • Re: avoid multiple script startup overhead
      ... problem we are seeing on our solaris servers due to various cron jobs ... spawning of new perl and ksh interpreters to run various scripts is ... interpreter, ...
      (comp.lang.perl.misc)