From owner-freebsd-doc Sun Jun 11 13:42:13 1995 Return-Path: doc-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA18265 for doc-outgoing; Sun, 11 Jun 1995 13:42:13 -0700 Received: from mpp.com ([204.157.201.242]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA18259 for ; Sun, 11 Jun 1995 13:42:10 -0700 Received: (from mpp@localhost) by mpp.com (8.6.11/8.6.9) id PAA00339 for doc@freebsd.org; Sun, 11 Jun 1995 15:30:58 -0500 From: Mike Pritchard Message-Id: <199506112030.PAA00339@mpp.com> Subject: PPP FAQ To: doc@freebsd.org Date: Sun, 11 Jun 1995 15:30:43 -0500 (CDT) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1088 Sender: doc-owner@freebsd.org Precedence: bulk I would like to suggest making the following changes to the PPP FAQ: *** tmp/ppp.FAQ Sun Jun 11 15:05:32 1995 --- ppp.FAQ Sun Jun 11 15:24:39 1995 *************** *** 4,10 **** Before you start setting up PPP on your machine make sure that pppd is located in /usr/sbin and directory /etc/ppp ! exists. pppd can work in two modes: --- 4,19 ---- Before you start setting up PPP on your machine make sure that pppd is located in /usr/sbin and directory /etc/ppp ! exists. Also make sure that PPP is configured into your kernel. ! First, run "ifconfig -a" and see if "ppp0" appears in the ! list of devices. If not, add the following line to your ! kernel configuration file and rebuild and reboot your kernel: ! ! pseudo-device ppp 1 #Point-to-point protocol ! ! If the "pppd" command prints a message stating that "PPP is not ! available on this system", then you have not properly configured ! PPP into your kernel. pppd can work in two modes: -- Mike Pritchard mpp@legarto.minn.net "Go that way. Really fast. If something gets in your way, turn" From owner-freebsd-doc Thu Jun 15 14:42:02 1995 Return-Path: doc-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA09185 for doc-outgoing; Thu, 15 Jun 1995 14:42:02 -0700 Received: from netcom11.netcom.com (root@netcom11.netcom.com [192.100.81.121]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA09178 for ; Thu, 15 Jun 1995 14:42:01 -0700 Received: from Ðãs’³6 *tá$6¢*tP by netcom11.netcom.com (8.6.12/Netcom) id OAA27130; Thu, 15 Jun 1995 14:41:06 -0700 Date: Thu, 15 Jun 1995 14:41:06 -0700 Message-Id: <199506152141.OAA27130@netcom11.netcom.com> X-Mailer: NCSA Mosaic/2.0.0b4 (Windows x86) X-URL: http://www.freebsd.org:80/How/ From: rjiang@akbs.com (Ruiyuan Jiang) To: doc@freebsd.org Subject: Installing FreeBSD 2.0.5 From Floppy Diskettes Sender: doc-owner@freebsd.org Precedence: bulk I am trying to install FreeBSD Release 2.0.5 to a machine "Compaq luggable" 486 DX-33 with 202MB hard disk, 20 MB RAM(no MS-DOS nothing). I use Kern-Developer and 3.5" diskettes (each diskettes has 6 files on it) options to do installation. After I specified all the options and started to load FreeBSD, the first message I got was "Warning: You have selected a Read-only root device and may be unable to find the appropriate device entries on it if it is from an older pre-slice version of FreeBSD". What I could do at this point was to hit enter to go to the next step. The system started to load from diskette "boot.flp" and rest of them. It seemed OK but when the system asked me to put in file bin\bin.as (started with file bin\bin.as to bin\bin.ax) which in my case is diskette 4. I put in and hit enter. After reading about 3 second, the system prompted me a message "Write failure on transfer! (wrote -1 bytes of 10240 bytes)". I could skip this diskette (I can choose to load it later) and could load next disketts. I tried to reformat the diskette and downloaded all the files again and tried to use brand new diskette, formated it first and downloaded the files and reinstalled FreeBSD but I stucked at the same place and got the same message. Does anyone out there know why? Thanks in advance. Ruiyuan Jiang System Administrator ADVANTAGE kbs, Inc. rjiang@akbs.com (908) 287-2236 FAX (908) 287-3193 From owner-freebsd-doc Thu Jun 15 19:46:32 1995 Return-Path: doc-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA24524 for doc-outgoing; Thu, 15 Jun 1995 19:46:32 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA24517 ; Thu, 15 Jun 1995 19:46:30 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.11/8.6.9) id TAA03119; Thu, 15 Jun 1995 19:46:28 -0700 From: Poul-Henning Kamp Message-Id: <199506160246.TAA03119@ref.tfs.com> Subject: disk handling program To: hackers@freebsd.org Date: Thu, 15 Jun 1995 19:46:28 -0700 (PDT) Cc: faq@freebsd.org, doc@freebsd.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 3497 Sender: doc-owner@freebsd.org Precedence: bulk There has been a lot of questions about disks and what to do. The situations isn't quite optimal in 2.0.5/current and hopefully somebody will get/take time to remedy this before 2.1. Presently we take a very conservative position on geometry, and it is ABSOLUTELY CRUCIAL that the "bios-geometry" is correct/sensible. For your boot-disk it MUST be correct. For other disks it merely have to make sense. There are two ways to get it right: A: Create a msdos partition, and delete it from FreeBSD. B: Boot freebsd with -v and look at the "bios-geometry" table it prints at the end, find the right one for this particular drive and use that. In the meantime: For those of you who really feel adventurous, you can cd /usr/src/release/libdisk make tst01 ./tst01 wd0 tst01 is a small driver program for the libdisk library, it's pretty much the same as the undocumented wizard mode in the sysinstall program. ALL GUARANTEES ARE OFF if you run it (well, we don't give any in the first place). It will NEVER write to the disk unless you ask it to. (If there is a curses-programmer with extra time at hand, please make a decent userinterface to this please. Contact phk@freebsd.org.) In particular if you send email with questions/complaints, it is very helpful for us if you can include the output from tst01 in the email. The output could look like this: ref# ./tst01 sd0 --==##==-- Debug_Disk(sd0) flags=0 bios_geom=675/128/32 boot1=0x0, boot2=0x0, bootmgr=0x0 --> 0x15040 0 2766300 2766299 sd0 whole 0x00 --> 0x15080 0 32 31 - unused 0x00 --> 0x150c0 32 2764768 2764799 sd0s1 freebsd 0xa5 C= --> 0x15100 32 65536 65567 sd0s1a part 0x07 --> 0x151c0 65568 65536 131103 sd0s1b part 0x01 --> 0x15200 131104 65536 196639 sd0s1e part 0x07 --> 0x15240 196640 1024000 1220639 sd0s1f part 0x07 --> 0x15280 1220640 1544160 2764799 sd0s1g part 0x07 --> 0x15140 2764800 1500 2766299 - unused 0x00 Column Explanation -------------------------------------------------------------------------- 1 The arrows show at what level this chunk of disk lives. All chunks must fit inside exactly one higherlevel chunk. 2 Pointer. This is the pointer inside the tst01 program. You pass this to the delete command: "delete 0x151c0" for instance. 3 Offset. Where on the disk the chunk starts. Can be negative for the Ontrack'ed disks. 4 Length, numbers of 512bytes sectors in chunk. 5 End, number of last sector in chunk. 6 Name. "X" means that no meaningful name can be assigned. 7 whole represents the entire disk unused space presently without a name of it's own. Some unused chunks are reserved. freebsd FreeBSD slice dos MSDOS slice part FreeBSD partition extended Extended dos partition 8 Subtype. For things which live in the MBR (freebsd,dos,extended) this is the MBR type field. For things in a FreeBSD slice, this is the disklabel type. 9 Flags C FreeBSD compatibility slice. A Active = Aligned > Extends past cyl 1023 R marked as 'root' B marked as using bad144 -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Just that: dried leaves in boiling water ? From owner-freebsd-doc Thu Jun 15 22:19:20 1995 Return-Path: doc-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA25137 for doc-outgoing; Thu, 15 Jun 1995 22:19:20 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA25110 ; Thu, 15 Jun 1995 22:19:06 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA07652; Fri, 16 Jun 1995 15:13:04 +1000 Date: Fri, 16 Jun 1995 15:13:04 +1000 From: Bruce Evans Message-Id: <199506160513.PAA07652@godzilla.zeta.org.au> To: hackers@freebsd.org, phk@ref.tfs.com Subject: Re: disk handling program Cc: doc@freebsd.org, faq@freebsd.org Sender: doc-owner@freebsd.org Precedence: bulk >For your boot-disk it MUST be correct. For other disks it merely have >to make sense. >There are two ways to get it right: >A: Create a msdos partition, and delete it from FreeBSD. >B: Boot freebsd with -v and look at the "bios-geometry" table > it prints at the end, find the right one for this particular > drive and use that. That's 2 more wrong ways. A: Fails if the fdisk used to create the msdos partition does things a little differently. Deletion of foreign partitions may cause trouble later. It may be necessary to delete certain metadata within the partitions, and fdisk (on any system) has no way of knowing where the metadata is. The problems occur if stale metadata is reactivated (and used). For DOS, stale parameter blocks may be used by `format' to format areas outside the (new) slice. For FreeBSD, stale disklabels may be used by `newfs' to newfs the wrong areas. The damage is now limited by disklabels being restricted to the slice that they are in. B: Usually fails if a disk manager is normally installed but isn't installed when you boot with -v. Right ways: A1: If a disk manager isn't normally installed, use method B. B1: If a disk manager is normally installed: Install disk manager. Install DOS (on the same disk). Boot DOS (on the same disk). Run pfdisk or some other DOS utility that reports the geometry. Use DOS fdisk to remove DOS. Use the geometry reported by pfdisk. Simpler methods might work: C: If a disk manager is normally installed: Install disk manager. Boot DOS from a floppy. Run utility to load disk manager for hard disk. Run pfdisk or some other DOS utility that reports the geometry. Use the geometry reported by pfdisk. D: If a disk manager is normally installed: Install disk manager. Use method B. This requires booting FreeBSD with -v from ANOTHER disk with BOTH the disk manager and FreeBSD already installed. Bruce From owner-freebsd-doc Fri Jun 16 14:32:27 1995 Return-Path: doc-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA20435 for doc-outgoing; Fri, 16 Jun 1995 14:32:27 -0700 Received: from netcom16.netcom.com (root@netcom16.netcom.com [192.100.81.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA20429 for ; Fri, 16 Jun 1995 14:32:24 -0700 Received: from Ðãs’³6 *tá$6¢*tP by netcom16.netcom.com (8.6.12/Netcom) id OAA11118; Fri, 16 Jun 1995 14:31:39 -0700 Date: Fri, 16 Jun 1995 14:31:39 -0700 Message-Id: <199506162131.OAA11118@netcom16.netcom.com> X-Mailer: NCSA Mosaic/2.0.0b4 (Windows x86) X-URL: http://www.freebsd.org:80/How/ From: rjiang@akbs.com (Ruiyuan Jiang) To: doc@freebsd.org Subject: Newbie Tries to install FreeBSD 2.0.5 From Diskettes Sender: doc-owner@freebsd.org Precedence: bulk Yesterday I sent a message to doc@freebsd.org. This morning I received two response messages from Mr. Mike Smith and Mr. Jordan K. Hubbard" . They are very helpful. Thanks a lot. Right now the installation can pass diskette 4 no problem but the installation (same Kern-Developer installation) stopped at diskette dict\dict.aa, info\info.aa and src\ssys.aa. All these three diskettes had the same messages "Warning: You have selected a Read-only root device and may be unable to find the appropriate device entries on it if it is from an older pre-slice version of FreeBSD". Does anybody out there know why? Thanks in advance. Ruiyuan Jiang > Make sure that the root filesystem is marked for "newfs", and that the > warning you describe below does not come up. You must have been > fooling around in the label editor and somehow set the options wrong. >> I am trying to install FreeBSD Release 2.0.5 to a machine "Compaq >> luggable" 486 DX-33 with 202MB hard disk, 20 MB RAM(no MS-DOS >> nothing). I use Kern-Developer and 3.5" diskettes (each diskettes has >> 6 files on it) options to do installation. After I specified all the >> options and started to load FreeBSD, the first message I got was >> "Warning: You have selected a Read-only root device and may be unable >> to find the appropriate device entries on it if it is from an older >> pre-slice version of FreeBSD". What I could do at this point was to >> hit enter to go to the next step. The system started to load from >> diskette "boot.flp" and rest of them. It seemed OK but when the >> system asked me to put in file bin\bin.as (started with file >> bin\bin.as to bin\bin.ax) which in my case is diskette 4. I put in >> and hit enter. After reading about 3 second, the system prompted me a >> message "Write failure on transfer! (wrote -1 bytes of 10240 bytes)". >> I could skip this diskette (I can choose to load it later) and could >> load next disketts. I tried to reformat the diskette and downloaded >> all the files again and tried to use brand new diskette, formated it >> first and downloaded the files and reinstalled FreeBSD but I stucked >> at the same place and got the same message. Does anyone out there >> know why? Thanks in advance. >> >> Ruiyuan Jiang >> System Administrator >> ADVANTAGE kbs, Inc. >> rjiang@akbs.com >> (908) 287-2236 >> FAX (908) 287-3193