AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070711145228.3d8a45f1@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<charissa.willard@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	BB375AF679D4A34E9CA8DFA650E2B04E047C34FE@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 11 Jul 2007 14:52:35 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Charissa Willard" <charissa.willard@onstor.com>
Subject: Re: rc.initial over IP
Message-ID: <20070711145235.505ff238@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E047C34FE@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E047C3432@onstor-exch02.onstor.net>
	<20070711131559.692310bf@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E047C3478@onstor-exch02.onstor.net>
	<20070711132616.68ae499f@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E047C34FE@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 Wed, 11 Jul 2007 14:37:20 -0700 "Charissa Willard"
<charissa.willard@onstor.com> wrote:

> Does this note in the rc.initial script still apply:

I have no idea.  Probably written by one or more people long ago.  I
don't think it's relevant at all anymore -- the daemons can't start if
there is no clusDB and if there is, the rc.initial script will be
skipped.

>  
> 
> # This is phase 1 of some usability improvements, initially just
> reworking
> 
> # of the original rc.initial script to use menus. Currently it only
> sets the
> 
> # date, time, SSC ports, and default route.  Longer term goal is to
> have
> 
> # the initial setup completely configure a machine so that it is ready
> 
> # to create file systems.  To do this, this script should not be
> called
> 
> # by the rc script before the ONStor daemons are all running as it is
> now
> 
> #
> 
>  
> 
>  
> 
> -----Original Message-----
> From: Andy Sharp 
> Sent: Wednesday, July 11, 2007 1:26 PM
> To: Charissa Willard
> Subject: Re: rc.initial over IP
> 
>  
> 
> On Wed, 11 Jul 2007 13:21:29 -0700 "Charissa Willard"
> 
> <charissa.willard@onstor.com> wrote:
> 
>  
> 
> > So is this after we move the daemons to inetd?
> 
>  
> 
> Nope, exactly how everything works today.  The only change that
> *might*
> 
> have to be made is that these daemons listen on 0.0.0.0 rather than a
> 
> specific IP address.  Which they might already do, I don't know.
> 
>  
> 
> > 
> 
> > -----Original Message-----
> 
> > From: Andy Sharp 
> 
> > Sent: Wednesday, July 11, 2007 1:16 PM
> 
> > To: Charissa Willard
> 
> > Subject: Re: rc.initial over IP
> 
> > 
> 
> >  
> 
> > 
> 
> > On Wed, 11 Jul 2007 12:25:29 -0700 "Charissa Willard"
> 
> > 
> 
> > <charissa.willard@onstor.com> wrote:
> 
> > 
> 
> >  
> 
> > 
> 
> > > Andy,
> 
> > 
> 
> > > 
> 
> > 
> 
> > >  
> 
> > 
> 
> > > 
> 
> > 
> 
> > > It's my understanding that the dhclient app is run as part of the
> 
> > > boot
> 
> > 
> 
> > > process. Once the parameters are obtained from a DHCP server, we
> > > may
> 
> > 
> 
> > > still need to be able to verify these parameters in addition to
> 
> > 
> 
> > > setting values for those that may not be in the DHCP server. We
> 
> > > would
> 
> > 
> 
> > > want to do this and then commit the values as we currently do in
> 
> > 
> 
> > > rc.initial. In order to do this over IP instead of a serial cable,
> 
> > 
> 
> > > would we just need to move the required daemons (sscccc & http) to
> 
> > 
> 
> > > inetd? You had suggested this earlier. Please let me know your
> 
> > 
> 
> > > thoughts on this. At a minimum, we could always do this over IP
> 
> > > using
> 
> > 
> 
> > > a script and not NCM.
> 
> > 
> 
> >  
> 
> > 
> 
> > The daemons should work without modification.  If they don't, then
> 
> > they
> 
> > 
> 
> > need fixin'.  After they are fixed, then they will work w/o
> 
> > 
> 
> > modification ~:^)
> 
> > 
> 
> >  
> 
> > 
> 
> > The dhcp client daemon should be configured to request a minimum set
> 
> > of
> 
> > 
> 
> > required parameters necessary to connect.  We can add a few lines to
> 
> > 
> 
> > whatever shell script to copy the information to the correct
> 
> > 
> 
> > locations.  At that point the user can connect and the GUI initial
> 
> > 
> 
> > config should then "take care" of configuring whatever items were
> > not
> 
> > 
> 
> > obtained via dhcp.
> 
> > 
> 
