home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.minix
- Path: sparky!uunet!news.univie.ac.at!email!hp
- From: hp@vmars.tuwien.ac.at (Peter Holzer)
- Subject: Re: dosread
- Message-ID: <1992Aug20.083043.5104@email.tuwien.ac.at>
- Sender: news@email.tuwien.ac.at
- Nntp-Posting-Host: quasi.vmars.tuwien.ac.at
- Organization: Technical University Vienna, Dept. for Realtime Systems, AUSTRIA
- References: <1992Aug18.183026.8428@udel.edu> <8255@sirius.ucs.adelaide.edu.au>
- Date: Thu, 20 Aug 1992 08:30:43 GMT
- Lines: 32
-
- newton@iagu.itd.adelaide.edu.au (Mark Newton) writes:
-
- >In article <1992Aug18.183026.8428@udel.edu> hilander@silver.lcs.mit.edu (Most things are better eaten than forgotten) writes:
- >>i do a dosread -a foobar > /tmp/foobar
- >>with no luck
- >>i have tried to get a file off of the a drive.. no luck
-
- >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
- argument, but a single letter from which they build the pathname by
- prepending /dev/dos to it. So to read something from the A: drive you need a special file
- /dev/dosA (with the same major/minor numbers as /dev/fd0 or a link to
- /dev/fd0). Then you call
-
- dosread -a a /dev/fd0 foobar > /tmp/foobar
-
- (All of this is in the manual, BTW. Is it really that hard to
- understand?)
-
- --
- | _ | Peter J. Holzer | Think of it |
- | |_|_) | Technical University Vienna | as evolution |
- | | | | Dept. for Real-Time Systems | in action! |
- | __/ | hp@vmars.tuwien.ac.at | Tony Rand |
-