diff options
Diffstat (limited to 'share/FAQ')
-rw-r--r-- | share/FAQ/FreeBSD.FAQ | 8 | ||||
-rw-r--r-- | share/FAQ/ctm.FAQ | 120 | ||||
-rw-r--r-- | share/FAQ/current-policy.FAQ | 54 |
3 files changed, 155 insertions, 27 deletions
diff --git a/share/FAQ/FreeBSD.FAQ b/share/FAQ/FreeBSD.FAQ index 7c62062..334dc2f 100644 --- a/share/FAQ/FreeBSD.FAQ +++ b/share/FAQ/FreeBSD.FAQ @@ -6,7 +6,7 @@ Please mail all suggestions and additions to <FAQ@FreeBSD.ORG> -Revision: $Id: FreeBSD.FAQ,v 1.17 1995/02/25 23:42:14 roberto Exp $ +Revision: $Id: FreeBSD.FAQ,v 1.18 1995/02/26 21:27:29 gclarkii Exp $ All entries are assumed to be relevant to FreeBSD 2.0. Any entries with a <XXX> are under construction. @@ -603,9 +603,9 @@ be corrupted. 5.6: I would like to track changes to current and do not have net access. Is there any way besides downloading the whole tree? -Yes, Poul-Henning has set up a source tracking list. Please email -majordomo@ref.tfs.com with a body of "get ctm-src-cur README" for -futher information. +Yes, you can use the CTM facility. Check out the ctm.FAQ file or + ftp://freefall.cdrom.com/pub/CTM/README +for more information. 5.7: How do I split up large binary files into smaller 240k files like the distribution does? diff --git a/share/FAQ/ctm.FAQ b/share/FAQ/ctm.FAQ new file mode 100644 index 0000000..3217e06 --- /dev/null +++ b/share/FAQ/ctm.FAQ @@ -0,0 +1,120 @@ +# ---------------------------------------------------------------------------- +# "THE BEER-WARE LICENSE" (Revision 42): +# <phk@login.dknet.dk> wrote this file. As long as you retain this notice you +# can do whatever you want with this stuff. If we meet some day, and you think +# this stuff is worth it, you can buy me a beer in return. Poul-Henning Kamp +# ---------------------------------------------------------------------------- +# +# Mon Feb 27 00:06:22 PST 1995 +# + + Obtaining FreeBSD-current sources using CTM. + ============================================ + +CTM is a method to keep a remote directory-tree in sync with a central one. +It has been developed for FreeBSD usage, but other people might use it as +time goes by, but little if any documentations exists on this time on the +process of creating deltas. + + +Why should I use CTM ? +---------------------- +CTM will give you a local copy of the "FreeBSD-current" sources. +If you are an active developer on FreeBSD, but have lousy or non-existent +TCP/IP connectivity, CTM is made for you. +You will need to pick up up to four deltas per day (or you can have them +arrive in email automatically) and sizes are as small as we can do it: +typically less than 5K, one delta in ten is like 10-50K and every now and +then a biggie of 100K+ comes around. + +You need to make yourself aware of the caveats of following the "current" +sources, refer to the relevant FAQ for more info on that topic. + +Only if you have commit priviledge, or are similary authorized, can you get +access to the cvs tree by the same means. Contact phk@FreeBSD.org for that. + +What do I need to use CTM ? +--------------------------- +You need two things. The "ctm" program and the stuff to feed it. "ctm" is +in the FreeBSD-current tree from version 2.0.0 and forward. (src/usr.sbin/ctm) + +The "deltas" you feed ctm can be had two ways, ftp or email. + + +FTP-access: +----------- +The CTM-deltas can be found on the following sites: + + ftp://freefall.cdrom.com/pub/CTM + + +eMail-access: +------------- +Send email to majordomo@freebsd.org, subscribe to the list "ctm-src-cur". +Use the ctm_rmail program to unpack and apply the emails with. You can +actually use the ctm_rmail program directly from a entry in /etc/aliases +if you want. Check the "ctm_rmail" man page. + + +How to get started. +------------------- +You need to get up to speed. Every now and then I will produce a special +additional delta: a delta from nothing. You can recognize these in two +ways, the are large: 25 to 30 Megabytes gzip'ed, and they have an 'A' +appended to the number. (src-cur.0341A.gz for instance). You will also +need all deltas with higher numbers. + +Now working... +-------------- +To apply the deltas, simply say + + cd /where/ever/you/want/the/stuff + ctm -v -v /where/you/store/your/deltas/src-cur.* + +Unless it feels very secure about the entire thing, ctm will not touch +your tree. To check out a delta you can add a "-c", then ctm will never +touch you tree. + +There are other options to ctm as well, look in the sources. It's a +little bit confusing right now, but it will become better I hope. + +I would be very happy if somebody will help with the "user-interface" +part, as I have realized that I can't make up my mind on what options +should do what, how and when... + +ctm understands deltas which have been put through gzip, so you don't need +to gunzip them first. + +That's really all there is to it. Everytime you get a new delta, you +run it through ctm. + +Don't remove the deltas, if they are hard to download again. You just might +want to keep them around in case something bad happens. Even if you only have +floppy disks, consider using "fdwrite" to make a copy. + + +Plans: +------ +Tons of them. Don't forget to tell me what you want though... + + +Misc. stuff: +------------ +If you are a frequent or valuable contributor to FreeBSD, I will be willing +to arrange special services, one option is delivery via ftp or rcp to a +machine closer to you. You need to have earned this, since it takes time +to do, but I'll be all the more happy to do it for you then. + +Thanks! +------- +Bruce Evans, for his pointed pen and invaluable comments. +Soren Schmidt, for patience. +Stephen McKay, wrote ctm_[rs]mail, much appreceiated. +Jordan Hubbard, for being so stubborn that I had to make it better. +All the users, I hope you like it... + +Comments ? +---------- +email phk@FreeBSD.org + +Poul-Henning diff --git a/share/FAQ/current-policy.FAQ b/share/FAQ/current-policy.FAQ index 38b6b50..4d9e86b 100644 --- a/share/FAQ/current-policy.FAQ +++ b/share/FAQ/current-policy.FAQ @@ -1,6 +1,6 @@ THE FREEBSD CURRENT POLICY -Last updated: $Date: 1994/09/11 10:56:05 $ +Last updated: $Date: 1994/10/03 03:48:39 $ This document attempts to explain the rationale behind FreeBSD-current, what you should expect should you decide to run it, and states some @@ -97,21 +97,29 @@ FreeBSD-current is made generally available for 3 primary interest groups: unsubscribe to the various other mailing lists we support. 2. Grab the sources from ftp.FreeBSD.ORG. You can do this in - two ways: + three ways: - 1. Use the CMU `sup' program (Software Update Protocol). - This is the most recommended method, since it allows you - to grab the entire collection once and then only what's + 1. Using the CTM facility. Read the ctm.FAQ file for more + information. Unless you have a good TCP/IP connection at + a flat rate, this is the way to do it. + + 2. Use the CMU `sup' program (Software Update Protocol). + This is the second most recommended method, since it allows + you to grab the entire collection once and then only what's changed from then on. Many people run sup from cron and keep their sources up-to-date automatically. + The problem is that sup does not use the bandwidth efficient, + unless the round-trip is very fast. If the cost of connection + or the duration of the session is a concern, use CTM. + To get a binary of the sup program for FreeBSD, as well as the documentation and some sample configuration files, look in: FreeBSD.ORG:~ftp/pub/sup - 2. Use ftp. The source tree for FreeBSD-current is always + 3. Use ftp. The source tree for FreeBSD-current is always "exported" on: ftp.FreeBSD.ORG:~ftp/pub/FreeBSD/FreeBSD-current @@ -129,23 +137,23 @@ FreeBSD-current is made generally available for 3 primary interest groups: And it will get the whole directory for you as a compressed tar file. - 3. If you're grabbing the sources to run, and not just look at, - then grab ALL of current, not just selected portions. The - reason for this is that various parts of the source depend on - updates elsewhere and trying to compile just a subset is almost - guaranteed to get you into trouble. - - 4. Before compiling current, read the Makefile in /usr/src - carefully. You'll see one-time targets like `bootstrapld' - which *MUST* be run as part of the upgrading process. Reading - freebsd-hackers will keep you up-to-date on other bootstrapping - procedures that sometimes become necessary as we move towards - the next release. - - 5. Be active! If you're running FreeBSD-current, we want to know - what you have to say about it, especially if you have suggestions - for enhancements or bug fixes. Suggestions with accompanying code - are received most enthusiastically! :-) + 3. If you're grabbing the sources to run, and not just look at, + then grab ALL of current, not just selected portions. The + reason for this is that various parts of the source depend on + updates elsewhere and trying to compile just a subset is almost + guaranteed to get you into trouble. + + 4. Before compiling current, read the Makefile in /usr/src + carefully. You'll see one-time targets like `bootstrapld' + which *MUST* be run as part of the upgrading process. Reading + freebsd-hackers will keep you up-to-date on other bootstrapping + procedures that sometimes become necessary as we move towards + the next release. + + 5. Be active! If you're running FreeBSD-current, we want to know + what you have to say about it, especially if you have suggestions + for enhancements or bug fixes. Suggestions with accompanying code + are received most enthusiastically! :-) Thank you for taking the time to read this all the way through. We're |