Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!fu-berlin.de!zib-berlin.de!news.tu-chemnitz.de!irz401!uriah.heep!bonnie.heep!not-for-mail
From: j@bonnie.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: ZIP drive in FreeBSD
Date: 28 Aug 1995 16:49:22 +0200
Organization: Private U**x site, Dresden.
Lines: 26
Message-ID: <41sl1i$s45@bonnie.tcd-dresden.de>
References: <41pc3c$15j@hathor.mch.sni.de> <41rdok$i1b@gate.sinica.edu.tw> <41rjiq$1vr@hathor.mch.sni.de>
Reply-To: joerg_wunsch@uriah.heep.sax.de
NNTP-Posting-Host: 192.109.108.139
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Hans Wander <awan@hathor.mch.sni.de> wrote:
>I know this feature: the 'holographic' shell; it's nice and helpfull but:
>- it's chrooted to /mnt (no ps possible)
^^^^^^^^^^^^^^
This is since there's no /kernel, not even in the root file system.
Remember, the kernel has been a zipped one. A shell not chrooted
would not help you. Perhaps mounting a procfs would help you...
Otherwise, you'll have to wait until at least a /kernel exist in the
chroot'ed environment.
>MAKEDEV /dev/sd4 (the SCSI Id of the Zip drive is 5; only 5 or 6 are
>possible)
The SCSI ID is highly irrelevant. If you've got only one other SCSI
disk, the ZIP drive will get `sd1' assigned. You can verify this in
the boot messages. (Remember to hit ScrLck, followed by PgUp, if the
boot messages have been passing by too quickly.)
I think the device nodes for sd0 and sd1 are in the installer file
system.
--
cheers, J"org private: joerg_wunsch@uriah.heep.sax.de
http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)