search for: lfn

...rtual floppy, or else you have to synthesize the same set of > operations that syslinux performs. Also you have to deal with CHS > geometry. > --- > configure.ac | 2 + > plugins/floppy/Makefile.am | 68 ++ > plugins/floppy/directory-lfn.c | 623 ++++++++++++++++++ > plugins/floppy/floppy.c | 198 ++++++ > plugins/floppy/nbdkit-floppy-plugin.pod | 87 +++ > plugins/floppy/virtual-floppy.c | 797 ++++++++++++++++++++++++ > plugins/floppy/virtual-floppy.h | 233 +++++++ >...

Add nbdkit-floppy-plugin, “inspired” by qemu's VVFAT driver, but without the ability to handle writes. The implementation is pretty complete, supporting FAT32, LFNs, volume labels, timestamps, etc, and it passes both ‘make check’ and ‘make check-valgrind’. Usage is simple; to serve the current directory: $ nbdkit floppy . Then using guestfish (or any NBD client): $ guestfish --ro --format=raw -a nbd://localhost -m /dev/sda1 Welcome to guestfish, the guest...

...un the syslinux command on the virtual floppy, or else you have to synthesize the same set of operations that syslinux performs. Also you have to deal with CHS geometry. --- configure.ac | 2 + plugins/floppy/Makefile.am | 68 ++ plugins/floppy/directory-lfn.c | 623 ++++++++++++++++++ plugins/floppy/floppy.c | 198 ++++++ plugins/floppy/nbdkit-floppy-plugin.pod | 87 +++ plugins/floppy/virtual-floppy.c | 797 ++++++++++++++++++++++++ plugins/floppy/virtual-floppy.h | 233 +++++++ plugins/iso/nbdkit-iso-plugin....

On Tue, Oct 30, 2018 at 09:12:55AM -0500, Eric Blake wrote: > >+/* Used for dealing with VFAT LFNs when creating a directory. */ > >+struct lfn { > >+ const char *name; /* Original Unix filename. */ > >+ char short_base[8]; /* Short basename. */ > >+ char short_ext[3]; /* Short file extension. */ > >+ char *lfn;...

...ocated strings or a list of constant strings. Define either string_vector or const_string_vector as appropriate and use it to store these lists. --- plugins/iso/Makefile.am | 1 + plugins/split/Makefile.am | 1 + plugins/floppy/virtual-floppy.h | 7 +++-- plugins/floppy/directory-lfn.c | 35 +++++++++------------- plugins/floppy/virtual-floppy.c | 11 +++---- plugins/iso/iso.c | 25 ++++++---------- plugins/split/split.c | 51 +++++++++++++++------------------ plugins/ssh/ssh.c | 24 +++++++--------- 8 files changed, 69 insertions(+), 86 d...

This is a fsck log of my computer ,everytime when boot the system show this things, what's the problem? And how can I cancel it when system boot? Log of fsck -C -R -A -a Sun Oct 14 21:00:34 2007 fsck 1.40.2 (12-Jul-2007) dosfsck 2.11, 12 Mar 2005, FAT32, LFN /dev/hdb1: 18222 files, 425355/1053230 clusters dosfsck 2.11, 12 Mar 2005, FAT32, LFN /dev/hdb10: 22 files, 571488/1248831 clusters dosfsck 2.11, 12 Mar 2005, FAT32, LFN There are differences between boot sector and its backup. Differences: (offset:original/backup) 5:44/57, 6:4f/49, 7:53/4e, 8:35...

...;t longer than the old 8.3 dos convention. This is a requirement for a system behind it, which can only deal with old dos 8.3 dir/filename conventions. I tried to save to a fat16 partition type, but this vfat driver accepts long filenames instead. Searching for special mount options limiting the lfn functionality ended without any result. Maybe there is a solution for this problem, so hopefully someone here has an idea for this. Michael

...rder, whether the directory paths are > mangled as a common user would expect, and so on. You might think all > this is trivial, but this is how I have found and reported several bugs > in the past. > > I purposely test SYSLINUX under an environment without long file name > (LFN) support under DOS, among other cases. > > Another case: When building an ISO image, the resulting file name > resolution might depend on the specific options that were used in > mkisofs (or similar). The file name support in ISO9660 Level 1 is > limited, in a very similar way a...

On Fri, Sep 18, 2015 at 02:01:32PM +0300, Ady via Syslinux wrote: > > > > We have pxechn.c32 working with pxelinux.0 to switch between the two > > system, but pxechn.c32 under Uefi come up with the folowing error > > > @Developers, please consider using 8.3 file names format for c32 files > instead of such a long file name. Example of such a long file name? So

This was a rather longer trip around the houses than I anticipated! The basic purpose of the patch series is to set $nbdkit_stdio_safe to "0" or "1" in sh and eval plugin scripts. To do that, I ended up adding a nicer way to manipulate environ lists, and to do that, I ended up adding a whole generic vector implementation which is applicable in a lot of different places.

...should and in the documented order, whether the directory paths are mangled as a common user would expect, and so on. You might think all this is trivial, but this is how I have found and reported several bugs in the past. I purposely test SYSLINUX under an environment without long file name (LFN) support under DOS, among other cases. Another case: When building an ISO image, the resulting file name resolution might depend on the specific options that were used in mkisofs (or similar). The file name support in ISO9660 Level 1 is limited, in a very similar way as the "DOS 8.3"...

> >>> > > > > I have sent in the past two patches; one allows SL to chainload to efi > > executives and the other one > > allows to link the gnu-efi layer to a com32 module in order to access the > > EFI firmware from the com32 code. > > Despite minor changes I might've made during all this time that code > > works... > > Do you

I have a small home network running three Win95 pcs with a Samba/Linux server (thanks, Andrew and Linus!!!). All works well. The question now is what I can do to make a full system backup (including hidden and system files) from the Win95 boxes to the 8mm tape drive on the Linux box. I know I could use smbmount to mount the Win95 drive, and then do a tar or cpio backup, but I'm not nearly

I'm trying to use this universal DOS TCP/IP boot disk available here: http://members.iinet.net.au/~bdriver/bootdisk/ It requires an MS-DOS formatted disk created by Windows XP. It works great as a floppy but doesn't boot at all with memdisk. The problem can be simplified down to just the XP boot disk. If you make an MS-DOS startup disk with XP on a floppy, dd the floppy to an image

...(lowest two and highest bitrates don't cause it) - I don't think it's my makefiles' fault and maybe it will be gone in newer cvs versions. I'll try and will investigate if it doesn't. I'll also apreciate someone else with DJGPP to report. It needs win9x since it needs LFN (libvorbis{,file,enc} would clush and I was lazy to work around), and 2000 seems to dislike DJGPP in numerous mysterious ways. I've split them by package. For each package I made a patch for the modified files and an archive with the added files. Should be easier that way, since the added fi...

v1 was here: https://www.redhat.com/archives/libguestfs/2019-September/msg00100.html In v2 I've changed the patch so it avoids calling realloc at all in this case. The patch is a bit longer this way. But I don't see any other alternative if we are to avoid having a "realloc wrapper" of some kind that we use everywhere, which I guess we should avoid because it makes plugins

Hi all, I've been thinking about how best to represent MachO's LC_REEXPORT_DYLIB (used even by libSystem.dylib to provide its various sub-components[*]). It looks like this functionality would naturally fall into the InputGraph, in analogy with Groups and Archives. Unfortunately, it's rather more dynamic than the existing cases: we don't know the needed files before parsing the

...hell) the relevant efi boot file (which should be a copy of 'syslinux.efi')? Also, please note that I keep talking about FAT1x, and not a VFAT32 image. For troubleshooting, I would avoid unnecessary long-file-name support in FAT (so, simple FAT, no VFAT, although the UEFI Specs support LFN) and I would suggest using FAT1x as expected by the UEFI Specs for removable media (not FAT32, although in some sections the UEFI Specs use the term "_may_ contain... FAT32" for removable media too; another source of confusion from the long UEFI Specs). As I mentioned before, the fact...

> Hello, > > Gene Cumm said on Thu, Oct 22, 2015 at 06:39:44PM -0400: > >On Thu, Oct 22, 2015 at 1:56 PM, Bruno Cornec via Syslinux > ><syslinux at zytor.com> wrote: > > > >> 3/ Using syslinux.efi in a FAT32 image (similar to the previous 2 > >> confs) stored on a iso9660 media by genisoimage and its > >> -eltorito-alt-boot -efi-boot

...ort and SuSE 10.2. Did anyone observe anything similar with any USB flash drives (FAT OK, ext3 corrupted)? I've put files on these disks on FAT32 and run fsck.vfat, and everything looks fine: root at tarnica:~# dosfsck -v /dev/sda1 dosfsck 2.11 (12 Mar 2005) dosfsck 2.11, 12 Mar 2005, FAT32, LFN Checking we can access the last sector of the filesystem Boot sector contents: System ID "mkdosfs" Media byte 0xf8 (hard disk) 512 bytes per logical sector 4096 bytes per cluster 32 reserved sectors First FAT starts at byte 16384 (sector 32) 2 FATs, 32 bit en...