🚀 go-pugleaf

In article <6792@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes:
>In article <15069@cbmvax.commodore.com> ken@cbmvax.commodore.com (Ken Farinsky - CATS) writes:
>> How are you going to handle protection issues (user/group/other)
>> and file ownership (user name space)?
>
>You have a program called "login", that you have to run to get non-world
[...]
>you've blown security away anyway. And it's a model that works well in other
>PC-UNIX file sharing arrangements.

I agree. How would this be different than mounting an NFS partition
under AmigaNFS? Actually, I think it would be great to have a login
program just like this available under AmigaNFS to be used on an
outgoing basis. Have it use the same passwd resources that are used
when ftp'ing into the Amiga.

I have been wanting to provide for a 'multi-user' environment which
uses a passwd arrangement on one of the machines here since different
people use it - just to set up the different environments everyone
uses. Currently we just execute a script to set these things up.  This
does nothing for permissions, etc. but at least you get your home
directory, default editor, etc. & your own set of background programs
at your disposal.

Would SANA be able to resolve some of this stuff? I.e. have a passwd
program which sets variables internal to SANA, and then have SANA
handle the file ownership issues when dealing with a 'locally' mounted
Unix filesystem and an NFS mounted filesystem.

Kent Polk: Southwest Research Institute
Internet : kent@swrinde.nde.swri.edu
UUCP     : $ {cs.utexas.edu, gatech!petro, sun!texsun}!swrinde!kent