Re: freebsd-update upgrade -r 7.4-RELEASE-p12

2013-10-10 Thread Mark Felder
On Wed, Oct 9, 2013, at 8:36, Eduardo Morras wrote:
> 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
> > > [email protected]:/usr/obj/usr/src/sys/GENERIC
> > >  amd64
> > > #
> > > 
> > > can I take it all the way to -p12?
> > 
> > -p10 through -p12 probably didn't involve any kernel changes. Bumping the 
> > reported patchlevel isn't considered important enough to warrant building a 
> > new kernel.
> 
> That there's no kernel changes doesn't mean that uname -a info is not
> updated. 

You are incorrect. The output of uname -a is taken from the kernel and
cannot be updated without installing a new kernel.

The good news is that FreeBSD 10 will ship with a new utility called
freebsd-version which will provide a better way of identifying if your
system is up to date.

>From the 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 touch
the kernel, or when a new kernel has been installed but the system has
not yet rebooted.

http://svnweb.freebsd.org/base/head/bin/freebsd-version/


By the way, it will be /bin/freebsd-version as it has been relocated
since the import into head.
___
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[email protected]"


Re: freebsd-update upgrade -r 7.4-RELEASE-p12

2013-10-09 Thread Mike Brown
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 things are; our expectations of uname are at fault.

I believe if he were to compile his own kernel, it would say -p12.

Suggestions were made for how to deal with it, but I don't know if they 
were ever followed up on. They wouldn't affect 7.x in any case.

Start reading the thread here: 
http://lists.freebsd.org/pipermail/freebsd-questions/2012-May/240666.html
___
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[email protected]"


Re: freebsd-update upgrade -r 7.4-RELEASE-p12

2013-10-09 Thread alexus
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.

thank you.



On Tue, Oct 8, 2013 at 11:32 PM, 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
> > [email protected]:/usr/obj/usr/src/sys/GENERIC
> >  amd64
> > #
> >
> > can I take it all the way to -p12?
>
> -p10 through -p12 probably didn't involve any kernel changes. Bumping the
> reported patchlevel isn't considered important enough to warrant building a
> new kernel.
>
> If your sources are in /usr/src, do this:
>
> grep -v # /usr/src/sys/conf/newvers.sh | head -4
>



-- 
http://alexus.org/
___
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[email protected]"


Re: freebsd-update upgrade -r 7.4-RELEASE-p12

2013-10-09 Thread Eduardo Morras
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
> > [email protected]:/usr/obj/usr/src/sys/GENERIC
> >  amd64
> > #
> > 
> > can I take it all the way to -p12?
> 
> -p10 through -p12 probably didn't involve any kernel changes. Bumping the 
> reported patchlevel isn't considered important enough to warrant building a 
> new kernel.

That there's no kernel changes doesn't mean that uname -a info is not updated. 
If you update the system from p5 to current (p12), and it shows p9 instead p12 
the first thing you think is that something on the system update went wrong, 
not that everything was fine except the update of the file that uname -a reads. 
If release info patch is p12, it must update the whole system to p12.

If you update an app from 2.24.1 to 2.24.2 and doing 'app -v' shows 2.24.1 it 
means something went wrong, not that update only modified config files and not 
the binary.

> 
> If your sources are in /usr/src, do this:
> 
> grep -v # /usr/src/sys/conf/newvers.sh | head -4

No, 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.

---   ---
Eduardo Morras 
___
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[email protected]"


Re: freebsd-update upgrade -r 7.4-RELEASE-p12

2013-10-09 Thread Mark Felder
On Tue, Oct 8, 2013, at 22:32, 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
> > [email protected]:/usr/obj/usr/src/sys/GENERIC
> >  amd64
> > #
> > 
> > can I take it all the way to -p12?
> 
> -p10 through -p12 probably didn't involve any kernel changes. Bumping the 
> reported patchlevel isn't considered important enough to warrant building
> a 
> new kernel.
> 
> If your sources are in /usr/src, do this:
> 
> grep -v # /usr/src/sys/conf/newvers.sh | head -4
> 

If he had sources on the box he probably would have just compiled the
fixes himself. The version number shouldn't be embedded in 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-update, some were updated by src.
But they don't report the same OS version so I get asked why we haven't
updated those servers yet
___
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[email protected]"


Re: freebsd-update upgrade -r 7.4-RELEASE-p12

2013-10-08 Thread Mike Brown
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
> [email protected]:/usr/obj/usr/src/sys/GENERIC
>  amd64
> #
> 
> can I take it all the way to -p12?

-p10 through -p12 probably didn't involve any kernel changes. Bumping the 
reported patchlevel isn't considered important enough to warrant building a 
new kernel.

If your sources are in /usr/src, do this:

grep -v # /usr/src/sys/conf/newvers.sh | head -4
___
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[email protected]"


Re: freebsd-update upgrade -r 7.4-RELEASE-p12

2013-10-07 Thread alexus
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 files are affected by updates, but no changes have
been downloaded because the files have been modified locally:
/var/db/mergemaster.mtree

No updates needed to update system to 7.4-RELEASE-p12.

WARNING: FreeBSD 7.4-RELEASE-p9 HAS PASSED ITS END-OF-LIFE DATE.
Any security issues discovered after Fri Mar  1 00:00:00 UTC 2013
will not have been corrected.
# freebsd-update install
No updates are available to install.
Run '/usr/sbin/freebsd-update fetch' first.
#



On Mon, Oct 7, 2013 at 5:13 PM, 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 
> [email protected]:/usr/obj/usr/src/sys/GENERIC
>  amd64
> #
>
> can I take it all the way to -p12? (I'm running fetch 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 to run. The -r flag is for jumping major releases (from 7.x to 8.x,
>> for example).
>>
>> I can't comment on whether or not the freebsd-update data for 7.x is
>> still on the servers, though.
>> ___
>> [email protected] mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to "
>> [email protected]"
>>
>
>
>
> --
> http://alexus.org/
>



-- 
http://alexus.org/
___
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[email protected]"


Re: freebsd-update upgrade -r 7.4-RELEASE-p12

2013-10-07 Thread alexus
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
[email protected]:/usr/obj/usr/src/sys/GENERIC
 amd64
#

can I take it all the way to -p12? (I'm running fetch 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 to run. The -r flag is for jumping major releases (from 7.x to 8.x,
> for example).
>
> I can't comment on whether or not the freebsd-update data for 7.x is
> still on the servers, though.
> ___
> [email protected] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> [email protected]"
>



-- 
http://alexus.org/
___
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[email protected]"


Re: freebsd-update upgrade -r 7.4-RELEASE-p12

2013-10-07 Thread Mark Felder
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 whether or not the freebsd-update data for 7.x is
still on the servers, though.
___
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[email protected]"


Re: freebsd-update upgrade -r 7.4-RELEASE-p12

2013-10-07 Thread Andreas Rudisch
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/

Andreas
--
 Andreas Rudisch
 
___
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[email protected]"