Bug in #! processing

Pawel Jakub Dawidek pjd at FreeBSD.org
Fri Oct 1 11:34:43 PDT 2004

On Thu, Sep 30, 2004 at 03:30:26PM +0200, Sławek Żak wrote:
+> >> I like the bahavior of FreeBSD besides special
+> >>     treatment of # on the first line after #!. Allowing for comments on the
+> >>     first line is a strange excuse. Have you ever seen a script commenting on
+> >>     the interpreter execution or had a need to do so?
+> >
+> > No, but since this has been possible in FreeBSD for over 4.5 years, you
+> > can guarantee that someone is using it.
+>     What do you think of sysctl named say kern.exec_hash_compat (set to 1 by
+>     default) or kernel option (also set to old behavior) to `fix' the situation?

Adding sysctl to control this behaviour is the best we can get, IMHO.
I can commit this, with default value which keeps the current behvaiour,
but I don't like this name. We should find a name which starts at 'compat.'.
Any suggestions? compat.unix.exec_hash?

Pawel Jakub Dawidek                       http://www.FreeBSD.org
pjd at FreeBSD.org                           http://garage.freebsd.pl
FreeBSD committer                         Am I Evil? Yes, I Am!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20041001/08ace358/attachment.bin

More information about the freebsd-current mailing list