From owner-freebsd-stable Sat Oct 24 12:04:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01581 for freebsd-stable-outgoing; Sat, 24 Oct 1998 12:04:52 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (castles209.castles.com [208.214.165.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01574 for ; Sat, 24 Oct 1998 12:04:49 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA05550; Sat, 24 Oct 1998 12:08:36 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810241908.MAA05550@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Luigi Rizzo cc: mike@smith.net.au (Mike Smith), stable@FreeBSD.ORG Subject: Re: Request for change... In-reply-to: Your message of "Fri, 23 Oct 1998 04:10:49 BST." <199810230310.EAA13927@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 24 Oct 1998 12:08:36 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I don't think it's suitable for general consumption, no - there is too > > much of your local policy embedded in this. > > > > I'd keep it local, or perhaps see if you can't come up with a generic > > hook mechanism that's called out very early, and do everything inside > > that (optional) hook. > > of course, i did not mean to commit things in the current form: > > > > Do i have permission to work on this stuff for inclusion in -stable > > > and/or -current ? > > but just elaborate it and come up with something much simpler and > generic along these lines: > > very near the beginning of /etc/rc, figure out if this is a > diskless machine and set a variable. > > make fsck/mount/swapon contitional on this variable, and call > some alternate procedure from say rc.diskless for these actions. That's getting closer. I still can't help but think that this is the wrong way to do it; the process should be driven by the configuration data, not by policy embedded in code. Why should the fsck/mount/swapon be conditionalised in more than one location? You can already turn all of these off in /etc/fstab. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message