From owner-freebsd-current Fri Jan 30 04:18:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA17923 for current-outgoing; Fri, 30 Jan 1998 04:18:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA17918 for ; Fri, 30 Jan 1998 04:18:50 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id EAA19854; Fri, 30 Jan 1998 04:17:57 -0800 (PST) To: Charlie ROOT cc: freebsd-current@FreeBSD.ORG Subject: Re: /kernel.config takes over boot: -c :-(( In-reply-to: Your message of "Fri, 30 Jan 1998 13:12:02 +0100." Date: Fri, 30 Jan 1998 04:17:57 -0800 Message-ID: <19849.886162677@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" I understand what you essentially want here, but just to note that you're a little confused about what's going on currently. -c is NOT being ignored in this case, it's going straight into UserConfig just as you told it to do. Then UserConfig is saying "Hey, I see some data here which the boot blocks gave me from a /kernel.config file, and it starts with the magic string USERCONFIG, so off I go!" There's really not a lot you can do about that, either. If the data is there, it's there, and userconfig has little choice but to assume that you knew what you were doing when you gave it overrides. Boot in fixit mode and simply nuke or move that /kernel.config file if you want it to stop seeing it, I'd say that's a fairly simple solution. :) Like I said, I do understand what you essentially want, however, and what that is is *another* flag (-C?) which tells UserConfig *not* to pay attention to any provided parameters. :-) Bruce is also master of the boot blocks so if you can manage to talk him into polluting his argument space with yet another argument letter, it's as good as done. :-) Jordan > * Prepare /kernel.config file containing some config commands. > * boot with -c > * kernel ignores -c, and executes parameters from /kernel.config only. > > I think this is bad. If I screw something with configuration (perhaps I > won't be able to run the system at all if I mess with syscons), I want -c > to take precedence over (perhaps bogus) commands from /kernel.config. > > Kernel is -current. Bootblock is ca. 2 months old. > > I always thought that machines should first listen to me, and then to > their own instructions :-) Wouldn't you like it yourself? > > > Andrzej Bialecki > > ---------------------+------------------------------------------------------- -- > abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } > Research & Academic | "Be open-minded, but don't let your brains to fall out ." > Network in Poland | All of the above (and more) is just my personal opinio n. > ---------------------+------------------------------------------------------- -- >