similar to: klibc-0.130: s390, run-init

initramfs-tools wants to validate the real init program before running it, as there is no way out once it has exec'd run-init. This is complicated by the increasing use of symlinks for /sbin/init and for /sbin itself. We can't simply resolve them with 'readlink -f' because any absolute symlinks will be resolved using the wrong root. Add a dry-run mode (-n option) to run-init

On a train ride to Bruxelles, brought out my axe and directly attacked run_init(8). run_init(8) is dead, long live switch_root(8). The next run on switch_root(8) involves fdopendir, so another push for the upcoming stdio 1.6 branch. The following is boot tested with initramfs-tools, kinit(8) tests would very much be appreciated!? Michal Suchanek (1): [klibc] switch_root: Fix single file

systemd supports switching back to the initramfs during shutdown in order to make it easier to clean up the root file system. This is desirable in order to allow us to remove keys from RAM before rebooting, making it harder to obtain confidential information by rebooting into an environment that scrapes RAM contents. --- debian/changelog | 4 +

The following patches come from Debian and/or Ubuntu packages of klibc. Ben. Ben Hutchings (1): [klibc] run-init: Add dry-run mode Jay Vosburgh (1): [klibc] ipconfig: Use separate sockets for DHCP from multiple interfaces Mathieu Trudel-Lapierre (1): [klibc] ipconfig: Set broadcast when sending DHCPREQUEST and DHCPDISCOVER YunQiang Su (1): [klibc] mips: setjmp.S: don't

Hello! I have problems with installation of Xen 3.1 in OpenSUSE 10.2. I have unpacked the xen 3.1 tarball and installed software using #sh ./install.sh Then I have modified /boot/grub/menu.lst and now it looks like: title openSUSE 10.2 root(hd0,2) kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda3 vga=0x314 resume=/dev/sda2 initrd /boot/initrd-2.6.18.2-34-default title

Hi, I noticed some issues with the ssh transport mode where the virt-v2v would fail because of issue with libssh2. I see a lot of following errors before the conversion terminates: > commandrvf: /usr/sbin/update-initramfs -v -c -k 4.9.0-4-amd64 > read failed: would block (libssh2 error code: -37, sftp error code: 0) > /usr/sbin/mkinitramfs: 265: /usr/sbin/mkinitramfs: dirname: Exec

Oye 3 days on this now, my head hurts. I have spent what seems like 40 hours in the last 3 or 4 days reading, and I realize xen is in the middle of this transition of getting into mainline kernel, issues with dom0 etc etc. Ok, so i have come across a few howtos/tutorials on installing xen dom0 kernel, using git to download a patched? kernel tree, and getting xen source from mercurial. Below is my

Hi. I am trying to make initrd for xen0 but I am not successful. I receive error: #yaird error: Could not read output for /sbin/modprobe -v -n --show-depends --set-version 2.6.16.33-xen0 evdev (fatal). If I do that just for xen kernel (not xen0) it goes without any problem. I guest I have to use initrd for xen0 otherwise it does not want to boot. Similarly, xen kernel without initrd will not

Hi All, I am not able to boot Xen . My "/boot/grub/menu.lst" has this entry title Xen 3.3.2-rc5 / Debian GNU/Linux, kernel 2.6.18.8-xen root (hd0,0) kernel /boot/xen-3.3.2-rc5.gz module /boot/vmlinuz-2.6.18.8-xen root=/dev/sda1 ro console=tty0 module /boot/initrd.img-2.6.18.8-xen savedefault I am getting following error : ERROR

Hi All, I am not able to boot Xen . My "/boot/grub/menu.lst" has this entry title Xen 3.3.2-rc5 / Debian GNU/Linux, kernel 2.6.18.8-xen root (hd0,0) kernel /boot/xen-3.3.2-rc5.gz module /boot/vmlinuz-2.6.18.8-xen root=/dev/sda1 ro console=tty0 module /boot/initrd.img-2.6.18.8-xen savedefault I am getting following error : ERROR

Hi All, I am not able to boot Xen . My "/boot/grub/menu.lst" has this entry title Xen 3.3.2-rc5 / Debian GNU/Linux, kernel 2.6.18.8-xen root (hd0,0) kernel /boot/xen-3.3.2-rc5.gz module /boot/vmlinuz-2.6.18.8-xen root=/dev/sda1 ro console=tty0 module /boot/initrd.img-2.6.18.8-xen savedefault I am getting following error : ERROR

Hi, had a few problems with using xen: First: built a xen from source (tgz) and make dist ... then made initrd with mkinitrd and modules=all in the mkinitrd.conf -> initrd.img was 14mb and set it up in the grub with module /initrd.... on boot it loads the initrd like: Loading ramdisk into ram .... done but then NO MODULES in the initrd are being loaded by the kernel, though initrd

hi all, i want to install xen3.1 on my system, suse linux enterprise server 10 SP1 (kernel 2.6.16.46-0.12). i download the tarball binary file. it contains only "vmlinuz-2.6.18-xen" and "xen-3.1.gz", no initrd. but see the following code in my grub menu.lst, it seems like i need the initrd file. i tried the installation with this binary Tarball, it didn''t work.

Hello, I''ve this strange problem. When Xen kernel start and it try to start eth devices, network doesn''t work. It seems to be a problem with NICs firmware. Anyone had this problem? Do you know where I can download firmware upgrade? (on DELL''s site I''ve just searched...) Thanks, Carlo No virus found in this outgoing message. Checked by AVG Free Edition.

Hello, I want to implement a diskless xen hypervisor. The way I suppose it will work is xen booted over pxe and getting iscsi san storage to store vm images. Is solution like that usable ? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, I have an Slackware 12.1 running on Intel Core2Quad, 4 Gb RAM. (The result of dmesg is attached on this e-mail) I have downloaded ''Xen 3.3.0 official source distribution tarball'' from www.xen.org. Run make world, make install. Have no errors. Installed GRUB correctly and added the following lines on menu.list: title Xen 3.3 root (hd0,1) kernel /xen.gz dom0_mem = 262144

Hi, I have a vector like this: DF <- c("Aetna, Inc.", "Alexander's Inc.", "Allegheny Energy, Inc") For each element in the vector I would like to remove the "incorporated" info, so that my vector looks like this: DF <- c("Aetna", "Alexander's", "Allegheny Energy") That means that I have to strip: strip <-

Hi all, I''m struggling to install Xen Hypervisor on my PC, but after one week''s attempt again and again, it still doesn''t work. Anyone can give some suggestion or helpful link? 1. download the xen 4.0.0 stable tarball from here, http://www.xen.org/products/xen_source.html 2. unzip the tar and run install.sh and ''make world'' 3. make install 4. then I

This patch series allows user-specified mount commands to be sent in via kernel command line ("kinit_mount=...") or via an embedded /etc/fstab file. The first patch is a cleanup of a patch sent last November by San Mehat (http://web.archiveorange.com/archive/v/EazJNBMORV2U7E0coh5h); the next two are small improvements or bug fixes.

I have finally gotten one version of windows 2003 r2 x64 installed as a guest. The bad news is no network. The network tab says it''s a realtek 8139 when I know it is a intel. I tried downloading the intel drivers and they wont install says it''s the wrong hard ware. Is this common that it uses a 8139 as a generic network card? Also the network card shows The