From: Joost Roeleveld <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: LVM, /usr and really really bad thoughts.
Date: Fri, 16 Mar 2012 06:39:44 +0100 [thread overview]
Message-ID: <5226862.qPPr92EOYK@eve> (raw)
In-Reply-To: <20120315130512.6f19efd1@digimed.co.uk>
On Thursday, March 15, 2012 01:05:12 PM Neil Bothwick wrote:
> On Thu, 15 Mar 2012 08:41:38 -0400, Tanstaafl wrote:
> > > That's why I build the initramfs into the kernel and not as a
> > > separate
> > > file. If I do something to break the initramfs I just boot the
> > > previous kernel knowing it will still work.
> >
> > Ok, time to show my ignorance...
> >
> > How would I know if I am using an initramfs, and if I was, whether it
> > was built into the kernel or not?
>
> Well, you built the kernel, so you should know.
>
> Technically, we are all using an initramfs as all 2.6/3 kernels mount an
> initramfs when they load. If does not contain an init script, they fall
> back to the legacy behaviour.
>
> See /usr/src/linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt
Even when the init-options are not set?
***
admin@hera ~ $ uname -a
Linux hera 2.6.34-xen-r4_dom0 #1 SMP Wed Dec 8 15:52:31 CET 2010 x86_64 AMD
Phenom(tm) II X4 955 Processor AuthenticAMD GNU/Linux
admin@hera ~ $ zcat /proc/config.gz | grep -i init
CONFIG_INIT_ENV_ARG_LIMIT=32
# CONFIG_BLK_DEV_INITRD is not set
# CONFIG_SCSI_OSD_INITIATOR is not set
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
***
--
Joost
next prev parent reply other threads:[~2012-03-16 6:03 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 2:48 [gentoo-user] LVM, /usr and really really bad thoughts Dale
2012-03-10 3:44 ` Canek Peláez Valdés
2012-03-10 4:16 ` Dale
2012-03-10 5:41 ` Canek Peláez Valdés
2012-03-10 6:03 ` Dale
2012-03-10 8:45 ` Neil Bothwick
2012-03-10 9:45 ` Dale
2012-03-10 9:52 ` Neil Bothwick
2012-03-10 9:53 ` Neil Bothwick
2012-03-10 10:30 ` Dale
2012-03-10 10:49 ` Neil Bothwick
2012-03-10 11:28 ` Dale
2012-03-10 11:12 ` William Kenworthy
2012-03-10 10:58 ` pk
2012-03-10 15:35 ` Neil Bothwick
2012-03-10 20:50 ` pk
2012-03-10 21:01 ` Canek Peláez Valdés
2012-03-10 22:12 ` Neil Bothwick
2012-03-11 2:36 ` Canek Peláez Valdés
2012-03-11 9:37 ` pk
2012-03-11 12:16 ` Jorge Martínez López
2012-03-11 18:26 ` Canek Peláez Valdés
2012-03-12 18:13 ` Jorge Martínez López
2012-03-11 20:59 ` [gentoo-user] " walt
2012-03-12 18:23 ` Jorge Martínez López
2012-03-12 18:30 ` Michael Mol
2012-03-12 18:39 ` Bruce Hill, Jr.
2012-03-12 20:25 ` Mick
2012-03-12 20:39 ` Michael Mol
2012-03-12 20:40 ` Alan McKinnon
2012-03-12 23:22 ` Dale
2012-03-12 23:53 ` Canek Peláez Valdés
2012-03-13 15:35 ` Alan McKinnon
2012-03-13 15:50 ` Pandu Poluan
2012-03-13 1:58 ` Mike Edenfield
2012-03-13 4:54 ` Pandu Poluan
2012-03-13 7:13 ` Alan McKinnon
2012-03-13 7:31 ` Pandu Poluan
2012-03-13 7:38 ` Canek Peláez Valdés
2012-03-13 8:03 ` Pandu Poluan
2012-03-13 11:07 ` Neil Bothwick
2012-03-13 18:34 ` pk
2012-03-14 16:17 ` Mike Edenfield
2012-03-14 16:28 ` Pandu Poluan
2012-03-14 22:15 ` Mike Edenfield
2012-03-15 1:03 ` Walter Dnes
2012-03-15 2:47 ` Dale
2012-03-15 9:13 ` Neil Bothwick
2012-03-15 10:10 ` Dale
2012-03-15 10:18 ` Neil Bothwick
2012-03-15 12:41 ` Tanstaafl
2012-03-15 13:05 ` Neil Bothwick
2012-03-15 13:56 ` Tanstaafl
2012-03-15 14:13 ` Neil Bothwick
2012-03-15 14:13 ` Mark Knecht
2012-03-16 5:39 ` Joost Roeleveld [this message]
2012-03-16 8:47 ` Neil Bothwick
2012-03-15 14:09 ` Mike Edenfield
2012-03-15 14:47 ` Michael Mol
2012-03-15 16:37 ` Pandu Poluan
2012-03-16 18:14 ` Dale
2012-03-15 12:38 ` Tanstaafl
2012-03-13 8:09 ` Walter Dnes
2012-03-13 8:20 ` Canek Peláez Valdés
2012-03-14 14:21 ` Dale
2012-03-14 14:41 ` Alan Mackenzie
2012-03-14 14:55 ` Pandu Poluan
2012-03-13 8:15 ` [gentoo-user] " Walter Dnes
2012-03-11 3:25 ` John Blinka
2012-03-10 17:13 ` Todd Goodman
2012-03-10 21:07 ` Dale
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=5226862.qPPr92EOYK@eve \
--to=joost@antarean.org \
--cc=gentoo-user@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