Re: Very Beginning CVSup Questions
Thanks to everyone for the help! - Jonathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Very Beginning CVSup Questions
I'm a beginner with FreeBSD and somewhat intermediate with Unix-like operating systems in general, so please bear the nature of my questions. I have some questions about CVSup that seem unclear from the handbook. Right now I'm sticking with RELENG_7_0; I intend to track -STABLE once I get the hang of CVSup, make buildworld, etc. I understand that the supfile contains the list of *default settings (*default tag=RELENG_7_0 etc.) followed by the list of collections. The Using CVSup page suggests simply using the src-all collection. I understand that when tracking -STABLE I want to update the ports collection before running make buildworld; is the ports collection included in the base source tree (i.e. does src-all imply ports-all) or should ports-all be included as a separate line beneath src-all? The Using the Ports Collection page in the handbook says to make sure /usr/ports is empty before running csup because otherwise csup will not prune removed patch files. Isn't this what the delete in the supfile (as in the line *default release=cvs delete use-rel-suffix compress) is for? Do I have to clean /usr/ports every time I run csup or just the first time? If I don't care about encrypted transmission or HTTP vs. CVS protocols, are there any compelling reasons to use portsnap instead of CVSup/csup? Thank you very much for your help. - Jonathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Very Beginning CVSup Questions
On Mon, 21 Jul 2008 20:08:37 -0400 J.C. [EMAIL PROTECTED] wrote: I'm a beginner with FreeBSD and somewhat intermediate with Unix-like operating systems in general, so please bear the nature of my questions. I have some questions about CVSup that seem unclear from the handbook. Right now I'm sticking with RELENG_7_0; I intend to track -STABLE once I get the hang of CVSup, make buildworld, etc. You need to understand CVSup, make buildworld, to track RELENG_7_0 (and successors) too, are you sure you want to track a development branch? I understand that the supfile contains the list of *default settings (*default tag=RELENG_7_0 etc.) followed by the list of collections. The Using CVSup page suggests simply using the src-all collection. I understand that when tracking -STABLE I want to update the ports collection before running make buildworld; is the ports collection included in the base source tree (i.e. does src-all imply ports-all) No or should ports-all be included as a separate line beneath src-all? You can do that, but I think most people use separate files, so they can be updated independently. There are multiple sample files for this reason. The Using the Ports Collection page in the handbook says to make sure /usr/ports is empty before running csup because otherwise csup will not prune removed patch files. Isn't this what the delete in the supfile (as in the line *default release=cvs delete use-rel-suffix compress) is for? It's a bit subtle, csup has to establish a baseline in its metadata for it to be fully confident about which files it can delete, this can be done starting with an empty or fully syncronized tree. There's also a separate issue that it never deletes files which have never been under CVS. Do I have to clean /usr/ports every time I run csup or just the first time? Just the first. If I don't care about encrypted transmission or HTTP vs. CVS protocols, are there any compelling reasons to use portsnap instead of CVSup/csup? portsnap is much faster. And since the fetch part doesn't affect the ports tree it can be done safely from a crontab, which speeds things up even more. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Very Beginning CVSup Questions
On Mon, 21 Jul 2008 20:08:37 -0400, J.C. [EMAIL PROTECTED] wrote: I'm a beginner with FreeBSD and somewhat intermediate with Unix-like operating systems in general, so please bear the nature of my questions. I have some questions about CVSup that seem unclear from the handbook. Right now I'm sticking with RELENG_7_0; I intend to track -STABLE once I get the hang of CVSup, make buildworld, etc. I understand that the supfile contains the list of *default settings (*default tag=RELENG_7_0 etc.) followed by the list of collections. The Using CVSup page suggests simply using the src-all collection. I understand that when tracking -STABLE I want to update the ports collection before running make buildworld; Not necessarily. If you are tracking a -STABLE branch, the rule is that ports compiled on earlier builds should work in later builds. There are very few exceptions that may require a rebuild of ports, but the FreeBSD team tries to avoid those if at all possible. is the ports collection included in the base source tree (i.e. does src-all imply ports-all) or should ports-all be included as a separate line beneath src-all? It's probably a good idea to use a separate `supfile' for src/ and ports/. There are a few tiny but important differences between the base system (the src-all collection) and the ports. One of the differences is that the base system is branched. This means that the branch name RELENG_7 carries an important and well defined meaning for src-all. There are no branches in ports, on the other hand. A consequence of this is that using the same supfile with the option *default tag=RELENG_7_0 may do moderately surprising to your ports tree, like deleting it altogether. When CVSup fails to find a particular collection in the tag/branch you asked, and the supfile has enabled the *default delete use-rel-suffix option too, it _deletes_ the files that don't exist on the requested tag/branch. To avoid surprises like these, you can use two supfiles: one for the src-all collection, and one for the ports-all collection. The Using the Ports Collection page in the handbook says to make sure /usr/ports is empty before running csup because otherwise csup will not prune removed patch files. Isn't this what the delete in the supfile (as in the line *default release=cvs delete use-rel-suffix compress) is for? Do I have to clean /usr/ports every time I run csup or just the first time? Probably not. It's been a while that I haven't used CVSup for ports/, so someone with more recent experience should answer this. If I don't care about encrypted transmission or HTTP vs. CVS protocols, are there any compelling reasons to use portsnap instead of CVSup/csup? Speed. Portsnap doesn't have to worry about tags, branches, and CVS file revisions in the common case, so it can usually finish before CVSup has even finished uploading the current file versions. I just updated my /usr/ports tree with portsnap, and it took all of 50 seconds to fetch and apply 169 patches: | [EMAIL PROTECTED]:/root# \time portsnap fetch update | Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found. | Fetching snapshot tag from portsnap1.FreeBSD.org... done. | Fetching snapshot metadata... done. | Updating from Sat Jul 19 18:10:14 EEST 2008 to Tue Jul 22 03:17:39 EEST 2008. | Fetching 3 metadata patches.. done. | Applying metadata patches... done. | Fetching 0 metadata files... done. | Fetching 169 patches.102030405060708090100110120130140150160 done. | Applying patches... done. | Fetching 22 new ports or files... done. | Removing old files and directories... done. | Extracting new files: | [lots of file paths snipped] | /usr/ports/x11/xloadimage/ | Building new INDEX files... done. |68.64 real12.99 user24.40 sys | [EMAIL PROTECTED]:/root# That's fast enough for me :-) Having said that, there are compelling reasons to use CVSup for ports if you are a developer who wants to make local patches for some of the ports, or if you are maintaining a large number of ports. In this case, having a local CVS mirror of the ports, and checking out from CVS may be useful, because you can see the history of the ports, browse through patches committed, look at port changelogs, or even maintain a locally patched /usr/ports tree in semi-offline mode. That mode of updating is useful too. It all depends on what you are planning to do with your /usr/ports tree. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Very Beginning CVSup Questions
On Tue, 22 Jul 2008 05:08:03 +0300 Giorgos Keramidas [EMAIL PROTECTED] wrote: On Mon, 21 Jul 2008 20:08:37 -0400, J.C. [EMAIL PROTECTED] wrote: The Using the Ports Collection page in the handbook says to make sure /usr/ports is empty before running csup because otherwise csup will not prune removed patch files. Isn't this what the delete in the supfile (as in the line *default release=cvs delete use-rel-suffix compress) is for? Do I have to clean /usr/ports every time I run csup or just the first time? Probably not. It's been a while that I haven't used CVSup for ports/, so someone with more recent experience should answer this. The issue isn't specific to ports. The same thing can happen with the base system too when you adopt an existing tree that's older than the CVS version. Deletions made in CVS between the two points on the branch don't get made locally, because they rely on the relevant csup list file. To be safe you either start from an empty tree, or do an intermediate sync to the point on the branch that matches the local copy. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
CVSup questions
When 5.3 RELEASE first came out, I used the miniinst.iso CD to install 5.3 on a spare computer for tests. It installed ok and based on how it worked, I updated my primary computer. Now I have an application for the spare computer, and I thought I would use it to verify my understanding of how CVSup works. I installed cvsup-without-gui. pkg_info shows cvsup installed. pkg_version, however, failed. Unable to open INDEX in pkg_do I found that pkg_version http://www.FreeBSD.org/ports/INDEX-5 ran ok, so the problem was the missing /usr/ports/INDEX-5. In fact there was no /usr/ports directory. I built src-all and ports-all. Now, there is a /usr/ports directory and and lots of directories and files therein. In /usr/ports, I did make fetchindex. It failed. The /usr/ports/Makeindex file was really Makeindex,v. I copied it as Makeindex, and tried make fetchindex again. It showed many errors, finally fatal errors encountered -- cannot continue. Obviously I need to start over, this time using the CD with the full iso image. I'll do that, but What did I do wrong? And, What is the significance of the ,v (comma, v) tacked on to several of the files in /usr/ports when the files were placed there by CVSup? Jay O'Brien Rio Linda, California, USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CVSup questions
Jay O'Brien wrote: pkg_version, however, failed. Unable to open INDEX in pkg_do I found that pkg_version http://www.FreeBSD.org/ports/INDEX-5 ran ok, so the problem was the missing /usr/ports/INDEX-5. In fact there was no /usr/ports directory. This is because you didn't install the ports collection. IT is recommended either to download the port tarred port collection from the FTP or use cvsup to get the ports collection. I built src-all and ports-all. Now, there is a /usr/ports directory and and lots of directories and files therein. In /usr/ports, I did make fetchindex. It failed. The /usr/ports/Makeindex file was really Makeindex,v. I copied it as Makeindex, and tried make fetchindex again. It showed many errors, finally fatal errors encountered -- cannot continue. You probably used CVS instead of cvsup. CVS, also known as Concurrent Version System is a mechanism which allows developers to manage codebase on which more than one individual is working simultaneously. When some change is made to a file foo.bar managed by a CVS, a file called foo.bar,v is created by the CVS. This file contains all the information about what changed and who changed it along with the comments which a developer might have provided during updating the file foo.bar. Just to add, using the foo.bar,v file along with foo.bar, any version of the file may be created that ever existed. Obviously I need to start over, this time using the CD with the full iso image. I'll do that, but Well, its not always feasible to get hold of the full CD and also its most of the times not required. I generally use either the bootonly CD or the floppies to get a box on the network and pull off everything required over the network. However it is implied that you have a descent connection or you should arrange for some coffee while you install. :-) Best of Luck and welcome to the wonderful world where most of the things are free :-) Best Regards, S. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CVSup questions
Subhro wrote: Jay O'Brien wrote: /snip/ I built src-all and ports-all. Now, there is a /usr/ports directory and and lots of directories and files therein. In /usr/ports, I did make fetchindex. It failed. The /usr/ports/Makeindex file was really Makeindex,v. I copied it as Makeindex, and tried make fetchindex again. It showed many errors, finally fatal errors encountered -- cannot continue. You probably used CVS instead of cvsup. CVS, also known as Concurrent Version System is a mechanism which allows developers to manage codebase on which more than one individual is working simultaneously. When some change is made to a file foo.bar managed by a CVS, a file called foo.bar,v is created by the CVS. This file contains all the information about what changed and who changed it along with the comments which a developer might have provided during updating the file foo.bar. Just to add, using the foo.bar,v file along with foo.bar, any version of the file may be created that ever existed. No, I used cvsup. However, I was idly reading through all of the CVSup FAQ, and I found my problem. It explained that my supfile didn't have tag=. and I knew that it did. Sure enough, a typo. I used a - instead of an =. It read tag-.. Now, with it correct, pkg_version works. And now I understand the ,v indicates RCS files. /snip/ Best of Luck and welcome to the wonderful world where most of the things are free :-) Thank you very much, I really appreciate your quick and thoughtful answer. Jay Best Regards, S. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CVSup questions
Kevin, Stheg; Wow. You answered questions I didn't know how to ask. I was confused between src-all and cvs-all. The confusion is because of the example supfile /usr/share/examples/cvsup/cvs-supfile. It calls for the src- all collection, which I mistakenly thought would get everything. Now I see that it also individually calls for ports-all, doc-all and others. Obviously I didn't read that file carefully enough. I now have read the stable and standard supfiles and understand the reasons for them all. And, I now know to put them somewhere that they won't be eaten by an upgrade if I edit them. I also now see the need for different tags; I'll use RELENG_5_3 and . Thanks for the lead to script. Another useful new command to me. I hadn't seen Dru Lavigne's article on portupgrade. Good read. And this wasn't well documented with me (yet), but it is now: the well documented make buildworld, make buildkernel, make installkernel, reboot single user, mergemaster -p, make installworld, reboot, mergemaster cycle I haven't had so much fun since CP/M (on 8 floppy disks)! Jay O'Brien Rio Linda, California, USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CVSup questions
On 2004-11-23 19:58, Jay O'Brien [EMAIL PROTECTED] wrote: I'm attempting to follow Using CVSup and learn how CVSup works. See: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html Questions about CVSup: 1. Where should I place supfile? Practically, anywhere you want. I keep mine in `/etc/supfile'. The rationale behind the choise of /etc as the directory to save the supfile is that I consider the supfile a part of the system's setup and configuration options. These usually live under /etc. QED Obviously I could put it anywhere and make it work, but is there a usual place for it? I can't find where the manual makes a suggestion. The manual makes no suggestion. A supfile is a simple text file that you can put anywhere you want. In `/root/supfile', `/etc/mysupfile', `/opt/cvsup/freebsd/current/supfile/src.sup' or whatever. The CVSup program doesn't care much about the _path_ of the supfile, as long as it is readable. Do I have a need for more than one supfile? That depends on what you want to update. If you want to update many different collections of files (i.e. the ports, the src tree, the sources of the documentation, etc.), you may find it easier to create one supfile for each collection of files being updated. It's less of an administrative PITA this way. 2. I am running 5.3 RELEASE. It appears that if I specify *default tag=. that I will be getting updates from current. Correct. Is this what I should do, given that I want to stay current on security and bug fixes, but I don't (at this time) intend to get involved with beta testing? No. See the Handbook section ``FreeBSD-CURRENT vs. FreeBSD-STABLE'' at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html for details. Or should I specify *default tag=RELENG_5_3? Yes. This would pull in only the 5.3-RELEASE sources and any security fixes or other updates that are deemed critical enough for backporting to the `security branch' of 5.3-RELEASE (the RELENG_5_3 branch). And, if I do that, will the ports be updated, including adding new ports? No. The Ports do not have security branches. There is only one ports/ tree. 3. The tutorial at http://www.us-webmasters.com/FreeBSD/Install/ after item 68 describes CVSup. It suggests using the supfile /usr/share/examples/cvsup/ports-supfile which gets the ports-all collection. However, the Using CVSup manual says to get src-all, that includes ports-all. Is there some reason to use ports-all, not src-all as suggested by the handbook? Each collection pulls in a different set of files. The ports-all collection updates the files of the Ports collection, usually located under `/usr/ports'. The src-all collection updates `/usr/src', where the base-system sources live. 4. The tutorial (see 3 above) item 97 concludes, after running cvsup, FreeBSD is installed, CONGRATULATIONS! Poor wording. It should probably say ``If you reached this point and everything has worked correctly so far, congratulations! Your source trees have been updated. You may now proceed by building the system from source as described in `_Rebuilding world_'.'' Isn't this a bit premature? It seems to me that at that point I need to rebuild world per http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/book.html#MAKEWORLD to apply the new files and bring the system up to date. Am I missing something? Correct. - Giorgos ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
CVSup questions
I have a system that right now I'm using to learn FreeBSD. I want to go through the update process that I assume I'll have to follow regularly once the computer is up and running as a web and mail server. Right now I'm not concerned about backups; that's my next project. I'm attempting to follow Using CVSup and learn how CVSup works. See: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html Questions about CVSup: 1. Where should I place supfile? Obviously I could put it anywhere and make it work, but is there a usual place for it? I can't find where the manual makes a suggestion. Do I have a need for more than one supfile? 2. I am running 5.3 RELEASE. It appears that if I specify *default tag=. that I will be getting updates from current. Is this what I should do, given that I want to stay current on security and bug fixes, but I don't (at this time) intend to get involved with beta testing? Or should I specify *default tag=RELENG_5_3? And, if I do that, will the ports be updated, including adding new ports? 3. The tutorial at http://www.us-webmasters.com/FreeBSD/Install/ after item 68 describes CVSup. It suggests using the supfile /usr/share/examples/cvsup/ports-supfile which gets the ports-all collection. However, the Using CVSup manual says to get src-all, that includes ports-all. Is there some reason to use ports-all, not src-all as suggested by the handbook? 4. The tutorial (see 3 above) item 97 concludes, after running cvsup, FreeBSD is installed, CONGRATULATIONS! Isn't this a bit premature? It seems to me that at that point I need to rebuild world per http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/book.html#MAKEWORLD to apply the new files and bring the system up to date. Am I missing something? Jay O'Brien Rio Linda, California, USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CVSup questions
Jay O'Brien wrote: I have a system that right now I'm using to learn FreeBSD. I want to go through the update process that I assume I'll have to follow regularly once the computer is up and running as a web and mail server. Right now I'm not concerned about backups; that's my next project. I'm attempting to follow Using CVSup and learn how CVSup works. See: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html Questions about CVSup: 1. Where should I place supfile? Obviously I could put it anywhere and make it work, but is there a usual place for it? I can't find where the manual makes a suggestion. Do I have a need for more than one supfile? Place it whereever is convenient. I'm probably weird, but after I edit mine I stick 'em right in the root. Then it's just # cvsup /stable-supfile You can edit them directly in place (/usr/share/examples/cvsup), but then your changes would be overwritten if you reinstall world (for example, during the upgrade procedure ;-) I guess you could put 'em in your $HOME dir, too, with similar results to above --- cvsup ~/stable-supfile, for example. As for needing more than one supfile, the real answer is no, but with the quid pro quo not if you know what you're doing. If you're just getting started, I'd simply use the ones in /usr/share/examples/cvsup (all the appropriate ones) for stable, ports, and, if desired, doc. 2. I am running 5.3 RELEASE. It appears that if I specify *default tag=. that I will be getting updates from current. Is this what I should do, given that I want to stay current on security and bug fixes, but I don't (at this time) intend to get involved with beta testing? Or should I specify *default tag=RELENG_5_3? And, if I do that, will the ports be updated, including adding new ports? If you use only one supfile, you'll need to have two tags, one for src, and one for ports and/or docs. You probably want RELENG_5 or RELENG_5_3, depending on how conservative you want to be, in your -stable (src) supfile. In the ports supfile, you want . (the dot - HEAD/ CURRENT), because why would you want outdated ports or documentation? 3. The tutorial at http://www.us-webmasters.com/FreeBSD/Install/ after item 68 describes CVSup. It suggests using the supfile /usr/share/examples/cvsup/ports-supfile which gets the ports-all collection. However, the Using CVSup manual says to get src-all, that includes ports-all. Is there some reason to use ports-all, not src-all as suggested by the handbook? I'm not too familiar with the document you describe. I think that guy reads this list sometimes, but it's his site, not the official documentation. I've not read it, and can't comment on its quality or accuracy. The handbook should tell you what you need to know (if it doesn't, you can contact the doc team at [EMAIL PROTECTED]). src-all updates the base system; ports-all updates the ports tree. doc-all would update /usr/doc (assuming you're using default locations). So, it depends on what you're desiring to update at the time. I have been tracking -STABLE while it was 4.X, until 5.2 came out. I use the stable-supfile for that, set to RELENG_4. I guess I'll probably start cvsupping to RELENG_5 on my new 5.X boxes. After this, it's the well documented make buildworld, make buildkernel, make installkernel, reboot single user, mergemaster -p, make installworld, reboot, mergemaster cycle to update your installation of FreeBSD. To update your ports, cvsup with the ports-supfile and then run portupgrade (which itself is a port). Dru Lavigne has a good article on that one here: http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html 4. The tutorial (see 3 above) item 97 concludes, after running cvsup, FreeBSD is installed, CONGRATULATIONS! Isn't this a bit premature? It seems to me that at that point I need to rebuild world per http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/book.html#MAKEWORLD to apply the new files and bring the system up to date. Am I missing something? Jay O'Brien Rio Linda, California, USA HTH, Kevin Kinsey ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CVSup questions
it was said: I have a system that right now I'm using to learn FreeBSD. I want to go through the update process that I assume I'll have to follow regularly once the computer is up and running as a web and mail server. Right now I'm not concerned about backups; that's my next project. I'm attempting to follow Using CVSup and learn how CVSup works. See: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html Questions about CVSup: 1. Where should I place supfile? Obviously I could put it anywhere and make it work, but is there a usual place for it? I can't find where the manual makes a suggestion. Do I have a need for more than one supfile? See http://www.cvsup.org/faq.html 2. I am running 5.3 RELEASE. It appears that if I specify *default tag=. that I will be getting updates from current. Is this what I should do, given that I want to stay current on security and bug fixes, but I don't (at this time) intend to get involved with beta testing? Or should I specify *default tag=RELENG_5_3? And, if I do that, will the ports be updated, including adding new ports? The current current is 6.0, not 5.3, so when updating src use tag=RELENG_5_3. *See #11 on the FAQ above for an important exception to this. 3. The tutorial at http://www.us-webmasters.com/FreeBSD/Install/ after item 68 describes CVSup. It suggests using the supfile /usr/share/examples/cvsup/ports-supfile which gets the ports-all collection. However, the Using CVSup manual says to get src-all, that includes ports-all. Is there some reason to use ports-all, not src-all as suggested by the handbook? You can use one or two sup files. If you use one for both, you need two different tag= declarations, one for src (tag=RELENG_5_3) and one for everything else (tag=.). Ports, docs, etc. don't have RELENG versions, so if you try to use tag=RELENG_5_3, you will wipe out your ports, doc, etc., trees. 4. The tutorial (see 3 above) item 97 concludes, after running cvsup, FreeBSD is installed, CONGRATULATIONS! Isn't this a bit premature? It seems to me that at that point I need to rebuild world per http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/book.html#MAKEWORLD to apply the new files and bring the system up to date. Am I missing something? I don't think premature is the right word. Clearly, FBSD is installed _already_. You are updating it. But, at this point, you aren't finished. You need to do the world/kernel/portupgrade stuff. Then it's CONGRATULATIONS!, assuming something doesn't blow up during any of the various procedures. As an extra word of advice, you may want to run the script command at each step to record the vast amount of messages that fly by. If anything goes wrong, you'll have a complete log; and if nothing goes wrong, you can grep thru them to see the many config options you didn't know about and the wonderful, worrisome warning messages that you won't be sure you can safely ignore or not! HTH Stheg __ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Stupid cvsup questions
Hi, I have 2 identical (copy/paste) ports-supfiles on two machines: it# grep -v '#' /etc/ports-supfile *default host=cvsup.ro.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress ports-all one is produceing : Updating collection ports-all/cvs Edit ports/audio/abcmidi/Makefile Edit ports/audio/abcmidi/distinfo ... The other: Updating collection ports-all/cvs Edit ports/mail/perdition/pkg-plist Edit ports/math/R-letter/Makefile SetAttrs ports/math/p5-Statistics-Distributions/Makefile,v SetAttrs ports/math/p5-Statistics-Distributions/distinfo,v ... I run it like: # cvsup -g /etc/ports-supfile on both machines. The stupid question: why on the second I have the `,v' suffix ? Is there an env variable or something ? -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Stupid cvsup questions
At 11:41 PM +0200 12/15/03, Ion-Mihai Tetcu wrote: Hi, I have 2 identical (copy/paste) ports-supfiles on two machines: it# grep -v '#' /etc/ports-supfile *default host=cvsup.ro.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress ports-all I run it like: # cvsup -g /etc/ports-supfile on both machines. The stupid question: why on the second I have the `,v' suffix ? Is there an env variable or something ? I don't think so. Did you try copying the file from one machine to the other, and doing a direct diff? It looks like the 'tag=.' is being ignored for some reason. I suspect you have tried that, but it's hard to imagine why the two machines would be different. I'd also note that your grep command shouldn't ignore lines that have a '#' that is anywhere in the line. Only ignore lines where there is nothing interesting before the '#'. Eg: grep -v '^ *#' I don't know what else to suggest. From what you describe in your message, both hosts should be getting the same set of files. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Stupid cvsup questions
On Mon, 15 Dec 2003 21:34:55 -0500 Garance A Drosihn [EMAIL PROTECTED] wrote: At 11:41 PM +0200 12/15/03, Ion-Mihai Tetcu wrote: Hi, I have 2 identical (copy/paste) ports-supfiles on two machines: it# grep -v '#' /etc/ports-supfile *default host=cvsup.ro.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress ports-all I run it like: # cvsup -g /etc/ports-supfile on both machines. The stupid question: why on the second I have the `,v' suffix ? Is there an env variable or something ? I don't think so. Did you try copying the file from one machine to the other, and doing a direct diff? Copy /paste in ssh. It looks like the 'tag=.' is being ignored for some reason. I suspect you have tried that, but it's hard to imagine why the two machines would be different. One is 4.7 the other 5.1 but cvsup versions are the same. I'd also note that your grep command shouldn't ignore lines that have a '#' that is anywhere in the line. Only ignore lines where there is nothing interesting before the '#'. Eg: grep -v '^ *#' Yup. I don't know what else to suggest. From what you describe in your message, both hosts should be getting the same set of files. -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[2]: Stupid cvsup questions
IMT On Mon, 15 Dec 2003 21:34:55 -0500 IMT Garance A Drosihn [EMAIL PROTECTED] wrote: At 11:41 PM +0200 12/15/03, Ion-Mihai Tetcu wrote: Hi, I have 2 identical (copy/paste) ports-supfiles on two machines: it# grep -v '#' /etc/ports-supfile *default host=cvsup.ro.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress ports-all try this: cat /usr/share/examples/cvsup/ports-supfile | egrep -v ^# | sed s/CHANGE_THIS/cvsup.ro/g /home/ports-supfile then run cvsup: cvsup -g -L 2 /home/ports-supfile ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
