Re: dselect/dpkg problem: install/remove

[Mike Miller <miller5@uiuc.edu>]

>>>>> "bruce" == Bruce Perens <bruce@pixar.com> writes:
[...]
    > It's not likely that dpkg/dselect put the system in this
    > state on its own.  Things that wedge the system and then
    > make e2fsck not run generally have to do with the shared
    > library files containing corrupt data. This could be a
    > problem with the data on the disk, or bad RAM. Probably a
    > re-install would be a good idea at this point, since the
    > data on the disk is suspect.

I agree with that - the next morning e2fsck was able to fix the
problem with no trouble!  Sounds like hardware to me.  Now all I
have to do is track down the problem.

[...]
    > People get upset when I point at hardware, because of
    > course Windows 95 runs fine...
Of course, the first thing I did when I got my machine was delete
all that windows 95 stuff.  Keeps life simple.