| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <1165349565.5742.104.camel@lade.trondhjem.org> Date: Tue, 05 Dec 2006 15:12:45 -0500 From: Trond Myklebust <trond.myklebust@....uio.no> To: Jan Engelhardt <jengelh@...ux01.gwdg.de> Cc: Janne Karhunen <Janne.Karhunen@...il.com>, MrUmunhum@...dial.com, linux-kernel@...r.kernel.org Subject: Re: Mounting NFS root FS On Tue, 2006-12-05 at 20:59 +0100, Jan Engelhardt wrote: > >> >> ./run_init -c /mnt /sbin/init; # or similar > >> >> > >> >> And you can also start locking after pivot_rooting to /mnt, that would > >> >> not even require (/mnt)/var/lib/nfs to be a separate mount. > >> > > >> >Much better idea. You can delay starting rpc.statd until you have set up > >> >your filesystem provided that you are not running any programs that > >> >require NLM locking. If you do need to run such a program before you > >> >start rpc.statd, then you will have to use the '-onolock' mount option. > >> > >> Since we're on the topic locking, is it because I am not running > >> statd on the client that my NFS client hangs during boot phase? > > > >If you have applications that try to set locks before rpc.statd is up > >and running, then that would explain it. > > Even if the nfs mount is mounted using -o ro,nolock? No. The 'nolock' option means that the NFS client will use the VFS posix locks only, which will not depend on rpc.statd. Trond - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists