Date: Fri, 21 Jan 2005 10:55:17 -0600 From: "Johan Kuuse - Red Antigua" <kuuse@redantigua.com> To: "Ryan Sommers" <ryans@gamersimpact.com> Cc: current@freebsd.org Subject: Re: Problem with crt1.o and init tls Message-ID: <00ba01c4ffd9$fd5e7a70$10bca1cd@widserver1> References: <000a01c4ffd2$86d5cc70$10bca1cd@widserver1> <50177.208.4.77.66.1106324544.squirrel@208.4.77.66>
next in thread | previous in thread | raw e-mail | index | archive | help
OK, any suggestion? I admit I'm having a disaster. What I think about now (the ultimate case) is to get another HDD, install 5.3 on that HDD, mount this disaster as a second HDD to recover data. But I really wanted to get some experience in source updating, so if there is someway to get rid of this disaster, I would really appreciate som hints. Best Regards, Johan Kuuse kuuse@redantigua.com ----- Original Message ----- From: "Ryan Sommers" <ryans@gamersimpact.com> To: "Johan Kuuse - Red Antigua" <kuuse@redantigua.com> Cc: <current@freebsd.org> Sent: Friday, January 21, 2005 10:22 AM Subject: Re: Problem with crt1.o and init tls Johan Kuuse - Red Antigua said: > Hi, > > I'm trying to upgrade from 5.2.1 to 6.0 current. > > # make buildworld > # make buildkernel > # make installkernel > # reboot > > all went fine. > > uname -a now shows > FreeBSD 6.0-CURRENT ... > > With > # mergemaster -p > # make installworld > the problems started. What problems? At this point, removing your object files might have been a bad idea. Your kernel and world are out of sync and trying to build a new world with an out of sync userland might be asking for disaster. -- Ryan Sommers ryans@gamersimpact.com _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00ba01c4ffd9$fd5e7a70$10bca1cd>