similar to: Socket behavior change from 6.5 to 6.6

I have been following these instructions: https://www.centos.org/forums/viewtopic.php?t=501 to put a bunch of utilities (Clonezilla, SystemRescue, CentOS netinstall/rescue, etc.) on a single USB key. It works great for everything (including Ubuntu Live) except the CentOS 6.4 LiveCD. (You can see my postings at the bottom of the forum.) When booting the LiveCD, I got: Kernel panic - not syncing:

Quick question that I haven't been able to find the answer to (and not for lack of trying, believe me): Is dual-monitor display for the new Intel HD Graphics 4600 (Haswell, e.g. Intel E3-1200v3 family processors) supported in CentOS 6.4? In particular, I'm looking at a SuperMicro X10SAE; SuperMicro has already replied that triple-display only works with a VGA-HDMI-DP combo (lame) and only

So, after some discussion of our new control workstations, we are iterating in on a solution; we are looking at a 1U short-depth SuperMicro SuperServer 5017R-MF with a graphics card in the PCI-Ex16 expansion slot. However, the display requirements have increased to 3 or more monitors for future expansion, so I was wondering whether anyone had any experience with triple- or quad-display single card

A couple more thoughts... On Jan 16, 2015, at 10:42 AM, Warren Young <wyml at etr-usa.com> wrote: > On Jan 15, 2015, at 11:40 AM, Glenn Eychaner <geychaner at mac.com> wrote: > >> When the DOS box exits, crashes, or is rebooted, it fails to shut down the >> socket properly. > > Yes, that?s what happens when you use an OS that doesn?t implement sockets in

So, I have a CentOS 6 system, and I want to make several clones of it. I'm using Clonezilla to clone the drives; that's no problem. But the drive UUIDs are driving me up the wall. After cloning, the two drives have the same UUID, but I'd like each clone to have different UUIDs so there's no possibility of a conflict when I am running diagnostics with two drives installed, etc.

So, just today I noticed a problem with kernel 2.6.18-194 (CentOS 5.5) on several Intel DP965LT systems; the system beeps (such as terminal beeps) are no longer passed through to the external speakers. This is a problem because in our situation the boxes are distant from their monitor/keyboard, the system speaker on this motherboard is extremely weak, and there are no system speaker header pins

So, having returned from a month's vacation, I'm back to work on attempting to build a set of small form factor CentOS compatible computers. I've really tried to do my homework, but this doesn't appear (at first glance) to be at all easy. It's not made easier by the fact that I have to get it right the first time (and I haven't built a PC in a decade); the time and money

All- Ah, the saga of the 1U workstation continues. So, in all my work configuring the thing, I completely forgot about AUDIO; I only realized my mistake when I went on a cable-measuring expedition this morning. Unfortunately, none of the 1U servers I've been looking at come with audio outputs (there aren't even audio headers on the motherboard), and I've used the only availabnle slot

I'm having a puzzling problem with system-config-network-cmd in CentOS 6.4. I have a workstation with a number of different grub boot configurations (a spare for a set of workstations, basically), each of which has a parameter MYHOST=<hostname>, and I am using system-config-network-cmd to set the boot configuration during the network process (using a small custom system service that runs

On Jan 15, 2015, at 11:40 AM, Glenn Eychaner <geychaner at mac.com> wrote: > When the DOS box exits, crashes, or is rebooted, it fails to shut down the > socket properly. Yes, that?s what happens when you use an OS that doesn?t implement sockets in kernel space: there is no program still running that can send the RST packet for the dead socket. > Under CentOS 6.5, upon reboot,

I have finally received and am configuring my new workstations eith the NVS510 graphics cards, and have run into rather a problem. The X server seems to be loading the NOUVEAU driver properly (based on the contents of Xorg.0.log), but I have one X11 application that doesn't work correctly; it runs as though XSynchronized is always True, even though it's explicitly set to False in the

On my new Haswell-based machines, I am occasionally seeing entries like the following in /var/log/messages: kernel: [Hardware Error]: Machine check events logged (I would not have even noticed them, except that they get flagged by logwatch.) These messages always occur alone, and don't seem to have a corresponding entry in any other log file in /var/log. How can I get more info about these

Could someone please explain to me how to best configure printers in CentOS 5? I've been trying to configure a new printer, which is served by a Mac Mini: If I open a web browser at localhost:631, or "system-configure-printers" and I configure the new printer as an IPP printer, it winds up in a list of "Remote printers", and once it winds up there I can't seem to

I am trying to assemble or purchase a set of CentOS 6 compatible SFF workstations, and am finding it incredibly frustrating to do so. hardware.redhat.com is so slow as to be useless and provides almost no information about each of the 1,300 or so products listed in their database; clicking through them one at a time is incredibly frustrating (and about half of them are discontinued or out of stock

I'd like to thank everyone for their replies and advice. I'm sorry it took so long for me to respond; I took a long weekend after a long shift. Some remaining questions can be found in the final section of this posting. The summary (I hope i have all of this correct): Problem: A DOS box (client) connects to a Linux box (server) using the same local port (1025) on the client each time. The

On Wed, Jan 21, 2015 at 10:49 AM, Glenn Eychaner <geychaner at mac.com> wrote: > > 2) Protocol change: The server never writes to the socket in the existing > protocol, and can therefore never find out that the connection is dead. > Writing to the socket would reveal this. But what happens if the server writes > to the socket, and the client never reads? (We do, as it happens,

[I wish I knew how to get the mailing list to thread my replies properly in the archives; I subscribe to the daily digest, and replying to that doesn't do it.] Greg Lindahl wrote: > On Thu, Jan 15, 2015 at 03:40:08PM -0300, Glenn Eychaner wrote: > > > My only theory is that this has something to do with non-ephemeral ports and > > socket reuse, but I'm not sure what.

The latest updates to CentOS 5.5 seem to have broken the Java plugin, and have defeated any and all attempts to get it working again. I'm running CentOS 5.5 (32-bit) and Firefox 3.6.9 (installed from the CentOS repository); I've tried BOTH the openJDK plugin available through the Argeo repositories, and installing Java 1.6.0 directly from Sun/Oracle and creating the plugin soft link in

When rsync is used in remote-shell server mode, the documentation says: "Rsync supports connecting to a host using a remote shell and then spawning a single-use "daemon" server that expects to read its config file in the home dir of the remote user." I have been trying to make rsync read a config file (which I presume should be named rsyncd.conf) in the home directory of the

I manage a set of CentOS operations workstations which are all clones of each other (3 "live" and 1 "spare" kept powered down); each has a single drive with four partitions (/boot, /, /home, swap). I've already set up cron'd rsync jobs to copy the operations accounts between the workstations on a daily basis, so that when one fails, it is a simple, quick process to swap