Re: seduid scripts

[mh1@irz.inf.tu-dresden.de (Michael Hohmuth)]

> I somehow fail to understand, why you all are so keen to put
> '#!/bin/sh' in the beginning of shell scripts. I definitly want the
> '#!' feature myself, but why can't we live with '#!c:\bin\sh'. I mean,
> if there thousands of shell script, which could be moved from UNIX to
> MiNT and which can then run unmodified, then I can possibly understand
> the request, [...]

Frank,  in my understanding, that's exactly the way to go.  The aim is
to let the Unix folks feel at home on their Atari, and to make porting
software from Unix as easy as possible.

Wouldn't it be nice if you just take some piece of GNU software and type
	configure <cr>
	make all <cr>
	make install <cr>
without having to twiddle with shell script headers?

> [...] but we are on the ST which uses the '\' in the kernel.

Unfortunately, yes.  I think we shouldn't take that as a dogma; when using
the MiNT library or the GCC TOS lib, you don't have to use backslashes any
more.  (I even believe that it would be fairly easy to make the kernel
understand `/' as a path separator in a hypotetical new process domain. :-)

> Even with the links in the unified filesystem, I don't that we have a
> standard filesystem layout ala unix soon. 

Why not?  It's quite easy to set this up.  (I have done this on my machine.)

Regards,
Michael
-- 
Internet: hohmuth@freia.inf.tu-dresden.de