You are not logged in.
Hi all,
Just built my new home server to combine my fileserver and devel server in to one box. The new server has a tape drive in it for backup purposes.
Having not used Arch on a machine with a tape drive before, I've never noticed that /dev/tape/ exists as a directory. The mt command defaults to /dev/tape to find the device to interrogate. However, because the /dev/tape directory exists, I can't symlink /dev/nst0 to /dev/tape like I would normally do. This means I have to either pass the -f option to mt everytime I call it, or set the $TAPE variable.
/dev/tape is similar to /dev/disk for connecting to devices by-id or by-path.
Symlinking /dev/nst0 to /dev/tape is my preferred option, as it doesn't rely on the environment to be setup when I want to use mt.
Where did /dev/tape come from? Has it been done upstream by the kernel folk?
Any suggestions for how to remove / disable it? Does anyone else think this is a bug? I'd prefer not to compile a custom kernel if possible (I like being able to just pacman -Syu )
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
It's coming from the udev devs, see /lib/udev/rules.d/60-persistent-storage-tape.rules.
I wouldn't consider it a bug, but an unwanted default
You could move/delete the rules file but I'd prefer the $TAPE / -f approach.
Last edited by byte (2008-09-20 07:13:42)
1000
Offline
udev... Cool. thanks for that
Is it a default that should / could be changed?
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline