similar to: standalone bootable usb-stick

Hello all Now I may be way of whack here, so please forgive me. I''m trying to merge xen with redhat''s config-netboot. The idea being a kinda stateless domU. For those that haven''t seen you share a rootfs and then bind mount all the individual files over then top, and the redhat gui builds all the pxeboot config and stuff for you if you want a diskless client. I

Hey, guys. I have a problem when installing syslinux 4.06, and I'd be grateful if someone could tell me how to solve the problem. My task - to install the bootloader on the virtual machine image. The image contains the MBR and the only partition with the file system ext4. The file system contains all the files for the guest OS. To install bootloader into the image of the guest OS, I use the

Hello, Im a Gentoo kernel maintainer thats trying to fix some bugs on are upcoming 1.4 livecd release that uses IsoLinux. Our isolinux.cfg is pretty standard : ######################################### default gentoo append initrd=initrd acpi=off root=/dev/ram0 init=/linuxrc timeout 300 prompt 1 display boot.msg F1 boot.msg F2 help.msg label livecd kernel gentoo append

Having fought my PXE config and eventually getting it to work (had to comment out the group { } statments ? I now come across another issue I cannot resolve and would appreciate some help. in my /tftpboot/pxelinux.cfg/default file I have cause to use the APPEND statement to pass options to the kernel being used. Unfortunately this line has now become longer than 255 characters and appears to be

This is most exceedingly weird boot/shutdown sequence that I used once, and can't find a way to adapt to initramfs. Since you guys are trying to adapt all mechanisms that use initrd to using initramfs, this should interest you. initrd has (all binaries static): /bin: init halt mount poweroff pivot_root reboot sh umount /etc: fstab haltrc /dev: null zero tty tty0 tty1 console->tty0 hda1

Hi! I recently tried to mount a filesystem in RAID1 mode using loopback devices. I followed the instructions at [1]. Here''s exactly what I''ve done: $ dd if=/dev/zero of=raid1_0.img bs=1M count=500 $ dd if=/dev/zero of=raid1_1.img bs=1M count=500 $ mkfs.btrfs -m raid1 -d raid1 raid1_0.img raid1_1.img $ losetup /dev/loop0 raid1_0.img $ losetup /dev/loop1 raid1_1.img $ mount -t

Hi, I'm trying to build a bootable MSDOS disk and put it on a ISO with floppy and hard disk emulation. I want to use commonly available Linux tools like dd, losetup, mkdosfs, memdisk etc. I have done the following: 1. dd if=/dev/zero of=myImage bs=1M count=50 [ Builds a 52MB image ] 2. losetup /dev/loop0 myImage [Links /dev/loop0 to myImage file ] 3. vi /grub/stage1; %!xxd; [ NULL the partion

fixes install from ISO --- scripts/ovirt-functions | 12 +++++++----- 1 files changed, 7 insertions(+), 5 deletions(-) diff --git a/scripts/ovirt-functions b/scripts/ovirt-functions index e01ee0e..3f55656 100644 --- a/scripts/ovirt-functions +++ b/scripts/ovirt-functions @@ -249,11 +249,13 @@ mount_live() { return 0 fi local live_dev=/dev/live - if [ ! -e $live_dev ]

The following is a pxelinux problem, specifically to do with including config files with the menu include directive and the ifcpu64.c32 com module. I have a working ifcpu64.c32 setup that jumps to the label rescue64 in the case of a 64-bit CPU. The label "rescue64" defines a 64-bit kernel and a 64-bit initrd.img. The setup jumps to a label named "rescue32" in the case of a

Here's the problem. We perform full tar backups of our CentOS 4/5 machines in real-time at regular intervals. And when a disaster happens, we are able to restore those backups onto virgin filesystems, make the /dev/null, /dev/zero and /dev/console devices .. and boot the machine. This has worked well on standalone systems, and also on Xen 3.0.3 guests on CentOS 4.4 machines, where each guest

hi there i try to setup OCFS2 with loop device /dev/loop0 i've 4 servers running SLES10 SP2. internal ip's: 192.168.55.1, .2, .3 and .6 my cluster.conf: -------------------------------------------- node: ip_port = 7777 ip_address = 192.168.55.1 number = 0 name = www cluster = cawww node: ip_port = 7777 ip_address = 192.168.55.2

Hi, I 'am trying to launch linux kernel 2.6.7 with initramfs. My pxelinux.cfg/default file looks as follows: default a1 prompt 1 timeout 600 label a1 kernel vmlinuz-2.6.7-1 append initrd=initramfs_data.cpio.gz root=/dev/ram0 init=/linuxrc Kernel image vmlinuz-2.6.7-1 and initramfs_data.cpio.gz was loaded succesfully by pxelinux. Kernel says: checking if image is initramfs... it is but

Hi! $ xm create -n -f xmtest Using config file "xmtest". (vm (name testdomain) (memory 128) (image (linux (kernel /boot/vmlinuz-2.6.8-foo1-XenU) (ip :1.2.3.4:::tesmo:eth0:dhcp) (root ''/dev/xda1 ro'') (args 1) ) ) (device (vbd (uname phy:loop0) (dev xda1) (mode w))) (device (vif (mac

Hi! I write this config line: kernel /boot/i386/vmlinuz ro ramdisk=32768 root=/dev/ram0 init=/linuxrc but when I try to boot I got this mesasge: Could not find kernel image: /boot/i.386/ Same symptomes are with slash and backslash too. I think, the parses don't understand the directory separator characters and count as the part of filename. ps Sorry for my english -- Gabor HALASZ

I am trying to create a bootable cd from a working LFS 6.1 partition. Thank you in advance for any thoughts on this. This is the error I get: ISOLINUX 3.10 2008-08-24 Copyright (C) 1994-2005 H. Peter Anvin Could not find kernel image: lfskernel-2.6.11.12 boot : _ under /isolinux/ I have these files: isolinux.bin I've tried 3.10 and 3.09 isolinux.cfg: default livecd label livecd

Hello, When I upgrade syslinux from 2.13 to 3.02. my linux floppy doesn't boot anymore. steps: dd if=/dev/zero of=fdimg bs=18k count=160 mkdosfs fdimg syslinux fdimg mount -o loop fdimg /mnt cp files/* /mnt/ umount /mnt then use memdisk load fdimg the files includes: vmlinuz initrd syslinux.cfg message.txt f1.txt ... it only prompts 1 line: SYSLINUX 3.02

Looking at the FAQ for SysLinux there is an option for an initrd file (initrd=filename), this does not seem to work with pxelinux (or it is just that I am doing something wrong...). here is my config file: prompt 1 #serial 0 115200 label linux kernel vmlinuz-2.4.18-ssi #read-write #root=/dev/ram0 append init=/linuxrc console=tty0 console=ttyS0,115200 initrd initrd-2.4.18-ssi.img label local

Have been trying some things, but something isn't working at least with using Virtual Box with EFI option. With it off, the cd boots as normal, and works, but with EFI on, it has an error that flashes on screen, and then it drops to a shell prompt. I'm hoping it is just a dumb mistake I am making, and can be resolved. Perhaps I've named the directories incorrectly, or there is a

centos 6 failed to create entries under /dev for newly created loopback devices. Any one know why? and how to fix/workaround it? The steps to duplicate is pretty simple dd if=/dev/zero of=/tmp/deleteme bs=1M count=100 losetup /dev/loop0 /tmp/deleteme fdisk /dev/loop0?? ## created partitions 1, 2, etc. fdisk -l /dev/loop0? ## confirmed that the partitions do exist mkfs.ext3 /dev/loop0p1 ## failed

Hello again, I'm always not able to boot-up my CF-FileSystem. (It works with a 2.4.x Kernel!) See: http://syslinux.zytor.com/archives/2006-June/006942.html I dont't understand, why the kernel can't mount the root-fs on exit of "linuxrc". Before finising "linuxrc" I can work on it, start a "bash"-shell, do all sorts of linux-cmds on the root-fs...