Processing commands for [EMAIL PROTECTED]:
> reopen 475783
Bug#475783: busybox: mounting loopback device fails in initrd (using
live-initramfs)
Bug is already open, cannot reopen.
> reassign 475783 live-initramfs
Bug#475783: busybox: mounting loopback device fails in initrd (using
reopen 475783
reassign 475783 live-initramfs
retitle 475783 generated initrd fails mounting loopback device
thanks
On Mon, 21 Apr 2008, Bastian Blank wrote:
> On Mon, Apr 21, 2008 at 09:28:29AM +0200, Raphael Hertzog wrote:
> > Why aren't you reassigning it to klibc-utils ins
On Mon, Apr 21, 2008 at 09:28:29AM +0200, Raphael Hertzog wrote:
> Why aren't you reassigning it to klibc-utils instead?
Its neither a bug in busybox nor in klibc-utils. It is a bug in a
non-Debian component.
Bastian
--
Without followers, evil cannot spread.
-- Spock, "And The C
On Sun, 20 Apr 2008, Debian Bug Tracking System wrote:
> On Sun, Apr 20, 2008 at 07:37:02PM +0200, Michael Prokop wrote:
> > * Bastian Blank <[EMAIL PROTECTED]> [20080420 19:03]:
> > > On Sun, Apr 13, 2008 at 12:51:29AM +0200, Michael Prokop wrote:
> > So the mount binary of busybox works whereas t
Why should this be a bug in my setup? It used to work just fine. I
never said that this is a bug in klibc-utils or in busybox, but
anyway it's a bug in one of all the involved packages. So why are
you closing my bugreport?
When I use:
mount -t squashfs /dev/loop0 /mnt
mounting the squashfs fil
Your message dated Sun, 20 Apr 2008 20:42:44 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#475783: busybox: mounting loopback device fails in
initrd (using live-initramfs)
has caused the Debian Bug report #475783,
regarding busybox: mounting loopback device fails in
; Nowadays using busybox version 1:1.9.2-2 with different versions of
> > klibc-utils, initramfs-tools and live-initramfs fails at the stage
> > of mounting the loopback device (being a squashfs file behind).
> Please provide commands used and error messages.
That's what I can f
Processing commands for [EMAIL PROTECTED]:
> tags 475783 moreinfo
Bug#475783: busybox: mounting loopback device fails in initrd (using
live-initramfs)
There were no tags set.
Tags added: moreinfo
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tr
erent versions of
> klibc-utils, initramfs-tools and live-initramfs fails at the stage
> of mounting the loopback device (being a squashfs file behind).
Please provide commands used and error messages.
Bastian
--
It is a human characteristic to love little animals, especially if
they'
live-initramfs fails at the stage
of mounting the loopback device (being a squashfs file behind).
I tested several different software versions in all possible
combinations (no setup changes except for the initrds).
The results:
Working
===
ii busybox 1:1.1.3-5
o nothing was actually happening.
Somebody on debianhelp.org said the loopback device doesn't usually cause
problems. I was wondering if I should load drivers from a floppy because my
machine is really old.
Research concludes that the loopback device is used to mount CD-ROMs. Could
my old CD-ROM
?
After all the drivers.tgz is a very large file
end it takes time to process it, especially on old (old equals slow) hardware.
> I researched the loopback device and found out that it's used to mount the
> CD-ROM or something. I'm a first timer with Linux, so I'm not sure wh
d and tried this several more times. Every
time it failed.
I researched the loopback device and found out that it's used to mount the
CD-ROM or something. I'm a first timer with Linux, so I'm not sure what to
do. Maybe the loopback device wasn't being compiled or something? S
ed: from pre by saruman.uio.no with local (Exim 2.12 #7)
id 16N2W4-00016A-00; Sun, 6 Jan 2002 02:54:28 +0100
To: [EMAIL PROTECTED]
Subject: boot-floppies: Missing loopback device and localhost in /etc/hosts
From: Petter Reinholdtsen <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PR
[Philip Blundell]
> Did you actually use this option, or did you continue the installation in
> some other way (e.g. using the new "chroot without rebooting", or by hitting
> Ctrl-Alt-Delete, or anything of that kind)?
I'm pretty sure I used the "Reboot the system" entry, after making the
boot f
The appropriate stuff should get written to /etc/hosts and
/etc/network/interfaces when you choose "Reboot the system" from the main
menu, if the network hasn't ever been configured at that point. It seems
that this didn't happen on your machine, for whatever reason.
Did you actually use this op
Package: boot-floppies
Version: 3.0.17
Severity: important
When installing from CD, and not configuring the network during
install, the loopback device is missing from /etc/network/interfaces
(giving lots of warnings and error messages after boot, and breaking
some server daemons), and
On Sun, Jun 18, 2000 at 02:14:24PM -0400, Adam Di Carlo wrote:
> > > > but the new system has no network file. Interestingly the network file
> > > > is not known on the upgraded system:
> > > > rainer@rakete:~$ dpkg -S /etc/init.d/network
> > > > dpkg: /etc/init.d/network not found.
> > >
> > >
[EMAIL PROTECTED] (Karl M. Hegbloom) writes:
> From: Rainer Dorsch <[EMAIL PROTECTED]>
> Subject: Re: New install / loopback device
> To: [EMAIL PROTECTED]
> Date: Wed, 14 Jun 2000 09:55:45 +0200
> Resent-From: [EMAIL PROTECTED]
>
>
> > > but the new syste
> > but the new system has no network file. Interestingly the network file
> > is not known on the upgraded system:
> > rainer@rakete:~$ dpkg -S /etc/init.d/network
> > dpkg: /etc/init.d/network not found.
>
> /etc/init.d/network has never been known by dpkg, btw, it used
> to be created by boo
CTED]>
Subject: no localhost hostname or loopback device setup on fresh install of potato
X-Reportbug-Version: 0.54
X-Mailer: reportbug 0.54
Date: Thu, 11 May 2000 09:33:22 -0400
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Package: netbase
Version: 3.18-4
Sever
21 matches
Mail list logo
