> 1) While losetup 'cooks' you a block device from the file, it does not
> expose underlying partitions. What you need is:
>
> sudo kpartx -a /home/pgmaudio/2016-11-25-raspbian-jessie-lite.img
> Look for devices created in /dev/mapper, don't forget to run afterward:
>
> sudo kpartx -d
"Martin McCormick" writes:
> sudo losetup /dev/loop0 /home/pgmaudio/2016-11-25-raspbian-jessie-lite.img
[...]
> sudo mount /dev/loop0 p2 /mnt
>
> The report is that it doesn't exist and ls /dev/loop0* only shows
> the original loop0 loopback device. I looked through all of /dev
> such as
Hi.
On Sun, 18 Dec 2016 08:41:01 -0600
"Martin McCormick" wrote:
> The following command works:
>
> sudo losetup /dev/loop0 /home/pgmaudio/2016-11-25-raspbian-jessie-lite.img
>
> When one does
>
> fdisk -l /dev/loop0 the result is sensable:
>
> Device
The following command works:
sudo losetup /dev/loop0 /home/pgmaudio/2016-11-25-raspbian-jessie-lite.img
When one does
fdisk -l /dev/loop0 the result is sensable:
Device Boot Start End Blocks Id System
/dev/loop0p18192 137215 64512c W95
4 matches
Mail list logo