Letters to the Editor
In “An introduction to block device drivers” (Issue 9, January) you write:
“... you will not be able to mount the tape, even though it contains the same information as the disk”.
I hope you know that the half-inch tape drives have all the features allowing half-inch tapes, written in a standard way, to be mounted read-only and (if the tape quality permits) to use the tape as a full-featured random-access read/write media after formatting.
I believe the sentence I've quoted has been written to simplify things and not because of lack of knowledge.
Also, I have another question close to the topic. Why are there no raw disk devices in Linux, unlike, for example, BSD and SVR3 (I don't know for sure about SVR4)? Is it because the buffering is implemented in a more correct way so that one is able to do fsck on a block device and then mount it immediately or because of something else?Sincerely,Leo Broukhis email@example.com
I was perhaps not explicit enough. My statement was not intended to say anything about the hardware capabilities. The Linux kernel does not have block device drivers for any form of tapes and, therefore, is unable to mount them as filesystems, even if the hardware supports it.
The reason that there are no raw devices is that the VFS is implemented such that an open of a block device, while it does buffer, is immediate. See block_read() and block_write() and notice that they aren't used for reading and writing blocks on mounted devices, but only opened devices.
I found the remove article interesting (in January 1995). The remove alias needs to be more general. It only handles one file: you need to do something like:
alias rm='mv $* ~/.rm'
Actually, it's better to use the -b (backup) option in GNU fileutils and do:
alias rm='mv -b $* ~/.mv'
and default to numbered backups. Then, if you remove foo.c in two different directories, you'll get entries like:
so you can recover each one, with some work.
I also find the /bin/rm -r ~/.rm in your .profile incredibly bad.
You often find you want to check something after you log out, so if you log in, you automatically erase your backup right away. It is much better to use cron.
Also, I haven't used it, but I want to try the MIT Athena delete/undelete system (posted to comp.source.misc, v17). It may be worth a try. You should also review this.Marty Leisner firstname.lastname@example.org
- New Products
- Readers' Choice Awards 2014
- Android Candy: Google Keep
- How Can We Get Business to Care about Freedom, Openness and Interoperability?
- Handling the workloads of the Future
- Days Between Dates?
- December 2014 Issue of Linux Journal: Readers' Choice
- diff -u: What's New in Kernel Development
- Computing without a Computer
Editorial Advisory Panel
Thank you to our 2014 Editorial Advisors!
- Jeff Parent
- Brad Baillio
- Nick Baronian
- Steve Case
- Chadalavada Kalyana
- Caleb Cullen
- Keir Davis
- Michael Eager
- Nick Faltys
- Dennis Frey
- Philip Jacob
- Jay Kruizenga
- Steve Marquez
- Dave McAllister
- Craig Oda
- Mike Roberts
- Chris Stark
- Patrick Swartz
- David Lynch
- Alicia Gibb
- Thomas Quinlan
- Carson McDonald
- Kristen Shoemaker
- Charnell Luchich
- James Walker
- Victor Gregorio
- Hari Boukis
- Brian Conner
- David Lane