X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C80640.F45AB40B@onstor-exch02.onstor.net>; Wed, 3 Oct 2007 20:42:22 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: update on prom kernel option processing
Date: Wed, 3 Oct 2007 20:42:23 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E05DD7029@onstor-exch02.onstor.net>
In-Reply-To: <20071003182638.4d424f04@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: update on prom kernel option processing
Thread-Index: AcgGJZzfiBjQT2XtSvKfFOUpBfQtDQAENCFQ
References: <20071003182638.4d424f04@ripper.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	"Warren Gale" <warren.gale@onstor.com>

Andy,

OK, we're busted.  It's the porn server that's clogging up the
connection to Campbell.

It turns out that limiting the PROM to a fixed space is more than a
quick change.  It involves defining all of the virtual address mapping,
which will take us some time.  We'll get to this when Rick gets settled
in full-time early next week.=20


Brian


> -----Original Message-----
> From: Andy Sharp=20
> Sent: Wednesday, October 03, 2007 6:27 PM
> To: Brian Stark; Warren Gale
> Subject: update on prom kernel option processing
>=20
> Well, I've spent too much time delving into this only to=20
> realize what the biggest problem probably is, but here goes.
>=20
> The PROM is running in 32-bit mode, which means that the=20
> argument processing code needs to be reworked substantially. =20
> I did that only to discover that _now_ argc is coming up 0. =20
> After spending half of today on that (mostly because of=20
> network ho-zed-ness), I remembered that the kernel is=20
> currently free to step on the PROM code right now because the=20
> PROM code is using memory beyond it's limits.
>=20
> So, I suspect the argument processing won't really work until=20
> that bug is fixed.  That bug has been around for quite a long=20
> time now, and should theoretically have been relatively easy=20
> to fix.  Can we please bump it up, way up, the list?  Like=20
> fixed sometime tomorrow?  Gracias!
>=20
> Cheers,
>=20
> a
>=20
> PS Could you guys temporarily turn off that wind-ho's box up=20
> there that you are using to continuously download all that=20
> porn via Campbell's internet connection?
>=20
