From owner-freebsd-current Wed Apr 24 23:20:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from peetree.cs.huji.ac.il (peetree.cs.huji.ac.il [132.65.80.34]) by hub.freebsd.org (Postfix) with ESMTP id 3B0AC37B41A; Wed, 24 Apr 2002 23:20:18 -0700 (PDT) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=danny) by peetree.cs.huji.ac.il with esmtp id 170cc4-0006kh-00; Thu, 25 Apr 2002 09:20:16 +0300 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: obrien@freebsd.org Cc: current@FreeBSD.ORG Subject: Re: FreeBSD 5.0 Developer Preview #1 Now Available / diskless booting In-reply-to: Your message of Wed, 24 Apr 2002 19:25:38 -0700 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Apr 2002 09:20:16 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Danny, > > What do you think about doing a little more polishing and rolling a new > set of patches taking this /etc/rc.conf option into account? Your kernel > env dhcp variables are really good. I know that many do want to do what > you are doing (large scale RO /); but up until now /etc/rc.diskless* has > not been well engineered. polishing wont help, if i don't know all the problems :-) in the begining, there was no way to mount / ro - sunos would not run, and so we had zilions of /, one for each host, linux makes a mfs image, so even if freebsd is a bit messy it is by far better engineered - my .5$ the root_rw_mount is fine, but it's a bit late. now that devfs is here (great!) the only problem to solve is what/how to deal with /etc rc.conf* fstab X11 and some othere local-configurable files. the name/value knobs are fine - though some more documentation ... :-) btw, there is still another tricky problem: if i have / ro, and shared among many hosts, i can't: 1- easely specify different kernels i do this at the moment by commenting out kernel= in boot/loader.conf and passing it as a dhcp tag. 2- loadable modules for the very early modules: like unionfs, no harm in loading it, so fine but what about others that might cause problems? later ones, i load from rc.local and now for some coffee, danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message