unexpected softupdate inconsistency

[Stephen Bader]

Thanks! It is interesting that vi can't do this, but vim can. Very neat
trick, thanks!

-Steve

-------------------------------------------------------------------------
Stephen Bader                  JORSM Internet, Regional Internet Services
Systems Administrator          7 Area Codes in Chicagoland and NW Indiana
steveb at jorsm.com               100Mbps+ Connectivity, 56K-DS3, V.90, ISDN
(219) 322-2180                 Quality Service, Affordable Prices
http://www.jorsm.com           Serving Gov, Biz, Indivds Since 1995
-------------------------------------------------------------------------

On Thu, 11 Mar 2004, Mark Sergeant wrote:

>
>
> On Thu, 2004-03-11 at 01:10, Stephen Bader wrote:
> > Just for my information if I ever run into this in the future, what do you
> > mean by 'use vim on the dir entry'?
> >
>
> vim /usr/ports/editors/vim gives the following output ...
>
> " Press ? for keyboard shortcuts
> " Sorted by name (.bak,~,.o,.h,.info,.swp,.obj at end of list)
> "= /usr/ports/editors/vim/
> ../
> files/
> Makefile
> distinfo
> pkg-descr
> pkg-plist
> ~
>
> you are then able to edit the directory and what files it sees under
> that directory (careful it's easy to break things). So for example if
> the above included work/ which from an ls I can see is not there and a
> rm -rf of /usr/ports/editors/vim was failing then you could edit
> /usr/ports/editors/vim and remove the offending entry which should then
> enable you to remove that directory (hope this isn't too confusing).
>
> Cheers,
>
> Mark
>
> > -Steve
> >
> > -------------------------------------------------------------------------
> > Stephen Bader                  JORSM Internet, Regional Internet Services
> > Systems Administrator          7 Area Codes in Chicagoland and NW Indiana
> > steveb at jorsm.com               100Mbps+ Connectivity, 56K-DS3, V.90, ISDN
> > (219) 322-2180                 Quality Service, Affordable Prices
> > http://www.jorsm.com           Serving Gov, Biz, Indivds Since 1995
> > -------------------------------------------------------------------------
> >
> > On Wed, 10 Mar 2004, Michael Nottebrock wrote:
> >
> > > On Wednesday 10 March 2004 11:23, Manfred Lotz wrote:
> > > > On Wed, 10 Mar 2004 19:21:30 +1000
> > > >
> > > > Mark Sergeant <msergeant at snsonline.net> wrote:
> > > > > In situations like this it can be useful to use vim on the dir entry
> > > > > that is affected and remove the invalid filenames. This has worked for
> > > > > me before.
> > > > >
> > > > > Cheers,
> > > > >
> > > > > Mark
> > > >
> > > > Thanks for the reply. Have to admit that it would have never occured to
> > > > me to do this. Good idea.
> > > >
> > > > Did you experience this often? I'm worried. Never had something like
> > > > this before.
> > >
> > > You should watch that system - filesystems going bad out of the blue are
> > > usually a warning sign of failing hardware (though not necessarily the hdd
> > > itself, might be power issues, bad memory, etc.).
> > >
> > > --
> > >    ,_,   | Michael Nottebrock               | lofi at freebsd.org
> > >  (/^ ^\) | FreeBSD - The Power to Serve     | http://www.freebsd.org
> > >    \u/   | K Desktop Environment on FreeBSD | http://freebsd.kde.org
> > >
> >
> > _______________________________________________
> > freebsd-stable at freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
> --
> Mark Sergeant <msergeant at snsonline.net>
> SNSOnline Technical Services
>