search for: 9660

Hi, While researching on where rsync-3.0.6 spending more time when we have huge number of files in directory(~1000K files). I got below statistics: 2009/05/28 19:05:38 [9660] building file list . . . 2009/05/28 21:40:09 [9660] Number of files: 724591 2009/05/28 21:40:09 [9660] Number of files transferred: 5674 2009/05/28 21:40:09 [9660] Total file size: 63492447862 bytes 2009/05/28 21:40:09 [9660] Total transferred file size: 1472465959 bytes 2009/05/28 21:40:09...

https://bugzilla.samba.org/show_bug.cgi?id=9660 Summary: rsync --daemon --bwlimit does not work on server side Product: rsync Version: 3.0.9 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayne...

Hi, i began to implement a common lookup function for SUSP and Rock Ridge entries: /* Obtain the payload bytes of all SUSP entries with a given signature. @param fs The data source from which to read CE blocks. @param dir_rec Memory containing the whole ISO 9660 directory record. @param sig Two characters of SUSP signature. E.g. "NM", "ER", ... @param data Returns allocated memory with the found payload. @param len_data Returns the number of valid bytes in *data. (Does not include the trailing 0-...

Hi, OLPC's Openfirmware (OFW) implementation chokes when attempting to boot an iso created by isohybrid. The problem is that OFW's ISO-9660 support expects a partition type of 0x96 (CHRP ISO-9660, according to http://en.wikipedia.org/wiki/Partition_type). I see from http://git.kernel.org/cgit/boot/syslinux/syslinux.git/commit/utils/isohybrid.in?id=aee4e8fa73571eaca80ad43aa007523cde5d4567 that the partition type was originally 0x83 (Li...

...oot/isolinux xorriso is comprised of the following components: - libisofs under responsibility of Vreixo Formoso, - libburn, libisoburn, xorriso under responsibility of me, Thomas Schmitt. Neither Vreixo nor i have experience with creating live CDs or DVDs. Vreixo knows about ECMA-119 (aka ISO 9660) and El Torito. I know about MMC (for driving burners) and about the xorriso application. So if the ISOLINUX community is interested in having a custom-tailored ISO 9660 and MMC burn program, here is the chance to exert influence. xorriso's -boot_image class "isolinux" is open to any...

Hi there. Slackware's installer, that I am internationalizing, makes use of ISOLINUX. I want to give instructions to users in other languages than US English, e.g. which code to type to see installation messages in their native language. So my question are: (1) Which character encodings can be used in message.txt and f1.txt through f1O.txt? (2) Is UTF-8 allowed? (3) I'm guessing that

Hi, piranna wrote: > > Quoting http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI: > > "The additional isohybrid feature for UEFI adds a partition to the MBR > > partition table pointing to the same file in the ISO 9660 filesystem > > as does the El Torito catalog entry for EFI." Ady wrote: > IMHO, the current content of the Isohybrid page in the Syslinux Wiki is > not clear enough [...] The current generic information is > rather focused on _potential_ capabilities of _isohybrid_ tools and...

...oducer. Its formatting as MS-DOS-ly FAT filesystem image and the FAT path /efi/boot/bootx64.efi are prescribed by UEFI specs. The program bootx64.efi is supposed to start the boot process. I understand from the sparse content of Debian's amd64 FATs that GRUB2's bootx64.efi can interpret ISO 9660 and find its configuration files in there. > wrongly, suggests [...] that the 'syslinux.efi' is lacking > such "important" feature. This is what i understand from SYSLINUX being unable to boot from ISO 9660 via UEFI. The EFI related software of SYSLINUX seems not to be p...

When I try to install Leogo Mindstorms NXT directly from cdrom, I get this error (in a pop up window): ----------------------------------------------------------------------------------------------------- .\ConfigInfo.cpp(2653): IInstallerError 11006 Developer Error. The following errors were found in your ini file: 1. Specified file not found: [MsiEngine] WinNTPath =

...wrote: > If users want to find the "--uefi" parameter for the isohybrid command, > it is already there, documented. Yes. But it does only work with non-SYSLINUX boot images. It is undisputed that one can work around that problem on a hard-disk-like medium by simply not using ISO 9660 but a set of partitions and SYSLINUX EFI software. But this does not help with optical media. There the El Torito specs clearly define the boot catalog and images as parasites of an ISO 9660 filesystem. You have no chance to express this by a set of partitions. So for ISOLINUX and isohybrid, EFI...

...s, genisoimage offers option -e for embedding a FAT filesystem image. (genisoimage is a fork of mkisofs, so "real" is somewhat misleading in respect to history.) For details see: http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI I am author of xorriso and willing to help with ISO 9660 composition, if questions arise. > Alternatively, instead of using a "floppy-like" ("super-floppy", > "partition-less") FAT image, you "could" try a "HDD-like" image, with > GPT (somewhat equivalent to the "El Torito HDD-emulation&...

Hello! I have a problem with a bootable cd that i'm trying to make .. The problem is that i don't know what all the mkisofs parameters do and because that weird things happen, if the filenames or directorynames contain spaces they do not open and if i'm in windows's safe mode it gives me an error message stating that the file or folder does not exist! Can anyone help with that?

Quoting http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI: "The additional isohybrid feature for UEFI adds a partition to the MBR partition table pointing to the same file in the ISO 9660 filesystem as does the El Torito catalog entry for EFI." According to this (and can be see using fdisk) it's being created a partition-inside-partition just by setting its start and end sectors, so this could be done to be equal to the initial MBR partition generated by IsoHybrid, so ther...

> Hello, > > Ady via Syslinux said on Mon, Apr 06, 2015 at 09:57:02PM +0300: > >Can 'syslinux.efi' v.6.03 boot some media formatted with ISO9660? > > Not at this time, no. > > It took me quite some time to find that :-( Google didn't really help. > > I'd like to get a bit more details on this issue: > > 1/ Using syslinux.efi for PXE booting of a UEFI server is working for > me. > 2/ Using syslinux...

Hi I'm having an issue with doveadm batch - the following command always crashes: doveadm batch : mailbox status all inbox Whereas the following work as expected: doveadm mailbox status all inbox doveadm batch : mailbox list Any assistance gratefully received. Debug output from the crash: Debug: Loading modules from directory: /usr/lib64/dovecot Debug: Module loaded:

Until Syslinux 3.86, isolinux.bin contained a checksum that was calculated by 'core/checksumiso.pl'. The checksum is related to the patching of the boot info table. During May 2009, a commit by Peter deleted the checksumiso.pl file. The commit is: core: LZO compress the PM part of the core repo.or.cz/syslinux.git/commit/0d82b71304d596d80f3c4520f9dcf90048ca50b7 And so, since

...ISO production run: > > sudo mkisofs -r -V "$IMAGE_NAME" -cache-inodes -J -l -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -o ../ubuntu-remix.iso . > > (But i really wonder why one needs to be superuser to create an > ISO 9660 filesystem.) > > So what are your actual symptoms of failure with ISO production ? > > > Have a nice day :) > > Thomas > > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options...

...". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/doveadm...Reading symbols from /usr/lib/debug/usr/bin/doveadm.debug...done. done. (gdb) run Starting program: /usr/bin/doveadm batch : mailbox status all inbox process 9660 is executing new program: /usr/bin/doveconf process 9660 is executing new program: /usr/bin/doveadm [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". doveadm(jc): Panic: file mail-storage.c: line 875 (mailbox_set_reason): assertion...

...mming begins at byte 64 of isolinux.bin. When prepcore writes isolinux.bin it begins copying bytes from the input file at the offset given by variable "start". But it begins checksumming at offset 64 of the input file. The problem exists since introduction of prepcore by release 4.00. ISO 9660 programs usually fix it when they write the Boot Info Table. Signed-off-by: Thomas Schmitt <scdbackup at gmx.net> --- --- a/lzo/prepcore.c +++ b/lzo/prepcore.c @@ -331,7 +331,7 @@ int main(int argc, char *argv[]) unsigned int ptr; outfile_len = ((offset - start +...

Just tried the latest release and found a minor bug. Have a UFD w/ SYSLINUX, which boots a simple .BSS image no problem. Launching exactly the same image on a ISOLINUX disc fails w/ the following error msg: Invalid image type for this media That's it for this msg. Later....Jet -- Powered by Outblaze