From owner-freebsd-doc Sun May 26 01:41:04 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA14349 for doc-outgoing; Sun, 26 May 1996 01:41:04 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA14309; Sun, 26 May 1996 01:40:39 -0700 (PDT) Received: from palmer.demon.co.uk (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-1) with ESMTP id JAA07810; Sun, 26 May 1996 09:32:19 +0100 (BST) To: doc@FreeBSD.ORG CC: FAQ@FreeBSD.ORG From: "Gary Palmer" Subject: Gregory D Moncreaff: Using Bernoulli 230 under FreeBSD 2.1 Date: Sun, 26 May 1996 09:32:17 +0100 Message-ID: <7808.833099537@palmer.demon.co.uk> Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Someone may like to look at this and put it in the doc somewhere. It looks like one of these little tit bits of info that we should try and publish somewhere to save other people hassle/worry/hair loss... Thanks Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info ------- Forwarded Message Date: Fri, 24 May 1996 13:42:00 -0400 From: Gregory_D_Moncreaff@ccmail.ed.ray.com To: gpalmer@FreeBSD.org, info@iomega.com, Robert_Connelly@ccmail.ed.ray.com, Gregory_D_Moncreaff@ccmail.ed.ray.com Subject: Using Bernoulli 230 under FreeBSD 2.1 I noticed that there wasn't any information about using the Bernoulli 230 (or any removable media) under FreeBSD 2.1 ( a BSD 4.4 Lite based unix ) The Bernoulli was recognized by the SCSI adapter(with some warning/error messages): ---------------------------------------------------------------------- ahc0 rev 0 int a irq 15 on pci0:17 ahc0: aic7870 Ultra Single Channel, SCSI Id=7, aic7870, 255 SCBs ahc0 waiting for scsi devices to settle ... ahc0:A:6: refuses syncronous negotiation. Using asyncronous transfers (ahc0:6:0): "IOMEGA BETA230 2.02" type 0 removable SCSI 2 sd1(ahc0:6:0): Direct-Access sd1(ahc0:6:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd1 could not mode sense (4). Using ficticious geometry 220MB (450566 512 byte sectors) ---------------------------------------------------------------------- --- I had to change the partition sysid from DOS (the disk was originally formatted for DOS) to FreeBSD via the 'fdisk' program : ---------------------------------------------------------------------- # fdisk /dev/sd1 ******* Working on device /dev/sd1 ******* parameters extracted from in-core disklabel are: cylinders=220 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=220 heads=64 sectors/track=32 (2048 blks/cyl) Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 0 is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 32, size 450528 (219 Meg), flag 80 beg: cyl 0/ sector 1/ head 1; end: cyl 219/ sector 32/ head 63 ---------------------------------------------------------------------- I added the following section to '/etc/disktab' ---------------------------------------------------------------------- # Bernoulli transportable 230 (a really big floppy) bern230:\ :ty=winchester:dt=SCSIse#512:nt#64:ns#32:nc#220:rm#3600:\ :pa#447280:oa#0:ba#4096:fa#512:ta=4.2BSD: \ :pb#447280:ob#0:bb#4096:fb#512:tb=4.2BSD: \ :pc#447280:oc#0:bc#4096:fc#512:tc=4.2BSD: ---------------------------------------------------------------------- I the used 'newfs' to format the disk ---------------------------------------------------------------------- # newfs -T bern230 /dev/sd1s4 ---------------------------------------------------------------------- I then could mount and read/write the disk ---------------------------------------------------------------------- # mount /dev/sd1s4 /bern # df /bern Filesystem 512-blocks Used Avail Capacity Mounted on /dev/sd1s4 422255 1 388473 0% /bern ---------------------------------------------------------------------- The related man pages refer to a command 'disklabel' whose write operations are not supported by the Bernoulli disk/drive. There will be messages logged to console about the disk not being labeled that can be (safely?) ignored. The output of 'disklabel', below, would have, for a standard disk, type be 'SCSI', disk be a disk/bios partition name, eg 'sd1', and the interleave should be non-zero. ---------------------------------------------------------------------- # disklabel /dev/sd1 # /dev/sd1: type: unknown disk: label: flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 64 sectors/cylinder: 2048 cylinders: 220 sectors/unit: 450566 rpm: 0 interleave: 0 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 3 partitions: # size offset fstype [fsize bsize bps/cpg] c: 450566 0 unused 0 0 # (Cyl. 0 - 220*) Warning, revolutions/minute 0 boot block size 0 super block size 0 ====================================================================== If any of this could be improved, I'd appreciate a response to this message indicating how so. Feel free to distribute this info (with standard disclaimers!) dist: System Administration: Gary Palmer Iomega Info: ------- End of Forwarded Message From owner-freebsd-doc Sun May 26 14:16:11 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA18247 for doc-outgoing; Sun, 26 May 1996 14:16:11 -0700 (PDT) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA18239 for ; Sun, 26 May 1996 14:16:06 -0700 (PDT) Received: from campa.panke.de (anonymous234.ppp.cs.tu-berlin.de [130.149.17.234]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id XAA22360 for ; Sun, 26 May 1996 23:13:53 +0200 Received: (from wosch@localhost) by campa.panke.de (8.6.12/8.6.12) id SAA10831; Sun, 26 May 1996 18:27:34 +0200 Date: Sun, 26 May 1996 18:27:34 +0200 From: Wolfram Schneider Message-Id: <199605261627.SAA10831@campa.panke.de> To: doc@FreeBSD.ORG Subject: Unix Programmer's Manual, Seventh Edition Reply-to: Wolfram Schneider MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk AT&T put the manual pages for Seventh research edition of the Unix Time-Sharing System online: ftp://netlib.att.com/pub/netlib/att/cs/v7man/ (only 240K if gzip'd) This should be documented in the handbook and/or WWW server as a reference README: These subdirectories contain Unix Programmer's Manual Seventh Edition, Volume 2A January, 1979 as it was distributed with the Seventh research edition of the Unix Time-Sharing System. The printed version of the manual contained the following notice. Copyright 1979, Bell Telephone Laboratories Incorporated Holders of a UNIX (TM) software license are permitted to copy this document, or any portion of it, as necessary for licensed use of the software, provided this copyright notice and statement of permission are included. For this machine-readable version, permission is granted to view, store, and prepare reasonable numbers of copies for non-commercial use. All other rights are reserved. For further permission, contact Dennis Ritchie, dmr@research.att.com. From owner-freebsd-doc Sun May 26 14:27:05 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA18829 for doc-outgoing; Sun, 26 May 1996 14:27:05 -0700 (PDT) Received: from Mona (ppp_017.unm.edu [129.24.14.17]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA18824 for ; Sun, 26 May 1996 14:27:00 -0700 (PDT) Received: from Mona.tech.com (localhost [127.0.0.1]) by Mona (8.6.12/8.6.12) with SMTP id PAA02050 for ; Sun, 26 May 1996 15:25:57 -0600 Message-ID: <31A8CC63.41C67EA6@Mona.tech.com> Date: Sun, 26 May 1996 15:25:55 -0600 From: Everette Taylor III X-Mailer: Mozilla 2.01 (X11; I; FreeBSD 2.1.0-RELEASE i386) MIME-Version: 1.0 To: doc@freebsd.org Subject: tutorial device witers guide X-URL: http://www.freebsd.org/tutorials/index.html Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Could you please let me know where I can download a copy of the Tutorial, Writing Device Drivers for FreeBSD. thanks, everette@unm.edu From owner-freebsd-doc Sun May 26 14:49:38 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA21679 for doc-outgoing; Sun, 26 May 1996 14:49:38 -0700 (PDT) Received: from Mona (ppp_017.unm.edu [129.24.14.17]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA21366 for ; Sun, 26 May 1996 14:47:48 -0700 (PDT) Received: from Mona.tech.com (localhost [127.0.0.1]) by Mona (8.6.12/8.6.12) with SMTP id PAA02076 for ; Sun, 26 May 1996 15:43:24 -0600 Message-ID: <31A8D07C.167EB0E7@unm.edu> Date: Sun, 26 May 1996 15:43:24 -0600 From: Everette Taylor III X-Mailer: Mozilla 2.01 (X11; I; FreeBSD 2.1.0-RELEASE i386) MIME-Version: 1.0 To: doc@freebsd.org Subject: writing device drivers for FreeBSD X-URL: http://www.freebsd.org/tutorials/index.html Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Please tell me where I can down a copy of the HTML document "Writing device drivers for FreeBSD". thanks, everette@unm.edu From owner-freebsd-doc Sun May 26 16:31:34 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA09621 for doc-outgoing; Sun, 26 May 1996 16:31:34 -0700 (PDT) Received: from mail.pixi.com (phoenix.pixi.com [204.182.46.6]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA09610 for ; Sun, 26 May 1996 16:31:32 -0700 (PDT) Received: from default (mothra08.pixi.com [140.174.243.139]) by mail.pixi.com (8.6.12/SMI-4.1) with SMTP id NAA05929 for ; Sun, 26 May 1996 13:31:30 -1000 Message-ID: <31A8E87B.79FF@pixi.com> Date: Sun, 26 May 1996 13:25:47 -1000 From: Calvin Umphlett Organization: MAXMINN X-Mailer: Mozilla 2.0 (Win95; I) MIME-Version: 1.0 To: freebsd-doc@FreeBSD.ORG Subject: subscribe X-URL: http://www.freebsd.org/handbook/handbook17.html#19 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk subscribe From owner-freebsd-doc Sun May 26 19:47:15 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA19405 for doc-outgoing; Sun, 26 May 1996 19:47:15 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA19396 for ; Sun, 26 May 1996 19:47:12 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id TAA03518; Sun, 26 May 1996 19:45:36 -0700 (PDT) To: Gary Aitken cc: freebsd-doc@FreeBSD.ORG Subject: Re: sources to doc? In-reply-to: Your message of "Fri, 24 May 1996 17:45:49 MDT." <31A64A2D.1373@ics.com> Date: Sun, 26 May 1996 19:45:36 -0700 Message-ID: <3516.833165136@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Site alias? I'm not sure I follow you.. > > And context diffs submitted via send-pr work just great! > > So what should the site alias be? I would guess there is a set > of things like doc@freebsd.org.? > > -- > Gary Aitken garya@ics.com (business) > garya@dreamchaser.org (personal) From owner-freebsd-doc Sun May 26 23:42:10 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA07939 for doc-outgoing; Sun, 26 May 1996 23:42:10 -0700 (PDT) Received: from zaraza.bofh.org.il (zaraza.bofh.org.il [192.115.153.33]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA07911 for ; Sun, 26 May 1996 23:42:05 -0700 (PDT) Received: from localhost (sgt@localhost [127.0.0.1]) by zaraza.bofh.org.il (8.6.12/8.6.12) with SMTP id JAA27419 for ; Mon, 27 May 1996 09:46:26 +0200 Message-Id: <199605270746.JAA27419@zaraza.bofh.org.il> X-Authentication-Warning: zaraza.bofh.org.il: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.7 5/3/96 To: freebsd-doc@freebsd.org Subject: FreeBSD Handbook on ftp? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 May 1996 09:46:25 +0200 From: Sergei Barbarash Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I wonder if the latest version of the FreeBSD Handbook is available tar.gz'ed somewhere on ftp. The one I got from ftp.freebsd.org/..../doc/ was far outdated - December, I think. Thanks, -- ======================================================================== Sergei Barbarash, NetMedia System Administrator | (972)-2-795860 (w) POB 48253 Jerusalem 91482, Israel | (972)-2-664779 (h) WWW: http://www.bofh.org.il/sgt/ | sgt@netmedia.net.il ======================================================================== From owner-freebsd-doc Mon May 27 04:31:09 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA06290 for doc-outgoing; Mon, 27 May 1996 04:31:09 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA06284; Mon, 27 May 1996 04:31:03 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id NAA01867; Mon, 27 May 1996 13:15:31 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by knobel.gun.de (8.7.5/8.7.3) with SMTP id NAA01804; Mon, 27 May 1996 13:16:30 +0200 (MET DST) Date: Mon, 27 May 1996 13:16:29 +0200 (MET DST) From: Andreas Klemm To: current@freebsd.org cc: doc@freebsd.org Subject: A new hosts.lpd(5) manpage and diffs for lpd(8) and printcap(5) Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1036435388-833195789=:1563" Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1036435388-833195789=:1563 Content-Type: TEXT/PLAIN; charset=US-ASCII -----BEGIN PGP SIGNED MESSAGE----- Hi ! A question from a user in the freebsd newsgroup, why someone isn't able to print via network to his local printer, brought me to the idea to write a hosts.lpd(5) manpage. I think you should add a reference to hosts.lpd(5) in the lpd(8) and printcap(5) manpage. In the attachement I'll send you diffs for - /usr/src/share/man/man5/Makefile - /usr/src/share/man/man5/printcap - /usr/src/usr.sbin/lpr/lpd/lpd.8 and the - manual page itself. Would be nice, if someone could please commit it to the -current, - -2.1 and -stable tree. Andreas /// - -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ $$ Support Unix - aklemm@wup.de $$ pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBMamPDfMLpmkD/U+FAQGmKAQAnHMA6Yk87kfgwHR7Mpz7c2RFd36ULHo8 bR8ybQ+LoldnozVTuU1ZazDRdbjW5R6FXLkC/UsUZEMsCf4qOin1+60+3ycwbehk DCxfE53DFpIjqvUcrNqEVfybgcKPDktMG16mgfMv1QNNVJldXeotpHhOUwxfbXDK r/A032GZibA= =buBN -----END PGP SIGNATURE----- --0-1036435388-833195789=:1563 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="hosts.lpd.5" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: LlwiIENvcHlyaWdodCAoYykgMTk4MywgMTk5MSwgMTk5Mw0KLlwiCVRoZSBS ZWdlbnRzIG9mIHRoZSBVbml2ZXJzaXR5IG9mIENhbGlmb3JuaWEuICBBbGwg cmlnaHRzIHJlc2VydmVkLg0KLlwiDQouXCIgUmVkaXN0cmlidXRpb24gYW5k IHVzZSBpbiBzb3VyY2UgYW5kIGJpbmFyeSBmb3Jtcywgd2l0aCBvciB3aXRo b3V0DQouXCIgbW9kaWZpY2F0aW9uLCBhcmUgcGVybWl0dGVkIHByb3ZpZGVk IHRoYXQgdGhlIGZvbGxvd2luZyBjb25kaXRpb25zDQouXCIgYXJlIG1ldDoN Ci5cIiAxLiBSZWRpc3RyaWJ1dGlvbnMgb2Ygc291cmNlIGNvZGUgbXVzdCBy ZXRhaW4gdGhlIGFib3ZlIGNvcHlyaWdodA0KLlwiICAgIG5vdGljZSwgdGhp cyBsaXN0IG9mIGNvbmRpdGlvbnMgYW5kIHRoZSBmb2xsb3dpbmcgZGlzY2xh aW1lci4NCi5cIiAyLiBSZWRpc3RyaWJ1dGlvbnMgaW4gYmluYXJ5IGZvcm0g bXVzdCByZXByb2R1Y2UgdGhlIGFib3ZlIGNvcHlyaWdodA0KLlwiICAgIG5v dGljZSwgdGhpcyBsaXN0IG9mIGNvbmRpdGlvbnMgYW5kIHRoZSBmb2xsb3dp bmcgZGlzY2xhaW1lciBpbiB0aGUNCi5cIiAgICBkb2N1bWVudGF0aW9uIGFu ZC9vciBvdGhlciBtYXRlcmlhbHMgcHJvdmlkZWQgd2l0aCB0aGUgZGlzdHJp YnV0aW9uLg0KLlwiIDMuIEFsbCBhZHZlcnRpc2luZyBtYXRlcmlhbHMgbWVu dGlvbmluZyBmZWF0dXJlcyBvciB1c2Ugb2YgdGhpcyBzb2Z0d2FyZQ0KLlwi ICAgIG11c3QgZGlzcGxheSB0aGUgZm9sbG93aW5nIGFja25vd2xlZGdlbWVu dDoNCi5cIglUaGlzIHByb2R1Y3QgaW5jbHVkZXMgc29mdHdhcmUgZGV2ZWxv cGVkIGJ5IHRoZSBVbml2ZXJzaXR5IG9mDQouXCIJQ2FsaWZvcm5pYSwgQmVy a2VsZXkgYW5kIGl0cyBjb250cmlidXRvcnMuDQouXCIgNC4gTmVpdGhlciB0 aGUgbmFtZSBvZiB0aGUgVW5pdmVyc2l0eSBub3IgdGhlIG5hbWVzIG9mIGl0 cyBjb250cmlidXRvcnMNCi5cIiAgICBtYXkgYmUgdXNlZCB0byBlbmRvcnNl IG9yIHByb21vdGUgcHJvZHVjdHMgZGVyaXZlZCBmcm9tIHRoaXMgc29mdHdh cmUNCi5cIiAgICB3aXRob3V0IHNwZWNpZmljIHByaW9yIHdyaXR0ZW4gcGVy bWlzc2lvbi4NCi5cIg0KLlwiIFRISVMgU09GVFdBUkUgSVMgUFJPVklERUQg QlkgVEhFIFJFR0VOVFMgQU5EIENPTlRSSUJVVE9SUyBgYEFTIElTJycgQU5E DQouXCIgQU5ZIEVYUFJFU1MgT1IgSU1QTElFRCBXQVJSQU5USUVTLCBJTkNM VURJTkcsIEJVVCBOT1QgTElNSVRFRCBUTywgVEhFDQouXCIgSU1QTElFRCBX QVJSQU5USUVTIE9GIE1FUkNIQU5UQUJJTElUWSBBTkQgRklUTkVTUyBGT1Ig QSBQQVJUSUNVTEFSIFBVUlBPU0UNCi5cIiBBUkUgRElTQ0xBSU1FRC4gIElO IE5PIEVWRU5UIFNIQUxMIFRIRSBSRUdFTlRTIE9SIENPTlRSSUJVVE9SUyBC RSBMSUFCTEUNCi5cIiBGT1IgQU5ZIERJUkVDVCwgSU5ESVJFQ1QsIElOQ0lE RU5UQUwsIFNQRUNJQUwsIEVYRU1QTEFSWSwgT1IgQ09OU0VRVUVOVElBTA0K LlwiIERBTUFHRVMgKElOQ0xVRElORywgQlVUIE5PVCBMSU1JVEVEIFRPLCBQ Uk9DVVJFTUVOVCBPRiBTVUJTVElUVVRFIEdPT0RTDQouXCIgT1IgU0VSVklD RVM7IExPU1MgT0YgVVNFLCBEQVRBLCBPUiBQUk9GSVRTOyBPUiBCVVNJTkVT UyBJTlRFUlJVUFRJT04pDQouXCIgSE9XRVZFUiBDQVVTRUQgQU5EIE9OIEFO WSBUSEVPUlkgT0YgTElBQklMSVRZLCBXSEVUSEVSIElOIENPTlRSQUNULCBT VFJJQ1QNCi5cIiBMSUFCSUxJVFksIE9SIFRPUlQgKElOQ0xVRElORyBORUdM SUdFTkNFIE9SIE9USEVSV0lTRSkgQVJJU0lORyBJTiBBTlkgV0FZDQouXCIg T1VUIE9GIFRIRSBVU0UgT0YgVEhJUyBTT0ZUV0FSRSwgRVZFTiBJRiBBRFZJ U0VEIE9GIFRIRSBQT1NTSUJJTElUWSBPRg0KLlwiIFNVQ0ggREFNQUdFLg0K LlwiDQouRGQgTWFpIDE5OTYNCi5EdCBIT1NUUy5MUEQgNQ0KLk9zIEZyZWVC U0QNCi5TaCBOQU1FDQouTm0gaG9zdHMubHBkDQouTmQgdHJ1c3RlZCBob3N0 cyB0aGF0IG1heSB1c2UgbG9jYWwgcHJpbnQgc2VydmljZXMNCi5TaCBERVND UklQVElPTg0KVGhlDQouTm0gaG9zdHMubHBkDQpmaWxlIGNvbnRhaW5zIGEg bGlzdCBvZiBob3N0bmFtZXMgb3IgSVAgYWRkcmVzc2VzDQp0aGF0IGFyZSBh bGxvd2VkIHRvIHVzZSB5b3VyIGxvY2FsIHByaW50IHNlcnZpY2VzLg0KTGlz dCBldmVyeSBob3N0bmFtZSBvciBJUCBhZGRyZXNzIG9uIGEgbGluZSBpdHNl bGYuDQouU2ggRklMRVMNCi5CbCAtdGFnIC13aWR0aCAvZXRjL2hvc3RzLmxw ZHh4eHh4IC1jb21wYWN0DQouSXQgUGEgL2V0Yy9ob3N0cy5scGQNClRoZQ0K Lk5tIGhvc3RzLmxwZA0KZmlsZSByZXNpZGVzIGluDQouUGEgL2V0YyAuDQou U2ggU0VFIEFMU08NCi5YciBwcmludGNhcCA1ICwNCi5YciBscGQgOCAuDQo= --0-1036435388-833195789=:1563 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="hosts.lpd.diffs" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: SW5kZXg6IE1ha2VmaWxlDQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQpSQ1Mg ZmlsZTogL2N2cy9zcmMvc2hhcmUvbWFuL21hbjUvTWFrZWZpbGUsdg0KcmV0 cmlldmluZyByZXZpc2lvbiAxLjEzDQpkaWZmIC11IC1yMS4xMyBNYWtlZmls ZQ0KLS0tIE1ha2VmaWxlCTE5OTYvMDIvMTIgMDU6MTc6MjcJMS4xMw0KKysr IE1ha2VmaWxlCTE5OTYvMDUvMjcgMTA6NDc6MTENCkBAIC00LDcgKzQsNyBA QA0KIE1BTjU9CWEub3V0LjUgYWNjdC41IGNvcmUuNSBkaXIuNSBkaXNrdGFi LjUgZXRoZXJzLjUgZnMuNSBmYnRhYi41IGZzdGFiLjUgXA0KIAlncm91cC41 IGhvc3RzLjUgbGluay41IG5ldHdvcmtzLjUgcGFzc3dkLjUgcGJtLjUgcGhv bmVzLjUgcHJpbnRjYXAuNSBcDQogCXByb2Nmcy41IHByb3RvY29scy41IHJl bW90ZS41IHJlc29sdmVyLjUgc2VydmljZXMuNSBzaGVsbHMuNSBcDQotCXN0 YWIuNSBzeXNjb25maWcuNSB0eXBlcy41IHV0bXAuNSBob3N0cy5lcXVpdi41 DQorCXN0YWIuNSBzeXNjb25maWcuNSB0eXBlcy41IHV0bXAuNSBob3N0cy5l cXVpdi41IGhvc3RzLmxwZC41DQogTUxJTktTPQlmcy41IGlub2RlLjUgdXRt cC41IHd0bXAuNSB1dG1wLjUgbGFzdGxvZy41IGRpci41IGRpcmVudC41IFwN CiAJcmVzb2x2ZXIuNSByZXNvbHYuY29uZi41IGhvc3RzLmVxdWl2LjUgcmhv c3RzLjUNCg0KSW5kZXg6IHByaW50Y2FwLjUNCj09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT0NClJDUyBmaWxlOiAvY3ZzL3NyYy9zaGFyZS9tYW4vbWFuNS9wcmlu dGNhcC41LHYNCnJldHJpZXZpbmcgcmV2aXNpb24gMS4zDQpkaWZmIC11IC1y MS4zIHByaW50Y2FwLjUNCi0tLSBwcmludGNhcC41CTE5OTYvMDQvMDggMDQ6 MTg6MTgJMS4zDQorKysgcHJpbnRjYXAuNQkxOTk2LzA1LzI3IDExOjA5OjM5 DQpAQCAtMjY5LDEzICsyNjksMTQgQEANCiBFcnJvciBtZXNzYWdlcyBzZW50 IHRvIHRoZSBjb25zb2xlIGhhdmUgYSBjYXJyaWFnZSByZXR1cm4gYW5kIGEg bGluZQ0KIGZlZWQgYXBwZW5kZWQgdG8gdGhlbSwgcmF0aGVyIHRoYW4ganVz dCBhIGxpbmUgZmVlZC4NCiAuU2ggU0VFIEFMU08NCisuWHIgaG9zdHMubHBk IDUgLA0KIC5YciB0ZXJtY2FwIDUgLA0KIC5YciBscGMgOCAsDQogLlhyIGxw ZCA4ICwNCiAuWHIgcGFjIDggLA0KIC5YciBscHIgMSAsDQogLlhyIGxwcSAx ICwNCi0uWHIgbHBybSAxDQorLlhyIGxwcm0gMSAuDQogLlJzDQogLiVUICI0 LjMgQlNEIExpbmUgUHJpbnRlciBTcG9vbGVyIE1hbnVhbCINCiAuUmUNCklu ZGV4OiBscGQuOA0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ0KUkNTIGZpbGU6 IC9jdnMvc3JjL3Vzci5zYmluL2xwci9scGQvbHBkLjgsdg0KcmV0cmlldmlu ZyByZXZpc2lvbiAxLjUNCmRpZmYgLXUgLXIxLjUgbHBkLjgNCi0tLSBscGQu OAkxOTk2LzA1LzA1IDIyOjQwOjQ3CTEuNQ0KKysrIGxwZC44CTE5OTYvMDUv MjcgMTE6MTM6MTINCkBAIC0yMzgsNiArMjM4LDcgQEANCiAuWHIgbHBybSAx ICwNCiAuWHIgc3lzbG9nIDMgLA0KIC5YciBwcmludGNhcCA1ICwNCisuWHIg aG9zdHMubHBkIDUgLA0KIC5YciBscGMgOCAsDQogLlhyIHBhYyA4DQogLlJz DQo= --0-1036435388-833195789=:1563-- From owner-freebsd-doc Mon May 27 08:12:22 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA19240 for doc-outgoing; Mon, 27 May 1996 08:12:22 -0700 (PDT) Received: from Fieber-John.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA19233 for ; Mon, 27 May 1996 08:12:20 -0700 (PDT) Received: from localhost (jfieber@localhost) by Fieber-John.campusview.indiana.edu (8.7.5/8.7.3) with SMTP id KAA03365; Mon, 27 May 1996 10:12:13 -0500 (EST) X-Authentication-Warning: Fieber-John.campusview.indiana.edu: jfieber owned process doing -bs Date: Mon, 27 May 1996 10:12:13 -0500 (EST) From: John Fieber X-Sender: jfieber@Fieber-John.campusview.indiana.edu To: Everette Taylor III cc: doc@freebsd.org Subject: Re: tutorial device witers guide In-Reply-To: <31A8CC63.41C67EA6@Mona.tech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 26 May 1996, Everette Taylor III wrote: > Could you please let me know where I can download a copy of the Tutorial, Writing Device Drivers > for FreeBSD. http://www.freebsd.org/tutorials/ddwg/ddwg-html.tar.gz http://www.freebsd.org/tutorials/ddwg/ddwg.ascii and if you are running FreeBSD, you have the tools to generate these and LaTeX from: http://www.freebsd.org/tutorials/ddwg/ddwg.sgml with the help of http://www.freebsd.org/tutorials/ddwg/Makefile For the mh document, just replace `ddwg' with `mh'. I'll get this information put into the main tutorial page soon. -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================ From owner-freebsd-doc Mon May 27 08:15:51 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA19371 for doc-outgoing; Mon, 27 May 1996 08:15:51 -0700 (PDT) Received: from Fieber-John.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA19363 for ; Mon, 27 May 1996 08:15:47 -0700 (PDT) Received: from localhost (jfieber@localhost) by Fieber-John.campusview.indiana.edu (8.7.5/8.7.3) with SMTP id KAA03381; Mon, 27 May 1996 10:15:29 -0500 (EST) X-Authentication-Warning: Fieber-John.campusview.indiana.edu: jfieber owned process doing -bs Date: Mon, 27 May 1996 10:15:28 -0500 (EST) From: John Fieber X-Sender: jfieber@Fieber-John.campusview.indiana.edu To: Sergei Barbarash cc: freebsd-doc@FreeBSD.ORG Subject: Re: FreeBSD Handbook on ftp? In-Reply-To: <199605270746.JAA27419@zaraza.bofh.org.il> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 27 May 1996, Sergei Barbarash wrote: > I wonder if the latest version of the FreeBSD Handbook is available tar.gz'ed > somewhere on ftp. The one I got from ftp.freebsd.org/..../doc/ was far > outdated - December, I think. It was. Apparently the directory was restored from an ancient backup some time ago. I just noticed a couple days ago and fixed it. The url is: ftp://ftp.freebsd.org/pub/FreeBSD/docs The handbook and FAQ are updated daily from the FreeBSD-current sources. -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================ From owner-freebsd-doc Tue May 28 04:32:15 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA19456 for doc-outgoing; Tue, 28 May 1996 04:32:15 -0700 (PDT) Received: from axiom-nt (axiom-nt.zlin.axiom.cz [193.179.2.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA19432 for ; Tue, 28 May 1996 04:31:55 -0700 (PDT) Received: by axiom-nt with Microsoft Mail id <01BB4C9A.2821F810@axiom-nt>; Tue, 28 May 1996 13:32:46 +-200 Message-ID: From: Robenek Jiri To: "'freebsd-doc@FreeBSD.ORG'" Date: Tue, 28 May 1996 13:32:44 +-200 Encoding: 1 TEXT Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk help From owner-freebsd-doc Tue May 28 08:38:06 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA07889 for doc-outgoing; Tue, 28 May 1996 08:38:06 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA07841 for ; Tue, 28 May 1996 08:37:55 -0700 (PDT) Received: from aesop.rutgers.edu (aesop.rutgers.edu [128.6.59.6]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id IAA05681 for ; Tue, 28 May 1996 08:25:50 -0700 Received: from chang01.rutgers.edu by AESOP.RUTGERS.EDU (PMDF V5.0-6 #8073) id <01I58K7BUJJK003V7M@AESOP.RUTGERS.EDU>; Tue, 28 May 1996 11:25:24 -0400 (EDT) Date: Tue, 28 May 1996 11:23:49 -0400 From: Bill Crosbie Subject: Re: PS version question X-Sender: crosbie@aesop.rutgers.edu To: John Fieber Cc: freebsd-doc@freebsd.org Message-id: <01I58K7BVM4I003V7M@AESOP.RUTGERS.EDU> MIME-version: 1.0 X-Mailer: Windows Eudora Light Version 1.5.2 Content-type: text/plain; charset="us-ascii" Content-transfer-encoding: 7BIT Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 02:19 PM 5/25/96 -0500, John Fieber wrote: >On Fri, 24 May 1996, Bill Crosbie wrote: > >> ftp://ftp.FreeBSD.ORG/pub/FreeBSD/docs/handbook.ps >> >> When I ran it through Acrobat Distiller 2.1, I received the message: >> ============================= >> Distilling: handbook.ps >> Source:t:\common\e-reserv\in-eps\handbook.ps >> Desitination:t:\common\e-reserv\out-pdf\handbook.pdf >> Start Time: Friday, May 24, 1996 at 6:08AM (time set wrong :) >> %%[Error: invalidfileaccess; Offending Command: definefont]%% >> >> Stack: >> /Font >> -dict- >> -dict- > >I checked and the file was a long outdated version that must have >come from an old backup. I've put a new version there new. Try >it out. If it still doesn't work, y suspicion is that it may be >getting tripped up by bitmap fonts that are getting thrown in by >dvips. > I'm still getting the same error. Pity. Would be handy to have a pdf version of the document around. Maybe I'll just do a quick and dirty version of the ascii text with a full text catalog of the contents. That would be a start. Bill =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= "All is strange and vague..." Bill Crosbie "Are we dead?" Microcomputer Analyst "...or is this Ohio?" Chang Science Library Rutgers University Yakko Warner crosbie@aesop.rutgers.edu Dot Warner 908-932-0305 x114 From owner-freebsd-doc Tue May 28 09:02:20 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA09251 for doc-outgoing; Tue, 28 May 1996 09:02:20 -0700 (PDT) Received: from Fieber-John.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA09243 for ; Tue, 28 May 1996 09:02:15 -0700 (PDT) Received: from localhost (jfieber@localhost) by Fieber-John.campusview.indiana.edu (8.7.5/8.7.3) with SMTP id LAA09138; Tue, 28 May 1996 11:01:47 -0500 (EST) X-Authentication-Warning: Fieber-John.campusview.indiana.edu: jfieber owned process doing -bs Date: Tue, 28 May 1996 11:01:46 -0500 (EST) From: John Fieber X-Sender: jfieber@Fieber-John.campusview.indiana.edu To: Bill Crosbie cc: freebsd-doc@FreeBSD.ORG Subject: Re: PS version question In-Reply-To: <01I58K7BVM4I003V7M@AESOP.RUTGERS.EDU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 28 May 1996, Bill Crosbie wrote: > I'm still getting the same error. Pity. Would be handy to have a pdf > version of the document around. Maybe I'll just do a quick and dirty > version of the ascii text with a full text catalog of the contents. That > would be a start. Hmm... I may just have try out a new version of dvips. My TeX installation is of mid 1993 vintage (yes, ancient 386BSD binaries still alive and kicking!) and dvips has gone through many versions since then. Does anyone listening have a more recent version of dvips than 5.521a? If so, would they be willing to give it a whirl and see if Bill can squeeze a pdf file out of it? The thought of trying to upgrade my TeX installation gives me the shiwers... -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================ From owner-freebsd-doc Tue May 28 09:14:16 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA10760 for doc-outgoing; Tue, 28 May 1996 09:14:16 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA10725 for ; Tue, 28 May 1996 09:14:13 -0700 (PDT) Received: from homer18.u.washington.edu (root@homer18.u.washington.edu [140.142.76.2]) by who.cdrom.com (8.6.12/8.6.11) with SMTP id HAA04986 for ; Tue, 28 May 1996 07:21:59 -0700 Received: from cs3-15.u.washington.edu by homer18.u.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA102504; Tue, 28 May 96 07:21:54 -0700 Message-Id: <9605281421.AA102504@homer18.u.washington.edu> Date: Tue, 28 May 96 07:22:32 -0700 From: Ken Marsh X-Mailer: Mozilla 1.2N (Windows; I; 16bit) Mime-Version: 1.0 To: freebsd-doc@FreeBSD.ORG Subject: FreeBSD Documentation - Installing Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk There is an omission in the installation instructions that renders them virtually useless for a first time user, such as myself. You do specify how much disk space is needed, but how many partitions must I make, and how big must they be? I have gathered that a root is required, a user is recommended, and a swap should take around 16MB. Please add a paragraph describing at least a partitioning scheme for a standard intel based BSD system. Thanks for your time, and thank you for preparing the documentation! Ken Marsh From owner-freebsd-doc Tue May 28 15:09:55 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA05918 for doc-outgoing; Tue, 28 May 1996 15:09:55 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA05892 for ; Tue, 28 May 1996 15:09:49 -0700 (PDT) Received: from relay-2.mail.demon.net (disperse.demon.co.uk [158.152.1.77]) by who.cdrom.com (8.6.12/8.6.11) with SMTP id KAA06978 for ; Tue, 28 May 1996 10:56:57 -0700 Received: from post.demon.co.uk ([158.152.1.72]) by relay-2.mail.demon.net id ab27817; 28 May 96 18:34 +0100 Received: from jraynard.demon.co.uk ([158.152.42.77]) by relay-3.mail.demon.net id aa03998; 28 May 96 18:32 +0100 Received: (from fdocs@localhost) by jraynard.demon.co.uk (8.7.5/8.6.12) id RAA09291; Tue, 28 May 1996 17:37:25 GMT Date: Tue, 28 May 1996 17:37:25 GMT Message-Id: <199605281737.RAA09291@jraynard.demon.co.uk> From: James Raynard To: jfieber@indiana.edu CC: doc@freebsd.org In-reply-to: (message from John Fieber on Mon, 27 May 1996 10:12:13 -0500 (EST)) Subject: Re: tutorial device witers guide Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > http://www.freebsd.org/tutorials/ddwg/ddwg.sgml Here's a diff which corrects a number of typos in this document, as well as inserting a few "pauses for breath" where appropriate. One thing I left out, as it's really a matter of style, but shouldn't acronyms, such as ide and scsi, be capitalised? *** ddwg.sgml.orig Tue May 28 16:34:58 1996 --- ddwg.sgml Tue May 28 17:18:55 1996 *************** *** 113,119 **** XXioctl()

! It's argument list is as follows: int XXioctl(dev_t dev, int cmd, caddr_t arg, int flag, struct proc *p) --- 113,119 ---- XXioctl()

! Its argument list is as follows: int XXioctl(dev_t dev, int cmd, caddr_t arg, int flag, struct proc *p) *************** *** 136,148 **** Header Files --- 163,169 ---- io. It is most common in a block device. This is significantly different than the System V model, where only the block driver performs scatter-gather io. Under BSD, character devices are sometimes requested to perform ! scatter-gather io via the readv() and writev() system calls. Header Files *************** *** 279,289 **** This is the structure used by the probe/attach code to detect and ! initialize your device. The This is the structure used by the probe/attach code to detect and ! initialize your device. The XXprobe()

XXprobe() takes a XXattach() --- 297,307 ---- XXprobe()

XXprobe() takes a XXattach() *************** *** 333,339 **** Header Files ! PCI -- Peripheral Computer Interconect Data Structures

Header Files ! PCI -- Peripheral Computer Interconnect Data Structures

A typical driver has the source code in one c-file, say dev.c. The ! driver also can have some include files devreg.h contains device public device register declarations, macros, and other driver specific declarations. Some drivers call this devvar.h instead. Some drivers, such as the dgb (for the Digiboard PC/Xe), --- 419,425 ----

A typical driver has the source code in one c-file, say dev.c. The ! driver also can have some include files; devreg.h contains public device register declarations, macros, and other driver specific declarations. Some drivers call this devvar.h instead. Some drivers, such as the dgb (for the Digiboard PC/Xe), *************** *** 467,473 ****

The standard model for adding a device driver to the Berkeley kernel is to add your driver to the list of known devices. This list is ! dependant on the cpu architecture. If the device is not i386 specific (pccard, pci, scsi), the file is in ``/usr/src/sys/conf/files''. If the device is i386 specific, use ``/usr/src/sys/i386/conf/files.i386''. A typical line looks like: --- 467,473 ----

The standard model for adding a device driver to the Berkeley kernel is to add your driver to the list of known devices. This list is ! dependent on the cpu architecture. If the device is not i386 specific (pccard, pci, scsi), the file is in ``/usr/src/sys/conf/files''. If the device is i386 specific, use ``/usr/src/sys/i386/conf/files.i386''. A typical line looks like: *************** *** 494,501 **** Make room in conf.c

! Now you must edit ``/usr/src/sys/i386/i386/conf.c`` to make an entry ! for your driver. Somewhere near the top, you need to delcare your entry points. The entry for the joystick driver is: #include "joy.h" --- 494,501 ---- Make room in conf.c

! Now you must edit ``/usr/src/sys/i386/i386/conf.c'' to make an entry ! for your driver. Somewhere near the top, you need to declare your entry points. The entry for the joystick driver is: #include "joy.h" *************** *** 547,555 **** Order is what determines the major number of your device. Which is why there will always be an entry for your driver, either null entry points, or actual entry points. It is probably worth noting that this ! is significantly different from SCO and other system V derrivatives, where any device can (in theory) have any major number. This is ! largley a convenience on FreeBSD, due to the way device nodes are created. More on this later. Adding your device to the config file. --- 547,555 ---- Order is what determines the major number of your device. Which is why there will always be an entry for your driver, either null entry points, or actual entry points. It is probably worth noting that this ! is significantly different from SCO and other system V derivatives, where any device can (in theory) have any major number. This is ! largely a convenience on FreeBSD, due to the way device nodes are created. More on this later. Adding your device to the config file. *************** *** 565,578 **** A slightly more complicated entry is for the ``ix'' driver: ! device ix0 at isa? port 0x300 net irq 10 iomem 0xd0000 iosiz 32768 vector ixint ! r This says that we have a device called `ix0' on the isa bus. It uses ! io-port 0x300. It's interrupt will be masked with other devices in the network class. It uses interrupt 10. It uses 32k of shared memory at physical address 0xd0000. It also defines ! it's interrupt handler to be ``ixintr()'' config(8) the kernel.

--- 565,577 ---- A slightly more complicated entry is for the ``ix'' driver: ! device ix0 at isa? port 0x300 net irq 10 iomem 0xd0000 iosiz 32768 vector ixintr This says that we have a device called `ix0' on the isa bus. It uses ! io-port 0x300. Its interrupt will be masked with other devices in the network class. It uses interrupt 10. It uses 32k of shared memory at physical address 0xd0000. It also defines ! its interrupt handler to be ``ixintr()''. config(8) the kernel.

*************** *** 600,606 ****

On FreeBSD, you are responsible for making your own device nodes. The major number of your device is determined by the slot number in the ! device switch. Minor number is driver dependant, of course. You can either run the mknod's from the command line, or add a section to /dev/MAKEDEV.local, or even /dev/MAKEDEV to do the work. I sometimes create a MAKEDEV.dev script that can be run stand-alone or pasted --- 599,605 ----

On FreeBSD, you are responsible for making your own device nodes. The major number of your device is determined by the slot number in the ! device switch. Minor number is driver dependent, of course. You can either run the mknod's from the command line, or add a section to /dev/MAKEDEV.local, or even /dev/MAKEDEV to do the work. I sometimes create a MAKEDEV.dev script that can be run stand-alone or pasted *************** *** 674,680 **** -- Declares the device driver entry points as external. 38 /* ! 39 * delcare your entry points as externs 40 */ 41 42 extern int pcaprobe(struct isa_device *); --- 673,679 ---- -- Declares the device driver entry points as external. 38 /* ! 39 * declare your entry points as externs 40 */ 41 42 extern int pcaprobe(struct isa_device *); *************** *** 692,698 **** Lines 52 - 70 -- This is creates the device switch entry table for your driver. ! This table gets wholesale swapped into the system device switch at the location specified by your major number. In the standard model, these are in /usr/src/sys/i386/i386/conf.c. NOTE: you cannot pick a device major number higher than what exists in conf.c, for example at --- 691,697 ---- Lines 52 - 70 -- This is creates the device switch entry table for your driver. ! This table gets swapped wholesale into the system device switch at the location specified by your major number. In the standard model, these are in /usr/src/sys/i386/i386/conf.c. NOTE: you cannot pick a device major number higher than what exists in conf.c, for example at *************** *** 725,731 **** -- This section is analogous to the config file declaration of your device. The members of the isa_device structure are filled in by what ! is known about your device, I/O port, shared memory segment, etc. we will probably never have a need for two pcaudio devices in the kernel, but this example shows how multiple devices can be supported. --- 724,730 ---- -- This section is analogous to the config file declaration of your device. The members of the isa_device structure are filled in by what ! is known about your device, I/O port, shared memory segment, etc. We will probably never have a need for two pcaudio devices in the kernel, but this example shows how multiple devices can be supported. *************** *** 798,806 **** driver, as opposed to an lkm filesystem, or an lkm system call. 132 /* ! 133 * this macro maps to a funtion which 134 * sets the lkm up for a driver ! 135 * as opposed to a filesystem, systemcall, or misc 136 * lkm. 137 */ 138 MOD_DEV("pcaudio_mod", LM_DT_CHAR, 24, &pcacdevsw); --- 797,805 ---- driver, as opposed to an lkm filesystem, or an lkm system call. 132 /* ! 133 * this macro maps to a function which 134 * sets the lkm up for a driver ! 135 * as opposed to a filesystem, system call, or misc 136 * lkm. 137 */ 138 MOD_DEV("pcaudio_mod", LM_DT_CHAR, 24, &pcacdevsw); *************** *** 826,832 **** 140 /* 141 * this function is called when the module is ! 142 * loaded, it tries to mimic the behavior 143 * of the standard probe/attach stuff from 144 * isa.c 145 */ --- 825,831 ---- 140 /* 141 * this function is called when the module is ! 142 * loaded; it tries to mimic the behavior 143 * of the standard probe/attach stuff from 144 * isa.c 145 */ *************** *** 857,863 **** Lines 169 - 179 ! -- This is the function called when your driver is unloaded, it just displays a message to that effect. 169 /* --- 856,862 ---- Lines 169 - 179 ! -- This is the function called when your driver is unloaded; it just displays a message to that effect. 169 /* *************** *** 898,910 **** 191 #endif /* NICP > 0 */ ! Device Type Idiosyncracies Character Block Network Line Discipline ! Bus Type Idiosyncracies ISA EISA PCI --- 897,909 ---- 191 #endif /* NICP > 0 */ ! Device Type Idiosyncrasies Character Block Network Line Discipline ! Bus Type Idiosyncrasies ISA EISA PCI *************** *** 950,957 **** * control, known in UN*X as a process; it has references to substructures * containing descriptions of things that the process uses, but may share * with related processes. The process structure and the substructures ! * are always addressible except for those marked "(PROC ONLY)" below, ! * which might be addressible only on a processor on which the process * is running. */ struct proc { --- 949,956 ---- * control, known in UN*X as a process; it has references to substructures * containing descriptions of things that the process uses, but may share * with related processes. The process structure and the substructures ! * are always addressable except for those marked "(PROC ONLY)" below, ! * which might be addressable only on a processor on which the process * is running. */ struct proc { From owner-freebsd-doc Tue May 28 21:45:59 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA04850 for doc-outgoing; Tue, 28 May 1996 21:45:59 -0700 (PDT) Received: from felix.iupui.edu (root@felix.iupui.edu [134.68.45.77]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA04845 for ; Tue, 28 May 1996 21:45:56 -0700 (PDT) Received: from corona (jrclark@indy1.indy.net [199.3.65.5]) by felix.iupui.edu (8.6.12/8.6.9) with SMTP id XAA01699 for ; Tue, 28 May 1996 23:45:36 -0500 Date: Tue, 28 May 1996 23:45:36 -0500 Message-Id: <2.2.32.19960528235238.002fea00@felix.iupui.edu> X-Sender: jrclark@felix.iupui.edu X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: docs@freebsd.org From: John Clark Subject: FAQ Contribution: "How do I create emergency boot diskettes?" Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk How do I create emergency boot diskettes? ----------------------------------------- Currently, for FreeBSD version 2.1, emergency recovery is as simple as two floppy disk images. To create an Emergency Boot Diskette Set (EBDS), obtain the floppy disk images from your favorite FreeBSD FTP mirror site, or directly from the primary FTP site: "ftp.freebsd.org/pub/FreeBSD" Boot disks for the current version 2.1 are available from the primary site in the "ftp.freebsd.org/pub/FreeBSD/2.1.0-RELEASE/floppies" directory. Two floppy images are needed for a complete (you hope) recovery kit: boot.flp and fixit.flp. The images will fit on 1.2 MB floppies, but I must suggest that if you are using a 5.25" floppy disk drive, that you convert to a 1.44" HD disk drive, and discard your 5.25" disk drive (the year 2000 is ~ 3 years from now!). To make the disks while running MS-DOS, download rawrite.exe (ftp.freebsd.org/pub/FreeBSD/2.1.0-RELEASE/tools/rawrite.exe), then run it: C:\> rawrite You will be then prompted for the floppy drive letter that contains the disk you want to write (A: or B:), and the name of the image file to write (boot.flp). To make the disks while running a UNIX system: % dd if=boot.flp of=disk_device where disk_device is the /dev entry for the floppy drive. On FreeBSD systems, this is /dev/fd0 for the A: drive and /dev/fd1 for the B: drive. Similarly, create another floppy disk for the "fixit.flp" image file. When needed, the system can be booted using the "boot" floppy. When booted, a menu will be displayed; insert the fixit floppy, and select "Fixit" from the menu. You will then be in a maintenance shell with a reasonable compliment of commands. The floppy is mounted as "/mnt2" and "/mnt" is available for mounting your hard drive volumes. Just two words: "en" "joy." --John [jrclark@indy.net] From owner-freebsd-doc Wed May 29 07:26:25 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA07379 for doc-outgoing; Wed, 29 May 1996 07:26:25 -0700 (PDT) Received: from Fieber-John.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA07366 for ; Wed, 29 May 1996 07:26:20 -0700 (PDT) Received: from localhost (jfieber@localhost) by Fieber-John.campusview.indiana.edu (8.7.5/8.7.3) with SMTP id JAA03080; Wed, 29 May 1996 09:26:11 -0500 (EST) X-Authentication-Warning: Fieber-John.campusview.indiana.edu: jfieber owned process doing -bs Date: Wed, 29 May 1996 09:26:11 -0500 (EST) From: John Fieber X-Sender: jfieber@Fieber-John.campusview.indiana.edu To: Bill Crosbie cc: freebsd-doc@freebsd.org Subject: Re: PS version question In-Reply-To: <01I58K7BVM4I003V7M@AESOP.RUTGERS.EDU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 28 May 1996, Bill Crosbie wrote: > I'm still getting the same error. Pity. Would be handy to have a pdf > version of the document around. Maybe I'll just do a quick and dirty > version of the ascii text with a full text catalog of the contents. That > would be a start. I generated a version that uses times roman rather than the bitmap TeX fonts. However, it looks as though dvips still pulled some bitmap characters in. I suspect they may be from a symbol font. ftp://fallout.campusview.indiana.edu/pub/handbook.ps.gz -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================ From owner-freebsd-doc Wed May 29 08:14:55 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA10566 for doc-outgoing; Wed, 29 May 1996 08:14:55 -0700 (PDT) Received: from aesop.rutgers.edu (aesop.rutgers.edu [128.6.59.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA10557 for ; Wed, 29 May 1996 08:14:51 -0700 (PDT) Received: from chang01.rutgers.edu by AESOP.RUTGERS.EDU (PMDF V5.0-6 #8073) id <01I59Y41AMR4005UE9@AESOP.RUTGERS.EDU>; Wed, 29 May 1996 11:14:33 -0400 (EDT) Date: Wed, 29 May 1996 11:13:07 -0400 From: Bill Crosbie Subject: Re: PS version question X-Sender: crosbie@aesop.rutgers.edu To: John Fieber , Bill Crosbie Cc: freebsd-doc@freebsd.org Message-id: <01I59Y41OKAQ005UE9@AESOP.RUTGERS.EDU> MIME-version: 1.0 X-Mailer: Windows Eudora Light Version 1.5.2 Content-type: text/plain; charset="us-ascii" Content-transfer-encoding: 7BIT Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I generated a version that uses times roman rather than the >bitmap TeX fonts. However, it looks as though dvips still pulled >some bitmap characters in. I suspect they may be from a symbol >font. > >ftp://fallout.campusview.indiana.edu/pub/handbook.ps.gz > John Would have to agree with your assessment. I downloaded the file and had the distiller crap out on me again. :-( I'm going to try downloading the copy that Thomas had suggested and see what happens... but I'll probably wait for a time when I can get in here during the evening to do it. Bill =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= "All is strange and vague..." Bill Crosbie "Are we dead?" Microcomputer Analyst "...or is this Ohio?" Chang Science Library Rutgers University Yakko Warner crosbie@aesop.rutgers.edu Dot Warner 908-932-0305 x114 From owner-freebsd-doc Wed May 29 15:44:22 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA18138 for doc-outgoing; Wed, 29 May 1996 15:44:22 -0700 (PDT) Received: from fresno1-12.valleynet.com (fresno1-12.valleynet.com [206.43.246.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA18132 for ; Wed, 29 May 1996 15:44:18 -0700 (PDT) From: pzasso@lightspeed.net@lightspeed.net Message-Id: <199605292244.PAA18132@freefall.freebsd.org> Date: Wed, 29 May 96 15:46:36 To: Subject: Init string for Bitsurfer Pro X-Mailer: IBM WebExplorer DLL Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am having trouble installing freebsd via the internet. I think the problem lies in my init string for my Motorola Bitsurfer Pro. Any suggestions on how to set it up would be appreciated. Thank You pzasso@vnet.ibm.com From owner-freebsd-doc Wed May 29 19:40:06 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA17838 for doc-outgoing; Wed, 29 May 1996 19:40:06 -0700 (PDT) Received: from pop01.ny.us.ibm.net (pop01.ny.us.ibm.net [165.87.194.251]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA17789 for ; Wed, 29 May 1996 19:40:01 -0700 (PDT) Received: (from mail@localhost) by pop01.ny.us.ibm.net (8.6.9/8.6.9) id CAA24073; Thu, 30 May 1996 02:39:59 GMT Message-Id: <199605300239.CAA24073@pop01.ny.us.ibm.net> From: "Francisco Reyes" To: "FreeBSD doc Mailing list" Date: Mon, 27 May 96 22:43:12 -0400 Reply-To: "Francisco Reyes" Priority: Normal X-Mailer: Francisco Reyes's Registered PMMail 1.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: What to include in hardware compatibility list? Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I would like to get some suggestions on what we should include in a hardware compatibility list for the handbook. After some emails with John Fieber I reached the conclusion that there are many ways that such list could be compiled. One possible approach is to simply have a list of hardware that works with FreeBSD without any special installation procedures. This does not mean that later on we could include other hardware. The possible advantages of this method is that we won't need to ask to many questions to the people filling the forms and that we could get a list compiled sooner. Another approach is to try to have a more comprehensive questionaire with a few more questions and perhaps have a "note" section for hardware pieces that work with FreeBSD, but that need some changes to the standard installation. With this approach we could also ask what is computer used for such as FTP or WWW server and how many clients are supported by it. The possible advantages of this method are that we could have more complete/usefull information and only need to ask users once to fill out forms about their hardware configuration. Some pieces of information that I consider could be asked are: -Computer:make,model,cpu,cpu speed, amount of RAM -Video:make,model,bus type,resolution -Harddrive:make,model,HD type -Soundcard:make,model,options -Cdrom:make,model,bus type -Monitor:make,model,size,resolution -Network card:make,model,network protocol -Use of computers and how many clients are supported From owner-freebsd-doc Wed May 29 20:35:10 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA23296 for doc-outgoing; Wed, 29 May 1996 20:35:10 -0700 (PDT) Received: from pop01.ny.us.ibm.net (pop01.ny.us.ibm.net [165.87.194.251]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA23287 for ; Wed, 29 May 1996 20:35:03 -0700 (PDT) Received: (from mail@localhost) by pop01.ny.us.ibm.net (8.6.9/8.6.9) id DAA28307; Thu, 30 May 1996 03:35:02 GMT Message-Id: <199605300335.DAA28307@pop01.ny.us.ibm.net> From: "Francisco Reyes" To: "FreeBSD doc Mailing list" Date: Mon, 27 May 96 22:43:12 -0400 Reply-To: "Francisco Reyes" Priority: Normal X-Mailer: Francisco Reyes's Registered PMMail 1.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: What to include in hardware compatibility list? Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I would like to get some suggestions on what we should include in a hardware compatibility list for the handbook. After some emails with John Fieber I reached the conclusion that there are many ways that such list could be compiled. One possible approach is to simply have a list of hardware that works with FreeBSD without any special installation procedures. This does not mean that later on we could include other hardware. The possible advantages of this method is that we won't need to ask to many questions to the people filling the forms and that we could get a list compiled sooner. Another approach is to try to have a more comprehensive questionaire with a few more questions and perhaps have a "note" section for hardware pieces that work with FreeBSD, but that need some changes to the standard installation. With this approach we could also ask what is computer used for such as FTP or WWW server and how many clients are supported by it. The possible advantages of this method are that we could have more complete/usefull information and only need to ask users once to fill out forms about their hardware configuration. Some pieces of information that I consider could be asked are: -Computer:make,model,cpu,cpu speed, amount of RAM -Video:make,model,bus type,resolution -Harddrive:make,model,HD type -Soundcard:make,model,options -Cdrom:make,model,bus type -Monitor:make,model,size,resolution -Network card:make,model,network protocol -Use of computers and how many clients are supported From owner-freebsd-doc Wed May 29 20:41:54 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA24358 for doc-outgoing; Wed, 29 May 1996 20:41:54 -0700 (PDT) Received: from mb.tpu.edu.ru (mb.tpu.edu.ru [194.58.182.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA24349 for ; Wed, 29 May 1996 20:41:46 -0700 (PDT) Received: (from kiddy@localhost) by mb.tpu.edu.ru (8.6.12/8.6.12) id LAA02486; Thu, 30 May 1996 11:42:06 +0800 From: "Oleg S. Kolobov" Message-Id: <199605300342.LAA02486@mb.tpu.edu.ru> Subject: PCI SCSI chip To: docs@freebsd.org Date: Thu, 30 May 1996 11:42:06 +0800 (TSD) Cc: kiddy@mb.tpu.edu.ru (Oleg S. Kolobov) X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm having problem addopting PCI SCSI chip's AM53C974 under FreeBSD 2.1. Current release of FreeBSD recognise a chip, but driver is absent. I think is temporary ( need wait :). However, Linux and QNX already heving it :). Thank You. :)leg From owner-freebsd-doc Thu May 30 10:25:03 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA00252 for doc-outgoing; Thu, 30 May 1996 10:25:03 -0700 (PDT) Received: from Fieber-John.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA00232 for ; Thu, 30 May 1996 10:24:59 -0700 (PDT) Received: from localhost (jfieber@localhost) by Fieber-John.campusview.indiana.edu (8.7.5/8.7.3) with SMTP id MAA11032; Thu, 30 May 1996 12:22:19 -0500 (EST) X-Authentication-Warning: Fieber-John.campusview.indiana.edu: jfieber owned process doing -bs Date: Thu, 30 May 1996 12:22:18 -0500 (EST) From: John Fieber X-Sender: jfieber@Fieber-John.campusview.indiana.edu To: Francisco Reyes cc: FreeBSD doc Mailing list Subject: Re: What to include in hardware compatibility list? In-Reply-To: <199605300335.DAA28307@pop01.ny.us.ibm.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 27 May 1996, Francisco Reyes wrote: > One possible approach is to simply have a list of hardware that works > with FreeBSD without any special installation procedures. This does not > mean that later on we could include other hardware. The possible Although it looks good to just have a large list of hardware that work, given the realities of the PC industry, having a list of hardware that is known NOT to work is pretty valuable. We should probably collect records for both working and problematic hardware. > by it. The possible advantages of this method are that we could have > more complete/usefull information and only need to ask users once to > fill out forms about their hardware configuration. It would be nice to have some separation between the basic hardware info, and the commentary. This could allow multiple people to add their own comments/experiences. (just make sure it doesn't degrade into a series of "This fimblewhizzer card is AWESOME" fallowed by "Get real! Its a piece of crap!") > -Computer:make,model,cpu,cpu speed, amount of RAM I think this one may prove problematic. It shouldn't be dispensed of because it may be the best thing for "name brand" computers, but I a lot of people either have no-name computers, or ones they have put together themselves in which case "make" and "model" don't work. For those, a "Motherboard" might be better. Also, I'd throw in a few attributes such as bios vendor and revision (eg AMI, OPTI), chipset (eg Triton), busses (eg ISA, VESA, PCI), and possibly some others. From reading the mailing list over the years, this level of detail seems to be important and particularly useful for people building custom systems just for FreeBSD. > -Use of computers and how many clients are supported This will need some more detail as well. I'll think about this one... -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================ From owner-freebsd-doc Thu May 30 13:11:36 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA18340 for doc-outgoing; Thu, 30 May 1996 13:11:36 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA18334 for ; Thu, 30 May 1996 13:11:33 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id WAA01050; Thu, 30 May 1996 22:10:24 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id WAA04085; Thu, 30 May 1996 22:10:38 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.5/keltia-uucp-2.8) id WAA12575; Thu, 30 May 1996 22:09:18 +0200 (MET DST) From: Ollivier Robert Message-Id: <199605302009.WAA12575@keltia.freenix.fr> Subject: Re: PS version question To: jfieber@indiana.edu (John Fieber) Date: Thu, 30 May 1996 22:09:17 +0200 (MET DST) Cc: crosbie@AESOP.RUTGERS.EDU, freebsd-doc@FreeBSD.ORG In-Reply-To: from John Fieber at "May 28, 96 11:01:46 am" X-Operating-System: FreeBSD 2.2-CURRENT ctm#2043 X-Mailer: ELM [version 2.4ME+ PL19 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It seems that John Fieber said: > Does anyone listening have a more recent version of dvips than > 5.521a? If so, would they be willing to give it a whirl and see I have 5.58 from teTeX. I can generate current's handbook to PS and put it on freefall if you want it. 262 [22:07] roberto@keltia:~/handbook> dvips handbook.dvi -o This is dvipsk 5.58f Copyright 1986, 1994 Radical Eye Software ' TeX output 1996.05.30:2206' -> handbook.ps kpathsea: Running MakeTeXPK cmss17 360 300 magstep\(1.0\) deskjet > if Bill can squeeze a pdf file out of it? The thought of trying > to upgrade my TeX installation gives me the shiwers... That's what I thought till teTeX appeared. It is _easy_ to install and a joy to use. Switching to LaTeX 2e is also a nice thing to do... -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #4: Sun May 26 14:34:02 MET DST 1996 From owner-freebsd-doc Thu May 30 16:25:05 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA14440 for doc-outgoing; Thu, 30 May 1996 16:25:05 -0700 (PDT) Received: from paloalto.access.hp.com (daemon@paloalto.access.hp.com [15.254.56.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA14423 for ; Thu, 30 May 1996 16:25:00 -0700 (PDT) Received: from srmail.sr.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA151708553; Thu, 30 May 1996 16:22:34 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA202598552; Thu, 30 May 1996 16:22:33 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA224338551; Thu, 30 May 1996 16:22:31 -0700 Message-Id: <199605302322.AA224338551@hpnmhjw.sr.hp.com> To: "Francisco Reyes" Cc: "FreeBSD doc Mailing list" Subject: Re: What to include in hardware compatibility list? In-Reply-To: Your message of "Mon, 27 May 1996 22:43:12 EDT." <199605300239.CAA24073@pop01.ny.us.ibm.net> Date: Thu, 30 May 1996 16:22:31 -0700 From: Darryl Okahata Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > One possible approach is to simply have a list of hardware that works > with FreeBSD without any special installation procedures. This does not > mean that later on we could include other hardware. The possible This is a good idea, but I think that it would also be useful to include information on hardware that could CURRENTLY cause problems, e.g.: * Mach64 vs serial ports. * Hardware with buggy or suboptimal drivers (3COM 3C509 boards?). However, any such information would have to include: 1. A datestamp. A listing that's older than six months or more could be suspect (this would also be a great incentive for keeping the listings up-to-date ;-). 2. The OS revision(s) (2.1R, 2.2-960321-SNAP, etc.) to which it is known to apply. Many bugs that are in 2.1R will probably be fixed in 2.2. ;-) 3. Workarounds. ;-) -- 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 May 31 01:38:17 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA29159 for doc-outgoing; Fri, 31 May 1996 01:38:17 -0700 (PDT) Received: from uu.elvisti.kiev.ua ([193.125.28.132]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA29132 for ; Fri, 31 May 1996 01:37:52 -0700 (PDT) Received: from office.elvisti.kiev.ua (office.elvisti.kiev.ua [193.125.28.129]) by uu.elvisti.kiev.ua (8.7.5/8.7.3) with ESMTP id LAA04508; Fri, 31 May 1996 11:40:15 +0300 (EET DST) Received: (from stesin@localhost) by office.elvisti.kiev.ua (8.6.12/8.ElVisti) id LAA08514; Fri, 31 May 1996 11:40:05 +0300 From: "Andrew V. Stesin" Message-Id: <199605310840.LAA08514@office.elvisti.kiev.ua> Subject: Re: What to include in hardware compatibility list? To: jfieber@indiana.edu (John Fieber) Date: Fri, 31 May 1996 11:40:05 +0300 (EET DST) Cc: reyes01@ibm.net, doc@freebsd.org In-Reply-To: from "John Fieber" at May 30, 96 12:22:18 pm X-Mailer: ELM [version 2.4 PL24alpha5] Content-Type: text Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, # # On Mon, 27 May 1996, Francisco Reyes wrote: # # > One possible approach is to simply have a list of hardware that works # > with FreeBSD without any special installation procedures. This does not # > mean that later on we could include other hardware. The possible # # Although it looks good to just have a large list of hardware that # work, given the realities of the PC industry, having a list of # hardware that is known NOT to work is pretty valuable. We should # probably collect records for both working and problematic # hardware. Seconded. Probably the hardware compatibility guide should state: "Generally, any combination of off-the-shelf PC hardware should work. Exclusions are listed below: ... blah-blah ..." # case "make" and "model" don't work. For those, a "Motherboard" # might be better. Seconded. The exact motherboard model is much better and informative. -- With best regards -- Andrew Stesin. +380 (44) 2760188 +380 (44) 2713457 +380 (44) 2713560 "You may delegate authority, but not responsibility." Frank's Management Rule #1. From owner-freebsd-doc Fri May 31 16:20:02 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA21119 for doc-outgoing; Fri, 31 May 1996 16:20:02 -0700 (PDT) Received: from relay-4.mail.demon.net (relay-4.mail.demon.net [158.152.1.108]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA21079 for ; Fri, 31 May 1996 16:19:55 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-4.mail.demon.net id aa10667; 31 May 96 23:14 GMT Received: from jraynard.demon.co.uk ([158.152.42.77]) by relay-3.mail.demon.net id aa13147; 1 Jun 96 0:14 +0100 Received: (from fdocs@localhost) by jraynard.demon.co.uk (8.7.5/8.6.12) id VAA20274; Fri, 31 May 1996 21:14:44 GMT Date: Fri, 31 May 1996 21:14:44 GMT Message-Id: <199605312114.VAA20274@jraynard.demon.co.uk> From: James Raynard To: doc@freebsd.org Subject: Beginner's guide to program development Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello there, I've just written a document for beginners on how to write and develop programs on FreeBSD - how to use the compiler, how to set Emacs up as a development environment, that kind of thing. Would this be of any interest for the Handbook? It's about 25kB, gzip'd and uuencoded, which is probably too big to post to the list - should I just put it in my home directory on freefall? James Raynard, Edinburgh, Scotland jraynard@freebsd.org jraynard@dial.pipex.com james@jraynard.demon.co.uk From owner-freebsd-doc Fri May 31 20:31:08 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA06307 for doc-outgoing; Fri, 31 May 1996 20:31:08 -0700 (PDT) Received: from Fieber-John.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA06302 for ; Fri, 31 May 1996 20:31:01 -0700 (PDT) Received: from localhost (jfieber@localhost) by Fieber-John.campusview.indiana.edu (8.7.5/8.7.3) with SMTP id WAA23208; Fri, 31 May 1996 22:30:46 -0500 (EST) X-Authentication-Warning: Fieber-John.campusview.indiana.edu: jfieber owned process doing -bs Date: Fri, 31 May 1996 22:30:45 -0500 (EST) From: John Fieber X-Sender: jfieber@Fieber-John.campusview.indiana.edu To: James Raynard cc: doc@freebsd.org Subject: Re: Beginner's guide to program development In-Reply-To: <199605312114.VAA20274@jraynard.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 31 May 1996, James Raynard wrote: > I've just written a document for beginners on how to write and develop > programs on FreeBSD - how to use the compiler, how to set Emacs up as > a development environment, that kind of thing. Would this be of any > interest for the Handbook? Maybe, at the very least we can pop it in with the tutorials. Put it up in your ~/public_html directory on freefall for all to see! -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================ From owner-freebsd-doc Fri May 31 21:59:46 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA08638 for doc-outgoing; Fri, 31 May 1996 21:59:46 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA08633 for ; Fri, 31 May 1996 21:59:44 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id VAA13869; Fri, 31 May 1996 21:58:58 -0700 (PDT) To: James Raynard cc: doc@freebsd.org Subject: Re: Beginner's guide to program development In-reply-to: Your message of "Fri, 31 May 1996 21:14:44 GMT." <199605312114.VAA20274@jraynard.demon.co.uk> Date: Fri, 31 May 1996 21:58:58 -0700 Message-ID: <13867.833605138@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I've just written a document for beginners on how to write and develop > programs on FreeBSD - how to use the compiler, how to set Emacs up as > a development environment, that kind of thing. Would this be of any > interest for the Handbook? If it's written in SGML, yeah! Otherwise, we're going to have to find a "ghost formatter" for you before it can go into the handbook. :-) > It's about 25kB, gzip'd and uuencoded, which is probably too big to > post to the list - should I just put it in my home directory on > freefall? Given the caveat above, sure! I'd be happy to look into integrating it. Jordan From owner-freebsd-doc Sat Jun 1 09:39:37 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA26221 for doc-outgoing; Sat, 1 Jun 1996 09:39:37 -0700 (PDT) Received: from mail.kornet.nm.kr (mail.kornet.nm.kr [168.126.63.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA26206 for ; Sat, 1 Jun 1996 09:39:34 -0700 (PDT) Received: from co-B-117 (root@co-B-112.kornet.nm.kr [203.251.125.112]) by mail.kornet.nm.kr (8.6.12+hangul/8.6.9) with SMTP id BAA11821 for ; Sun, 2 Jun 1996 01:38:03 +0900 Message-ID: <31B072F6.1D0EC9A@soback.kornet.nm.kr> Date: Sun, 02 Jun 1996 01:42:30 +0900 From: kim gi jung X-Mailer: Mozilla 3.0b3 (X11; I; Linux 1.2.13 i586) MIME-Version: 1.0 To: freebsd-doc@FreeBSD.ORG Subject: (no subject) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-doc@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk subscribe deepblue@soback.kornet.nm.kr From owner-freebsd-doc Sat Jun 1 09:42:49 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA26795 for doc-outgoing; Sat, 1 Jun 1996 09:42:49 -0700 (PDT) Received: from pop01.ny.us.ibm.net (pop01.ny.us.ibm.net [165.87.194.251]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA26781 for ; Sat, 1 Jun 1996 09:42:42 -0700 (PDT) Received: (from mail@localhost) by pop01.ny.us.ibm.net (8.6.9/8.6.9) id QAA56153; Sat, 1 Jun 1996 16:41:54 GMT Message-Id: <199606011641.QAA56153@pop01.ny.us.ibm.net> From: "Francisco Reyes" To: "Darryl Okahata" , "Andrew V. Stesin" , "John Fieber" , "FreeBSD doc Mailing list" Date: Sat, 01 Jun 96 12:27:44 -0400 Reply-To: "Francisco Reyes" Priority: Normal X-Mailer: Francisco Reyes's Registered PMMail 1.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Hardware compatibility list. Second round. Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk After getting some feedback about what to include in a hardware compatibility list here is what I would like to propose. Information to be collected: -Version of FreeBsd tried on -Computer:make,model,cpu,cpu speed, amount of RAM, motherboard, bios and revision, busses(eg ISA, VESA, PCI), chipset -Video:make,model,bus type,resolution -Harddrive:make,model,HD type -Soundcard:make,model,options -Cdrom:make,model,bus type -Monitor:make,model,size,resolution -Network card:make,model,network protocol -Use of computers and how many clients are supported For each piece of hardware we could have a checkbox button indicating if it worked or not or we could have another form for incompatible hardware. One possible good thing about the separate forms may be less confusion and smaller forms. Some of the questions in the "compatible" form may not need to be included in the second. As for comments I am getting the feeling that the best is to either leave an entry field for a general comment that applies to all pieces or have a few lines for each part. Any comments on this? In the comments for the "compatible" hardware people could write work arounds they did to get the hardware working. > -Use of computers and how many clients are supported The way we could use this part of the form would be to include two or three of the complete configurations we get and place them in an area "FreeBSD computes and their uses". We don't even need to include brands in that since it may be a guide for people in terms of how much horsepower they may need. Darryl Okahata wrote: -> This is a good idea, but I think that it would also be useful to ->include information on hardware that could CURRENTLY cause problems, -> e.g.: * Mach64 vs serial ports. -> However ...... -> 1. ...older than six months or more could be -> suspect -> 2. The OS revision(s) (2.1R, 2.2-960321-SNAP, etc.) to which it is known -> to apply. Many bugs that are in 2.1R will probably be fixed in 2.2. ;-) This is something we need to look into. It may be a little difficult to follow up with imcompatible hardware. A possible approach is to keep incompatibilities in the list until someone says otherwise. A date stamp approach or looking at the entry after a new release of FreeBSD may be difficult to track since after we know we need to look into an entry what should we do about it? Delete it? Post a message requesting comments on whether it still doesn't work? Andrew V. Stesin wrote: -> # case "make" and "model" don't work. For those, a "Motherboard" -> # might be better. -->Seconded. The exact motherboard model is much better and informative. I think it is better to have them both! See the new recommended list on top. Many people may not know what their motherboard is. Those who assembled their computer know, but I am hoping that we can get users that although not experts know their way around a computer. Those may not know many details about their systems. From owner-freebsd-doc Sat Jun 1 10:30:09 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA08052 for doc-outgoing; Sat, 1 Jun 1996 10:30:09 -0700 (PDT) Received: from jolt.eng.umd.edu (jolt.eng.umd.edu [129.2.102.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA08033 for ; Sat, 1 Jun 1996 10:30:05 -0700 (PDT) Received: from gilligan.eng.umd.edu (gilligan.eng.umd.edu [129.2.98.205]) by jolt.eng.umd.edu (8.7.5/8.7.3) with ESMTP id NAA18282; Sat, 1 Jun 1996 13:23:24 -0400 (EDT) Received: (from chuckr@localhost) by gilligan.eng.umd.edu (8.7.5/8.7.3) id NAA26321; Sat, 1 Jun 1996 13:23:23 -0400 (EDT) Date: Sat, 1 Jun 1996 13:23:23 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@gilligan.eng.umd.edu To: Francisco Reyes cc: Darryl Okahata , "Andrew V. Stesin" , John Fieber , FreeBSD doc Mailing list Subject: Re: Hardware compatibility list. Second round. In-Reply-To: <199606011641.QAA56153@pop01.ny.us.ibm.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 1 Jun 1996, Francisco Reyes wrote: > After getting some feedback about what to include in a hardware compatibility list > here is what I would like to propose. > > Information to be collected: > -Version of FreeBsd tried on > -Computer:make,model,cpu,cpu speed, amount of RAM, motherboard, bios and revision, > busses(eg ISA, VESA, PCI), chipset > -Video:make,model,bus type,resolution > -Harddrive:make,model,HD type > -Soundcard:make,model,options > -Cdrom:make,model,bus type > -Monitor:make,model,size,resolution > -Network card:make,model,network protocol > -Use of computers and how many clients are supported Comment: Many folks have a computer made of parts bought here and there. If you don't allow folks to spec the motherboard, well, they can't very well give a name to a 'computer'. Spec'ing the motherboard counts a lot more nowadays than specing the vendor it was bought from. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-doc Sat Jun 1 10:39:35 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA10646 for doc-outgoing; Sat, 1 Jun 1996 10:39:35 -0700 (PDT) Received: from relay-4.mail.demon.net (relay-4.mail.demon.net [158.152.1.108]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA10625 for ; Sat, 1 Jun 1996 10:39:32 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-4.mail.demon.net id af05760; 1 Jun 96 17:39 GMT Received: from jraynard.demon.co.uk ([158.152.42.77]) by relay-3.mail.demon.net id aa05701; 1 Jun 96 18:32 +0100 Received: (from fdocs@localhost) by jraynard.demon.co.uk (8.7.5/8.6.12) id OAA00263; Sat, 1 Jun 1996 14:39:47 GMT Date: Sat, 1 Jun 1996 14:39:47 GMT Message-Id: <199606011439.OAA00263@jraynard.demon.co.uk> From: James Raynard To: jfieber@indiana.edu CC: doc@freebsd.org In-reply-to: (message from John Fieber on Fri, 31 May 1996 22:30:45 -0500 (EST)) Subject: Re: Beginner's guide to program development Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Put it up in your ~/public_html directory on freefall for all to > see! Yes, that's a much better idea. The URL is:- http://freefall.freebsd.org/~jraynard/devel/devel.html Comments, corrections, suggestions for improvements, etc are very welcome, but please send them to me rather than the list. Thanks! -- James Raynard, Edinburgh, Scotland jraynard@freebsd.org jraynard@dial.pipex.com james@jraynard.demon.co.uk From owner-freebsd-doc Sat Jun 1 11:10:34 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA14475 for doc-outgoing; Sat, 1 Jun 1996 11:10:34 -0700 (PDT) Received: from Fieber-John.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA14466 for ; Sat, 1 Jun 1996 11:10:32 -0700 (PDT) Received: from localhost (jfieber@localhost) by Fieber-John.campusview.indiana.edu (8.7.5/8.7.3) with SMTP id NAA27177; Sat, 1 Jun 1996 13:10:27 -0500 (EST) X-Authentication-Warning: Fieber-John.campusview.indiana.edu: jfieber owned process doing -bs Date: Sat, 1 Jun 1996 13:10:25 -0500 (EST) From: John Fieber X-Sender: jfieber@Fieber-John.campusview.indiana.edu To: James Raynard cc: doc@freebsd.org Subject: Re: Beginner's guide to program development In-Reply-To: <199606011439.OAA00263@jraynard.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 1 Jun 1996, James Raynard wrote: > Yes, that's a much better idea. The URL is:- > > http://freefall.freebsd.org/~jraynard/devel/devel.html > > Comments, corrections, suggestions for improvements, etc are very > welcome, but please send them to me rather than the list. How long did it take you to write this?? If you run out of things to write, I'm sure we can come up with some more. ;-> I would move the section on Emacs down just before Further Reading. First cover the compiler, make and debugging, then talk about how emacs can tie these all together. -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================ From owner-freebsd-doc Sat Jun 1 11:58:53 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA19477 for doc-outgoing; Sat, 1 Jun 1996 11:58:53 -0700 (PDT) Received: from pop01.ny.us.ibm.net (pop01.ny.us.ibm.net [165.87.194.251]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA19466 for ; Sat, 1 Jun 1996 11:58:50 -0700 (PDT) Received: (from mail@localhost) by pop01.ny.us.ibm.net (8.6.9/8.6.9) id SAA83863; Sat, 1 Jun 1996 18:58:37 GMT Message-Id: <199606011858.SAA83863@pop01.ny.us.ibm.net> From: "Francisco Reyes" To: "Chuck Robey" Cc: "Andrew V. Stesin" , "Darryl Okahata" , "FreeBSD doc Mailing list" , "John Fieber" Date: Sat, 01 Jun 96 14:57:27 -0400 Reply-To: "Francisco Reyes" Priority: Normal X-Mailer: Francisco Reyes's Registered PMMail 1.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Hardware compatibility list. Second round. Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 1 Jun 1996 13:23:23 -0400 (EDT), Chuck Robey wrote: >On Sat, 1 Jun 1996, Francisco Reyes wrote: >> -Computer:make,model,cpu,cpu speed, amount of RAM, motherboard, bios and >> revision, busses(eg ISA, VESA, PCI), chipset >Comment: Many folks have a computer made of parts bought here and >there. If you don't allow folks to spec the motherboard, well, they >can't very well give a name to a 'computer'. Spec'ing the motherboard >counts a lot more nowadays than specing the vendor it was bought from. Notice that I suggested to have both in the form. Some people may build their own computers, but others may just buy them. If we have space for both then it works for everybody. Some people may not even know many of the names of their components. They can simply fill whatever they know. From owner-freebsd-doc Sat Jun 1 14:10:51 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA04693 for doc-outgoing; Sat, 1 Jun 1996 14:10:51 -0700 (PDT) Received: from paloalto.access.hp.com (daemon@paloalto.access.hp.com [15.254.56.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA04688 for ; Sat, 1 Jun 1996 14:10:49 -0700 (PDT) Received: from srmail.sr.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA033533359; Sat, 1 Jun 1996 14:09:19 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA278473358; Sat, 1 Jun 1996 14:09:19 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA172603357; Sat, 1 Jun 1996 14:09:17 -0700 Message-Id: <199606012109.AA172603357@hpnmhjw.sr.hp.com> To: "Francisco Reyes" Cc: "Andrew V. Stesin" , "John Fieber" , "FreeBSD doc Mailing list" Subject: Re: Hardware compatibility list. Second round. In-Reply-To: Your message of "Sat, 01 Jun 1996 12:27:44 EDT." <199606011641.QAA56153@pop01.ny.us.ibm.net> Date: Sat, 01 Jun 1996 14:09:17 -0700 From: Darryl Okahata Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > For each piece of hardware we could have a checkbox button indicating if it w > orked or > not or we could have another form for incompatible hardware. One possible goo > d thing Wouldn't it make more sense to assume that any listed hardware works (which would be the usual case, otherwise people would probably not be using them with FreeBSD ;-), and, if there are problems, list them in some comments? With the above checkbox approach, I believe most entries will have the box checked, making the checkboxes less useful. > As for comments I am getting the feeling that the best is to either leave an > entry field > for a general comment that applies to all pieces or have a few lines for eac > h part. > Any comments on this? In the comments for the "compatible" hardware people co > uld > write work arounds they did to get the hardware working. Why not have both? I can see cases where comments apply to a particular component, and cases where comments apply to the entire system. > -> This is a good idea, but I think that it would also be useful to > ->include information on hardware that could CURRENTLY cause problems, > -> e.g.: * Mach64 vs serial ports. > -> However ...... > -> 1. ...older than six months or more could be > -> suspect > -> 2. The OS revision(s) (2.1R, 2.2-960321-SNAP, etc.) to which it is known > -> to apply. Many bugs that are in 2.1R will probably be fixed in 2.2. ;- > ) > > This is something we need to look into. It may be a little difficult to follo > w up > with imcompatible hardware. A possible approach is to keep incompatibilities > in the list until someone says otherwise. A date stamp approach or looking at > the entry after a new release of FreeBSD may be difficult to track since afte > r > we know we need to look into an entry what should we do about it? Delete it? > Post a message requesting comments on whether it still doesn't work? No, that's the reason for datestamps and OS revs. If an entry is, say, more than a year old or more than two revs old, it's very suspect. When a new FreeBSD release comes out, nothing HAS to be done with the hardware list, although something probably SHOULD be done with it. Let's take the most probable case: the hardware list is not updated ;-). With date and OS revision stamps, anyone reading the hardware list, and seeing that they have "problem hardware", can at least make at intelligent guess at one of: 1. Their hardware has problems. They're using the same FreeBSD revision mentioned in the problem hardware list. 2. Their hardware might have problems. They're using a newer release of FreeBSD. In this case, they can ask in FreeBSD-questions to see if (1) their hardware is still broken, or (2) the hardware list entry is out-of-date. If it's out of date, we can use this as a trigger to change the entry (someone could re-write the entry and mention that it's fixed in FreeBSD 99.07, and send it off to the docs folks ;-). I think we really need a section on hardware problems; a section on known working hardware, while useful, is no where near as useful as a "problem hardware" section. I'd say that most people reading the hardware list will be doing so to see if their *existing* hardware will work, with the people building a new PC being next. It's not very useful as an "accomplishments list" ("See? BinkyCo's new 1000 Gigaflurb system runs FreeBSD and supports a million users!"); such a list, while useful, is best put elsewhere. Assuming most people reading the hardware list will be doing so to see if their *existing* hardware will work, it's unlikely that they'll find their particular combination of hardware listed in the list. There are just too many commodity part makers out there. Because of this, having a list of known problem parts or known problem part combinations would be more useful. -- 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 Sat Jun 1 17:13:30 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA13772 for doc-outgoing; Sat, 1 Jun 1996 17:13:30 -0700 (PDT) Received: from pop01.ny.us.ibm.net (pop01.ny.us.ibm.net [165.87.194.251]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA13761 for ; Sat, 1 Jun 1996 17:13:26 -0700 (PDT) Received: (from mail@localhost) by pop01.ny.us.ibm.net (8.6.9/8.6.9) id AAA25556; Sun, 2 Jun 1996 00:09:36 GMT Message-Id: <199606020009.AAA25556@pop01.ny.us.ibm.net> From: "Francisco Reyes" To: "Darryl Okahata" Cc: "Andrew V. Stesin" , "FreeBSD doc Mailing list" , "John Fieber" Date: Sat, 01 Jun 96 20:04:25 -0400 Reply-To: "Francisco Reyes" Priority: Normal X-Mailer: Francisco Reyes's Registered PMMail 1.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Hardware compatibility list. Second round. Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 01 Jun 1996 14:09:17 -0700, Darryl Okahata wrote: >> For each piece of hardware we could have a checkbox button indicating if it w >> orked or not or we could have another form for incompatible hardware. > Wouldn't it make more sense to assume that any listed hardware >works (which would be the usual case, otherwise people would probably >not be using them with FreeBSD ;-), and, if there are problems, list >them in some comments? With the above checkbox approach, I believe most >entries will have the box checked, making the checkboxes less useful. I had thought of using the checkbox for hardware that didn't work. In that case then it would be mostly unchecked. > I'd say that most people reading the hardware list will be doing so >to see if their *existing* hardware will work, with the people building >a new PC being next. I think you touched in three things with that comment. I believe that people will find it usefull to have hardware that works, hardware that doesnt' work, and what configurations are used for what. For exising users not finding their hardware in the trouble list is not guarantee that it work. If they find in the list of compatible hardware then they may at least give it a try. >It's not very useful as an "accomplishments list" >("See? BinkyCo's new 1000 Gigaflurb system runs FreeBSD and supports a >million users!"); such a list, while useful, is best put elsewhere. As to what a configuration is used for and the number of users it will certainly be usefull. Some people that may try FreeBSD it do it solely because they have heard some frriend became and ISP and is supporting X number of users with FreeBSD. Another case is that someone wants to know if their current hardware will be enough to support 100 newsgroups or 10,000 newsgroups. In that section I was thinking of not having brands just bare hardware sizes (eg 16MB, 1.2Gig SCSI HD). I had in mind having a few of those sample configuration separate from the compatibility list. > Assuming most people reading the hardware list will be doing so to >see if their *existing* hardware will work, it's unlikely that they'll >find their particular combination of hardware listed in the list. There >are just too many commodity part makers out there. Because of this, >having a list of known problem parts or known problem part combinations >would be more useful. For the same reason (too many combinations of hardware) just having what doesn't work is not enough. Should someone believe that their hardware will work because it is not listed in the "incompatible" section? They may not find the exact match of hardware, but at least they may find some. It may be also helpful in troubleshooting to have both. Perhaps the HD and controller are compatible, but the network card isn't. By having the information at least the user may be warned in certain cases of what they can expect if they try to install/use FreeBSD. From owner-freebsd-doc Sat Jun 1 17:48:32 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA17632 for doc-outgoing; Sat, 1 Jun 1996 17:48:32 -0700 (PDT) Received: from Fieber-John.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA17623 for ; Sat, 1 Jun 1996 17:48:30 -0700 (PDT) Received: from localhost (jfieber@localhost) by Fieber-John.campusview.indiana.edu (8.7.5/8.7.3) with SMTP id TAA28732; Sat, 1 Jun 1996 19:48:26 -0500 (EST) X-Authentication-Warning: Fieber-John.campusview.indiana.edu: jfieber owned process doing -bs Date: Sat, 1 Jun 1996 19:48:23 -0500 (EST) From: John Fieber X-Sender: jfieber@Fieber-John.campusview.indiana.edu Reply-To: John Fieber To: Francisco Reyes cc: FreeBSD doc Mailing list Subject: Re: Hardware compatibility list. Second round. In-Reply-To: <199606020009.AAA25556@pop01.ny.us.ibm.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [cc list trimmed...] On Sat, 1 Jun 1996, Francisco Reyes wrote: > For the same reason (too many combinations of hardware) just > having what doesn't work is not enough. Should someone believe > that their hardware will work because it is not listed in the > "incompatible" section? FreeBSD is in an awkward position with regards to publishing hardware compatibility. It "PC compatible" enough that maintaining any *comprehensive* list of compatible hardware is wildly unrealistic, yet we do not have anywhere near the resources to be able to accurately state that any PC with 8 megabytes of ram and a 100 megabyte hard drive will work. So, buing stuck in the middle, what sort of hardware information is most useful to: * People who already have their hardware and want to run FreeBSD. * People running FreeBSD but having some hardware difficulties. * People in a position of purchasing hardware with the knowledge that they will be running FreeBSD. The first group just wants to know *if* it will work. The second wants to know *how* to get to work, and the latter is probably more interested in how *well* it will work. I suspect the latter group is probably the easiest to satisfy because a fair population of FreeBSD users use pretty high powered systems, and a few are in dealership positions with opportunities to try out the latest and greatest. Information for the second group can only come from existing users war stories about how they managed to get the Zingle 987FX PCI bus vacuum cleaner controller working. The first group is the hardest because they will have *lots* of questions about hardware nobody here has ever heard of. A lot of it will be stuff the "power users" among us wouldn't dream of buying (like ide cdrom drives). I don't think we will ever be able to completely satisfy people in this department, but some effort is warranted. A lot of information to address these three needs exists in collective FreeBSD user community. The task at hand is to enhance access to this. Currently it lies burried in peoples brains, mailing lists, and newsgroup archives. Francisco is working on some web forms for collecting information from people, normalizing it so that it isn't quite so scattered about. Although we may want to put it in the handbook, I'm thinking it may be more useful as an interactive piece of software (web based or otherwize)... -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================ From owner-freebsd-doc Sat Jun 1 17:56:03 1996 Return-Path: owner-doc Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA18454 for doc-outgoing; Sat, 1 Jun 1996 17:56:03 -0700 (PDT) Received: from paloalto.access.hp.com (daemon@paloalto.access.hp.com [15.254.56.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA18447 for ; Sat, 1 Jun 1996 17:56:02 -0700 (PDT) Received: from srmail.sr.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA202166908; Sat, 1 Jun 1996 17:55:09 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA284486908; Sat, 1 Jun 1996 17:55:08 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA262786907; Sat, 1 Jun 1996 17:55:07 -0700 Message-Id: <199606020055.AA262786907@hpnmhjw.sr.hp.com> To: "Francisco Reyes" Cc: "Andrew V. Stesin" , "FreeBSD doc Mailing list" , "John Fieber" Subject: Re: Hardware compatibility list. Second round. In-Reply-To: Your message of "Sat, 01 Jun 1996 20:04:25 EDT." <199606020009.AAA25556@pop01.ny.us.ibm.net> Date: Sat, 01 Jun 1996 17:55:07 -0700 From: Darryl Okahata Sender: owner-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I'd say that most people reading the hardware list will be doing so > >to see if their *existing* hardware will work, with the people building > >a new PC being next. > > I think you touched in three things with that comment. I believe that people > will find it > usefull to have hardware that works, hardware that doesnt' work, and what con > figurations > are used for what. For exising users not finding their hardware in the troubl > e list is not > guarantee that it work. If they find in the list of compatible hardware then > they may > at least give it a try. You misunderstand me. I am *NOT* saying that we should *NOT* have a list of compatible hardware. We need something that contains a list of compatible hardware *AND* problem hardware configurations. We need both. We need a list of compatible hardware, and we also need a list of problem hardware (which is stamped by date and OS rev). It's nice to know what hardware works, but it's a GODSEND to know what hardware configurations have problems or do not work. You can prevent lots of people from wasting lots of time by doing that (and, as a nice side-effect, you might also lower the traffic in FreeBSD-questions ;-). > >It's not very useful as an "accomplishments list" > >("See? BinkyCo's new 1000 Gigaflurb system runs FreeBSD and supports a > >million users!"); such a list, while useful, is best put elsewhere. > > As to what a configuration is used for and the number of users it will certai > nly be usefull. > Some people that may try FreeBSD it do it solely because they have heard some > frriend > became and ISP and is supporting X number of users with FreeBSD. Another case > is > that someone wants to know if their current hardware will be enough to suppor > t 100 No, this belongs in an "accomplishments" or (dare I say it ;-) an "advocacy" list, because: * If you really want to promote FreeBSD, such a list needs constant updating (to keep track of the latest and greatest hardware and accomplishments). * It needs more hype. It would be real BORING if you buried it inside an hardware compatibility list (which could still have an hyperlink to such an advocacy list). * It provides fodder for the "My OS is bigger than your OS" groupies. It's too political. The hardware compatibility list should be practical. -- 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.