had a big problem this afternoon - had some serious issues with the
reiserfs on /dev/hda1 (an oldish 1.6 gig maxtor), ended up not being
able to fsck it to an orderly state. Had to redo the whole fs, (should
have made a backup) and grab a /var from a ubuntu disk. Obviously,
ubuntu is not debian,
David E. Fox wrote:
had a big problem this afternoon - had some serious issues with the
reiserfs on /dev/hda1 (an oldish 1.6 gig maxtor), ended up not being
able to fsck it to an orderly state. Had to redo the whole fs, (should
have made a backup) and grab a /var from a ubuntu disk. Obviously,
On Wed, 11 Oct 2006 14:54:01 +0200
Johannes Wiedersich [EMAIL PROTECTED] wrote:
I've also had some issues with reiserfs and have always sticked to ext3
ever since. I guess the advantages of reiserfs don't warrant experiments
on important data. ext3 is rock solid on debian. YMMV.
Well, I had
Greetings,
apt-get complains:
dpkg: parse error, in file `/var/lib/dpkg/status' near line 18124 package `ksysguard':
`Depends' field, reference to `xlibs': version contains ` '
Indeed, the status file at that line looks like this
Replaces: kdebase ( 4:3.0.0), kdebase-doc ( 4:3.0.0), kpm (
On Tue, Nov 08, 2005 at 05:04:43PM -0500, Aaron Stromas wrote:
Greetings,
apt-get complains:
dpkg: parse error, in file `/var/lib/dpkg/status' near line 18124 package
`ksysguard':
`Depends' field, reference to `xlibs': version contains ` '
Indeed, the status file at that line looks like
On 11/8/05, Roberto C. Sanchez [EMAIL PROTECTED] wrote:
Is there a graceful way to fix it? TIA,Edit the file and change it to libsm6 | xlibs ( 4.1.0)
just plain editor? no fancy tools? worked, though. thanks!
-a
Joey Hess wrote:
David A. Cobb wrote:
I found a huge problem with my /var filesystem. Or, at least, fsck was
going to take all day and more fixing 11 inode block numbers each pass.
It's supposed to be possible to clean /var, or at least FHS suggests
so.
Not really, it only says
Joey Hess wrote:
David A. Cobb wrote:
I found a huge problem with my /var filesystem. Or, at least, fsck was
going to take all day and more fixing 11 inode block numbers each pass.
It's supposed to be possible to clean /var, or at least FHS suggests
so.
Not really, it only says
I found a huge problem with my /var filesystem. Or, at least, fsck was
going to take all day and more fixing 11 inode block numbers each pass.
It's supposed to be possible to clean /var, or at least FHS suggests
so. And it was messing me up horribly anyway. So, I re-initialized /var.
One
David A. Cobb wrote:
I found a huge problem with my /var filesystem. Or, at least, fsck was
going to take all day and more fixing 11 inode block numbers each pass.
It's supposed to be possible to clean /var, or at least FHS suggests
so.
Not really, it only says you can delete data from
This morning I made the mistake of remotely killing an 'apt-get update'
that had not finished running on another terminal. Now, apt-get is
totally broken. Whenever I try to install anything, I get:
debconf: DbDriver config: /var/cache/debconf/config.dat is locked by
another process
and
Andrew Schulman wrote:
This morning I made the mistake of remotely killing an 'apt-get update'
that had not finished running on another terminal. Now, apt-get is
totally broken. Whenever I try to install anything, I get:
debconf: DbDriver config: /var/cache/debconf/config.dat is locked
Andrew Schulman wrote:
This morning I made the mistake of remotely killing an 'apt-get update'
that had not finished running on another terminal. Now, apt-get is
totally broken. Whenever I try to install anything, I get:
debconf: DbDriver config: /var/cache/debconf/config.dat is
13 matches
Mail list logo
