From owner-freebsd-bugs Thu Apr 29 3:20: 7 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id E874414D99 for ; Thu, 29 Apr 1999 03:20:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id DAA33833; Thu, 29 Apr 1999 03:20:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Thu, 29 Apr 1999 03:20:02 -0700 (PDT) Message-Id: <199904291020.DAA33833@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Dan Langille" Subject: Re: misc/11373: errata.txt for 3.1 Reply-To: "Dan Langille" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/11373; it has been noted by GNATS. From: "Dan Langille" To: "Daniel C. Sobral" Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: misc/11373: errata.txt for 3.1 Date: Thu, 29 Apr 1999 22:13:14 +1200 On 29 Apr 99, at 18:16, Daniel C. Sobral wrote: > Dan Langille wrote: > > > > The scenario which I base my claims on: > > > > Person arrives in channel > > how can I save my config > > read errata.txt > > nothing in there. > > read errata.txt for 3.1 release. > > One must always read the errata from the web page, of course. It's > obviously either impossible or ridiculous to put an errata with > thing that has the error, even though that's common practice with > commercial software (my comment still applies :). I got my details form the from the FTP site, not the webpages. > > Mind you, these people *may* have been installing 3.1-release. But I > > *know* I installed 3.1-stable and had that problem. > > Ok, I thought about it after I originally replied and I have this > question: are you talking about the kernel configuration you did > when you _installed_, or are you talking about doing it later? There > is no automated saving of these settings afterwards. The kernel configuration performed at install time when you remove conflicts. > As for you installing 3.1-stable, it was corrected at _some_ point. > Depending on how long ago you did it... The version in question is 3.1-19990318-STABLE, which *is* some time ago. > > > OTOH, for the past few days the person _will_ have a loader.rc. But > > > the explanation ought to be printed. Is that *not* happening??? > > > > What do you mean "for the past few days"? Is this a recent change to > > sysinstall? > > 3.1-RELEASE ran an internal version of kget, saving data to > /kernel.config, but never did anything to actually load that > information. Yep. I remember that. I'm the one that told Jordan about it and got errata.txt modified. > Later, it was changed to save data to /boot/kernel.conf, and to > write a /boot/loader.rc with the commands needed to load the > information. If /boot/loader.rc existed, though, it would just > inform the user that a /boot/loader.rc existed, and that certain > changes to it must be made. Ahhh. sounds good. > On last saturday or sunday I committed a default loader.rc to > -stable, resulting in sysinstall always showing the information > instead. (Or, at least, I imagine so... see below.) > > Today, Jordan has committed a patch to sysinstall that makes things > ok again (this time by using loader.conf(5)). > > > I have heard nobody mention the "explanation". Mind you, those people > > would merely have made the change. > > > > I can always reinstall a system to test this out. > > I, unfortunately, cannot... :-( I don't even have enough space to do > mock installs. If you could get a stable snapshot from tomorrow > (today's don't have the change yet) and test it, I'd be grateful. I will. Time to update the NZ mirror anyways... > Meanwhile, I'll start to wonder what happens if you have a kernel > configuration being loaded and the kernel doesn't have some of the > drivers (ie, you installed a customized kernel)... How does installing the latest stable over an existing stable sound? One that the changes made to it as detailed in the errata.txt for 3.1-release? At any rate, I will let the others ops on undernet #freebsd know to contact me if anyone else reports the problem. And to get the release they are upgrading to. And the snapshot details if they are on stable. cheers. -- Dan Langille - DVL Software Limited The FreeBSD Diary - http://www.FreeBSDDiary.org/freebsd/ NZ FreeBSD User Group - http://www.nzfug.nz.freebsd.org/ The Racing System - http://www.racingsystem.com/racingsystem.htm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message