From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ramfs - is it necessary ???
Date: Wed, 21 Feb 2007 18:29:33 -0600 [thread overview]
Message-ID: <200702211829.33508.bss03@volumehost.net> (raw)
In-Reply-To: <200702220113.56624.volker.armin.hemmann@tu-clausthal.de>
[-- Attachment #1: Type: text/plain, Size: 1407 bytes --]
On Wednesday 21 February 2007, "Hemmann, Volker Armin"
<volker.armin.hemmann@tu-clausthal.de> wrote about 'Re: [gentoo-user]
ramfs - is it necessary ???':
> On Mittwoch, 21. Februar 2007, pat wrote:
> > My question is if this is realy necessary and if
> > not, what I have to do. And if it is necessary where I can find good
> > documentation (samples, explanation, etc.).
>
> you don't need initrd. You don't need initramfs. You don't need to use
> genkernel (IMHO genkernel is evil). And you don't need ramfs.
That's my experience with genkernel as well.
> initrd/initramfs is mostly for distributions who want to compile
> everything as module, people with strange settings (like some kind of
> raid), or people too stupid to build their own kernel. If you build your
> kernel and build everything you need to boot into it, you can live
> without that crap.
I need it because my '/' in on an LVM device which does require some
userland tools to setup. initrd/ramfs really isn't "crap", but they are
generally unnecessary (unless you have '/' on EVMS/LVM/software-RAID) on
Gentoo.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss03@volumehost.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.org/ \_/
New GPG Key! Old key expires 2007-03-25. Upgrade NOW!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-02-22 0:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 22:42 [gentoo-user] ramfs - is it necessary ??? pat
2007-02-21 23:16 ` Boyd Stephen Smith Jr.
2007-02-22 0:08 ` pat
2007-02-22 0:25 ` Boyd Stephen Smith Jr.
2007-02-22 0:41 ` pat
2007-02-22 10:07 ` Boyd Stephen Smith Jr.
2007-02-22 7:45 ` Alan McKinnon
2007-02-22 10:08 ` Boyd Stephen Smith Jr.
2007-02-22 10:56 ` Dirk Heinrichs
2007-02-22 11:05 ` Alan McKinnon
2007-02-22 18:12 ` Neil Bothwick
2007-02-23 7:11 ` Dirk Heinrichs
2007-02-23 9:36 ` Neil Bothwick
2007-02-22 0:13 ` Hemmann, Volker Armin
2007-02-22 0:29 ` Boyd Stephen Smith Jr. [this message]
2007-02-22 0:39 ` pat
2007-02-22 1:50 ` Hemmann, Volker Armin
2007-02-22 10:08 ` Boyd Stephen Smith Jr.
[not found] ` <200702220958.49233.alan@linuxholdings.co.za>
2007-02-22 10:08 ` Boyd Stephen Smith Jr.
2007-02-22 7:50 ` Alan McKinnon
2007-02-22 8:14 ` Neil Bothwick
[not found] ` <200702221108.31090.alan@linuxholdings.co.za>
2007-02-22 9:18 ` pat
[not found] ` <200702220411.04512.bss03@volumehost.net>
2007-02-22 12:02 ` pat
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=200702211829.33508.bss03@volumehost.net \
--to=bss03@volumehost.net \
--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