search for: 411647

...da > ... > Partition table scan: > MBR: protective > BSD: not present > APM: not present > GPT: present > > Found valid GPT with protective MBR; using GPT. > ... > Number Start (sector) End (sector) Size Code Name > 1 2048 411647 200.0 MiB EF00 EFI System Partition > 2 411648 1435647 500.0 MiB 8300 BOOT System Partition > 3 1435648 22646783 10.1 GiB 8300 ROOT System Partition > 4 22646784 25163775 1.2 GiB 8200 SWAP System Partition >...

...f49517aa36b4a79998b4332289489 > # gdisk -l /dev/vda ... Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. ... Number Start (sector) End (sector) Size Code Name 1 2048 411647 200.0 MiB EF00 EFI System Partition 2 411648 1435647 500.0 MiB 8300 BOOT System Partition 3 1435648 22646783 10.1 GiB 8300 ROOT System Partition 4 22646784 25163775 1.2 GiB 8200 SWAP System Partition # fdisk -l /dev/vda...

...an: >> MBR: protective >> BSD: not present >> APM: not present >> GPT: present >> >> Found valid GPT with protective MBR; using GPT. >> ... >> Number Start (sector) End (sector) Size Code Name >> 1 2048 411647 200.0 MiB EF00 EFI System Partition >> 2 411648 1435647 500.0 MiB 8300 BOOT System Partition >> 3 1435648 22646783 10.1 GiB 8300 ROOT System Partition >> 4 22646784 25163775 1.2 GiB 8200 SWAP System Part...

The exisiting label= option offer to boot on a gpt partition that have a particular label. The existing guuid= option offer to boot on a disk or partition with a particular label. This new option offer to boot the disk that have a partition which have a given label. The label is so just a way to detect a disk to boot. A typical use is for making an intelligent localboot like : label

Good day time! Using openssh with a serial attached terminal figures with a problem with flow control when serial terminal has printer connected to it etc. because ssh disables xon/xoff on associated terminal. At present ssh client always disables xon/xoff on associated terminal device, regarding of it's previous state, e.g. ixon and ixoff options were set or not. By searching the google

...mfs-4.4.0-0.rc5.git0.1.fc24.x86_64.img This is also necessary so grubby can update configuration file # ln -s /boot/efi/EFI/extlinux /boot And finally, what disk and partition, ... # fdisk -l /dev/vda ... Disklabel type: gpt ... Device Start End Sectors Size Type /dev/vda1 2048 411647 409600 200M Microsoft basic data /dev/vda2 411648 1435647 1024000 500M Linux filesystem ... Switching from a freshly installed system # exit ... disk, and partition number, pass to EFI Boot Manager # efibootmgr -c -d /dev/vda -p 1 -l /EFI/extlinux/syslinux.efi -L "Syslinux efi64&quot...

I used Hiren Boot CD (Some tool on it) to create 8 partitions for Windows XP and CentOS 6. Now, CentOS6 Disk Utility reports for first partition: "Warning: The partition is misaligned by 512 bytes. This may result in very poor performances. Repartitioning is suggested.", and similar warnings almost all other partitions. Since I already have both Windows (NTFS) and CentOS 6

...linders, total 3904897024 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0006e122 Device Boot Start End Blocks Id System /dev/sda1 * 2048 411647 204800 83 Linux Partition 1 does not end on cylinder boundary. /dev/sda2 411648 1048987647 524288000 83 Linux /dev/sda3 1048987648 1082542079 16777216 82 Linux swap / Solaris /dev/sda4 1082542080 3904897023 1411177472 83 Linux I assume I can ignore it a...

...> BSD: not present > >> APM: not present > >> GPT: present > >> > >> Found valid GPT with protective MBR; using GPT. > >> ... > >> Number Start (sector) End (sector) Size Code Name > >> 1 2048 411647 200.0 MiB EF00 EFI System > Partition > >> 2 411648 1435647 500.0 MiB 8300 BOOT System > Partition > >> 3 1435648 22646783 10.1 GiB 8300 ROOT System > Partition > >> 4 22646784 25163775 1.2...

...artnum); + free (out); + return NULL; + } + + /* Parse the output of sgdisk -i: + * Partition GUID code: 21686148-6449-6E6F-744E-656564454649 (BIOS boot partition) + * Partition unique GUID: 19AEC5FE-D63A-4A15-9D37-6FCBFB873DC0 + * First sector: 2048 (at 1024.0 KiB) + * Last sector: 411647 (at 201.0 MiB) + * Partition size: 409600 sectors (200.0 MiB) + * Attribute flags: 0000000000000000 + * Partition name: 'EFI System Partition' + */ + for (char **i = lines; *i != NULL; i++) { + char *line = *i; + + if (verbose) fprintf (stderr, "%s\n", line); + +...

I think this fixes everything mentioned: - Added the Optgroups module as suggested. - Remove command temporary files. - Replace command ~flags with ?fold_stdout_on_stderr. - Nest _with_mounted function. - Rebase & retest. Rich.

v1 was posted here: https://www.redhat.com/archives/libguestfs/2017-July/msg00098.html This series now depends on two small patches which I posted separately: https://www.redhat.com/archives/libguestfs/2017-July/msg00207.html https://www.redhat.com/archives/libguestfs/2017-July/msg00209.html v1 -> v2: - Previously changes to generator/daemon.ml were made incrementally through the patch

Previously posted as part of the mega utilities/inspection series here: https://www.redhat.com/archives/libguestfs/2017-June/msg00232.html What I've done is to extract just the parts related to rewriting daemon APIs in OCaml, rebase them on top of the current master, fix a few things, and recompile and test everything. Rich.

v6 was posted here: https://www.redhat.com/archives/libguestfs/2017-June/msg00103.html and this requires the utilities refactoring posted here: https://www.redhat.com/archives/libguestfs/2017-June/msg00169.html Inspection is now complete[*], although not very well tested. I'm intending to compare the output of many guests using old & new virt-inspector to see if I can find any

v5: https://www.redhat.com/archives/libguestfs/2017-June/msg00065.html Since v5, this now implements inspection almost completely for Linux and Windows guests. Rich.

v7 was: https://www.redhat.com/archives/libguestfs/2017-June/msg00169.html https://www.redhat.com/archives/libguestfs/2017-June/msg00184.html I believe this addresses all comments received so far. Also it now passes a test where I compared about 100 disk images processed with old and new virt-inspector binaries. The output is identical in all cases except one which is caused by a bug in blkid