Compiling a New Kernel

2002-10-11 Thread Jamie Heckford

Being one of these difficult people who like sticking to the old way of doing things, 
im still compiling my kernel the old way
(config KERNELNAME; cd ../../KERNELNAME; make depend; make ; make install) :P

I picked up a rumour on the mailing lists that this may no longer work in 
future/recent releases?

Just curious ;)

--
Jamie Heckford
[EMAIL PROTECTED]
http://www.jamiesdomain.org.uk/

FreeBSD: The Power to Serve


-- 

Message scanned for viruses and dangerous content by
http://www.newnet.co.uk/av/ and believed to be clean


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message



Re: Compiling a New Kernel

2002-10-11 Thread Kris Kennaway

On Fri, Oct 11, 2002 at 09:44:57AM +0100, Jamie Heckford wrote:
 Being one of these difficult people who like sticking to the old way of doing 
things, im still compiling my kernel the old way
 (config KERNELNAME; cd ../../KERNELNAME; make depend; make ; make install) :P
 
 I picked up a rumour on the mailing lists that this may no longer work in 
future/recent releases?

It's fine when you're rebuilding your kernel with the same sources as
your installed world, but if you upgrade your sources and want to
build the kernel then this method WILL NOT WORK in all cases (and
there have been cases in the past when it would not work).  This is
why 'make buildkernel' and friends were introduced; they are
guaranteed [1] to work properly in all cases.  The exact steps are
documented in the handbook.

Kris

[1] Modulo /COPYRIGHT :-)



msg50365/pgp0.pgp
Description: PGP signature


Re: Compiling a New Kernel

2002-10-11 Thread Matthew Seaman

On Fri, Oct 11, 2002 at 09:44:57AM +0100, Jamie Heckford wrote:

 Being one of these difficult people who like sticking to the old way
 of doing things, im still compiling my kernel the old way (config
 KERNELNAME; cd ../../KERNELNAME; make depend; make ; make install)
 :P

 I picked up a rumour on the mailing lists that this may no longer
 work in future/recent releases?

Nowadays, the old way is only guarranteed to work if you've
previously built and installed world, kernel with that same set of
sources.  The new way, 'make buildkernel' doesn't have that
restriction, as it uses the compiler toolchain and so forth freshly
created in the build area.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
  Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message



Re: Compiling a New Kernel

2002-10-11 Thread Kris Kennaway
On Fri, Oct 11, 2002 at 08:24:33AM -0700, Kevin Oberman wrote:

 When you build a new world (make buildworld), none of the new tools
 that have been built are installed. So any kernel built with this
 system will attempt to use the existing tools.
 
 If something critical to building the kernel, say the .mk files or
 compiler, have been updated and the kernel Makefile has been modified
 to work with the new .mk files, any attempt to build the kernel with
 existing, installed tools is doomed to failure.

This is exactly correct.  Examples in the past have included
binutils/compiler upgrades and *.mk changes.

Kris



msg50727/pgp0.pgp
Description: PGP signature


Re: Compiling a New Kernel

2002-10-11 Thread Aragon Gouveia
| By Jamie Heckford [EMAIL PROTECTED]
|  [ 2002-10-11 11:13 +0200 ]
 Bizarre how could it be different/not work if you have cvsup'd all of your 
sources including sys/ tree at exactly the same time,
 and compile your kernel just after the installworld?

Ideally you should build, install, and boot your new kernel before
installing your new world. If your new kernel fails to boot for whatever
reason, you can easily boot the old kernel and have a fully functional
system again. If you installworld before verifying your new kernel, you
could run into worse problems if your new kernel doesn't load and you
have to boot the old kernel with your new world.


Regards,
Aragon


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message



Re: Compiling a New Kernel

2002-10-11 Thread Phil Kernick
Aragon Gouveia wrote:

Ideally you should build, install, and boot your new kernel before
installing your new world. If your new kernel fails to boot for whatever
reason, you can easily boot the old kernel and have a fully functional
system again. If you installworld before verifying your new kernel, you
could run into worse problems if your new kernel doesn't load and you
have to boot the old kernel with your new world.


The only problem that I have with this approach, is that I keep all of my 
source on a vinum raid-5 volume.  If I reboot before doing a make 
installworld, then there is always the possibility that with the new kernel 
and the old world I may not be able to mount the volume.  So I always shutdown 
but *not* reboot before doing the installworld.


Phil.


--
   _-_|\   Phil Kernick  E-Mail: [EMAIL PROTECTED]
  / \  ROTFL Enterprises Mobile:  041 61 ROTFL
  \_.-*_/
   v   Humourist, satirist, and probably a few more 'ists to boot!


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message


Re: Compiling a New Kernel

2002-10-11 Thread ian j hart
Phil Kernick wrote:
 
 Aragon Gouveia wrote:
  Ideally you should build, install, and boot your new kernel before
  installing your new world. If your new kernel fails to boot for whatever
  reason, you can easily boot the old kernel and have a fully functional
  system again. If you installworld before verifying your new kernel, you
  could run into worse problems if your new kernel doesn't load and you
  have to boot the old kernel with your new world.
 
 The only problem that I have with this approach, is that I keep all of my
 source on a vinum raid-5 volume.  If I reboot before doing a make
 installworld, then there is always the possibility that with the new kernel
 and the old world I may not be able to mount the volume.  So I always shutdown
 but *not* reboot before doing the installworld.
 
 Phil.
 
 --
 _-_|\   Phil Kernick  E-Mail: [EMAIL PROTECTED]
/ \  ROTFL Enterprises Mobile:  041 61 ROTFL
\_.-*_/
 v   Humourist, satirist, and probably a few more 'ists to boot!
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-stable in the body of the message

It's early in the morning here :), but if the mount fails, you reboot
and load kernel.old. At which point you should be able to mount your
source.

-- 
ian j hart

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message



Re: Compiling a New Kernel

2002-10-11 Thread Greg 'groggy' Lehey
On Saturday, 12 October 2002 at 10:32:09 +0930, Phil Kernick wrote:
 Aragon Gouveia wrote:
 Ideally you should build, install, and boot your new kernel before
 installing your new world. If your new kernel fails to boot for whatever
 reason, you can easily boot the old kernel and have a fully functional
 system again. If you installworld before verifying your new kernel, you
 could run into worse problems if your new kernel doesn't load and you
 have to boot the old kernel with your new world.

 The only problem that I have with this approach, is that I keep all of my
 source on a vinum raid-5 volume.  If I reboot before doing a make
 installworld, then there is always the possibility that with the new kernel
 and the old world I may not be able to mount the volume.  So I always
 shutdown but *not* reboot before doing the installworld.

I don't anticipate any problems with Vinum after an upgrade.  The
on-disk format has never changed, and though it's possible in the
future, I'd hope it would do so in a compatible manner.

Greg
--
See complete headers for address and phone numbers

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message