[unios] Re: Networked user (was: Networked GUI)
Anders Petersson
anders.petersson@mbox320.swipnet.se
Tue, 22 Dec 1998 23:36:37 +0100
From: Anders Petersson <anders.petersson@mbox320.swipnet.se>
>From: "Srikant Sharma (Chiku)" <srikants@wipinfo.soft.net>
>> From: Anders Petersson <anders.petersson@mbox320.swipnet.se>
>> Something that I start to see more and more as essential is the ability of
>> nested users (a user can host other users under his home dir).
>> A special "user" home dir could be implemented, the networked user. This
>> user would be distributed in the whole network. How is only needed to be
>> known by the code that implements it... invisible for "outsiders", that is.
>> So, under this net user the tree would look as it would anywhere else, but
>> the implementation would be different. Users that are created here are
>> known anywhere on the network (network-wide home dir). The same holds for
>> everything else that can be stored in the tree... the whole sub-part of the
>> systree is distributed.
>> If you wanted to be able to log onto your own machine from everywhere in
>> the network, you could place a symbolic link to your user mounting point.
>> When you log in, the link is found and followed, and you are transported
>> outside the net user, to your own account. On your physical computer.
>>
>> Problem: This user would not be a child of any FS, but the data needs to be
>> stored no matter what. It need not be visible *where* the data is stored
>> (it logically exist on the very network), so much freedom is given to the
>> implementation to store the data on any node, and duplicated too. But in
>> the end someone has to give it some real storage space.
>> What if you just give the net user access to (limited) space in another
>> part of the systree? That part would be on reliabable storage which the net
>> user could use.
>>
>> This is not something that we *need* to think about. The flexibility of
>> UniOS would allow anybody to do it later... but of course it's fun to do
>> anyway. :)
>>
>> binEng
>>
>
>NIS on solaris gives you all this plus lot many things ....
>
>In my work environment My account is on NIS server ....
>All the other build machines reflect the status of my NIS account ...
>
>log in to any machine of your choice .... do the development ....
>finally goes to the NIS server .....
It sounds on you like "so what? that's already done!"
That's not what it is about. The challange is to have it worked out in the
context of mOS.
One feature may be implemented one one system, another feature on another
system... but they have never been brought together in a single OS. That's
what we're here for. Or maybe not even that - with the flexibility of
UniOS, others could do that afterwards, ok so I already said that.
BTW, does NIS/Solaris really support nested users?
binEng
------------------------------------------------------------------------
To unsubscribe from this mailing list, or to change your subscription
to digest, go to the ONElist web site, at http://www.onelist.com and
select the User Center link from the menu bar on the left.
------------------------------------------------------------------------
UniOS Group
http://members.xoom.com/unios