Date: Fri, 15 Sep 2000 12:55:41 -0700 From: Kent Stewart <kstewart@urx.com> To: Mark Ovens <marko@freebsd.org> Cc: "Tomlinson, Drew" <Drew.Tomlinson@lc.ca.gov>, "'FreeBSD Questions (E-mail)'" <freebsd-questions@freebsd.org> Subject: Re: Part #1 - Newbie Help Determining Lost Root After Upgrade Fro m 4.0 to 4.1 Message-ID: <39C27EBD.D06FA2FC@urx.com> References: <8C224DC088D8D111B67D0000F67AC17E029C4C66@ldcmsx01.lc.ca.gov> <39C264D6.E7D745D0@urx.com> <20000915195219.E258@parish>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Ovens wrote: > > On Fri, Sep 15, 2000 at 11:05:10AM -0700, Kent Stewart wrote: > > > > > > > "Tomlinson, Drew" wrote: > > > > > > Thank you both for your help. I am compiling a new kernel right > > > now. > > > > > > I'm actually in California but I use a dynamic IP (dynip.com) DNS > > > service that is located in Canada. So would this be why I had an > > > error using CVSup with the "cvs-crypto" tag? I don't remember the > > > exact error but it was something along the lines of it not being > > > available. When I commented out the "cvs-crypto" and uncommented > > > the individual collections, I didn't get the unavailable error. > > > > That message was caused by the fact they folded crypto in to src-all. > > The cryto stuff should all be commented out or moved in front of the > > ports-all tag=. section. I think commented out is the best choice > > because it is already in src-all. I don't include the ports with my > > system cvsup. I update the ports and docs manually because they are > > based on tag=. and I don't mixed different worlds :). The fact that > > you have your crypto stuff after the ports-all tag=. concerns me. I > > have doubts on this but no notion what it did for you or to you. I > > just don't do it that way because of my way of handling building my > > world. > > > > I'd suggest that if he has any problems once he has a new, working, > kernel to re-cvsup (with a fixed supfile) and re-make the world > (following the instructions in /src/UPDATING). I thought that a re-cvsup after he gets things running smoothly would be a default. I would keep a log of the updates, cvsup [options] >& cvsup.log, and look at the logs. If anything crypto looking is updated, I think I would rebuild the world and kernel. > > > > > > > So what problems am I likely to encounter once I get a good kernel? > > > Also, you are correct, mergemaster didn't actually update anything > > > as the default is to leave it for later. I've read the man page but > > > don't understand why/when I want to keep, replace, or merge. I am > > > completely new to Unix and am having a difficult time grasping > > > concepts. > > > > I am very carefull to always use a KERNEL=SOMETHING on my buildkernel. > > The previous commands stick around in roots history file. I rarely > > modify my kernel config file and so I always do the > > build[install]kernel method in /usr/src/UPDATING. I find I can get > > away without doing the intermediate singe user mode boot but you > > shouldn't try it right now. > > > > With mergemaster I follow the rule that anything I haven't modified I > > use the new file (the "i" option). That is what the system is > > expecting to use. > > I'd expand that to say use "i" for *anything* in /etc/defaults (I > think that's what you meant, but it may not be obvious to a newcomer) > as (for Drew's info) you should *never* change anything in > /etc/defaults but create a file of the same name in /etc and copy the > relevant lines to the new file and edit them there. I hadn't thought about ../defaults as a special case because there are so many new rc.files being added to /etc/*. As a matter of practice, I don't modify anything in ../defaults and I always use the mergemaster "i" option for the ../defaults/files. > > > You will have to update what seems like 100 files. > > It will try to change your host* files. I look at those and do it > > manually (the <cr> option). I have modified my dot.* files and I don't > > let it change them back. It will try to change /root/.* files and I > > don't let it do that either. My root aliases kept disappearing until > > the light went on. > > > > Sendmail is going to thrash around until you build a new aliases.db > > using the "newaliases" command. That is discussed in the first screen > > of text on /usr/src/UPDATING. > > > > I can't think of anything else at this point. I have a buildworld > > running now and something may come up in ~30 minutes or so. It is > > running on a P-II 400 and uses a little over a wall clock hour to > > complete. Actually it was longer - 1:23 [it is only a 400] and the buildworld only had the usual improper pointer or structure intialization messages that I haven't tracked down yet. > > > > Bah humbug, it's alright for some ;) I look at it as a tool. There are actually two of them and one is always available to test a build. One of them can be cvsup'ed and rebuilt when ever a number of people appear to be having problems. My system will either have similar problems or not. If I could do a build and install in less than an hour, I would be even more likely to test the cvs changes I see in cvs-all for RELENG_4. Since it takes two hours, I wait for someone to have problems before I try updating one of them. Both of the systems seem to run pretty clean and when a recent build and install has problems, I get concerned. Kent > > > Kent > > > > > > > > > > Thank you both again for your time. I really appreciate it. > > > > > > Drew > > > > > > -----Original Message----- > > > From: Mark Ovens [mailto:marko@freebsd.org] > > > Sent: Friday, September 15, 2000 9:42 AM > > > To: Kent Stewart > > > Cc: Tomlinson, Drew; 'FreeBSD Questions (E-mail)' > > > Subject: Re: Part #1 - Newbie Help Determining Lost Root After > > > Upgrade > > > From 4. 0 to 4.1 > > > > > > On Fri, Sep 15, 2000 at 09:33:30AM -0700, Kent Stewart wrote: > > > > > > > > > > > > Mark Ovens wrote: > > > > > > > > > > On Fri, Sep 15, 2000 at 09:13:36AM -0700, Kent Stewart wrote: > > > > > > > > > > > > > > > > > > Mark Ovens wrote: > > > > > > > > > > > > > > Hmm, the file you really should consult here is > > > /usr/src/UPDATING. You > > > > > > > got the sequence slightly wrong (the handbook doesn't always > > > get > > > > > > > updated immediately, UPDATING does). From /usr/src/UPDATING: > > > > > > > > > > > > > > > > > To update from 4.0-RELEASE or later to the most > > > current > > > > > > > 4.x-STABLE > > > > > > > ---------- > > > > > > > make buildworld > > > > > > > make buildkernel KERNEL=YOUR_KERNEL_HERE > > > > > > > make installkernel KERNEL=YOUR_KERNEL_HERE > > > > > > > reboot (in single user) [1] > > > > > > > make installworld > > > > > > > mergemaster > > > > > > > reboot > > > > > > > > > > > > > > > When I reboot, the system is unable to mount the root > > > > > > > > device. I am able to unload the new kernel, load the old > > > one > > > > > > > > and boot without error. > > > > > > > > > > > > > > Good, at least you can boot the system.... > > > > > > > > > > > > > > > I'm sure I've done something wrong and would like to know > > > > > > > > what it is. I could take the easy way out and just install > > > > > > > > > > > 4.1 from scratch but I wouldn't learn anything that way. > > > > > > > > > > > > > > > > > > > > > > Looking at the boot messages it is finding ata0 and ata1, > > > the IDE > > > > > > > controllers, but it isn't even probing for the disks. In the > > > config > > > > > > > file for your custom kernel you have commented out important > > > IDE > > > > > > > devices: > > > > > > > > > > > > > > # ATA and ATAPI devices > > > > > > > device ata0 at isa? port IO_WD1 irq 14 > > > > > > > device ata1 at isa? port IO_WD2 irq 15 > > > > > > > #device ata > > > > > > > #device atadisk # ATA disk drives > > > > > > > #device atapicd # ATAPI CDROM drives > > > > > > > > > > #device atapifd # ATAPI floppy > > > drives > > > > > > > #device atapist # ATAPI tape drives > > > > > > > #options ATA_STATIC_ID #Static device > > > numbering > > > > > > > #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI > > > devices > > > > > > > > > > > > > > uncomment ata, atadisk, atapicd (if you have a CD-ROM), and > > > atapifd > > > > > > > and re-build your custom kernel. If that fails, build a > > > GENERIC kernel > > > > > > > and see if that boots. > > > > > > > > > > > > In his cvsup file he has ports-all tag=. and then lines later > > > he has > > > > > > the crypto souces. Did he get RELENG_4 crypto's or did he get > > > > > > -current? > > > > > > > > > > > > > > > > I spotted that, but since -crypto doesn't exist as a separate > > > > > collection anymore I would expect an error message from cvsup to > > > that > > > > > effect, which is what I saw when -crypto became part of src-all > > > > > (judging by his domain he's in Canada so the USA-specific crypto > > > > > > > > issues wouldn't apply) > > > > > > > > > > > Also, isn't the default on mergemaster todo nothing, which > > > didn't > > > > > > upgrade any of his /etc files. > > > > > > > > > > > > > > > > Yes, but that wouldn't prevent the kernel finding the root > > > partition. > > > > > > > > You got that part covered. I was thinking of the next set of > > > problems > > > > that he is going to have after he remakes a good kernel. > > > > > > > > > > Ah right. Well, as long as he hasn't nuked /usr/obj he can just boot > > > > > > single-user and re-run mergemaster (with our guidance :)). > > > > > > BTW, looking back at the original post I notice: > > > > > > # The easiest way to get the export-restricted code is to use the > > > # "cvs-crypto" mega-collection. > > > #cvs-crypto -- This is commented as I got errors when trying to > > > fetch > > > # > > > # These are the individual collections that make up "cvs-crypto". > > > If > > > # you use these, be sure to comment out "cvs-crypto" above. -- I > > > didn't get > > > errors. > > > src-crypto > > > src-secure > > > src-sys-crypto > > > > > > So he did get the error about cvs-crypto, as I expected, but I > > > missed > > > src* lines after. I guess that this would get -current crypto stuff, > > > > > > but is all of the crypto stuff MFC'd so it wouldn't make any > > > difference? > > > > > > > KEnt > > > > > > > > > > > > > > > Kent > > > > > > > > > > > > > > > > > > > > WARNING: Make a copy of your working kernel (e.g. > > > /kernel.ok). I > > > > > > > suspect it is currently called kernel.old, if so it will get > > > > > > > > > > overwritten (with the broken /kernel) when the next kernel > > > you build > > > > > > > is installed. > > > > > > > > > > > > > > > Thank you in advance for your help. > > > > > > > > > > > > > > You're welcome. > > > > > > > > > > > > > > > I really want to learn this operating system! > > > > > > > > > > > > > > > > > > > > > > Good for you :) > > > > > > > > > > > > > > > Drew > > > > > > > > > > > > > > > [snip] > > > > > > > > > > > > > > -- > > > > > > > 4.4 - The number of the Beastie > > > > > > > > > > ________________________________________________________________ > > > > > > > 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org > > > > > > > > > > 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark > > > > > > > mailto:marko@freebsd.org http://www.radan.com > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > > > with "unsubscribe freebsd-questions" in the body of the > > > message > > > > > > > > > > > > -- > > > > > > Kent Stewart > > > > > > Richland, WA > > > > > > > > > > > > mailto:kbstew99@hotmail.com > > > > > > http://kstewart.urx.com/kstewart/index.html > > > > > > FreeBSD News http://daily.daemonnews.org/ > > > > > > > > > > -- > > > > > 4.4 - The number of the Beastie > > > > > ________________________________________________________________ > > > > > > > > 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org > > > > > 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark > > > > > mailto:marko@freebsd.org http://www.radan.com > > > > > > > > -- > > > > Kent Stewart > > > > Richland, WA > > > > > > > > mailto:kbstew99@hotmail.com > > > > http://kstewart.urx.com/kstewart/index.html > > > > FreeBSD News http://daily.daemonnews.org/ > > > > > > -- > > > 4.4 - The number of the Beastie > > > ________________________________________________________________ > > > 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org > > > 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark > > > mailto:marko@freebsd.org http://www.radan.com > > > > -- > > Kent Stewart > > Richland, WA > > > > mailto:kbstew99@hotmail.com > > http://kstewart.urx.com/kstewart/index.html > > FreeBSD News http://daily.daemonnews.org/ > > -- > 4.4 - The number of the Beastie > ________________________________________________________________ > 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org > 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark > mailto:marko@freebsd.org http://www.radan.com -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39C27EBD.D06FA2FC>