I would like to know about freebsd-update command.
It is rumoured that freebsd-update command does not work well with custom
kernel.
First question is the following :
su -
#freebsd-update fetch
#freebsd-update install
Does this command work well?
The answer is .
[A].Always work, [B]Depend
It will work fine - it won't attempt to update the kernel.
On Thu, Nov 3, 2011 at 8:49 AM, masayoshi rocksta...@y7mail.com wrote:
I would like to know about freebsd-update command.
It is rumoured that freebsd-update command does not work well with custom
kernel.
First question is the
On Thu, Nov 3, 2011 at 9:13 AM, Jason Helfman jhelf...@e-e.com wrote:
I does work fine with a custom kernel, as long as you are running and
maintaining the actual update server that distributes.
I don't think that's relevant. It works fine with the public servers.
On Thu, Nov 03, 2011 at 08:49:16AM -0700, masayoshi thus spake:
I would like to know about freebsd-update command.
It is rumoured that freebsd-update command does not work well with custom
kernel.
First question is the following :
su -
#freebsd-update fetch
#freebsd-update install
Does this
On Thu, Nov 03, 2011 at 09:19:29AM -0700, Michael Sierchio thus spake:
On Thu, Nov 3, 2011 at 9:13 AM, Jason Helfman jhelf...@e-e.com wrote:
I does work fine with a custom kernel, as long as you are running and
maintaining the actual update server that distributes.
I don't think that's
This is simply not the case. freebsd-update works on the basis of
cryptographic hashes on the binaries. It is, after all, a binary
update program. If it detects a custom kernel, it will not update the
kernel, but updates userland programs. It doesn't *care* what your
kernel config name is, it
I beg to differ. If you run a kernel called CUSTOM, it won't work. And if
you run a custom kernel called GENERIC, the moment you upgrade, you custom
kernel is no longer custom.
All of this aside, I would be interested in hearing how you are able to
avoid non-custom updates to your custom
On Thu, Nov 03, 2011 at 09:42:12AM -0700, Michael Sierchio thus spake:
This is simply not the case. freebsd-update works on the basis of
cryptographic hashes on the binaries. It is, after all, a binary
update program. If it detects a custom kernel, it will not update the
kernel, but updates
---
Inexperienced FreeBSD user: Level 1
pow 1, spd 1, vit 1,int 1,luck 1
--- On Fri, 4/11/11, Alexandre axel...@ymail.com wrote:
From: Alexandre axel...@ymail.com
Subject: Re: freebsd-update (custom kernel)
To: Jason Helfman jhelf...@e-e.com, Michael Sierchio
ku...@tenebras.com, masayoshi
Sorry,all.
I will email same message.
I am not familiar with this webmail.
Thank you very much for the understandable explanations.
I appreciate it very much.
___
freebsd-questions@freebsd.org mailing list
Greetings,
I did binary update with freebsd-update from RELENG6_2p2 to p5 and now
uname -a shows:
FreeBSD mail.uni-svishtov.bg 6.2-RELEASE-p4 FreeBSD 6.2-RELEASE-p4 #0: Thu
Apr 26 17:55:55 UTC 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386
Is that normal ?
My original kernel was
[EMAIL PROTECTED] wrote:
Greetings,
I did binary update with freebsd-update from RELENG6_2p2 to p5 and now
uname -a shows:
FreeBSD mail.uni-svishtov.bg 6.2-RELEASE-p4 FreeBSD 6.2-RELEASE-p4 #0: Thu
Apr 26 17:55:55 UTC 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386
Is that
Manolis Kiagias wrote:
Well, after freebsd-update from my p4 system, uname continued showing p4
as well.
Yes, this is because the update from 6.2-RELEASE-p4 to 6.2-RELEASE-p5 didn't
modify the kernel.
Colin Percival
___
freebsd-questions@freebsd.org
13 matches
Mail list logo