Date: Tue, 4 Jan 2005 20:56:49 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Eric Anderson <anderson@centtech.com> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: portupgrade system destruction? SOLVED Message-ID: <20050105045649.GA77187@xor.obsecurity.org> In-Reply-To: <41DB51F3.4010706@centtech.com> References: <41DA0AB8.3080400@centtech.com> <20050104041859.GA56168@xor.obsecurity.org> <41DA1B2B.5080504@centtech.com> <20050104043510.GA56556@xor.obsecurity.org> <41DB51F3.4010706@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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 [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB23ORWry0BWjoQKURAm7ZAJ9UVsVMaftXKtVjNvL2UitBJyOikwCeNoBQ zQ6rRDZ1zxEOFbuWiAT2Hjs= =SMn+ -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050105045649.GA77187>