From owner-freebsd-doc Wed Jul 26 03:35:08 1995 Return-Path: doc-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id DAA14663 for doc-outgoing; Wed, 26 Jul 1995 03:35:08 -0700 Received: from ccslinux.dlsu.edu.ph (linux1.dlsu.edu.ph [165.220.8.15]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id DAA14647 for ; Wed, 26 Jul 1995 03:34:49 -0700 Received: by ccslinux.dlsu.edu.ph (Linux Smail3.1.28.1 #13) Sender: doc-owner@FreeBSD.org Precedence: bulk id m0sb3oM-000A4zC; Wed, 26 Jul 95 18:35 GMT+0800 Sender: humprey@linux1.dlsu.edu.ph (Humprey Sy) Date: Wed, 26 Jul 1995 18:35:32 +48000 From: "Humprey C. Sy" Sender: "Humprey C. Sy" Reply-To: "Humprey C. Sy" To: doc@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Hello! I am currently interested in FreeBSD. Actually, we are currently considering implementing our thesis (process migration) on FreeBSD platform. Do you possibly have any documentation on the design of the FreeBSD operating system, and where may I obtain this? Thanks! ----- Humprey Sy 4BSCS-ST De La Salle University humprey@linux1.dlsu.edu.ph From owner-freebsd-doc Wed Jul 26 18:29:14 1995 Return-Path: doc-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id SAA00904 for doc-outgoing; Wed, 26 Jul 1995 18:29:14 -0700 Received: from muse.microunity.com (muse1.microunity.com [192.216.206.2]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id SAA00898 for ; Wed, 26 Jul 1995 18:29:13 -0700 Received: from gaea.microunity.com by muse.microunity.com (4.1/ericm1.1) id AA23074; Wed, 26 Jul 95 18:28:42 PDT Received: from gallifrey (gallifrey.microunity.com) by gaea.microunity.com (4.1/muse1.3) id AA12559; Wed, 26 Jul 95 18:28:40 PDT Received: from localhost.microunity.com by gallifrey via SMTP (931110.SGI.ANONFTP/muse-sgi.2) for @gaea.microunity.com:doc@freebsd.org id AA11087; Wed, 26 Jul 95 18:28:40 -0700 Message-Id: <9507270128.AA11087@gallifrey> Date: Wed, 26 Jul 95 18:28:40 -0700 From: Deborah Bennett Organization: MicroUnity Systems Engineering, Inc. X-Mailer: Mozilla 1.1N (X11; I; IRIX 5.2 IP20) Mime-Version: 1.0 To: doc@freebsd.org Subject: Reconfiguring the Kernel X-Url: http://freefall.cdrom.com/How/ Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: doc-owner@freebsd.org Precedence: bulk Hi. I've just finished reconfiguring my own kernel for a FreeBSD 2.0.5 machine using the directions in the FAQ section of your html files (http://freefall.cdrom.com/How/faq/freebsd-faq-47.html#47) As this information stands, I believe that it's a good enough starting point that it should be linked or copied to Chapter 5 of the handbook, Reconfiguring the Kernel, which is currently empty. It could perhaps be a first section titled "Basic Instructions". -deborah bennett -- Deborah Gronke Bennett (WD5HJH) kernel and device drivers engineer deborah@microunity.com (408)-734-8100 MicroUnity Systems Eng., 255 Caspian Drive, Sunnyvale, CA 94089-1015 USA "Pick yourself up, dust yourself off, start all over again" Ginger Rogers in "Swingtime" From owner-freebsd-doc Thu Jul 27 09:30:29 1995 Return-Path: doc-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id JAA27691 for doc-outgoing; Thu, 27 Jul 1995 09:30:29 -0700 Received: from grendel.csc.smith.edu (grendel.csc.smith.edu [131.229.222.23]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id JAA27685 for ; Thu, 27 Jul 1995 09:30:26 -0700 Received: from localhost (jfieber@localhost) by grendel.csc.smith.edu (8.6.5/8.6.5) id MAA12180; Thu, 27 Jul 1995 12:32:18 -0400 From: jfieber@grendel.csc.smith.edu (John Fieber) Message-Id: <199507271632.MAA12180@grendel.csc.smith.edu> Subject: Re: Reconfiguring the Kernel To: deborah@gallifrey.microunity.com (Deborah Bennett) Date: Thu, 27 Jul 1995 12:32:18 -0400 (EDT) Cc: doc@freebsd.org In-Reply-To: <9507270128.AA11087@gallifrey> from "Deborah Bennett" at Jul 26, 95 06:28:40 pm Content-Type: text Content-Length: 503 Sender: doc-owner@freebsd.org Precedence: bulk Deborah Bennett writes: > Hi. I've just finished reconfiguring my own kernel for a FreeBSD 2.0.5 > machine using the directions in the FAQ section of your html files > (http://freefall.cdrom.com/How/faq/freebsd-faq-47.html#47) > As this information stands, I believe that it's a good enough starting point > that it should be linked or copied to Chapter 5 of the handbook, For a quick band-aid, I put a link to the FAQ. -john === jfieber@cs.smith.edu ========== Come up and be a kite! --K. Bush === From owner-freebsd-doc Thu Jul 27 17:09:28 1995 Return-Path: doc-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id RAA15045 for doc-outgoing; Thu, 27 Jul 1995 17:09:28 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id RAA15036 for ; Thu, 27 Jul 1995 17:09:22 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id RAA03550 for ; Thu, 27 Jul 1995 17:08:30 -0700 To: doc@freebsd.org Subject: Nik Clayton: Draft iijppp FAQ Date: Thu, 27 Jul 1995 17:08:30 -0700 Message-ID: <3548.806890110@time.cdrom.com> From: "Jordan K. Hubbard" Sender: doc-owner@freebsd.org Precedence: bulk You guys have seen this, yes? I've seen no comments - we all think it's perfect, do we? :-) Jordan ------- Forwarded Message Return-Path: nik@blueberry.co.uk Received: from freefall.cdrom.com (freefall.cdrom.com [192.216.222.4]) by time.cdrom.com (8.6.11/8.6.9) with ESMTP id PAA00882 for ; Sun, 23 Jul 1995 15:18:20 -0700 Received: from elbereth.blueberry.co.uk (surfs-up.demon.co.uk [158.152.128.94]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id PAA15688 for ; Sun, 23 Jul 1995 15:18:20 -0700 Received: (from nik@localhost) by elbereth.blueberry.co.uk (8.6.11/8.6.9) id XAA01048 for faq@freebsd.org; Sun, 23 Jul 1995 23:20:09 GMT From: Nik Clayton Message-Id: <199507232320.XAA01048@elbereth.blueberry.co.uk> Subject: Draft iijppp FAQ To: faq@freebsd.org Date: Sun, 23 Jul 1995 23:20:09 +0000 () X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 14103 What follows is a draft FAQ for iijppp and FreeBSD 2.0.5. If anyone could cast an experienced eye over it, suggest improvements, and in particular volunteer to write a section on dynamically allocated IP addressess... I'm not subscribed to the faq mailing list (yet) so I'd appreciate it if any comments we're cc'd to me as well as to the list. N $Id: iijppp.faq,v 1.1 1995/07/23 21:58:15 nik Exp nik $ $Log: iijppp.faq,v $ # Revision 1.1 1995/07/23 21:58:15 nik # Initial revision # Introduction ~~~~~~~~~~~~ This FAQ/HowTo is intended to get you up and running with iijppp, also known as the 'user level ppp' for FreeBSD 2.0.5 (and above). I hope this document turns into a collaborative effort, largely because I am not really much of an authority on PPP. I've got it working, and want to pass on details of what I did so that other people can get it working. But I'm not 100% clear on some details, so I hope that by writing this and haveing others flesh out some of the information I'm going to learn something as well. Anything that I'm explicitly unsure about I've marked with an asterisk ``*'' in the first column. Unless otherwise stated, all commands shown below should be executed as ``root''. What is IIJPPP? ~~~~~~~~~~~~~~~ From the man page (``man ppp'') This is a user process PPP software package. Normally, PPP is implemented as a part of the kernel (e.g. as managed by pppd) and it's thus somewhat hard to debug and/or modify its behavior. However, in this implementation PPP is done as a user process with the help of the tunnel device driver (tun). In essence, this means that rather than running a PPP daemon, the ``ppp'' program can be run as and when desired. No PPP interface needs to be compiled into the kernel, as the program can use the generic ``tunnel'' device to to get data into and out of the kernel. From here on in I'm going to refer to iijppp as ``ppp'', unless I need to distinguish between it and any other PPP client/server software. Before you start ~~~~~~~~~~~~~~~~ This document assumes you're in roughly this position: You have an account with an Internet Service Provider (ISP) which lets you use PPP. Further, you have a modem (or other device) connected and configured correctly which allows you to connect to your ISP. You are going to need the following information to hand: o IP address of your ISP's gateway o Your ISP's netmask setting o IP adresses of one or more nameservers o If your ISP allocates you a static IP address and/or hostname then you will need that as well. If not, you will need to know from what range of IP addresses your allocated IP address will fall in. If you do not have any of this information then contact your ISP and make sure they provide it to you. As well as this, you may need the files required to recompile your kernel. Check the ``Kernel compiling'' FAQ for more information on how to acquire these. In addition, I've assumed that because your connection to the Internet is not full time you are not running a name server (``named''). Building a ppp ready kernel ~~~~~~~~~~~~~~~~~~~~~~~~~~~ As the description states, ``ppp'' uses the kernel ``tun'' device. It is necessary to make sure that your kernel has support for this device compiled in. To check this, go to your kernel compile directory (probably /sys/i386/conf) and examine your kernel configuration file. It needs to have the line pseudo-device tun 1 in it somewhere. The stock GENERIC kernel has this as standard, so if you have not installed a custom kernel you don't have to change anything. If your kernel configuration file does not have this line in it then you should add the line, re-compile and then re-install the kernel. Boot from this new kernel. Check the tun device ~~~~~~~~~~~~~~~~~~~~ My experiences with ppp have only been with one ``tun'' device (tun0). If you have used more (i.e., a number other than `1' in the pseudo-device line in the kernel configuration file) then alter all references to ``tun0'' below to reflect whichever device number you are using. The easiest way to make sure that the tun0 device is configured correctly is to re-make it. To this end, execute the following commands, # cd /dev # ./MAKEDEV tun0 PPP Configuration ~~~~~~~~~~~~~~~~~ The meat of the problem. Confusingly, it appears that both iijppp and pppd (the kernel level implementation of PPP) both assume configuration files kept in /etc/ppp. However, the sample configuration files provided are good for iijppp, so keep them around for reference. The easiest way to do this is, # cd /etc # mv ppp ppp.orig # mkdir ppp Configuring ppp requires that you edit somewhere between one and three files, depending on your requirements. What you put in them depends to some extent on whether your ISP allocates IP addresses statically (i.e., you get given one IP address, and always use that one) or dynamically (i.e., your IP address can be different during different PPP sessions). However, there are a few things that you should do first, regardless of whether you are using static or dynamic IP addresses. a) Configure the resolver(5) The resolver is the part of the networking system that turns IP addresses into hostnames. It can be configured to look for maps that describe IP to hostname mappings in one of two places. The first is a file called /etc/hosts (``hosts'' in section 5 of the manual). The second is the Internet Domain Name Service, a distributed data base, the discussion of which is beyond the realm of this document. The resolver is a set of system calls that do the mappings, and you have to tell them where to get their information from. You do this by editing the file /etc/host.conf. Do *not* call this file /etc/hosts.conf (note the extra ``s'') as the results can be confusing. This file should contain the following two lines, hosts bind which instruct the resolver to look in the file /etc/hosts first, and then to consult the DNS if the name was not found in the /etc/hosts file. It's probably a good idea to make sure you are not running the ``named'' service. Check your /etc/sysconfig file for the line that refers to ``namedflags'', and make sure the line reads namedflags="NO" b) Create the /etc/hosts(5) file This file should contain the IP addresses and names of machines on your network. At a bare minimum it should contain entries for the machine which will be running ppp. Assuming that you're machine is called foo.bar.com with the IP address 10.0.0.1, /etc/hosts should contain 127.0.0.0 localhost 10.0.0.1 foo.bar.com foo The first line defines the alias ``localhost'' as a synonym for the current machine. Regardless of your own IP address, the IP address for this line should always be 127.0.0.1. The second line maps the name ``foo.bar.com'' (and the shorthand ``foo'') to the IP address 10.0.0.1. If your provider allocates you a static IP address then use this in place of 10.0.0.1. * What should they do if they are allocated an IP address dynamically? c) Create the /etc/resolv.conf file /etc/resolv.conf contains some extra information required when you are not running a nameserver. It points the resolver routines at real nameservers, and specifies some other information. At the very least, /etc/resolv.conf should contain one line with a nameserver which can be queried. You should enter this as an IP address. My /etc/resolv.conf contains nameserver 158.152.1.193 nameserver 158.152.1.65 Which are Demon Internet's two nameservers. Add as many ``nameserver'' lines as your ISP provides nameservers. PPP and static IP addresses ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Probably the easiest to configure for. You will need to create three files in the /etc/ppp directory. The first of these is ppp.conf. It should look similar to the example below. Note that lines that end in a ``:'' start in column 1, all other lines should be indented as shown. /etc/ppp/ppp.conf 1 default: 2 set device /dev/cuaa0 3 set speed 9600 4 disable lqr 5 deny lqr 6 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" ATE1Q0 OK-AT-OK \\dATDT\\T TIMEOUT 40 CONNECT" 7 provider: 8 set phone 01234567890 9 set login "TIMEOUT 10 gin:-BREAK-gin: foo word: bar col: ppp" 10 set timeout 120 11 set ifaddr x.x.x.x y.y.y.y Don't include the line numbers, they're just for this discussion. Line # Purpose ------------------------------------------------------------------------ 1 Identifies the default entry. Commands in this entry are executed automatically when ppp is run. 2 Identifies the device that has the modem hanging from it. COM1: is /dev/cuaa0 and COM2: is /dev/cuaa1 3 Sets the speed you want to connect at. * 4 and 5 Don't know exactly what effect these lines have 6 Dial string commands. iijppp uses the chat(8) language. Check the manual page for information on the features of this language. 7 Identifies an entry for a provider called ``provider''. 8 Sets the phone number for this provider. Don't include any spaces in the phone number. 9 Set's the login string sequence. In this example, the string is for a service who's login session looks like J. Random Provider login: foo password: bar protocol: ppp You will need to alter this script to suit your own needs. It is written in the chat(8) language. 10 Sets the default timeout (in seconds) for the connection. So the connectioned will be closed automatically after 120 seconds of inactivity. 11 Sets the interface addresses. The string x.x.x.x should be replaced by the IP address that your provider allocates you. The string y.y.y.y should be replaced by the IP address that your ISP indicated for their gateway. Now you have to edit the file ppp.linkup /etc/ppp/ppp.linkup x.x.x.x: add 0 0 HISADDR Replace x.x.x.x with your IP address as before. This file is used to automatically add a default route from your ISP (who's address is automatically inserted with the HISADDR macro) to you. Finally, you can create the file /etc/ppp/ppp.secret, which sets some passwords to prevent people messing around with ppp on your system. You may or may not want to do this, depending on how many people have access to your ppp system. PPP and Dynamic IP configuration ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * Don't have a clue how to do this. Could someone who does submit something to go in here? Final system configuration ~~~~~~~~~~~~~~~~~~~~~~~~~~ You now have PPP configured, but there's a few more things to do before it's ready to work. They all involve editing the /etc/sysconfig file. Working from the top down in this file, make sure the ``hostname='' line is set, e.g., hostname=foo.bar.com Look for the network_interfaces variable, and make sure the tun0 device is added to the list. My line looks like network_interfaces="lo0 tun0 ep0" but I have an ethernet card (ep0) to configure as well. Now add an ifconfig line for the tun0 device. It should look something like ifconfig_tun0="inet foo.bar.com y.y.y.y netmask 0xffffffff" as before, change ``foo.bar.com'' to be your hostname, y.y.y.y is the IP address of your providers gateway, and 0xffffffff is the netmask they provided you with (in hexadecimal). Two command values for the netmask are 255.255.255.255 = 0xffffffff 255.255.255.0 = 0xffffff00 Set the routed flags to ``-s'' with the line routedflags=-s It's probably worth your while ensuring that the ``sendmail_flags'' line does not include the ``-q'' option, otherwise sendmail will attempt to do a network lookup every now and then, possibly causing your machine to dial out. My sendmail line looks like sendmail_flags="-bd" The upshot of this is that I must force sendmail to re-examine the mailqueue whenever I have the PPP link up, by typing # /usr/sbin/sendmail -q That should be about all you need to do to get PPP working with a static IP address. All that's left is to reboot the machine. During startup the tun0 device should be detected, and two lines like the following should be printed, tun0: flags=51 mtu 1500 inet x.x.x.x --> y.y.y.y netmask 0xffffffff At this point, it should all be working. You can now either type # ppp and then ``dial provider'' to start the PPP session, or, if you want ppp to establish sessions automatically when there is outbound traffic, type # ppp -auto provider This line could be added to your /etc/rc.local file. Acknowledgements ~~~~~~~~~~~~~~~~ Rob Snow who proved to be a mine of useful information when I was first experimenting with iijppp. Anyone else who can provide any more information to go in this FAQ, particularly in the area of dynamically allocated IP addresses, on which I know next to nothing. - -- - --+=[ Nik Clayton System Administration, Blueberry Design Ltd, ]=+-- - --+=[ nik@blueberry.co.uk 1/9 Chelsea Harbour Design Centre ]=+-- - --+=[ root@blueberry.co.uk London, SW10 0XE. Tel: 0171 351 3313 ]=+-- "It's two o'clock in the morning . . . do you know where your stack pointer is?" ------- End of Forwarded Message From owner-freebsd-doc Fri Jul 28 05:22:49 1995 Return-Path: doc-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id FAA07381 for doc-outgoing; Fri, 28 Jul 1995 05:22:49 -0700 Received: from grendel.csc.smith.edu (grendel.csc.smith.edu [131.229.222.23]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id FAA07375 for ; Fri, 28 Jul 1995 05:22:47 -0700 Received: from localhost (jfieber@localhost) by grendel.csc.smith.edu (8.6.5/8.6.5) id IAA03041; Fri, 28 Jul 1995 08:24:38 -0400 From: jfieber@grendel.csc.smith.edu (John Fieber) Message-Id: <199507281224.IAA03041@grendel.csc.smith.edu> Subject: Re: Nik Clayton: Draft iijppp FAQ To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 28 Jul 1995 08:24:38 -0400 (EDT) Cc: doc@freebsd.org In-Reply-To: <3548.806890110@time.cdrom.com> from "Jordan K. Hubbard" at Jul 27, 95 05:08:30 pm Content-Type: text Content-Length: 327 Sender: doc-owner@freebsd.org Precedence: bulk Jordan K. Hubbard writes: > You guys have seen this, yes? I've seen no comments - we all think > it's perfect, do we? :-) Um, no, I have not seen it. I'll see if I can sew it into the handbook before I take off for moving and vacation stuff. -john === jfieber@cs.smith.edu ========== Come up and be a kite! --K. Bush === From owner-freebsd-doc Fri Jul 28 08:32:41 1995 Return-Path: doc-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id IAA13197 for doc-outgoing; Fri, 28 Jul 1995 08:32:41 -0700 Received: from grendel.csc.smith.edu (grendel.csc.smith.edu [131.229.222.23]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id IAA13185 for ; Fri, 28 Jul 1995 08:32:39 -0700 Received: from localhost (jfieber@localhost) by grendel.csc.smith.edu (8.6.5/8.6.5) id LAA06042; Fri, 28 Jul 1995 11:33:26 -0400 From: jfieber@grendel.csc.smith.edu (John Fieber) Message-Id: <199507281533.LAA06042@grendel.csc.smith.edu> Subject: User PPP tutorial To: nik@blueberry.co.uk Date: Fri, 28 Jul 1995 11:33:26 -0400 (EDT) Cc: doc@freebsd.org Content-Type: text Content-Length: 650 Sender: doc-owner@freebsd.org Precedence: bulk I've put the iijppp into the handbook. Please take a preview look at http://www.freebsd.org/~jfieber/handbook/handbook.html. If there are not objections, it will become part of FreeBSD-current tomorrow morning (eastern united states time). I just did minimal sgml tagging (essentially section headings and file snippets only), and edited the introduction to make it fit into the flow of the handbook better. For pre-commit changes (if any), you can grab the sgml source at http://www.freebsd.org/~jfieber/handbook/userppp.sgml and send me diffs relative to that. -john === jfieber@cs.smith.edu ========== Come up and be a kite! --K. Bush === From owner-freebsd-doc Fri Jul 28 14:52:48 1995 Return-Path: doc-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id OAA09356 for doc-outgoing; Fri, 28 Jul 1995 14:52:48 -0700 Received: from violet.berkeley.edu (violet.Berkeley.EDU [128.32.155.22]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id OAA09343 ; Fri, 28 Jul 1995 14:52:44 -0700 Received: by violet.berkeley.edu (8.6.10/1.33r) id OAA00397; Fri, 28 Jul 1995 14:52:43 -0700 Date: Fri, 28 Jul 1995 14:52:43 -0700 From: jkh@violet.berkeley.edu (Jordan K. Hubbard) Message-Id: <199507282152.OAA00397@violet.berkeley.edu> To: doc@freebsd.org, faq@freebsd.org Subject: I do not see that this ever made it in to the FAQ?? Sender: doc-owner@freebsd.org Precedence: bulk Path: agate!howland.reston.ans.net!swrinde!sdd.hp.com!col.hp.com!news.dtc.hp.com!canyon.sr.hp.com!darrylo From: darrylo@sr.hp.com (Darryl Okahata) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: More virtual terminals Date: 28 Jul 1995 17:19:16 GMT Organization: Hewlett-Packard / Center for Primal Scream Therapy Lines: 168 Message-ID: <3vb66k$6lj@canyon.sr.hp.com> References: <3vb5oo$idb@ddi2.digital.net> Reply-To: darrylo@sr.hp.com NNTP-Posting-Host: mina.sr.hp.com X-Newsreader: TIN [version 1.2 PL2] Kevin (klo@digital.net) wrote: > How do I go about adding more virutal terminals? MAKEDEV doesn't want to > make any more, and I can't seem to find it in my kernel config file > (maybe I'm blind or something). Here's a fragment of some things that I submitted for addition to the FAQ (ignore the strange question numbering). Check out the last question. [ Hmm. Looking at these answers, some of them are a bit incomplete. Not all possibilities are given. ] -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion or policy of Hewlett-Packard or of the little green men that have been following him all day. =============================================================================== 5 Miscellaneous Questions ---------------- 5.0.1: Hey! Chmod doesn't change the file permissions of symlinked files! What's going on? You have to use either "-H" or "-L" together with the "-R" option to make this work. See the chmod(1) and symlink(7) man pages for more info. WARNING: the "-R" option does a *RECURSIVE* chmod. Be careful about specifying directories or symlinks to directories to chmod. If you want to change the permissions of a directory referenced by a symlink, use chmod(1) without any options and follow the symlink with a trailing slash ("/"). For example, if "foo" is a symlink to directory "bar", and you want to change the permissions of "foo" (actually "bar"), you would do something like: chmod 555 foo/ With the trailing slash, chmod will follow the symlink, "foo", to change the permissions of the directory, "bar". 5.0.2: How do I mount a CDROM? I've tried using mount(8), but it keeps on giving me an error like, "/dev/cd0a on /mnt: Incorrect super block." You have to tell mount(8) the type of the device that you want to mount. By default, mount(8) will assume the filesystem is of type "ufs". You want to mount a CDROM filesystem, and you do this by specifying the "-t cd9660" option to mount(8). This does, of course, assume that the CDROM contains an ISO 9660 filesystem, which is what most CDROMs have. As of 2.0.5R, FreeBSD also understands the Rock Ridge (long filename) extensions. As an example, if you want to mount the CDROM device, "/dev/cd0c", under /mnt, you would execute: mount -t cd9660 /dev/cd0c /mnt Note that your device name ("/dev/cd0c" in this example) could be different, depending on the CDROM interface. Note that the "-t cd9660" option just causes the "mount_cd9660" command to be executed, and so the above example could be shortened to: mount_cd9660 /dev/cd0c /mnt 5.0.3: When I try to mount a CDROM, I get a "Device not configured" error. What's going on? This generally means that there is no CDROM in the CDROM drive. Feed the drive something. 5.0.4: My programs occasionally die with "Signal 11" errors. What's going on? 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). 5.0.5: Help, some of my X Window menus and dialog boxes don't work right! I can't select them. Try turning off the Num Lock key. 5.0.6: How do I access the virtual consoles? If the console is not currently displaying X Windows, just press Alt-F1 to Alt-F12. NOTE: the default FreeBSD installation has only three (3) virtual consoles enabled, and so only Alt-F1, Alt-F2, and Alt-F3 will work to switch between three virtual consoles. If you want to increase this number, see the next question. If the console is currently displaying X Windows, you can use Ctrl-Alt-F1, etc. to switch to a virtual console. Note, however, that once you've switched away from X Windows to a virtual terminal, you use only the Alt- function key to switch to another virtual terminal or back to X Windows. You do not also press the Ctrl key; the Ctrl-Alt-function key combination is used only when switching from X Windows to a virtual terminal. 5.0.7: How do I increase the number of virtual consoles? Edit /etc/ttys and add entries for "ttyv4" to "ttyvc" after the comment on "Virtual terminals" (delete the leading whitespace in the following example): # Edit the existing entry for ttyv3 in /etc/ttys and change # "off" to "on". ttyv3 "/usr/libexec/getty Pc" cons25 on secure ttyv4 "/usr/libexec/getty Pc" cons25 on secure ttyv5 "/usr/libexec/getty Pc" cons25 on secure ttyv6 "/usr/libexec/getty Pc" cons25 on secure ttyv7 "/usr/libexec/getty Pc" cons25 on secure ttyv8 "/usr/libexec/getty Pc" cons25 on secure ttyv9 "/usr/libexec/getty Pc" cons25 on secure ttyva "/usr/libexec/getty Pc" cons25 on secure ttyvb "/usr/libexec/getty Pc" cons25 on secure Use as many or as few as you want. The more virtual terminals you have, the more resources that are used; this can be important if you have 8MB RAM or less. You may also want to change the "secure" to "insecure". IMPORTANT NOTE: if you want to run X Windows, you *MUST* leave a virtual terminal unused (or turned off). For example, if you want to attach a virtual terminal to all of your twelve Alt-function keys, you can only attach virtual terminals to eleven of them. The last must be left unused, because X Windows will use it, and you will use the last Alt-function key to switch back to X Windows (after you have switched from X Windows to a virtual console via a Ctrl-Alt-function key). The easiest way to do this is to disable a console by turning it off. For example, if you have a keyboard with twelve function keys, you would change settings for virtual terminal 12 from: ttyvb "/usr/libexec/getty Pc" cons25 on secure to: ttyvb "/usr/libexec/getty Pc" cons25 off secure If your keyboard has only ten function keys, you would end up with: ttyv9 "/usr/libexec/getty Pc" cons25 off secure ttyva "/usr/libexec/getty Pc" cons25 off secure ttyvb "/usr/libexec/getty Pc" cons25 off secure (You could also just delete these lines.) Once you have edited /etc/ttys, the next step is to make sure that you have enough virtual terminal devices. The easiest way to do this is: cd /dev ./MAKEDEV vty12 # For 12 devices Next, the easiest (and cleanest) way to activate the virtual consoles is to reboot. However, if you really don't want to reboot, you can just shut down X Windows and execute (as root): kill -HUP 1 It's imperative that you completely shut down X Windows if it is running, before running this command. If you don't, your system will probably appear to hang/lock up after executing the kill command. From owner-freebsd-doc Fri Jul 28 14:56:12 1995 Return-Path: doc-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id OAA09582 for doc-outgoing; Fri, 28 Jul 1995 14:56:12 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id OAA09573 ; Fri, 28 Jul 1995 14:56:08 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id OAA09241; Fri, 28 Jul 1995 14:55:15 -0700 To: faq@freefall.cdrom.com cc: doc@freefall.cdrom.com Subject: Any serious objections to a semi-hostile takeover of the FAQ? Date: Fri, 28 Jul 1995 14:55:14 -0700 Message-ID: <9239.806968514@time.cdrom.com> From: "Jordan K. Hubbard" Sender: doc-owner@FreeBSD.org Precedence: bulk Well, I've been watching the FAQ for about 6 months now and I have to say that I'm not at all happy with its progress. Large sections of it have mouldered, submissions have gone unadded, it's generally just Not Happening and our user base is suffering for it (to say nothing of folks like Joerg and I who are answering all these bloody questions in the newsgroups). I would like to take the FAQ over at this point, if nobody has any serious objections. There is a lot of material to be added and updated and I have a pretty good idea of where and when it needs to happen, so... Unless I hear any substantial argument to the contrary, I'm going to jump in there sometime in the next 24 hours. As they say at weddings: Speak now or forever hold your peace! Jordan From owner-freebsd-doc Fri Jul 28 15:50:13 1995 Return-Path: doc-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id PAA12842 for doc-outgoing; Fri, 28 Jul 1995 15:50:13 -0700 Received: from relay.hp.com (relay.hp.com [15.255.152.2]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id PAA12836 ; Fri, 28 Jul 1995 15:50:12 -0700 Received: from srmail.sr.hp.com by relay.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA030201805; Fri, 28 Jul 1995 15:50:06 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA112171804; Fri, 28 Jul 1995 15:50:05 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA230141804; Fri, 28 Jul 1995 15:50:04 -0700 Message-Id: <199507282250.AA230141804@hpnmhjw.sr.hp.com> To: "Jordan K. Hubbard" Cc: faq@freefall.cdrom.com, doc@freefall.cdrom.com Subject: Re: Any serious objections to a semi-hostile takeover of the FAQ? In-Reply-To: Your message of "Fri, 28 Jul 1995 14:55:14 PDT." <9239.806968514@time.cdrom.com> Date: Fri, 28 Jul 1995 15:50:03 -0700 From: Darryl Okahata Sender: doc-owner@FreeBSD.org Precedence: bulk > I would like to take the FAQ over at this point, if nobody has any > serious objections. There is a lot of material to be added and > updated and I have a pretty good idea of where and when it needs to > happen, so... Unless I hear any substantial argument to the contrary, > I'm going to jump in there sometime in the next 24 hours. > > As they say at weddings: Speak now or forever hold your peace! A week or two ago, I sent in some additions (which I now realize are slightly incomplete) for the FAQ. Would you like me to send them to you? -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion or policy of Hewlett-Packard or of the little green men that have been following him all day. From owner-freebsd-doc Fri Jul 28 16:09:23 1995 Return-Path: doc-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id QAA13976 for doc-outgoing; Fri, 28 Jul 1995 16:09:23 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id QAA13966 ; Fri, 28 Jul 1995 16:09:21 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id QAA09452; Fri, 28 Jul 1995 16:04:32 -0700 To: Darryl Okahata cc: faq@freefall.cdrom.com, doc@freefall.cdrom.com Subject: Re: Any serious objections to a semi-hostile takeover of the FAQ? In-reply-to: Your message of "Fri, 28 Jul 1995 15:50:03 PDT." <199507282250.AA230141804@hpnmhjw.sr.hp.com> Date: Fri, 28 Jul 1995 16:04:31 -0700 Message-ID: <9450.806972671@time.cdrom.com> From: "Jordan K. Hubbard" Sender: doc-owner@FreeBSD.org Precedence: bulk > A week or two ago, I sent in some additions (which I now realize > are slightly incomplete) for the FAQ. Would you like me to send them to > you? I just forwarded the contents of your recent posting, but if you've got updates to this then by all means, yes. Jordan From owner-freebsd-doc Sat Jul 29 11:14:26 1995 Return-Path: doc-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id LAA05828 for doc-outgoing; Sat, 29 Jul 1995 11:14:26 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id LAA05815 ; Sat, 29 Jul 1995 11:14:22 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id UAA14542 ; Sat, 29 Jul 1995 20:14:12 +0200 Received: from (roberto@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) id UAA05346 ; Sat, 29 Jul 1995 20:14:11 +0200 From: roberto@blaise.ibp.fr (Ollivier Robert) Message-Id: <199507291814.UAA05346@blaise.ibp.fr> Subject: Re: Any serious objections to a semi-hostile takeover of the FAQ? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sat, 29 Jul 1995 20:14:11 +0200 (MET DST) Cc: faq@freefall.cdrom.com, doc@freefall.cdrom.com In-Reply-To: <9239.806968514@time.cdrom.com> from "Jordan K. Hubbard" at Jul 28, 95 02:55:14 pm X-Operating-System: FreeBSD 2.2-CURRENT ctm#880 X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 364 Sender: doc-owner@FreeBSD.org Precedence: bulk > > As they say at weddings: Speak now or forever hold your peace! I've committed a whole bunch of changes to bring it in sync with 2.0.5R. Sorry, I've been swamped with work lately. I promise to be faster in the future... -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD 2.2-CURRENT #5: Fri Jul 14 12:28:04 MET DST 1995 From owner-freebsd-doc Sat Jul 29 16:03:57 1995 Return-Path: doc-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id QAA03355 for doc-outgoing; Sat, 29 Jul 1995 16:03:57 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id QAA03348 ; Sat, 29 Jul 1995 16:03:55 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id BAA15495 ; Sun, 30 Jul 1995 01:03:56 +0200 Received: from (roberto@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) id BAA05932 ; Sun, 30 Jul 1995 01:03:55 +0200 From: roberto@blaise.ibp.fr (Ollivier Robert) Message-Id: <199507292303.BAA05932@blaise.ibp.fr> Subject: Re: I do not see that this ever made it in to the FAQ?? To: jkh@violet.berkeley.edu (Jordan K. Hubbard) Date: Sun, 30 Jul 1995 01:03:55 +0200 (MET DST) Cc: doc@freebsd.org, faq@freebsd.org In-Reply-To: <199507282152.OAA00397@violet.berkeley.edu> from "Jordan K. Hubbard" at Jul 28, 95 02:52:43 pm X-Operating-System: FreeBSD 2.2-CURRENT ctm#880 X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 381 Sender: doc-owner@freebsd.org Precedence: bulk > 5 Miscellaneous Questions > ---------------- All of these along with Bruce Evans message on slices have been incorpor ated in the FAQ (in SGML). John has said the Text version will go away soon. Do I have to sync it up with the sgml one ? -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD 2.2-CURRENT #5: Fri Jul 14 12:28:04 MET DST 1995 From owner-freebsd-doc Sat Jul 29 18:59:41 1995 Return-Path: doc-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id SAA09629 for doc-outgoing; Sat, 29 Jul 1995 18:59:41 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id SAA09623 ; Sat, 29 Jul 1995 18:59:38 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id DAA15997 ; Sun, 30 Jul 1995 03:59:36 +0200 Received: from (roberto@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) id DAA06300 ; Sun, 30 Jul 1995 03:59:35 +0200 From: roberto@blaise.ibp.fr (Ollivier Robert) Message-Id: <199507300159.DAA06300@blaise.ibp.fr> Subject: Updated FAQ on WWW.FreeBSD.ORG To: doc@freebsd.org (FreeBSD's documentation list), hackers@freebsd.org (Hackers' list FreeBSD) Date: Sun, 30 Jul 1995 03:59:35 +0200 (MET DST) Cc: www@freebsd.org X-Operating-System: FreeBSD 2.2-CURRENT ctm#880 X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 343 Sender: doc-owner@freebsd.org Precedence: bulk As John Fieber is on the move, I've put the updated FAQ in HTML in my home directory so everyone can check it at It will be put at the usual place soon I hope. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG FreeBSD 2.2-CURRENT #5: Fri Jul 14 12:28:04 MET DST 1995