similar to: How to rsync only directories, no files inside ?

Hi, all I migrate a vm from source host to the destination host. I am sure every part is ok for migration. 1 Create the image in the destination and change the user and group. 2 Open TCP socket in the destination host. and I migrate in the source host command line. $ virsh migrate --live --copy-storage-all vmubuntu qemu+ssh://destinationHost/system --verbose But I get the error

Hello all, Do someone know how can I delete files on a rsync server by using a rsync client without using SSH/RSH? Doing a "rsync -avz --stats --port=874 /export/home/user/* destinationhost::TEST" I?m copying files from /export/home/user/* to the 'path' of destinationhost. TEST module have the ?path? directive set to ?/home/user?. My doubt is how can I delete all

On Thu, Sep 12, 2013 at 12:24 AM, Steven Shiau <steven at nchc.org.tw> wrote: > On 2013/9/12 11:55, Steven Shiau wrote: >> >> Deal developers, >> I'd like to follow the thread >> http://www.zytor.com/pipermail/syslinux/2013-April/019761.html >> but change the subject to 'pxelinux 5.10 and memtest86+ 4.20' and >> provide more test cases.

I have an issue to boot iPXE with Syslinux 5.01. However, the same method works for Syslinux 4.06. The error messages I got is (see attached png file): =================================== iPXE 1.0.0+git-20120202.f8840ba-3 -- Open Source Network Boot Firmware -- http://ipxe.org Features: VLAN HTTP iSCSI DNS TFTP AoE SRP BzImage COMBOOT ELF MBOOT PXE PXEXT /syslinux/ipxe.lkn: command not found

Hi, I am trying the simple menu passswd in syslinux 3.11, and it seems that if I set the timeout option, the menu passwd is ignored. For example: ----------- default menu.c32 timeout 70 prompt 0 noescape 1 MENU MARGIN 5 MENU MASTER PASSWD $4$x$03NXHMe7QS0Ukxlkyh684LkWdqY$ label local MENU DEFAULT # MENU HIDE MENU LABEL Local operating system (if available) MENU PASSWD localboot 0 label

Deal developers, I'd like to follow the thread http://www.zytor.com/pipermail/syslinux/2013-April/019761.html but change the subject to 'pxelinux 5.10 and memtest86+ 4.20' and provide more test cases. The pxelinux before version 5, e.g. version 4.06, worked very well with memtest86+ 4.20, all my PXE client machines, including VMWare workstation 9, VirtualBox 4.2, and all the real

On 04/23/2014 09:06 PM, Ady wrote: > Suggestions and patches are surely welcome. Ady, Mine is only suggestion, and for sure I will just follow what Syslinux developers decide. Thanks. Steven. -- Steven Shiau <steven _at_ stevenshiau org> Public Key Server PGP Key ID: 4096R/47CF935C Fingerprint: 0240 1FEB 695D 7112 62F0 8796 11C1 12DA 47CF 935C

command: virsh migrate --live --copy-storage-all vm qemu+ssh://destinationHost/system error : unexpected failure PS log file in the jpg -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20111028/23c5a7bf/attachment.htm> -------------- next part -------------- A non-text attachment was scrubbed...

That doesn't seem like a good reason to keep the old code base alive... we need to reduce our support load. Steven Shiau <steven at nchc.org.tw> wrote: > >On 09/27/2013 02:37 AM, H. Peter Anvin wrote: >> "Big jump" in what way? >Oh, I should not use that strong words... Actually what I meant is the >implementation of EFI support so the file directories in the

After switching to version 6.2, I am having a problem to use chain.c32 to boot a local disk. My settings: ====================== label local MENU LABEL Local operating system in hard drive kernel chain.c32 append hd0 ====================== It gave me "Error: Couldn't read the first disk sector" If I change the settings as ====================== label local MENU LABEL

Hi, Sorry for asking this again if this have been asked. I searched this mailing list but I can not find the confirmed answer. We tried to use syslinux to boot USB flash drive. The problem is, if we put the kernel and initrd in /casper directory, syslinux failed to boot, it showed us: ------------------ Booting error message: SYSLINUX 3.11 Debian-2007-03-12 EBIOS boot: /casper/vmlinuz1 Could not

On Thu, Sep 19, 2013 at 11:59 PM, Steven Shiau <steven at nchc.org.tw> wrote: > > On 09/13/2013 06:36 AM, Gene Cumm wrote: >> I believe this is a result of how/where memtest wants to be loaded. I >> can confirm it's present in 5.11-pre9 but appears resolved for me in >> 6.02-pre16. I should be able to test in Workstation-9.0.2 tomorrow. > Hi Gene, > Were

On 09/25/2013 11:39 PM, Steven Shiau wrote: > > > On 09/24/2013 04:58 AM, Gene Cumm wrote: >> I'm not sure if there will be another 5.xx release or pre-release, >> except possibly more testing with some changes I've made recently for >> lwIP-enabled PXELINUX (lpxelinux.0) > Gene, > Got it. If possible, please have another 5.xx release since 6.x is a big

Dear all, I packaged syslinux 6.03-pre9 on AMD64 Debian Sid, however, the problem is, I have problem to use it for PXE booting (BIOS mode). It always gives me "Failed to load COM32 file vesamenu.c32". I am sure all the settings are correct because if I switch to the prebuilt syslinux downloaded from

On Wed, Apr 23, 2014 at 7:49 AM, Steven Shiau <steven at nchc.org.tw> wrote: > On 04/23/2014 06:12 PM, Gene Cumm wrote: >> Currently, the linker drops text strings into hdt.c32 specifying its >> dependencies and the Syslinux core hunts for those. It would be a change of >> the Makefiles and the list of filename suffixes to attempt which is already >>

First I would like to say thank you to HPA for providing some really nice features in recently syslinux version. About new functions, actually I have another radical idea, since we are in Asia, most of the users here they would like to see some local fonts for the syslinux/pxelinux menu. I am wondering is that possible, in the future, the syslinux/pxelinux menu can support CJK fonts or icon ?

/sudo/pseudo code/ On Wednesday, April 23, 2014 9:32 AM, Don Cupp <doncuppjr at yahoo.com> wrote: I actually propose another strategy that may kills many birds with one stone. I think it should be able to be handled internally. Right now, we take a kernel argument as a literal file name hdt.c32 really mean load file hdt.c32. That great, it works, that is how most config files are written.

On 03/08/2014 10:06 PM, Gene Cumm wrote: >> Hi Gene, >> > Thanks. As you suggested, I did a test about 6.03-pre6, and I still got >> > the same issue. My client machine >> > still only shows: >> > ==================== >> > Getting cached packets >> > My IP is 192.168.120.1 >> > ==================== >> > The syslog log

On 09/26/2013 01:44 AM, Jeffrey Hutzelman wrote: > Yes; you can configure your DHCP server to hand out different values for > the pxelinux.configfile option to specific clients, matching on MAC > address or a variety of other conditions. Of course, this means that > the config file for that machine will need to know what firmware to > expect and thus what path to set. Hi Jeffrey,

On 09/26/2013 02:02 PM, Jeffrey Hutzelman wrote: > > Right; you've asked for a feature that doesn't exist. I've given you an > alternative approach you can use with your existing DHCP server that > does not require any new features in Syslinux > It wouldn't be too hard to implement, just a matter of someone finding the time. -hpa