[SLL] script interpreter bootstrap tricks

Ted Stern dodecatheon at gmail.com
Wed Apr 2 10:48:03 PDT 2008


Sorry, I was confused.

Turns out that "#!/usr/bin/env bash" is indeed accepted on the weird
system I'm working with.

The only problem is that bash is not in the standard minimal path by
default.  I'm working with the admin to add a symlink from /bin/bash
so it will be there.

Ted

On 01 Apr 2008 18:40:38 -0700, Brian Hatch wrote:
>
> At almost 2008-04-01 17:23 -0700, Scott Blachowicz spoke out:
>
>> > I'll have to petition the admins on the oddball system to allow it in
>> > /etc/shells.
>> 
>> Just curious...what does /etc/shells have to do with anything?  Are you saying
>> that there's something in the system that looks at /etc/shells to decide
>> what's OK to be on the #! line?  I've never heard of that before...
>
> /etc/shells is traditionally used as the list of acceptable login
> shells.  Then, in order to allow things like pop/ftp/etc where
> you didn't want interactive shells, you'd create '/bin/poponly'
> or '/bin/ftponly' which did an exit(1), and then add those to
> /etc/shells and make that a user's login shell.
>
> Shouldn't have anything to do with what your shebang line looks
> like.  Python/perl/ruby/etc aren't shells after all.

-- 
 dodecatheon at gmail dot com
 Frango ut patefaciam -- I break so that I may reveal


More information about the linux-list mailing list