Linux-kernel mailing list archive 1998-25,: Re: WARNING Re: SYSENTER based syscalls patch, 2.1.105, RFC

# Re: WARNING Re: SYSENTER based syscalls patch, 2.1.105, RFC

Nix (nix-kernel@esperi.demon.co.uk)
Sun, 21 Jun 1998 22:23:43 +0100 (BST)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Brion Vibber: "Re: Promise Ultra33 controller"
- Previous message: Pine.LNX.3.96.980621125814.16513A-100000@possum.my.ami.com.au: "Pine.LNX.3.96.980621125814.16513A-100000@possum.my.ami.com.au"
- Next in thread: Myrdraal: "Re: WARNING Re: SYSENTER based syscalls patch, 2.1.105, RFC"
- Reply: Myrdraal: "Re: WARNING Re: SYSENTER based syscalls patch, 2.1.105, RFC"

> Try 2.1.42 to find out what is meant by
> severe filesystem corruption.

As a matter of interest[1] what was wrong with 2.1.42? I've heard
it mentioned in passing as a horror story many times, but I still
don't know what was actually wrong with it.

btw, 2.1.106 working fine here.

(I could be really picky and say that audio from my CD doesn't work,
but I don't expect Linux to be able to synthesise missing cables
out of thin air.)

[1] from one who was not using devel kernels or on this list at that
point - indeed, I'd only just started using Linux ;)

    --
    `End users are just test loads for verifying that the system works, kind of
     like resistors in an electrical circuit.' - Kaz Kylheku in c.o.l.d.s

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu

- Next message: Brion Vibber: "Re: Promise Ultra33 controller"
- Previous message: Pine.LNX.3.96.980621125814.16513A-100000@possum.my.ami.com.au: "Pine.LNX.3.96.980621125814.16513A-100000@possum.my.ami.com.au"
- Next in thread: Myrdraal: "Re: WARNING Re: SYSENTER based syscalls patch, 2.1.105, RFC"
- Reply: Myrdraal: "Re: WARNING Re: SYSENTER based syscalls patch, 2.1.105, RFC"