From mantel@suse.de Mon Mar 30 16:26:50 1998
From: mantel@suse.de
To: users@lists.opensuse.org
Subject: [S.u.S.E. Linux] Re: Re: Fat32 patch
Date: Mon, 30 Mar 1998 18:26:50 +0200
Message-ID: <6foh4a$4lc$1@Galois.suse.de>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0156298509685690012=="

--===============0156298509685690012==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable




Hi,

On Fri, 27 Mar 1998, zentara wrote:

> I don't want to get you upset, since you know all the answers.:-)
> But that patch dosn't work, or else I'm way off in applying it.
>=20
> First it isn't named VFAT32, its called fat32_joliet_nls_patch-0.2.8.

Yes, this is one of the things I dislike about this patch: It collects
several things in one big patch. AFAIK there doesn't exist a VFAT32 patch
alone.

Meanwhile there's a version 0.2.9. I assume this patch will apply better
against recent kernels.

> And it apparently was for "linux-2.0.31-clean" ; cause it
> won't work on "linux-2.0.33.pre.SuSE.3".

I assume it will fail with a clean 2.0.33, too. We didn't change anything
in the relevant parts of the kernel, so you probably need a newer version
of the patch (<A HREF=3D"http://www-plateau.cs.berkeley.edu/people/chaffee/fa=
t32.html"><A HREF=3D"http://www-plateau.cs.berkeley.edu/people/chaffee/fat32.=
html</A">http://www-plateau.cs.berkeley.edu/people/chaffee/fat32.html</A</A>>=
).

> All it did was REMOVE the vfat option from the filesystems
> menu in menuconfig.=20

I think it's not a great deal to apply the rejects manually. But the new
version of the patch explicitly states that it works with 2.0.33.

> I don't use fat32 anyways, so it really dosn't matter--no complaints.
>=20
> But it would be nice to tell people that SuSe supports fat32,
> and even Microsoft dosn't yet in NT.=20

Sure this would be nice. Would save me lots of questions ;-)

> I seem to remember it worked OK under Caldera, it didn't
> seem buggy.

"Didn't seem buggy" is not enough ;-)

This kind of change is very critical, because existing filesystem code is
modified. If we end up with corrupted filesystems we have a BIG problem.
If the kernel is buggy, that's bad for us. If only a S.u.S.E. modified
kernel is buggy whereas the official kernel works, it's much worse for us.
Therefore we're waiting for the inclusion of this patch into the official
kernel. 2.1.x has it already and the web page states it will be included
in 2.0.34 (if it's ever released).

> zentara

    Hubert


--
To get out of this list, please send email to majordomo(a)suse.com with
this text in its body: unsubscribe suse-linux-e


--===============0156298509685690012==--