From: Sean <crisper@optonline.net>
To: linux-kernel@vger.kernel.org
Subject: Re: LARGE bug with 2.4.1ac10 and loop filesystem
Date: Mon, 12 Feb 2001 19:02:05 -0500 (EST) [thread overview]
Message-ID: <200102130001.f1D01ob13279@s1.optonline.net> (raw)
In-Reply-To: <E14SRSR-0008JM-00@the-village.bc.nu>
In-Reply-To: <E14SRSR-0008JM-00@the-village.bc.nu>
All,
I just compiled 2.4.1-ac10 with the loop-3 patch from adoeb and it seems to fix
the loopback problems. This is for someone NOT using the encrypted FS since I
did not test this.
If anyone has a better way to make sure everything is working correctly other
than using mkinitrd to test if the loopback works then please let me know.
Thanks for the fix,
Sean
On Mon, 12 Feb 2001 22:28:28 +0000 (GMT), Alan Cox said:
> > > That was Im afraid pure luck. Jens is currently sorting out the
> > > loop problems and has test patches
> >
> > By any chance, are these loop problems the same ones affecting
> > 2.4.2-pre2 and -pre3?
>
> And to varying degrees all 2.4.x kernels right now
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://vger.kernel.org/lkml/
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://vger.kernel.org/lkml/
prev parent reply other threads:[~2001-02-13 0:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-12 21:30 Mircea Ciocan
2001-02-12 21:58 ` Alan Cox
2001-02-12 22:08 ` Mircea Ciocan
2001-02-12 22:20 ` Michael J. Maravillo
2001-02-12 22:28 ` Alan Cox
2001-02-13 0:02 ` Sean [this message]
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=200102130001.f1D01ob13279@s1.optonline.net \
--to=crisper@optonline.net \
--cc=linux-kernel@vger.kernel.org \
/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®