public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ramfs - is it necessary ???
Date: Thu, 22 Feb 2007 02:50:58 +0100	[thread overview]
Message-ID: <200702220250.58794.volker.armin.hemmann@tu-clausthal.de> (raw)
In-Reply-To: <20070222003724.M75749@xvalheru.org>

On Donnerstag, 22. Februar 2007, pat wrote:
> On Thu, 22 Feb 2007 01:13:56 +0100, Hemmann, Volker Armin wrote
>
> > On Mittwoch, 21. Februar 2007, pat wrote:
> > > Hi,
> > >
> > > I have question about ramfs and if it is necessary. I have notebook
> > > with SATA drive. I generate kernel with genkernel and it generates
> > > initramfs file too. 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.).
> > >
> > > And next question is: hat is difference between ramfs and initrd ??? Is
> > > it the same thing or not ... ???
> > >
> > > Thanks a lot.
> > >
> > > 	Pat
> >
> > 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.
> >
> > 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.
>
> ... so the initramfs is not necessary for the SATA drive when it is not a
> module ??? Because I think I need it because of the SATA drive.
>

if you compile sata support into the kernel, you don't need the initramfs 
stuff.
I have a sata drive too. / and /home are on it. And I boot every day from it, 
without using a initrd or similar stuff.
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-02-22  1:56 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.
2007-02-22  0:39   ` pat
2007-02-22  1:50     ` Hemmann, Volker Armin [this message]
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=200702220250.58794.volker.armin.hemmann@tu-clausthal.de \
    --to=volker.armin.hemmann@tu-clausthal.de \
    --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