From owner-freebsd-stable Sun Feb 8 19:44:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA22485 for stable-outgoing; Sun, 8 Feb 1998 19:44:54 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from stcgate.statcan.ca (stcgate.statcan.ca [142.206.192.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA22479 for ; Sun, 8 Feb 1998 19:44:46 -0800 (PST) (envelope-from jeays@statcan.ca) Received: (from root@localhost) by stcgate.statcan.ca (8.6.11/8.6.9) id WAA23881; Sun, 8 Feb 1998 22:48:16 -0500 Received: from stcinet.statcan.ca(142.206.128.146) by stcgate via smap (V1.3) id sma023875; Mon Feb 9 03:47:21 1998 Received: from statcan.ca by statcan.ca (SMI-8.6/SMI-SVR4) id WAA01586; Sun, 8 Feb 1998 22:45:57 -0500 Date: Sun, 8 Feb 1998 22:42:40 -0500 (EST) From: Mike Jeays X-Sender: jeays@austral To: Mike Smith cc: freebsd-stable@FreeBSD.ORG Subject: Re: Zip drive problem again In-Reply-To: <199802081936.LAA00473@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Sun, 8 Feb 1998, Mike Smith wrote: > > I bought an Iomega ZIP drive (the internal ATAPI version), and am hoping > > to get it to work with FreeBSD as well as W*nd*ws 95. I downloaded all > > the source for -stable, and did my first-ever make world, and rebuilt the > > kernel with references to wfd0 as well as wcd0. (The CD-ROM is master on > > the second controller, the Zip drive is slave.) > > Ok, sounds reasonable so far. > > > On rebooting, it displayed the message that it had identified the "buggy > > drive", > > Sounds like it was found OK. > > > but came up with a damaged file system on my FreeBSD IDE disk > > (slave on the first controller). Fsck repaired "/", but I couldn't get at > > /mnt or /var. > > "couldn't get at" doesn't sound like an error message that I am > familiar with. Without the actual error texts, it's more or less > impossible to determine the actual nature of the problem. > No, it isn't a real error message. The actual message disappeared without any opportunity to capture it. The OS said that the / filesystem was damaged, and offered to repair it - I replied yes. It then bypassed the other file systems, and gave me a Bourne shell prompt. I expect an expert would have some idea what to try. I tried the fixit option from the second CD, but didn't really know what to do. What is a holographic shell anyway? > > I unplugged the Zip drive so that the CD would work, and > > By this I take it that the CD drive *didn't* work while the Zip was > connected? This is correct. If, in 2.2.1, I try to mount the CD when the Zip is plugged in, the mount command doesn't return. Hitting control-C cancels it, but a second attempt seems to hang the OS entirely. > > > Any similar experiences or advice, please? Have others used a CD-ROM and > > Zip drive on the same controller? > > Yes, although I only ran the Zip as master (time was limited, and no > other testers reported any problems). > > > My first try at the make world failed, because I did not have 'mail' and > > 'network' as groups defined in /etc/group. Should the make world be > > enhanced to make sure all required groups are present? > > Please feel free to submit the changes. Note that if you have the > 2.2.5 CDROM lying around, it's much easier to upgrade to -stable if > you're starting from the most recent mainline release (and we don't > actually support upgrading from anything older). > I think I will be patient and wait for 2.2.6-RELEASE. Will there be a CD-ROM version, and if so, will it be a 4 CD set? Thanks for the help! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe stable" in the body of the message