From: Art Boulatov <art@ksu.ru>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: Russell King <rmk@arm.linux.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: pivot_root & linuxrc problem
Date: Fri, 16 Mar 2001 15:34:45 +0300 [thread overview]
Message-ID: <3AB20865.2070804@ksu.ru> (raw)
In-Reply-To: <Pine.LNX.4.33.0103160822350.1057-100000@mikeg.weiden.de>
Mike Galbraith wrote:
........
>
> Aha.. so that's it. I've never been able to get /linuxrc to execute
> automagically. I wonder why /linuxrc executes on Art's system, but
> not on mine. I can call it whatever I want and it doesn't run unless
> I explicitly start it with init=whatever.
>
> If it does execute though, that explains init complaining.. pid is
> going to be whatever comes after the last thread started (would be
> 8 here). It looks like you're only supposed to do setup things in
> magic filename /linuxrc and not exec /sbin/init from there.
>
> In any case, it looks like renaming linuxrc to whatever.sh and booting
> with init=/whatever.sh instead will likely make init happy.
>
> -Mike
>
>
Thank you for your answers, Mike and Russell.
They made me sure something weird going on with my setup.
And I think a have figured the problem.
I was using etherboot to boot the kernel and initrd.
I should have told you that before, and I'm sorry I did not.
Bootin' localy, with lilo, seems to solve the "PID problem".
I guess that's more of mknbi from etherboot question than kernel-related...
I have to check more in depth the etherboot documenation/sources.
Art.
next prev parent reply other threads:[~2001-03-16 12:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 13:16 pivot_root & linuxrc problem Art Boulatov
2001-03-15 21:11 ` Mike Galbraith
2001-03-15 22:41 ` Russell King
2001-03-16 8:54 ` Mike Galbraith
2001-03-16 12:34 ` Art Boulatov [this message]
2001-03-16 14:05 ` union mounts WAS: " Art Boulatov
2001-03-16 17:37 ` Guest section DW
2001-03-16 23:33 ` Bernd Eckenfels
2001-03-17 10:54 ` Mike Galbraith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3AB20865.2070804@ksu.ru \
--to=art@ksu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mikeg@wen-online.de \
--cc=rmk@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.