This is a discussion on Next Issue, Home Directories within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> On Fri, 16 Apr 2004 06:05:27 +0000, Sebastian Stein wrote: > On Thu, 15 Apr 2004 14:58:47 GMT, Menno ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| On Fri, 16 Apr 2004 06:05:27 +0000, Sebastian Stein wrote: > On Thu, 15 Apr 2004 14:58:47 GMT, Menno Duursma <menno@desktop.lan> wrote: >> I think you need to compile Samba feeding: "--with-smbmount" to >> "configure", Yup. > which Slackware defaults to _not_ do. I looked at the buildscript and this is bullshit... How come i though that, i have no idee. Maybe i ment "--with-automount" which wasn't included with samba-2.2.8a but *is* with samba-3.0.2a idunno. > I don't think this is needed, It is needed, but the Slackware packages (for both 9.1 and -current) also set it default. > because I use the slackware samba package and > can do smbmount without recompiling. Thanks for correcting me. I see the 3.x package is compiled with ACL support as well, kewl. IMO the only thing still left missing with in the 3.0.2a package are libnss_wins.so and libnss_winbind.so ! (Is that a bug?) -- -Menno. |
| ||||
| On Thu, 15 Apr 2004 08:30:12 +0000, Joost Kremers wrote: > Sebastian Stein wrote: >> Put the home directories on a central server and mount this filesystem >> during startup on the clients. A very easy way would be to just have a >> central samba server with the directories and then mount them at startup >> with smb mount. > > AFAIK the samba file system does not support unix-like permissions and > ownerships, That is correct (at least, on the machines i used it). But those would only be needed should you run some kind of shell server (or other setup, where user/group perms are usefull). And in the NT way of doing things you'd use ACLs instead: http://www.bluelightning.org/linux/samba_acl_howto/ http://networking.earthweb.com/netsy...0954_3077971_1 The samba 3x package from -current is compiled with support ... The 2.6.x kernel supports it, and 2.4.x can be patched for it: http://acl.bestbits.at/ > so you may not want to do it this way. The way i understand this setup, it looks like a NT network. Only the server is Linux and some (but not all) of the clients are Linux as well. Now, the most nice way i see one could go about it, is to make the Linux clients act like NT as well. That can (accouding to the docs) be done using some createive setup for: smb.conf, fstab, and nsswitch.conf. man winbindd But you'll need "libnss_winbind.so" installed then (i hope not PAM...): http://www.google.nl/groups?selm=pan...0deskt op.lan -- -Menno. |