search for: isoimage

...with 2 CPUS and 8 GB of memory. This V240 is attached to a 3510 FC that has 12 x 300 GB disks. The 3510 is configured as HW RAID 5 with 10 disks and 2 spares and it''s exported to the V240 as a single LUN. We create iso images of our product in the following way (high-level): # mkfile 3g /isoimages/myiso # lofiadm -a /isoimages/myiso /dev/lofi/1 # newfs /dev/rlofi/1 # mount /dev/lofi/1 /mnt # cd /mnt; zcat /product/myproduct.tar.Z | tar xf - and we finally use mkisofs to create the iso image. UFS performance ---------------------- We created a UFS file system on the above LUN and the above...

...nuxPartition_UsbDrv Img kernel /DiskImages/memdisk append initrd=/DiskImages/BtInsUSB.img LABEL nu2-4 MENU LABEL ^4. Partition Magic8 -->Universal partition manager kernel /DiskImages/memdisk append initrd=/DiskImages/Pm8.img LABEL nu2-5 MENU LABEL ^5. Plpbt. KERNEL /ISOimages/memdisk INITRD /ISOimages/Plpbt.iso APPEND iso Thanks in advance Prof S W Damle

In the past I have used clonzilla under xen to backup windows domains. I just tried it and it will not work. this is xen 4.1.2 and clonzilla-live 1.2.10-14 the disk line is: disk = [ ''phy:/dev/xvg0/nfdlts-c,hda,w'', ''file:/extra/isoimages/clonzilla.iso,hdc:cdrom,r'' ] It boots cd OK. The problem is devices are xvda not hda and clonzilla is not happy with that. I tried sda and it seems to have a scsi driver problem. Can I force the device to be hda? Any ideas? John _______________________________________________ Xen-use...

Hello is there something wrong with the mail archive search scripts? I always seem to get 'list unavailable' :-( Anyway - 5_1 on Dell Latitude C640. the vmware3 port installs but the paths are a little odd - isoimages, licences are looked for in /usr/lib/vmware rather than /usr/local/lib.... I installed (w2k) a guest and it is fine but I cannot get networking host-only or bridge modes as the vmnet1 interface IP isn't found which indicates it hasn't found the config file in /usr/local/ - I tried sym-l...

...root 1638118 Mai 29 03:00 sfdisk lrwxrwxrwx 1 root root 4 Mai 29 19:55 sh -> bash -rwxr-xr-x 1 root root 2119455 Mai 29 03:00 umount /lfs/dev: [ ... snip (created with MKDEV-1.5) ... ] following dirs are empty but exists: ./etc ./lib ./mnt ./proc ./var the /isoimage/isolinux/ directory: -rw-r--r-- 1 root root 5416064 Mai 29 19:59 initrdgz.img -rw-r--r-- 1 root root 9020 Mai 29 20:04 isolinux.bin -rw-r--r-- 1 root root 88 Mai 29 20:04 isolinux.cfg -rw-r--r-- 1 root root 746466 Mai 29 19:24 linux the /isoimag...

.../cache/ is empty. And, yes, the UUID matches: # blkid /dev/vda1: UUID="297e2939-d6f5-431a-9813-9848368ee306" TYPE="xfs" /dev/vda2: UUID="OR1eUA-1hhb-PCff-qybQ-rLt4-JuTN-EcWX61" TYPE="LVM2_member" /dev/sr0: UUID="2017-03-16-21-15-06-00" LABEL="ISOIMAGE" TYPE="iso9660" PTTYPE="PMBR" /dev/mapper/centos-root: UUID="fcee6215-e97a-4a4f-9473-5115f8559683" TYPE="xfs" /dev/mapper/centos-swap: UUID="b220b45f-ae22-4393-a74d-90b03d37c41b" TYPE="swap" # cat /etc/fstab # # /etc/fstab # Creat...

Hello, Is "Dos installer from Win98" REMOVED from Syslinux-5.00/syslinux-5.01-pre1? Prof S W Damle

...successfully before? > > # blkid > /dev/vda1: UUID="297e2939-d6f5-431a-9813-9848368ee306" TYPE="xfs" > /dev/vda2: UUID="OR1eUA-1hhb-PCff-qybQ-rLt4-JuTN-EcWX61" TYPE="LVM2_member" > /dev/sr0: UUID="2017-03-16-21-15-06-00" LABEL="ISOIMAGE" TYPE="iso9660" > PTTYPE="PMBR" > /dev/mapper/centos-root: UUID="fcee6215-e97a-4a4f-9473-5115f8559683" > TYPE="xfs" > /dev/mapper/centos-swap: UUID="b220b45f-ae22-4393-a74d-90b03d37c41b" > TYPE="swap" > > # cat /e...

...er Anvin isolinux: Starting up, DL = 9F isolinux: Loaded spec packet OK, drive = 9F isolinux: Loading main image from LBA = 0000278 isolinux: Sectors to load = 0004 isolinux: Disk error 32, drive 9F Boot failed: press a key to retry. To create the iso image I am using the command: mkisofs -o $ISOIMAGE -b isolinux/${BOOTBIN} \ -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 \ -boot-info-table $MASTERISO (where BOOTBIN=isolinux-debug.bin, and the other variable subsitute for appropiate files/directories). The isolinux.cfg file contains display isolinux.dsp timeout 10 default...

...om0, and I want to create DomU images. I have downloaded the .iso image for Fedora 17. I have a logical volume xmf17lvm on volume group xenvg. Here is my install profile ( will use "xm create -c xmf17install" ) name="xmf17install" memory=1024 vcpus=1 disk=[''file:/home/isoimage/Fedora17.iso,xvdc:cdrom,r'',''phy:/dev/xenvg/xmf17lvm,xvda,w''] vif = [ ''bridge=br0'' ] onreboot = ''restart'' oncrash = ''restart'' boot=''d'' builder=''hvm'' Its almost 3 AM here, so I am giv...

Hello, I'm struggling to make a cloned CentOS 7 VM (under KVM) to work. The VM was cloned using mondorestore. Restore appears successful but the VM won't boot; see: http://iweb.noa.gr/files/centos7/supergrub2-scratchvm-20170503-04.png I booted with CentOS 7 disk in troubleshooting mode (where the virtual disk was automatically mounted without issues) and I tried to repair:

hey, Ive got your syslinux booting a floppy disk that boots an image via NFS just fine and dandy.. default linux-jason prompt 1 display boot.msg timeout 100 label linux-jason kernel vmlinuz append append=root=/dev/nfs rw nfsroot=xx.xx.xx.xx:/var/local/user/thinpc,rw,v3,rsize=32768,wsize=32768,hard,udp,nolock,posix vga=792 ip=dhcp label linux-egg kernel vmlinuz

Hello all, I thought I'd ask you guys about this one since I've had no luck from vmware forums/kb or google ... I have a centos 4.3 x86-64 (athlon64 with cool-n quiet enabled) with vmware server 1.0 installed and working beautifully with the annoying exception of my guest machines clocks (centos, ubuntu etc) run very fast. I've read the vmware white paper on guest clocks, tried

On 16 Aug 2019 at 5:40, Ady Ady via Syslinux wrote: To: "syslinux at zytor.com" <syslinux at zytor.com> Date sent: Fri, 16 Aug 2019 05:40:45 +0000 Subject: Re: [syslinux] Question on upgrading to syslinux 6.04? From: Ady Ady via Syslinux <syslinux at syslinux.org> Send reply to: Ady Ady <ady-sf at hotmail.com> > > I've

This series: 1. Updates the boot protocol to version 2.07 2. Clean up the existing build process, to get rid of tools/build and make the linker do more heavy lifting 3. Make the bzImage payload an ELF file. The bootloader can extract this as a naked ELF file by skipping over boot_params.setup_sects worth of 16-bit setup code. 4. Update the boot_params to 2.07, and update the

This series: 1. Updates the boot protocol to version 2.07 2. Clean up the existing build process, to get rid of tools/build and make the linker do more heavy lifting 3. Make the bzImage payload an ELF file. The bootloader can extract this as a naked ELF file by skipping over boot_params.setup_sects worth of 16-bit setup code. 4. Update the boot_params to 2.07, and update the

isolinux: Extremely broken BIOS detected Yoper 2.1 --------- ISOLINUX 2.11 2004-08-16 isolinux: Loading spec packet failed, trying to wing it... isolinux: Extremely broken BIOS detected, last ditch attempt with drive = 9F isolinux: Disk error 01, AX = 4209, drive 9F Boot failed: press a key to retry... Helix 1.5 --------- ISOLINUX 2.04 (Debian, 2003-06-06) isolinux: Loading spec packet failed,

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some