lkml.org 
[lkml]   [1999]   [Mar]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: #!perl - alternative path to script interpreters - patch to 2.2

Alexander Viro writes:

> And script written under Linux and using that feature will break
> *everywhere* else. Fun, fun...

That would not be a Linux problem.

>>>> It is more elegant to treat word after #! as a name of language...
>>>
>>> It is *completely* non-portable. Moreover, it will be useless for
>>> situations when different names are used for different versions of
>>> aforementioned awk (gawk vs. mawk).

One could have the kernel substitute any pathname for any other
pathname when executing a script.

>>> If you have permissions to tweak
>>> sysctls (aka /proc/sys) you have permissions to create a symlink.
...
> Excuse me? If you can set sysctls (root-only, otherwise I'll just
> reassign the path for sh and wait until the next cron task will run it. As
> root) you can set symlinks. Or fix the frigging script, in the first

# ln -s foo bar
ln: cannot create symbolic link `bar' to `foo': Read-only file system

It is completely normal to have problems writing to CD-ROMs and to NFS
servers controlled by someone else. The Linux filesystem layout is
designed to support a read-only /usr, and some people really do it.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:50    [W:0.041 / U:0.864 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site