Quoting Bernd Schoeller <[EMAIL PROTECTED]>:

> On Fri, Aug 05, 2005 at 01:24:41PM +0200, Artur Grabowski wrote:
> > Nick Holland <[EMAIL PROTECTED]> writes:
> >
> > > Roger Neth Jr wrote:
> > > ...
> > > > Did this newbie (me) do this wrong?
> > > >
> > > > cd /
> > > > cp bsd bsd.old
> > > > cp bsd.mp bsd
> > > > #reboot
> > >
> > > PERSONALLY, 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 OpenBSD 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 [EMAIL PROTECTED]
----------------------------------------------------------------

Reply via email to