Marcel Moolenaar wrote:
>
> > But this still doesn't entirely solve the problem. You still have
> > to build and install a new kernel before installing the world.
> > While this is typically what most -current folks do anyways, it
> > still prevents backing up to a previous kernel after the install
> > world.
>
> You can easily install a kernel as part of the upgrade process. A
> complete upgrade would be something like:
>
> 1. Verify and/or install cross-compilation tools
> 2. Build world
> 3. Build kernel
> 4. Copy tools that are used by the install process
> 5. install kernel
> 6. install world
> 7. reboot
>
> If you install a kernel before installing world, you can easily recover
> when the install world fails: reboot. The new kernel is capable of
> running those binaries that got installed before the breakage.
You missed the point. This is -current, right? You do all of the
above, and then reboot and find out that the new kernel doesn't
work. What do you do? The default procedure is to boot kernel.old.
> > This is why I kind of like (was it?) Peter Wemms libc hack.
>
> It's a solution that may work out very well, yes. But it seems to me
> that cross-compilation is on everybodies wishlist for as long as FreeBSD
> exists (well almost :-) That's why I'm pressing it. This doesn't rule
> out interim solutions of course. Real cross-compilation may not be worth
> the effort/problems, but you can't really tell if you haven't tried
> it...
>From where I stand, it doesn't seem that cross-compilation will
solve the problem of world needing to be built before kernel (and
that includes installworld).
--
Daniel C. Sobral (8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Rule 69: Do unto other's code as you'd have it done unto yours
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
