X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7C3F9.106897C1@onstor-exch02.onstor.net>; Wed, 11 Jul 2007 12:21:29 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7C3F9.106897C1"
Content-class: urn:content-classes:message
Subject: RE: rc.initial over IP
Date: Wed, 11 Jul 2007 12:21:29 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E047C3478@onstor-exch02.onstor.net>
In-Reply-To: <20070711131559.692310bf@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: rc.initial over IP
Thread-Index: AcfD+Evsihgjqa/oSzCOAgMUYMAobQAAH46g
References: <BB375AF679D4A34E9CA8DFA650E2B04E047C3432@onstor-exch02.onstor.net> <20070711131559.692310bf@ripper.onstor.net>
From: "Charissa Willard" <charissa.willard@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7C3F9.106897C1
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

So is this after we move the daemons to inetd?

=20

-----Original Message-----
From: Andy Sharp=20
Sent: Wednesday, July 11, 2007 1:16 PM
To: Charissa Willard
Subject: Re: rc.initial over IP

=20

On Wed, 11 Jul 2007 12:25:29 -0700 "Charissa Willard"

<charissa.willard@onstor.com> wrote:

=20

> Andy,

>=20

> =20

>=20

> 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.

=20

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 ~:^)

=20

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.


------_=_NextPart_001_01C7C3F9.106897C1
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:"Courier New";}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 100.75pt 1.0in 100.75pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>So is this after we move the daemons to =
inetd?<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>-----Original Message-----<br>
From: <st1:PersonName w:st=3D"on">Andy Sharp</st1:PersonName> <br>
Sent: Wednesday, July 11, 2007 1:16 PM<br>
To: <st1:PersonName w:st=3D"on">Charissa Willard</st1:PersonName><br>
Subject: Re: rc.initial over IP</span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>On Wed, 11 Jul 2007 12:25:29 -0700 &quot;<st1:PersonName =
w:st=3D"on">Charissa
 Willard</st1:PersonName>&quot;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>&lt;charissa.willard@onstor.com&gt; =
wrote:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>&gt; Andy,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>&gt;&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>&gt; <o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>&gt; It's my understanding that the dhclient app is run as part =
of the
boot<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>&gt; process. Once the parameters are obtained from a DHCP =
server, we
may<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>&gt; still need to be able to verify these parameters in addition =
to<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>&gt; setting values for those that may not be in the DHCP server. =
We
would<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>&gt; want to do this and then commit the values as we currently =
do in<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>&gt; rc.initial. In order to do this over IP instead of a serial =
cable,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>&gt; would we just need to move the required daemons (sscccc =
&amp; http)
to<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>&gt; inetd? You had suggested this earlier. Please let me know =
your<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>&gt; thoughts on this. At a minimum, we could always do this over =
IP
using<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>&gt; a script and not NCM.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>The daemons should work without modification.&nbsp; If they =
don't, then they<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>need fixin'.&nbsp; After they are fixed, then they will work =
w/o<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>modification ~:^)<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>The dhcp client daemon should be configured to request a minimum =
set of<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>required parameters necessary to connect.&nbsp; We can add a few =
lines to<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>whatever shell script to copy the information to the =
correct<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>locations.&nbsp; At that point the user can connect and the GUI =
initial<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>config should then &quot;take care&quot; of configuring whatever =
items
were not<o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D1 face=3D"Courier New"><span =
style=3D'font-size:
9.0pt'>obtained via dhcp.<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C7C3F9.106897C1--
