From: Ben Bacarisse on 22 Sep 2009 18:21 "Bill Cunningham" <nospam(a)nspam.invalid> writes: <snip> > Can someone help me then with just mt and how it was used in old unixes > that ran of DECs? mt did not exist on old unixes (at least not the very old ones). Tapes were written using the tp command (which was considered a bad idea) or directly by using dd to raw tape device (/dev/rmt0 etc). Rather than describe mt (the manual does a better job than I could) I think I'd rather what you are try to do? -- Ben.
From: Gordon Burditt on 22 Sep 2009 18:49 > I have mt on my linux system and I think it's from back when tapes were >used. How was mt used? mt has two primary uses: (a) to position the tape, and (b) to get or set options on the tape drive that it may not be able to autodetect, like density and compression options. You use mt on an actual tape drive, not on a file that contains an image of what was on the tape. >Was it to create executables or slpit up a directory >tape? No. What on earth is a "directory tape"? >I would like to create a file that knows where what execuatables and >binaries are where? A tape has, roughly, zero or more *unnamed* files ended by tape marks. You may, for example, position the tape to read the third file by using mt to rewind the tape, then "forward space file" over two files. A file on a tape has no name. However, it may contain something that contains files within it, and those may have names. Common things to put on tape as files: - CPIO archives - dump/restor filesystem dumps - TAR archives - Filesystem images If you want to see what's on the tape, you might: - Position the tape to the correct file you're interested in, using mt. - Try using the file(1) command to figure out what is in that file on the tape (cpio, tar, filesystem, dump/restor, etc). - Position the tape (again!) to the correct file you're interested in, using mt. - Use the appropriate command to list the files on the tape. tar: tar -xvf /dev/mt0 cpio: cpio -itv < /dev/mt0 dump/restor: restor -tvf /dev/mt0 where /dev/mt0 is the device name of your tape drive (adjust to suit your system). filesystem: You probably can't mount a filesystem image on tape directly, unless it's on DECtape (a directly-addressable tape). You might dd an image to a disk partion, then mount it and look at it or use ls -lR. Or some systems let you mount a file containing an image of a filesystem as a filesystem (Linux will).
From: Bill Cunningham on 22 Sep 2009 20:02 "Gordon Burditt" <gordonb.mee7b(a)burditt.org> wrote in message news:8q2dnUpwX6vgySTXnZ2dnUVZ_sqdnZ2d(a)posted.internetamerica... >> I have mt on my linux system and I think it's from back when tapes >> were >>used. How was mt used? > > mt has two primary uses: (a) to position the tape, and (b) to get or > set options on the tape drive that it may not be able to autodetect, > like density and compression options. > > You use mt on an actual tape drive, not on a file that contains an > image of what was on the tape. > >>Was it to create executables or slpit up a directory >>tape? > > No. What on earth is a "directory tape"? [snip] The /usr directory. Which you would then use mknod to create devices in order to use restor(e). There are alot of good old tapes around for collectors. They can be use with emulators like simh. Bill
From: Ben Finney on 22 Sep 2009 21:38 "Bill Cunningham" <nospam(a)nspam.invalid> writes: > I'm going to try to explain here. With this pdf A PDF, attached, at around 1MiB, to a message in Usenet. Welcome to my kill file, Bill. *plonk* -- \ “… a Microsoft Certified System Engineer is to information | `\ technology as a McDonalds Certified Food Specialist is to the | _o__) culinary arts.” —Michael Bacarella | Ben Finney
From: Barry Margolin on 22 Sep 2009 23:52 In article <0.9cdd9f92239f91041fb3.20090922232159BST.87pr9isjqw.fsf(a)bsb.me.uk>, Ben Bacarisse <ben.usenet(a)bsb.me.uk> wrote: > "Bill Cunningham" <nospam(a)nspam.invalid> writes: > <snip> > > Can someone help me then with just mt and how it was used in old unixes > > that ran of DECs? > > mt did not exist on old unixes (at least not the very old ones). I'm pretty sure I used it on SunOS in the late 80's. Not prehistoric, but still pretty old. -- Barry Margolin, barmar(a)alum.mit.edu Arlington, MA *** PLEASE post questions in newsgroups, not directly to me *** *** PLEASE don't copy me on replies, I'll read them in the group ***
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 Prev: broken pipe when reading and writing a pipe Next: Using recvfrom with a raw socket on linux |