home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.aux
- Path: sparky!uunet!elroy.jpl.nasa.gov!ames!nsisrv!jagubox!jim
- From: jim@jagubox.gsfc.nasa.gov (Jim Jagielski)
- Subject: Yet more about 'tc'
- Message-ID: <1228@jagubox.gsfc.nasa.gov>
- Lines: 23
- Sender: usenet@nsisrv.gsfc.nasa.gov (Usenet)
- Nntp-Posting-Host: jagubox.gsfc.nasa.gov
- Reply-To: jim@jagubox.gsfc.nasa.gov (Jim Jagielski)
- Organization: NASA/Goddard Space Flight Center
- Date: Fri, 6 Nov 1992 14:04:23 GMT
-
- Is the fact that 'tc' needs to be blocked at 8k a big problem (or pain)
- for most people? So far I've heard from only one person who says that it is,
- but the only reason is because it makes it tough (impossible) to read tapes
- from other workstations that write at 512/1024 and not because of any
- A/UX-world problems.
-
- I for one don't mind the 8k blocking at all. It makes the driver more
- efficient (and therefore quicker) but you have to recall to block at
- 8k. Of course, if 'tc' used the tape drive's actual physical block size
- as it's blocking factor, then you'd have to block at either 512 or 1024
- or 8192, depending on your tape drive so you'd still have to concern
- yourself about blocking...
-
- Of course, I may just make 'tc' aware of some other minor device bits
- and _maybe_ do stuff there but that's a bit of work and I don't think
- I have the time.
-
- What say the world?
- --
- Jim Jagielski | "It is not I who am crazy...
- jim@jagubox.gsfc.nasa.gov | it is I who am MAD!"
- NASA/GSFC, Code 734.4 |
- Greenbelt, MD 20771 | - Ren
-