From nobody@FreeBSD.ORG Wed Apr 28 16:31:54 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 160BB1578F; Wed, 28 Apr 1999 16:31:53 -0700 (PDT)
Message-Id: <19990428233153.160BB1578F@hub.freebsd.org>
Date: Wed, 28 Apr 1999 16:31:53 -0700 (PDT)
From: junkmale@xtra.co.nz
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: errata.txt for 3.1
X-Send-Pr-Version: www-1.0

>Number:         11373
>Category:       misc
>Synopsis:       errata.txt for 3.1
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Apr 28 16:40:01 PDT 1999
>Closed-Date:    Mon Oct 25 13:02:25 PDT 1999
>Last-Modified:  Mon Oct 25 13:02:52 PDT 1999
>Originator:     Dan Langille
>Release:        
>Organization:
The FreeBSD Diary
>Environment:
FreeBSD daisy.nz.freebsd.org 3.1-19990318-STABLE FreeBSD 3.1-19990318-STABLE #0: Fri Mar 19 01:18:10 GMT 1999 jkh@usw3.freebsd.org:/usr/src/sys/compile/GENERIC  i386
>Description:
The "Kernel change information" text in errata.txt for 3.1-Release should be included in 3.1-Stable as it apears this problem has not been fixed.

note: I'm basing this on a 3.1-stable install I just did and the number of people installing 3.1-stable who come into #freebsd asking about this problem.... <grin>
>How-To-Repeat:
Install 3.1-stable and try saving your config.  You'll have to change it every time unless you do the mods mentioned in 3.1-RELEASE errata.txt.
>Fix:


>Release-Note:
>Audit-Trail:

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 11:05:08 +0900

 junkmale@xtra.co.nz wrote:
 > 
 > >Description:
 > The "Kernel change information" text in errata.txt for 3.1-Release should be included in 3.1-Stable as it apears this problem has not been fixed.
 > 
 > note: I'm basing this on a 3.1-stable install I just did and the number of people installing 3.1-stable who come into #freebsd asking about this problem.... <grin>
 
 ?
 
 I just took a look at the -stable sysinstall, and it *does* the
 right thing. If the person does not have a /boot/loader.rc, it will
 create one with the appropriate lines. If the person already have
 that file, sysinstall will explain the procedure to him/her.
 
 OTOH, for the past few days the person _will_ have a loader.rc. But
 the explanation ought to be printed. Is that *not* happening???
 
 --
 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."
 

From: "Dan Langille" <junkmale@xtra.co.nz>
To: "Daniel C. Sobral" <dcs@newsguy.com>
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: misc/11373: errata.txt for 3.1
Date: Thu, 29 Apr 1999 19:28:25 +1200

 On 29 Apr 99, at 11:05, Daniel C. Sobral wrote:
 
 > junkmale@xtra.co.nz wrote:
 > > 
 > > >Description:
 > > The "Kernel change information" text in errata.txt for 3.1-Release
 > > should be included in 3.1-Stable as it apears this problem has not been
 > > fixed.
 > > 
 > > note: I'm basing this on a 3.1-stable install I just did and the number
 > > of people installing 3.1-stable who come into #freebsd asking about this
 > > problem.... <grin>
 > 
 > ?
 > 
 > I just took a look at the -stable sysinstall, and it *does* the
 > right thing. If the person does not have a /boot/loader.rc, it will
 > create one with the appropriate lines. If the person already have
 > that file, sysinstall will explain the procedure to him/her.
 
 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.
 
 Mind you, these people *may* have been installing 3.1-release.  But I 
 *know* I installed 3.1-stable and had that problem.
 
 Is this a recent
 
 > 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?
 
 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.
 --
 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
 

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."
 
 
 

From: "Dan Langille" <junkmale@xtra.co.nz>
To: "Daniel C. Sobral" <dcs@newsguy.com>
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... <grin>
 
 > 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
 

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 22:14:25 +0900

 Dan Langille wrote:
 > 
 > > 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.
 
 That's long ago. I doubt sysinstall was already DTRT then.
 
 > > 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... <grin>
 
 Thanks. If you could send me the resulting /boot/loader.rc,
 /boot/loader.conf and /boot/kernel.conf, just so I can rest assured
 everything is being installed as expected, I'd be even more
 grateful.
 
 > 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?
 
 If done through make world, nothing changes in this regard. Anyway,
 make world doesn't run kget, or even changes the kernel. :-)
 
 If done through install disk/sysinstall, I expect a newer
 /boot/loader.rc to be installed, as well as all the rest of the
 required infrastructure. Of course, I'd prefer to be sure than
 confident. :-)
 
 > 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.
 
 Ok. Feel free to contact me in following up on any problem related
 to bootstrapping in general.
 
 --
 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."
 

From: "Dan Langille" <junkmale@xtra.co.nz>
To: "Daniel C. Sobral" <dcs@newsguy.com>
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: misc/11373: errata.txt for 3.1
Date: Fri, 30 Apr 1999 21:25:40 +1200

 On 29 Apr 99, at 22:14, Daniel C. Sobral wrote:
 
 > Dan Langille wrote:
 >
 > > > 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... <grin>
 > 
 > Thanks. If you could send me the resulting /boot/loader.rc,
 > /boot/loader.conf and /boot/kernel.conf, just so I can rest assured
 > everything is being installed as expected, I'd be even more
 > grateful.
 
 Ummm, things are strange.  I downloaded the bin directory for 3.1-19990429-
 STABLE and installed via FTP from another box.  There is no loader.conf or 
 kernel.conf.
 
 This machine previously had 3.1-19990318-STABLE as noted in the uname -a 
 below.
 
 Here's what I got.
 
 $ uname -a    
 FreeBSD daisy.nz.freebsd.org 3.1-19990318-STABLE FreeBSD 3.1-19990318-
 STABLE #0: Fri Mar 19 01:18:10 GMT 1999     
 jkh@usw3.freebsd.org:/usr/src/sys/compile/GENERIC  i386
 
 $ cd /boot
 $ ls -lt
 total 191
 drwxr-xr-x  2 root  wheel     512 May  1 08:36 defaults
 -r--r--r--  1 root  wheel   11462 Apr 30 16:49 loader.help
 -r--r--r--  1 root  wheel   23639 Apr 30 16:49 support.4th
 -r--r--r--  1 root  wheel     171 Apr 30 16:49 loader.rc
 -r-xr-xr-x  1 root  wheel  131072 Apr 30 16:49 loader
 -r--r--r--  1 root  wheel    5181 Apr 30 16:49 loader.4th
 -r--r--r--  1 root  wheel    7680 Apr 30 16:49 boot2
 -r--r--r--  1 root  wheel     512 Apr 30 16:49 boot1
 -r--r--r--  1 root  wheel     512 Apr 30 16:49 boot0
 -rw-r--r--  1 root  wheel     139 Apr 24 12:07 kernel.config
 $ 
 
 $ cat loader.rc
 \ Loader.rc
 \
 \ Includes additional commands
 include /boot/loader.4th
 
 \ Reads and processes loader.rc
 start
 
 \ Unless set otherwise, autoboot is automatic at this point
 
 $ cat kernel.config
 di psm0
 di zp0
 di ze0
 di lnc0
 di le0
 di ie0
 di fe0
 di ex0
 di ep0
 di cs0
 di wt0
 di wdc1
 di scd0
 di mcd0
 di matcdc0
 di bt0
 di aha0
 di adv0
 q
 $
 
 > If done through install disk/sysinstall, I expect a newer
 > /boot/loader.rc to be installed, as well as all the rest of the
 > required infrastructure. Of course, I'd prefer to be sure than
 > confident. :-)
 
 That loader.rc looks newer by the timestamp.
 
 > Ok. Feel free to contact me in following up on any problem related
 > to bootstrapping in general.
 
 FWIW, I was speaking with Jordan on irc.  He figured I'^H^H^H the snapshot 
 is messed up and that I should try again with a newer snap.
 
 Lemme know when.
 --
 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
 

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: Sat, 01 May 1999 08:23:51 +0900

 Dan Langille wrote:
 > 
 > > Thanks. If you could send me the resulting /boot/loader.rc,
 > > /boot/loader.conf and /boot/kernel.conf, just so I can rest assured
 > > everything is being installed as expected, I'd be even more
 > > grateful.
 > 
 > Ummm, things are strange.  I downloaded the bin directory for 3.1-19990429-
 > STABLE and installed via FTP from another box.  There is no loader.conf or
 > kernel.conf.
 
 These are not in bin, they are created by sysinstall during the
 installation process.
 
 That's why it's difficult for me to test it... :-)
 
 --
 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."
 
 
 

From: "Dan Langille" <junkmale@xtra.co.nz>
To: "Daniel C. Sobral" <dcs@newsguy.com>
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: misc/11373: errata.txt for 3.1
Date: Sat, 1 May 1999 12:43:37 +1200

 On 1 May 99, at 8:23, Daniel C. Sobral wrote:
 
 > Dan Langille wrote:
 > > 
 > > > Thanks. If you could send me the resulting /boot/loader.rc,
 > > > /boot/loader.conf and /boot/kernel.conf, just so I can rest assured
 > > > everything is being installed as expected, I'd be even more grateful.
 > > 
 > > Ummm, things are strange.  I downloaded the bin directory for
 > > 3.1-19990429- STABLE and installed via FTP from another box.  There is
 > > no loader.conf or kernel.conf.
 > 
 > These are not in bin, they are created by sysinstall during the
 > installation process.
 > 
 > That's why it's difficult for me to test it... :-)
 
 Ummm, OK.  Is my testing procedure correct?
 --
 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
 
State-Changed-From-To: open->closed 
State-Changed-By: jim 
State-Changed-When: Mon Oct 25 13:02:25 PDT 1999 
State-Changed-Why:  
Closed at request of submitter. 
>Unformatted:
