-
Senior Member
registered user
There is always two sides to a coin. Either you call it knoppix created not enough loop devices or you call it knoppix created one too many loop device/directory.
Furthermore, if you could just extract a copy of /bin/mount from a knoppix 6.2 and test use it on your system ( you could copy it to say /tmp, and then issue command as /tmp/mount), then you will appreciate what I mean:- That extra loop device/directory is not disturbing the system at all with /bin/mount from knoppix 6.2. If you use a newer /bin/mount, yes, it matters.
-
Senior Member
registered user
Originally Posted by
kl522
There is always two sides to a coin. Either you call it knoppix created not enough loop devices or you call it knoppix created one too many loop device/directory.
Furthermore, if you could just extract a copy of /bin/mount from a knoppix 6.2 and test use it on your system ( you could copy it to say /tmp, and then issue command as /tmp/mount), then you will appreciate what I mean:- That extra loop device/directory is not disturbing the system at all with /bin/mount from knoppix 6.2. If you use a newer /bin/mount, yes, it matters.
I still don't understand this. Knoppix 6.2.1 created /dev/loop/0 - that's enough for Knoppix to mount on, but not for other purposes. So it's not one too many directories, it conforms to what newer versions try to use, just as you write. And we can, as I did, create more ourselves. I thought it seemed better to follow the development, but basically, I just wanted it to work. (And I'm not interested in more details than I absolutely need to know..)
Using your rm -rf /dev/loop trick, /dev/loop0../dev/loop7 are created afterwards - the old way. Seems to work just nice, BUT if some programs expect the newer organization, at least in theory it could be safer to use that? Instinctively, I'm not too happy with recursively deleting devices in init scripts.
-
Senior Member
registered user
Trying to find out more about this, I really get confused, as the /dev/loop/X way of naming seems to be associated with the deprecated devfs nomenclature. So it should be /dev/loopX? I would very much like to stay out of such silly naming discussions, but that Knoppix bug just placed me there
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
ASUS H110M-R Motherboard Intel 6th/7th Gen LGA1151 DDR4 Micro-ATX i/o shield
$42.00
ASUS Prime B250M-C LGA1151 DDR4 Desktop Motherboard USB 3.0 w/ I/O Shield
$39.99
Asrock Z390 Phantom Gaming 4S/AC Wifi 8th/9th Gen Intel 1151 Motherboard Bulk
$41.16
MSI PRO B650-P WiFi AMD AM5 DDR5 WiFi 6E ProSeries Motherboard
$80.71
ASUS P8B75-M/CSM Desktop Motherboard Intel Socket LGA1155 DDR3 w/ IO
$29.99
ASUS Prime Z390-A LGA 1151 Intel Z390 SATA USB 3.1 ATX Motherboard NO I/O
$99.00
MSI B450M PRO-VDH MAX AM4 AMD B450 USB3.2 Micro-ATX Motherboard
$67.99
MSI A320M-A Pro mATX AM4 Motherboard (Ryzen 1000-5000 Ready)
$49.99
MSI PRO B650-P WiFi AMD AM5 DDR5 WiFi 6E ProSeries Motherboard
$96.01
ASUS PRIME Z690-P WIFI D4 ATX Motherboard Intel LGA1700 DDR4 HDMI
$99.99