From: rich@example.invalid
David Chmelik wrote:
> On Mon, 14 Feb 2022 06:36:02 -0000 (UTC), Henrik Carlqvist wrote:
>
>> On Mon, 14 Feb 2022 03:30:34 +0000, David Chmelik wrote:
>>
>>> On Slackware64 15+current, I can no longer mount ISOs on loopback.
>>>
>>> root@cosmos:~# mount
>>> ware/slackware/slackware64-15.0-iso/slackware64-15.0- install-dvd.iso
>>> /scd -o loop mount: /scd: can't read superblock on /dev/loop0.
>>
>> What does
>>
>> file
>> ware/slackware/slackware64-15.0-iso/slackware64-15.0-install-dvd.iso
>>
>> say?
>
> root@cosmos:~# file ware/slackware/slackware64-15.0-iso/slackware64-15.0-
> install-dvd.iso
> ware/slackware/slackware64-15.0-iso/slackware64-15.0-install-dvd.iso: ISO
> 9660 CD-ROM filesystem data (DOS/MBR boot sector) 'SlackDVD' (bootable)
>
>> I don't think that it does matter, but if the iso file seems OK I would
>> try to put the options before the device and mount point on the command
>> line:
>>
>> mount -o loop ware/slackware/slackware64-15.0-iso/slackware64-15.0-
>> install-dvd.iso /scd
>
> It doesn't matter for that command; I originally learned to put '-o loop'
> afterwards but you can put it before also.
> The same thing happens with all ISOs.
Can you loop mount manually, then mount the loop device?
I.e.:
# losetup --find --show ware/slackware/slackware64-15.0-iso/sl
ckware64-15.0-install-dvd.iso
/dev/loop0
# mount /dev/loop0 /scd
The /dev/loop0 will change depending upon what else is already mounted,
you need to use the value returned by losetup for the mount.
When done, you have to unmount, then remove the loop device:
# umount /scd
# losetup -d /dev/loop0
See the man page for losetup for details of other options.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
