Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!uunet!sun-barr!olivea!spool.mu.edu!agate!doc.ic.ac.uk!uknet!mcsun!chsun!hslrswi!aut!nbladt From: nbladt@autelca.ascom.ch (Norbert Bladt) Newsgroups: comp.unix.bsd Subject: Re: device 0/0 0/1 Message-ID: <1992Oct6.122726.15841@autelca.ascom.ch> Date: 6 Oct 92 12:27:26 GMT References: <1992Oct5.081610.5486@autelca.ascom.ch> <1992Oct6.023619.11968@rhrk.uni-kl.de> Organization: Ascom Autelca AG, Guemligen, Switzerland Lines: 31 andrick@sun.rhrk.uni-kl.de (Ulf Andrick [Biologie]) writes: >nbladt@autelca.ascom.ch (Norbert Bladt) writes: >: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) writes: >: >: >: >I'm running 386bsd on a ah1542b with as0a as root, as0b swap, as0h /usr. >: >Yesterday I installed Julian Elischers (thank you, Julian), scsibeta2.1 >: >release because my DAT tape (DEC TLZ04) was never recognized by the as >: >driver. With the above SCSI driver it is recognized. >: >: [ text about error message: "sd0: device not configured" deleted - NB. ] >I have no experience with that, but I wonder whether one >shouldn't have a look at /etc/fstab in such a case. That file >should be decisive for what devices are used as swap space, >shouldn't it? Yes but savecore doesn't look at it ! Savecore (or whatever the name of the program is) does a nlist for the current unix and looks for the entry "dumpdev". There must be "sd0b" (or device 4,1) in it, which is usually the swap area, unless configured differently, i.e. not using "install" for installing 386BSD. I don't know how it proceeds from then, but I looked in the code and found this call to "nlist". Norbert. -- Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland Phone: +41 31 999 65 52 FAX: +41 31 999 65 44 Mail: nbladt@autelca.ascom.ch UUCP: ..!uunet!mcsun!chsun!hslrswi!aut!nbladt