As Peter Jeremy wrote ...
> On 1999-Oct-28 07:36:53 +1000, David O'Brien wrote:
> >IF you are going to run -CURRENT, you need to read this list.
>
> And read /usr/src/UPDATING which also warns about this
>
> >(/me wonders how many MORE times we are going to have to say this because
> >of the signal changes...)
>
> A very large number I suspect.
>
> IMHO, the correct solution is to for the entire make world process to
> be re-worked. I believe the process should always be to boot a new
> kernel first (as bde(?) commented - it's much easier to recover from a
> broken kernel than a broken world), and then install a new world.
> Getting there from here is non-trivial - the major problem being that
> our build process does not adequately differentiate between compiling
> code that must run now and code that must run with the new kernel.
Marcel (the one that hacked on signals ;-) is giving this very subject
intensive thought. But it is definitely a lot of work.
--
| / o / / _ Arnhem, The Netherlands - Powered by FreeBSD -
|/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
