From: Amit D Chaudhary <amit@muppetlabs.com>
To: werner.almesberger@epfl.ch, lermen@fgan.de, linux-kernel@vger.kernel.org
Subject: /linuxrc query
Date: Thu, 22 Mar 2001 22:36:02 -0800 [thread overview]
Message-ID: <3ABAEED2.6020708@muppetlabs.com> (raw)
Hi,
I have a initrd working, a /linuxrc on it that runs and executes. My question
for the commands after pivot_root which works like a charm, thanks to initrd.txt,
what does redirecting stdin\stdout\stderr to dev/console achieve? I thought
since the root is now the "new" root, dev/console will be used automatically?
Also, why chroot, why not call init directly?
#exec chroot . sbin/init 3 <dev/console >dev/console 2>&1
Since the above never returns, what follows in not freed. Does this mean I have
around 4-6 mb of ram being used up unnecessarily? Any solution?
#umount /initrd
#blockdev --flushbufs /dev/ram0 # /dev/rd/0 if using devfs
Thanks and Regards
Amit
next reply other threads:[~2001-03-23 6:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-23 6:36 Amit D Chaudhary [this message]
2001-03-23 6:51 ` /linuxrc query Werner Almesberger
2001-03-23 7:00 ` Amit D Chaudhary
2001-03-23 11:18 ` Werner Almesberger
2001-03-23 17:46 ` Amit D Chaudhary
2001-03-23 7:07 ` Amit D Chaudhary
2001-03-23 11:24 ` Werner Almesberger
2001-03-23 14:07 ` David Woodhouse
2001-03-23 18:00 ` RAMFS, CRAMFS and JFFS2(was Re: /linuxrc query) Amit D Chaudhary
2001-03-23 19:37 ` David Woodhouse
2001-03-23 20:25 ` CRAMFS Bjorn Wesen
2001-03-23 22:01 ` CRAMFS Amit D Chaudhary
[not found] <985356959.24859@whiskey.enposte.net>
2001-03-24 7:33 ` /linuxrc query Stuart Lynne
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=3ABAEED2.6020708@muppetlabs.com \
--to=amit@muppetlabs.com \
--cc=lermen@fgan.de \
--cc=linux-kernel@vger.kernel.org \
--cc=werner.almesberger@epfl.ch \
/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.