AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080219154044.6a46d58c@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<warren.gale@onstor.com>,<brian.stark@onstor.com>,<larry.scheer@onstor.com>,<tim.gardner@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E08627CCF@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 19 Feb 2008 15:41:24 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Warren Gale" <warren.gale@onstor.com>
Cc: "Brian Stark" <brian.stark@onstor.com>, "Larry Scheer"
 <larry.scheer@onstor.com>, "Tim Gardner" <tim.gardner@onstor.com>
Subject: Re: Check out this wild boot sequence when using rev 1.0.4 proms
Message-ID: <20080219154124.421e4457@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E08627CCF@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E08627A9E@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E056C93C2@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E08627AE6@onstor-exch02.onstor.net>
	<20080219114725.7aacd851@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E08627CCF@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Tue, 19 Feb 2008 13:53:43 -0800 "Warren Gale"
<warren.gale@onstor.com> wrote:

> Ok, let me see, I believe this is what everyone wants:
> 
>  
> 
> Boot from
> 
> Environments
> 
> PROM passes in
> 
> Net
> 
> Load_src = network
> 
> Boot_dev =   don't care
> 
>   Arg [0] = bsd
              ^^^
might not be the best idea to pass this.

>   Arg [1] = root=/dev/nfs
> 
>   Arg [2] = ip=dhcp
              ^^^^^^^

Nope, do not pass this here.  root=/dev/nfs only.  The kernel will take
care of the rest.

> Sda1   CF present in other slot
> 
> Load_src = disk
> 
> Boot_dev = sda1
> 
>   Arg [0] = g
> 
>   Arg [1] = root=/dev/sda1
> 
>   Arg [2] = ip=none
> 
>   Arg [3] = rootdelay=1
> 
> Sda2   CF present in other slot
> 
>  
> 
> Load_src = disk
> 
> Boot_dev = sda2
             ^^^^
er?

>   Arg [0] = g
> 
>   Arg [1] = root=/dev/sdb2
                        ^^^^
ner
 
>   Arg [2] = ip=none
> 
>   Arg [3] = rootdelay=1
> 
> Sda1   no CF in other slot
> 
>  
> 
> Load_src = disk
> 
> Boot_dev = sda1
> 
>   Arg [0] = g
> 
>   Arg [1] = root=/dev/sda1
> 
>   Arg [2] = ip=none
> 
>   Arg [3] = rootdelay=1
> 
> Sda2   no CF in other slot
  ^^^^
something's gone way off course here

>  
> 
> Load_src = disk
> 
> Boot_dev = sda2
             ^^^^
ger?

>   Arg [0] = g
> 
>   Arg [1] = root=/dev/sda1
> 
>   Arg [2] = ip=none
> 
>   Arg [3] = rootdelay=1
> 
>  
> 
> Is this correct?
> 
>  
> 
> Thanks,
> 
> Warren
> 
>  
> 
>  
> 
> -----Original Message-----
> From: Andy Sharp 
> Sent: Tuesday, February 19, 2008 11:47 AM
> To: Brian Stark
> Cc: Larry Scheer; Warren Gale; Tim Gardner
> Subject: Re: Check out this wild boot sequence when using rev 1.0.4
> proms
> 
>  
> 
> On Tue, 19 Feb 2008 10:52:22 -0800 "Brian Stark"
> 
> <brian.stark@onstor.com> wrote:
> 
>  
> 
> > Larry,
> 
> > 
> 
> > Excellent, thanks to both you and Warren for jumping on this.  We
> > will
> 
> > make this fix part of 1.0.5.
> 
> > 
> 
> > 
> 
> > Andy,
> 
> > 
> 
> > Let us know how you'd like to proceed with ip=dhcp and any other
> 
> > command line args.
> 
>  
> 
> The prom should not pass in ip=dhcp.  If boot_dev is CF, then it
> 
> should pass in ip=none and rootdelay=1 in addition to the
> root=boot_dev
> 
> argument.   It appeared to be doing that in the trace Larry sent,
> 
> except that it got the boot_dev wrong.
> 
>  
> 
> Cheers,
> 
>  
> 
> a
> 
>  
> 
>  
> 
