Hi,
sorry if this has been covered, or I'm posting to the wrong list (if so,
could you point me in the right direction?). We use Red Hat on a cluster,
and I'm currently trying to modify how we've done things with 7.3 to work
with 9; but I'm stuck and am not sure how best to proceed. We use a
On Thu, 6 Feb 2003, Bret Hughes wrote:
> On Thu, 2003-02-06 at 15:17, Todd A. Jacobs wrote:
> > I thought that initrd was only needed if you required SCSI drivers for the
> > root file system. However, after building a new kernel, both grub and lilo
> > choke on the new k
On Thu, 6 Feb 2003, Bret Hughes wrote:
> ext3 - journaling
Only if ext3 is included as a module, though, according to the
documentation. Hmmm; I'll double-check my kernel config, but I could swear
I built that in.
--
"Of course I'm in shape! Round's a shape, isn't it?"
--
redhat-list mail
On Thu, 2003-02-06 at 15:17, Todd A. Jacobs wrote:
> I thought that initrd was only needed if you required SCSI drivers for the
> root file system. However, after building a new kernel, both grub and lilo
> choke on the new kernel at boot, saying that I didn't specify an initrd.
I thought that initrd was only needed if you required SCSI drivers for the
root file system. However, after building a new kernel, both grub and lilo
choke on the new kernel at boot, saying that I didn't specify an initrd.
Is there something in the kernel config that could be causing thi
On Wed, 22 Jan 2003, Rigler, S C (Steve) wrote:
> If you want to see exactly what mkinitrd does, it is really
> just a bash script. Among other things, it looks at your
> /etc/fstab and /etc/modules.conf to decide what to load
> into the initrd.
oh, i've used mkinitrd before
If you want to see exactly what mkinitrd does, it is really
just a bash script. Among other things, it looks at your
/etc/fstab and /etc/modules.conf to decide what to load
into the initrd.
-Steve
-Original Message-
From: Robert P. J. Day [mailto:[EMAIL PROTECTED]]
Sent: Wednesday
a few related questions, building up to using LVMs:
1) i'm pretty sure this is true, but just wanted to confirm
that part of the install process is to build the initial
"initrd" image based on which features you select during
the install itself.
for the longest tim
In message <[EMAIL PROTECTED]
aux.com>, Stat
ux writes:
> create your own.. there should be a man page for mkinitrd (provided you
> have the mkinitrd package installed) :)
>
> Do you even need an initial ramdisk? Most systems don't.
Red Hat 6.2 install included initrd=ker
On 13-Dec-2000 Bob Taylor opined:
> I installed the kernel-2.2.16-3 updates on my wife's Pentium and
> noticed that there is no initrd installed. What do I do?
As root:
/sbin/mkinitrd /boot/initrd-2.2.16-3.img 2.2.16-3
That will create a new one.
The next question is, do
gt; noticed that there is no initrd installed. What do I do?
>
> Thanks in advance.
>
> Bob
>
>
>
--
-Statux
___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
I installed the kernel-2.2.16-3 updates on my wife's Pentium and
noticed that there is no initrd installed. What do I do?
Thanks in advance.
Bob
--
+---+
| Bob Taylor Email: [EMAIL PROT
da
wdm> Merging with /boot/boot.b
wdm> Boot image: /boot/vmlinuz-2.0.32
wdm> Mapping RAM disk /boot/initrd-2.0.32
wdm> Added linux *
wdm> Boot image: /boot/vmlinuz-2.0.31
wdm> Mapping RAM disk /boot/initrd
wdm> open /boot/initrd: No such file or directory
wdm> ^^^
After installing 5.0 and throwing up the kernels I have this problem:
/sbin/lilo -v
LILO version 20, Copyright 1992-1997 Werner Almesberger
Reading boot sector from /dev/sda
Merging with /boot/boot.b
Boot image: /boot/vmlinuz-2.0.32
Mapping RAM disk /boot/initrd-2.0.32
Added linux *
Boot
Well, I'm running Debian 1.3.
What does Redhat uses /boot/initrd, some
start-up scripts?
Thanks for the reply,
Nikita.
According to Keith Schoenefeld:
>
> What version are you using? In RedHat 5.0 /boot/initrd is required, but
> I've not seen a /initrd directory or
[EMAIL PROTECTED] wrote:
>
> Hi,
>
> I have been cleaning the system, and
> removing directories created by me, that
> I did not use in the last half a year. I
> have a full backup, just in case.
> Anyway, can I delete /initrd ?
&
Hi,
I have been cleaning the system, and
removing directories created by me, that
I did not use in the last half a year. I
have a full backup, just in case.
Anyway, can I delete /initrd ?
Although it was created during
installation, it
17 matches
Mail list logo
