According to Ray Olszewski: While burning my CPU.
>
> See my comments below.
>
> At 12:12 AM 2/5/99 +0000, Richard Adams wrote [with deletions]:
> >According to Ray Olszewski:
> >> 1. On Slackware, the problem occurs between the point where /etc/rc.d/rc.M
> >> starts executing and the where it executes /etc/rc.d/rc.inet1 . So look for
> >> lines you added or changed either in rc.M or at the beginning of rc.inet1 .
> >
> >I dont think its the beginning, as his ethernet card gets found and seeminly
> >configured. Possably either at the end of inet1 or the start of inet2.
> >The message says,
> >loading device 'eth0'
> >ne.c:v1.10 ......
> >NE*000 ethercard probe ....
> >eth0: NE2000 found at......
> >
> >So rc.inet1 is being read and executed.
>
> Not exactly. The eth0 messages you're quoting are from the kernel, when it
> assigns the interface to the physical device, not from rc.inet1, which (on a
> stock Slackware install) doesn't write anything to the screen (unless it
> doesn't find a working eth0).
Correct, if it cant find eth0 then it writes the message which is written
in rc.inet1 which is why i said rc.inet1 IS being read.
I may have been overzellous with the word executed.
>
> In fact, the pop to a shell is occurring between these two messages:
>
> >gling multiuser
>
> >Mounting remote file systems
>
> The first is (I presume) a typo for "Going multiuser", the first echo line
> in rc.M . The second is the first echo line in rc.inet2, which rc.M calls.
> Before it does so, it calls rc.inet1, which sets up the IP address and
> routing for eth0.
I rather think we mean the same thing, i cant imagen why there was a need to
fiddle with those files at all to get samba and X to run at bootime, it
should be enough to just edit /etc/inittab change the first line from
id:3:initdefault:
to
id:4:initdefault:
{ Read Ray's comment on THIS being "Slackware specific". }
That should take care of X, to take care of samba, edit rc.M near the bottom
uncomment the part for "samba", doing that should not produce the problems
being experianced.
Possably it would be a good thing if the person with the problem sent Ray
and me, NOT THE WHOLE LIST, his files, i speak for myself but i think you
Ray will agree that is a sensable thing to do, as one little typo (possably
hidden to the newbie eye) could cause this problem.
Please ask Ray first before flooding his box with your files, i said, i
speak for myself.
A way of preventing this problem would have been "Make backup copys FIRST"
before fiddling with rc files, you can lock up the boot process completly
with invalid entrys.
>
> I assume the eth0 interface is getting its IP address and such, but there's
> no way to know (from the message that was posted) whether this occurs before
> or after the popout to bash. So the problem is, I infer, in one of these places:
>
> -- in rc.M, after the first echo and before the call to rc.inet2
> -- in rc.inet1, anywhere
> -- in rc.inet2, before the first echo
> -- in /etc/inittab, as discussed in my earlier message
>
> NOTE to bystanders: this stuff is all very specific to Slackware. I don't
> think any of the other distributions (certainly not RH, Debian, or S.u.S.E.)
> has an initialization sequence anything like Slackware's any more. So unless
> you use Slackware, don't try to use this for anything.
>
> ------------------------------------"Never tell me the odds!"---
> Ray Olszewski -- Han Solo
> 762 Garland Drive
> Palo Alto, CA 94303-3603
> 650.321.3561 voice 650.322.1209 fax [EMAIL PROTECTED]
> ----------------------------------------------------------------
>
--
Regards Richard.
[EMAIL PROTECTED]
