similar to: rsync {options} -- {arguments}

Displaying 20 results from an estimated 100 matches similar to: "rsync {options} -- {arguments}"

2009 Dec 20
2
ogg "chapters"?
i'm thinking about albums like "dark side of the moon" and also live bands (especially live-pa) and DJs where there's a continuous flow from one song to the next... i could use a MKV file with vorbis or mp3 and include a chapter listing [with named chapters], that would allow listening to the whole thing with no skipping between songs. at the same time, a listener can skip
2013 Jun 28
2
pxelinux 5.x, 6.x memtest problem
Hello, FYI. This problem looks similar to the problem I reported in Februari http://www.syslinux.org/archives/2013-February/019517.html Kind regards, Wim. On 06/28/2013 10:02 AM, Matt Fleming wrote: > On Fri, 28 Jun, at 08:13:03AM, N?meth P?ter wrote: >> Hi guys! >> I tried to boot memtest86+ v4.2 (renamed memtest.bin to memtest), and >> i have issues to boot it with
2016 Aug 17
5
AutoFDO sample profiles v. SelectInst,
On Fri, Aug 12, 2016 at 12:15 PM, Xinliang David Li via llvm-dev < llvm-dev at lists.llvm.org> wrote: > +dehao. > > There are two potential problems: > > 1) the branch gets eliminated in the binary that is being profiled, so > there is no profile data > This seems like a fundamental problem for PGO. Maybe it is also responsible for this bug:
2013 Jun 28
3
pxelinux 5.x, 6.x memtest problem
Hi guys! I tried to boot memtest86+ v4.2 (renamed memtest.bin to memtest), and i have issues to boot it with pxelinux 5.x and greater.Pxelinux 4.06 works fine both memtest 4.1 and 4.2. With version 6.00 no error message caught, only writes out dots. Any keypress does a reboot.With version 5.01 the error message is the follow:Loading images/memtest/memtest86... okBooting kernel failed: Bad file
2013 Jun 29
3
Plop Boot Manager quit working with 5.10
> On 06/28/2013 05:32 PM, Patrick Verner wrote: > > I have updated syslinux in Parted Magic's test version to the 5.10 release. > > With 4.06 I booted plop like this: > > > > LINUX /boot/plpbt/plpbt.bin > > > > Now it says /boot/plpbt/plpbt.bin... ok > > Booting kernel failed: Invalid argument > > > > Other "extras" like
2003 Sep 05
1
rsync // su
Hi, Please send questions to the list, not to me. On 4 Sep 2003 Atom 'Smasher' <atom@suspicious.org> wrote: > i've been trying to find a good answer for this, but pretty much all > i've found is disagreement on what level of insecurity is > acceptable.... > > the problem arises when trying to use rsync as root. > > obviously, allowing root logins
2013 Apr 22
2
libvirt tls error
centos6.3,libvirt 0.9.10. [root at ovirtdev private]# virsh -c qemu+tls://ovirtdev.localhost/system list 2013-04-22 03:37:09.362+0000: 9898: info : libvirt version: 0.9.10, package: 21.el6_3.8 (CentOS BuildSystem <http://bugs.centos.org>, 2013-01-28-19:24:16, c6b10.bsys.dev.centos.org) 2013-04-22 03:37:09.362+0000: 9898: warning : virNetClientIncomingEvent:1665 : Something went wrong during
2016 Aug 12
3
AutoFDO sample profiles v. SelectInst,
I am looking for advice on a problem observed with -fprofile-sample-use for samples built with the AutoFDO tool I took the "hmmer" benchmark out of SPEC2006 It is initially compiled clnag++ -o hmmer -O3 -std=gnu89 -DSPEC_CPU -DNDEBUG -fno-strict-aliasing -w -g *.c This baseline binary runs in about 164.2 seconds as reported by "perf stat" We build a sample file from this
2013 Jun 28
0
pxelinux 5.x, 6.x memtest problem
> Hello, > > FYI. This problem looks similar to the problem I reported in Februari > http://www.syslinux.org/archives/2013-February/019517.html > > Kind regards, > Wim. > > On 06/28/2013 10:02 AM, Matt Fleming wrote: > > On Fri, 28 Jun, at 08:13:03AM, N?meth P?ter wrote: > >> Hi guys! > >> I tried to boot memtest86+ v4.2 (renamed memtest.bin to
2013 Jun 28
1
pxelinux 5.x, 6.x memtest problem
On 06/28/2013 04:25 AM, Ady wrote: > > @Wim and @All, > FWIW, in 2013-February there still were other additional issues with > some kernels, including memory testers, so having a problem to boot > memtest(86|86+|other) might or might not be related to the > "PXE-stack-smasher" bug. > > For example, in v.4.06, the cfg entry could be: > LINUX memtest >
2012 Oct 14
0
need help with passthrough of intel igp
Hello. It is update of my previous message. I''ve checked that I can passthrough discrete graphic card, but when I try use in IGP (without discrete card in the slot) linux come to desktop without usage in inteldmr driver indeed. Dmesg show that I have some problem with ioremap. Is someone tried do pci/vga passthrough of integrated graphic or know way to solve that problem? Best regards.
2013 May 28
0
Re: libvirt tls error
On Mon, Apr 22, 2013 at 12:03:43PM +0800, yue wrote: > centos6.3,libvirt 0.9.10. > [root@ovirtdev private]# virsh -c qemu+tls://ovirtdev.localhost/system list > 2013-04-22 03:37:09.362+0000: 9898: info : libvirt version: 0.9.10, package: 21.el6_3.8 (CentOS BuildSystem <http://bugs.centos.org>, 2013-01-28-19:24:16, c6b10.bsys.dev.centos.org) > 2013-04-22 03:37:09.362+0000: 9898:
2014 Jul 12
1
Virtualbox on CentOS 7
Hi there, because I just noticed that there is still no RPM package for RHEL 7/ CentOS 7 for Virtualbox .... what is the safest and cleanest way to install Virtualbox on CentOS 7? Has anyone already done and can make a recommendation? Thanks & Regards, Matthias -- Matthias Petermann <matthias at petermann-it.de> | www.petermann-it.de GnuPG: 0x5C3E6D75 | 5930 86EF 7965 2BBA 6572
2016 Mar 09
4
Setting up public mailboxes - user not found
Hi all, This is the first time I use the dovecot mail list so I?m sorry if I forget something. My problem is that for some reason I can get public mailboxes to work. I have setup the directory Public, the folders and the cur,tmp and new folder in them: Public | |- .office3 | |- cur |- tmp |- new |- dovecot-acl Here is my dovecot conf: # 2.2.13: /etc/dovecot/dovecot.conf # OS:
2013 Apr 19
0
Unexplained shutdown of VM on upgrade of libvirt package
I am running KVM on Centos 6.3 and am seeing an unexplained shut down of two guests. The libvirt package was upgraded to libvirt-0.10.2-18.el6_4.4.x86_64 at the time of the shutdown. Only the two guests shown below was affected, while 9 others running on the same hypervisor were not. Can some one help me to find the cause please ? Regards Chandana GUEST #1 ======== 2013-04-10
2013 Jun 28
0
pxelinux 5.x, 6.x memtest problem
On Fri, 28 Jun, at 08:13:03AM, N?meth P?ter wrote: > Hi guys! > I tried to boot memtest86+ v4.2 (renamed memtest.bin to memtest), and > i have issues to boot it with pxelinux 5.x and greater.Pxelinux 4.06 > works fine both memtest 4.1 and 4.2. > With version 6.00 no error message caught, only writes out dots. Any > keypress does a reboot.With version 5.01 the error message is the
2013 Jun 30
0
Plop Boot Manager quit working with 5.10
On Sat, Jun 29, 2013 at 3:04 PM, Ady <ady-sf at hotmail.com> wrote: > If with "ancient kernel" you are referring to the memtest(86|86+) > issue, I don't see the same *exact* problem / behavior. My cuent understanding is as follows: HPA is using the label "ancient kernel" for any kernel that has a hard-coded load address and that linux.c32 and all 5.xx+
2013 Jun 28
2
FW: pxelinux 5.x, 6.x memtest problem
Additional information: I was tried it with 2 virtualbox (version 4.2.14r86644).1rst: debian weezy with isc-dhcp-server, pxelinux5.01, pxelinux 6.00, tftp-hpa2nd: empty virtualbox booting from virtual network card. So memtest 4.1 and 4.2 worked with pxelinux 4.06 Peter > Date: Fri, 28 Jun 2013 09:02:30 +0100 > From: matt at console-pimps.org > To: coolpet80 at hotmail.com > CC:
2017 Feb 07
2
[Bug 12570] New: Problems with --checksum --existing
https://bugzilla.samba.org/show_bug.cgi?id=12570 Bug ID: 12570 Summary: Problems with --checksum --existing Product: rsync Version: 3.1.1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter: atom at
2013 Jun 30
1
Plop Boot Manager quit working with 5.10
> On Sat, Jun 29, 2013 at 3:04 PM, Ady <ady-sf at hotmail.com> wrote: > > > If with "ancient kernel" you are referring to the memtest(86|86+) > > issue, I don't see the same *exact* problem / behavior. > > My cuent understanding is as follows: HPA is using the label "ancient > kernel" for any kernel that has a hard-coded load address and