FreeBSD a écrit :
FreeBSD a écrit :
matt donovan a écrit :
On Sun, Oct 5, 2008 at 12:58 PM, FreeBSD <[EMAIL PROTECTED]> wrote:

There is my situation:
I want to be able to use freebsd-update to update a FreeBSD 7.0-Release
installation to the latest security patches (I want an update and not an upgrade if I understand correctly). Where this gets more complicated is that
I need a custom kernel (for ULE, pf and ALTQ while also disabling some
devices I'll never need) and I want to use jails to isolate every services
(Apache and MySQL by now).

So, I read at some places that you can't use freebsd-update with a custom
kernel, but I'm not sure if this apply only in the case of an upgrade
between release or if I'll need to manually recompile the kernel with every
use of freebsd-update.

I also read that it's possible to update the jails from the host system
with the -b flag. In this case, I supposed that I need to update the host system before the jail, but is the procedure going to be exactly the same?

yes all you need to do is freebsd-update fetch install your kernel won't be
updated but your userland will

So it is right to say that the custom kernel "problem" applies only when upgrading to a newer release?

All I have to do is 'freebsd-update fetch install' to update the base system then 'freebsd-update -b /usr/jail/jail_name fetch install' to update the jails?

I hope so because it would be very impressing :)

Another question just came to my head: May I update the src before compiling my custom kernel or should I keep the original src that shipped with the release to be able to use freebsd-update?

Thank you very much for your help!


I just tried it (freebsd-update fetch install) and after a reboot uname -a still shows FreeBSD 7.0-RELEASE #0 while freebsd-update told me I was going to update to 7.0-RELEASE-p5. But, I noticed that the files that needed to be updated were updated.

I'm a little confused...can someone explain this behaviour to me?



_______________________________________________ mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to