Don Jackson wrote: > Matt and Paul, > > Thank you for the information about boot.conf, using that will enable > me to keep the uniprocessor and multiprocessor versions of the kernel > distinct. > > I think I was led astray initially by this comment in Section 8.12 in the FAQ: > > A separate SMP kernel, "bsd.mp", is provided with the install file sets, > which can be selected at install time. > It is suggested that you test booting this kernel before renaming > it to "bsd" to make it your default kernel. > > See: http://www.openbsd.org/faq/faq8.html#SMP > > Perhaps the FAQ should be modified to tell people to change boot.conf > instead of renaming the kernel files, to prevent others from > overloading /bsd and the default kernel.
no way. The only thing that lead you astray is you and some questionable advice. Please stop trying to redesign things you just don't understand how to use properly. You are trying to fix something that isn't a problem. The boot.conf file is a good way to really mess with your own head. When you build a kernel, you end up with "bsd" as the file name. That's true if you build a GENERIC kernel, a GENERIC.MP, a DISKLESS, whatever. It all creates "bsd". So, you are developer or experimenting (or you are building -stable), you build your kernel as desired, you "make install", and reboot. And things don't work as desired. So you test some more, you reboot, and things still don't work as desired. After a few hours of this, you remember that you altered boot.conf to load "bsd.mp", and you have been building and installing "bsd", which is sitting there completely ignored. If you are lucky. If you were not so lucky, you just patched and installed a new kernel to fix some horrible bug...that is still going to bite you because you thought it was really cool to turn the boot.conf knobs. Sometimes the way to "avoid" one error opens the door to three or four others. Nick.
