> "bruce" == Bruce Perens <[EMAIL PROTECTED]> 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. T
> I tried to use dselect to
> purge the kernel-source package and again dpkg crashed, this time
> leaving me with a hung system. All I could do was power cycle my
> machine since the keyboard was apparently frozen and I could not
> log in on any other consoles. This left me with a bad disk which
> "john" == John Houwen <[EMAIL PROTECTED]> writes:
> I seem to have a similar problem with dselect/dpkg, but not
> with the dpkg-ftp option (haven't gotten that far yet)
> The dselect package has given me problems from the first. I
> made a few errors in my 1st attempt at the
In article "John Houwen" <[EMAIL PROTECTED]> writes:
>
>I have tried to remove these packages, but upon running either
>dselect or dpkg I get something along the lines of "Package is in an
>unstable/condititon please re-install before attempting to remove"
>
The kernel-image, kernel-source and k
o at the /var/lib/dpkg/info to learn "by example" what comes with
every package. In my case, the package_name.list file for the "unstable"
packages in that directory was missing ...and that confused dselect.
Lazaro <[EMAIL PROTECTED]>
__ Re
I seem to have a similar problem with dselect/dpkg, but not with the
dpkg-ftp option (haven't gotten that far yet)
The dselect package has given me problems from the first. I made a
few errors in my 1st attempt at the CDRom install, but managed to get
most of the selected packages unpacked & i
6 matches
Mail list logo
