linux-mips-fnet
[Top] [All Lists]

Re: concurent running init on DECstations

To: linux-mips@fnet.fr
Subject: Re: concurent running init on DECstations
From: Florian Lohoff <flo@rfc822.org>
Date: Mon, 18 Jan 1999 15:38:56 +0100
In-reply-to: <Pine.LNX.3.95.990118141304.1883A-100000@whale.dutch.mountain>; from Richard van den Berg on Mon, Jan 18, 1999 at 02:15:10PM +0100
References: <Pine.LNX.3.95.990118141304.1883A-100000@whale.dutch.mountain>
Sender: flo@mini.gt.owl.de
On Mon, Jan 18, 1999 at 02:15:10PM +0100, Richard van den Berg wrote:
> Hello DECstation fans,
> 
> The DECstations here (5000/25 and 133) aren't able to run multi-user
> yet, using the 2.1.131 kernel, when the system normally boots
> and init is starting the last visible execution is the last line
> of /etc/rc.d/rc.sysinit, which is an echo, after that the machines
> remains silent, ping-'ing them is possible and the only sign of life I
> can discover.
> 
> When rc.sysinit drops into a shell because fstab is missing a line with
> the root filesytem, the machines work fine because they've compiled
> binutils, egcs and there own kernel which runs fine. `ps ax` in this
> shell gives following result:
> 
> [root@fortuna /root]# ps ax
>   PID  TTY STAT   TIME COMMAND
>     1  ?   S      0:00 init bo
>     2  ?   SW     0:00 (kflushd) 
>     3  ?   SWN    0:00 (kswapd) 
>     4  ?   SW     0:00 (rpciod)
>     5  S2  S      0:00 init bo
>     6  S2  S      0:01 sh /etc/rc.d/rc.sysinit
>    15  S2  S      0:01 -bash
>    32  S2  R      0:00 ps ax
> 
> And shows 2 init's to my surprise, which might be the cause of the
> problem. But how is it possible that there are 2 init's running?

That might be a compile time debug option for the init which 
lets the init fork at startup to make in straceable and debuggable ...

Flo
-- 
Florian Lohoff          flo@rfc822.org                  +49-5241-470566
Good, Fast, Cheap: Pick any two (you can't have all three).  (RFC 1925)

<Prev in Thread] Current Thread [Next in Thread>