diff options
Diffstat (limited to 'contrib/FAQ/OTHER-FAQS')
| -rw-r--r-- | contrib/FAQ/OTHER-FAQS/FreeBSD.current.policy | 162 | ||||
| -rw-r--r-- | contrib/FAQ/OTHER-FAQS/FreeBSD.kdebug.FAQ | 33 | ||||
| -rw-r--r-- | contrib/FAQ/OTHER-FAQS/FreeBSD.mailing-list.FAQ | 77 | ||||
| -rw-r--r-- | contrib/FAQ/OTHER-FAQS/FreeBSD.ports.supfile | 18 | ||||
| -rw-r--r-- | contrib/FAQ/OTHER-FAQS/FreeBSD.slip.dialup.faq | 172 | ||||
| -rw-r--r-- | contrib/FAQ/OTHER-FAQS/FreeBSD.standard.supfile | 16 | ||||
| -rw-r--r-- | contrib/FAQ/OTHER-FAQS/FreeBSD.sup.faq | 98 | ||||
| -rw-r--r-- | contrib/FAQ/OTHER-FAQS/FreeBSDvsLinux | 70 | ||||
| -rw-r--r-- | contrib/FAQ/OTHER-FAQS/NFS | 77 | ||||
| -rw-r--r-- | contrib/FAQ/OTHER-FAQS/Systems.FAQ | 266 |
10 files changed, 989 insertions, 0 deletions
diff --git a/contrib/FAQ/OTHER-FAQS/FreeBSD.current.policy b/contrib/FAQ/OTHER-FAQS/FreeBSD.current.policy new file mode 100644 index 000000000000..cdebbc72bbbf --- /dev/null +++ b/contrib/FAQ/OTHER-FAQS/FreeBSD.current.policy @@ -0,0 +1,162 @@ + THE FREEBSD CURRENT POLICY + +Last updated: $Date: 1994/05/07 11:39:26 $ + +This document attempts to explain the rationale behind FreeBSD-current, +what you should expect should you decide to run it, and states some +prerequisites for making sure the process goes as smoothly as possible. + + +1. What is FreeBSD-current? + +FreeBSD-current is, quite literally, nothing more than a daily snapshot of +the working sources for FreeBSD. These include work in progress, experimental +changes, and transitional mechanisms that may or may not be present in +the next official release of the software. While many of us compile +almost daily from FreeBSD-current sources, there are periods of time when +the sources are literally uncompilable. These problems are generally resolved +as expeditiously as possible, but whether or not FreeBSD-current sources bring +disaster or greatly desired functionality can literally be a matter of which +part of any given 24 hour period you grabbed them in! Please read on.. + +Under certain circumstances we will sometimes make binaries for parts of +FreeBSD-current available, but only because we're interested in getting +something tested, not because we're in the business of providing binary +releases of current. If we don't offer, please don't ask! It takes far +too much time to do this as a general task. + + +2. Who needs FreeBSD-current? + +FreeBSD-current is made generally available for 3 primary interest groups: + + 1. Members of the FreeBSD group who are actively working on one + part or another of the source tree and for whom keeping `current' + is an absolute requirement. + + 2. Members of the FreeBSD group who are active ALPHA/BETA testers + and willing to spend time working through problems in order to + ensure that FreeBSD-current remains as sane as possible. These + are also people who wish to make topical suggestions on changes + and the general direction of FreeBSD. + + 3. Peripheral members of the FreeBSD (or some other) group who merely + wish to keep an eye on things and use the current sources for + reference purposes (e.g. for *reading*, not running). These + people also make the occasional comment or contribute code. + + +3. What is FreeBSD-current _NOT_? + + 1. A fast-track to getting pre-release bits because there's something + you heard was pretty cool in there and you want to be the first on + your block to have it. + + 2. A quick way of getting bug fixes. + + 3. In any way "officially supported" by us. + + We do our best to help people genuinely in one of the 3 + "legitimate" FreeBSD-current catagories, but we simply DO NOT + HAVE THE TIME to help every person who jumps into FreeBSD-current + with more enthusiasm than knowledge of how to deal with + experimental system software. This is not because we're mean and + nasty people who don't like helping people out (we wouldn't even be + doing FreeBSD if we were), it's literally because we can't answer + 400 messages a day AND actually work on FreeBSD! I'm sure if + given the choice between having us answer lots of questions or + continue to improve FreeBSD, most of you would vote for us + improving it (and so would we! :-). + + +4. Ok. I still think I "qualify" for FreeBSD-current, so what do I do? + + 1. Join the freebsd-hackers and freebsd-commit mailing lists. + This is not just a good idea, it's ESSENTIAL. If you aren't on + freebsd-hackers, you won't read the comments that people are + making about the current state of the system and thus will end + up stumbling over a lot of problems that others have already + found and solved. Even more importantly, you will miss out on + potentially critical information (e.g. "Yo, Everybody! Before you + rebuild /usr/src, you MUST rebuild the kernel or your system + will crash horribly!"). + + The freebsd-commit list will allow you to see the commit log + entry for each change as its made. This can also contain + important information, and will let you know what parts of the + system are being actively changed. + + To join these lists, send mail to `majordomo@freefall.cdrom.com' + and say: + + subscribe freebsd-hackers + subscribe freebsd-commit + + In the body of your message. Optionally, you can also say `help' + and MajorDomo will send you full help on how to subscribe and + unsubscribe to the various other mailing lists we support. + + 2. Grab the sources from freebsd.cdrom.com. You can do this in + two 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 + changed from then on. Many people run sup from cron + and keep their sources up-to-date automatically. + + To get a binary of the sup program for FreeBSD, as well + as the documentation and some sample configuration files, + look in: + + freefall.cdrom.com:~ftp/pub/sup + + 2. Use ftp. The source tree for FreeBSD-current is always + "exported" on: + + freebsd.cdrom.com:~ftp/pub/FreeBSD/FreeBSD-current + + We use `wu-ftpd' which allows compressed/tar'd grabbing + of whole trees. e.g. you see: + + usr.bin/lex + + You can do: + + ftp> cd usr.bin + ftp> get lex.tar.Z + + 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! :-) + + +Thank you for taking the time to read this all the way through. We're +always very keen to remain "open" and share the fruits of our labor +with the widest possible audience, but sharing development sources has +always had certain pitfalls associated with it (which is why most +commercial organizations won't even consider it) and I want to make +sure that people at least come into this with their eyes open, and +don't make the leap unless they're good at working without a net! + + Jordan + + + diff --git a/contrib/FAQ/OTHER-FAQS/FreeBSD.kdebug.FAQ b/contrib/FAQ/OTHER-FAQS/FreeBSD.kdebug.FAQ new file mode 100644 index 000000000000..150fb8aac735 --- /dev/null +++ b/contrib/FAQ/OTHER-FAQS/FreeBSD.kdebug.FAQ @@ -0,0 +1,33 @@ + Kernel debugging FAQ + FreeBSD + +Last modified: $Id: FreeBSD.kdebug.FAQ,v 1.1 1994/06/12 15:12:21 gclarkii Exp $ + +Here are some instructions for getting kernel debugging working on +a crash dump, it assumes that you have enough swap space for a crash +dump. + +*** Start *** + +Config you're kernel using config -g + +Remove ${STRIP} -x $@; from the Makefile for the kernel so it doesn't +get stripped. + +When the kernel's been built make a copy of it, say 386BSD.debug, and +then run strip -x on the original. Install the original as normal. + +Now, after a crash dump, go to /sys/compile/WHATEVER and run kgdb. From kgdb +do: + +symbol-file 386BSD.debug +exec-file /var/crash/system.0 +core-file /var/crash/ram.0 + +and viola, you can debug the crash dump using the kernel sources just like +you can for any other program. + + + + Paul Richards, FreeBSD core team member. + diff --git a/contrib/FAQ/OTHER-FAQS/FreeBSD.mailing-list.FAQ b/contrib/FAQ/OTHER-FAQS/FreeBSD.mailing-list.FAQ new file mode 100644 index 000000000000..f522e79f782a --- /dev/null +++ b/contrib/FAQ/OTHER-FAQS/FreeBSD.mailing-list.FAQ @@ -0,0 +1,77 @@ + THE FREEBSD MAILING LIST FAQ + +Last updated: $Date: 1994/05/07 11:42:03 $ + +Though many of the FreeBSD development members read USENET, we cannot +always guarantee that we'll get to your questions in a timely fashion +(or at all) if you post them only to one of the comp.os.386bsd.* +groups. By addressing your questions to the appropriate mailing list +you will reach both us and a concentrated FreeBSD audience, invariably +assuring a better (or at least faster) response. + +The following is a summary of the mailing lists: + +List Purpose +----------------------------------------------------------------------------- +freebsd-admim Administrative issues (limited) +freebsd-arch Architecture and design discussions (limited) +freebsd-scsi Discussions concerning the SCSI system +freebsd-bugs Bug reports +freebsd-tz Discussions of proper timezone handling +freebsd-hackers Technical discussions and suggestions +freebsd-questions User questions +freebsd-announce Important events / milestones +freebsd-current Discussions about the use of FreeBSD-current + +----------------------------------------------------------------------------- + +Of all the lists, freebsd-arch and freebsd-admin have closed memberships +limited to a small subset of core team members and developers, though anyone +is free to send suggestions and commentary to them. The other lists may +be freely joined by anyone. + +All mailing lists live on `freefall.cdrom.com', so to post to a list you +simply mail to `<listname>@freefall.cdrom.com'. It will then be redistributed +to mailing list members throughout the world. + +To subscribe to a list, send mail to: + + majordomo@freefall.cdrom.com + +And include the keyword + + subscribe <listname> [<optional address>] + +In the body of your message. For example, to subscribe yourself to +freebsd-hackers, you'd do: + + % mail majordomo@freefall.cdrom.com + subscribe freebsd-hackers + ^D + +If you want to subscribe yourself under a different name, or submit a +subscription request for a local mailing list (note: this is more efficient +if you have several interested parties at one site, and highly appreciated by +us!), you would do something like: + + % mail majordomo@freefall.cdrom.com + subscribe freebsd-hackers local-hackers@somesite.com + ^D + +Finally, it is also possible to unsubscribe yourself from a list, get a +list of other list members or see the list of mailing lists again by +sending other types of control messages to majordomo. For a complete +list of available commands, do this: + + % mail majordomo@freefall.cdrom.com + help + ^D + +Finally, it is suggested that you only join the freebsd-hackers or +freebsd-questions mailing lists if you're also willing to see upwards +of 100 messages a day (peak)! If you're only interested in the "high points", +then it's suggested that you join freebsd-announce, which will contain +only infrequent traffic. + + Thank you! + diff --git a/contrib/FAQ/OTHER-FAQS/FreeBSD.ports.supfile b/contrib/FAQ/OTHER-FAQS/FreeBSD.ports.supfile new file mode 100644 index 000000000000..60d30bfedac5 --- /dev/null +++ b/contrib/FAQ/OTHER-FAQS/FreeBSD.ports.supfile @@ -0,0 +1,18 @@ + +ports-audio release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/ports delete compress +ports-base release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/ports delete compress +ports-comm release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/ports delete compress +ports-db release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/ports delete compress +ports-devel release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/ports delete compress +ports-editor release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/ports delete compress +ports-game release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/ports delete compress +ports-lang release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/ports delete compress +ports-mail release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/ports delete compress +ports-math release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/ports delete compress +ports-net release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/ports delete compress +ports-news release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/ports delete compress +ports-print release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/ports delete compress +ports-shell release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/ports delete compress +ports-util release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/ports delete compress +ports-x11 release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/ports delete compress + diff --git a/contrib/FAQ/OTHER-FAQS/FreeBSD.slip.dialup.faq b/contrib/FAQ/OTHER-FAQS/FreeBSD.slip.dialup.faq new file mode 100644 index 000000000000..23734d4c8ec4 --- /dev/null +++ b/contrib/FAQ/OTHER-FAQS/FreeBSD.slip.dialup.faq @@ -0,0 +1,172 @@ +*********************************************************************** +*** How to Set Up SLIP on FreeBSD *** +*********************************************************************** + +Last updated: $Date: 1994/06/01 09:03:08 $ + $Id: FreeBSD.slip.dialup.faq,v 1.1 1994/06/01 09:03:08 asami Exp $ + +The following is I (asami) set up my FreeBSD machine for SLIP on a +static host network. For dynamic hostname assignments (i.e., your +address changes each time you dial up), you probably need to do +something much fancier. + +This is just "what I did, and it worked for me". I'm sharing this +just for your reference, I'm no expert in SLIP nor networking so your +mileage may vary. + +First, make sure you have + +pseudo-device sl 2 + +in your kernel's config file. It is included in the GENERICAH and +GENERICBT kernels, so this won't be a problem unless you deleted it. + +Things you have to do only once: + +(1) Add your home machine, the gateway and nameservers to your + /etc/hosts file. Mine looks like this: + +127.0.0.1 localhost loghost +136.152.64.181 silvia.HIP.Berkeley.EDU silvia.HIP silvia + +136.152.64.1 inr-3.Berkeley.EDU inr-3 slip-gateway +128.32.136.9 ns1.Berkeley.edu ns1 +128.32.136.12 ns2.Berkeley.edu ns2 + + By the way, silvia is the name of the car that I had when I was + back in Japan (it's called 2?0SX here in U.S.). + +(2) Make sure you have "hosts" before "bind" in your /etc/host.conf. + Otherwise, funny things may happen. + +(3) Edit the /etc/netstart and add this to the end of the file: + +# set up slip +gateway=slip-gateway +ifconfig sl0 inet $hostname $gateway netmask 0xffffff00 +route add default $gateway + + Note that because of the "slip-gateway" entry in /etc/hosts, there + is no local dependency in the netstart file. Also, you might want + to un-comment the "route add $hostname localhost" line. + +(3') Make a file /etc/resolv.conf which contains: + +domain HIP.Berkeley.EDU +nameserver 128.32.136.9 +nameserver 128.32.136.12 + + As you can see, these set up the nameserver hosts. Of course, the + actual addresses depend on your environment. + +(4) Set the password for root and toor (and any other accounts that + doesn't have a password). Use passwd, don't edit the passwd or + passwd.master files! + +(5) Edit /etc/myname and reboot the machine. + +How to set up the connection: + +(6) Dial up, type "slip" at the prompt, enter your machine name and + password. The things you need to enter depends on your + environment. I use kermit, with a script like this: + +# kermit setup +set modem hayes +set line /dev/tty01 +set speed 57600 +set parity none +set flow rts/cts +set terminal bytesize 8 +set file type binary +# The next macro will dial up and login +define slip dial 643-9600, input 10 =>, if failure stop, - +output slip\x0d, input 10 Username:, if failure stop, - +output silvia\x0d, input 10 Password:, if failure stop, - +output ***\x0d, echo \x0aCONNECTED\x0a + + (of course, you have to change the hostname and password to fit + yours). Then you can just type "slip" from the kermit prompt to + get connected. + + Note: leaving your password in plain text anywhere in the + filesystem is generally a BAD idea. Do it at your own risk. I'm + just too lazy. + + If kermit doesn't give you a prompt, try "stty -f /dev/tty01 + clocal". I put this in /etc/rc.local so that it works the first + time I boot the machine. + +(7) Leave the kermit there (you can suspend it by "z") and as root, + type + +slattach -h -c -s 57600 /dev/tty01 + + if you are able to "ping" hosts on campus, you are connected! + + If it doesn't work, you might want to try "-a" instead of "-c". + +(8) Happy slipping! + +How to shutdown the connection: + +(9) Type "ps gx" (as root) to find out the PID of slattach, and use + "kill -INT" to kill it. + + Then go back to kermit ("fg" if you suspended it) and exit from it + ("q"). + + The slattach man page says you have to use "ifconfig sl0 down" to + mark the interface down, but this doesn't seem to make any + difference for me. ("ifconfig sl0" reports the same thing.) + + Some times, your modem might refuse to drop the carrier (mine + often does). In that case, simply start kermit and quit it again. + It usually goes out on the second try. + + When you want to connect again, go back to (6). You may have to + watch out for clocal mode. If "stty -f /dev/tty01" doesn't tell + you it's clocal, you need to re-set it before kermitting. + +TROUBLESHOOTING: + +If it doesn't work, feel free to ask me. The things that people +tripped over so far: + +* Not using "-c" or "-a" in slattach (I have no idea why this can be + fatal, but adding this flag solved the problem for at least one + person) + +* Using "s10" instead of "sl0" (might be hard to see the difference on + some fonts :) + +Try "ifconfig sl0" to see your interface status. I get: + +silvia# ifconfig sl0 +sl0: flags=10<POINTOPOINT> + inet 136.152.64.181 --> 136.152.64.1 netmask ffffff00 + +Also, "netstat -r" will give the routing table, in case you get the +"no route to host" messages from ping. Mine looks like: + +silvia# netstat -r +Routing tables +Destination Gateway Flags Refs Use IfaceMTU Rtt +Netmasks: +(root node) +(root node) + +Route Tree for Protocol Family inet: +(root node) => +default inr-3.Berkeley.EDU UG 8 224515 sl0 - - +localhost.Berkel localhost.Berkeley UH 5 42127 lo0 - 0.438 +inr-3.Berkeley.E silvia.HIP.Berkele UH 1 0 sl0 - - +silvia.HIP.Berke localhost.Berkeley UGH 34 47641234 lo0 - 0.438 +(root node) + +(this is after transferring a bunch of files, your numbers should be +smaller). + +--- +Satoshi Asami +asami@cs.berkeley.edu diff --git a/contrib/FAQ/OTHER-FAQS/FreeBSD.standard.supfile b/contrib/FAQ/OTHER-FAQS/FreeBSD.standard.supfile new file mode 100644 index 000000000000..531a98110b38 --- /dev/null +++ b/contrib/FAQ/OTHER-FAQS/FreeBSD.standard.supfile @@ -0,0 +1,16 @@ +base release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/src delete old compress +bin release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/src delete old compress +contrib release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/src delete old compress +crypt release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/src delete old compress +etc release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/src delete old compress +games release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/src delete old compress +gnu release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/src delete old compress +include release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/src delete old compress +ksrc release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/src delete old compress +lib release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/src delete old compress +libexec release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/src delete old compress +sbin release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/src delete old compress +share release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/src delete old compress +usrbin release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/src delete old compress +usrsbin release=current host=freefall.cdrom.com hostbase=/home base=/usr prefix=/usr/src delete old compress + diff --git a/contrib/FAQ/OTHER-FAQS/FreeBSD.sup.faq b/contrib/FAQ/OTHER-FAQS/FreeBSD.sup.faq new file mode 100644 index 000000000000..35c552168d6b --- /dev/null +++ b/contrib/FAQ/OTHER-FAQS/FreeBSD.sup.faq @@ -0,0 +1,98 @@ + + FreeBSD + Sup FAQ + +Last updated: $Date: 1994/05/11 22:40:48 $ + + SUP is a network based software update tool developed at CMU. The +purpose of this document is get the beginner up and running with sup. + + First off you will need to pick up the sup binaries. The easiest +way of doing this is to grab the sup_bin.tgz package from: + + freebsd.cdrom.com:~ftp/pub/FreeBSD/packages + (FreeBSD 1.1 or later) + freebsd.cdrom.com:~ftp/pub/FreeBSD/packages-1.0 + (FreeBSD 1.0.2 or earlier) + +Install the sup package using pkg_add and add the following line to your +/etc/services file: + + sup 871/tcp #sup + + + SUP gets the information it needs to run from a configuration file +called a supfile. This file tells sup what collections it will be updating +and/or installing and where they go. There are already two files that +have been created for supping FreeBSD, both of which may be gotten from: + + freebsd.cdrom.com:~ftp/pub/FreeBSD/FAQ/OTHER-FAQS + +The file `FreeBSD.standard.supfile' is used for supping from the +/usr/src tree, the file `FreeBSD.ports.supfile' for the /usr/ports tree. +These two files can be installed whereever it is convient to do so. + + Next you will have to comment out whichever distributions you do +not wish to receive with a # at the begining of the distribution line. +You will find a list of distributions and a description for each at the +end of this file. + + Once this is setup, you're ready to go. + +To start sup type: + + sup supfile + +If you wish to see what sup is doing "verbosely", give it the -v option, +like so: + + sup -v supfile + + Thats all there is to it! Remember that if you're running current, +which is what you will have if you sup, please join the freebsd-current +mailing list. For more information on current please see the file: + +freefall.cdrom.com:~ftp/pub/FreeBSD/FAQ/OTHER-FAQS/FreeBSD.current.policy + +Gary Clark II +FreeBSD maintainance person + +---- + +FreeBSD SUP distributions + +From FreeBSD.standard.supfile: + +base: Just those files at the top of /usr/src. +bin: /bin +contrib: Sources to programs located in /usr/src/contrib, including the FAQ. +crypt: Sources to libcrypt. NOTE: This is for use by US and Canadians only!! +etc: /etc +games: /usr/games +gnu: Software that is under the GPL, like gcc, groff and uucp. +include: /usr/include +ksrc: The kernel sources +lib: /usr/lib +libexec: /usr/libexec +sbin: /sbin +usrbin: /usr/bin +usrsbin: /usr/sbin + +From FreeBSD.ports.supfile + +ports-audio: Audio applications +ports-base: Just those files at the top of /usr/ports. +ports-comm: Communications software +ports-db: Database software +ports-devel: Development software +ports-editor: Editing software +ports-game: Game software +ports-lang: Programming Languages +ports-mail: Mail software +ports-math: Math software +ports-net: Network software +ports-news: USENET news software +ports-print: Printing software +ports-shell: User shell software +ports-util: Utility software +ports-x11: X11 software diff --git a/contrib/FAQ/OTHER-FAQS/FreeBSDvsLinux b/contrib/FAQ/OTHER-FAQS/FreeBSDvsLinux new file mode 100644 index 000000000000..c282475d60e5 --- /dev/null +++ b/contrib/FAQ/OTHER-FAQS/FreeBSDvsLinux @@ -0,0 +1,70 @@ +[ Note: You could very well simply substitute the word "NetBSD" for Linux + in the argument that follows ] + +From time to time, a thread in both the comp.os.386bsd.misc and +comp.os.linux.misc groups flares up regarding which operating system is +"better", FreeBSD or Linux. This generally provokes controversy from +users on both sides, with one group claiming that their OS is "better" +for some reason and the other group claiming that the first group +doesn't know what the heck it's talking about. + +Both arguments are a waste of time. + +Rather than trying to win a rather questionable debate on relative +(and constantly changing) technical merits, we should be asking ourselves +what both groups are REALLY about and what they represent. This is +naturally going to be a matter of personal opinion, but I believe even the +most seriously at-odds members would agree that both operating systems +represent a unique and long-awaited opportunity: The ability to run a +fully featured operating system on popular, easily affordable hardware +and for which all source code is freely available. + +Those who have been in computing for awhile will remember when the term +`operating system' referred almost exclusively to something provided solely +by the hardware vendor, with very little in the way of alternative options. +It was never EVER given out with source code, and true "wizard" status could +only be achieved by exerting mind-numbing amounts of effort and patience in +digging through forbidden bits of binary data. By comparison, the situation +today seems almost too good to be true! Certainly, the feeling of achievement +that came from finally ferreting out some esoteric bit of information from +a 4MB printed system dump was high, but I don't think that anyone would argue +that it was hardly the most optimal way of truly getting to know your +operating system! :-) + +So now, within a very short space of time, we're almost spoiled for choice in +having machines several times more powerful than the first multi-user VAX +machines and available for under $2000, and we've got not one but SEVERAL +perfectly reasonable free operating systems to chose from. We are in a +comparative paradise, and what are some of us doing? *Complaining* about it! +I suppose too much is never enough, eh? :-) + +So, my essential point is simply this: For the first time ever we +have what previous computing generations could only dream about; +powerful computers at a reasonable prices and a wonderful selection of +things to run on them. Be happy, read the source code you're so +privileged to now have available (*believe* me! What I wouldn't have +given, even 5 years ago!) and spend your energy in making constructive +use of it, not in arguing with the guys on the other side of the +fence! + +Additionally, it should be said that none of the FreeBSD team has +anything but the highest degree of respect for Linus Torvalds and his +"team" of dedicated volunteers (and we occasional exchange gripe mail +about the huge volume of messages each of us gets as a direct result +of being insane enough to volunteer to do something like this :-). +Our common commitment to the Intel platform also gives us more common +ground (and interests) than one might think and, if anything, it's a pity +that we do not endevor to share more code and effort - ideologically, +at least, I'd say we share pretty similar goals. + +As to which is "best", I have only one standard reply: Try them both, +see for yourself, think for yourself. Both groups have given you +something for free, at considerable personal effort, and the least you +can do is give them the benefit of exerting enough effort to try what +they're offering out before passing judgment (or worse, blindly +accepting someone else's!). + +Whichever you run, you're getting a great deal - enjoy! + + + Jordan Hubbard diff --git a/contrib/FAQ/OTHER-FAQS/NFS b/contrib/FAQ/OTHER-FAQS/NFS new file mode 100644 index 000000000000..e6f7af8fc511 --- /dev/null +++ b/contrib/FAQ/OTHER-FAQS/NFS @@ -0,0 +1,77 @@ +FreeBSD and NFS [for a FAQ] + +Certain Ethernet adapters for ISA PC systems have limitations which +can lead to serious network problems, particularly with NFS. This +difficulty is not specific to FreeBSD, but FreeBSD systems are affected +by it. + +The problem nearly always occurs when (FreeBSD) PC systems are networked +with high-performance workstations, such as those made by Silicon Graphics, +Inc., and Sun Microsystems, Inc. The NFS mount will work fine, and some +operations may succeed, but suddenly the server will seem to become +unresponsive to the client, even though requests to and from other systems +continue to be processed. This happens to the client system, whether the +client is the FreeBSD system or the workstation. On many systems, there is +no way to shut down the client gracefully once this problem has manifested +itself. The only solution is often to reset the client, because the NFS +situation cannot be resolved. + +Though the "correct" solution is to get a higher performance and capacity +Ethernet adapter for the FreeBSD system, there is a simple workaround that +will allow satisfactory operation. If the FreeBSD system is the SERVER, +include the option "wsize=1024" on the mount from the client. If the +FreeBSD system is the CLIENT, then mount the NFS file system with the +option "rsize=1024". These options may be specified using the fourth +field of the fstab entry on the client for automatic mounts, or by using +the "-o" parameter of the mount command for manual mounts. + +In the following examples, "fastws" is the host (interface) name of a +high-performance workstation, and "freebox" is the host (interface) name of +a FreeBSD system with a lower-performance Ethernet adapter. Also, +"/sharedfs" will be the exported NFS filesystem (see "man exports"), and +"/project" will be the mount point on the client for the exported file +system. In all cases, note that additional options, such as "hard" or +"soft" and "bg" may be desireable in your application. + +Examples for the FreeBSD system ("freebox") as the client: + in /etc/fstab on freebox: +fastws:/sharedfs /project nfs rw,rsize=1024 0 0 + as a manual mount command on freebox: +mount -t nfs -o rsize=1024 fastws:/sharedfs /project + +Examples for the FreeBSD system as the server: + in /etc/fstab on fastws: +freebox:/sharedfs /project nfs rw,wsize=1024 0 0 + as a manual mount command on fastws: +mount -t nfs -o wsize=1024 freebox:/sharedfs /project + +Nearly any 16-bit Ethernet adapter will allow operation without the above +restrictions on the read or write size. + +For anyone who cares, here is what happens when the failure occurs, which +also explains why it is unrecoverable. NFS typically works with a "block" +size of 8k (though it may do fragments of smaller sizes). Since the maximum +Ethernet packet is around 1500 bytes, the NFS "block" gets split into +multiple Ethernet packets, even though it is still a single unit to the +upper-level code, and must be received, assembled, and ACKNOWLEDGED as a +unit. The high-performance workstations can pump out the packets which +comprise the NFS unit one right after the other, just as close together as +the standard allows. On the smaller, lower capacity cards, the later +packets overrun the earlier packets of the same unit before they can be +transferred to the host and the unit as a whole cannot be reconstructed or +acknowledged. As a result, the workstation will time out and try again, +but it will try again with the entire 8K unit, and the process will be +repeated, ad infinitum. + +By keeping the unit size below the Ethernet packet size limitation, we +ensure that any complete Ethernet packet received can be acknowledged +individually, avoiding the deadlock situation. + +Overruns may still occur when a high-performance workstations is slamming +data out to a PC system, but with the better cards, such overruns are +not guarranteed on NFS "units". When an overrun occurs, the units affected +will be retransmitted, and there will be a fair chance that they will be +received, assembled, and acknowledged. +-- + John Lind, Starfire Consulting Services +E-mail: john@starfire.MN.ORG USnail: PO Box 17247, Mpls MN 55417 diff --git a/contrib/FAQ/OTHER-FAQS/Systems.FAQ b/contrib/FAQ/OTHER-FAQS/Systems.FAQ new file mode 100644 index 000000000000..c2e3e2ed5177 --- /dev/null +++ b/contrib/FAQ/OTHER-FAQS/Systems.FAQ @@ -0,0 +1,266 @@ + Systems FAQ + For FreeBSD + Last Modified: $Id: Systems.FAQ,v 1.1 1994/06/11 17:59:19 gclarkii Exp $ + +This FAQ is a list of systems that people have sent to the FAQ maintnance +person for inclusion. If you have a system you would like to be included +please send it to FreeBSD-FAQ@freefall.cdrom.com. + +Disclaimer: This document is composed of systems that people have sent to +the FAQ maintnance person. It is the not to be taken as an endorsement +for any system or manufacture. + + +1. + +386DX/20 real AMI, ISA +Oak SVGA (no X) +8MB +Adaptec 1542B, WD1007V ESDI +Wren VI and Miniscribe 660MB 20Mbit/sec ESDI +WD 8013EBT + +2. + +486DX/25 clone, AMI BIOS, ISA +Orchid PCIII gas plasma (yes, VGA16) +8MB +Adaptec 1542B +Micropolis 1684 SCSI +SMC 8013EEWC + +3. + + ??? OPTI chipset AMI BIOS 486/50 ISA +ISA ET4000 w/ X11 (not so slow) +16 Mb - 48 Mb swap +ISA aha1542 B +ISA no-name IDE w/ floppies +FUJITSU M2623S-512 405MB set to SCSI2 +SEAGATE ST3283N 237MB SCSI2 +SANYO CRD-400I SCSI2 cdromcdrom + +4. + +Lipizzan LDO-1 486DX-33 motherboard +Orchid ProIIs (1M) video +8 MB memory +Generic 2S/1P/2FD/IDE controller: +Maxtor 7213 AT +WDC AC2420H +PAS-16 + Sony CDU31A CD drive (Fusion 16 package). + *** The CD drive does not currently work with FreeBSD. + +5. + +Asus VL/ISA-486SV2 (ISA-VLB as you can see) +Orchid Fahrenheit 1280+ VLB (yes) +20MB +Some no-name IDE VLB controller +Conner CP30504 (I think....the 540MB IDE one) +Zoltrix 14.4/14.4 Fax/Modem on tty01 +Intel 486DX2/66 CPU + fan +Conner CP30104 (120MB....for DOS) + +6. + +AIR 486El (running with AMD486/40) +ATI Graphics Ultra Pro running XFree862.1 +16M +Adaptec 1742 +Micropolis 2217 +Wangtec 6130FS DAT drive (Some problems) + +7. + +Compudyne 486 DX2/66 +ATI Local Bus GUP w/ 2megs +16 Megs Memory +504 IDE Hard Drive +Colorado 250 meg QIC-80 tape drive + +8. + +American Megatrends Enterprise III, 486DX2-66 +ATI VLB Mach 32 (with X) +16 meg +Adaptec 1742 EISA SCSI with floppy +Toshiba 5030 SCSI-II +Toshiba 5157 SCSI-II +SMC Elite16T ISA Ethernet (ISA) + +9. + +American Megatrends Enterprise III, 486DX +ATI VLB Mach 32 (with X) +32 meg +Adaptec 1742 EISA SCSI with floppy +Maxtor P0-12S SCSI +Digital DSP5200S SCSI-II +Pro Audio Spectrum 16 +Wonder Board, 4 serial (16550), 3 parallel, each on a different interrupt + +10. + +NoName 486DX/33, Intel Chipset, EISA-Bus +ATI Graphics Ultra Pro EISA, +17" Nanao (Eizo) F550-i Monitor +Running the Mach32 X-Server XFree86-2.1.1 with fonts created from source. +16 MB RAM (planning to add another 8 MB). +AHA1742A +Conner CP3100 +Fujitsu 520 MB +Archive 525MB streamer tape. +Gravis UltraSound - works for mod-files. + +11. + +ASUS SP3 PCI Board with i486 DX/2 66 MHz +ISA ET4000 (I already tested a S3 805 PCI card successfully) +Adaptec 1542B +Toshiba XM3301TA CD-Rom +CDC Harddisk, 572 MB (I don't know the exact specs) + +12. + +Mylex MAE486/33 EISA Motherboard +16MB memory +Actix GE32+ S3 801 gfx +Adaptec 1742A controller +Seagate ST3160 drive +Seagate ST5120 drive +Archive Viper 150MB tape +Roland SCC-1 sound card +Gravis Ultrasound card +Longshine SMC/Novell compatable ethernet card + +13. + +Model: DECpc LPv 466d2 +Config: Local (Motherboard) S3 801 gfx, IDE controller, PS/2 mouse, 12MB memory + +14. + + +??? 486/DX266 EISA/VLB Motherboard +16MB memory +#9 GXE L12 VLB 3MB graphics card +Bt445S VLB disk controller +DEC DSP3105S drive +MAXSTOR P-17S drive +Tandberg 525MB tape drive +Toshiba XM3301 CDROM +Soundblaster 2.0 +Longshine SMC/Novell compatable ethernet card + +15. + +M407 PC chips with 33Mhz 486. +Had to disable external cache due to DMA problems. Board uses write-through +cache unless a second chip is added to allow write-back.write-back. +Orchid ProDesigner II (yes) +16Mb +IDE +Maxtor 7213 AT and Maxtor 7120 AT +2 BICC Isolans (Lance based cards) + +16. + +Gigabyte EISA/VLB motherboard with SIS chipset, AMI bios, 32 MB ram +Adaptec 1742 SCSI 2 controller with floppy controller enabled +Spea/V7 Mirage - S3/805 based localbus graphics card with 1 MB d-ram +no name wd8013 compatible ethernet card +Gravis Ultrasound card with 1 MB ram +2 Fujitsu 400 MB and 1 Seagate 500 MB SCSI 2 harddisks +5 1/4 + 3 1/2 inch floppy drives +Tandberg TDC3600 60 MB + Tandberg TDC3800 525 MB Streamer (these don't work +quite properly yet) + +17. + +i486DX33, 16 Mb RAM, 256 Kb external cache, VLB board +no-name IDE/floppy controller +Western Digital Caviar 2340 (325 Mb) +Kalok KL-343 (40 Mb) +Chips & Technologies 451 SuperVGA card (800x600, 16 colours, 256Kb) + +18. + +no name EISA i486DX/33 board, 16 MB RAM +Adaptec AHA-1540*A* (not knowing if the current -current might cause + problems, my kernel is from end of march) +Maxtor MXT-1240S, 1.2Gig very fast SCSI disk +Seagate ST-1144A, just to boot off the beast (also has a messdos partition yet) +Archive Viper 150 tape; has a firmware braindeadness when appending files, + works very well otherwise +ELSA Winner 1000 ISA/EISA, 1MB VRAM, S3 86C928 (unfortunately, D-step chip) +Nokia 447-B 17in monitor, running ~ 1100x800 resolution, very nice +true `Mouse Systems' optical mouse, fine thing! +sometimes a Toshiba XM-3301 CDROM, rather old, but solid & reliable + +19. + +older south-east Asia made notebook, i386SX/16, 5 MB RAM (where the 384 k hole + can be re-mapped, so all the 5 MB are useable) +Seagate ST-9145AG, 120 MB 2.5in IDE disk, very low power consumption, but + rather slow transfer rate, only about 350 K/s, so paging is a mess +640x480 LCD, ~ 16 gray tones distinguishable, Cirrus Logic CL-GD610/620 + chipset; runs generic VGA-Mono and VGA-16 XFree86[tm] servers; needs + some hacks in rc.local to give full contrast when running with the + pcvt display driver (due to their different default attribute handling) + + +20. + +Data General Dasher 386sx/16, 8 MB RAM +Adaptec AHA-1542B +Seagate ST-3655N, 525 MB SCSI disk +Conner CP-3044, 40 MB IDE disk +has been working with a Western Digital WD-1007V ESDI controller (on + secondary wdc address), and a Micropolis 1664-7 330 MB ESDI disk - + but this beast was terribly slow, loud (& unreliable) and therefore + had to go +ET-3000 based 512 K VGA, slow (wrt. XFree86), but reliable +3Com 3C503 Ethernet adaptor, suffers from the `do not nfs mount with + too large packets' problem, but works well otherwise +`Mouse Systems' optical mouse +Toshiba XM-3301 CDROM +already ran with a Micropolis 1664-3 330 MB SCSI disk (same drive as + above, but different interface) +already ran with an IBM 2Gig SCSI disk (don't remember the type) + + +21. + +Mylex MNA 486/33 EISA Motherboard +16Mb of Memory +1.2 GB Toshiba 538 SCSI disk +400Mb IBM SCSI disk +150/250Mb Tandberg SCSI tape drive +Toshiba 3401 SCSI CD-ROM +Tseng 4000 Video Controller +Logitech Bus Mouse +Mediavision Pro Audio Stereo Sound Card +Adaptech 1742A SCSI controller +WD8013EBT Ethernet Card + +22. + +386DX-40 w/Cyrix math co-processor +ET-4000 running X +16MB +IDE +540MB Western Digital +WD8003EP + + + + + + + + + + + + |