commit message:
Introduce the /libexec/freebsd-version script, which is intended to be
used by auditing tools to determine the userland patch level when it
differs from what `uname -r` reports. This can happen when the system
is kept up-to-date using freebsd-update and the last SA did not touc
Eduardo Morras wrote:
> [...] uname -a should give the correct answer. Has uname other utility than
> show information about the operating system implementation? No, and it must
> be accurate.
That's what I thought, but when I asked about it here last year, I was told
that this is the way thing
Mike Brown:
$ grep ^BRANCH /usr/src/sys/conf/newvers.sh
BRANCH="RELEASE-p12"
$
then again, I used freebsd-update and not /usr/src, but it makes sense what
you said with kernel, so I guess I _AM_ on the latest -p12 and kernel is on
-p9 as there was no changes after that to kernel.
On Tue, 8 Oct 2013 21:32:39 -0600 (MDT)
Mike Brown wrote:
> alexus wrote:
> > ok, I just did fetch & install and got bumped from p5 to p9
> >
> > # uname -a
> > FreeBSD XX.X.org 7.4-RELEASE-p9 FreeBSD 7.4-RELEASE-p9 #0: Mon Jun 11
> > 19:47:58 UTC 2012
> > r...@amd64-builder.daemonology.net:
n the kernel
like that so it's easier for people to audit their systems. I have VMs
right now in Xen that report different FreeBSD versions and it's
confusing for other sysadmins who aren't intimately familiar with
FreeBSD. Some were updated by freebsd-upda
alexus wrote:
> ok, I just did fetch & install and got bumped from p5 to p9
>
> # uname -a
> FreeBSD XX.X.org 7.4-RELEASE-p9 FreeBSD 7.4-RELEASE-p9 #0: Mon Jun 11
> 19:47:58 UTC 2012
> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
> amd64
> #
>
> can I take it all the way t
it didn't help..
# freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 7.4-RELEASE from update6.freebsd.org...
done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.
The following file
tch again, hoping it will
do that)
On Mon, Oct 7, 2013 at 4:16 PM, Mark Felder wrote:
> On Mon, Oct 7, 2013, at 14:22, alexus wrote:
> > bash-4.2# freebsd-update upgrade -r 7.4-RELEASE-p12
>
> Just freebsd-update fetch && freebsd-update install is all you should
> have
On Mon, Oct 7, 2013, at 14:22, alexus wrote:
> bash-4.2# freebsd-update upgrade -r 7.4-RELEASE-p12
Just freebsd-update fetch && freebsd-update install is all you should
have to run. The -r flag is for jumping major releases (from 7.x to 8.x,
for example).
I can't comment on wh
On Mon, 7 Oct 2013 15:22:17 -0400
alexus wrote:
> bash-4.2# freebsd-update upgrade -r 7.4-RELEASE-p12
> Is there a way to upgrade 7.4-RELEASE-p5 to 7.4-RELEASE-p12 using
> freebsd-update now?
What about:
# freebsd-update fetch
# freebsd-update install
http://www.freebsd.org/security/
bash-4.2# freebsd-update upgrade -r 7.4-RELEASE-p12
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 7.4-RELEASE from update4.freebsd.org...
done.
Fetching metadata index... done.
Inspecting system... done.
The following components of FreeBSD seem to be
freebsd-update whatever on 9.2-PRERELEASE yields "Fetching public key from
... failed." using the freebsd-update.conf that comes w/the system. i must
be doing something wrong. what?
david coder
___
freebsd-questions@freebsd.org ma
Help! I just used freebsd-update to upgrade a system to FreeBSD
9.1-RELEASE-p5 to close the latest security holes. I then rebuilt
my custom kernel and tried to reboot. I'm now getting the message
Can't work out which disk we are booting from.
Guessed BIOS device 0x not found
Hi all,
A small followup:
Looks like freebsd-update does try to rebuild the password database but does
not quite succeed, leaving binary files in somewhat corrupted state, this
leading to some problems when trying to add new users later. This is
discussed here:
http://www.freebsd.org/cgi
Hi all,
In case anybody was following this discussion, I have successfully upgraded
the system from 8.2 to 8.4 using freebsd-update. The process did have some
glitches (in retrospect, minor ones) but mostly they were not related to
freebsd-update (like some issues with gmirror and firewall
On Thu, Jun 27, 2013 at 8:05 PM, Patrick wrote:
> Is it possible to skip point releases using freebsd-update so that I
> can go from 8.0 to 8.4
Yes. http://www.freebsd.org/releases/8.4R/relnotes-detailed.html#upgrade
--
Adam Vand
Is it possible to skip point releases using freebsd-update so that I
can go from 8.0 to 8.4, or do I need to go 8.0 -> 8.1 -> 8.2 -> 8.3 ->
8.4?
Patrick
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/list
On Wed, Jun 26, 2013, at 2:07, Mike Brown wrote:
>
> Next step, I think, is reboot, before another 'freebsd-update install'
> run.
> I'm worried something is still amiss, though, so I'm holding off for now.
> :(
When in doubt: fetch source, build, instal
I wrote:
> The main problem this time is that I'm not so lucky with the password files,
> because for 8.4, freebsd-update has fetched new, stock .db files to put in
> /etc.
Whoa, sorry, I misspoke here.
freebsd-update asked me, after the merges, to approve unspecified differen
On Tue, Jun 25, 2013, at 15:29, Eugene wrote:
> I do not quite understand. Is the freebsd-update upgrade process
> completely broken?
IMHO it is partially broken; I'm not doing anything special. How broken it is
depends on what's getting changed. Most of what the system is des
On Tue, Jun 25, 2013, at 15:29, Eugene wrote:
> Hi all,
>
> I do not quite understand. Is the freebsd-update upgrade process
> completely
> broken? Or is it some special mode? Or was it broken recently?
> Because some time ago I have upgraded from 8.1 to 8.2 quite nicely, wi
Hi all,
I do not quite understand. Is the freebsd-update upgrade process completely
broken? Or is it some special mode? Or was it broken recently?
Because some time ago I have upgraded from 8.1 to 8.2 quite nicely, with
editor-based merging of config files, and was planning to upgrade to 8.4
On Tue, Jun 25, 2013, at 3:14, Mike Brown wrote:
>
> Well, thanks for reading this far. I'm scared to death to reboot now,
> since my
> server is in another city, but we'll see how it goes.
>
I always avoid freebsd-update when moving between releases simply
because
> I'm using freebsd-update to upgrade my system to the latest minor version
> (from 8.3-RELEASE to 8.4-RELEASE).
>
> I'm surprised that the merge handling system isn't more robust. When
> upgrading
> the old way, from source, I was used to using mergemaster to h
> Fetching 1 metadata files... 70.5%
> done.
> 70.5%
> 70.5%
> 74.2%
> 74.2%
> 81.7%
> 81.7%
> 70.5%
I think this is a result of having "-v" in my GZIP environment variable.
I always forget about my GZIP and BZIP2 variables. I should've known.
So, never mind about that.
___
I'm using freebsd-update to upgrade my system to the latest minor version
(from 8.3-RELEASE to 8.4-RELEASE).
I'm surprised that the merge handling system isn't more robust. When upgrading
the old way, from source, I was used to using mergemaster to handle any
merges that c
I'm using freebsd-update to upgrade my system to the latest minor release.
At a couple points in the process, I get weird status indicators (percentages)
showing me that something is happening:
Fetching 1 metadata files... 70.5%
done.
70.5%
70.5%
74.2%
74.2%
81.7%
81.7%
On Mon, May 13, 2013 at 11:22:41AM +0200, Wolfgang Riegler wrote:
> Hi,
>
> since last freebsd-update fetch install I always get this message after
> freebsd-update fetch:
>
> The following files will be updated as part of updating to 9.1-RELEASE-p3:
> /boot/kernel/linker.h
Hi,
since last freebsd-update fetch install I always get this message after
freebsd-update fetch:
The following files will be updated as part of updating to 9.1-RELEASE-p3:
/boot/kernel/linker.hints
but freebsd-update install doesn't install anything.
Is there something wrong with my s
I had an 8.2 system that I wanted to take to 8.4. First I tried upgrade to 8.4,
getting (in essence) can't do that. So I upgraded 8.2 which worked giving the
end-of-life warning. But seemed work. I then did an upgrade to 8.3 with:
freebsd-update -r 8.3-RELEASE upgrade
The first
On Thu, 25 Apr 2013 11:14:06 -0400 (EDT), Daniel Feenberg wrote:
> This is written as though it applies to FreeBSD, but I was
> under the impression that FreeBSD didn't do anything with
> /etc/issue.
It actually works quite well, I'm using it for decades. :-)
You just need to add the item "if=/et
On Thu, 25 Apr 2013, Polytropon wrote:
On Thu, 25 Apr 2013 07:37:01 -0400 (EDT), Daniel Feenberg wrote:
On Thu, 25 Apr 2013, Steve O'Hara-Smith wrote:
The problem under discussion is that the kernel version does not
change when a freebsd-update update does not include a k
On Thu, 25 Apr 2013 07:37:01 -0400 (EDT), Daniel Feenberg wrote:
>
>
> On Thu, 25 Apr 2013, Steve O'Hara-Smith wrote:
>
> >
> > The problem under discussion is that the kernel version does not
> > change when a freebsd-update update does not include a
On Thu, 25 Apr 2013, Steve O'Hara-Smith wrote:
The problem under discussion is that the kernel version does not
change when a freebsd-update update does not include a kernel change.
Perhaps we could adopt the Linux practice of placing the release
information in /etc/
On Thu, 25 Apr 2013 13:43:03 +1000
Da Rock wrote:
> Interesting. My only observation was that sysctl is supposed to be the
> 'system' database where all queries relate to. It is supposed to display
> everything about the system; therefore any of these data bits should be
> fixed here first. An
if the version of the OS itself was stored in
> >> something like /etc/freebsd-version so you know what the version of
> >> the OS as a
> > Yes it would.
> >
> sysctl kern.version
The problem under discussion is that the kernel version does not
change when a freeb
ersion level of the operating system.
|
|This part of documentation would, given the case, also require
|adjustment, refering to the kernel instead of the OS.
=
On the other hand, maybe instead of changing the documentation of uname
to accommodate a problem with freebsd update, maybe
ystem.
|
|This part of documentation would, given the case, also require
|adjustment, refering to the kernel instead of the OS.
=
On the other hand, maybe instead of changing the documentation of uname
to accommodate a problem with freebsd update, maybe freebsd update
should be chang
On Wed, 24 Apr 2013 22:32:17 -0400, Mike. wrote:
> If uname -r [-a] does not give the proper version of the OS, then it is
> either a bug, or the documentation for uname should be changed.
> Currently, the man page for uname gives the following option:
>
> -r Write the current release level o
On 4/24/2013 at 5:07 PM Mike Brown wrote:
|Da Rock wrote:
|> sysctl kern.version
|
|For me, that's the same info as in uname -a.
|
|Try this:
|
|grep -v # /usr/src/sys/conf/newvers.sh | head -4
=
If uname -r [-a] does not give the proper version of the OS, then it is
either a bug, o
w more
precise information about what version of the OS is currently
installed. I suggest having a text file in /etc that contains
the currently installed version, maybe also a SVN revision
number and a date. Updating via freebsd-update should not be
that complicated. Also by updating from source (e. g. w
On Wed, Apr 24, 2013, at 20:41, Da Rock wrote:
> On 04/25/13 09:07, Mike Brown wrote:
> > Da Rock wrote:
> >> sysctl kern.version
> > For me, that's the same info as in uname -a.
> >
> > Try this:
> >
> > grep -v # /usr/src/sys/conf/newvers.sh | head -4
> That shows even less. But the point of the
On 04/25/13 09:07, Mike Brown wrote:
Da Rock wrote:
sysctl kern.version
For me, that's the same info as in uname -a.
Try this:
grep -v # /usr/src/sys/conf/newvers.sh | head -4
That shows even less. But the point of the OP was having a file in etc
with the info on version, which I fell could
On Wed, Apr 24, 2013, at 18:07, Mike Brown wrote:
> Da Rock wrote:
> > sysctl kern.version
>
> For me, that's the same info as in uname -a.
>
> Try this:
>
> grep -v # /usr/src/sys/conf/newvers.sh | head -4
>
Not useful if you don't have src on your servers, but that's good to
know.
___
Da Rock wrote:
> sysctl kern.version
For me, that's the same info as in uname -a.
Try this:
grep -v # /usr/src/sys/conf/newvers.sh | head -4
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To u
On 04/25/13 06:31, Steve O'Hara-Smith wrote:
On Wed, 24 Apr 2013 14:52:17 -0500
"Mark Felder" wrote:
On Wed, 24 Apr 2013 14:34:30 -0500, Steve O'Hara-Smith
wrote:
You have updated to 9.1-RELEASE-p2 - but since there have been no
kernel changes since 9.1-RELEASE the kernel version message ha
On Wed, 24 Apr 2013 14:52:17 -0500
"Mark Felder" wrote:
> On Wed, 24 Apr 2013 14:34:30 -0500, Steve O'Hara-Smith
> wrote:
>
> > You have updated to 9.1-RELEASE-p2 - but since there have been no
> > kernel changes since 9.1-RELEASE the kernel version message hasn't
> > changed.
> > This could
update.
>
> It would be nice if the version of the OS itself was stored in something
> like /etc/freebsd-version so you know what the version of the OS as a
> whole is. I'd even accept some sort of output by freebsd-update. It just
> seems silly that there's no other way --
On Wed, 24 Apr 2013 19:35:01 +0200, Alexandre wrote:
> Freebsd-update tool apply binary patches to your -RELEASE system and
> GENERIC kernel.
> Furthermore, sources are synced too (/usr/src) by default.
> If you want to see the -p# increased, you have to recompile your GENERIC
> k
the version of the OS as a
whole is. I'd even accept some sort of output by freebsd-update. It just
seems silly that there's no other way -- kern.osrelease is just the base
release and kern.version is the same thing that uname -a outputs. It's
hard to pick thi
On Wed, 24 Apr 2013 16:00:47 + (UTC)
Walter Hurry wrote:
> When I issue 'freebsd-update fetch install I see this:
>
> Looking up update.FreeBSD.org mirrors... 3 mirrors found.
> Fetching metadata signature for 9.1-RELEASE from up
o_ change has been written to the kernel, it will still report
> > 9.1, even though the updates for -p2 have been applied to other places
> > (like system binaries or libraries).
> >
> > You can use the -r option to freebsd-update to explicitely specify a
> > version to
, even though the updates for -p2 have been applied to other places
> (like system binaries or libraries).
>
> You can use the -r option to freebsd-update to explicitely specify a
> version to update to. See "man freebsd-update" for details.
Thank
On Wed, 24 Apr 2013 16:00:47 + (UTC), Walter Hurry wrote:
> When I issue 'freebsd-update fetch install I see this:
>
> Looking up update.FreeBSD.org mirrors... 3 mirrors found.
> Fetching metadata signature for 9.1-RELEASE from up
When I issue 'freebsd-update fetch install I see this:
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 9.1-RELEASE from update5.freebsd.org...
done.
Fetching metadata index... done.
Inspecting system...
following:
> On Wed, 17 Apr 2013 22:37:06 +0200, andreas scherrer wrote:
>> For some reason I was under the impression that /usr/src/sys is not
>> being updated by freebsd-update if I remove "kernel" from the
>> "Components" directive in freebsd
On Wed, 17 Apr 2013 22:37:06 +0200, andreas scherrer wrote:
> For some reason I was under the impression that /usr/src/sys is not
> being updated by freebsd-update if I remove "kernel" from the
> "Components" directive in freebsd-update.conf. But I might be wrong (I
I want to "track" RELEASE (not a
>> development branch) and I want to receive security related updates. And
>> I want to run a custom kernel.
>
> Without actually havint tested it, it seems that if you want
> to use freebsd-update (binary updating), you should note thi
Hi Andreas and Polytropon,
In the case your are tracking -RELEASE branch, you can use freebsd-update
tool to apply binary security patches on your system and upgrade versions
(e.g. 9.0 to 9.1 or 9.x to 10.0 when available).
Freebsd-update tool apply binary updates to your system and GENERIC
I want to receive security related updates. And
> I want to run a custom kernel.
Without actually havint tested it, it seems that if you want
to use freebsd-update (binary updating), you should note this:
In /etc/freebsd-update.conf, you should have the line for what
to update as "Components s
rom what I understand I cannot use "freebsd-update" in this case
because it will invariably either overwrite my custom kernel (if I have
"Components kernel" in the config file) or not update the kernel sources
in /usr/src/sys (when I do not have "Components kernel" in the
Thank you, Matthew!
That answers all of my questions. :-)
I've done a "freebsd-update install" and it seems to have resolved the
situation alright.
~ melanie
--
M. Schulte -- mail & jabber: m...@fuglos.org
http://m.fuglos.org/
__
9.1-RELEASE-p2 #5 r249029: Wed Apr 3
> 12:29:28 CEST 2013 root@XXX:/usr/obj/usr/src/sys/FUGLOS amd64
>
> But what I don't understand is the following. Whenever I execute
> 'freebsd-update fetch' (I had added a 'freebsd-update cron' to my
> crontab), t
following. Whenever I execute
'freebsd-update fetch' (I had added a 'freebsd-update cron' to my
crontab), the output below(!) is generated.
It's not clear to me what this actually means:
* Why does freebsd-update want to update my system to 9.1-RELEASE-p2,
although
The article "Build Your Own FreeBSD Update Server" at
http://www.freebsd.org/doc/en/articles/freebsd-update-server/index.htmlrefers
to the freebsd-update-server located at
http://www.freebsd.org/cgi/cvsweb.cgi/projects/freebsd-update-server which
does not exist. Does this project still
Paul Macdonald writes:
> On 01/02/2013 22:50, Carl Johnson wrote:
>> Gökşin Akdeniz writes:
>>
>>> Fri, 01 Feb 2013 11:51:41 -0800 tarihinde
>>> Carl Johnson yazmış:
Does anybody have any suggestions on what might have happened and what
can be done?
>>> Hello Carl,
>>>
>>> What d
On 01/02/2013 22:50, Carl Johnson wrote:
Gökşin Akdeniz writes:
Fri, 01 Feb 2013 11:51:41 -0800 tarihinde
Carl Johnson yazmış:
Does anybody have any suggestions on what might have happened and what
can be done?
Hello Carl,
What does "# uname -a" or "# uname -r" output says?
It still show
Carl Johnson writes:
> Kevin Kinsey writes:
>
>> On Fri, Feb 01, 2013 at 11:51:41AM -0800, Carl Johnson wrote:
>>> I ran freebsd-update to update my 8.1-RELEASE system to 8.3-RELEASE
>>> (freebsd-update -r 8.3-RELEASE upgrade). It downloaded a bunch of
&g
On 01/02/2013 22:50, Carl Johnson wrote:
Gökşin Akdeniz writes:
Fri, 01 Feb 2013 11:51:41 -0800 tarihinde
Carl Johnson yazmış:
Does anybody have any suggestions on what might have happened and what
can be done?
Hello Carl,
What does "# uname -a" or "# uname -r" output says?
It still show
Gökşin Akdeniz writes:
> Fri, 01 Feb 2013 11:51:41 -0800 tarihinde
> Carl Johnson yazmış:
>>
>> Does anybody have any suggestions on what might have happened and what
>> can be done?
>>
>
> Hello Carl,
>
> What does "# uname -a" or "# uname -r" output says?
It still shows 8.1, but another pos
Kevin Kinsey writes:
> On Fri, Feb 01, 2013 at 11:51:41AM -0800, Carl Johnson wrote:
>> I ran freebsd-update to update my 8.1-RELEASE system to 8.3-RELEASE
>> (freebsd-update -r 8.3-RELEASE upgrade). It downloaded a bunch of
>> files, asked me to edit some configuration
Fri, 01 Feb 2013 11:51:41 -0800 tarihinde
Carl Johnson yazmış:
>
> Does anybody have any suggestions on what might have happened and what
> can be done?
>
Hello Carl,
What does "# uname -a" or "# uname -r" output says?
--
Gökşin Akdeniz
pgpxkVgruffrn.pgp
Description: PGP signature
On Fri, Feb 01, 2013 at 11:51:41AM -0800, Carl Johnson wrote:
> I ran freebsd-update to update my 8.1-RELEASE system to 8.3-RELEASE
> (freebsd-update -r 8.3-RELEASE upgrade). It downloaded a bunch of
> files, asked me to edit some configuration files, showed me long lists
> of fil
I ran freebsd-update to update my 8.1-RELEASE system to 8.3-RELEASE
(freebsd-update -r 8.3-RELEASE upgrade). It downloaded a bunch of
files, asked me to edit some configuration files, showed me long lists
of files that have been changed, added and removed, and then ended with
no status or error
I can't seem to get freebsd-update to do the jump from 9.2-RELEASE-p9 to p10.
This is what I'm getting.
> sudo freebsd-update fetch
Password:
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 8.2-RELEASE from update5.FreeBS
Hi!
I run freebsd-update on my upgraded FreeBSD 9.1-RELEASE and I got:
/var/cache has 0755 permissions, but should have 0750 permissions
I don't have a server. Should I change permission, please?
Thank you.
Mitja
http://www.redbubble.com/people/l
Joe Altman wrote:
On Thu, Jan 03, 2013 at 03:50:44PM +0100, Martin Laabs wrote:
Hi,
On 01/02/13 01:21, Joe Altman wrote:
Greetings, list. I have the following error; though I can load
update5.FreeBSD.org in a browser:
[...]
maybe you use a release that is not supported by freebsd-update. Run
On Thu, Jan 03, 2013 at 03:50:44PM +0100, Martin Laabs wrote:
> Hi,
>
> On 01/02/13 01:21, Joe Altman wrote:
> > Greetings, list. I have the following error; though I can load
> > update5.FreeBSD.org in a browser:
> > [...]
>
> maybe you use a release that i
Hi,
On 01/02/13 01:21, Joe Altman wrote:
> Greetings, list. I have the following error; though I can load
> update5.FreeBSD.org in a browser:
> [...]
maybe you use a release that is not supported by freebsd-update. Run "uname
-r" an compare the release with that you see w
Hi,
On 01/02/13 01:21, Joe Altman wrote:
> Greetings, list. I have the following error; though I can load
> update5.FreeBSD.org in a browser:
> [...]
maybe you use a release that is not supported by freebsd-update. Run "uname
-r" an compare the release with that you see w
I've used STABLE for years, but with csup going away, I don't want to
deal with adding extra packages, and keeping them unbroken, just to stay
up date. Running freebsd-update doesn't work for people running STABLE,
and I'm not sure freebsd-update will work properly anyway
On 02/01/2013 20:55, Paul Schmehl wrote:
> I wasn't thinking when I wrote this. Freebsd-update pulls *binary*
> copies of files, so you're not ever going to get the src files to
> rebuild your kernel from freebsd-update. You need to pull those in
> using svn.
Not so
/kernel/kernel which is my custom kernel with a GENERIC kernel.
As it seems that freebsd-update works by comparing a hash of
/boot/kernel/kernel with the GENERIC kernel's hash I checked the md5
and sha1 hash of /boot/kernel/kernel and /boot/GENERIC/kernel. They
differ (see [3]).
So why is fr
.
As it seems that freebsd-update works by comparing a hash of
/boot/kernel/kernel with the GENERIC kernel's hash I checked the md5 and
sha1 hash of /boot/kernel/kernel and /boot/GENERIC/kernel. They differ
(see [3]).
So why is freebsd-update going to overwrite my custom kernel? And how
can I pr
On Wed, Jan 2, 2013 at 11:18 AM, andreas scherrer wrote:
This is no longer true, though it was true at the time that was written...
-
> However, freebsd-update will detect and update the GENERIC kernel in
> /boot/GENERIC (if it exists), even if it is not the current (running)
> kern
on 2.1.13 19:15 Paul Schmehl said the following:
> --On January 2, 2013 6:45:50 PM +0100 andreas scherrer
>> And from experience this is what it will do: replace /boot/kernel/kernel
>> which is my custom kernel with a GENERIC kernel.
>>
>> As it seems that freebsd-updat
The confusion comes from the fact that the original behavior of
freebsd-update was NOT to update the kernel binaries if a custom kernel was
detected.
FYI my /etc/freebsd-update.conf has
# Components of the base system which should be kept updated.
#Components src world kernel
Components src
Hi Jose,
with the freebsd-update method you don't need to pass through the "make
installworld" as it's a binary patch/upgrade system.
Using "freebsd-update upgrade -r 9.1-RELEASE" for example allows you to
get your system patched directly without recompiling t
For some reason my email hasn't apparently been delivered so I'm re-sending it.
"From: ASV
To: Jose Garcia Juanino
Cc: freebsd-questions@freebsd.org
Subject:Re: Newbie question about freebsd-update: single user mode is
not needed anymore?
Date: Mon, 31 De
--On January 2, 2013 6:45:50 PM +0100 andreas scherrer
wrote:
Hi
This can be considered a follow up to the message "How to keep
freebsd-update from trashing custom kernel?" sent to this list by Brett
Glass on August 13th 2012 (see [1]). Unfortunately there is no solution
to the
Well,
I understand your concern. I've been using the freebsd-update method
since several years now and mostly remotely. I've never encounter a
problem. I haven't recompiled everything many times as I didn't really
found a tangible advantage in this method but I've ne
Hi
This can be considered a follow up to the message "How to keep
freebsd-update from trashing custom kernel?" sent to this list by Brett
Glass on August 13th 2012 (see [1]). Unfortunately there is no solution
to the problem in that thread (or I cannot see it).
I am running currently r
Greetings, list. I have the following error; though I can load
update5.FreeBSD.org in a browser:
root-is-on-fire # freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching public key from update4.FreeBSD.org... failed.
Fetching public key from update5.FreeBSD.org
El lunes 31 de diciembre a las 16:27:44 CET, ASV escribió:
> Hi Jose,
>
> with the freebsd-update method you don't need to pass through the "make
> installworld" as it's a binary patch/upgrade system.
> Using "freebsd-update upgrade -r 9.1-RELEASE"
single user is not required with freebsd-update method, in the
> second "freebsd-update install". Someone could explain the reason? Am I
> misunderstanding something? Can I run the upgrade enterely by mean a ssh
> connection in a safe way, or will I need a serial console?
>
&
Hi,
I am planning to upgrade from FreeBSD 9.0-RELEASE to
FreeBSD-9.1-RELEASE. With upgrade source method, it is always needed to
do the "make installworld" step in single user mode. But it seems to
be that single user is not required with freebsd-update method, in the
second "
On Sun, 25 Nov 2012 12:06:06 +, Karl Pielorz wrote:
>
>
> --On 22 November 2012 17:41 +0100 Polytropon wrote:
>
> >> I'm looking at switching to 'freebsd-update' - is there an equivalent
> >> way to get it to update me to '-STABLE'?
--On 22 November 2012 17:41 +0100 Polytropon wrote:
I'm looking at switching to 'freebsd-update' - is there an equivalent
way to get it to update me to '-STABLE'?
No. The freebsd-update program can only be used to follow
the RELEASE branch, plus the sec
On Fri, 23 Nov 2012, free...@johnea.net wrote:
One of the complications was getting old metadata off of the drive. After
trying a couple of 'dd' invocations:
# overwriting the first sector
dd if=/dev/zero of=/dev/ada0 bs=512 count=1
# also tried overwriting the last sector
diskinfo ada0 | cut -
On 2012-11-20 21:10, Warren Block wrote:
> On Tue, 20 Nov 2012, free...@johnea.net wrote:
>
>> On 2012-11-20 14:28, Gary Aitken wrote:
>>> On 11/20/12 13:34, free...@johnea.net wrote:
>>
>>>> freebsd-update upgrade -r 9.1-RC3
>> ...
>>>>
1 - 100 of 656 matches
Mail list logo
