From owner-freebsd-doc Thu Oct 19 18:48:33 1995 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA09362 for doc-outgoing; Thu, 19 Oct 1995 18:48:33 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA09356 ; Thu, 19 Oct 1995 18:48:25 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id LAA16956; Fri, 20 Oct 1995 11:52:36 +0930 From: Michael Smith Message-Id: <199510200222.LAA16956@genesis.atrad.adelaide.edu.au> Subject: Re: 50 line console display To: andi@actcom.co.il (Andi Gutmans) Date: Fri, 20 Oct 1995 11:52:35 +0930 (CST) Cc: freebsd-questions@freebsd.org, doc@freebsd.org In-Reply-To: from "Andi Gutmans" at Oct 19, 95 05:31:45 pm Content-Type: text Content-Length: 1821 Sender: owner-doc@freebsd.org Precedence: bulk Andi Gutmans stands accused of saying: > > Can someone please let me know if there's an FAQ file on how to make a 50 > line console display with FreeBSD? One that goes through the steps? > > Any refrences would be appreciated, 1) Select display fonts that suit your requirements from the set in /usr/share/syscons/fonts/* 2) Edit /etc/sysconfig and specify these fonts in the Syscons section. For 80x50 or 80x60, you will need an 8x8 font, for 80x30 an 8x14 font, and to replace the 80x25 font, specify an 8x16 font. 3) Reboot. You can also load fonts on the fly; see the 'vidcontrol' manpage. 4) Select your desired video mode with 'vidcontrol', eg. 'vidcontrol VGA_80x50' This is really about as trivial as it gets 8) If you want to have your virtual consoles default to 80x50 without you having to do this yourself, you can try this : Put this in /usr/local/libexec/gettywrap #!/bin/sh # # Frob video modes and exec arguments # vidcontrol -r white blue vidcontrol VGA_80x50 exec $* make sure it's chmodded 500 and owned by root. Then in /etc/ttys, edit the getty fields in the entries for your ttyv* ports to read : "/usr/local/libexec/gettywrap /usr/local/libexec/getty Pc" I would advice against doing this on ttyv0, as fiddling with the console is a Bad Idea in general. If someone wants to cut this out and stick it in the FAQ or the handbook, go right ahead. (I've cc'd this to -doc) > Andi Gutmans -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[ From owner-freebsd-doc Fri Oct 20 04:28:23 1995 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA29726 for doc-outgoing; Fri, 20 Oct 1995 04:28:23 -0700 Received: from plato.ucsalf.ac.uk (plato.ucsalf.ac.uk [193.62.40.188]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id EAA29713 for ; Fri, 20 Oct 1995 04:27:00 -0700 Received: by plato.ucsalf.ac.uk (Smail3.1.29.1 #11) id m0t6FbA-0005NaC; Fri, 20 Oct 95 12:26 BST Date: Fri, 20 Oct 1995 12:26:52 +0100 (BST) From: Mark Powell To: doc@freebsd.org Subject: Handbook Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org Precedence: bulk Hi, I'm trying to get hold of the handbook.tex file, but it keeps aborting midway. Could you email me this file and also a PostScript version if you have it. Many thanks. Mark Powell - Senior Network Technician - Room: C806 Computer Services Unit, University College Salford, Salford, UK. Tel: +44 161 745 3376 Fax: +44 161 736 3596 Email: mark@ucsalf.ac.uk finger mark@ucsalf.ac.uk (for PGP key) Home Page From owner-freebsd-doc Fri Oct 20 06:45:55 1995 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA02955 for doc-outgoing; Fri, 20 Oct 1995 06:45:55 -0700 Received: from fieber-john.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id GAA02950 for ; Fri, 20 Oct 1995 06:45:53 -0700 Received: (from jfieber@localhost) by fieber-john.campusview.indiana.edu (8.6.11/8.6.9) id IAA17549; Fri, 20 Oct 1995 08:44:32 -0500 Date: Fri, 20 Oct 1995 08:44:31 -0500 (EST) From: John Fieber To: Mark Powell cc: doc@freebsd.org Subject: Re: Handbook In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org Precedence: bulk On Fri, 20 Oct 1995, Mark Powell wrote: > I'm trying to get hold of the handbook.tex file, but it keeps aborting > midway. Could you email me this file and also a PostScript version if you > have it. You can also get it via ftp from ftp://ftp.freebsd.org/pub/FreeBSD/docs. I don't have a postscript version handy. :( -john == jfieber@indiana.edu =========================================== == http://fieber-john.campusview.indiana.edu/~jfieber ============ From owner-freebsd-doc Fri Oct 20 11:03:27 1995 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA13682 for doc-outgoing; Fri, 20 Oct 1995 11:03:27 -0700 Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id LAA13665 for ; Fri, 20 Oct 1995 11:03:05 -0700 Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA04782; Fri, 20 Oct 95 19:03:17 +0100 Date: Fri, 20 Oct 95 19:03:17 +0100 Message-Id: <9510201803.AA04782@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: mark@ucsalf.ac.uk Cc: doc@freebsd.org In-Reply-To: (message from Mark Powell on Fri, 20 Oct 1995 12:26:52 +0100 (BST)) Subject: Re: Handbook X-Mailer: Emacs Sender: owner-doc@freebsd.org Precedence: bulk >>>>> Mark Powell writes: > Hi, > I'm trying to get hold of the handbook.tex file, but it keeps aborting > midway. Could you email me this file and also a PostScript version if you > have it. > Many thanks. I have put the PostScript version in freefall.cdrom.com:incoming/handbook.ps.gz Jean-Marc > Mark Powell - Senior Network Technician - Room: C806 > Computer Services Unit, University College Salford, Salford, UK. > Tel: +44 161 745 3376 Fax: +44 161 736 3596 > Email: mark@ucsalf.ac.uk finger mark@ucsalf.ac.uk (for PGP key) > Home Page _____________________________________________________________________________ Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex PGP Key: finger jmz@cabri.obs-besancon.fr ============================================================================= From owner-freebsd-doc Fri Oct 20 11:25:57 1995 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA15338 for doc-outgoing; Fri, 20 Oct 1995 11:25:57 -0700 Received: from eikon.e-technik.tu-muenchen.de (eikon.regent.e-technik.tu-muenchen.de [129.187.42.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA15146 for ; Fri, 20 Oct 1995 11:23:49 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de (vector.eikon.e-technik.tu-muenchen.de [129.187.142.36]) by eikon.e-technik.tu-muenchen.de (8.6.12/8.6.9) with ESMTP id TAA21584 for ; Fri, 20 Oct 1995 19:18:43 +0100 Received: (from jhs@localhost) by vector.eikon.e-technik.tu-muenchen.de (8.6.12/8.6.9) id TAA09290 for doc@freebsd.org; Fri, 20 Oct 1995 19:15:47 +0100 Date: Fri, 20 Oct 1995 19:15:47 +0100 From: "Julian H. Stacey" Message-Id: <199510201815.TAA09290@vector.eikon.e-technik.tu-muenchen.de> To: doc@freebsd.org Subject: http://www.FreeBSD.org/What/ Sender: owner-doc@freebsd.org Precedence: bulk Hi WWW/Doc People, Ref. http://www.FreeBSD.org/What/ > Applications: FreeBSD is not just for hackers anymore The word `hackers' in very large bold type is sufficient for me NOT to be able to point customers at this page when I'm simultaneously promoting my consultancy services & FreeBSD as a base software set. I'm not interested in what we think hackers are & how the definition changes by part of world & by type of person, that's not the point, it's what non programmers think a `hacker' is that is the problem (ie a cracker). While the word `Hacker' is there, I cannot point conservative customers to this page :-( Any chance we can remove usage of `hackers' & put something (Anything !) else instead ? Julian --- Julian H. Stacey EMAIL: jhs@freebsd.org WEB: http://www.freebsd.org/~jhs/ TEL: +49.89.268616 FAX: +49.89.2608126 CONSULTANT: Internet, Unix, C POST: Vector Systems Ltd, Holz Strasse 27d, 80469 Munich, Germany. FreeBSD has: BSD-Un*x, ~400 ported packages, Sources on CD & Net. From owner-freebsd-doc Fri Oct 20 13:43:07 1995 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA18830 for doc-outgoing; Fri, 20 Oct 1995 13:43:07 -0700 Received: from fieber-john.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA18823 for ; Fri, 20 Oct 1995 13:42:58 -0700 Received: (from jfieber@localhost) by fieber-john.campusview.indiana.edu (8.6.11/8.6.9) id PAA18455; Fri, 20 Oct 1995 15:40:29 -0500 Date: Fri, 20 Oct 1995 15:40:27 -0500 (EST) From: John Fieber To: "Julian H. Stacey" cc: doc@freebsd.org Subject: Re: http://www.FreeBSD.org/What/ In-Reply-To: <199510201815.TAA09290@vector.eikon.e-technik.tu-muenchen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org Precedence: bulk On Fri, 20 Oct 1995, Julian H. Stacey wrote: > Ref. http://www.FreeBSD.org/What/ > > > Applications: FreeBSD is not just for hackers anymore ... > Any chance we can remove usage of `hackers' & put something (Anything !) else > instead ? Yes, see http://fieber-john.campusview.indiana.edu/FreeBSD for "FreeBSD WWW: The Next Generation". These pages are almost to the point where I'm ready to replace the old with the new. Comments are appreciated. Note, the searching of the WWW pages appears to work, but it doesn't really... -john == jfieber@indiana.edu =========================================== == http://fieber-john.campusview.indiana.edu/~jfieber ============ From owner-freebsd-doc Sat Oct 21 01:47:41 1995 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA19060 for doc-outgoing; Sat, 21 Oct 1995 01:47:41 -0700 Received: from strider.ibenet.it (root@strider.ibe.net [194.179.130.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA19031 for ; Sat, 21 Oct 1995 01:47:31 -0700 Received: (from piero@localhost) by strider.ibenet.it (8.6.12/8.6.12) id JAA21395; Sat, 21 Oct 1995 09:46:31 +0100 From: Piero Serini Message-Id: <199510210846.JAA21395@strider.ibenet.it> Subject: Re: http://www.FreeBSD.org/What/ To: jhs@vector.eikon.e-technik.tu-muenchen.de (Julian H. Stacey) Date: Sat, 21 Oct 1995 09:46:30 +0100 (MET) Cc: doc@freebsd.org In-Reply-To: <199510201815.TAA09290@vector.eikon.e-technik.tu-muenchen.de> from "Julian H. Stacey" at Oct 20, 95 07:15:47 pm Reply-To: piero@strider.ibenet.it Operating-System: FreeBSD 1.1.5.1 X-Phone-Number: +39 (2) 58113562 X-NCC-RegID: it.ibenet X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 478 Sender: owner-doc@freebsd.org Precedence: bulk Hello. Quoting from Julian H. Stacey (Fri Oct 20 19:15:47 1995): > Any chance we can remove usage of `hackers' & put something (Anything !) else > instead ? Any chance we can make that word a link to a page with the correct meaning of the word itself? Bye, -- # $Id: .signature,v 1.12 1995/08/14 12:10:54 piero Exp $ Piero Serini Via Giambologna, 1 I 20136 Milano - ITALY From owner-freebsd-doc Sat Oct 21 12:51:40 1995 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA10655 for doc-outgoing; Sat, 21 Oct 1995 12:51:40 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA10633 for ; Sat, 21 Oct 1995 12:51:27 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id UAA01499 for ; Sat, 21 Oct 1995 20:51:10 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id UAA20542 for doc@freebsd.org; Sat, 21 Oct 1995 20:51:09 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id UAA18548 for doc@freebsd.org; Sat, 21 Oct 1995 20:29:52 +0100 From: J Wunsch Message-Id: <199510211929.UAA18548@uriah.heep.sax.de> Subject: Some update To: doc@freebsd.org Date: Sat, 21 Oct 1995 20:29:51 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 22765 Sender: owner-doc@freebsd.org Precedence: bulk Hi Doc :-) Well, after i finally figured out how to convert all these funny SGML files into something human-readable, and it turned out that even a simple "make" would do , i've took the time to update some of the portions, mainly those that originated from me. Guys, GREAT work that you've done here! Here's the updates. Everything is against the 2.1.0 branch, in hope that this wouldn't be too late yet for 2.1. -- Jörg Index: handbook/authors.sgml =================================================================== RCS file: /home/cvs/src/share/doc/handbook/authors.sgml,v retrieving revision 1.3.4.2 diff -u -r1.3.4.2 authors.sgml --- 1.3.4.2 1995/10/12 03:15:42 +++ authors.sgml 1995/10/21 18:03:13 @@ -55,7 +55,7 @@ "> -"> Index: handbook/basics.sgml =================================================================== RCS file: /home/cvs/src/share/doc/handbook/basics.sgml,v retrieving revision 1.1.1.1.4.2 diff -u -r1.1.1.1.4.2 basics.sgml --- 1.1.1.1.4.2 1995/10/12 03:15:43 +++ basics.sgml 1995/10/21 13:06:35 @@ -45,7 +45,12 @@ % man 1 chmod which will display the manual page for the user command - chmod. + chmod. References to a particular + section of the on-line manual are traditionally placed + in paranthesis in written documentation; so + chmod(1) refers to the chmod + user command, while chmod(2) + means the system call.

This is fine if you know the name of the command and forgot how to use it, but what if you cannot recall the @@ -57,7 +62,21 @@ With this command you will be presented with a list of commands that have the keyword `mail' in their - descriptions. + descriptions. This is the same as the separate command + apropos. + +

You are seeing all those fancy commands in + /usr/bin, but don't even have the silliest idea + what most of the names do actually stand for? Simply + do a + + % cd /usr/bin; man -f * + + or + + % cd /usr/bin; whatis * + + which is the same. GNU Info files Index: handbook/booting.sgml =================================================================== RCS file: /home/cvs/src/share/doc/handbook/booting.sgml,v retrieving revision 1.2.4.2 diff -u -r1.2.4.2 booting.sgml --- 1.2.4.2 1995/10/12 03:15:47 +++ booting.sgml 1995/10/21 18:56:43 @@ -107,7 +107,7 @@ Initialize user-land things

To get the user-land going, when the kernel has finished - initialization, it will create a with ``/sbin/init''. @@ -115,8 +115,11 @@ in mind that: there is no stdin/out/err unless you open it yourself, if you exit, - the machine panics signal handling is special for ``/stand/sysinstall'' + program on the installation floppy. Interesting combinations Index: handbook/contrib.sgml =================================================================== RCS file: /home/cvs/src/share/doc/handbook/contrib.sgml,v retrieving revision 1.15.2.2 diff -u -r1.15.2.2 contrib.sgml --- 1.15.2.2 1995/10/12 03:15:48 +++ contrib.sgml 1995/10/21 18:04:57 @@ -254,7 +254,7 @@ James da Silva <jds@cs.umd.edu> et al Jay Fenlason <hack@datacube.com> Jim Wilson <wilson@moria.cygnus.com> - Joerg Lohse <lohse@tech7.informatik.uni-hamburg.de> + Jörg Lohse <lohse@tech7.informatik.uni-hamburg.de> Jörg Wunsch <joerg_wunsch@uriah.heep.sax.de> John Dyson - <formerly dyson@ref.tfs.com> John Polstra <jdp@polstra.com> Index: handbook/install.sgml =================================================================== RCS file: /home/cvs/src/share/doc/handbook/install.sgml,v retrieving revision 1.9.2.2 diff -u -r1.9.2.2 install.sgml --- 1.9.2.2 1995/10/18 04:36:28 +++ install.sgml 1995/10/21 12:48:59 @@ -202,11 +202,16 @@ Not yet! We'd like to add support for this someday, but are still lacking anyone to actually do the work. - Ongoing work with Linux's PCEMU utility may bring this + Ongoing work with Linux's DOSEMU utility may bring this much closer to being a reality sometime soon. Send mail to hackers@freebsd.org if you're interested in joining this effort! + However, there's a nice application available in the + called pcemu, + that allows you to run many basic MS-DOS text-mode binaries + by entirely emulating an 8088 CPU. + Supported Configurations @@ -244,7 +249,9 @@ Adaptec 274X/284X/2940 (Narrow/Wide/Twin) series EISA/VLB/PCI SCSI controllers - Adaptec AIC-6260 and AIC-6360 based boards, + Adaptec + + AIC-6360 based boards, which includes the AHA-152x and SoundBlaster SCSI cards. @@ -366,6 +373,8 @@ BOCA IOAT66 6 port serial card using shared IRQ. + BOCA 2016 16 port serial card using shared IRQ. + Cyclades Cyclom-y Serial Board. STB 4 port card using shared IRQ. @@ -453,12 +462,14 @@ You will also need, at minimum, as many 1.44MB or 1.2MB floppies as it takes to hold all files in the bin - (binary distribution) directory. THESE floppies *must* + (binary distribution) directory. THESE floppies must be formatted using MS-DOS, using with the FORMAT command in MS-DOS or the File Manager format command in Microsoft Windows(tm). Factory preformatted floppies will also work well, provided that they haven't been - previously used for something else. + previously used for something else. Note that only media + without any defects are usable for these floppies; there + is no kind of bad sector remapping available for them. Many problems reported by our users in the past have resulted from the use of improperly formatted media, so Index: handbook/kernelconfig.sgml =================================================================== RCS file: /home/cvs/src/share/doc/handbook/kernelconfig.sgml,v retrieving revision 1.1 diff -u -r1.1 kernelconfig.sgml --- 1.1 1995/10/07 04:31:31 +++ kernelconfig.sgml 1995/10/21 13:44:48 @@ -192,6 +192,11 @@ your kernel's name in quotation marks if it contains any numbers. + Since this name is passed to the C compiler as a + -D switch, don't use names like + DEBUG, or something that could be confused + with another machine or CPU name, like vax. + maxusers number

This file sets the size of a number of important @@ -294,7 +299,8 @@ Windows. For example, you can create a console xterm by typing xterm -C, which will display any `write', `talk', and other messages you - receive. + receive, as well as any console messages sent by the + kernel. options SYSVSHM @@ -381,6 +387,7 @@ is a pretend filesystem mounted on /proc which allows programs like ps(1) to give you more information on what processes are running. + <-- XXX why? it's perfectly working as LKM. joerg --> Leave it in. options MFS @@ -624,6 +631,16 @@

Support for SCSI CD-ROM drives. +

Note that the number 0 in the above entries + is slightly misleading: all these devices are + automatically configured as they are found, regardless + of how many of them are hooked up to the SCSI bus(es), + and which target IDs they have. + + If you want to ``wire down'' specific target IDs to + particular devices, refer to the appropriate section + of the LINT kernel config file. + Console, Bus Mouse, and X Server Support @@ -652,9 +669,13 @@ console driver, backwards compatible to VT100/102. It works well on some laptops which have hardware incompatibilities with sc0. Also, set - your TERM variable to ``vt220'' when you log in if - full-screen programs do not run correctly on this - console. + your TERM variable to ``vt100'' or ``vt220'' when + you log in. This driver might also prove useful + when connecting to a large number of different + machines over the network, where the termcap + or terminfo entries for the sc0 + device are often not available -- ``vt100'' should be + available on virtually any platform. @@ -712,7 +733,17 @@ it from FreeBSD. If you have a multiport serial card, check the manual page for sio(4) for more information on the proper values for these - lines. + lines. Some video cards (notably + those based on S3 chips) use IO addresses of the + form 0x*2e8, and since many cheap serial + cards do not fully decode the 16-bit IO address + space, they clash with these cards, making the + COM4 port practically unavailable. + + Each serial port is required to have a unique + IRQ (unless you are using one of the multiport cards + where shared interrupts are supported), so the default + IRQs for COM3 and COM4 cannot be used! device lpt0 at isa? port? tty irq 7 vector lptintr @@ -958,7 +989,7 @@

Stand-alone 6850 UART for MIDI. - device pca0 at isa? port ``IO_TIMER1'' tty + device pca0 at isa? port ``IO_TIMER1'' tty

Digital audio through PC speaker. This is going to be very poor sound quality and quite CPU-intensive, @@ -1060,6 +1091,9 @@ game NetHack (in the ports collection) can be configured to use this device to play songs when you play musical instruments in the game. + +

See also the device. Index: handbook/kerneldebug.sgml =================================================================== RCS file: /home/cvs/src/share/doc/handbook/kerneldebug.sgml,v retrieving revision 1.3.2.1 diff -u -r1.3.2.1 kerneldebug.sgml --- 1.3.2.1 1995/10/12 03:16:09 +++ kerneldebug.sgml 1995/10/21 18:55:51 @@ -26,10 +26,8 @@ normally arranged via /etc/sysconfig and /etc/rc. Alternatively, you can hard-code the dump device via the `dump' clause in the `config' line - of your kernel config file. This is deprecated, but might be the - only chance to get a crash dump from a kernel that's not booting at - all, so that you didn't had the ability to run any command before it - used to crash. + of your kernel config file. This is deprecated, use only if you + want a crash dump from a kernel that crashes during booting. Note: In the following, the term `kgdb' refers to gdb run in `kernel debug mode'. This can be accomplished by @@ -44,7 +42,7 @@ programs will drastically increase, and since the whole kernel is loaded entirely at boot time and cannot be swapped out later, several megabytes of - physical RAM will be wasted. + physical memory will be wasted. If you are testing a new kernel, for example by typing the new kernel's name at the boot prompt, but need to boot a different @@ -58,7 +56,9 @@ exit # ...to multi-user This instructs savecore(8) to use another kernel for symbol name - extraction. It would otherwise default to the currently running kernel. + extraction. It would otherwise default to the currently running kernel + and most likely not do anything at all since the crash dump and the + kernel symbols differ. Now, after a crash dump, go to /sys/compile/WHATEVER and run kgdb. From kgdb do: @@ -70,22 +70,8 @@ and voila, you can debug the crash dump using the kernel sources just like you can for any other program. - If your kernel panicked due to a trap, perhaps the most common - case for getting a core dump, the following trick might help - you. Examine the stack using kgdb's `where' command, - and look for the stack frame in the function trap(). Go `up' - to that frame, and then type: - - frame frame->tf_ebp frame->tf_eip - - This will tell kgdb to go to the stack frame explicitly named by a - frame pointer and instruction pointer, which is the location where - the trap occured. There are still some bugs in kgdb (you can go - `up' from there, but not `down'; the stack trace will still remain - as it was before going to here), but generally this method will lead - you much closer to the failing piece of code. - - Here's a script log of a kgdb session illustrating the above. Long + Here's a script log of a kgdb session illustrating the + procedure. Long lines have been folded to improve readability, and the lines are numbered for reference. Despite of this, it's a real-world error trace taken during the development of the pcvt console driver. @@ -180,9 +166,13 @@ a page fault trap though. trap() in the stack trace. -COPTFLAGS?=-O. Add the -g option @@ -270,14 +256,17 @@ Ctrl-Alt-ESC. For syscons, this can be remapped, and some of the distributed maps do this, so watch out. There's an option - available for a COMCONSOLE kernel (``options BREAK_TO_DEBUGGER'') + available for serial consoles that allows the use of a serial line BREAK on the console line to - enter DDB. + enter DDB (``options BREAK_TO_DEBUGGER'' + in the kernel config file). It is not the default since there are a lot of + crappy serial adapters around that gratuitously generate a + BREAK condition for example when pulling the cable. The third way is that any panic condition will branch to DDB if - the kernel is configured to use it. It is not wise to - configure a kernel with DDB for a machine running unattended - for this reason. + the kernel is configured to use it. + For this reason, it is not wise to + configure a kernel with DDB for a machine running unattended. The DDB commands roughly resemble some gdb commands. The first you probably need is to set a breakpoint: @@ -325,7 +314,7 @@ n - Note: this is different from gdb's `next' statement, it's like + Note: this is different from gdb's `next' statement, it's like gdb's `finish'. To examine data from memory, use (for example): @@ -364,7 +353,7 @@ Alternatively, you can display a single register value by e.g. - print $eax + p $eax and modify it by @@ -412,14 +401,24 @@ is the final way out of disaster and almost the same as hitting the Big Red Button. + If you nead a short command summary, simply type + + help + + However, it's highly recommended to have a printed copy of the + ddb(4) manual page ready for a debugging session. + Remember that it's hard to read the on-line manual while + single-stepping the kernel. Debugging a console driver

Since you need a console driver to run DDB on, things are more - complicated if the console driver itself is flakey. You might - remember the options COMCONSOLE line, and hook up a standard + complicated if the console driver itself is failing. You might + remember the use of a serial console (either with modified boot + blocks, or by specifying -h at the Boot: + prompt), and hook up a standard terminal onto your first serial port. DDB works on any configured - console driver, of course it also works on a COMCONSOLE. + console driver, of course also on a serial console. Index: handbook/memoryuse.sgml =================================================================== RCS file: /home/cvs/src/share/doc/handbook/memoryuse.sgml,v retrieving revision 1.1.4.2 diff -u -r1.1.4.2 memoryuse.sgml --- 1.1.4.2 1995/10/12 03:16:13 +++ memoryuse.sgml 1995/10/21 19:05:24 @@ -11,26 +11,26 @@ what 0-640K gets used for, does the kernel load there or higher, is the kernel relocated, etc. Is there a paper on this? -The boot sector will be loaded at 0:0x7c00, and relocates itself -immediately to 0x7c0:0. (This is nothing magic, just an adjustment -for the %cs selector, done by an ljmp.) +The boot sector will be loaded at 0:0x7c00, and relocates itself +immediately to 0x7c0:0. (This is nothing magic, just an adjustment +for the %cs selector, done by an ljmp.) -It then loads the first 15 sectors at 0x10000 (segment BOOTSEG in the -biosboot Makefile), and sets up the stack to work below 0x1fff0. +It then loads the first 15 sectors at 0x10000 (segment BOOTSEG in the +biosboot Makefile), and sets up the stack to work below 0x1fff0. After this, it jumps to the entry of boot2 within that code. I.e., it jumps over itself and the (dummy) partition table, and it's going to adjust the %cs selector---we are still in 16-bit mode there. -boot2 asks for the boot file, and examines the a.out header. It masks -the file entry point (usually 0xf0100000) by 0x00ffffff, and loads the -file there. Hence the usual load point is 1 MB (0x00100000). During +boot2 asks for the boot file, and examines the a.out header. It masks +the file entry point (usually 0xf0100000) by 0x00ffffff, and loads the +file there. Hence the usual load point is 1 MB (0x00100000). During load, the boot code toggles back and forth between real and protected mode, to use the BIOS in real mode. -The boot code itself uses segment selectors 0x18 and 0x20 for %cs and -%ds/%es in protected mode, and 0x28 to jump back into real mode. The -kernel is finally started with %cs 0x08 and %ds/%es/%ss 0x10, which -refer to dummy descriptors covering the whole address space. +The boot code itself uses segment selectors 0x18 and 0x20 for %cs and +%ds/%es in protected mode, and 0x28 to jump back into real mode. The +kernel is finally started with %cs 0x08 and %ds/%es/%ss 0x10, which +refer to dummy descriptors covering the entire address space. The kernel will be started at its load point. Since it's been linked for another (high) address, it will have to execute PIC until the page @@ -38,9 +38,6 @@ paging will be enabled and the kernel will finally run at the address for which it was linked. -The kernel still skips over the first 0x500 bytes of code, in the -assumption this were valuable BIOS data space (back from old days -where it has been loaded low). Contributed by &a.davidg;. 16 Apr 1995. @@ -48,7 +45,7 @@ The physical pages immediately following the kernel BSS contain proc0's page directory, page tables, and upages. Some time later when the VM system is initialized, the physical memory between -0x1000-0x9ffff and the physical memory after the kernel +0x1000-0x9ffff and the physical memory after the kernel (text+data+bss+proc0 stuff+other misc) is made available in the form of general VM pages and added to the global free page list. Index: handbook/relnotes.sgml =================================================================== RCS file: /home/cvs/src/share/doc/handbook/relnotes.sgml,v retrieving revision 1.4.2.1 diff -u -r1.4.2.1 relnotes.sgml --- 1.4.2.1 1995/10/12 03:16:30 +++ relnotes.sgml 1995/10/21 12:25:56 @@ -383,7 +383,7 @@ WD7000 driver Owner: Olof Johansson (offe@ludd.luth.se) - Pcvt Console driver Owner: Joerg Wunsch + Pcvt Console driver Owner: Jörg Wunsch (joerg@FreeBSD.org) Submitted by: Hellmuth Michaelis -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)