In article <VA.000019af.00cd3437@nscsysops.net>, bd@NSCSysOps.net
says...
> As Eric said for the login process. As for the mappings, there are

no
> login script equivalents for CIFS, but if you're logging into a

domain,
> the user profile could be used to connect a drive letter to the home


> dirs. Or, use Windows persistent mappings.
>


Windows persistent mappings will have to do, although that doesn't
help
my Mac OS X users. I was ideally looking to make the process of making

the initial mapping as easy as possible: For instance, with shares on
my
Linux box, all I need to specify on the client computer (Mac or
Windows)
is

foo.new.ox.ac.uk/username

and give the password. A drive is mapped directly to the home
directory.
Since that is also CIFS (Samba), I was hoping this would have made it

into NFA's CIFS implementation. Apparently not. Since I have about 900

users with individual home directories, as it stands, students see
everyone else's home directory. Searching through 900-odd is bad
enough
(even in alphabetical order) but it turns out I can connect as one
user,
and read/write contents in another users' home directory. Are there
specific rights I need to apply to my USR volume?

Cheers,
James