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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 04 Dec 2006 16:20:51 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Trond Myklebust <trond.myklebust@....uio.no>
CC:	Janne Karhunen <Janne.Karhunen@...il.com>, MrUmunhum@...dial.com,
	linux-kernel@...r.kernel.org
Subject: Re: Mounting NFS root FS

Trond Myklebust wrote:
> On Mon, 2006-12-04 at 22:05 +0200, Janne Karhunen wrote:
>> On Monday 04 December 2006 20:21, Trond Myklebust wrote:
>>
>>>>> 2) NFS provides persistent storage.
>>>> To me this sounds like a chicken and an egg problem. It
>>>> both depends and provides this at the same time :/. But
>>>> hey, if it's supposed to work then OK.
>>> ??? Locking depends on persistent storage, but persistent storage never
>>> depended on locking.
>> Except for the fact that to be able to mount anything RW you
>> generally _want_ to have locks. And can't have locks without 
>> the mount. Not that it wouldn't work, it's just that I would
>> not do it [for obvious reasons].
> 
> You just need to be careful to set it up correctly in the initrd: either
> make sure that you mount the root partition as 'nolock' or else make
> sure that you mount /var/lib/nfs, and start rpc.statd before you start
> init and any other applications that might need locking.
> 

The nfsmount which is in the klibc distribution supports running an ad 
hoc portmap daemon, which allows locking to be done by forwarding 
information to the "real" portmap for when the real rpc.statd is run.

	-hpa
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ