Date: Thu, 29 Apr 1999 02:40:03 -0700 (PDT) From: "Daniel C. Sobral" <dcs@newsguy.com> To: freebsd-bugs@FreeBSD.org Subject: Re: misc/11373: errata.txt for 3.1 Message-ID: <199904290940.CAA27917@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/11373; it has been noted by GNATS. From: "Daniel C. Sobral" <dcs@newsguy.com> To: junkmale@xtra.co.nz Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: misc/11373: errata.txt for 3.1 Date: Thu, 29 Apr 1999 18:16:26 +0900 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 :). > 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. As for you installing 3.1-stable, it was corrected at _some_ point. Depending on how long ago you did it... > > 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. 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. 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. 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)... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Proof of Trotsky's farsightedness if that _none_ of his predictions have come true yet." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199904290940.CAA27917>