*BSD News Article 66160


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!gatech!news.mathworks.com!fu-berlin.de!cs.tu-berlin.de!uni-erlangen.de!news.tu-chemnitz.de!News.HTWM.De!news.HRZ.HAB-Weimar.DE!news.uni-jena.de!news.uni-leipzig.de!news1.urz.tu-dresden.de!irz401!uriah.heep!news
From: j@uriah.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Mounting msdos fs and cdrom fs
Date: 14 Apr 1996 18:49:43 GMT
Organization: Private FreeBSD site, Dresden
Lines: 41
Message-ID: <4krhc7$7h3@uriah.heep.sax.de>
References: <4kr1kt$eln@fu-berlin.de>
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
NNTP-Posting-Host: localhost.heep.sax.de
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: knews 0.9.6

axl@zedat.fu-berlin.de (Axel Thimm) writes:

>environment. I have found out how to mount a primary dos partition, but
>I cannot firgure out if and how to do so with extended dos partitions.

The extended DOS partitions are called `slices' in FreeBSD (to
differentiate them from what Unix calls `partition', that is, it comes
with partitions of its own traditionally).  The convention is that the
first four slices are pre-allocated for the four fdisk table entries
(regardless whether they are valid or not), while the following are
being used for extended partitions.

The first slices are /dev/[r]wd0s1 through /dev/[r]wd0s4, you get the
picture.  Since it's impossible to ship the system with pre-configured
device nodes for ``all'' slices and partitions, you gotta create the
device nodes yourself (by now):

	cd /dev
	./MAKEDEV wd0s5

(for example).  You should then be able to mount your DOS partition
by

	mount -t msdos /dev/wd0s5 /dos2

Likewise for slices 6 and 7, should they exist.

>Another point is mounting IDE CD-ROMs.

Though unsupported, the 2.1R CD-ROM contains preliminary code for
ATAPI CD-ROMs.  Check the kernel.ATAPI, or the appropriate kernel
config file under /sys/i386/conf/.  It is, however, known to not work
with all sort of drives.  (The situation has been improved much
meanwhile.)

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)