: All of your loopback devices are in use! (was: Re:
kernel-2.4.0-0.43.4)
"Edward S. Marshall" <[EMAIL PROTECTED]> writes:
> A word to the wise: if you don't currently need initrd to get your system
> online, don't blindly upgrade to 2.4.0-0.43.4; do:
>
>
BS"D
It may sound stupid, but when I once found myself in the same maze as Jens-Ulrik,
the system sent me also a "kernel too big" message. Found no intelligent way to
get out of this. After compiling an own kernel with the new resources it stopped
also complaining about loopback devices.
Maybe
Thanks for your reply.
"John Summerfield" <[EMAIL PROTECTED]> writes:
> Are they there?
> [summer@dugite summer]$ ls /dev/loop?
> brw-rw1 root 7, 0 May 6 1998 /dev/loop0
> brw-rw1 root 7, 1 May 6 1998 /dev/loop1
> brw-rw1 root 7, 2 May 6 1998
[EMAIL PROTECTED] said:
> Is there anything else that needs to be done to enable the loop
> devices?
Are they there?
[summer@dugite summer]$ ls /dev/loop?
brw-rw1 root 7, 0 May 6 1998 /dev/loop0
brw-rw1 root 7, 1 May 6 1998 /dev/loop1
brw-rw1 root
Thanks for the fast reply, Bill.
"Bill Nottingham" <[EMAIL PROTECTED]> writes:
> Jens-Ulrik Petersen ([EMAIL PROTECTED]) said:
> > I am running kernel-2.4.0-0.37.i686 currently and trying to upgrade to
> > 2.4.0-0.43.12 (before that also tried 2.4.0-0.43.11). I seem to have
> > trouble with my
On Fri Jan 12 2001 at 11:32, Jens-Ulrik Petersen wrote:
> I am running kernel-2.4.0-0.37.i686 currently and trying to upgrade to
> 2.4.0-0.43.12 (before that also tried 2.4.0-0.43.11). I seem to have
> trouble with my loop devices, since:
>
> % sudo mkinitrd -v --omit-scsi-modules /boot/initrd-
[EMAIL PROTECTED] said:
> (I get this for all the first 8 loop devices.)
> % sudo losetup /dev/loop8 loop: can't open device /dev/loop8: No such
> device
> What's wrong? Any ideas how to fix this? (I get this same on another
> machine also running RH7 and 2.4.0-test11.)
Sounds to me like yo
Jens-Ulrik Petersen ([EMAIL PROTECTED]) said:
> I am running kernel-2.4.0-0.37.i686 currently and trying to upgrade to
> 2.4.0-0.43.12 (before that also tried 2.4.0-0.43.11). I seem to have
> trouble with my loop devices, since:
>
> % sudo mkinitrd -v --omit-scsi-modules /boot/initrd-2.4.0-0.43
"Edward S. Marshall" <[EMAIL PROTECTED]> writes:
> A word to the wise: if you don't currently need initrd to get your system
> online, don't blindly upgrade to 2.4.0-0.43.4; do:
>
> mkinitrd -v /boot/initrd-2.4.0-0.43.4.img 2.4.0-0.43.4
I am running kernel-2.4.0-0.37.i686 currently and
Pekka Savola ([EMAIL PROTECTED]) said:
> # /sbin/mkinitrd -f -v /boot/initrd-2.4.0-0.43.4.img 2.4.0-0.43.4
> Using modules:
> Using loopback device /dev/loop1
> /sbin/sash -> /tmp/initrd.PeIApz/bin/sash
> /sbin/insmod.static -> /tmp/initrd.PeIApz/bin/insmod
> ---
>
> Whoops. No drivers loaded o
On Fri, 15 Dec 2000, Edward S. Marshall wrote:
> Hmm. "CONFIG_IDE=m"?
>
> So now basically everyone with ordinary PC hardware gets to use initrd?
>
> A word to the wise: if you don't currently need initrd to get your system
> online, don't blindly upgrade to 2.4.0-0.43.4; do:
>
> mkinitrd
Hmm. "CONFIG_IDE=m"?
So now basically everyone with ordinary PC hardware gets to use initrd?
A word to the wise: if you don't currently need initrd to get your system
online, don't blindly upgrade to 2.4.0-0.43.4; do:
mkinitrd -v /boot/initrd-2.4.0-0.43.4.img 2.4.0-0.43.4
And then add
12 matches
Mail list logo
