mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: grfgguvf@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Whys and hows of initrds
Date: Sun, 6 Nov 2005 23:35:34 +0000	[thread overview]
Message-ID: <200511062335.34520.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <8413367b0511060924s550024b8w1113564cd6bb9340@mail.gmail.com>

On Sunday 06 November 2005 17:24, grfgguvf@gmail.com wrote:
> Hi,
> I don't know if the LKML is a technical kernel development list or a
> newbie support list (or both?) so maybe I'm posting to the wrong
> place.
>
> Questions:
> * Why is an initrd needed?
> * What does it do?

Though there are reasons beyond this, ultimately an initrd is useful primarily 
to distributors, who provide too many drivers to build them all in (the 
resulting kernel image would be too large to boot).

In particular, filesystem, RAID and SCSI drivers (required for rootfs to exist 
before calling onto init), are put into such an image.

> * What are the differences between an initrd and an initramdisk (if
> any)? And an initramfs?
> * Why cannot the task of initrds be done more easily?

> * Why don't other operating systems need an equivalent? Or do they?
>
> Opinions and technical explanations welcome. Please, no excessive flames!

-- 
Cheers,
Alistair.

'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

  parent reply	other threads:[~2005-11-06 23:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-06 17:24 grfgguvf
     [not found] ` <436E4FDF.7000503@mnsu.edu>
2005-11-06 20:56   ` grfgguvf
2005-11-06 21:57     ` Andreas Schwab
2005-11-06 23:35 ` Alistair John Strachan [this message]
2005-11-06 23:58 ` Neil Brown
2005-11-07  1:23   ` grfgguvf
     [not found] <55Wvl-4jY-27@gated-at.bofh.it>
2005-11-06 17:50 ` Robert Hancock

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=200511062335.34520.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --cc=grfgguvf@gmail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®