search for: volid

Hi everyone; I noticed today while watching my syslog, a few entries like this: Nov 8 15:17:08 [machine] smbd[26137]: Attempt to create file (FILE.GHO) with volid set - please report this Nov 8 15:28:08 [machine] smbd[26137]: Attempt to create file (FILE0001.GHS) with volid set - please report this Nov 8 15:41:46 [machine] smbd[26137]: Attempt to create file (FILE0002.GHS) with volid set - please report this So, I'm reporting it. :) I'm using...

...mds I'm using now, which are working with syslinux4 just fine: xorriso -as mkisofs ${_qflag} \ -iso-level 3 -rock -joliet \ -max-iso9660-filenames -omit-period \ -omit-version-number \ -relaxed-filenames -allow-lowercase \ -volid "${LABEL}" \ -appid "${APPLICATION}" \ -publisher "${PUBLISHER}" \ -preparer "prepared by mkmiso" \ -eltorito-boot isolinux/isolinux.bin \ -eltorito-catalog isolinux/boot.cat \ -no-...

...with syslinux4 just > fine: > > xorriso -as mkisofs ${_qflag} \ > -iso-level 3 -rock -joliet \ > -max-iso9660-filenames -omit-period \ > -omit-version-number \ > -relaxed-filenames -allow-lowercase \ > -volid "${LABEL}" \ > -appid "${APPLICATION}" \ > -publisher "${PUBLISHER}" \ > -preparer "prepared by mkmiso" \ > -eltorito-boot isolinux/isolinux.bin \ > -eltorito-catalog isolinux/boo...

Thomas Schmitt via Syslinux said on Sat, Oct 24, 2015 at 12:56:49AM +0200: >Needed is a EFI FAT image > 32 MiB and a new xorriso (available >on demand). My test script on RHEL 7.1 creates that even if I could make it smaller as the kernel + initrd fits in less than 32 MB. So let me make that try first ! o I changed myline in the script to dd a 30 MB image file, burt the ISO with it, and

I''m trying to use this feature of qgroup: btrfs qgroup assign <srcid> <destid> <path> Assigns the lower level qgroup src to the higher level qgroup dest in the btrfs found in <path>. It is used to build qgroup hierarchies. However, I fail to understand how this feature should work, and I''m getting "ERROR: bad relation requested":

...hing that does not restrict filenames, it doesn't boder me that are shortnames as long as it let's me access the directory or filename. This is the commandline I use to compile my iso file: %BASEDIR%\isolinux\buildcd\win32\mkisofs -r -log-file log.txt -J -l -relaxed-filenames %CD_VERBOSE% -volid %CD_VOLID% -p %CD_PREPARER% -P %CD_PUBLISHER% -A %CD_APPID% -b isolinux/isolinux.bin -no-emul-boot -boot-load-size 4 -boot-info-table -hide boot.catalog -hide-joliet boot.catalog -o bootcd.iso %BASEDIR% __________________________________________________ Do you Yahoo!? Yahoo! Web Hosting - establis...

...hing that does not restrict filenames, it doesn't boder me that are shortnames as long as it let's me access the directory or filename. This is the commandline I use to compile my iso file: %BASEDIR%\isolinux\buildcd\win32\mkisofs -r -log-file log.txt -J -l -relaxed-filenames %CD_VERBOSE% -volid %CD_VOLID% -p %CD_PREPARER% -P %CD_PUBLISHER% -A %CD_APPID% -b isolinux/isolinux.bin -no-emul-boot -boot-load-size 4 -boot-info-table -hide boot.catalog -hide-joliet boot.catalog -o bootcd.iso %BASEDIR% Can anyone help please because when I use a filename or directoryname wich contains the space c...

...ccurs. - 3.11 boots, BUT windows boot files will not load and no error message occurs. used mkiso command: mkisofs -joliet-long -relaxed-filenames -r -l -d -D -N -J \ -p "$PREPARER" -publisher "$PUBLISHER" -b $BOOT \ -no-emul-boot -boot-load-size 4 -V "$VOLID" -no-iso-translate \ -c boot.cat -hide $BOOT -hide-joliet $BOOT \ -o $ISOFILENAME $ISOROOT Windows boot files are these files to boot up a windows NT installation. What did I wrong? What should I have a look at that my CDs work on most systems? When the BIOS gives an option...

is there any way to use cloud-init configs in python libvirt? cloud-init require to create an iso, which seems that ovirt support cloud-config: https://red.ht/2K1gBkn But how can I do that by python libvirt? I know I can mount iso by python libvirt to the VM, but the process of creating iso file is the problem which if it is possible to enter the cloud-config commands by libvirt could be better

...label linux_ks menu label ^Install CentOS 7 with Kickstart kernel vmlinuz append initrd=initrd.img inst.stage2=hd:sdb2:/ ks=hd:sdb1:/ks.cfg 7. create the ISO with: /usr/bin/genisoimage -untranslated-filenames -volid 'CentOS-7.0-KS-x86_64' -J -joliet-long -rational-rock -translation-table -input-charset utf-8 -x ./lost+found -b isolinux/isolinux.bin -c isolinux/ boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table 8. dd if=/CentOS-7-ISO-respin/CentOS-7-CSB-iso/CentOS-7.0-KS-x86_64-...

...s.fat 3.0.20 (12 Jun 2013) GNU xorriso 1.4.1 : RockRidge filesystem manipulator, libburnia project. Drive current: -outdev 'stdio:testuefi.iso' Media current: stdio file, overwriteable Media status : is blank Media summary: 0 sessions, 0 data blocks, 0 data, 33.0g free xorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119 rules xorriso : FAILURE : -as mkisofs: Unrecognized option '-efi-boot' xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE So the efi-boot option is not known. >In any case i would be interested to see what xorriso repor...

On 11/21/2013 02:50 AM, Carl Duff wrote: > Hi All, > > It is impossible to boot Linux-based ISOs that use Syslinux 6.02 via > CD or DVD on older - non-UEFI - systems. Any attempt to do so will > result in the following error message: ISOLINUX 6.02 ETCDisolinux: > Disk error 01, AX = 4279, drive FE > Error 01 is unsupported operation, 42xx is read, so something is really

hi, i'm doing my own windows multiboot dvd's using latest ultraiso and isolinux 3.09, and everything was fine till now. now i tried 3.11 and this release doesn't load any windows cd boot sectors while other stuff like memtest works fine. same for isolinux 3.10, both the normal and the debug version. the attachment shows a vmware 5.5 beta window with an error message by isolinux 3.11

I am reposting this because it's been 2 or 3 weeks. Hello, Hopefully this is the right place to send a question like this... I'm attempting to automate creation of VMs using virt-install and a cloud-init disk image. To get this to work, I need to specify the location of the cloud-init configs by passing smbios key/value pairs. Normally, -smbios is provided to qemu to do this. With

T.D.Lee@durham.ac.uk wrote: > > > But we'd like to go one step further and have the return code from preexec > be used to continue or abort the connection being established. The script > above would be modified to generate this return code. > > Looking through the source code (smbd/service.c), it doesn't seem to check > the return code (calling smbrun to do the