>From: Lars Hansson <lars (AT) unet (DOT) net.ph>
>To: misc (AT) openbsd (DOT) org
>Subject: Re: Requesting an change in the installer
>Date: Fri, 5 Aug 2005 10:19:41 +0800
>
Thu, 04 Aug 2005 20:06:55 -0600
>Theo de Raadt <deraadt (AT) cvs (DOT) openbsd.orgwrote:
>
you could just set the kernel image to bsd.mp.
man boot.conf.
No. That is not the same. Bad advice.
>
>My bad then. You learn sometihng new every day.
>
>
>Lars Hansson
>
Did this newbie (me) do this wrong?
cd /
cp bsd bsd.old
cp bsd.mp bsd
#reboot
rogern
the road to retirement? Check out MSN Life Events for advice on how to
get there!

Roger Neth Jr wrote:

Did this newbie (me) do this wrong?

cd /
cp bsd bsd.old
cp bsd.mp bsd
#reboot

PERSNALLY, I prefer to call the single processor kernel "bsd.sp",
rather than "bsd.old". "bsd.old" is most commonly the "previous kernel
before I tried to build my own and hosed the heck out of everything". :)
But yes, other than the one small detail, this is my prefered way.
Altering boot.conf is dangerous. Art's story isn't the only one I've
heard along those lines from developers.

If I'm working on an SMP machine, I'll do it before first boot by
adjusting things in /mnt after install. I often also chroot to /mnt,
and do some other "before first boot" housekeeping, such as adding
"softdep" to all mount points in /etc/fstab.

Nick.

Nick Holland <nick (AT) holland-consulting (DOT) netwrites:

Roger Neth Jr wrote:

Did this newbie (me) do this wrong?

cd /
cp bsd bsd.old
cp bsd.mp bsd
#reboot

PERSNALLY, I prefer to call the single processor kernel "bsd.sp",
rather than "bsd.old". "bsd.old" is most commonly the "previous kernel
before I tried to build my own and hosed the heck out of everything". :)
But yes, other than the one small detail, this is my prefered way.
Altering boot.conf is dangerous. Art's story isn't the only one I've
heard along those lines from developers.

The best one I've heard was about a "unix" consultant that was trained
on RedHat. He was hired to do some job at a customer on a real system
and as part of that job he decided to clean up /etc. Since rm is alias
to "rm -i" on RedHat, he typed "rm /etc/*"

//art

Fri, Aug 05, 2005 at 01:24:41PM +0200, Artur Grabowski wrote:
Nick Holland <nick (AT) holland-consulting (DOT) netwrites:

Roger Neth Jr wrote:

Did this newbie (me) do this wrong?

cd /
cp bsd bsd.old
cp bsd.mp bsd
#reboot

PERSNALLY, I prefer to call the single processor kernel "bsd.sp",
rather than "bsd.old". "bsd.old" is most commonly the "previous kernel
before I tried to build my own and hosed the heck out of everything". :)
But yes, other than the one small detail, this is my prefered way.
Altering boot.conf is dangerous. Art's story isn't the only one I've
heard along those lines from developers.

[a story about some Linux admin deleting /etc/*]

Everybody knows that there are tons of ways to shoot yourself into the
foot. But at least BSD should not help you in doing it.

More and more machines require the bsd.mp kernel, and I think there
should be a hint of how to do the switch. This would prevent
home-brewed solutions and keep the installations consistent.

My recommendation would be:

- call the single user kernel /bsd.sp
- add a hard link from /bsd.sp to /bsd
- add a description to 'man afterboot' for changing the default
kernel by doing 'rm /bsd && ln /bsd.mp /bsd'

This would give a clean setup for switching the kernel. Also it is
clear that by booting /bsd.sp, you always boot the single processor
kernel, by booting /bsd.mp, you always boot the multi processor
kernel. By booting /bsd you boot the configured kernel.

Bernd

[demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]

Quoting Bernd Schoeller <bernd.schoeller (AT) inf (DOT) ethz.ch>:

Fri, Aug 05, 2005 at 01:24:41PM +0200, Artur Grabowski wrote:
Nick Holland <nick (AT) holland-consulting (DOT) netwrites:

Roger Neth Jr wrote:

Did this newbie (me) do this wrong?

cd /
cp bsd bsd.old
cp bsd.mp bsd
#reboot

PERSNALLY, I prefer to call the single processor kernel "bsd.sp",
rather than "bsd.old". "bsd.old" is most commonly the "previous kernel
before I tried to build my own and hosed the heck out of everything". :)
But yes, other than the one small detail, this is my prefered way.
Altering boot.conf is dangerous. Art's story isn't the only one I've
heard along those lines from developers.

[a story about some Linux admin deleting /etc/*]

Everybody knows that there are tons of ways to shoot yourself into the
foot. But at least BSD should not help you in doing it.

More and more machines require the bsd.mp kernel, and I think there
should be a hint of how to do the switch. This would prevent
home-brewed solutions and keep the installations consistent.

My recommendation would be:

- call the single user kernel /bsd.sp
- add a hard link from /bsd.sp to /bsd
- add a description to 'man afterboot' for changing the default
kernel by doing 'rm /bsd && ln /bsd.mp /bsd'

This would give a clean setup for switching the kernel. Also it is
clear that by booting /bsd.sp, you always boot the single processor
kernel, by booting /bsd.mp, you always boot the multi processor
kernel. By booting /bsd you boot the configured kernel.

Bernd

[demime 1.01d removed an attachment of type application/pgp-signature which
had a name of signature.asc]
--

I disagree the hardlink, since it would change bsd.* after using 'config'.

Kind regards,
Jimmy Scott

This message has been sent through ihosting.be
To report spamming or other unaccepted behavior
by a iHosting customer, please send a message
to abuse (AT) ihosting (DOT) be

Fri, Aug 05, 2005 at 03:00:25PM +0200, jimmy (AT) inet-solutions (DOT) be wrote:
[]
Quoting Bernd Schoeller <bernd.schoeller (AT) inf (DOT) ethz.ch>:
- call the single user kernel /bsd.sp
- add a hard link from /bsd.sp to /bsd
- add a description to 'man afterboot' for changing the default
kernel by doing 'rm /bsd && ln /bsd.mp /bsd'
[]

I disagree the hardlink, since it would change bsd.* after using 'config'.

Different opinions here: I my view 'config -ef /bsd' should change the
configuration of the current kernel, which is /bsd.sp on a single
processor machine and /bsd.mp on a multi processor machine. Switch
back and forth between the two kernels should not delete your
configuration for the kernel.

Bernd