Re: freebsd-update upgrade -r 7.4-RELEASE-p12
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 > > > r...@amd64-builder.daemonology.net:/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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: freebsd-update upgrade -r 7.4-RELEASE-p12
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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: freebsd-update upgrade -r 7.4-RELEASE-p12
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 > > r...@amd64-builder.daemonology.net:/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/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: freebsd-update upgrade -r 7.4-RELEASE-p12
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:/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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: freebsd-update upgrade -r 7.4-RELEASE-p12
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 > > r...@amd64-builder.daemonology.net:/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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: freebsd-update upgrade -r 7.4-RELEASE-p12
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 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: freebsd-update upgrade -r 7.4-RELEASE-p12
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 > r...@amd64-builder.daemonology.net:/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. >> ___ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to " >> freebsd-questions-unsubscr...@freebsd.org" >> > > > > -- > http://alexus.org/ > -- http://alexus.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: freebsd-update upgrade -r 7.4-RELEASE-p12
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 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. > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscr...@freebsd.org" > -- http://alexus.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: freebsd-update upgrade -r 7.4-RELEASE-p12
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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: freebsd-update upgrade -r 7.4-RELEASE-p12
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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
re: freebsd-update upgrade -r 9.0-RC2: incorrect hash error [SOLVED]
i'd like to call off my call for help with the problem reported below. i was able to upgrade to 9.0-RC2 today without any trouble. my internet connection got cut off temporarily as i was pulling the files. some of the files might have got corrupted or something. Original Message Subject: re: freebsd-update upgrade -r 9.0-RC2: incorrect hash error Date: Sun, 20 Nov 2011 20:57:50 +0200 From: Alexander Kapshuk To: freebsd-questions@freebsd.org when performing a binary upgrade from 9.0-RC1 to 9.0-RC2 by following the instructions found here: http://lists.freebsd.org/pipermail/freebsd-current/2011-November/029373.html i've had this error: Applying patches... done. Fetching 5612 files... gunzip: (stdin): unexpected end of file 137c71ff94c207e764b910e3b7dca9a4fe282e43104bdeb18af4377014033116 has incorrect hash. has anyone else has this error? what can be done to fix it? :; uname -a FreeBSD localhost 9.0-RC1 FreeBSD 9.0-RC1 #0: Tue Oct 18 18:30:38 UTC 2011 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 thanks. sasha kapshuk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
re: freebsd-update upgrade -r 9.0-RC2: incorrect hash error
when performing a binary upgrade from 9.0-RC1 to 9.0-RC2 by following the instructions found here: http://lists.freebsd.org/pipermail/freebsd-current/2011-November/029373.html i've had this error: Applying patches... done. Fetching 5612 files... gunzip: (stdin): unexpected end of file 137c71ff94c207e764b910e3b7dca9a4fe282e43104bdeb18af4377014033116 has incorrect hash. has anyone else has this error? what can be done to fix it? :; uname -a FreeBSD localhost 9.0-RC1 FreeBSD 9.0-RC1 #0: Tue Oct 18 18:30:38 UTC 2011 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 thanks. sasha kapshuk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: freebsd-update upgrade
On 6/9/10 9:26 PM, Fbsd1 wrote: Glen Barber wrote: On 6/9/10 9:07 PM, Aiza wrote: The upgrade function requires the -r newrelease flag. The manpage does not state the formate of the newrelease value. Is it just the release number like this 8.0 or is it like this 8.0-RELEASE? 8.0-RELEASE. I believe you can pull 8.0-RELEASE-p2 using -r as well. Regards, Thanks. Have another question. When freebsd-update first entered the ports system, it was limited to updating systems that not been changed from the basic release. IE: Recompiling the kernel adding devices or removing them. Is that still true now? If you have a custom kernel installed, freebsd-update will overwrite it with GENERIC, which means you will need to recompile your custom kernel. Regards, -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: freebsd-update upgrade
Glen Barber wrote: On 6/9/10 9:07 PM, Aiza wrote: The upgrade function requires the -r newrelease flag. The manpage does not state the formate of the newrelease value. Is it just the release number like this 8.0 or is it like this 8.0-RELEASE? 8.0-RELEASE. I believe you can pull 8.0-RELEASE-p2 using -r as well. Regards, Thanks. Have another question. When freebsd-update first entered the ports system, it was limited to updating systems that not been changed from the basic release. IE: Recompiling the kernel adding devices or removing them. Is that still true now? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: freebsd-update upgrade
On 6/9/10 9:07 PM, Aiza wrote: The upgrade function requires the -r newrelease flag. The manpage does not state the formate of the newrelease value. Is it just the release number like this 8.0 or is it like this 8.0-RELEASE? 8.0-RELEASE. I believe you can pull 8.0-RELEASE-p2 using -r as well. Regards, -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 'freebsd-update upgrade' hosed system - rescuable?
The installer eventually worked on the sixth attempt (I had to use the CD to load the kernel and then yank the CD out amongst streams of READ_TIMED_OUT errors). May have made things worse, however. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 'freebsd-update upgrade' hosed system - rescuable?
On Wed, 25 Nov 2009 11:49:44 +, cali clarke wrote: > What's the quickest and cleanest way out of this mess? You can install the base system from the FreeBSD 8.0-RC CD-ROM. This should give you a working system again. Keep an eye on NOT formatting anything. Using a live system CD-ROM, it would possibly be a good idea to make a copy of important system configuration files in /etc. With such a live system CD-ROM, you can even install just parts, such as the content of various /usr subtrees that are affected. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: freebsd-update upgrade problem
Tore Lund wrote: Manolis Kiagias wrote: Hi, I have already upgraded a couple of machines from 7.0-RC1/2 to 7.0-RELEASE using: freebsd-update -r 7.0-RELEASE upgrade However, on this one machine, I get this: freebsd-update: cannot open files/.gz: No such file or directory I have no answer, but as step in hopefully the right direction, let me ask: does /var/db/freebsd-update/files exist when you get that message? Are there any files in it? I upgraded yesterday, and my ../files directory is full of *.gz files. I can't really remember, but since I've deleted and recreated the entire folder, it should have been recreated at first run as well. I didn't really solve the freebsd-update problem, but I upgraded the machine in the following way: I did a binary upgrade from the CD, then csup'd the sources and recompiled the kernel. I guess if there continues to be a problem with freebsd-update, it may exhibit itself during normal updates as well. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: freebsd-update upgrade problem
Manolis Kiagias wrote: > Hi, > > I have already upgraded a couple of machines from 7.0-RC1/2 to > 7.0-RELEASE using: > > freebsd-update -r 7.0-RELEASE upgrade > > However, on this one machine, I get this: > > freebsd-update: cannot open files/.gz: No such file or directory I have no answer, but as step in hopefully the right direction, let me ask: does /var/db/freebsd-update/files exist when you get that message? Are there any files in it? I upgraded yesterday, and my ../files directory is full of *.gz files. -- Tore ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Update Upgrade
Am Montag, 25. April 2005 01:59 schrieb Giuliano Cardozo Medalha: > People, > > When I try to use CVSUP ... if I use the script with: > > tag=. ... what it mean ? It mean 5.4 or 5.3 sources ? It's HEAD, which is 6-current, the developers code base ;) You want RELENG_5_4 for 5.4 sources and RELENG_5 for the -stable branch. See the handbook for further details. -Harry > > How is possible to put the system in the current version and in the > stable version ? > > Thanks a lot > > giuliano > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" pgpMaSTQIc4lP.pgp Description: PGP signature
