On Fri, Dec 28, 2007 at 12:23:29AM +0100, Jens Seidel wrote:
>
> using
> # LANG=C e2fsck.static /dev/sda1
> I get
>
> FATAL: kernel too old
> Speicherzugriffsfehler
>
> (Speicherzugriffsfehler = segmentation fault)
>
> I use a Woody system with up-to-date e2fsck-static:
> $ uname -a
> Linux Erde 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686 unknown
>
> What kernel version do I need to be able to start e2fsck.static?
> Is this related to the crash?
I take it you you installed the latest e2fsck-static package on a
woody system, right? That package was meant for Debian etch or lenny
systems, since the latest uuid library uses the Thread Local Storage
feature, which requires a 2.6 linux kernel --- and Debian stopped
support 2.4 kernels starting with Debian etch.
If you recompile e2fsprogs on your woody system, it will notice that
you are running on a system that doesn't support TLS, which will
result in slightly less reliable UUIDD generation on a multiprocessor
machine. But if all you want is e2fsck-static, that won't matter
anyway.
Hmm... it hadn't occurred to me that people running back-level Debian
systems would attempt to take e2fsck-static and installing it on their
systems. It makes sense that they would do that, since e2fsck-static
has no libc dependencies so it would work (up until now) and that way
they could get the benefit of the latest e2fsprogs updates/fixes
easily.
And it looks like woody backports stopped a while ago, so that
wouldn't work as a solution.
I will look into disabling TLS support for the bootfloopies udeb
packages, and grab that version of e2fsck when building the
e2fsck-static package. No promises, Debian has stopped supporting
both woody and 2.6 kernels in general already, and there was never any
guarantee that this would work, but if it's not too much trouble, I'll
try to make it possible for e2fsck-static to be installed on old 2.4
based systems. In the meantime, if you rebuild e2fsprogs yourself,
that should work for you.
Regards,
- Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
