search for: iso9660

...//www.syslinux.org/commit/5de463f724da515fd6c5ea49ded6dde178362181 > Author: Thomas Schmitt <scdbackup at gmx.net> > AuthorDate: Thu, 4 Apr 2013 20:02:37 +0200 > Committer: Matt Fleming <matt.fleming at intel.com> > CommitDate: Thu, 25 Apr 2013 14:59:08 +0100 > > iso9660.c did not copy terminating 0 of Rock Ridge name > > I noticed that the trailing 0-byte is not copied to the result of > iso_readdir(). The function iso_convert_name() does append a trailing 0. > > --- > core/fs/iso9660/iso9660.c | 2 +- > 1 file changed, 1 insertion(+), 1 de...

...e Rock Ridge info as perceived by the library. 50 ISO images tested. Some bugs repaired. Now they are in sync. (The macro case Isolinux_rockridge_in_libisofS in susp_rr.c can later be removed, when no further tests in libisofs are expected.) Most of the code is in two new source files: core/fs/iso9660/susp_rr.h ~ 4000 bytes core/fs/iso9660/susp_rr.c ~ 15000 bytes Opinions regarding coding style and license are welcome. I inserted two calls of susp_rr_get_nm() into iso9660/iso9660.c, so that hopefully Rock Ridge names will be processed in functions iso_find_entry() and iso_readdir(). The o...

Compile issue with tools/libfsimage/iso9660 char vs unsigned char signedness causes a warning when compiling iso9660 (xen-unstable). This patch changes the unsigned char * for char *. Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> diff -r 8eff89a69521 tools/libfsimage/iso9660/fsys_iso9660.c --- a/tools/libfsimage/is...

> > http://en.wikipedia.org/wiki/SYSLINUX#List > > The original SYSLINUX, used for booting from FAT<http://en.wikipedia.org/wiki/File_Allocation_Table>and > NTFS <http://en.wikipedia.org/wiki/NTFS> filesystems (such as floppy > disks and USB drives). > I have a question generated from the above wikipedia explanation. Is it possible for the latest version of

Greetings, I wonder whether there are any plans to build udflinux or the likes. I've searched through the mailing list, finding out that should I create a mixed ISO9660/UDF filesystem. Unfortunately, that is not an option if I want to use a significant feature of UDF filesystem, which is writing. Making a mixed ISO9660/UDF, using mkisofs -udf, will (to my best knowledge) not allow me to perform any writing. Creating the UDF filesystem using mkudffs does, howev...

.../dev/mapper/VolGroup00-LogVol00 / ext3 rw 0 0 none /proc proc rw 0 0 none /sys sysfs rw 0 0 none /dev/pts devpts rw,gid=5,mode=620 0 0 usbfs /proc/bus/usb usbfs rw 0 0 /dev/sda1 /boot ext3 rw 0 0 none /dev/shm tmpfs rw 0 0 none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0 /dev/hdc /media/cdrecorder iso9660 ro,nosuid,nodev,user=froggy 0 0 How do I change /dev/hdc /media/cdrecorder iso9660 ro to rw? $ cat /etc/fstab # This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/VolGroup00/LogVol00 / ext3 defaults 1 1 LABEL=/boot /boot...

The attached patch adds iso9660 detection support to fstype. Signed-off-by: David H?rdeman <david at hardeman.nu> -- fstype.c | 17 +++++++++++++++++ iso9660_sb.h | 24 ++++++++++++++++++++++++ 2 files changed, 41 insertions(+) -------------- next part -------------- diff -Nru klibc/usr/kinit/fstype/fstype.c k...

On Wed, 2007-02-21 at 14:46 +0000, Xen staging patchbot-unstable wrote: > # HG changeset patch > # User john.levon@xxx > # Date 1172012044 28800 > # Node ID fe3e024e38f8323c311fbd61710eff3c4b92f514 > # Parent bca284f67702cf46502809f29eb634e2ab6d294f > Add iso9660 support to libfsimage. There seems to be some sign-age problems introduced here. I''m surprised the staging tests didn''t hit them too. On ia64 it fails to build: gcc -DPIC -O2 -fomit-frame-pointer -DNDEBUG -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration...

...flows for free. I think this is the safer patch of the three. Signed-off-by: Frediano Ziglio <frediano.ziglio at citrix.com> --- core/fs/diskio.c | 80 +++++++++++++++++++++++++++++++++++++++++++-- core/fs/ext2/ext2.c | 2 +- core/fs/fat/fat.c | 2 +- core/fs/iso9660/iso9660.c | 8 ++-- core/fs/ntfs/ntfs.c | 4 +- core/include/disk.h | 2 + 6 files changed, 87 insertions(+), 11 deletions(-) diff --git a/core/fs/diskio.c b/core/fs/diskio.c index 6683816..7e58d6f 100644 --- a/core/fs/diskio.c +++ b/core/fs/diskio.c @@ -265,6 +265,80 @@ stati...

...ude/syslinux/sysappend.h | 1 + core/fs/btrfs/btrfs.c | 3 ++- core/fs/ext2/ext2.c | 1 + core/fs/fat/fat.c | 31 +++++++++++++++++++++++++++++++ core/fs/fat/fat_fs.h | 2 ++ core/fs/fs.c | 12 ++++++++++++ core/fs/iso9660/iso9660.c | 1 + core/fs/ntfs/ntfs.c | 1 + core/fs/pxe/pxe.c | 1 + core/fs/xfs/xfs.c | 1 + core/include/core.h | 1 + core/include/fs.h | 4 ++++ core/sysappend.c | 17 ++++++++++++++...

...sig, char **data, int *len_data); The function and its subordinates already have more than 300 lines, i fear. And still some necessary features are missing. Some open questions: How do i check for success or failure of get_cache() ? Shall the new code become part of iso9660/iso9660.c or shall i start a new source file iso9660/susp.c ? Would it be ok to extend struct iso_sb_info ? (I should implement non-zero skip length that might be defined by the SUSP SP entry. Probably i find more use for global-ish parameters.) Have a nice day :) Thomas

...g its start and end sectors, so this could be done to be equal to the initial MBR partition generated by IsoHybrid, so there would not be duplicated files (kernel, initram and syslinus.cfg). Is that possible, currently or with some patches on isohybrid command? In what situations it would not work (iso9660 can be seen as a read-only FAT filesystem)? Also, could it be used directly the same MBR entry just by setting the partition entry flags or with some other minor tune-ups? -- "Si quieres viajar alrededor del mundo y ser invitado a hablar en un monton de sitios diferentes, simplemente escri...

I'm wondering if it's possible to use isolinux on a bootable CDR to boot an ISO9660 disk image off of the CDR's filesystem. I'm trying to make a multi-boot CD which is capable of booting both floppy images and smaller ISO9660 images (such as the debian netinst or DSL - damnsmall linux), and I am wondering if isolinux is capable of doing this (or something similar to thi...

...syslinux.efi can be used for booting > from ISO 9660 via UEFI. Currently there is no example > around which would succeed without GRUB or GRUB2. I don't know how many times I have to express this and in how many different ways: 'syslinux.efi v.6.03 cannot be used for booting from ISO9660 via UEFI. Can 'syslinux.efi' be included in an isohybrid image? Yes, for example as 'EFI/BOOT/BOOTX64.EFI'. Can such isohybrid image be burned to optical media? Yes. Can such optical media boot a BIOS system? Yes, for example if 'isolinux.bin' was used as bootloader wh...

Hi, i cannot yet see my most recent bug fix patch applied to http://git.kernel.org/cgit/boot/syslinux/syslinux.git/log/?h=rockridge The fixed problem could lead to memory faults. http://www.syslinux.org/archives/2013-April/019790.html Have a nice day :) Thomas

...need to use its on-board tools for accessing files on it while mounted on Centos 6.5, and those tools assume uppercawse, since they assume the entire world runs Windoze.) but despite my best efforts, it keeps being mounted with UC-LC mapping enabled. here's what I've been trying: mount -t iso9660 -o norock,remount,ro,nosuid,nodev,uhelper=udisks,uid=500,gid=500,iocharset=utfi,mode=0400,dmode=0500 /dev/sr0 /mnt/cd and even this: umount /mnt/cd mount -t iso9660 -o norock,ro,nosuid,nodev,uhelper=udisks,uid=500,gid=500,iocharset=utfi,mode=0400,dmode=0500 /dev/sr0 /mnt/cd I've also tried u...

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.efi for booting from the local HDD of a UEFI...

> 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...

...2010-02-08 10:31:44.000000000 +0100 @@ -46,15 +46,9 @@ cobbler distro add --name="oVirt-Node-$node_arch" --arch=$node_arch \ --initrd=$node_dir/tftpboot/initrd0.img -- kernel=$node_dir/tftpboot/vmlinuz0 \ - --kopts="rootflags=loop root=/ovirt-node-image.iso rootfstype=iso9660 ro console=tty0 console=ttyS0,115200n8" + --kopts="rootflags=loop root=live:/ovirt-node-image.iso rootfstype=iso9660 ro console=tty0 console=ttyS0,115200n8" I didn't try this patch but I think this is the way to get this kind of config in /var/lib/tftpboot/pxelinux.cfg/de...

...tramfs to deal with the .iso in the vfat filesystem. What would be ideal, and what I would *really like*, is if sys/isolinux would support referencing kernels and initrds that live *within* a .iso image, that is either residing on a vfat fs on a usbstick, or a .iso image that is residing in the iso9660 filesystem of the cdrom boot media. One perhaps controversial use-case of this, would be to take a Fedora LiveCD iso image, and redistribute it *intact and unmodified* inside another iso9660 filesystem, along with custom modifications, and a bootloader that can *efficiently* utilize the kernel...