[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: CALL FOR HELP : debian boot floppies 2.2.15 on apus still not ok.

Sven LUTHER wrote:
> On Sun, Jul 09, 2000 at 01:36:41PM -0700, Daniel Jacobowitz wrote:
> > On Sun, Jul 09, 2000 at 10:24:36PM +0200, Michel Dänzer wrote:
> > > > $ mount -r -t vfat -o loop=/dev/loop0 resceu.bin /mnt
> > > >
> > > > And see if it can be mounted ...
> > >
> > > It works if I omit the '=/dev/loop0' , and now on the second try (after
> > > getting back to the installer main menu) df shows /dev/loop0 .
> > >
> > > So the problem must be elsewhere, any ideas?
> >
> > Oho!  Now that is interesting.  Is /dev/loop0 created properly (I think
> > someone doublechecked that earlier...)?  If so, then I would blame the
> > APUS kernel patches.
> Ok, but remember, when i install the base tarball by hand, the above works
> without problem, with the exact same kernel. But then modules are installed,
> that is the only difference, but the loop module is builtin.
> Could there be another module that has soime influence on this ?

You can find out very easily: lsmod will tell after you have mounted the

What really caught my eye in the log though was that dbootstrap doesn't even
use the -o loop[=...] mount option, it apparently uses losetup to initialize
the loop device and then mounts from it directly. I feel the problem might be
there somewhere.


...and that is how we know the Earth to be banana-shaped.
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

Reply to: