similar to: PHP version not enough for developers

On 10/23/2015 05:45 PM, Yamaban wrote: > Well, looking back, during kernel 2.6 there was no systemd at all. > But! That was the time where udev and dbus came into the boot cycle. > ... > What was the rationale to get udev into boot? -- Handling the ever > changing mess of plugable, switchable hardware. Not born and bred > for servers, but for mobiles (phones, tablets, laptops).

Ok, got a quickie. I have an eSATA drive, a 750GB Seagate in an eSATA external enclosure, and a Silicon Image sil3132 ExpressCard controller for my laptop. The disk and controller work great in CentOS 5 (or F7, for that matter), if I specifically mount it. This is not how I want to have to use this drive, however. I want to hotplug it; that is, plug the controller into the laptop, and then

Hi CentOS 5.4(final) 2.6.18-164el5PAE. I am trying to prevent removable USB and eSATA devices from occupying /dev/sdX devices ahead of a 3ware RAID controller. For example: at boot, if a USB drive and eSATA HDD (connected to an LSI 1068E onboard controller, reflashed in "IT" mode to handle hotplug devices) were both present, they would occupy devices /dev/sdb and /dev/sdc, ahead of

I got a WD 1TB My Book with eSATA/USB/Firewire400 connectivity to backup data on a client Centos 5.1 machine. USB 2.0 works fine out of the box but is rather slow, Nautilus predicts about 1+ hour to fully backup just one day's worth of data or about 100GB. So I was hoping Firewire would be faster, which is why we got the version with all 3 interfaces to experiment with first. Following the

Does any one know how to, if at all possible currently, to export a block device via eSATA? i.e. how do I do something like iSCSI, but over eSATA? I have a cheat ($15 probably?) media player at home (Egreat EG-M31B Network Media Tank - awesome little machine) that runs some flavor of Debian and can be connected to any PC via eSATA as an external HDD's. i.e. it exports the built-in HDD as a

Hi, I'm having a grief with Seagate FreeAgent Pro drive connected to CentOS 4 box via USB. The problem is that drive is factory configured to take a nap (spin down) after some 15-20 minutes of inactivity, and there doesn't seem to be a way to disable it. Since it's USB connected, hdparm can't be used on it. Getting the drive out of the case is not an option either, since it

Hey, just bought an eSATA/USB dual drive docking station and my CentOS 5 can only see one drive at a time... Any one knows if there are specific parameters to set somewhere? Or do I need a more recent kernel (like upgrading to CentOS 6?) The docking is a Sharkoon Quickport Duo v2 + 2 drives + 1 eSATA cable... http://www.sharkoon.com/?q=en/content/sata-quickport-duo-v2 The eSATA controller is an

We've got this Dell server. In it, we've got two LSI HBAs. Mini-SAS to one RAID box. The other, cheapo RAID box, has eSATA. We got a mini-SAS-to-eSATA cable - actually, it's one mini-SAS to three eSATA. The systems sees not those disks. Will this just not work, with the HBA, or is there a driver that will let the what, mpt2SAS driver see the eSATA drives? mark

On 10/22/2015 10:31 AM, Andrew Holway wrote: > Hi, > > So, it seems that the current version of PHP in Centos 7 is PHP 5.4.16 > however this version of PHP stopped getting security support from the PHP > people one month ago [1]. > > Now, our developers want to use the new and shiny PHP because they want to > use the latest version of Zend. They are proposing using this

Nux! wrote on Thu, 22 Oct 2015 17:27:26 +0100 (BST): > It's irrelevant in this case that PHP 5.3 is EOL. It will continue > to be supported by Red Hat with security patches. Exactly. Nevertheless, PHP 5.6 is not "bleeding edge" as someone else said. 5.5 and 5.6 are really state of the art and often necessary to install certain software packages or for some functionality.

On 10/22/2015 10:31 AM, Andrew Holway wrote: > Hi, > > So, it seems that the current version of PHP in Centos 7 is PHP 5.4.16 > however this version of PHP stopped getting security support from the PHP > people one month ago [1]. > > Now, our developers want to use the new and shiny PHP because they want to > use the latest version of Zend. They are proposing using this

El 22/10/2015 a las 01:40 p.m., Nux! escribi?: > Kai, > > It is a reality, but when you look at the RHEL target audience, it's not exactly hip devs deploying Docker in the cloud. > Big corps, banks and the like have a very slow development cycle and long term support is absolutely crucial, software needs to run for years on end without glitches, without interruptions, in a very

James B. Byrne wrote: > > On Thu, October 22, 2015 17:25, Valeri Galtsev wrote: >> . . . Still, disregarding the part some of us dislike personally >> (plus often reboots necessary to install some vital updates >> - which all Linuxes are prone to beginning somewhere around >> 2.6 kernel) . . . > > I am glad to discover that I am not losing my mind. I too have

On Fri, 23 Oct 2015, Valeri Galtsev wrote: > But coming back to negative part (which is about almost any Linux > distribution). These often reboots started in my recollection around 2.6 > kernel which is long ago. There's no way that needing a reboot is related to 2.6. Indeed newer features like ksplice can /reduce/ the number of reboots required. jh

Jonathan Billings wrote: > On Oct 23, 2015, at 9:46 AM, m.roth at 5-cent.us wrote: >> James B. Byrne wrote: >>> >>> I am glad to discover that I am not losing my mind. I too have been >>> rather dismayed at the perceived increase in frequency with which I >>> must reboot my servers. I wondered whether this was simply a >>> misconception on my

Yamaban wrote: >The mess we have now, is not the work of just one change. >What was the rationale to get udev into boot? -- Handling the ever >changing mess of plugable, switchable hardware. Not born and bred >for servers, but for mobiles (phones, tablets, laptops). >Who was the one that decided that "one-size-fits-all" and put that >into server environment? IMHO

On 2015-10-24, Johnny Hughes <johnny at centos.org> wrote: > > For the sake of everyone's sanity .. if you (any user, not mark > specifically) don't want to use systemd, then please don't use CentOS-7. For example, you could help out with Devuan, which aims to remove systemd from Debian, or you can switch to Slackware, one of the few major distros not to even include

On 10/24/2015 01:59 PM, Valeri Galtsev wrote: > > On Sat, October 24, 2015 12:23 pm, Keith Keller wrote: >> On 2015-10-24, Johnny Hughes <johnny at centos.org> wrote: >>> >>> For the sake of everyone's sanity .. if you (any user, not mark >>> specifically) don't want to use systemd, then please don't use CentOS-7. >> >> For

On Thu, October 22, 2015 12:49 pm, Johnny Hughes wrote: > On 10/22/2015 11:50 AM, Juan Bernhard wrote: >> >> El 22/10/2015 a las 01:40 p.m., Nux! escribi?: >>> Kai, >>> >>> It is a reality, but when you look at the RHEL target audience, it's >>> not exactly hip devs deploying Docker in the cloud. >>> Big corps, banks and the like have

El 22/10/2015 a las 12:48 p.m., Valeri Galtsev escribi?: > > On Thu, October 22, 2015 10:40 am, Jim Perrin wrote: >> >> >> On 10/22/2015 10:31 AM, Andrew Holway wrote: >>> Hi, >>> >>> So, it seems that the current version of PHP in Centos 7 is PHP 5.4.16 >>> however this version of PHP stopped getting security support from the