Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 2 Apr 2003 21:39:46 -0500
From:      cas <xcas@cox.net>
To:        "Bruce A. Mah" <bmah@freebsd.org>, freebsd-stable@freebsd.org
Subject:   Re: 4.8-RELEASE status
Message-ID:  <20030403023947.GAXA10140.fed1mtao07.cox.net@smtp.west.cox.net>

next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.

------=____1049337586683_No5fQ8Evo?
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


> 
> 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)"));

------=____1049337586683_No5fQ8Evo?
Content-Transfer-Encoding: base64
Content-Type: application/pgp-signature;
	name="replyAll"
Content-Disposition: inline;
	filename="replyAll"

LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0NClZlcnNpb246IEdudVBHIHYxLjIuMSAo
RnJlZUJTRCkNCg0KaUQ4REJRRStpMzc5Mk1veGNWdWdVc01SQXNXS0FLRDdaWjJieXQ3U1JD
NXlDRDEwQVhmME95QlhzUUNkSFdlNA0KdkpxUHZMNDRxREpRT2hLVTgyV3U1c2c9DQo9eGdT
dA0KLS0tLS1FTkQgUEdQIFNJR05BVFVSRS0tLS0tDQoNCg==
------=____1049337586683_No5fQ8Evo?--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030403023947.GAXA10140.fed1mtao07.cox.net>