From: "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] initrd
Date: Sat, 29 Oct 2005 17:36:59 +0200 [thread overview]
Message-ID: <200510291736.59906.volker.armin.hemmann@tu-clausthal.de> (raw)
In-Reply-To: <436231EC.6080707@manchester.ac.uk>
On Friday 28 October 2005 16:13, DR GM SEDDON wrote:
> Dear list,
> I have just started using Gentoo and up-to-now am impressed. I have
> generated a kernel using 'genkernel' and the kernel is in /boot.
> However, I do not have 'initrd' but 'initramfs'. is this a problem or
> should I modify grub appropriately?
> Gavin.
I touched genkernel only once (when a friend used it, and it made a totally
useless kernel) and from my experience it builds inadequate kernels.
Plus, if you are not using raid, any initrd/initramfs just adds time and
overhead to your booting. It is a waste of ressources.
The only ones who 'need' it are distributions, who do want to use a 'one
kernel fits all' approach and people with / on a raid/dm device.
Just build a kernel by yourself. It is easy.
make menuconfig
mount /boot
make all modules_install install
and let grub.conf point to vmlinuz and vmlinuz.old.
The install run will create a vmlinuz link to your latest kernel and a
vmlinuz.old link to the one used.
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-29 15:38 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 14:13 [gentoo-amd64] initrd DR GM SEDDON
2005-10-28 14:54 ` Mark Knecht
2005-10-28 15:27 ` [gentoo-amd64] initrd Duncan
2005-10-29 15:36 ` Hemmann, Volker Armin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-28 16:19 [gentoo-amd64] initrd Dmitri Pogosyan
2005-10-29 6:12 ` Lee Thompson
2005-10-29 13:21 ` DR GM SEDDON
2005-10-29 13:29 ` Craig Webster
2005-10-29 14:16 ` DR GM SEDDON
2005-10-29 15:41 ` Karol Krizka
2005-10-30 9:48 ` DR GM SEDDON
2005-10-30 15:45 ` Karol Krizka
2005-10-30 17:38 ` William Tetrault
2005-10-29 16:40 ` Drake Donahue
2005-10-29 18:12 ` Drake Donahue
2005-10-29 17:15 ` William Tetrault
2005-10-31 1:23 ` bruce harding
2005-10-29 23:49 Dmitri Pogosyan
2005-10-29 23:54 Dmitri Pogosyan
2005-10-30 15:59 Dmitri Pogosyan
2005-10-30 17:35 ` Karol Krizka
2005-10-31 9:33 ` DR GM SEDDON
2005-10-30 15:59 Dmitri Pogosyan
2005-10-30 18:07 Dmitri Pogosyan
2005-10-30 19:24 ` William Tetrault
2005-10-30 20:32 ` Nuitari
2005-10-31 9:52 ` DR GM SEDDON
2005-10-31 13:43 ` DR GM SEDDON
2005-10-31 16:39 ` Drake Donahue
2005-11-01 14:45 ` DR GM SEDDON
2005-11-01 17:31 ` Drake Donahue
2005-11-01 18:06 ` Drake Donahue
2005-11-02 12:38 ` DR GM SEDDON
2005-11-02 13:14 ` Harm Geerts
2005-10-31 9:47 ` DR GM SEDDON
2005-10-31 0:56 Dmitri Pogosyan
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=200510291736.59906.volker.armin.hemmann@tu-clausthal.de \
--to=volker.armin.hemmann@tu-clausthal.de \
--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