Updating 5.2.1 Release #
Hi, I completed my first update (upgrade?) of a 5.2.1 fresh FreeBSD install. I followed a couple how-to's, the handbook, and Absolute BSD as my guides. My machine is a 1.8Ghz AMD. Here is my supfile: *default host=cvsup15.us.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_5_2_1_RELEASE *default delete use-rel-suffix *default compress src-all ports-all tag=. Everything seemed to go without a hitch. I did: 1. cvsup mysupfile 2. make buildworld 3. make buildkernel 4. make installkernel 5. make installworld The system is up and seems to be running fine, but here's my question: uname -a shows: FreeBSD 5.2.1-Release #0: I was expecting the release (version, revision# ?) number to be greater than #0. I think I've seen where the latest revision is #9 or so? Do I need to tell it to get the latest revision somehow? Do I need to change the cvs tag= to something else to get up to date? Thanks for your time, Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating 5.2.1 Release #
Change this: *default release=cvs tag=RELENG_5_2_1_RELEASE for this *default release=cvs tag=RELENG_5_2_1 On this way it will download the release 5.2.1 with the last revision - Original Message - From: Scott [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, July 29, 2004 11:05 AM Subject: Updating 5.2.1 Release # Hi, I completed my first update (upgrade?) of a 5.2.1 fresh FreeBSD install. I followed a couple how-to's, the handbook, and Absolute BSD as my guides. My machine is a 1.8Ghz AMD. Here is my supfile: *default host=cvsup15.us.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_5_2_1_RELEASE *default delete use-rel-suffix *default compress src-all ports-all tag=. Everything seemed to go without a hitch. I did: 1. cvsup mysupfile 2. make buildworld 3. make buildkernel 4. make installkernel 5. make installworld The system is up and seems to be running fine, but here's my question: uname -a shows: FreeBSD 5.2.1-Release #0: I was expecting the release (version, revision# ?) number to be greater than #0. I think I've seen where the latest revision is #9 or so? Do I need to tell it to get the latest revision somehow? Do I need to change the cvs tag= to something else to get up to date? Thanks for your time, Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating 5.2.1 Release #
Scott wrote: Hi, I completed my first update (upgrade?) of a 5.2.1 fresh FreeBSD install. I followed a couple how-to's, the handbook, and Absolute BSD as my guides. My machine is a 1.8Ghz AMD. Here is my supfile: *default host=cvsup15.us.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_5_2_1_RELEASE *default delete use-rel-suffix *default compress src-all ports-all tag=. Everything seemed to go without a hitch. I did: 1. cvsup mysupfile 2. make buildworld 3. make buildkernel 4. make installkernel 5. make installworld The system is up and seems to be running fine, but here's my question: uname -a shows: FreeBSD 5.2.1-Release #0: I was expecting the release (version, revision# ?) number to be greater than #0. I think I've seen where the latest revision is #9 or so? Do I need to tell it to get the latest revision somehow? Do I need to change the cvs tag= to something else to get up to date? I thought the #number indicated the number of times the server has been rebooted based upon the last time the kernel was recompiled. Being that it is #0, it was your first book. Reboot the machine and check the number again. Puna Thanks for your time, Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating 5.2.1 Release #
On Thu, Jul 29, 2004 at 09:37:35AM -0500, Puna Tannehill wrote: Scott wrote: uname -a shows: FreeBSD 5.2.1-Release #0: I was expecting the release (version, revision# ?) number to be greater than #0. I think I've seen where the latest revision is #9 or so? Do I need to tell it to get the latest revision somehow? Do I need to change the cvs tag= to something else to get up to date? I thought the #number indicated the number of times the server has been rebooted based upon the last time the kernel was recompiled. Being that it is #0, it was your first book. Reboot the machine and check the number again. I believe that the #n is the number of times the kernel has been re-compiled since the last time the system was installed. It's probably not a very interesting datum except to kernel hackers who need to do a lot of recompiling. What the original poster was thinking of is the patchlevel that gets incremented every time a new security (or nowadays: errata) patch is applied to any of the -RELEASE branches. That modifies the OS name (ie. the output of 'uname -r'), so instead of: 5.2.1-RELEASE it says (at the latest count): 5.2.1-RELEASE-p9 See /usr/src/sys/conf/newvers.sh for the file that controls all that. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgpQ0wYOal1Cj.pgp Description: PGP signature
Re: Updating 5.2.1 Release #
( What the original poster was thinking of is ( the patchlevel that gets incremented every ( time a new security (or nowadays: errata) ( patch is applied to any of the -RELEASE ( branches. That modifies the OS name (ie. ( the output of 'uname -r') That is exactly right Matthew. I thought (assumed) that #0 in the uname -a output was the patchlevel of the OS. At this point in my life, I'm not so concerned about what that number is, but rather I am running the most secure and stable patchlevel available. So if I set my cvs tag as Ezequiel (thank you) suggested: change: *default release=cvs tag=RELENG_5_2_1_RELEASE to: *default release=cvs tag=RELENG_5_2_1 That will get me the latest patches? I'll make that change and rebuild again today. Thanks all for your help. :) Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Updating 5.2.1 Release #
Matthew Seaman On Thu, Jul 29, 2004 at 09:37:35AM -0500, Puna Tannehill wrote: Scott wrote: uname -a shows: FreeBSD 5.2.1-Release #0: I was expecting the release (version, revision# ?) number to be greater than #0. I think I've seen where the latest revision is #9 or so? Do I need to tell it to get the latest revision somehow? Do I need to change the cvs tag= to something else to get up to date? I thought the #number indicated the number of times the server has been rebooted based upon the last time the kernel was recompiled. Being that it is #0, it was your first book. Reboot the machine and check the number again. I believe that the #n is the number of times the kernel has been re-compiled since the last time the system was installed. It's probably not a very interesting datum except to kernel hackers who need to do a lot of recompiling. What the original poster was thinking of is the patchlevel that gets incremented every time a new security (or nowadays: errata) patch is applied to any of the -RELEASE branches. That modifies the OS name (ie. the output of 'uname -r'), so instead of: So what is the diff between uname -r and uname -v, which produce for me : Uname -r : 5.2.1-RELEASE Uname -v : FreeBSD 5.2.1-RELEASE #0: Mon Jun 14 14:52:08 CEST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CNV_TOTAL Extract from man page : -r Write the current release level of the operating system -v Write the version level of this release of the operating system So that's mean that there are several Release ( as relesase level) and inside each release level there are several version level, am'I understanding well ? Cedric. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating 5.2.1 Release #
Ok, I just did as suggested: ( Change this: ( *default release=cvs tag=RELENG_5_2_1_RELEASE ( ( for this ( *default release=cvs tag=RELENG_5_2_1 and ran cvsup again. This time, I successfully and quickly deleted every thing under /usr/src. There must be something wrong with my cvs tag. I read the notice in the handbook that says Be very careful to specify any tag= fields correctly. Some tags are valid only for certain collections of files. If you specify an incorrect or misspelled tag, CVSup will delete files which you probably do not want deleted. Here is my supfile that just deleted everything under /usr/src: *default host=cvsup15.us.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_5_2_1 *default delete use-rel-suffix *default compress src-all ports-all tag=. To keep up to date with 5.2.1, is that the correct tag? I'm reinstalling now . . . Thanks, Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating 5.2.1 Release #
On Thu, Jul 29, 2004 at 05:51:57PM +0200, Cedric GROSS wrote: So what is the diff between uname -r and uname -v, which produce for me : Uname -r : 5.2.1-RELEASE Uname -v : FreeBSD 5.2.1-RELEASE #0: Mon Jun 14 14:52:08 CEST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CNV_TOTAL Extract from man page : -r Write the current release level of the operating system -v Write the version level of this release of the operating system So that's mean that there are several Release ( as relesase level) and inside each release level there are several version level, am'I understanding well ? The different flags to uname(1) basically select different bits out of the uname data -- so 'uname -a' gives you *all* of the data, 'uname -r' gives you the release level, 'uname -m' gives you the hardware architecture, etc. etc. Note that this command isn't FreeBSD specific -- the behaviour of uname(1) is part of the POSIX.2 specification, which means it will work the same way on any current unixoid OS you care to mention. Of course, different development groups do tend to have slightly different interpretations of exactly what it is POSIX.2 mandates should be printed out in each case. Under FreeBSD, 'uname -v' attempts to give you as unambiguous as possible identification of exactly what kernel/OS setup you have. Since FreeBSD has quite a number of different code branches, and several of those branches are under continuous development, and kernels can be compiled in various different configurations by various different people, it takes quite a complicated string to identify all of that. Other OSes tend to be somewhat more terse, especially those where the development process isn't exposed to the public: for instance Solaris just gives you the OS version number and the relevant patch id (if any) where patching has involved replacing the kernel image. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp9C6ddiRuje.pgp Description: PGP signature
Re: Updating 5.2.1 Release #
On Thu, Jul 29, 2004 at 11:01:34AM -0500, Scott wrote: Ok, I just did as suggested: ( Change this: ( *default release=cvs tag=RELENG_5_2_1_RELEASE ( ( for this ( *default release=cvs tag=RELENG_5_2_1 and ran cvsup again. This time, I successfully and quickly deleted every thing under /usr/src. Ooops. Yes, you would see that effect. There's actually no such tag as RELENG_5_2_1. What you need is RELENG_5_2 Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgpUkUxbmzstA.pgp Description: PGP signature
Re: Updating 5.2.1 Release #
On Thu, Jul 29, 2004 at 10:05:49AM -0500, Scott wrote: So if I set my cvs tag as Ezequiel (thank you) suggested: change: *default release=cvs tag=RELENG_5_2_1_RELEASE to: *default release=cvs tag=RELENG_5_2_1 That will get me the latest patches? No -- that's correct in spirit, but wrong in detail. Use tag=RELENG_5_2 for best results. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgpP4pUoA1A4q.pgp Description: PGP signature
Re: Updating 5.2.1 Release #
So if I set my cvs tag as Ezequiel (thank you) suggested: change: *default release=cvs tag=RELENG_5_2_1_RELEASE to: *default release=cvs tag=RELENG_5_2_1 That will get me the latest patches? I'll make that change and rebuild again today. Thanks all for your help. :) Scott ___ Scott, You'll be much happier if you use: *default release=cvs tag=RELENG_5_2 That will get you what you want. I'm not sure, but I think using the your last proposed tag might just erase your sorces and that's it. Don ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating 5.2.1 Release #
( No -- that's correct in spirit, but wrong ( in detail. Use tag=RELENG_5_2 for best ( results. Ah, that would be what I did wrong then. I've reinstalled, am currently installing cvsup from ports and when that is done I'll try to update again with the correct tag this time. Thanks again to all that have helped. :) Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating 5.2.1 Release #
Matthew Seaman wrote: On Thu, Jul 29, 2004 at 09:37:35AM -0500, Puna Tannehill wrote: Scott wrote: uname -a shows: FreeBSD 5.2.1-Release #0: I was expecting the release (version, revision# ?) number to be greater than #0. I think I've seen where the latest revision is #9 or so? Do I need to tell it to get the latest revision somehow? Do I need to change the cvs tag= to something else to get up to date? I thought the #number indicated the number of times the server has been rebooted based upon the last time the kernel was recompiled. Being that it is #0, it was your first book. Reboot the machine and check the number again. I believe that the #n is the number of times the kernel has been re-compiled since the last time the system was installed. It's probably not a very interesting datum except to kernel hackers who need to do a lot of recompiling. Oh right right. Thank you for the correction. I'm still wiping the sleep from my eyes. Actually, it might be an fun indicator of how many 15-20 minute chunks of time one can never get back. heehee hmm ~sighs and sips coffee~ Puna What the original poster was thinking of is the patchlevel that gets incremented every time a new security (or nowadays: errata) patch is applied to any of the -RELEASE branches. That modifies the OS name (ie. the output of 'uname -r'), so instead of: 5.2.1-RELEASE it says (at the latest count): 5.2.1-RELEASE-p9 See /usr/src/sys/conf/newvers.sh for the file that controls all that. Cheers, Matthew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating 5.2.1 Release #
Scott, I'm sorry the correct tag is *default release=cvs tag=RELENG_5_2 - Original Message - From: Scott [EMAIL PROTECTED] To: Ezequiel [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, July 29, 2004 1:01 PM Subject: Re: Updating 5.2.1 Release # Ok, I just did as suggested: ( Change this: ( *default release=cvs tag=RELENG_5_2_1_RELEASE ( ( for this ( *default release=cvs tag=RELENG_5_2_1 and ran cvsup again. This time, I successfully and quickly deleted every thing under /usr/src. There must be something wrong with my cvs tag. I read the notice in the handbook that says Be very careful to specify any tag= fields correctly. Some tags are valid only for certain collections of files. If you specify an incorrect or misspelled tag, CVSup will delete files which you probably do not want deleted. Here is my supfile that just deleted everything under /usr/src: *default host=cvsup15.us.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_5_2_1 *default delete use-rel-suffix *default compress src-all ports-all tag=. To keep up to date with 5.2.1, is that the correct tag? I'm reinstalling now . . . Thanks, Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating 5.2.1 Release #
( Scott, I'm sorry the correct tag is ( ( *default release=cvs tag=RELENG_5_2 That's ok Ezequiel. No harm done. Fortunately I was upgrading a fresh install so none of my own data was lost. I've learned a lot today. I've put off upgrading because the entire process looked so daunting, but when you break it down into each step, it's not as hard as I thought it would be. :) I just finished the upgrade using the correct cvs tag. It took three hours total, but seems to be up and running fine now. Uname now shows: FreeBSD 5.2.1-RELEASE-p9 Woo Hoo! It worked! Thanks again to everyone for the assistance today. :) Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
