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 fil
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 mult
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 nam
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.
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
> > /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), th
> 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.
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".
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. :-)
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 wi
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 li
> 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 sc
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.
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
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 ke
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 m
16 matches
Mail list logo