All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: "Zvi Har'El" <rl@math.technion.ac.il>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 vs resiserfs vs xfs
Date: Thu, 08 Nov 2001 11:06:13 +0000	[thread overview]
Message-ID: <3BEA6725.739463C2@redhat.com> (raw)
In-Reply-To: <E161aYo-0000ch-00@fenrus.demon.nl> <Pine.GSO.4.33.0111080903360.28492-100000@leeor.math.technion.ac.il>

Zvi Har'El wrote:
> 
> Hi all,
> 
> Initrd did it! I was not using initrd. I generated the relevant initrd.img and
> added the line to my grub.conf configuration, and the problem is solved.
> System crashes are now easily recovered.
> 
> The only mystery is, why RedHat has ext3fs compiled as a module?

The basic idea is "everything which can be a module will be a module", 
even scsi is a module. And if you use grub, it's 100% transparent as the
initrd
will be automatically added to the grub config when you install the RH
kernel rpm;
even if you use lilo the initrd is supposed to be made for you
automatically.

Greetings,
    Arjan van de Ven

  reply	other threads:[~2001-11-08 11:06 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-07 15:00 ext3 vs resiserfs vs xfs Roy Sigurd Karlsbakk
2001-11-07 15:23 ` Alan Cox
2001-11-07 15:28   ` Zvi Har'El
2001-11-07 20:19     ` Andreas Dilger
2001-11-07 21:11       ` Zvi Har'El
2001-11-07 21:25         ` Christian Bornträger
2001-11-07 21:45           ` Mike Fedyk
2001-11-07 21:42         ` Andreas Dilger
2001-11-07 22:11           ` arjan
2001-11-07 21:48         ` arjan
2001-11-08  7:08           ` Zvi Har'El
2001-11-08 11:06             ` Arjan van de Ven [this message]
2001-11-08 12:10               ` Zvi Har'El
2001-11-08 12:11                 ` Arjan van de Ven
2001-11-08 11:35           ` ramfs leak Padraig Brady
2001-11-07 16:31   ` ext3 vs resiserfs vs xfs James A Sutherland
2001-11-07 19:38     ` Ville Herva
2001-11-07 19:50       ` Daniel Gryniewicz
2001-11-07 20:24       ` Robert Love
2001-11-07 20:35         ` Andrew Morton
2001-11-07 20:44       ` James A Sutherland
2001-11-07 21:11         ` Andreas Dilger
2001-11-07 21:37           ` ext3 vs resizerfs " Ville Herva
2001-11-07 21:45             ` Andreas Dilger
2001-11-08  0:13           ` ext3 vs resiserfs " James A Sutherland
2001-11-07 18:40 ` Anton Altaparmakov
2001-11-07 19:12   ` Alan Cox
2001-11-07 19:40   ` Anton Altaparmakov
2001-11-07 20:15     ` Andrew Morton
2001-11-07 21:33       ` Mike Fedyk
2001-11-07 22:00         ` Andrew Morton
2001-11-07 22:27           ` Mike Fedyk
2001-11-07 22:56             ` Andrew Morton
2001-11-07 23:18               ` Andreas Dilger
2001-11-07 22:52           ` Mike Fedyk
2001-11-07 22:59             ` Andrew Morton
2001-11-07 23:36               ` D. Stimits
2001-11-07 23:55                 ` Mike Castle
2001-11-07 23:38             ` Mike Castle
2001-11-07 23:49               ` Mike Fedyk
2001-11-08 10:58           ` Juan Quintela
2001-11-07 20:25     ` Andreas Dilger
2001-11-07 23:33       ` Ryan Cumming
2001-11-09 16:11         ` Andreas Dilger
2001-11-07 20:36     ` Anton Altaparmakov
2001-11-07 20:21   ` Andreas Dilger
2001-11-07 20:27   ` Anton Altaparmakov
2001-11-07 20:05 ` Theodore Tso
2001-11-07 20:18 ` Andreas Dilger

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=3BEA6725.739463C2@redhat.com \
    --to=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rl@math.technion.ac.il \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.