linux-kernel - Re: Mounting NFS root FS

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]

Message-Id: <200612042227.43751.Janne.Karhunen@gmail.com>
Date:	Mon, 4 Dec 2006 22:27:43 +0200
From:	Janne Karhunen <Janne.Karhunen@...il.com>
To:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
Cc:	Trond Myklebust <trond.myklebust@....uio.no>,
	MrUmunhum@...dial.com, linux-kernel@...r.kernel.org
Subject: Re: Mounting NFS root FS

On Monday 04 December 2006 22:03, Jan Engelhardt 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.
>
> Way 1:
>
> mount -nt tmpfs none /var/lib/nfs;
> mount -nt nfs fserve:/tftpboot/linux /mnt;
> mount -n --move /var/lib/nfs /mnt/var/lib/nfs/;
> ./run_init -c /mnt /sbin/init; # or similar

Statd should probably be started before nfs mount to get it 
right. But doesn't statd require state data ( some sort of 
generation number ) from persistent storage to work? This 
would start with a blank slate.


-- 
// Janne
-
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/