home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!swrinde!mips!mips!munnari.oz.au!yoyo.aarnet.edu.au!sirius.ucs.adelaide.edu.au!iagu.itd.adelaide.edu.au!newton
- From: newton@iagu.itd.adelaide.edu.au (Mark Newton)
- Newsgroups: comp.os.minix
- Subject: Re: dosread
- Message-ID: <8283@sirius.ucs.adelaide.edu.au>
- Date: 22 Aug 92 08:58:41 GMT
- References: <1992Aug18.183026.8428@udel.edu> <8255@sirius.ucs.adelaide.edu.au> <1992Aug20.083043.5104@email.tuwien.ac.at>
- Sender: news@ucs.adelaide.edu.au
- Organization: University of Adelaide, South Australia
- Lines: 29
- Nntp-Posting-Host: iagu.itd.adelaide.edu.au
-
- In article <1992Aug20.083043.5104@email.tuwien.ac.at> hp@vmars.tuwien.ac.at (Peter Holzer) writes:
- >newton@iagu.itd.adelaide.edu.au (Mark Newton) writes:
- >
- >>dosread expects a block special device that it is supposed to read from.
- >>So, to read something from drive A:, use a command line like this:
- >
- >> dosread -a /dev/fd0 foobar > /tmp/foobar
- >
- >>/dev/fd0 corresponds to the A: drive.
- >
- >What version of dosread are you using? All versions I know (1.3 ...
- >1.6.16) do not take the pathname of a block device as their first
- >arguent, but a single letter from which they build the pathname by
-
- Ah, yes... I was thinking of tosread/toswrite, which does exactly the
- same thing (to what is oestensibly exactly the same disk format, too).
- tosread and toswrite are supplied with m68k MINIXes.
-
- >(All of this is in the manual, BTW. Is it really that hard to
- >understand?)
-
- Agreed :-)
-
- - mark
- --
- ------------------------------------------------------------------
- 'Do not expose your LaserWriter to naked flame...'
- newton@iagu.itd.adelaide.edu.au - Apple LaserWriter Manual
- ------------------------------------------------------------------
-