search for: aschorr

Hi, On Tue, Nov 12, 2013 at 01:41:29PM -0800, H. Peter Anvin wrote: > On 11/12/2013 01:22 PM, Andrew J. Schorr wrote: > > I am using 4.05 because that's what's packaged in the latest Fedora > > release (Fedora 19 in my case). I wonder why they are using such an > > old version. I will take a look at how difficult it would be to build > > the latest version on

On Tue, Nov 12, 2013 at 5:20 PM, Andrew J. Schorr <aschorr at telemetry-investments.com> wrote: > Hi, > > On Tue, Nov 12, 2013 at 01:41:29PM -0800, H. Peter Anvin wrote: >> On 11/12/2013 01:22 PM, Andrew J. Schorr wrote: >> > I am using 4.05 because that's what's packaged in the latest Fedora >> > release (Fedora...

On 11/14/2013 03:39 AM, Gene Cumm wrote: > On Tue, Nov 12, 2013 at 5:20 PM, Andrew J. Schorr > <aschorr at telemetry-investments.com> wrote: >> Hi, >> >> On Tue, Nov 12, 2013 at 01:41:29PM -0800, H. Peter Anvin wrote: >>> On 11/12/2013 01:22 PM, Andrew J. Schorr wrote: >>>> I am using 4.05 because that's what's packaged in the latest Fedora >>&g...

Hi, This is perhaps a stupid question. I apologize in advance if it's already been covered, but I'm stumped... I'm using rsync to backup some file systems to a remote host. The transport is openssh-2.9.9p2. The problem does not occur when the transport is rsh. I'm invoking rsync as follows: rsync -RlHptgoD --numeric-ids -e "ssh" -rzx --stats .

Hi, Thanks for your help. On Mon, Nov 11, 2013 at 08:00:47PM -0800, H. Peter Anvin wrote: > There is no reason by Syslinux would reboot the system on a serial > disconnect. There could be a bug, of course; now, Syslinux 4.05 is > pretty old so unless you can reproduce this on a current version that > would be useful. I am using 4.05 because that's what's packaged in the

Hi, I hope somebody can help me with this problem. I don't know whether it's a problem with my configuration or a bug or feature in extlinux. I am using an IPMI 2.0 serial-over-lan console to connect to a system with an Intel S3200SHL motherboard. The first line of my extlinux.conf file looks like this: serial 0 57600 0x003 I am using ipmitool to access the console, like so:

Hi, I discovered a very strange situation. I have 22 systems running Fedora 21 (F21) with bundled syslinux-extlinux 6.03. On one of those systems, I am having trouble booting. This machine was upgraded from Fedora 19 (F19), so can boot either the new or the old O/S -- F19 is on one disk partitition, F21 is on another, and there's a shared /boot partition. On this one machine, when I try

Hi, On Fri, Jul 03, 2015 at 06:41:41PM +0300, Ady via Syslinux wrote: > Are the other systems (those that are booting OK) also attached to a serial > console? Yes. > Is there any other output method available (I mean, other than the serial console)? I can also attach a VGA display to the system, but the serial console output is nice because it's logged. > What happens when

Hi, On Fri, Jul 03, 2015 at 07:13:18AM +0300, Ady via Syslinux wrote: > It is not so clear to me which version of Syslinux (or which version of its > Fedora's packages) you are actually using to boot these systems (not just the one > currently failing). Sorry I wasn't clear. Fedora 19 was installed on a / and /boot partition. I then installed Fedora 21 on a separate /

Hi, I don't want to start another --files-from war, but I am attaching an updated version of my patch to allow you to specify a list of files to transfer. The normal rsync syntax allows you to specify a list of SRC files to transfer on the command line. This patch adds some new options to allow you to instead supply a file that contains a list of files to transfer. The previous version of