X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7DA0B.0B7C81F2@onstor-exch02.onstor.net>; Wed, 8 Aug 2007 14:25:37 -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: Just asking...
Date: Wed, 8 Aug 2007 14:25:37 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E04EEC65A@onstor-exch02.onstor.net>
In-Reply-To: <20070808151249.09cdd6b1@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Just asking...
Thread-Index: AcfaCUMVCKzo6elGSxWWxx3MVQe9RAAAPyYg
References: <BB375AF679D4A34E9CA8DFA650E2B04E02215963@onstor-exch02.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E04EEC5D7@onstor-exch02.onstor.net> <20070808151249.09cdd6b1@ripper.onstor.net>
From: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	"Warren Gale" <warren.gale@onstor.com>
Cc: "dl-Cougar" <dl-Cougar@onstor.com>

I have no idea what Warren changes are. The space limitation is because
of the common environment structure that is used by bsd, embedded boards
and prom. Changing this structure will not be backward compatible, the
prom will have to be upgraded every time to switch between releases.

The bootp solution is much more flexible, if we really want to boot the
same kernel everywhere this is what I would do.

>-----Original Message-----
>From: Andy Sharp
>Sent: Wednesday, August 08, 2007 3:13 PM
>To: Warren Gale
>Cc: dl-Cougar
>Subject: Re: Just asking...
>
>Well, I'm not just asking... ~:^)
>
>Warren, Max, I'd like to understand why Max's changes and Warren's
>changes can't coexist.  How can it be a space limitation?  We're only
>talking about a handleful of bytes here.
>
>a
>
>On Wed, 8 Aug 2007 14:25:37 -0700 "Maxim Kozlovsky"
><maxim.kozlovsky@onstor.com> wrote:
>
>> There was no space in prom for a longer command without larger
>> modifications, so we'll have to live with modifying the kernels for
>> now.
>>
>> There are alternative methods of setting up the network boot without
>> static configuration files like DHCP/BOOTP etc. Somebody with
infinite
>> time on their hands surely could look into this :-)
>>
>> _____________________________________________
>> From: Larry Scheer
>> Sent: Wednesday, August 08, 2007 2:16 PM
>> To: dl-Cougar
>> Subject: Just asking...
>>
>> Rather than hard coding the unique TFPT boot command information into
>> the each kernel we build is there a way to put this in a
configuration
>> file and either have a shorter command line to invoke the boot of the
>> SSC and embedded processors or a prom setting that points to the TFTP
>> boot configuration file that the kernel can read to find its nfs root
>> and interface settings?
>>
>>
