Subject: Re: Changing exec's #! behavior
To: Christos Zoulas <firstname.lastname@example.org>
From: Dave Huang <email@example.com>
Date: 06/13/2000 16:56:18
On Tue, 13 Jun 2000, Christos Zoulas wrote:
> Now I suddenly cannot use an interpreter that has a space in its
> filename. What should the kernel do next? Start parsing backslash
It's not all that sudden... you can't do that right now either:
yerfable /tmp> cp /bin/cat "cat with spaces"
yerfable /tmp> cat > script
#!/tmp/cat with spaces
yerfable /tmp> chmod 700 script
yerfable /tmp> ./script
./script: Command not found.
A ktrace shows that it's looking for "/tmp/cat".
Name: Dave Huang | Mammal, mammal / their names are called /
INet: firstname.lastname@example.org | they raise a paw / the bat, the cat /
FurryMUCK: Dahan | dolphin and dog / koala bear and hog -- TMBG
Dahan: Hani G Y+C 24 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++