From wlloyd@tolstoy.mpd.ca Wed Jan 1 10:44:57 1997 Received: from tolstoy.mpd.ca (wlloyd.HIP.CAM.ORG [199.84.42.209]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA19069 for ; Wed, 1 Jan 1997 10:44:27 -0800 (PST) Received: (from wlloyd@localhost) by tolstoy.mpd.ca (8.7.5/8.7.3) id NAA00636; Wed, 1 Jan 1997 13:45:54 -0500 (EST) Message-Id: <199701011845.NAA00636@tolstoy.mpd.ca> Date: Wed, 1 Jan 1997 13:45:54 -0500 (EST) From: William Lloyd Reply-To: wlloyd@tolstoy.mpd.ca To: FreeBSD-gnats-submit@freebsd.org Subject: Changes to FAQ X-Send-Pr-Version: 3.2 >Number: 2353 >Category: docs >Synopsis: Changes to FAQ >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: closed >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Jan 1 10:50:01 PST 1997 >Closed-Date: Sun May 31 08:13:46 PDT 1998 >Last-Modified: Sun May 31 08:16:31 PDT 1998 >Originator: William Lloyd >Release: FreeBSD 2.1.5-STABLE i386 >Organization: William Lloyd (wlloyd@mpd.ca) >Environment: >Description: Update to the FAQ. Most URL's (except thoese that need it) are now relative. Mailing list and search stuff is still hard coded to www.freebsd.org Removed information that has been moved to the handbook. Like most of the serial port stuff Updates for other questions. I have made a lot more pointers to the handbook. Copy also sent to pds@freebsd.org >How-To-Repeat: >Fix: *** FAQ.sgml.orig Sun Nov 24 18:48:47 1996 --- FAQ.sgml Fri Dec 20 12:11:30 1996 *************** *** 1,15 **** !
Frequently Asked Questions for FreeBSD 2.X ! <author>The FreeBSD FAQ Team, <tt/FAQ@FreeBSD.ORG/ ! <date>$Date: 1996/11/21 16:38:29 $ <abstract> This is the FAQ for FreeBSD systems version 2.X All entries are assumed to be relevant to FreeBSD 2.0.5+, unless otherwise noted. ! Any entries with a <XXX> are under construction. </abstract> <toc> --- 1,18 ---- <!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN"> ! <!-- $Id: FAQ.sgml,v 1.16 1996/12/14 18:12:17 joerg Exp $ --> <article> <title>Frequently Asked Questions for FreeBSD 2.X ! <author>Maintainer: Peter da Silva <tt><htmlurl url='mailto:pds@FreeBSD.ORG' ! name='<pds@FreeBSD.ORG>'></tt> ! ! <date>$Date: 1996/12/14 18:12:17 $ <abstract> This is the FAQ for FreeBSD systems version 2.X All entries are assumed to be relevant to FreeBSD 2.0.5+, unless otherwise noted. ! Any entries with a <XXX> are under construction. FreeBSD's main documentation is kept in the <url url="../handbook/handbook.html" name="Handbook."> ! </abstract> <toc> *************** *** 277,367 **** Fax: +44 01892 667473<newline> (Do not dial the leading zero if calling from outside the UK). - <sect1> - <heading>What FreeBSD mailing lists are available?</heading> - <p> - The following mailing lists are provided for FreeBSD users and - developers. For more information, send to - <majordomo@FreeBSD.ORG> and include a single line saying - ``help'' in the body of your message. ! <descrip> ! <tag/announce/ For announcements about or on FreeBSD. ! <tag/hackers/ Useful for persons wishing to work on the internals. ! <tag/questions/ General questions on FreeBSD. ! <tag/bugs/ Where bugs should be sent. ! <tag/SCSI/ Mailing list for SCSI developers. ! <tag/current/ This is the mailing list for communications ! between the developers and users of freebsd-current. It also ! carries announcements and discussions on current. <tt ! /Required/ reading for anyone using freebsd-current! ! <tag/security/ For issues dealing with system security. ! <tag/platforms/ Deals with ports to non-Intel platforms. ! <tag/ports/ Discussion of the Ports collection. ! <tag/fs/ Discussion of FreeBSD Filesystems. ! <tag/hardware/ Discussion on hardware requirements for ! FreeBSD. ! <tag/committers/ All CVS commit messages ! <tag/chat/ Miscellaneous chit-chat that does not belong ! anywhere else, humour, etc. ! <tag/hubs/ This the mailing-list for all of the generous ! people who manage the ``regional'' part of the <tt/freebsd.org/ ! domain. ! <tag/users-groups/ For the local area Users Groups coordinators. ! </descrip> ! <p> ! The FreeBSD-commit list has been broken up into groups dealing ! with different areas of interest. Please see the FreeBSD mailing ! list FAQ in: ! <url url="http://www.freebsd.org/How/handbook/eresources:mail.html" name="Handbook entry on mailing-lists"> ! <p> <sect1> ! <heading>How can I get on the mailing lists?</heading> ! <p> ! Example: ! <p> ! To subscribe to the <tt/questions/ list, you'll to send a message ! containing the following command in the <bf/body/ of the message ! (the subject will be ignored): ! <verb> ! subscribe questions john.smith@foo.bar (John Smith) ! </verb> <p> - Unsubscribing is just as easy:- - <verb> - unsubscribe questions john.smith@foo.bar (John Smith) - </verb> - Just remember to send your request - to - <url url="mailto:Majordomo@FreeBSD.ORG" name="the mail administrator"> - and <bf/not/ to the list itself! (The last thing the subscribed - users want to see is administrative requests...) <sect1> <heading>What FreeBSD news groups are available?</heading> <p> ! There are two newsgroups currently dedicated to FreeBSD: ! <descrip> ! <tag/comp.unix.bsd.freebsd.announce/ For announcements ! <tag/comp.unix.bsd.freebsd.misc/ General discussion ! </descrip> ! The following newsgroups may also be of interest to ! general BSD enthusiasts: ! <descrip> ! <tag><tt/comp.unix.bsd/</tag> ! General BSD topics ! </descrip> ! <tt>/usr/ports/news</tt> contains a number of ready-ported ! programs not only for reading Usenet News, but even setting ! up and running your own News server! You'll find trn, TIN, ! Cnews, INN and others there. ! ! For French-speaking people, the <tt/fr.comp.os.bsd/ group is for ! you; there is also a Japanese newsgroup, <tt /fj.os.bsd.freebsd/. ! If you do not receive these newsgroups, ask your system ! administrator to get them for you. ! </sect1> ! <sect1> <heading>Is there anything about FreeBSD on IRC (Internet Relay Chat) ?</heading> <p> --- 280,298 ---- Fax: +44 01892 667473<newline> (Do not dial the leading zero if calling from outside the UK). ! <sect1> ! <heading>Where do I find info on the mailing lists?</heading> ! <p> ! You can find full information in the <url url="../handbook/eresources#mail.html" name="Handbook entry on mailing-lists."> <p> <sect1> <heading>What FreeBSD news groups are available?</heading> <p> ! You can find full information in the <url url="../handbook/eresources:news.html" name="Handbook entry on newsgroups."> ! <sect1> <heading>Is there anything about FreeBSD on IRC (Internet Relay Chat) ?</heading> <p> *************** *** 386,394 **** even better, join) on the <tt>doc</tt> mailing list: <url url="mailto:doc@FreeBSD.ORG" name="<doc@FreeBSD.ORG>">. ! A FreeBSD ``handbook'' is being created, and can be found as: ! ! <url url="../handbook/handbook.html" name="the FreeBSD Handbook"> Note that this is a work in progress, and so parts may be incomplete. However, as FreeBSD 2.X is based upon Berkeley 4.4BSD-Lite, most --- 317,323 ---- even better, join) on the <tt>doc</tt> mailing list: <url url="mailto:doc@FreeBSD.ORG" name="<doc@FreeBSD.ORG>">. ! A FreeBSD ``handbook'' is availible, and can be found as: <url url="../handbook/handbook.html" name="the FreeBSD Handbook">. Note that this is a work in progress, and so parts may be incomplete. However, as FreeBSD 2.X is based upon Berkeley 4.4BSD-Lite, most *************** *** 454,477 **** <sect1> <heading>Other sources of information.</heading> <p> ! One good source of additional information is the ! ``[comp.unix.bsd] NetBSD, FreeBSD, and 386BSD (0.1) ! FAQ''. Much of the information is relevant to FreeBSD, and this ! FAQ is posted around twice a month to the following newsgroups: ! ! <verb> ! comp.unix.bsd.netbsd.announce ! comp.unix.bsd.freebsd.announce ! comp.answers ! news.answers ! </verb> ! ! If you have WWW access, the FreeBSD home page is at: <url url="http://www.freebsd.org/" name="Main FreeBSD page"> The FreeBSD handbook has a pretty complete ! <url url="http://www.FreeBSD.ORG/How/handbook/bibliography.html" name="Bibliography"> <sect> <heading>Installation</heading> --- 383,394 ---- <sect1> <heading>Other sources of information.</heading> <p> ! If you have WWW access, the FreeBSD home page is at: <url url="http://www.freebsd.org/" name="Main FreeBSD page"> The FreeBSD handbook has a pretty complete ! <url url="../handbook/bibliography.html" name="Bibliography"> <sect> <heading>Installation</heading> *************** *** 504,510 **** of the FreeBSD installation (lucky you!), the simplest way to install FreeBSD is to download <url ! url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/2.1.5-RELEASE/floppies/boot.flp" name="the boot image,"> make a boot floppy, boot with it and watch it pull down all the necessary files. Depending on connection speed and how much of FreeBSD you wish to install, this could take several hours --- 421,427 ---- of the FreeBSD installation (lucky you!), the simplest way to install FreeBSD is to download <url ! url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/2.1.6-RELEASE/floppies/boot.flp" name="the boot image,"> make a boot floppy, boot with it and watch it pull down all the necessary files. Depending on connection speed and how much of FreeBSD you wish to install, this could take several hours *************** *** 524,558 **** tape or over a network via SLIP, PPP, NFS, PLIP and Ethernet. For further information, please see ! <url url="http://www.freebsd.org/handbook/install.html" name="Handbook entry on installing FreeBSD."> <sect1> <heading>Where are the instructions for installing FreeBSD?</heading> <p> ! Installation instructions can be found as: ! ! <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/2.1.5-RELEASE/INSTALL" ! name="INSTALL from 2.1.5R"> ! ! Release notes are also available as: ! ! <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/2.1.5-RELEASE/RELNOTES" ! name="RELNOTES from 2.1.5R"> - On the CDROM, the following files are in the top-most directory: - - <verb> - HARDWARE.TXT -- Hardware information - INSTALL -- Installation instructions - README.TXT -- Basic README file - RELNOTES -- Release notes - </verb> - <sect1> <heading>What do I need to run FreeBSD?</heading> <p> ! you'll need a 386 or better PC, with 4 MB or more of RAM and at least 60 MB of hard disk space. It can run with a low end MDA card but to run X11R6, a VGA or better video card is needed. --- 441,458 ---- tape or over a network via SLIP, PPP, NFS, PLIP and Ethernet. For further information, please see ! <url url="../handbook/install.html" name="Handbook entry on installing FreeBSD."> <sect1> <heading>Where are the instructions for installing FreeBSD?</heading> <p> ! Installation instructions can be found in the <url url="../handbook/install.html" name="Handbook install section."> <sect1> <heading>What do I need to run FreeBSD?</heading> <p> ! You'll need a 386 or better PC, with 4 MB or more of RAM and at least 60 MB of hard disk space. It can run with a low end MDA card but to run X11R6, a VGA or better video card is needed. *************** *** 561,570 **** <sect1> <heading>I have only 4 MB of RAM. Can I install FreeBSD?</heading> <p> ! The latest version of FreeBSD (2.1.5) will install on a 4MB ! system, provided you use the <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/2.1.5-RELEASE/floppies/boot4.flp" ! name="special boot floppy for 4MB systems."> FreeBSD 2.1.5 does not install in 4 MB. To be exact: it does not install with 640 kB base + 3 MB extended memory. If your --- 461,473 ---- <sect1> <heading>I have only 4 MB of RAM. Can I install FreeBSD?</heading> <p> ! FreeBSD 2.1.5 is the last version of FreeBSD that will install on a 4MB system. Other newer versions of FreeBSD like 2.2 cannot install on a 4 MB system. ! ! All versions of FreeBSD including 2.2 WILL run in 4MB of ram. You can add extra memory for the install process. After the system is up an running, you can go back to 4MB if you want. ! ! Use <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/2.1.5-RELEASE/floppies/boot4.flp" ! name="special boot floppy for 4MB computers from FreeBSD 2.1.5"> FreeBSD 2.1.5 does not install in 4 MB. To be exact: it does not install with 640 kB base + 3 MB extended memory. If your *************** *** 1181,1187 **** </verb> <p> ! See the <url url="http://www.freebsd.org/handbook/kernelconfig.html" name="Handbook entry on configuring the kernel"> if you've no experience with building kernels. --- 1084,1090 ---- </verb> <p> ! See the <url url="../handbook/kernelconfig.html" name="Handbook entry on configuring the kernel"> if you've no experience with building kernels. *************** *** 1344,1350 **** <heading>I am about to buy a new machine. What do you recommend?</heading> <p> ! See the <htmlurl url="handbook/hw.html" name="hardware section"> of the handbook. --> <sect1> --- 1247,1253 ---- <heading>I am about to buy a new machine. What do you recommend?</heading> <p> ! See the <htmlurl url="../handbook/hw.html" name="hardware section"> of the handbook. --> <sect1> *************** *** 1396,1401 **** --- 1299,1340 ---- the section <ref id="bigram" name="on 32 MB machines">. This is a problem that occurs with the Vesa-Local Buslogic SCSI cards. + <sect1> + <heading>FreeBSD does not recognise my on-board AIC-7xxx EISA SCSI in an HP Netserver</heading> + <p> + This is basically a known problem. The EISA on-board SCSI controller + in the HP Netserver machines occupies EISA slot number 11, so all + the ``true'' EISA slots are in front of it. Alas, the address space + for EISA slots >= 10 collides with the address space assigned to PCI, + and FreeBSD's auto-configuration currently cannot handle this + situation very well. + + So now, the best you can do is to pretend there were no address + range clash :), go right ahead and edit the file + <tt>/sys/i386/eisa/eisaconf.h</tt>. Look for a line defining the + macro <tt/EISA_SLOTS/, and bump the number it's defining to 12. + Configure and compile a kernel, as described in the + <url url="../handbook/kernelconfig.html" + name="Handbook entry on configuring the kernel">. + + Of course, this does present you a chicken-and-egg problem when + installing on such a machine. In order to work around this + problem, a special hack is available inside <em>UserConfig</em>. + Do not use the ``visual'' interface, but the plain command-line + interface there. Simply type + <verb> + eisa 12 + quit + </verb> + + at the prompt, and install your system as usual. Don't forget + to install the kernel source distribution, since you need to + build a custom kernel, or otherwise you would have to repeat the + described procedure at each boot! <tt/dset(8)/ doesn't save this + change for you. + + Hopefully, future version will have a proper fix for this problem. + <sect> <heading>Commercial Applications</heading> *************** *** 1814,1829 **** to run DOS text mode applications. It requires the X Window System (provided as XFree86 3.1.2). - <sect1> - <heading>My programs occasionally die with ``Signal 11'' errors.</heading> - <p> - This can be caused by bad hardware (memory, motherboard, etc.). - Try running a memory-testing program on your PC. Note that, even - though every memory testing program you try will report your - memory as being fine, it's possible for slightly marginal memory - to pass all memory tests, yet fail under operating conditions - (such as during busmastering DMA from a SCSI controller like the - Adaptec 1542). <sect1> <heading>Help! X Window menus and dialog boxes don't work right!</heading> --- 1753,1758 ---- *************** *** 2026,2061 **** <p> SUP stands for Software Update Protocol, and was developed by CMU ! for keeping their development trees in sync. We use it to keep remote sites in sync with our central development sources. ! Unless you have direct Internet connectivity, and don't care too ! much about the cost/duration of the sessions, you shouldn't use ! sup. For those ``low/expensive-bandwidth'' applications, we have ! developed <tt/CTM/, see the section <ref id="ctm" name="on CTM"> ! for more about that. ! ! To use it, you need to have direct Internet connectivity (not ! just mail or news). First, pick up the <tt/sup.tgz/ package ! from: ! ! <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/packages/sup.tgz" ! name="The SUP package"> ! ! Second, read the <url ! url="http://www.freebsd.org/How/handbook/sup.html" ! name="Handbook entry on SUP"> ! ! This file describes how to setup sup on your machine. You may ! also want to look at ! ! <tt>/usr/src/share/examples/sup/*-supfile</tt>, or you may grab ! updated supfiles from: ! ! <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FAQ/extras" ! name="Updated SUP files"> ! ! which are a set of supfiles for supping from <tt/FreeBSD.ORG/. <sect1> <heading>How cool is FreeBSD?</heading> --- 1955,1965 ---- <p> SUP stands for Software Update Protocol, and was developed by CMU ! for keeping their development trees in sync. We used it to keep remote sites in sync with our central development sources. ! SUP is not bandwidth friendly, and has been retired. The current recommended method to keep your sources up to date is <url url="../handbook/cvsup.html" ! name="Handbook entry on CVSup"> <sect1> <heading>How cool is FreeBSD?</heading> *************** *** 2156,2162 **** Yes, you can do this <tt /without/ downloading the whole source tree by using the <url ! url="http://www.freebsd.org/How/handbook/handbook/ctm.html" name="CTM facility."> <sect1> --- 2060,2066 ---- Yes, you can do this <tt /without/ downloading the whole source tree by using the <url ! url="../handbook/ctm.html" name="CTM facility."> <sect1> *************** *** 2178,2191 **** </verb> <sect1> - <heading><XXX> I'd like to browse the system dumps after a panic.</heading> - - <sect1> <heading>I've written a kernel extension, who do I send it to?</heading> <p> Please take a look at: ! <url url="http://www.FreeBSD.ORG/How/handbook/submitters.html" name="The Handbook entry on how to submit code."> And thanks for the thought! --- 2082,2092 ---- </verb> <sect1> <heading>I've written a kernel extension, who do I send it to?</heading> <p> Please take a look at: ! <url url="../handbook/submitters.html" name="The Handbook entry on how to submit code."> And thanks for the thought! *************** *** 2574,2580 **** Please have a look at the Handbook entry on printing. It should cover most of your problem. See the <url ! url="http://www.freebsd.org/How/handbook/printing.html" name="Handbook entry on printing."> </sect1> --- 2475,2481 ---- Please have a look at the Handbook entry on printing. It should cover most of your problem. See the <url ! url="../handbook/printing.html" name="Handbook entry on printing."> </sect1> *************** *** 2708,2714 **** network, and reads the necessary files from a server instead of its hard disk. For full details, please read ! <url url="http://www.FreeBSD.ORG/How/handbook/diskless.html" name="the Handbook entry on diskless booting"> <sect1> --- 2609,2615 ---- network, and reads the necessary files from a server instead of its hard disk. For full details, please read ! <url url="../handbook/diskless.html" name="the Handbook entry on diskless booting"> <sect1> *************** *** 2772,2784 **** handbook in <tt>/usr/share/doc/handbook</tt> or use the following links: ! <url url="http://www.FreeBSD.ORG/How/handbook/slips.html" name="Handbook entry on SLIP (server side)"> ! <url url="http://www.FreeBSD.ORG/How/handbook/slipc.html" name="Handbook entry on SLIP (client side)"> ! <url url="http://www.FreeBSD.ORG/How/handbook/ppp.html" name="Handbook entry on PPP (kernel version)"> ! <url url="http://www.FreeBSD.ORG/How/handbook/userppp.html" name="Handbook entry on PPP (user-mode version)"> <sect1> --- 2673,2685 ---- handbook in <tt>/usr/share/doc/handbook</tt> or use the following links: ! <url url="../handbook/slips.html" name="Handbook entry on SLIP (server side)"> ! <url url="../handbook/slipc.html" name="Handbook entry on SLIP (client side)"> ! <url url="../handbook/ppp.html" name="Handbook entry on PPP (kernel version)"> ! <url url="../handbook/userppp.html" name="Handbook entry on PPP (user-mode version)"> <sect1> *************** *** 2838,2844 **** See <url ! url="http://www.freebsd.org/How/handbook/nfs.html" name="the Handbook entry on NFS"> for more information on --- 2739,2745 ---- See <url ! url="../handbook/nfs.html" name="the Handbook entry on NFS"> for more information on *************** *** 2930,3144 **** Zynx ZX342 </code> </sect1> - <sect1> - <heading>Why do I have to use the FQDN for hosts on my site?</heading> - <p> - You will probably find that the host is actually in a different - domain; for example, if you are in foo.bar.edu and you wish to reach - a host called ``mumble'' in the bar.edu domain, you will have to - refer to it by the fully-qualified domain name, ``mumble.bar.edu'', - instead of just ``mumble''. - <p> - Traditionally, this was allowed by BSD BIND resolvers. However - the current version of <em>BIND</em> that ships with FreeBSD - no longer provides default abbreviations for non-fully - qualified domain names other than the domain you are in. - So an unqualified host <tt>mumble</tt> must either be found - as <tt>mumble.foo.bar.edu</tt>, or it will be searched for - in the root domain. - <p> - This is different from the previous behaviour, where the - search continued across <tt>mumble.bar.edu</tt>, and - <tt>mumble.edu</tt>. Have a look at RFC 1535 for why this - was considered bad practice, or even a security hole. - <p> - As a good workaround, you can place the line - <p><tt> - search foo.bar.edu bar.edu - </tt><p> - instead of the previous - - <p><tt> - domain foo.bar.edu - </tt><p> - into your <tt>/etc/resolv.conf</tt>. However, make sure - that the search order does not go beyond the ``boundary - between local and public administration'', as RFC 1535 - calls it. - - </sect1> - - <sect1><heading>Sendmail says ``mail loops back to myself''</heading> - <p> - This is answered in the sendmail FAQ as follows:- - <verb> - * I'm getting "Local configuration error" messages, such as: - - 553 relay.domain.net config error: mail loops back to myself - 554 <user@domain.net>... Local configuration error - - How can I solve this problem? - - You have asked mail to the domain (e.g., domain.net) to be - forwarded to a specific host (in this case, relay.domain.net) - by using an MX record, but the relay machine doesn't recognize - itself as domain.net. Add domain.net to /etc/sendmail.cw - (if you are using FEATURE(use_cw_file)) or add "Cw domain.net" - to /etc/sendmail.cf. - </verb> - <p> - The sendmail FAQ is in <tt>/usr/src/usr.sbin/sendmail</tt> - and is recommended reading if you want to do any - ``tweaking'' of your mail setup. - - <sect1> - <heading>How do I use sendmail for mail delivery with UUCP?</heading> - - <p> - The sendmail configuration that ships with FreeBSD is - suited for sites that connect directly to the Internet. - Sites that wish to exchange their mail via UUCP must install - another sendmail configuration file. - - <p> - Tweaking <tt>/etc/sendmail.cf</tt> manually is considered - something for purists. Sendmail version 8 comes with a - new approach of generating config files via some <tt>m4</tt> - preprocessing, where the actual hand-crafted configuration - is on a higher abstraction level. You should use the - configuration files under - - <verb> - /usr/src/usr.sbin/sendmail/cf - </verb> - - If you didn't install your system with full sources, - the sendmail config stuff has been - broken out into a separate source distribution tarball just - for you. Assuming you've got your CD-ROM mounted, do: - - <verb> - cd /usr/src - tar -xvzf /cdrom/dists/src/ssmailcf.aa - </verb> - - Don't panic, this is only a few hundred kilobytes in size. - The file <tt>README</tt> in the <tt>cf</tt> directory can - serve as a basic introduction to m4 configuration. - - <p> - For UUCP delivery, you are best advised to use the - <em>mailertable</em> feature. This constitutes a database - that sendmail can use to base its routing decision upon. - - <p> - First, you have to create your <tt>.mc</tt> file. The - directory <tt>/usr/src/usr.sbin/sendmail/cf/cf</tt> is the - home of these files. Look around, there are already a few - examples. Assuming you have named your file <tt>foo.mc</tt>, - all you need to do in order to convert it into a valid - <tt>sendmail.cf</tt> is: - - <verb> - cd /usr/src/usr.sbin/sendmail/cf/cf - make foo.cf - cp foo.cf /etc/sendmail.cf - </verb> - - A typical <tt>.mc</tt> file might look like: - - <verb> - include(`../m4/cf.m4') - VERSIONID(`Your version number') - OSTYPE(bsd4.4) - - FEATURE(nodns) - FEATURE(nocanonify) - FEATURE(mailertable) - - define(`UUCP_RELAY', your.uucp.relay) - define(`UUCP_MAX_SIZE', 200000) - - MAILER(local) - MAILER(smtp) - MAILER(uucp) - - Cw your.alias.host.name - Cw youruucpnodename.UUCP - </verb> - - The <em>nodns</em> and <em>nocanonify</em> features will - prevent any usage of the DNS during mail delivery. The - <em>UUCP_RELAY</em> clause is needed for bizarre reasons, - don't ask. Simply put an Internet hostname there that - is able to handle .UUCP pseudo-domain addresses; most likely, - you will enter the mail relay of your ISP there. - - <p> - Once you've got this, you need this file called - <tt>/etc/mailertable</tt>. A typical example of this - gender again: - - <verb> - # - # makemap hash /etc/mailertable.db < /etc/mailertable - # - horus.interface-business.de uucp-dom:horus - .interface-business.de uucp-dom:if-bus - interface-business.de uucp-dom:if-bus - .heep.sax.de smtp8:%1 - horus.UUCP uucp-dom:horus - if-bus.UUCP uucp-dom:if-bus - . uucp-dom:sax - </verb> - - As you can see, this is part of a real-life file. The first - three lines handle special cases where domain-addressed mail - should not be sent out to the default route, but instead to - some UUCP neighbour in order to ``shortcut'' the delivery - path. The next line handles mail to the local Ethernet - domain that can be delivered using SMTP. Finally, the UUCP - neighbours are mentioned in the .UUCP pseudo-domain notation, - to allow for a ``uucp-neighbour!recipient'' override of the - default rules. The last line is always a single dot, matching - everything else, with UUCP delivery to a UUCP neighbour that - serves as your universal mail gateway to the world. All of - the node names behind the <tt>uucp-dom:</tt> keyword must - be valid UUCP neighbours, as you can verify using the - command <tt>uuname</tt>. - - <p> - As a reminder that this file needs to be converted into a - DBM database file before being usable, the command line to - accomplish this is best placed as a comment at the top of - the mailertable. You always have to execute this command - each time you change your mailertable. - - <p> - Final hint: if you are uncertain whether some particular - mail routing would work, remember the <tt>-bt</tt> option to - sendmail. It starts sendmail in <em>address test mode</em>; - simply enter ``0 '', followed by the address you wish to - test for the mail routing. The last line tells you the used - internal mail agent, the destination host this agent will be - called with, and the (possibly translated) address. Leave - this mode by typing Control-D. - - <verb> - j@uriah 191% sendmail -bt - ADDRESS TEST MODE (ruleset 3 NOT automatically invoked) - Enter <ruleset> <address> - > 0 foo@interface-business.de - rewrite: ruleset 0 input: foo @ interface-business . de - ... - rewrite: ruleset 0 returns: $# uucp-dom $@ if-bus $: foo \ - < @ interface-business . de > - > ^D - j@uriah 192% - </verb> - - - </sect1> <sect1> <heading>``Permission denied'' for all networking operations.</heading> --- 2831,2836 ---- *************** *** 3263,3307 **** <p> Not yet. You'll have to use a different irq for each card. - <sect1> - <heading>How can I set the default serial parameters for a port?</heading> - <p> - The <tt/ttydX/ (or <tt/cuaaX/) device is the regular device - you'll want to open for your applications. When a process opens - the device, it'll have a default set of terminal I/O settings. - You can see these settings with the command - <verb> - stty -a -f /dev/ttyd1 - </verb> - - When you change the settings to this device, the settings are in - effect until the device is closed. When it's reopened, it goes - back to the default set. To make changes to the default set, you - can open and adjust the settings of the ``initial state'' device. - For example, to turn on <tt/CLOCAL/ mode, 8 bits, and - <tt>XON/XOFF</tt> flow control by default for ttyd5, do: - <verb> - stty -f /dev/ttyid5 clocal cs8 ixon ixoff - </verb> - - A good place to do this is in <tt>/etc/rc.serial</tt>. Now, an - application will have these settings by default when it opens - <tt/ttyd5/. It can still change these settings to its liking, - though. - - You can also prevent certain settings from being changed by an - application by making adjustments to the ``lock state'' device. - For example, to lock the speed of <tt/ttyd5/ to 57600 bps, do - <verb> - stty -f /dev/ttyld5 57600 - </verb> - - Now, an application that opens <tt/ttyd5/ and tries to change the - speed of the port will be stuck with 57600 bps. - - Naturally, you should make the initial state and lock state - devices writable only by <tt/root/. The <tt/MAKEDEV/ script does - <bf/NOT/ do this when it creates the device entries. <sect1> <heading>How can I enable dialup logins on my modem?</heading> --- 2955,2960 ---- *************** *** 3322,3331 **** <verb> AT &C1 &D3 &K3 &Q6 S0=1 &W </verb> ! See the section <ref id="direct-at" name="on sending AT ! commands"> below for information on how to make these settings ! without resorting to an MS-DOS terminal program. ! Next, make an entry in <tt>/etc/ttys</tt> for the modem. This file lists all the ports on which the operating system will await logins. Add a line that looks something like this: --- 2975,2981 ---- <verb> AT &C1 &D3 &K3 &Q6 S0=1 &W </verb> ! Next, make an entry in <tt>/etc/ttys</tt> for the modem. This file lists all the ports on which the operating system will await logins. Add a line that looks something like this: *************** *** 3365,3645 **** 747 ?? I 0:00.04 /usr/libexec/getty std.57600 ttyd1 </verb> - <sect1> - <heading>How can I connect a dumb terminal to my FreeBSD box?</heading> - <p> - If you're using another computer as a terminal into your FreeBSD - system, get a null modem cable to go between the two serial - ports. If you're using an actual terminal, see its accompanying - instructions. - - Then, modify <tt>/etc/ttys</tt>, like above. For example, if - you're hooking up a WYSE-50 terminal to the fifth serial port, - use an entry like this: - <verb> - ttyd4 "/usr/libexec/getty std.38400" wyse50 on secure - </verb> - This example shows that the port on <tt>/dev/ttyd4</tt> has a - wyse50 terminal connected at 38400 bps with no parity - (<tt/std.38400/ from <tt>/etc/gettytab</tt>) and <tt/root/ logins - are allowed (secure). - - <sect1> - <heading>Why can't I run <tt/tip/ or <tt/cu/?</heading> - <p> - On your system, the programs <tt/tip/ and <tt/cu/ are probably - executable only by <tt/uucp/ and group <tt/dialer/. You can use - the group <tt/dialer/ to control who has access to your modem or - remote systems. Just add yourself to group dialer. - - Alternatively, you can let everyone on your system run <tt/tip/ - and <tt/cu/ by typing: - <verb> - chmod 4511 /usr/bin/tip - </verb> - You don't have to run this command for <tt/cu/, since <tt/cu/ is - just a hard link to <tt/tip/. - - <sect1> - <heading>My stock Hayes modem isn't supported---what can I do?</heading> - <p> - Actually, the man page for <tt/tip/ is out of date. There is a - generic Hayes dialer already built in. Just use - ``<tt/at=hayes/'' in your <tt>/etc/remote</tt> file. - - The Hayes driver isn't smart enough to recognize some of the - advanced features of newer modems---messages like <tt/BUSY/, - <tt/NO DIALTONE/, or <tt/CONNECT 115200/ will just confuse it. - You should turn those messages off when you use <tt/tip/ (using - <tt/ATX0&W/). - - Also, the dial timeout for <tt/tip/ is 60 seconds. Your modem - should use something less, or else tip will think there's a - communication problem. Try <tt/ATS7=45&W/. - - Actually, as shipped <tt/tip/ doesn't yet support it fully. The - solution is to edit the file <tt/tipconf.h/ in the directory - <tt>/usr/src/usr.bin/tip/tip</tt> Obviously you need the source - distribution to do this. - - Edit the line ``<tt/#define HAYES 0/'' to ``<tt/#define HAYES - 1/''. Then ``<tt/make/'' and ``<tt/make install/''. Everything - works nicely after that. - - <sect1> - <heading>How am I expected to enter these AT commands?<label id="direct-at"></heading> - <p> - Make what's called a ``<tt/direct/'' entry in your - <tt>/etc/remote</tt> file. For example, if your modem's hooked - up to the first serial port, <tt>/dev/cuaa0</tt>, then put in the - following line: - <verb> - cuaa0:dv=/dev/cuaa0:br#19200:pa=none - </verb> - Use the highest bps rate your modem supports in the br - capability. Then, type ``<tt/tip cuaa0/'' and you'll be - connected to your modem. - - If there is no <tt>/dev/cuaa0</tt> on your system, do this: - <verb> - cd /dev - MAKEDEV cuaa0 - </verb> - <p> - Or use cu as root with the following command: - <verb> - cu -l``line'' -s``speed'' - </verb> - with line being the serial port (e.g.<tt>/dev/cuaa0</tt>) - and speed being the speed (e.g.<tt>57600</tt>). - When you are done entering the AT commands hit <tt>~.</tt> to exit. - - <sect1> - <heading>The <tt/@/ sign for the pn capability doesn't work!</heading> - <p> - The <tt/@/ sign in the phone number capability tells tip to look in - <tt>/etc/phones</tt> for a phone number. But the <tt/@/ sign is - also a special character in capability files like - <tt>/etc/remote</tt>. Escape it with a backslash: - <verb> - pn=\@ - </verb> - - <sect1> - <heading>How can I dial a phone number on the command line?</heading> - <p> - Put what's called a ``<tt/generic/'' entry in your - <tt>/etc/remote</tt> file. For example: - <verb> - tip115200|Dial any phone number at 115200 bps:\ - :dv=/dev/cuaa0:br#115200:at=hayes:pa=none:du: - tip57600|Dial any phone number at 57600 bps:\ - :dv=/dev/cuaa0:br#57600:at=hayes:pa=none:du: - </verb> - - Then you can things like ``<tt/tip -115200 5551234/''. If you - prefer <tt/cu/ over <tt/tip/, use a generic cu entry: - <verb> - cu115200|Use cu to dial any number at 115200bps:\ - :dv=/dev/cuaa1:br#57600:at=hayes:pa=none:du: - </verb> - and type ``<tt/cu 5551234 -s 115200/''. - - <sect1> - <heading>Do I have to type in the bps rate every time I do that?</heading> - <p> - Put in an entry for <tt/tip1200/ or <tt/cu1200/, but go ahead and - use whatever bps rate is appropriate with the br - capability. <tt/tip/ thinks a good default is 1200 bps which is - why it looks for a ``<tt/tip1200/'' entry. You don't have to use - 1200 bps, though. - - <sect1> - <heading>I access a number of hosts through a terminal server.</heading> - <p> - Rather than waiting until you're connected and typing - ``<tt/CONNECT <host>/'' each time, use tip's <tt/cm/ - capability. For example, these entries in - <tt>/etc/remote</tt>: - <verb> - pain|pain.deep13.com|Forrester's machine:\ - :cm=CONNECT pain\n:tc=deep13: - muffin|muffin.deep13.com|Frank's machine:\ - :cm=CONNECT muffin\n:tc=deep13: - deep13:Gizmonics Institute terminal server:\ - :dv=/dev/cua02:br#38400:at=hayes:du:pa=none:pn=5551234: - </verb> - - will let you type ``<tt/tip pain/'' or ``<tt/tip muffin/'' to - connect to the hosts pain or muffin; and ``<tt/tip deep13/'' to - get to the terminal server. - - <sect1> - <heading>Can tip try more than one line for each site?</heading> - <p> - This is often a problem where a university has several modem lines - and several thousand students trying to use them... - <p> - Make an entry for your university in <tt>/etc/remote</tt> - and use <tt>\@</tt> for the <tt/pn/ capability: - <verb> - big-university:\ - :pn=\@:tc=dialout - dialout:\ - :dv=/dev/cuaa3:br#9600:at=courier:du:pa=none: - </verb> - - Then, list the phone numbers for the university in - <tt>/etc/phones</tt>: - <verb> - big-university 5551111 - big-university 5551112 - big-university 5551113 - big-university 5551114 - </verb> - - <tt/tip/ will try each one in the listed order, then give up. If - you want to keep retrying, run <tt/tip/ in a while loop. - - <sect1> - <heading>Why do I have to hit CTRL+P twice to send CTRL+P once?</heading> - <p> - CTRL+P is the default ``force'' character, used to tell <tt/tip/ - that the next character is literal data. You can set the force - character to any other character with the <tt/~s/ escape, which - means ``set a variable.'' - - Type ``<tt/~sforce=<single-char>/'' followed by a newline. - <tt/<single-char>/ is any single character. If you leave - out <tt/<single-char>/, then the force character is the nul - character, which you can get by typing CTRL+2 or CTRL+SPACE. A - pretty good value for <tt/<single-char>/ is SHIFT+CTRL+6, - which I've seen only used on some terminal servers. - - You can have the force character be whatever you want by - specifying the following in your <tt>$HOME/.tiprc</tt> - file: - <verb> - force=<single-char> - </verb> - - <sect1> - <heading>Suddenly everything I type is in UPPER CASE??</heading> - <p> - You must've pressed CTRL+A, <tt/tip/'s ``raise character,'' - specially designed for people with broken caps-lock keys. Use - <tt/~s/ as above and set the variable ``raisechar'' to something - reasonable. In fact, you can set it to the same as the force - character, if you never expect to use either of these features. - - Here's a sample .tiprc file perfect for Emacs users who need to - type CTRL+2 and CTRL+A a lot: - <verb> - force=^^ - raisechar=^^ - </verb> - The ^^ is SHIFT+CTRL+6. - - <sect1> - <heading>How can I do file transfers with <tt/tip/?</heading> - <p> - If you're talking to another UNIX system, you can send and - receive files with <tt/~p/ (put) and <tt/~t/ (take). These - commands run ``<tt/cat/'' and ``<tt/echo/'' on the remote system - to accept and send files. The syntax is: - <verb> - ~p <local-file> [<remote-file>] - ~t <remote-file> [<local-file>] - </verb> - - There's no error checking, so you probably should use another - protocol, like zmodem. - - <sect1> - <heading>How can I run zmodem with <tt/tip/?</heading> - <p> - To receive files, start the sending program on the remote end. - Then, type ``<tt/~C rz/'' to begin receiving them locally. - - To send files, start the receiving program on the remote end. - Then, type ``<tt/~C sz <files>/'' to send them to the - remote system. - - </sect> - <sect> <heading>ACKNOWLEDGMENTS</heading> <p> ! <code> ! If you see a problem with this FAQ, or wish to submit an entry, ! please mail us at <FAQ@FreeBSD.ORG>. We appreciate your ! feedback, and cannot make this a better FAQ without your help! ! ! ! FreeBSD Core Team ! </code> ! ! <descrip> ! <tag/James Raynard/ ! Acting FAQ caretaker ! <tag/Ollivier Robert/ ! FreeBSD FAQ maintenance man ! <tag/Gary Clark II/ ! FreeBSD Doc Team ! <tag/Jordan Hubbard/ ! Janitorial services (I don't do windows) ! <tag/Doug White/ ! Services above and beyond the call of duty on freebsd-questions ! <tag/Joerg Wunsch/ ! Services above and beyond the call of duty on Usenet ! <tag/Garrett Wollman/ ! Networking and formatting ! <tag/Jim Lowe/ ! Multicast information ! <tag/The FreeBSD Team/ ! Kvetching, moaning, submitting data ! </descrip> ! And to any others we've forgotten, apologies and heartfelt thanks! </article> --- 3015,3025 ---- 747 ?? I 0:00.04 /usr/libexec/getty std.57600 ttyd1 </verb> <sect> <heading>ACKNOWLEDGMENTS</heading> <p> ! If you would like more information on the people behind the scenes, check out the <url url="../handbook/contrib.html" name="Handbook section on contributor list."> ! </article> f known (multiple lines)> >Release-Note: >Audit-Trail: Responsible-Changed-From-To: freebsd-bugs->freebsd-doc Responsible-Changed-By: hoek Responsible-Changed-When: Mon Apr 13 08:28:42 PDT 1998 Responsible-Changed-Why: -doc related PR. NB: this includes patches to the LinuxDoc sgml. Part of this may soon become irrelevant if not handled soon. State-Changed-From-To: open->closed State-Changed-By: steve State-Changed-When: Sun May 31 08:13:46 PDT 1998 State-Changed-Why: Doug White, our FAQ-meister, says that most of these changes squeaked in before the FAQ was broken into many little sections. If we overlooked anything that still needs to be included, please let us know. Thanks. >Unformatted: