A file that refers to a device. A block special file is normally distinguished from a character special file by providing access to the device in a manner such that the hardware characteristics of the device are not visible.
I have a card reader attached on
I previously used to create image files using
dd, set up a filesystem on them using
mount them to access them as mounted partitions. Later on, I have seen on the internet that many examples use
losetup beforehand to make a loop device entry under
/dev, and then mount it. I could not tell why one would practically need an image file to behave as a loop device and have its own
/dev entry while the same behaviour can be obtained without all the hassle.
badblocks to test my 32GB class-10 microSD card that I use to boot my RPi. I already have a functioning file system on it, so I don’t want to scan it with the
-w option (destructive read-write test).
I’m setting up
udev to handle my external USB hard drive when it gets plugged in and removed (no mounting yet). So far, I’ve made two new rules in
/etc/udev/rules.d/10-local.rules to log adding/removing the disk to a file:
Is it possible to export a block device such as a DVD or CDROM and make it so that it’s mountable on another computer as a block device?
Is there a way to take a disk img file that is broken up into parts and mount it as a single loop device?
I’m looking for a portable way to obtain parent block device name (e.g.
/dev/sda) given the partition device name (e.g.
/dev/sda1). I know I could just drop the last character, but that wouldn’t work in some cases: