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 firstname.lastname@example.org
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 email@example.com
Fast/Flexible Linux OS Recovery
On Demand Now
In this live one-hour webinar, learn how to enhance your existing backup strategies for complete disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible full-system recovery solution for UNIX and Linux systems.
Join Linux Journal's Shawn Powers and David Huffman, President/CEO, Storix, Inc.
Free to Linux Journal readers.Register Now!
- Server Hardening
- May 2016 Issue of Linux Journal
- EnterpriseDB's EDB Postgres Advanced Server and EDB Postgres Enterprise Manager
- The Humble Hacker?
- The US Government and Open-Source Software
- The Death of RoboVM
- BitTorrent Inc.'s Sync
- New Container Image Standard Promises More Portable Apps
- Open-Source Project Secretly Funded by CIA
- ACI Worldwide's UP Retail Payments
In modern computer systems, privacy and security are mandatory. However, connections from the outside over public networks automatically imply risks. One easily available solution to avoid eavesdroppers’ attempts is SSH. But, its wide adoption during the past 21 years has made it a target for attackers, so hardening your system properly is a must.
Additionally, in highly regulated markets, you must comply with specific operational requirements, proving that you conform to standards and even that you have included new mandatory authentication methods, such as two-factor authentication. In this ebook, I discuss SSH and how to configure and manage it to guarantee that your network is safe, your data is secure and that you comply with relevant regulations.Get the Guide