From: Richard Fish <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] udev & recent genkernel + gentoo-sources
Date: Wed, 13 Jul 2005 22:47:34 +0200 [thread overview]
Message-ID: <42D57DE6.2050207@asmallpond.org> (raw)
In-Reply-To: <42D574EC.7060905@gmail.com>
Zac Medico wrote:
>A. Khattri wrote:
>
>
>>On Wed, 13 Jul 2005, Dmitry S. Makovey wrote:
>>
>>
>>
>>
>>>Nope... might try it as well but my understanding that all genkernel
>>>does is automates compilation/installation and makes sure options for
>>>devfs or udev are on (depending on --[no]udev --[no]devfs flags).
>>>
>>>
>>True, but a lot of people have had problems with genkernel that went away
>>when they did a manual kernel build instead.
>>
>>
>>
>>
>
>In this case the problem is in the initrd so I can guarantee he won't have the same problem if he doesn't use root=/dev/ram0 with a broken initrd ;-).
>
>
>
Not quite, its an initramfs. Slightly different rules apply for
initramfs vs initrd, so you also have to remove the "initrd" line from
grub if you want to eliminate it.
-Richard
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-13 20:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 17:39 [gentoo-user] udev & recent genkernel + gentoo-sources Dmitry S. Makovey
2005-07-13 17:43 ` A. Khattri
2005-07-13 19:04 ` Dmitry S. Makovey
2005-07-13 19:17 ` Rumen Yotov
2005-07-13 19:56 ` A. Khattri
2005-07-13 20:09 ` Zac Medico
2005-07-13 20:47 ` Richard Fish [this message]
2005-07-13 21:11 ` Dmitry S. Makovey
2005-07-13 23:41 ` Dmitry S. Makovey
2005-07-14 0:13 ` Zac Medico
2005-07-14 17:33 ` A. Khattri
2005-07-14 6:03 ` Richard Fish
2005-07-14 6:15 ` Ow Mun Heng
2005-07-14 14:35 ` Dmitry S. Makovey
2005-07-13 18:14 ` Zac Medico
2005-07-13 19:18 ` Richard Fish
2005-07-13 19:42 ` Zac Medico
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=42D57DE6.2050207@asmallpond.org \
--to=bigfish@asmallpond.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