Re: missing libncurses.so.5 and other lib*
From: Brian Fundakowski Feldman (green_at_freebsd.org)
Date: 05/03/04
- Previous message: Dag-Erling Smørgrav: "Re: missing libncurses.so.5 and other lib*"
- Maybe in reply to: Kevin Oberman: "Re: missing libncurses.so.5 and other lib*"
- Next in thread: Ion-Mihai Tetcu: "Re: missing libncurses.so.5 and other lib*"
- Reply: Ion-Mihai Tetcu: "Re: missing libncurses.so.5 and other lib*"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: "Kevin Oberman" <oberman@es.net> Date: Mon, 03 May 2004 12:19:24 -0400
"Kevin Oberman" <oberman@es.net> wrote:
> > Date: Sun, 02 May 2004 19:33:21 -0700
> > From: Kris Kennaway <kris@obsecurity.org>
> > Sender: owner-freebsd-current@freebsd.org
> >
> > Joshua Boyd wrote:
> >
> > >> If you have a /rescue directory (which you should), then
> > >> boot into single user mode and specify /rescue/sh as your
> > >> shell. Next, mount your filesystems with /rescue/mount
> > >> and restore the missing libraries from your backup tapes.
> > >>
> > >>
> > >>
> > > Yes, I'm sure that he has backup tapes for his laptop. *rolls eyes*
> >
> > You mean you don't back up the contents of your laptop that runs
> > -CURRENT? You must like living dangerously and/or spending lots of time
> > recovering from errors.
>
> Lots of people live dangerously for a long time without realizing it.
> I've been running CURRENT on my laptop since months before 5.0-Release
> and I think I've only had to resort to my backup once. If I had been
> luckier, it would have never happened. (And, if my timing had been a bit
> worse, it could have happened a LOT more often.)
>
> Until someone has been bitten, they almost never do backups and, after
> being bitten they get careless after a while. Takes a few bites (or a
> really nasty one) before the lesson is really learned.
I never lost a single thing to -CURRENT (lost a few "just modified" files to
SoftUpdates/fsck default behavior, though) on my system for over half a
decade -- in fact, I don't remember reinstalling since 1998 or so -- until
an actual hardware failure recently. One CPU fan stopped and the
temperatures got high enough I saw corruption of almost every partition on
one hard drive (thankfully, though, not /home).
I would never choose to equate running -CURRENT with "living dangerously."
I know there are several cases in the past where certain drivers have been
screwed up for a short period of time such that users of those
less-ubiquitous devices would see that, but not stuff like normal IDE hard
drives.
-- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ _______________________________________________ freebsd-newbies@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-newbies To unsubscribe, send any mail to "freebsd-newbies-unsubscribe@freebsd.org"
- Previous message: Dag-Erling Smørgrav: "Re: missing libncurses.so.5 and other lib*"
- Maybe in reply to: Kevin Oberman: "Re: missing libncurses.so.5 and other lib*"
- Next in thread: Ion-Mihai Tetcu: "Re: missing libncurses.so.5 and other lib*"
- Reply: Ion-Mihai Tetcu: "Re: missing libncurses.so.5 and other lib*"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|