libc 5.4 breaks e2fsprogs compiled with 5.2 (fwd)
Does anyone know anything about this? This is the first I've heard
Michael Nonweiler writes:
> From firstname.lastname@example.org Fri Nov 15 19:07:02 1996
> Date: Sat, 16 Nov 1996 01:07:14 +0000 (GMT)
> From: Michael Nonweiler <email@example.com>
> X-Sender: firstname.lastname@example.org
> To: David Engel <email@example.com>
> Subject: libc 5.4 breaks e2fsprogs compiled with 5.2
> Message-ID: <Pine.LNX.3.95.961116005906.2500Bfirstname.lastname@example.org>
> MIME-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> Sender: "Michael R. Nonweiler" <email@example.com>
> I just received this message today. Farzad explains how he managed to
> trash a disk, just by using a version of e2fsprogs compiled against libc
> 5.2, with libc 5.4, due to changes to the llseek function call interface.
> Since this problem is so severe, could you please add a
> Breaks: e2fsprogs (<<1.06-4)
> line to the libc5 control file?
> Do you think there is anything else we should do about this? (a message to
> debian-user/devel or something?)
> Michael Nonweiler <firstname.lastname@example.org>
> Trinity College, Cambridge, England.
> ---------- Forwarded message ----------
> Date: Fri, 15 Nov 1996 23:32:13 +0100 (MET)
> From: Farzad FARID <email@example.com>
> To: Michael Nonweiler <firstname.lastname@example.org>
> Subject: Re: [upload] e2fsprogs-1.06-4 (i386 source)
> I'm sending you this mail because you're the maintainer of the
> utilities that made my life feel like hell today. But it was on a
> slackware, not a Debian, so don't worry :) Here is the probleme I had:
> I'm running a news server on a Linux 1.2.13 with a 4 Gb spool disk (only
> one 4 Go partition for /var/spool/news). For performance reason I decided
> to upgrade the kernel to 2.0.25.
> For the kernel to compile, and to have an homogenous system I decided to
> install the current ELF libc and gcc (yeah the computer was still entirely
> a.out, Slackware really sucks, it's damn hard to maintain/upgrade). So I
> installed libc 5.4.7, gcc 220.127.116.11, etc. I also upgraded some system
> utilities, including e2fsprogs 1.06, whose binary archive I found on
> Then I rebooted and... I was in hell :( After loosing a whole day, and 3
> Go of information on the disk (I ended reformating it), I finally
> discovered that the llseek() system call is NOT portable between libc
> 5.2.x and libc 5.4.x.
> So an e2fsck compiled with libc 5.2.18 does not work on a system running
> libc 5.4.7 when llseek() is needed, and that's the case for a partition
> bigger than 2 Gb. Same for mke2fs and badblocks, etc.
> So my question is: is your package compiled with the latest libc5? If not
> I think it's gonna drive everyone who's got a big partition like mine
> crazy :)
> Farzad FARID
> Administrateur Reseau
> SGIP - Publicis
David Engel Optical Data Systems, Inc.
email@example.com 1001 E. Arapaho Road
(972) 234-6400 Richardson, TX 75081
This message was distributed manually by Bruce@debian.org after the list
initially failed to distribute it.