similar to: [klibc 06/43] Re-create ROOT_DEV, too many architectures need it.

Linus' tree has a space-tab sequence for a few lines in these files, causing an unnecessary delta. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit 7c753dbe7467f0d5ff6904f1bf5840350527e3c4 tree c40a68f6556a702a836d9a6e90f5d632eed0bc0c parent 0f5a324d655ad582246b6830843114d09835f593 author H. Peter Anvin <hpa at zytor.com> Thu, 06 Apr 2006 14:15:53 -0700 committer H.

Here is a partial patch that I'm using to illustrate a few questions that I have. Looking at the gpllib write_sectors (com32/gpllib/disk/write.c) it looks like the allocated size is wrong; size is in sectors so we should adjust the alloc/memcpy by size*SECTOR. Also, comparing core/diskio.c it looks like the registers aren't even setup right. In the patch below I put an #if 0 around the

Based on syslinux 6.03 Memory allocation and copy length should be SECTOR * size for sectors operation. Signed-off-by: Robert <luyao-c at 360.cn> diff --git a/com32/gpllib/disk/write.c b/com32/gpllib/disk/write.c index d183ade..3c9edff 100644 --- a/com32/gpllib/disk/write.c +++ b/com32/gpllib/disk/write.c @@ -40,7 +40,7 @@ int write_sectors(const struct driveinfo *drive_info, const

Hi I am trying to have a built in initramfs along with the traditional initrd. So I mount the initrd from the initramfs, but am facing problems in trying to run the 'linuxrc'. Following are the issues: 1. I mount the initrd from the initramfs and exceve 'linuxrc'. It starts executing linuxrc, but gives the following errors and panics: Red hat nash version 3.4.42 starting

Hi Peter, Please pull the following changes. Paulo, I had to revert your "pxe: resolve names via DNS from protected-mode code" change because dns_resolv() is only implemented for PXELINUX and causes undefined symbol references for ISOLINUX, etc. Feel free to make the change again on top of the revert. The following changes since commit e7bd19def830e8341b1a100956345f1028740b9e:

Sorry, hit send instead of attach again. Rest of patches included. -- Anthony Liguori Samba, Linux/Windows Interoperability Linux Technology Center (LTC) - IBM Austin E-mail: aliguori@us.ibm.com Phone: (512) 838-1208 Tie Line: 678-1208

Sparc64 has support for a bunch of architecture-specific options taken from the PROM. Convert them to kernel command line form and write the file /arch.cmd in the rootfs, which can be recovered by kinit and processed. The kinit support has already been committed. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit c6e5c5a77681f5bf6f9fea55d031115e9f58ada6 tree

Boot options which have been obtained in an architecture-specific fashion have to be copied to /arch.cmd in the rootfs. This implements that functionality for sparc32; the code is identical to sparc64 minus the openprom support for obtaining nfsroot options. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit fc8c0c09f9dd5139dd8d797eaf9fe33962b6cd2c tree

Hi, I am looking for a solution to boot MY system on any PC. To store most of the system and all of my data I want to use an USB storage (in my case an external USB harddisk (2.0 capable)). Since booting off an USB device is not an universal thing I would prefer to have a boot disk with a minimal system - just enough to load most (all?) of the system from the attached USB device. Is this an

This patch removes support for use of NFS as a root filesystem from the kernel. It also updates the documentation to reflect this. b/Documentation/nfsroot.txt | 97 +++--- b/arch/arm/def-configs/a5k | 1 b/arch/arm/def-configs/adi_evb | 1 b/arch/arm/def-configs/adsbitsy | 1 b/arch/arm/def-configs/anakin | 1

This change is part of an ongoing effort to remove use of $desc and inspect the OS directly as required during conversion. --- lib/Sys/VirtConvert/Connection/LibVirtTarget.pm | 4 +- lib/Sys/VirtConvert/Connection/RHEVTarget.pm | 41 +++++++++--------- lib/Sys/VirtConvert/Converter.pm | 35 ++++++++++++---- lib/Sys/VirtConvert/Converter/RedHat.pm | 45

This patch adds the ability to mount filesystems via an embedded fstab or via the kernel command line. When using the kernel command-line, the following format is required: 'kinit_mount=<fs_name>;<fs_dir>;<fs_type>;<fs_opts>' Multiple mount options can be specified; they are evaluated in the order they appear in the command-line. Signed-off-by: San Mehat <san

Now we can complete the cleanup of the root device management. Use the preferred APIs for creating and managing the root device. As part of this cleanup get rid of the root device object from vmbus_driver_context. Signed-off-by: K. Y. Srinivasan <kys at microsoft.com> Signed-off-by: Haiyang Zhang <haiyangz at microsoft.com> Signed-off-by: Mike Sterling <mike.sterling at

Now we can complete the cleanup of the root device management. Use the preferred APIs for creating and managing the root device. As part of this cleanup get rid of the root device object from vmbus_driver_context. Signed-off-by: K. Y. Srinivasan <kys at microsoft.com> Signed-off-by: Haiyang Zhang <haiyangz at microsoft.com> Signed-off-by: Mike Sterling <mike.sterling at

Hi, Hopefully you someone can tell me what I'm doing wrong. First, the code. I placed this at the bottom of the main loop in com32/modules/disk.c as a simple test of writing to the disk: printf(" Host bus: %s, Interface type: %s\n\n", d->edd_params.host_bus_type, d->edd_params.interface_type); zero_buf = calloc(1, d->edd_params.bytes_per_sector); for(int

Now that struct vmbus_driver_context is properly cleaned up, rename this structure appropriately and cleanup the code. Signed-off-by: K. Y. Srinivasan <kys at microsoft.com> Signed-off-by: Haiyang Zhang <haiyangz at microsoft.com> Signed-off-by: Mike Sterling <mike.sterling at microsoft.com> Signed-off-by: Abhishek Kane <v-abkane at microsoft.com> Signed-off-by: Hank

Now that struct vmbus_driver_context is properly cleaned up, rename this structure appropriately and cleanup the code. Signed-off-by: K. Y. Srinivasan <kys at microsoft.com> Signed-off-by: Haiyang Zhang <haiyangz at microsoft.com> Signed-off-by: Mike Sterling <mike.sterling at microsoft.com> Signed-off-by: Abhishek Kane <v-abkane at microsoft.com> Signed-off-by: Hank

Previous implementation had staticly defined partitions to remove. This would break in the case of split Root and HostVG devices. Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-config-boot | 11 +-------- scripts/ovirt-config-uninstall | 49 ++++++++++++++++++++++++--------------- scripts/ovirt-functions | 27 ++++++++++++++++++++++ 3 files changed, 58

--- scripts/uninstall.py | 75 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 75 insertions(+), 0 deletions(-) create mode 100755 scripts/uninstall.py diff --git a/scripts/uninstall.py b/scripts/uninstall.py new file mode 100755 index 0000000..9e0baff --- /dev/null +++ b/scripts/uninstall.py @@ -0,0 +1,75 @@ +#!/usr/bin/python +# +# uninstall.py - destroys an installed

Previous implementation had staticly defined partitions to remove. This would break in the case of split Root and HostVG devices. Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-config-boot | 11 +-------- scripts/ovirt-config-uninstall | 48 ++++++++++++++++++++++++--------------- scripts/ovirt-functions | 33 +++++++++++++++++++++++++++ 3 files