From owner-freebsd-hackers Thu May 9 13:10:33 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from ns2.gnf.org (ns2.gnf.org [63.196.132.68]) by hub.freebsd.org (Postfix) with ESMTP id BA30C37B403 for ; Thu, 9 May 2002 13:10:28 -0700 (PDT) Received: from mail.gnf.org (smtp.gnf.org [172.25.11.11]) by ns2.gnf.org (8.11.6/8.11.6) with ESMTP id g49K0tO71191; Thu, 9 May 2002 13:00:55 -0700 (PDT) (envelope-from gordont@gnf.org) Received: by mail.gnf.org (Postfix, from userid 888) id 031FB11E511; Thu, 9 May 2002 13:10:28 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.gnf.org (Postfix) with ESMTP id 0191211A572; Thu, 9 May 2002 13:10:28 -0700 (PDT) Date: Thu, 9 May 2002 13:10:27 -0700 (PDT) From: Gordon Tetlow To: Michael Smith Cc: hackers@freebsd.org Subject: Re: nextboot loader diff In-Reply-To: <200205091911.g49JBaI3002178@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 9 May 2002, Michael Smith wrote: > You're fooling yourself if you think that just because you're rewriting a > different file, "something going wrong" isn't going to hose the user > anyway. True, but if I only hose /boot/nextboot.conf (which is going to be delete when the machine enters multi-user anyway), I can contain any damage done. > You probably want to overwrite with "TRY" rather than "NO", too, since > userland needs something to key off to know that this is a 'next' boot. > > Obviously, "TRY" then gets overwritten with "NO" on the next boot, but > the new kernel is not booted (this is the 'recovery') boot. This doesn't really have any hooks into userland. It's for loader options. I may not be understanding what you are trying to illustrate here. > I still think you're not thinking the processes associated with this > feature through carefully enough. Very possible. This was just a first cut of the feature and I'll be the first to admit that it's not pretty. I don't know forth so I was happy to get as far as I did. There isn't a notion of a recovery boot in this implementation. It either tries the new options (specified in /boot/nextboot.conf) or it doesn't and sticks to the defaults. -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message