similar to: FW: Error code 23, delete failed, error 0

Displaying 20 results from an estimated 10000 matches similar to: "FW: Error code 23, delete failed, error 0"

2008 Jan 30
2
--partial replaces destination file on interrupted transfer
I had a case where I was using the --partial option (client is running rsync-pre5, server daemon is rsync-pre8). The transfer was interrupted and the partially transferred file replaced the destination file on the server. My understanding is that the partially transferred file would be kept but it would not replace the destination file...that is, both files would be kept so that rsync could pick
2005 Sep 13
2
Fw: Issue with pxelinux
I've been working with Matt Burgess here on this problem, and have found the following: syslinux 3.08-pre10 ? broken >>> config.inc:max_cmd_len=255 syslinux 3.08-pre11 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.08 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre1 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre2 ? broken
2013 Jul 19
2
FW: pxelinux 5.x, 6.x memtest problem
Hi, 6.02-pre8 still doesn't work. Same error. Nothing happens, no menu. Did you change something on the build system between pre5 and pre6? -- Regards, Igor
2013 Jul 19
3
FW: pxelinux 5.x, 6.x memtest problem
Hi, > What steps are you using to recompile the releases? Are you working from > git? No, not git. See http://www.syslinux.org/archives/2013-July/020543.html and the f'up from Ady and my response regarding re-compiling. So actual I think I don't re-compile everything. I think I am using the pre-build modules from your provided archives (if 'make installer && make
2013 Jul 11
0
LDFLAGS and distro overrides
Hi, Matt Fleming: > This just came up on IRC, > > 15:01 < chithead> the first one that fails is ld -m elf_i386 -Wl,-O1 -Wl,--as-needed -Bsymbolic -pie -E --hash-style=gnu -T /var/tmp/portage/sys-boot/syslinux-6.01_pre5/work/syslinux-6.01-pre5/core/i386/syslinux.ld -M -o ldlinux.elf ldlinux.o \ > 15:01 < chithead> --start-group libcom32.a --whole-archive
2013 Jul 19
0
FW: pxelinux 5.x, 6.x memtest problem
On Fri, 19 Jul, at 03:59:09PM, Igor Sverkos wrote: > Hi, > > > What steps are you using to recompile the releases? Are you working from > > git? > > No, not git. OK, could you try 6.02-pre8? It contains a revert of the single commit that exists between 6.02-pre5 and 6.02-pre6. -- Matt Fleming, Intel Open Source Technology Center
2013 Jul 22
0
FW: pxelinux 5.x, 6.x memtest problem
On Fri, 19 Jul, at 07:49:06PM, Igor Sverkos wrote: > Hi, > > 6.02-pre8 still doesn't work. Same error. Nothing happens, no menu. > > Did you change something on the build system between pre5 and pre6? Not intentionally and I looked through the logs on the build machine to see if anything relevant was upgraded before I did the revert. The files are not being corrupted by the
2005 Aug 09
8
SYSLINUX 3.10-pre* testing
Hi! as i know that you like test reports, here are some... Testing environment: CompactFlash card, connected with an USB adapter to a Compaq Evo D310 frontal USB port. This machine boots via USB quite well with syslinux. 3.09 boots ok, no problem 3.10-pre2 does not boot 3.10-pre3 does not boot 3.10-pre4 does not boot 3.10-pre5 locks up pc 3.10-pre6 locks up pc 3.10-pre7 writes
2013 Jul 19
2
FW: pxelinux 5.x, 6.x memtest problem
Hi, > Are you positive that the menu works with 6.02-pre5? There are two > changes between 6.02-pre5 and 6.02-pre6 and those two commits are > unlikely to have caused any regressions. Yep, I very sure. I compiled 6.02-pre6 again (made sure, that I really copy the files from 6.02-pre6 to the tftp-host) and this isn't working. Now menu will appear. I re-compiled 6.02-pre5 again
2013 Jul 19
0
FW: pxelinux 5.x, 6.x memtest problem
On Fri, 19 Jul, at 02:50:25PM, Igor Sverkos wrote: > Hi, > > > Are you positive that the menu works with 6.02-pre5? There are two > > changes between 6.02-pre5 and 6.02-pre6 and those two commits are > > unlikely to have caused any regressions. > > Yep, I very sure. > > I compiled 6.02-pre6 again (made sure, that I really copy the files > from 6.02-pre6 to
2002 Jul 08
0
(no subject)
Which version should I use out of the list? Or do I install all of them, one after the other? ext3-2.4-0.9.9-2410p4.gz 05Sep01 (Against 2.4.10-pre4) (Changelog) ext3-2.4-0.9.9-249ac9.gz 05Sep01 (Against 2.4.9-ac9) ext3-2.4-0.9.10-2410.gz 23Sep01 (Against 2.4.10) (Changelog) patch-rml-2.4.10-ac3-ext3-0.9.9-with-dir-speedup-1.gz 01Oct01 (From Robert Love. Unofficial :-))
2002 Jul 11
1
(no subject)
Which version should I use out of the list? Or do I install all of them, one after the other? ext3-2.4-0.9.9-2410p4.gz 05Sep01 (Against 2.4.10-pre4) (Changelog) ext3-2.4-0.9.9-249ac9.gz 05Sep01 (Against 2.4.9-ac9) ext3-2.4-0.9.10-2410.gz 23Sep01 (Against 2.4.10) (Changelog) patch-rml-2.4.10-ac3-ext3-0.9.9-with-dir-speedup-1.gz 01Oct01 (From Robert Love. Unofficial :-))
2013 Jul 02
2
LDFLAGS and distro overrides
This just came up on IRC, 15:01 < chithead> the first one that fails is ld -m elf_i386 -Wl,-O1 -Wl,--as-needed -Bsymbolic -pie -E --hash-style=gnu -T /var/tmp/portage/sys-boot/syslinux-6.01_pre5/work/syslinux-6.01-pre5/core/i386/syslinux.ld -M -o ldlinux.elf ldlinux.o \ 15:01 < chithead> --start-group libcom32.a --whole-archive
2013 Jul 19
0
FW: pxelinux 5.x, 6.x memtest problem
On Fri, 19 Jul, at 12:25:11PM, Igor Sverkos wrote: > Hi, > > - syslinux-6.01-pre6 -> Working > - syslinux-6.02-pre5 -> Working > - syslinux-6.02-pre6 -> NOT WORKING Are you positive that the menu works with 6.02-pre5? There are two changes between 6.02-pre5 and 6.02-pre6 and those two commits are unlikely to have caused any regressions. -- Matt Fleming, Intel Open
2013 Jul 19
2
FW: pxelinux 5.x, 6.x memtest problem
Hi, - syslinux-6.01-pre6 -> Working - syslinux-6.02-pre5 -> Working - syslinux-6.02-pre6 -> NOT WORKING With working I mean that I get my expected menu and I am able to boot systemrescuecd. Memtest doesn't boot on any mentioned versions. Please tell me how I can help you debugging memtest or if you need anything else. -- Regards, Igor
2007 Feb 06
3
Syslinux: Broken file reading for fat16 with 3.35+?
Hello, I noticed after upgrading from 3.20, I haven't been able to get syslinux to boot properly with menu.c32 or mboot.c32 from a USB key. I get an error saying invalid kernel when its trying to load menu.c32 or mboot.c32 (or any other kernel for that matter). I tried 3.35 and 3.36-pre5. Same exact behaviour. I'm using the following to compile: gcc version 3.2.3 20030502 (Red Hat Linux
2008 Jan 24
1
Rsync iconv (Cygwin) (file has vanished)
I have another question. I'm not sure if this is the correct post for cygwin rsync related questions. I've compiled rsync 3.0.0pre8 under cygwin. Works splendidly and compiles cleanly. I made sure to have libiconv installed and it supports the --iconv command (at least it accepts it). I've been using rsync to test a backup of some files from a windows box to a linux box. I use
2013 Jun 28
2
FW: pxelinux 5.x, 6.x memtest problem
On Fri, Jun 28, 2013 at 10:13 AM, Ady <ady-sf at hotmail.com> wrote: > But, in Syslinux 4.06, there is linux.c32, which is a sort of > introduction to Syslinux 5.xx (please allow me to be not strictly > accurate in this sentence in this context). > > Booting with any variant of Syslinux 4.06, but using linux.c32, > memtest would fail, which indicated some kind of problem
2006 Aug 06
2
File fragmentation
I've been running some tests on files created by rsync and noticing fragmentation issues. I started the testing because our 5TB array started performing very slowly and it appears fragmentation was the culprit. The test I conducted was straighforward: 1. Copy over a 49GB file. Analyzed with contig (from sysinternals), no fragments. 2. Ran rsync and the file was recreated normally (rsync
2013 Jun 28
2
FW: pxelinux 5.x, 6.x memtest problem
On 06/28/2013 04:07 PM, Gene Cumm wrote: > On Fri, Jun 28, 2013 at 12:53 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Fri, Jun 28, 2013 at 10:13 AM, Ady <ady-sf at hotmail.com> wrote: >> >>> But, in Syslinux 4.06, there is linux.c32, which is a sort of >>> introduction to Syslinux 5.xx (please allow me to be not strictly >>> accurate in