You are not logged in.
I configured my home-directory to be mounted per nfs at startup
/etc/fstab
...
casablanca:/maps/home /home nfs auto,nouser,noexec 1 2
and start the following daemons
/ets/rc.conf
...
DAEMONS=(!pcmcia network crond inetd portmap nfslock ypbind autofs hotplug)
but the directory is not mounted after I boot up in AL and therefore no logging in is possible before mounting it myself
it's exactly the same configuration that works in gentoo and redhat so I wondered what could be the problem
any idea?
Before we could talk we were singing,
before we could run we were dancing.
"On Earth" by Samael
Offline
Are there any errors on startup? My guess is that the fs mount stage happens before the daemons stage, so things like portmap aren't started and when mount is called to mount the home directory it doesn't work.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
thanx, I guess you're right
I found no errors (a hint where to search? dmesg and /var/log/* tell me nothing)
but I solved it by adding "mount /home" to my rc.local
Before we could talk we were singing,
before we could run we were dancing.
"On Earth" by Samael
Offline
Another approach is to install autofs. And have your shared fs's mounted when you access them & unmounted after a predefined period of inactivity.
The AL pkg by default checks for nfs shared volumes by accessing /var/autofs/net/HOSTNAME/SHARE
so simply modify your user' s home entry in /etc/passwd to /var/autofs/net/SERVER/SHARE
This has the additional advantage that your client won' t crash when your server crashes...
Offline
When I said errors, I meant things like in the boot scripts, when you see everything going by and a whole bunch of "DONE"s. Are there any "FAIL"s?
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
My guess is that the fs mount stage happens before the daemons stage, so things like portmap aren't started and when mount is called to mount the home directory it doesn't work.
If that is the case I would consider that a point of future improvement - if not a bug ;-)
I would file an entry in the bug tracker, but only after I have checked it and possibly have a solution.
Something along changing the initial mount call to
mount -a -t nonfs,smbfs,coda
which mounts everything except the three network filesystems NFS, SMB and Coda. And later in the appropriate network filesystem startups, additionally mount the corresponding filesystems.
This is, of course, for those filesystems that are not controlled by any automounting facility.
Offline
I saw no FAILS on bootup but bootup is much too fast to be sure ;-)
is the bootup-output saved somewhere
the idea with -a -nonfs is excellent, didn't realize this combination
perhaps this is what the other distros do
Before we could talk we were singing,
before we could run we were dancing.
"On Earth" by Samael
Offline
the idea with -a -nonfs is excellent, didn't realize this combination
perhaps this is what the other distros do
And this is what AL does, quoting from /etc/rc.sysinit :
/bin/mount -a -t nonfsAn improvement should be to create an init script (i.e. nfsmount) to simply mount all nfs volumes in fstab & have it running after portmap & nfslock...
Offline
And this is what AL does ...
:oops: well, as I said, "after checking" and I was not in front of an Arch box then. ;-)
Offline