1 Jan 2007 20:52
Re: NSS on Linux, "Emulating", Netware, was - Re: FirstLinuxserver
Eric Rothweiler <jetadmin <at> gmail.com>
2007-01-01 19:52:33 GMT
2007-01-01 19:52:33 GMT
NSS is currently lacking DFS on Linux and last I had researched, could only
be failed from NetWare to Linux, NetWare to NetWare, or Linux to Linux, not
Linux to NetWare.
The 'volumes' at the Linux level will simply be mount points inside the file
system. 'nix does not use 'volumes' or 'drives' but integrates the
additional disk devices and partitioned space into the master file system at
a point you pick. By default NSS partitions on OES Linux will be mounted
under /media/nss/{volume name}.
What you present to the clients is another decision point. Lets say you
create an nss partition at /media/nss/vol1 and create a volume structure
under there of /data/home and /data/shared. Traditionally what the users
would see is a volume named vol1 with \data as a folder and \home & \shared
under that folder. On OES Linux you can choose to not present the volume
vol1 and instead define a home and shared volume instead. This would be
done by using NCPCON with the following structure:
ncpcon create volume home /media/nss/vol1/data/home and
ncpcon create volume shared /media/nss/vol1/data/shared
A bit more interesting. An alternative to DFS using local disk only would
be to mount multiple nss partitions and mount them under a common point that
is shared as a volume. I've done this as follows:
Create partitions and mount as-
/media/nss/vol1 (can be NSS, resier, or EXT3. I reccomend staying with NSS
so as to not confuse any file system features.
Under there create additional NSS partitions:
/media/nss/vol1/sales
/media/nss/vol1/engineering
/media/nss/vol1/finance
/media/nss/vol1/it
(Continue reading)
RSS Feed