Date: Sat, 23 Nov 2002 10:39:49 -0600 From: "Jack L. Stone" <jackstone@sage-one.net> To: Jez Hancock <jez.hancock@munk.nu>, FreeBSD questions List <freebsd-questions@FreeBSD.ORG> Subject: Re: Booting an alternate kernel Message-ID: <3.0.5.32.20021123103949.010ff368@mail.sage-one.net> In-Reply-To: <20021123160921.GA54194@users.munk.nu> References: <3.0.5.32.20021123093535.010ff368@mail.sage-one.net> <20021123150522.GA53763@users.munk.nu> <3.0.5.32.20021123093535.010ff368@mail.sage-one.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 04:09 PM 11.23.2002 +0000, Jez Hancock wrote: >On Sat, Nov 23, 2002 at 09:35:35AM -0600, Jack L. Stone wrote: >> At 03:05 PM 11.23.2002 +0000, Jez Hancock wrote: >> >Hi, >> > >> >I have fbsd 4.7 installed on a hdd in a dev machine which I want to transfer >> >to and from another machine. However the current machine is a K6-2 CPU >> and the target >> >machine is an AMD Athlon 1900+ - a generic kernel will not work >> >when I transfer the hdd between machines. >> > >> >I've just built a new kernel that will work in the Athlon and the kernel >> >that works ok in the K6 machine is now called /kernel.old. >> > >> >How can I make sure I don't accidentally overwrite /kernel.old (ie when >> >I rebuild the kernel again)? Ideally I'd like to rename kernel.old to >> >something like kernel.k6, but would I have to rename the /modules.old >> >dir too? >> > >> >Thanks in advance, >> > >> >Jez >> > >> >> You can just copy the kernel to kernel.k6. You don't need to delete the >> kernel.old..... >Cheers Jack. > >The main thing I was unsure of was what files a kernel rebuild puts in >/modules - ie if I had to rename /modules.old as well as just /kernel.old >- but I've had a chance to check it out now and it seems the size of >/modules and /modules.old is identical (as long as the release point >is the same of course). > >All ticking over verrrrrrrry fast - this athlon 1900+ is a far cry >from the p166 ! > >On to building X on freebsd for first time - joy ;) > >Thanks again, >Jez > As further example, I have occasions to copy desired kernels over to other machines. No problem because I try to keep most of the machines configured the same. One big difference would be a single CPU vs dual. Don't forget to keep track of your kernel config files. They should be symlinked to a directory separate from the "/usr/src/sys/i386/conf" just in case you suddenly decide to delete your /usr/src and forget the kernel.conf is in there. But, the main thing, I believe is to keep your kernel in sync with your userland build. Modules may or may not change, especially if you are only updating a release... although keeping a copy never hurts. Have fun.... Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net jackstone@sage-one.net 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?3.0.5.32.20021123103949.010ff368>