portupgrade system destruction? SOLVED

Kris Kennaway kris at obsecurity.org
Wed Jan 5 04:56:26 GMT 2005


On Tue, Jan 04, 2005 at 08:33:23PM -0600, Eric Anderson wrote:

> For those that are curious - what happened was the night before, I 
> installed a new port, but needed to change $PREFIX to a user's home area 
> to set the port up in that particular spot.  As expected, that went 
> uneventfully. The next morning,  I decided to do a portupgrade - and 
> promptly went about cvsupping my ports, bla bla, and then doing a 
> portupgrage -arR.  However - I never unset the $PREFIX variable, so each 
> port was being removed from the main system area, then the new port was 
> being installed in a users' home area.  Bash was one of the first to be 
> done, which explains the login errors (/usr/local/bin/bash was removed 
> from /etc/shells, and it was replaced with 
> /home/username/usr/local....bash, so my shell in the passwd file no 
> longer was in /etc/shells file).  The portupgrade continued until some 
> point when it basically killed itself off.
> 
> I'm now recovering pieces of the installed packages.
> 
> :)

Ouch :)

Glad to hear you're getting back on track.

Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-chat/attachments/20050104/c1e6e9d9/attachment.bin


More information about the freebsd-chat mailing list