Date: Thu, 05 Apr 2007 09:51:53 +0100 From: Tom Evans <tevans.uk@googlemail.com> To: kayve@sfsu.edu Cc: stable@freebsd.org Subject: Re: single user mode buildwerld failures Message-ID: <1175763113.1318.18.camel@zoot.mintel.co.uk> In-Reply-To: <1175736045.46144eed676c2@webmail.sfsu.edu> References: <20070403020736.8549C241BF@freebsd-stable.sentex.ca> <Pine.SOC.4.64.0704040855350.15464@libra.sfsu.edu> <20070404125452.M18358@fledge.watson.org> <Pine.SOC.4.64.0704040959490.15464@libra.sfsu.edu> <Pine.SOC.4.64.0704041006060.15464@libra.sfsu.edu> <14989d6e0704041034t1e197592jbd7d609ddd1d0765@mail.gmail.com> <1175734991.46144acfabc7a@webmail.sfsu.edu> <1175736045.46144eed676c2@webmail.sfsu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-ekHafhZpEc/Sil2jDnYR Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2007-04-04 at 18:20 -0700, kayve@sfsu.edu wrote: > Quoting kayve@sfsu.edu: >=20 > > Quoting Christian Walther <cptsalek@gmail.com>: > >=20 > > > On 04/04/07, KAYVEN RIESE <kayve@sfsu.edu> wrote: > > > > there were so many steps they didn't seem obvious.. i got halfway t= hru > > and > > > > realized i > > > > was in some prompt for mergemaster -p, or so i thought, so i starte= d > > over. > > > > i had no > > > > idea what was happening. i can't log on now. > > > > /etc/passwd is gone. i used a freeBSD disk that is certainly old t= o go > > to > > > > a fixit shell but i didn't > > > > know what to do. i can go back to the fixit shell if somebody tell= s me > > > > what to do but i have > > > > to *#@&ing walk over to kinkos now to get on the internet. > > >=20 > > > So firstly you should probably sit down and take a deep breath. > > >=20 > > > Secondly, it appears that you messed up your system pretty badly, I'm > > > not sure that it can be fixed. On the other hand, it just might be > > > that you missed a few steps. > > >=20 > > > For example, when you're in single user mode the root filesystem is > > > mounted read only, which means that you can't write to it. Anything > > > related to the upgrade process (installworld, mergemaster...) has to > > > fail. > >=20 > > i looked at the /usr/src/UPDATING and what to do after the command > > mergemaster -p was not described. is there a better web page for=20 > > that somewhere? i was also taking advice from an "expert" on=20 > > experts-exchange both sources did not described the bizzare behavior > > i observed after simply invoking the command "mergemaster -p" both > > sources informed me to do that command followed by another command. > > i saw no advice telling me more details than that. if such a site > > exists, could i please have a direct relevant link? > >=20 > >=20 > > >=20 > > > Question is (sorry this isn't ment to sound harsch) if you read the > > > manual carefully, because it describes the entire process pretty > > > detailed. That is to say you have to read all the chapters, not only > > > the beginning. > > > For example it appears that you didn't remount the root filesystem > > > read/writeable after you booted to single user mode. > >=20 > > i followed some instructions but nothing perpared me for the way > > my acted after the command "mergemaster -p" i did not get back > > the same prompt from which i invoked "mergemaster -p" from. it > > asked me a question that i fergot what it was. that was bad.. i > > know.. i could not cut and paste there. i could have maybe > > done "mergemaster -p > file.out" but i didn't. oops. that was=20 > > stupid. > >=20 > > >=20 > > > Passwords are not stored in /etc/passwd, there is /etc/pwd.db, > > > /etc/master.passwd and /etc/spwd.db, too. All are required for the > > > system to be fully functional. The latter two contain the passwords i= n > > > encrypted form. You might want to try to restore these files in > > > particular. > >=20 > > okay.. /etc/passwd was in /var/tmp/etc/passwd, so the others will > > be similarly so? i can handle this. > >=20 > > >=20 > > > BTW: Your mailer appears to be broken. Some of your postings are > > > really difficult to read, it seems as if quoted postings aren't marke= d > > > properly, for example with a ">". > >=20 > > sorry. i use pine. ">" marks recursively who is saying what. i > > cut and pasted hurredly which i guess is stupid. it sounds like you > > are giving me good advice that i can easily follow. i will try that > > and get back to you. it might be more easy to look at the links i gave= , > > but i posted a lot of makesplat that got that guy mad at me. you can > > scroll all the way to the bottom and see what the latest is maybe you > > can follow. > >=20 > > > _______________________________________________ > > > freebsd-stable@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.= org" > > >=20 > >=20 > >=20 > >=20 >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" Your emails are ridiculously poorly formatted - I think your responses are intermingled with quoted text, and it is hard to decipher what you have done. The guy helping you from "expertsexchange" isn't helping you. He clearly has some inkling of a clue, but he doesn't know what he is doing (or maybe he knows more than me. Whatever. I know how to read a manual, and the manual says not to do it like that). To upgrade FreeBSD, use the instructions in the handbook. They are clear, concise and correct. If you have a running system, read Appendix A.5 "Using CVSup" [1] of the handbook, which details how to update your sources and ports to the current version. If you don't have a running system, rebuild world + kernel and hope that restores enough functionality so you can update the sources and go again. This is all described in section 22.4 "Rebuilding world" [2] of the handbook, but I will summarise it for you. // change to root $ su - // remove /usr/obj to speed up the build # cd /usr/obj && chflags -R noschg * && rm -rf * // Build a new world # cd /usr/src # make -j4 buildworld // build a new kernel (do not put any job options for this build) # make buildkernel // install the new kernel # make installkernel // reboot to single user mode (boot -s from the loader prompt) # shutdown -r now // After reboot // check + mount all filesystems # fsck -p # mount -u / # mount -a -t ufs # swapon -a // prepare /etc for the world install # mergemaster -p // install the new world # cd /usr/src ; make installworld // run mergemaster again # mergemaster // reboot to an updated system # shutdown -r now All these instructions are in the handbook. Cheers Tom [1] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html [2] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html --=-ekHafhZpEc/Sil2jDnYR Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) iD8DBQBGFLiplcRvFfyds/cRAo9DAJ4ha4CDdhcm1rlymm92r+wIZWa/cACeLZpg TrUgcQ6ww3S/yLJRqDLKOPs= =6n2M -----END PGP SIGNATURE----- --=-ekHafhZpEc/Sil2jDnYR--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1175763113.1318.18.camel>