public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Dmitri Pogosyan" <pogosyan@phys.ualberta.ca>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] initrd
Date: Sun, 30 Oct 2005 17:56:22 -0700	[thread overview]
Message-ID: <200510310056.j9V0uM728063@webmail.phys.ualberta.ca> (raw)

It is not needed, I believe, with new kernels. Remnants from the earlier 
days, in my case. I am still mostly on 2.6.11 kernel with devfs, actually, 
and am used to combinations udev+nodevfs, devfs+noudev (which had quite 
magical interactions between themselves, BTW) 
 
 
> On Sat, 29 Oct 2005 14:21:52 +0100 
> DR GM SEDDON <gavin.m.seddon@manchester.ac.uk> wrote: 
>  
> > Dmitri Pogosyan wrote: 
> >  
> > >Not really, you can use initramfs in place of initrd. I have in 
> > >grub.conf  
> > >  
> > >title=Gentoo Linux 2.6.13-r3 UDEV  
> > >root (hd0,0)  
> > >kernel /kernel-2.6.13-gentoo-r3 root=/dev/ram0 ramdisk=16384 
> > >init=/linuxrc real_root=/dev/sda2 vga=3847 udev  
> > >initrd /initramfs-2.6.13-gentoo-r3  
>  
> I've notice that some ppl are putting udev on the kernel line.  I was 
> under the impression that this was not needed to get udev working? 
>  
> -- 
> bruce 
> --  
> gentoo-amd64@gentoo.org mailing list 
 
 
 
 
-- 
gentoo-amd64@gentoo.org mailing list



             reply	other threads:[~2005-10-31  0:59 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31  0:56 Dmitri Pogosyan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-10-30 18:07 [gentoo-amd64] initrd 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-30 15:59 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-29 23:54 Dmitri Pogosyan
2005-10-29 23:49 Dmitri Pogosyan
2005-10-28 16:19 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-28 14:13 DR GM SEDDON
2005-10-28 14:54 ` Mark Knecht
2005-10-29 15:36 ` Hemmann, Volker Armin

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=200510310056.j9V0uM728063@webmail.phys.ualberta.ca \
    --to=pogosyan@phys.ualberta.ca \
    --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