Re: kernel naming proposal

2008-02-27 Thread Piotrek Kapczuk
2008/2/25, Don Jackson [EMAIL PROTECTED]: The issue is that when building and installing new kernels (eg, when a new security patch is released), it is not totally obvious to the (automated) build script what the file /bsd really is, is it the uniprocessor kernel, or a link to the

Re: kernel naming proposal

2008-02-27 Thread mickey
On Wed, Feb 27, 2008 at 01:15:56PM +0100, Piotrek Kapczuk wrote: 2008/2/25, Don Jackson [EMAIL PROTECTED]: The issue is that when building and installing new kernels (eg, when a new security patch is released), it is not totally obvious to the (automated) build script what the file /bsd

kernel naming proposal

2008-02-25 Thread Don Jackson
OpenBSD kernel support on some architectures (I'm familiar with i386 and amd64) includes both a uniprocessor and multiprocessor version of the kernel. Currently the uniprocessor kernel is named bsd and the multiprocessor kernel is named bsd.mp It seems to me that /bsd is currently overloaded to

Re: kernel naming proposal

2008-02-25 Thread Jay Hart
While I have no stake in this issue, I think as a user /bsd and /bsd.mp are fine. As a new user, I have to determine what the diff is between /bsd and /bsd.mp now, and if it was changed to /bsd.up and /bsd.mp, I'd still have to determine which was which. Am I missing something? Jay OpenBSD

Re: kernel naming proposal

2008-02-25 Thread Don Jackson
The issue is that when building and installing new kernels (eg, when a new security patch is released), it is not totally obvious to the (automated) build script what the file /bsd really is, is it the uniprocessor kernel, or a link to the multiprocessor kernel? If the latter, than blindly copying

Re: kernel naming proposal

2008-02-25 Thread Matthew Dempsky
On 2/25/08, Don Jackson [EMAIL PROTECTED] wrote: Users who wanted to run the mp kernel could arrange to change this link in their install process (eg their install.site script) Or you can just run echo set image bsd.mp /etc/boot.conf after installation.

Re: kernel naming proposal

2008-02-25 Thread Tasmanian Devil
I propose that by default, the uniprocessor version of the kernel be named bsd.up, and that the install process arrange to have /bsd link to /bsd.up by default. Users who wanted to run the mp kernel could arrange to change this link in their install process (eg their install.site

Re: kernel naming proposal

2008-02-25 Thread Paul de Weerd
On Mon, Feb 25, 2008 at 11:06:18AM -0800, Don Jackson wrote: | The issue is that when building and installing new kernels (eg, when a | new security patch is released), it is not totally obvious to the | (automated) build script what the file /bsd really is, is it the | uniprocessor kernel, or a

Re: kernel naming proposal

2008-02-25 Thread Don Jackson
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

Re: kernel naming proposal

2008-02-25 Thread Matthew Dempsky
On 2/25/08, Tasmanian Devil [EMAIL PROTECTED] wrote: /bsd (the kernal in use, whichever it is) is a copy of one of them then, easy to identify by its file size. For me that's easier than with a link. Examining output of uname -v is probably even easier. :-)

Re: kernel naming proposal

2008-02-25 Thread Stuart Henderson
On 2008-02-25, Paul de Weerd [EMAIL PROTECTED] wrote: bsd is UP, bsd.mp is MP. ..unless you did cd /sys/arch/$ARCH/compile/GENERIC.MP make install.

Re: kernel naming proposal

2008-02-25 Thread Tasmanian Devil
bsd is UP, bsd.mp is MP. If you want to boot MP, boot bsd.mp. That seems to be even easier than my additional kernel file (my other posts in this thread). I'll try that with the next upgrade. Tas.

Re: kernel naming proposal

2008-02-25 Thread Tasmanian Devil
/bsd (the kernal in use, whichever it is) is a copy of one of them then, easy to identify by its file size. For me that's easier than with a link. Examining output of uname -v is probably even easier. :-) If I check which kernel my /bsd file is (during update/upgrade), then that's

Re: kernel naming proposal

2008-02-25 Thread Nick Holland
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

Re: kernel naming proposal

2008-02-25 Thread Tony Abernethy
Nick Holland wrote: Sometimes the way to avoid one error opens the door to three or four others. That's why I lurk on this list. Good advice regardless of context. Thanks.

Re: kernel naming proposal

2008-02-25 Thread Michael
Hi, Tasmanian Devil schrieb: Don't want to say your proposal is good or bad, but I use another way to make life easy for me on multiprocessor machines. I keep a copy of all three kernels in / with the uniprocessor kernel renamed to bsd.sp (for single processor, might not be the perfect name,