search for: loop1p1

...y for manipulating disk images. Some example commands are below. Please read the documentation for kpartx before you modify the disk image. * kpartx -l CentOS-7-1503-aarch64.img # List partitions in the image * kpartx -a -v CentOS-7-1503-aarch64.img # Add partition mappings * mount /dev/mapper/loop1p1 /mnt # mount the first partition to /mnt * umount /mnt # unmount /mnt, obviously. * kpartx -d -v CentOS-7-1503-aarch64.img # remove partition mappings -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77 ------------------------------ _________...

...iste, 8 cylindres, total 129024 secteurs Unit?s = secteur de 1 * 512 = 512 octets Taille de secteur (logique / physique) : 512 octets / 512 octets taille d'E/S (minimale / optimale) : 512 octets / 512 octets Identifiant de disque : 0x44533712 P?riph?rique Amorce D?but Fin Blocs Id Syst?me /dev/loop1p1 * 0 129023 64512 0 Vide /dev/loop1p2 136 127111 63488 ef EFI (FAT-12/16/32) bash-4.2# ?--- I no nothing about the ISO9660 spec, but I assume that the firmware should see the EFI partition. Is that right? I also assume that the firmware can "see" the content of the EFI partition as if I m...

...y for manipulating disk images. Some example commands are below. Please read the documentation for kpartx before you modify the disk image. * kpartx -l CentOS-7-1503-aarch64.img # List partitions in the image * kpartx -a -v CentOS-7-1503-aarch64.img # Add partition mappings * mount /dev/mapper/loop1p1 /mnt # mount the first partition to /mnt * umount /mnt # unmount /mnt, obviously. * kpartx -d -v CentOS-7-1503-aarch64.img # remove partition mappings -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

...y for manipulating disk images. Some example commands are below. Please read the documentation for kpartx before you modify the disk image. * kpartx -l CentOS-7-1503-aarch64.img # List partitions in the image * kpartx -a -v CentOS-7-1503-aarch64.img # Add partition mappings * mount /dev/mapper/loop1p1 /mnt # mount the first partition to /mnt * umount /mnt # unmount /mnt, obviously. * kpartx -d -v CentOS-7-1503-aarch64.img # remove partition mappings -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

Hi, Ady wrote: > http://www.syslinux.org/archives/2015-October/024526.html I still have it in my mailbox: ADY4UEFI.IMG in ADY4UEFI.ZIP. The test results are the same as with Didier's partition image. Wrapped in an ISO and presented as -cdrom it reboots in cycles. Presented as -hda it boots as naked disk image and as part of a GPT enhanced ISO 9660. > the wiki page needs

...virtual machine in this way: # losetup /dev/loop1 /dev/virtualmachines/windows7-x64 virtualmachines is the name of my volume group. windows7-x64 is the logical volume. # kpartx -av /dev/loop1 Then I would see the partitions of the virtual machine within a logical volume, like so: /dev/mapper/loop1p1 /dev/mapper/loop1p2 /dev/mapper/loop1p3 Now that I can access the partitions of the virtual machine within a logical volume, I can use partimage or fsarchiver to backup the partitions (provided the filesystem is supported by the archiver). But the problem is that I can only backup/clone the files...