mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ville Herva <vherva@mail.niksula.cs.hut.fi>
To: Nate Eldredge <neldredge@hmc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.1ac17 hang on mounting loopback fs
Date: Sun, 18 Feb 2001 02:01:40 +0200	[thread overview]
Message-ID: <20010218020140.F5199@niksula.cs.hut.fi> (raw)
In-Reply-To: <14990.18933.849551.526672@mercury.st.hmc.edu> <E14UE0r-00071Q-00@the-village.bc.nu> <14990.57922.176851.105401@mercury.st.hmc.edu>
In-Reply-To: <14990.57922.176851.105401@mercury.st.hmc.edu>; from neldredge@hmc.edu on Sat, Feb 17, 2001 at 12:42:42PM -0800

On Sat, Feb 17, 2001 at 12:42:42PM -0800, you [Nate Eldredge] claimed:
> Alan Cox writes:
>  > > # mount -t ext2 -o loop /spare/i486-linuxaout.img /spare/mnt
>  > > loop: enabling 8 loop devices
>  > 
>  > Loop does not currently work in 2.4. It might partly work by luck
>  > but thats it.  This will change as and when the new loop patches go
>  > in. Until then if you need loop use 2.2
> 
> I see.  Thank you.  I can live without it until then.
> 
> Btw, I applied Jens Axboe's loop-3 patch as suggested by Ville Herva.
> It applied with some fuzz and offset.  However, when I booted it, the
> kernel oopsed when I tried to mount the first ordinary ext2 partition
> (no loopback involved).  I can post the oops if anyone cares, but I
> presume that loop-3 and 2.4.1ac17 are just incompatible.

I'm not sure if it'll apply any more cleanly (and work), but the newest is
loop-4 at

ftp://ftp.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.2-pre1

(It should work with 2.4.1pre1, at least).


-- v --

v@iki.fi

  reply	other threads:[~2001-02-18  0:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-17  9:52 Nate Eldredge
2001-02-17 20:31 ` Alan Cox
2001-02-17 20:42 ` Nate Eldredge
2001-02-18  0:01   ` Ville Herva [this message]
2001-02-18  0:19     ` Pete Toscano
2001-02-18  3:28       ` Thomas Molina
2001-02-18  5:15         ` Pete Toscano

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=20010218020140.F5199@niksula.cs.hut.fi \
    --to=vherva@mail.niksula.cs.hut.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neldredge@hmc.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®