From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: Can initrd and/or RAID be disabled at boot?
Date: Thu, 27 Jun 2013 21:43:08 +0000 (UTC) [thread overview]
Message-ID: <pan$87f0e$d3aed2fe$b1167fed$a3daad7a@cox.net> (raw)
In-Reply-To: pan$1c1f0$15d94a4c$dd2793d$9fc594cf@cox.net
Duncan posted on Thu, 27 Jun 2013 18:53:08 +0000 as excerpted:
> But unfortunately, I've not actually tried the noinitrd kernel
> commandline option, so I can't VERIFY that it works here, with my now
> builtin initramfs. I'll have to reboot to try that, and will try to get
> back to you on that. (Note to self. Test the root=LABEL with
> initramfs-less boot too, while I'm at it.)
I couldn't get the noinitrd option to work here either, on builtin
initramfs.
Not too big a deal tho because as I think you (Mark, grandparent poster)
suggested, it's always possible to rebuild a new kernel without the
initramfs built-in. And if a kernel fails with its builtin for some
reason, there's still the previous kernels with their known working
builtins. So just as I can always boot a backup kernel when a new kernel
fails, I can always boot a backup kernel when the builtin initramfs fails.
Which of course means I didn't try the root=LABEL without an initramfs.
But one other option I DID try... rdinit= . This parameter is similar to
the init= parameter, but for the initr*. It is thus possible to, for
instance, do something like rdinit=/bin/bash (assuming that's the shell
available in your initr*), and get a direct initrd shell, instead of the
script that /bin/init usually is in the initr*. Then in that shell you
can do whatever manual thing you want, and possibly finish up with an
exec /bin/init or whatever, to run the normal rdinit script.
Of course another option would be to setup multiple scripts in the initr*,
each of which could be run as the rdinit replacement, but doing different
things. It would then obviously be possible to have one of those scripts
do something else entirely, whether that be mounting a different root, or
running a memory checker, or starting a game (either in the initr* itself
or mounting a different root to do it), or...
You could then set rdinit= in the kernel commandline to select the
replacement rdinit script you wanted.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2013-06-27 21:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 22:51 [gentoo-amd64] Can initrd and/or RAID be disabled at boot? Mark Knecht
2013-06-26 22:53 ` Bob Sanders
2013-06-27 13:40 ` Mark Knecht
2013-06-27 18:53 ` [gentoo-amd64] " Duncan
2013-06-27 20:52 ` Mark Knecht
2013-06-28 0:14 ` Duncan
2013-06-27 21:43 ` Duncan [this message]
2013-07-01 21:10 ` [gentoo-amd64] " Paul Hartman
2013-07-02 17:06 ` Mark Knecht
2013-07-03 1:47 ` [gentoo-amd64] " Duncan
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='pan$87f0e$d3aed2fe$b1167fed$a3daad7a@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-amd64@lists.gentoo.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox