Hi-- A number of you have been (rightfully) wondering what's up with the i386 4.8-RELEASE. Here's the current state: The files that are as of this moment tagged as RELENG_4_8_0_RELEASE can't be used to build a release because the MFSROOT kernel (that goes on the kern.flp) overflows a the size of a 1440K floppy disk. This bug was masked by another problem that happened to be present on the machines used by the RE team to build releases...namely, that they didn't have the cvsroot-all collection in their local repositories. To make a long story short, the $FreeBSD$ tags didn't get expanded in the source files, thus (I am not making this up) causing the MFSROOT kernel to be just a *little* bit smaller so that it could fit on a floppy. I think this was the world's April Fool's joke to the RE team. We're currently trying to fix this by finding some other driver we can move to a module on the mfsroot.flp image (or maybe just eliminate). After we finish some tests, we'll need to commit whatever change is required, re-tag the affected files, and then rebuild the base system. I'm not in a position to comment on a timeline for these happenings. Thanks for your continued patience! Bruce. PS. This may sound rude, for which I apologize in advance: The less time that the RE team has to spend replying to various emails (particularly those that are not relevant to the immediate goal of shipping 4.8-RELEASE), the faster the release is probably going to be finished. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20030402/3194e229/attachment.bin
> > From: "Bruce A. Mah" <bmah@freebsd.org> > Date: 2003/04/02 Wed PM 07:23:25 EST > To: freebsd-stable@freebsd.org > Subject: 4.8-RELEASE status > > Hi-- > > A number of you have been (rightfully) wondering what's up with > the i386 4.8-RELEASE. Here's the current state: > > The files that are as of this moment tagged as RELENG_4_8_0_RELEASE > can't be used to build a release because the MFSROOT kernel (that goes > on the kern.flp) overflows a the size of a 1440K floppy disk. > > This bug was masked by another problem that happened to be present on > the machines used by the RE team to build releases...namely, that they > didn't have the cvsroot-all collection in their local repositories. > To make a long story short, the $FreeBSD$ tags didn't get expanded in > the source files, thus (I am not making this up) causing the MFSROOT > kernel to be just a *little* bit smaller so that it could fit on a > floppy. I think this was the world's April Fool's joke to the RE > team. > > We're currently trying to fix this by finding some other driver we can > move to a module on the mfsroot.flp image (or maybe just eliminate). > After we finish some tests, we'll need to commit whatever change is > required, re-tag the affected files, and then rebuild the base system. > > I'm not in a position to comment on a timeline for these happenings. > > Thanks for your continued patience! > > Bruce. > > PS. This may sound rude, for which I apologize in advance: The less > time that the RE team has to spend replying to various emails > (particularly those that are not relevant to the immediate goal of > shipping 4.8-RELEASE), the faster the release is probably going to be > finished. >Are you guys aware of a perl bug in 'sockstat' in 4.8? It appears when you have 'kern.ps_showallprocs=0' set.. when a user uses 'sockstat' it spits out.. ------------- cas:~$ sockstat USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS cas sshd 2664 4 tcp4 ip#hidden:22 ip#hidden:1977 USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS USER COMMAND PID FD PROTO ADDRESS Use of uninitialized value in printf at /usr/bin/sockstat line 141. cas sshd 2664 3 stream cas sshd 2664 7 stream /tmp/ssh-T72DDMfh/agent.2664 ------------- it can be fixed by changing line 143 of '/usr/src/usr.bin/sockstat/sockstat.pl'.. - $nsd->[8] || ($fsd->[8] ? $endpoint{$fsd->[8]} : "(none)")); + $nsd->[8] || ($fsd->[8] && $endpoint{$fsd->[8]} ? $endpoint{$fsd->[8]} : "(none)")); -------------- next part -------------- A non-text attachment was scrubbed... Name: replyAll Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20030402/9c2e60b0/replyAll.bin
According to the post below, the problem is with the image for the 1.44 floppy disk. However, the is no problem with the CD ISO images. Is that correct? Thus furure changes of the FreeBSD i386 CD ISO images would not be made, and dowloading the ISOs currently on the ftp server is OK. Is that correct? I am booting my system from CD and I really don't care about the 1.44 floppies. I would like to know when the CD images are going to be final and ready for release. Thanks --- "Bruce A. Mah" <bmah@freebsd.org> wrote:> Hi-- > > A number of you have been (rightfully) wondering > what's up with > the i386 4.8-RELEASE. Here's the current state: > > The files that are as of this moment tagged as > RELENG_4_8_0_RELEASE > can't be used to build a release because the MFSROOT > kernel (that goes > on the kern.flp) overflows a the size of a 1440K > floppy disk. > > This bug was masked by another problem that happened > to be present on > the machines used by the RE team to build > releases...namely, that they > didn't have the cvsroot-all collection in their > local repositories. > To make a long story short, the $FreeBSD$ tags > didn't get expanded in > the source files, thus (I am not making this up) > causing the MFSROOT > kernel to be just a *little* bit smaller so that it > could fit on a > floppy. I think this was the world's April Fool's > joke to the RE > team. > > We're currently trying to fix this by finding some > other driver we can > move to a module on the mfsroot.flp image (or maybe > just eliminate). > After we finish some tests, we'll need to commit > whatever change is > required, re-tag the affected files, and then > rebuild the base system. > > I'm not in a position to comment on a timeline for > these happenings. > > Thanks for your continued patience! > > Bruce. > > PS. This may sound rude, for which I apologize in > advance: The less > time that the RE team has to spend replying to > various emails > (particularly those that are not relevant to the > immediate goal of > shipping 4.8-RELEASE), the faster the release is > probably going to be > finished. > >> ATTACHMENT part 2 application/pgp-signature__________________________________________________ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com
On Thu, Apr 03, 2003 at 06:01:06PM -0800, Georgi Hristov wrote:> According to the post below, the problem is with the > image for the 1.44 floppy disk. However, the is no > problem with the CD ISO images. > Is that correct? > > Thus furure changes of the FreeBSD i386 CD ISO images > would not be made, and dowloading the ISOs currently > on the ftp server is OK. > Is that correct?The ISO images were also recreated. Kris -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20030403/b7d805b0/attachment.bin
I have the correct ISO image. The mirror link I had in a separate email was a little outdated. ~Ken ----- Original Message ----- From: "Kris Kennaway" <kris@obsecurity.org> To: "Ken Mays" <kmays2000@hotmail.com> Cc: "Murray Stokely" <murray@freebsd.org>; "Georgi Hristov" <tweaky_81@yahoo.com>; <freebsd-stable@freebsd.org> Sent: Friday, April 04, 2003 10:23 PM Subject: Re: 4.8-RELEASE status