Pulling a patch release using cvsup
I'm trying to figure out how, using cvsup, to pull a specific patch release. For example, FreeBSD 4.11-RELEASE-p14. I've tried using the date of a specific patch from /usr/src/UPDATING but that does not work. Josef -- Josef Grosch | Another day closer to a | FreeBSD 6.1 [EMAIL PROTECTED] | Micro$oft free world | Berkeley, Ca. pgpZNtwb73AfT.pgp Description: PGP signature
Re: Pulling a patch release using cvsup
On 2007-01-05 18:16, Josef Grosch [EMAIL PROTECTED] wrote: I'm trying to figure out how, using cvsup, to pull a specific patch release. For example, FreeBSD 4.11-RELEASE-p14. I've tried using the date of a specific patch from /usr/src/UPDATING but that does not work. Using dates is certainly a possibility, but you have to be a bit careful about the date format. CVSup will accept dates of the format: .mm.dd.HH.MM.SS Where: = year mm = month dd = month day [01..28, 01..30 or 00..31, depending on the month] HH = hours MM = minutes SS = seconds The format is also described in the manpage of cvsup: #date=[cc]yy.mm.dd.hh.mm.ss #This specifies a date that should be used to select the #revisions that are checked out from the CVS repository. The #client will receive the revisions that were in effect at the #specified date and time. # #At present, the date format is inflexible. All 17 or 19 #characters must be specified, exactly as shown. For the years #2000 and beyond, specify the century cc. For earlier years, #specify only the last two digits yy. Dates and times are #considered to be GMT. The default date is `.', which means #``as late as possible''. Thus, you can update to a particular date *within* the RELENG_4 branch, by using both a tag=RELENG_4 and a date=2007.01.05.22.00.00 :) Please note that the dates specified in date=YY.mm.dd.HH.MM.SS format are in UTC, so if you are living in a different timezone, some adjustments may be necessary. - Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GUIDE step-by-step - FreeBSD-RELENG-upgrade + BUILDWORLD process, using CVSUP
On Sunday 18 June 2006 08:00, [EMAIL PROTECTED] wrote: Hanno Krusken wrote: Hi all, specially for the novice of you, please read carefully !! # make clean # make -j4 buildworld # make buildkernel KERNCONF=YOUR-KERNEL-FILE # make installkernel KERNCONF=YOUR-KERNEL-FILE # reboot Hanno Krusken make -j4 can cause many systems to fail The correct procedure is make buildworld make kernel KERNCONF=mykern mergemaster -p make installworld mergemaster regards Jason M Thought I'd throw in my 2cents to the conversation. I have a cheat-sheet I've created myself for this process. Generally, the procedure is as described as above. One issue is that the actual process can vary... there is more than one _correct_ procedure. That being said, it may help a newbie to have _more_ detail than less. Thus, I'll include my cheat sheet here too. Section 21.4 from the handbook should be the final authority ;-) Note, following the procedure isn't difficult at all... what _is_ difficult is answering the questions 'mergemaster' asks correctly. In reality, this usually isn't too difficult either, but can be intimidating for less experienced users. The general rule of thumb for mergemaster is answer 'i' (install temporary version) for any file that you don't remember editing yourself - this usually means press 'd' (delete) when prompted to merge files like /etc/hosts or (possibly) /etc/printcap. On a typically configured machine, you are instructing mergemaster to either install (95%) or delete (4%) the temporary file it's prompting about; the other 1% of the time a 'real' merge is necessary. Ultimately, you need to use your head a bit during mergemaster. Other than that, the only thing you need to understand is how to use cvsup. Enough already, here's my cheat-sheet: UPDATING FREEBSD cvsup standard-supfile #i'm tracking stable cd /usr/src cat UPDATING#glance at it for quirks make buildworld make buildkernel KERNCONF=your_filename make installkernel KERNCONF=your_filename shutdown now#optional; allows you to skip to next 'cd' command reboot #into single user mode fsck -p mount -u / mount -a -t ufs swapon -a adjkerntz -i#if cmos clock set to local time cd /usr/src #using mergemaster: usually just answer 'i' #for every file sans 'hosts', 'printcap' #and any other customized /etc files #use your head mergemaster -p #merges new stuff needed by installworld make installworld mergemaster #merges all new stuff: /etc /var/ usr reboot cd /usr/obj chflags -R noschg * #only if any files are immutable rm -rf *#saves disk space and #makes future updates easier but slower #THIS HAPPENS IN /usr/obj #LOL, BE CAREFUL TO INSURE THIS!!! -- New systems generate new problems. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GUIDE step-by-step - FreeBSD-RELENG-upgrade + BUILDWORLD process, using CVSUP
Hanno Krusken wrote: Hi all, specially for the novice of you, please read carefully !! # make clean # make -j4 buildworld # make buildkernel KERNCONF=YOUR-KERNEL-FILE # make installkernel KERNCONF=YOUR-KERNEL-FILE # reboot Hanno Krusken make -j4 can cause many systems to fail The correct procedure is make buildworld make kernel KERNCONF=mykern mergemaster -p make installworld mergemaster regards Jason M ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
GUIDE step-by-step - FreeBSD-RELENG-upgrade + BUILDWORLD process, using CVSUP
Hi all, specially for the novice of you, please read carefully !! OK, this is a the step-by-step GUIDE to do a FreeBSD-RELENG-upgrade + BUILDWORLD process, using CVSUP I have seen a lot of buildworld questions, and even more tips, on this news-group and now, finally I provide my GUIDE for all FreeBSD-RELENG-X.xx, builds, patches, ports-upgrades, in hope it will be help full for any one who still has problems building the system.. to make a BUILDWORLD as fast, safe and easy as possible using the CVSUP way ! You will find your answer to most of your questions below. NOTE !!! I only pull together and compress all the tips and information's out of news-groups, BSD-handbook, O'Reilly's publications and most my own try-and-error experiences. Even if it seams not quite perfect for some BSD-Gurus, but it happily dose the job for me, highly customised kernel and 520-installed-ports in one go, with out trouble. I used this steps for years now on all FreeBSD-releng-4.8, 4.9, 4.10, 4.11, 5.4, 5.5, 6.0 and on all patch levels. (well 4.x wont's it the old way, but 5.x and 6.x sweeps flawless ahead) Recently upgraded my Laptop from FreeBSD-5.4-p15 to FreeBSD-5.5-p1 and a FreeBSD-6.0 with out any problems, it will work for FreeBSD-6.1 and above as well promised ;o) Usually CVSUP the source, fetch the distfiles and e-mails in a pub with WiFi WLan down the road on my Laptop, have a beer or two, compile, build, install the rest on the way home and over night if needed. No joke, I have no DSL, ISDN or phone at home but it works sweet for me, beer taste better than a phone bill ;o) and keeps my system up-to-date as well. Now to make it even more convenience to fetch it all, using fastest_cvsup for the source is a treat, but to keep it simple in this guide I'll only describe the basic way. (at the end of this mail you'll find a small script to CVSUP with fatetest_cvsup) any way ;o) Over all, a buildworld or upgrade with this guide will only work if your config files are OK before you carry on to follow this guide: !! Make sure the following files are looked over and work sweet you'll run in to a lot of error messages, if not crafted carefully to suit your machine!! you have to tweak this files first, to match your system, before you even can think about calling a buildworld-step out of this guide !!! build a customs kernel first and you get in to it. If your machine boots up with your own kernel, give it a go /etc/make.conf /usr/src/sys/i386/conf/YOUR-KERNEL-FILE /etc/standard-supfile /etc/ports-supfile ### STEP-BY-STEP the stupid way, but easy as that 1+2=3a or 1+2=3b ;o) ### ### 1.) FETCHING SRC-SOURCE BY CVSUP, CLEANING SYSTEM AND RUNNING BUILDWORLD !! ### 2.) BOOT UP IN SINGLE MODE, MERGEMASTER AND INSTALLWORLD !! ### 3-a.) use for: RELEASE-PATCH-UPGRADE + DAILY-PORTS-UPGRADE AND FINISH !! ### 3-b.) or use for: FULL-RELEASE-UPGRADE + FULL-PORTS-UPGRADE AND FINISH !! ### ### BUILDWORLD PROCESS WITH CVSUP: ### guide for system upgrade: ### all action as root or su to root ;o) ###-- ### 1.) FETCHING SRC SOURCE BY CVSUP, CLEANING SYSTEM AND RUNNING BUILDWORLD: # cvsup -g -L 2 /etc/standard-supfile ### (you need to be online for this one to fetch the source) # cd /usr/obj # chflags -R noschg * # rm -rf * # cd /usr/src # make clean # make -j4 buildworld # make buildkernel KERNCONF=YOUR-KERNEL-FILE # make installkernel KERNCONF=YOUR-KERNEL-FILE # reboot ###-- ### 2.) BOOT UP IN SINGLE MODE, MERGEMASTER AND INSTALLWORLD !!! # hit the space-key if boot up delay counter starts !! # boot -s # mount -a # cd /usr/src # mergemaster -p### pre-buildworld mode, only essential files ! # make installworld # cp -Rp /etc /etc.old # mergemaster -cv ### do all changes as needed, take your time and think, redo every step if unsure !!! ... or you can hack the files by hand # reboot ###--- ### 3-a.) use FOR RELEASE-PATCH-UPGRADE, DAILY-PORTS-UPGRADE AND FINISH !! ### BOOT UP IN NORMAL MODE, PORTS UPGRADE AND FINISH !!! ### open a xterm if running in X11 # su # Password: # uname -a # cd /usr/src # make clean # cvsup -g -L 2 /etc/ports-supfile ### (you need to be online for this one to fetch the ports collection) # cd /usr/ports # make fetchindex ### (or make index but takes time) # portupgrade -rRaF ### (you need to be online for this one to fetch the distfiles SKIP THIS STEP IF PERMANENT ONLINE) # portupgrade -rRa ### (you can go offline for this one now) ### RESTART X11 and/or boot !!! FINISHED :o) ###--- ### 3-b.) FOR FULL-RELEASE-UPGRADE, AND FULL-PORTS-UPGRADE AND FINISH !!! ### (AFTER RELEASE UPGRADE) - after FreeBSD upgrade from 5.4 to 5.x, 6.x or newer !! # cvsup -g -L 2 /etc/ports-supfile ### (you need to be online for this one to fetch the ports collection) # cd /usr/ports # make fetchindex ### (or make index but takes time
Re: Using cvsup + make world, and keeping custom patches
patrick [EMAIL PROTECTED] writes: I recently had a need to patch the FreeBSD's jail utility to support multiple IP addresses. On a recent make update using cvsup, my patched versions of the jail files were blown away, and now I'll need to reapply the patches. Does anyone have a good strategy for including some custom patches when doing a make update in /usr/src? Keep a local cvs tree, and keep your patches in that? I think the cvsup documentation has some guidance on how to make that work... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Using cvsup + make world, and keeping custom patches
I recently had a need to patch the FreeBSD's jail utility to support multiple IP addresses. On a recent make update using cvsup, my patched versions of the jail files were blown away, and now I'll need to reapply the patches. Does anyone have a good strategy for including some custom patches when doing a make update in /usr/src? Thanks, Patrick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Updating packages list (using cvsup?)
Hi all, I was wondering about a thingy. Whenever I use sysinstall to add a package, the list seems to be constantly the same (i.e. often outdated), whereas more recent versions should be available of several of the packages. Of course I can manually d/l the packages and if necessary compile them and install them, but I have also heard of the possibility of using cvsup to automatically update the packages tree. Now, I have installed cvsup, and I quickly browsed over the man pages (I have to admit that I have not yet been able to spend much time on this), but I was wondering if this is really the best way to go. Sure, it does automatically update collections, etc., but is this really the handiest tool out there for this particular task? If not, can anyone please name me an alternative (approach)? If it is, OTOH, can anyone please give me some quick pointers for setting this up correctly, and/or point me to a page where this process is explained. Thanks in advance, and cheers! Olafo ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Updating packages list (using cvsup?)
Packages are pre-compiled so there is little ability to configure them, should you need to. Although I still know many people who prefer using packages. Do not use sysinstall to accomplish this. Also, there is no need to 'download or update' your 'packages'. Simply follow the below command to install the current package. # pkg_add -r some_package I would recommend ports and cvs to anyone. Below is a config to install cvsup and run it to update your ports collection. Remember though, ports are not precompiled and you will actually need to move into the /usr/ports/whatever_port/whatever_program dir to install them. # pkg_add -r cvsup-without-gui # cp /usr/share/examples/cvsup/ports-supfile /root/ports-supfile // change 'changethis' to cvsup2, cvsup3, etc. # ee /root/ports-supfile // REBOOT SERVER # shutdown -r now // Run CVsup to make ports current. (will take approx. 1 hour over broadband) # cvsup -g -L 2 /root/ports-supfile Also there is a wealth of information in the FreeBSD handbook and I would consider giving that a read. Best, Thomas S. Crum -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Olaf Greve Sent: Friday, November 26, 2004 8:45 AM To: [EMAIL PROTECTED] Subject: Updating packages list (using cvsup?) Hi all, I was wondering about a thingy. Whenever I use sysinstall to add a package, the list seems to be constantly the same (i.e. often outdated), whereas more recent versions should be available of several of the packages. Of course I can manually d/l the packages and if necessary compile them and install them, but I have also heard of the possibility of using cvsup to automatically update the packages tree. Now, I have installed cvsup, and I quickly browsed over the man pages (I have to admit that I have not yet been able to spend much time on this), but I was wondering if this is really the best way to go. Sure, it does automatically update collections, etc., but is this really the handiest tool out there for this particular task? If not, can anyone please name me an alternative (approach)? If it is, OTOH, can anyone please give me some quick pointers for setting this up correctly, and/or point me to a page where this process is explained. Thanks in advance, and cheers! Olafo ___ [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 packages list (using cvsup?)
Hi Thomas (and others), First off: thanks a lot for your answer, this is indeed what I was looking for... Then some specifics: Packages are pre-compiled so there is little ability to configure them, should you need to. Although I still know many people who prefer using packages. I find them handy at times, but indeed some of them are hopelessly outdated (like Clamd)...:) Do not use sysinstall to accomplish this. Also, there is no need to 'download or update' your 'packages'. Simply follow the below command to install the current package. I know. I didn't express myself correctly: what I meant to say was to update the tree of 'packages', but then, as you stated, what I actually should have been referring to is the tree of 'ports'. :P Below is a config to install cvsup and run it to update your ports collection. Remember though, ports are not precompiled and you will actually need to move into the /usr/ports/whatever_port/whatever_program dir to install them. Yes, that's fine thanks! So the below should do the trick. # pkg_add -r cvsup-without-gui # cp /usr/share/examples/cvsup/ports-supfile /root/ports-supfile // change 'changethis' to cvsup2, cvsup3, etc. # ee /root/ports-supfile // REBOOT SERVER # shutdown -r now // Run CVsup to make ports current. (will take approx. 1 hour over broadband) # cvsup -g -L 2 /root/ports-supfile Cool. Sounds easy enough. So I guess if I were to schedule the 'cvsup -g -L 2 /root/ports-supfile' command using cron, a weekly task should do. Also there is a wealth of information in the FreeBSD handbook and I would consider giving that a read. Thanks, indeed I have printed that (for the 5.1 version, but that should be o.k.) and I shall check that out as well... Cheers! Olafo ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating packages list (using cvsup?)
Thomas S. Crum - AAA Web Solution, Inc. wrote: Packages are pre-compiled so there is little ability to configure them, should you need to. Although I still know many people who prefer using packages. Do not use sysinstall to accomplish this. Also, there is no need to 'download or update' your 'packages'. Simply follow the below command to install the current package. # pkg_add -r some_package I would recommend ports and cvs to anyone. Below is a config to install cvsup and run it to update your ports collection. Remember though, ports are not precompiled and you will actually need to move into the /usr/ports/whatever_port/whatever_program dir to install them. # pkg_add -r cvsup-without-gui # cp /usr/share/examples/cvsup/ports-supfile /root/ports-supfile Or forget about making a copy, and do directly: # cvsup -g -L2 -h cvsup.foo.bar /usr/share/examples/cvsup/ports-supfile Rob. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updating packages list (using cvsup?)
On Friday 26 November 2004 14:22, Olaf Greve wrote: Hi Thomas (and others), First off: thanks a lot for your answer, this is indeed what I was looking for... I should also install portupgrade if I were you, it make managing ports a lot easier. It also has the -P and -PP options (and corresponding per port settings in /usr/local/etc/pkgtools.conf) which are useful for combining ports and packages. For example a full KDE upgrade from ports takes me 3 days, but by allowing portupgrade to install some of the less-important kde components from fully up-to-date packages, I cut that down to one day. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: using cvsup
like someone mentioned, it doesnt matter where you put it. my supfile is in /root, but its just preference. ive noticed you keep mentioning that you wont be using X, and you are thinking you need to deinstall your cvsup or something... you dont have to do that, just use use -g when running cvsup to tell it not to use a gui. for example, cvsup -g -L 2 path/to/supfile Curtis Vaughan wrote: I'm a little confused about using cvsup. I'm referring to 2 resources (The Complete FreeBSD - 4th edition, and www,freebsd.org manual for cvsup). BTW, I currently have FreeBSD 4.8 installed. Ok, so, I know I need to edit a supfile and I have found all the examples. But it seems to me that it is advisable to put my own edited supfile in a particular directory. What is the best or more common practice? Maybe in the base directory: i.e., /usr/local/etc/cvsup/ ? Note that I will not be using the gui. I have not installed X windows (XFree86) as this is to be a server and I no intention of using any gui interface. ___ [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]
using cvsup
I'm a little confused about using cvsup. I'm referring to 2 resources (The Complete FreeBSD - 4th edition, and www,freebsd.org manual for cvsup). BTW, I currently have FreeBSD 4.8 installed. Ok, so, I know I need to edit a supfile and I have found all the examples. But it seems to me that it is advisable to put my own edited supfile in a particular directory. What is the best or more common practice? Maybe in the base directory: i.e., /usr/local/etc/cvsup/ ? Note that I will not be using the gui. I have not installed X windows (XFree86) as this is to be a server and I no intention of using any gui interface. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading to 4.10 using cvsup(Pleeeease! I'm halfway there!!!)
On Thu, Jun 03, 2004 at 11:36:46PM +0200, Henrik W Lund wrote: As Mr. Simon Barner stated, you can save a whole lot of downloading by first installing the 4.9 sources off of the CD-ROM, then cvsupping using the supfile you just made. This will get you only those files that are different between 4.9 and 4.10, and only the bits of them in which the differences lie. If you start out with an empty /usr/src, you'll pull down around 300MB of source code (give or take, depending on what packages you download). If it's already populated by 4.9 sources, you can cut back considerably on this. This is very good advice, and using cvsup regularly to pull down the updates to your copy of the system sources will not unduely tax a 56k modem connection. Ditto for the ports tree. However when using cvsup(1) to take over a collection of sources obtained elsewhere (ie. copied from the installation media) you should be aware of these very useful one-time procedures: http://www.cvsup.org/faq.html#adopt http://www.cvsup.org/faq.html#adoptupgrade Although, obviously you will need to substitute 'RELENG_4_10' or 'RELENG_4_9_0_RELEASE' at appropriate points. 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 pgpudBsnXRwuv.pgp Description: PGP signature
Re: Upgrading to 4.10 using cvsup(Pleeeease! I'm halfway there!!!)
Mark Jayson Alvarez wrote: I'm currently on freebsd 4.9 and wanted to upgrade to 4.10 using cvsup This is my supfile *default host=cvsup1.ph.FReeBSD.org (Philippines... my home) *default base=/usr (...said this is to track down the download status... right?) *default prefix=/usr (...said this is the place where the files will go into my computer... is this correct? Can I use my home directory instead?) *default release=cvs tag=RELENG_4_10 (...said to get FreeBSD4.10 release... am i on the right track?) *default delete use-rel-suffix (no idea about this one... maybe you have?) *default compress (i think this might help... just using 56k modem) Here goes the most mind-boggling part... Which is which? I only want minimum download(56 k modem... remember?)I'm just a typical desktop user and I only need X and KDE... and some fresh manuals for 4.10 I guess. src-base(i think i need this...) src-bin(...and this...) src-contrib src-etc(...and this...) src-games src-gnu src-include src-kerberos5 src-kerberosIV src-lib(...and this...) src-libexec(...and this...) src-release(...and this...) src-sbin(...and this...) src-share(...and not much this...) src-sys(...and more of this...) src-tools src-usrbin(...maybe this...) src-usrsbin(...and also this...) src-crypto(...perhaps not this one...) src-eBones(...sounds like a rap artist..) src-secure(...perhaps in the future...) src-sys-crypto(...perhaps in the future too..) maraming salamat!(...thanks a lot!) mabuhay!(long live!) -jay:) Greetings! That looks fine to me. I'd probably pull down src-include as well, since it's likely to contain lots of header files that you need for your upcoming rebuilding of world. As Mr. Simon Barner stated, you can save a whole lot of downloading by first installing the 4.9 sources off of the CD-ROM, then cvsupping using the supfile you just made. This will get you only those files that are different between 4.9 and 4.10, and only the bits of them in which the differences lie. If you start out with an empty /usr/src, you'll pull down around 300MB of source code (give or take, depending on what packages you download). If it's already populated by 4.9 sources, you can cut back considerably on this. Good luck! -Henrik W Lund ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Help: Upgrading from 4.9 to 4.10 using cvsup
Hi, I'm using freebsd 4.9 and I wanted to upgrade to version 4.10. The first step I made was to select the 'upgrade' in the /stand/sysinstall utility and I've selected only the system binaries(bin) to lessen the amount of files that I have to download. After finishing, I think it didn't work because whenever I boot my system, it says can't load kernel... loading kernel.old... and it still reads freebsd 4.9... Somebody told me here in the mailing list that I should have done the cvsup way of upgrading to 4.10 I have already installed the cvsup16.1h and I can also see some cvsup file examples in my /usr/share/examples directory. The handbook said that I should use the stable-supfile if I wanted to upgrade to the latest stable release.. Questions: In the stable-supfile, I can see these lines... src-all (uncommented by default) #src-base #src-bin #src-contrib #src-etc #src-games #src-gnu #src-include #src-kerberos5 #src-kerberosIV #src-lib #src-libexec #src-release #src-sbin #src-share #src-sys #src-tools #src-usrbin #src-usrsbin If I comment the first line(src-all) which of the following lines should I uncomment out to attain the minimum possible download?(i'm just using a dial-up) And one last thing... The procedure that I've done before using the /stand/sysinstall/-upgrade I don't know really know what happened in my system.. somebody said that after doing that, he thinks that I'm already 80% upgraded.. and the only thing that might be missing in my system is the 4.10 kernel it self. If it is nearly correct, can I just download this kernel and install it instead of doing the whole cvsup download? And if this is possible.. please, I also really wanted to learn how to recompile my whole system using the cvsup... any tips about uncommenting those lines and the proper supfile to use will be very much appreciated.. Thanks a lot -jay __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help: Upgrading from 4.9 to 4.10 using cvsup
Mark Jayson Alvarez wrote: snip The handbook said that I should use the stable-supfile if I wanted to upgrade to the latest stable release.. Indeed. However, if you're looking for the 4.10 RELEASE, edit stable-supfile, find the line that has tag=RELENG_4 and change it to tag=RELENG_4_10. This will get you 4.10-RELEASE with all the latest security patches (as opposed to 4-STABLE). Questions: In the stable-supfile, I can see these lines... src-all (uncommented by default) #src-base #src-bin #src-contrib #src-etc #src-games #src-gnu #src-include #src-kerberos5 #src-kerberosIV #src-lib #src-libexec #src-release #src-sbin #src-share #src-sys #src-tools #src-usrbin #src-usrsbin If I comment the first line(src-all) which of the following lines should I uncomment out to attain the minimum possible download?(i'm just using a dial-up) If you comment out src-all, always, ALWAYS uncomment src-base, regardless of what other packages you uncomment. Otherwise you'll end up with a useless /usr/src. On a sidenote, this goes for the ports and docs as well. Commenting *-all requires uncommenting *-base at the very least. But I digress. For the minimal download that would leave you a useable system, I'd uncomment -base, -bin, -lib, -libexec, -sbin, -sys, -usrbin and -usrsbin, although I admit I may be missing something (or adding too much) here, I'm not entirely sure. And one last thing... The procedure that I've done before using the /stand/sysinstall/-upgrade I don't know really know what happened in my system.. somebody said that after doing that, he thinks that I'm already 80% upgraded.. and the only thing that might be missing in my system is the 4.10 kernel it self. If it is nearly correct, can I just download this kernel and install it instead of doing the whole cvsup download? If this is correct, then uncommenting src-base and src-sys above should suffice. Maybe you need to uncomment src-include as well, I'm not certain. At any rate, this is a much smaller download than the above mentioned, so maybe you should try this first? For rebuilding your kernel, check out the handbook. And if this is possible.. please, I also really wanted to learn how to recompile my whole system using the cvsup... any tips about uncommenting those lines and the proper supfile to use will be very much appreciated.. Fiddle around with the uncommenting (but always leave src-base uncommented) so that you get what you think you need, make sure that the proper settings are set in /etc/make.conf so that you don't try to build anything for which you do not have the sources (check out /etc/defaults/make.conf for clues as to what kind of control you have) and build away. Thanks a lot -jay You're very welcome! -Henrik W Lund ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Upgrading to 4.10 using cvsup(Pleeeease! I'm halfway there!!!)
I'm currently on freebsd 4.9 and wanted to upgrade to 4.10 using cvsup This is my supfile *default host=cvsup1.ph.FReeBSD.org (Philippines... my home) *default base=/usr (...said this is to track down the download status... right?) *default prefix=/usr (...said this is the place where the files will go into my computer... is this correct? Can I use my home directory instead?) *default release=cvs tag=RELENG_4_10 (...said to get FreeBSD4.10 release... am i on the right track?) *default delete use-rel-suffix (no idea about this one... maybe you have?) *default compress (i think this might help... just using 56k modem) Here goes the most mind-boggling part... Which is which? I only want minimum download(56 k modem... remember?)I'm just a typical desktop user and I only need X and KDE... and some fresh manuals for 4.10 I guess. src-base(i think i need this...) src-bin(...and this...) src-contrib src-etc(...and this...) src-games src-gnu src-include src-kerberos5 src-kerberosIV src-lib(...and this...) src-libexec(...and this...) src-release(...and this...) src-sbin(...and this...) src-share(...and not much this...) src-sys(...and more of this...) src-tools src-usrbin(...maybe this...) src-usrsbin(...and also this...) src-crypto(...perhaps not this one...) src-eBones(...sounds like a rap artist..) src-secure(...perhaps in the future...) src-sys-crypto(...perhaps in the future too..) maraming salamat!(...thanks a lot!) mabuhay!(long live!) -jay:) __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading to 4.10 using cvsup(Pleeeease! I'm halfway there!!!)
Mark Jayson Alvarez wrote: I'm currently on freebsd 4.9 and wanted to upgrade to 4.10 using cvsup This is my supfile [...] Hi, do yourself a favor and use a copy of the example supfile /usr/share/examples/cvsup/stable-supfile The only thing you need to change is the `host' line. If you want the security branch (4.10 release + security fixes) for FreeBSD 4.10, you will also need to change RELENG_4 (-stable) into RELENG_4_10. I wouldn't mess with partial fetching of the sources. If you already have the sources from your FreeBSD 4.9 cdrom, updating to 4.10 shouldn't take more than half of an hour using a 56K modem. I'd also give the same advice for ports: Install the from the cdrom first, use the example supfile, and fetch the whole tree -- this will save you a lot of trouble at virtually no expense (I don't now your connection charges, though). Simon signature.asc Description: Digital signature
open-ssh manual recompiled patched using cvsup
Hi, I'm trying to recompile openssh with latest patch on FreeBSD 5.0-RELEASE-p7 i386. I've cvsuped to the new version. So, cd /usr/src/secure/lib/libssh make depend make all install (succesfully done) After: # cd /usr/src/secure/usr.sbin/sshd # make depend make all install I got this error: In file included from /usr/src/crypto/openssh/sshd.c:83: /usr/src/crypto/openssh/auth.h:43:18: krb5.h: No such file or directory In file included from /usr/src/crypto/openssh/auth-rhosts.c:25: /usr/src/crypto/openssh/auth.h:43:18: krb5.h: No such file or directory In file included from /usr/src/crypto/openssh/auth-passwd.c:45: /usr/src/crypto/openssh/auth.h:43:18: krb5.h: No such file or directory In file included from /usr/src/crypto/openssh/auth-rsa.c:33: /usr/src/crypto/openssh/auth.h:43:18: krb5.h: No such file or directory In file included from /usr/src/crypto/openssh/auth-rh-rsa.c:25: /usr/src/crypto/openssh/auth.h:43:18: krb5.h: No such file or directory /usr/src/crypto/openssh/servconf.c:21:18: krb5.h: No such file or directory In file included from /usr/src/crypto/openssh/serverloop.c:51: /usr/src/crypto/openssh/auth.h:43:18: krb5.h: No such file or directory In file included from /usr/src/crypto/openssh/auth.c:45: /usr/src/crypto/openssh/auth.h:43:18: krb5.h: No such file or directory etc., etc. /usr/src/crypto/openssh/auth.h:43:18: krb5.h: No such file or directory /usr/src/crypto/openssh/auth-krb5.c:44:18: krb5.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/secure/usr.sbin/sshd. What should I do? Thank you, Paul JURCO ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
problems with getting through firewall using CVSup
Hello, I'm in despair. I cannot get past firewall to update my sources and ports of FreeBSD. At least it seems to me that this is a firewall problem. I tried to use all options with -P. Nothing happends, every time cvsup writes after quite a long pause, that connection to server refused. It is interesting, that about a week ago I used the same cvsup on the same system (FreeBSD-stable) successfully. Some day something happend (perhaps somebody reconfigured firewall) and nothing is working now. Here is my cvsup file: *default host=cvsup.FreeBSD.org *default prefix=/usr/home/src/CVS/FreeBSD *default base=/usr/home/src/CVS *default release=cvs *default delete compress use-rel-suffix ## Main Source Tree src-all # Other stuff ports-all www doc-all I tried to use different mirrors, nothing helps. Version of cvsup is SNAP_16_1f. -- Igor To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: problems with getting through firewall using CVSup
I've had the same situation here and I couldn't convince our security team to open 5999 for my cvsups. I do have ssh (22tcp) open, and a box at home, on which I setup xinetd to accept connections on localhost:5999 = cvsup7.freebsd.org:5999 added cvsup7.freebsd.org as alias to my localhost in /etc/hosts and tunneled 5999 through ssh between my office_box and my home_box ;) hope this helps, Ed. Quoting Igor Pokrovsky ([EMAIL PROTECTED]): Hello, I'm in despair. I cannot get past firewall to update my sources and ports of FreeBSD. At least it seems to me that this is a firewall problem. I tried to use all options with -P. Nothing happends, every time cvsup writes after quite a long pause, that connection to server refused. It is interesting, that about a week ago I used the same cvsup on the same system (FreeBSD-stable) successfully. Some day something happend (perhaps somebody reconfigured firewall) and nothing is working now. Here is my cvsup file: *default host=cvsup.FreeBSD.org *default prefix=/usr/home/src/CVS/FreeBSD *default base=/usr/home/src/CVS *default release=cvs *default delete compress use-rel-suffix ## Main Source Tree src-all # Other stuff ports-all www doc-all I tried to use different mirrors, nothing helps. Version of cvsup is SNAP_16_1f. -- Igor To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Edmond Baroud UNIX Systems Admin mailto:[EMAIL PROTECTED] Fingerprint 140F 5FD5 3FDD 45D9 226D 9602 8C3D EAFB 4E19 BEF9 UNIX is very user friendly, it's just picky about who its friends are. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: problems with getting through firewall using CVSup
or u can change ur cvsupfile's host to *default host=localhost of course :) Ed. Quoting Edmond Baroud ([EMAIL PROTECTED]): I've had the same situation here and I couldn't convince our security team to open 5999 for my cvsups. I do have ssh (22tcp) open, and a box at home, on which I setup xinetd to accept connections on localhost:5999 = cvsup7.freebsd.org:5999 added cvsup7.freebsd.org as alias to my localhost in /etc/hosts and tunneled 5999 through ssh between my office_box and my home_box ;) hope this helps, Ed. Quoting Igor Pokrovsky ([EMAIL PROTECTED]): Hello, I'm in despair. I cannot get past firewall to update my sources and ports of FreeBSD. At least it seems to me that this is a firewall problem. I tried to use all options with -P. Nothing happends, every time cvsup writes after quite a long pause, that connection to server refused. It is interesting, that about a week ago I used the same cvsup on the same system (FreeBSD-stable) successfully. Some day something happend (perhaps somebody reconfigured firewall) and nothing is working now. Here is my cvsup file: *default host=cvsup.FreeBSD.org *default prefix=/usr/home/src/CVS/FreeBSD *default base=/usr/home/src/CVS *default release=cvs *default delete compress use-rel-suffix ## Main Source Tree src-all # Other stuff ports-all www doc-all I tried to use different mirrors, nothing helps. Version of cvsup is SNAP_16_1f. -- Igor To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Edmond Baroud UNIX Systems Admin mailto:[EMAIL PROTECTED] Fingerprint 140F 5FD5 3FDD 45D9 226D 9602 8C3D EAFB 4E19 BEF9 UNIX is very user friendly, it's just picky about who its friends are. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Edmond Baroud UNIX Systems Admin mailto:[EMAIL PROTECTED] Fingerprint 140F 5FD5 3FDD 45D9 226D 9602 8C3D EAFB 4E19 BEF9 UNIX is very user friendly, it's just picky about who its friends are. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Using cvsup with multiple servers
On Wed, Feb 12, 2003 at 11:58:37AM -1000, Gary Dunn wrote: What is the best way to use cvsup in a multi-server environment? I have four servers. None are exactly the same. The only thing they have in common is that they use a Pentium CPU. Three (A B C) are production servers with lots of real user accounts and data. The forth is my test and configuration management (CM) system. Currently what I do is run cvsup from the CM machine, then push out the updates with rsync. Each system has its own ports collection. Each port is built on the machine it will run on. I thought it would be simpler if I use NFS to mount the ports collection on each of the production systems, maintaining just one copy on the CM machine. Then I would build each port on the machine it will run on. My concern is for how a build on server A will affect a build on server B. Will a make clean be enough? I do something very similar without problems. Works well. Another approach might be to build the ports on your management box, and make them into binary packages which you can then install on the production machines - it's much quicker to do, so will save valuable cycles which can then be (ab)used by your users. I have heard that there are tools for managing the ports collection. Are there any that would make my life easier? portupgrade is in sysutils in the ports, and is very good. BTW, I am in Hawaii, and it's a beautiful, sunny day, temp around 80F. I guess it's pretty cold today for most of you. Thanks, glad to hear you're having a nice day. Here in southern Lincolnshire, England, we have unbroken low level cloud as far as the eye can see, and a whole 2 degrees heat. -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: 3D73 AF47 D448 C5CA 88B4 0DCF 849C 1C33 3C48 2CDC _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Using cvsup with multiple servers
What is the best way to use cvsup in a multi-server environment? I have four servers. None are exactly the same. The only thing they have in common is that they use a Pentium CPU. Three (A B C) are production servers with lots of real user accounts and data. The forth is my test and configuration management (CM) system. Currently what I do is run cvsup from the CM machine, then push out the updates with rsync. Each system has its own ports collection. Each port is built on the machine it will run on. I thought it would be simpler if I use NFS to mount the ports collection on each of the production systems, maintaining just one copy on the CM machine. Then I would build each port on the machine it will run on. My concern is for how a build on server A will affect a build on server B. Will a make clean be enough? I have heard that there are tools for managing the ports collection. Are there any that would make my life easier? BTW, I am in Hawaii, and it's a beautiful, sunny day, temp around 80F. I guess it's pretty cold today for most of you. -- _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ Gary Dunn _/ _/ Open Slate Project _/ _/ http://openslate.sourceforge.net/ _/ _/ http://www.aloha.com/~knowtree/_/ _/ Honolulu _/ _/ registered Linux user #273809 _/ _/ _/ _/ This tagline is umop apisdn. _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Using cvsup with multiple servers
Gary Dunn wrote: What is the best way to use cvsup in a multi-server environment? I have four servers. None are exactly the same. The only thing they have in common is that they use a Pentium CPU. Three (A B C) are production servers with lots of real user accounts and data. The forth is my test and configuration management (CM) system. Currently what I do is run cvsup from the CM machine, then push out the updates with rsync. Each system has its own ports collection. Each port is built on the machine it will run on. I thought it would be simpler if I use NFS to mount the ports collection on each of the production systems, maintaining just one copy on the CM machine. Then I would build each port on the machine it will run on. My concern is for how a build on server A will affect a build on server B. Will a make clean be enough? Real world experience: I have anywhere between 3 and 6 FreeBSD machines here at any point in time. I keep 1 that is cvsupped nightly (via cron) and I mount both the ports directory and the /usr/src directory off that machine when I want to install a port or upgrade my sources. It seems to work very nicely for the most part. Each machine has its own /etc/make.conf so those values aren't shared. Another advantage is that the sources are all on the one machine and don't need transferred if I install on different machines. The only problem I've had is that sometimes the ports seem to get confused as to whether or not a machine already has the port installed. For example, I install the port on machine A and when it's done, do a 'make clean', but when I go to install the port on machine B, it seems to think it's already there. I've found that issuing 'make deinstall' on machine B generates a lot of complaints, but a 'make install' then works, so it's not a big deal. Keeping the FreeBSD sources up to date is even easier, I just keep /usr/obj on the local machine and /usr/src mounts via NFS. Since I always wipe /usr/obj before building, I've never had any problem. It makes it rather nice, since all my kernel config files are in one place. I have heard that there are tools for managing the ports collection. Are there any that would make my life easier? Not sure what tools would help in your particular situation. BTW, I am in Hawaii, and it's a beautiful, sunny day, temp around 80F. I guess it's pretty cold today for most of you. You're cruel and evil. I hope your ice cream melts. It's 17 degrees here and with the 25-50 mph wind chill, it feels like 5 below. There are snow drifts multiple feet deep in places and the roads are dangerous and the road crews are reporting that they'll be out of salt by this weekend, so things are going to get worse. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Idea: using CVSUP to mirror websites accross multiple servers... opinions?
I was just thinking of a way to effectively mirror content accross multiple webservers in a load-sharing environment. The webservers are accessed through a single caching machine running in http-acceleration mode. Some sites must run mod_perl and access MySQL databases; these servers do not serve any static content, but are called from the same urls as the static content is, (using re-directs on the cachine machine based on the filename called for eg *.pl). The images, and static pages however must be serviced from any one of many possible webservers, thus creating a redundant environment which can easily adapt to load balance. The problem now of course being the replication of the data held on the multiple servers. I was figuring on keeping a single FTP server for the master copy and then replicating the data accross multiple machines. I'd rather copy than use NFS; so there would not be a single point of failure, (eg: a drive on the ftp server croakes). I was thinking of using rsync; but from the way I understand it rsync just re-downloads the entire tree? Could I not use CVSUP to accomplish the replication of the data? As-in un a CVS server from the FTP server machine, and have the webservers sync the trees they need? Any issues with using CVS and image files? Or binaries alltogether? Any ideas or suggestions for a better method for data replication and synchronization? -- Nathan Vidican [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
