From owner-freebsd-hackers Mon Jun 5 13:40:25 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA03030 for hackers-outgoing; Mon, 5 Jun 1995 13:40:25 -0700 Received: from wcarchive.cdrom.com (wcarchive.cdrom.com [192.216.191.11]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA03005 for ; Mon, 5 Jun 1995 13:40:18 -0700 Received: from aristotle.algonet.se (aristotle.algonet.se [193.12.207.1]) by wcarchive.cdrom.com (8.6.11/8.6.9) with ESMTP id NAA28129 for ; Mon, 5 Jun 1995 13:40:57 -0700 Received: from sophocles. (mal@sophocles.algonet.se [193.12.207.10]) by aristotle.algonet.se (8.6.9/hdw.1.0) with SMTP id WAA08575 for ; Mon, 5 Jun 1995 22:37:55 +0200 Received: by sophocles. (5.x/SMI-SVR4) id AA06294; Mon, 5 Jun 1995 22:39:29 +0200 Date: Mon, 5 Jun 1995 22:39:29 +0200 From: mal@algonet.se (Mats Lofkvist) Message-Id: <9506052039.AA06294@sophocles.> To: freebsd-hackers@wcarchive.cdrom.com Subject: dos/floppy installation problems (2.0.5A, boot 950605 ~04:00) Sender: hackers-owner@FreeBSD.org Precedence: bulk I finally got to upgrade my system to 2.0.5A today (have used a snap from february so far). Here are the problems I stumbled into. - When choosing installation from a DOS partition, there seems to be no way to tell where the files are. Worse, the fact that they are expected to be under c:\freebsd\bin etc is not very clear neither from the documentation, in the installation menus or from the error messages. (Where the root disk is looked for I don't even know now after a successful installation since I could put in a floppy when it was not found on the disk.) - When I tried to install from floppies, I got a "you can remove the disk" almost immediately for each disk. Where I wrong to assume floppy install wants dos files on dos formatted disks?? (The "mount /dev/fd0?? /mnt" in the debug window looked like a try to mount a ufs disk to me.) - In one of my installation tries, I jumped in and configured the lp0 interface _before_ doing the installation. This might have been wrong since it didn't succeed, but it would be nice if there was some way to "unconfigure" an interface. I had to restart the installation to get past this error. (Maybe there _is_ a way that I missed?) - Finally when the system rebooted, there were no entries in /dev for sd0s4e, where fstab wanted my /usr. I changed it to sd0e in the fstab. (I did get an error message with something like "tar returned 1" or similar at the very very end of the bindist installation, could that be the source of this problem? I ignored that since I'm going to rebuild everything anyway.) [- I once choose n for newfs (since I already had been trough that step a number of times :-). Later on I got a message saying something like "you choose a read only root partition". Bug? I'm not very sure about the circumstances that resulted in this one, could be something else but I got the impression it was because of the newfs n choice.] System: 486DX2/66 w. 16 MB, bt445s scsi, fujitsu 1 GB disk, some old compaq graphics card, soundblaster 16 etc. The disk was partitioned into 100 MB dos, the rest bsd (~30 MB /, 64 swap, 800 /usr) when I started the installation. _ Mats Lofkvist mal@algonet.se