Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Mar 1999 04:00:11 +0100
From:      Roelof Osinga <roelof@eboa.com>
To:        Greg Lehey <grog@lemis.com>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: Have crashed, won't travel
Message-ID:  <36F1BDBB.E9E4F323@eboa.com>
References:  <19990303195632.B441@lemis.com> <36DDBFEB.86D89D20@eboa.com> <19990304095813.I441@lemis.com> <36DDEFFD.A4DB4978@eboa.com> <19990304130126.B441@lemis.com> <36DE0352.E99BCB70@eboa.com> <19990316174710.H429@lemis.com> <36EE54A4.8DC53017@eboa.com> <19990317093436.G429@lemis.com> <36EFC56A.ACBFB0A7@eboa.com> <19990318100818.L429@lemis.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Greg Lehey wrote:
> 
> > Hm. Same of course with 'rm -f PLIST'. Can't even rename it. Something's
> > fishy in the state of Denmark (to quote Inspector Clouseau).
> 
> Looks like it's time to learn to use fsdb.  I've never used it myself,
> but from the man page you should be able to go in there and remove the
> entries.

Pretty much a straightforward operation. You cd to the directory and
rm the file by name. Then I did a fsck which wanted to reconnect an inode.
Went back in with fsdb and there it was again <g>. Deleted it again and
fsck'd to find it truly gone.

Well, let's hope that was the last of it, crash aftermath that is.


Constructive (intended :) criticisms:

One thing is that when fsdb comes up it does so with the message:

  /dev/wd0s1g is not a character device
  CONTINUE? [yn]

I mean, I thought that was the whole point of the excercise. To
manipulate a block device's inode tables. So why ask confusing
questions when they are clearly superfluous. The man page doesn't
mention it.

This message sounds like a warning that you're about to do
something quite foolish. Like, doesn't everybody know you can
only use it with fifo devices... Usually one presents such
messages to warn folk that the device given is not of the
type normally used. To wit, a character device.

Also it ends with:

  No entry for terminal type "cons25"
  using dumb terminal settings

Which of course leads one to believe it comes complete with
a fancy visual editor. Point and shoot file system manipulation.
Microsoft eat your heart out kind of thing. Whereas I don't
think that is the case. In fact, I would be mighty - but pleasantly
so - surprised to learn that it was. Also, I think most uses
will be in single user mode with nada but the root mounted. So
why bother searching for a terminal type at all? Hm. Come to 
think of it. termcap is in /etc and was part of the root 
device. So why didn't it find cons25?

Roelof

-- 
Home is where the (@) http://eboa.com/ is.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36F1BDBB.E9E4F323>