search for: _copying_

Hi everbody! I'm currently working in a project which has to copy huge amounts of data from one storage to another. For a reason I cannot validate any longer, there is a roumor that "rsync may silently corrupt data". Personally, I don't believe that. "They" explain it this way: "rsync does an in-stream data deduplication. It creates a checksum for each data block

...ry_modules Or, simply, copy over all the c32 files from the relevant architecture the same build. Sometimes symlinks have been reported also as a problem. Whether this is a "user-related" problem or a really technical (file system related) one, I don't know. Therefore, I suggest _copying_ the whole set of c32 files for troubleshooting purposes. > > > > These are the reasons for a frequent request: add some kind of > > "version" ID to each and all c32 files in some "standard" way. > > Seconded! ;-) > > Also, an e32 or e64 extens...

> > For a KISS troubleshooting, *all* the c32 files should be located > together, in the root of the filesystem, where syslinux.efi and > ldlinux.e64 (for EFI x86_64) should be located too. > I should clarify, just in case. In my previous email, when I mentioned "all" the c32 files, I actually meant all the c32 files that pertain to the adequate firmware's

...9;ing_ the ISO image to it, then isohybrid would be a factor. But we are before that point. If we cannot boot optical media in UEFI mode with Syslinux, then we won't be able to achieve the "dd'ing" part in any meaningful way. As I wrote in my original email back in last April, _copying_ the content of the ISO image (not dd'ing) *can* achieve the goal of booting from storage media. We are not discussing such method either. So, for now, I am suggesting not to use isohybrid, and certainly not to use MBR as part of the UEFI-required FAT image. > > >For troubleshoot...

> 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