similar to: PATCH: rewrite of lomount

Am 29.09.2014 um 21:51 schrieb Don Cupp: > Renato, > > I don't think it would take that long to make a little script that even an XP user could use to generate GPT formatted thumb-drives. Win32DiskImage rulez. :-D Bonus: No more geometry problems on old BIOSes. Just create a nice GPT formatted image with a cool protective MBR. This can even expose the first partition via

>From: Tristan Gingold [mailto:Tristan.Gingold@bull.net] >Sent: 2006年4月21日 15:40 > >Le Vendredi 21 Avril 2006 09:28, Tian, Kevin a écrit : >> From: Tristan Gingold [mailto:Tristan.Gingold@bull.net] >> >> >Sent: 2006年4月21日 15:26 >> > >> >> >See how we solve this on x86 near the top of do_boot_cpu() in >> >> >arch/x86/smpboot.c.

The RAW nature of Disk Imager fails to leverage the unique intentions of UUID to surmount the problems of multiple bootable drives in the same system for purposes of knowing which one you actually booted from and should continue to use. On Monday, September 29, 2014 1:03 PM, Mattias Schlenker <ms at mattiasschlenker.de> wrote: Am 29.09.2014 um 21:51 schrieb Don Cupp: > Renato, >

lomount has been removed from xen-utils, but the same issue is still true for the rest of the packages binaries. Richard richih at adamantium:~$ apt-file search lomount richih at adamantium:~$

Allow reading and setting the GPT partition attribute flags. --- daemon/parted.ml | 23 +++++++++++++++++++++++ daemon/parted.mli | 2 ++ generator/actions_core.ml | 37 +++++++++++++++++++++++++++++++++++++ generator/proc_nr.ml | 2 ++ lib/MAX_PROC_NR | 2 +- 5 files changed, 65 insertions(+), 1 deletion(-) diff --git a/daemon/parted.ml b/daemon/parted.ml

Allow reading and setting the GPT partition attribute flags. --- daemon/parted.ml | 23 +++++++++++++++++++++++ daemon/parted.mli | 3 +++ generator/actions_core.ml | 37 +++++++++++++++++++++++++++++++++++++ generator/proc_nr.ml | 2 ++ lib/MAX_PROC_NR | 2 +- 5 files changed, 66 insertions(+), 1 deletion(-) diff --git a/daemon/parted.ml b/daemon/parted.ml

Allow reading and setting the GPT partition attribute flags. --- daemon/parted.ml | 18 +++++++++++++++++- daemon/parted.mli | 3 +++ generator/actions_core.ml | 40 ++++++++++++++++++++++++++++++++++++++++ generator/proc_nr.ml | 2 ++ lib/MAX_PROC_NR | 2 +- 5 files changed, 63 insertions(+), 2 deletions(-) diff --git a/daemon/parted.ml b/daemon/parted.ml

Hi, David Christensen wrote: > I use this USB flash drive for bootable installer images; I do not > attempt to mount it. I don't know that I could, even if I wanted to: mkdir /mnt/iso mount /dev/sdc /mnt/iso or, because partition 1 starts at block 0, you may mount it too mount /dev/sdc1 /mnt/iso > # fdisk -l /dev/sdc > WARNING: GPT (GUID Partition Table) detected on

This action moves second(backup) GPT header to the end of the disk. It is usable in in-place image expanding, since free space after second GPT header is unusable. To use additional space, we have to move second header. This is what sgdisk -e does. However, sgdisk -e may perform additional actions if the partition table has unexpected params (e.g. if we call sgdisk -e /dev/sda1, it may fix

Please take a look. This feature is necessary for in-place image expanding. On 12/01/2015 06:28 PM, Maxim Perevedentsev wrote: > This action moves second(backup) GPT header to the end of the disk. > It is usable in in-place image expanding, since free space after > second GPT header is unusable. To use additional space, we have > to move second header. This is what sgdisk -e does.

>From: Tristan Gingold [mailto:Tristan.Gingold@bull.net] >Sent: 2006年4月21日 15:26 >> > >> >See how we solve this on x86 near the top of do_boot_cpu() in >> >arch/x86/smpboot.c. Essentially we allocate extra idle domains on >> >demand to give us enough idle vcpus for one per physical cpu. >> > >> > -- Keir >> >> Yes,

On 01/13/2015 12:47 PM, Gordon Messmer wrote: >> I'm having an issue getting a C6.6 install to work on a 3 TB dual hard >> drive system, raid 0. I'm hoping that someone here can help. > 1: Is this system booting UEFI or BIOS? > 2: Is the disk partitioned with MBR or GPT? > 3: Is /boot on its own partition? > > 3TB drives are larger than MBR and BIOS properly

Thomas Schmitt wrote: > David Christensen wrote: > > # fdisk -l /dev/sdc > > WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util > > fdisk doesn't support GPT. > > That's actually a bug in fdisk. The GPT is invalid because it is not > announced by a "Protective MBR". > > > Device Boot Start End

Hi, xencomm is the ppc infrastructure to do hypercalls with guest physical addresses instead of virtual address. Because ia64 should also use physicall address, I think it''s better to re-use the ppc code and to put into common code. I''d propose to submit this patch is every part is OK (ie no NAK). This patch creates include/xen/xencomm_access.h which is to be included by

I have 4 ST2000DL003-9VT166 (2Tbyte) disks in a RAID 5 array. Because of the size I built them as a GPT partitioned disk. They were originally built on a CentOS 5.x machine but more recently plugged into a CentOS 6.2 machine where they were detected just fine e.g. % parted /dev/sdj print Model: ATA ST2000DL003-9VT1 (scsi) Disk /dev/sdj: 2000GB Sector size (logical/physical): 512B/512B

New APIs: part_set_gpt_type part_get_gpt_type --- appliance/packagelist.in | 1 + daemon/parted.c | 129 +++++++++++++++++++++++++++++++++++++++++++++++ generator/actions.ml | 30 +++++++++++ generator/tests_c_api.ml | 7 +++ generator/types.ml | 5 ++ src/MAX_PROC_NR | 2 +- 6 files changed, 173 insertions(+), 1 deletion(-) diff --git

This action moves second(backup) GPT header to the end of the disk. It is usable in in-place image expanding, since free space after second GPT header is unusable. To use additional space, we have to move second header. This is what sgdisk -e does. However, sgdisk -e may perform additional actions if the partition table has unexpected params (e.g. if we call sgdisk -e /dev/sda1, it may fix

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 I think a Xen user expects to have lomount available as it's standard part of the upstream distribution. It's quite useful to access images created on fedora, or netbsd domU installations. Currently it's put somewhere deep in /usr/lib/xen-utils*/.../bin I also don't understand why the bins are placed there and an extra wrapper

On 4/9/2015 5:22 PM, Chuck Campbell wrote: > Subject says it. > > I would like to find out if I have anything written on the MBR of a > disk in my system /dev/sda, or any other device. > If there is something there, is it readable, or recognizable to humans? the MBR contains both binary boot code, which is not human readable, and the master partiion table for the device. you can

Hey all, This utility (from Qemu) might be useful to anyone who has multiple partitions on a file-backed VBD and wants occasionally to mount them in dom0. http://www.dad-answers.com/qemu/utilities/QEMU-HD-Mounter/lomount/ You can tell it what partition to mount out of the file and it sorts out the offsets, etc. by parsing the partition table. This allows you to get around the loop