Re: [CentOS] PHP version not enough for developers

[Lamar Owen]

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).
...
What was the rationale to let dbus near the system start at all?
 -- Again mobile development.



Was it?  Many servers are deployed as standard images, both physical and 
virtual, and having a single, standard, cloned image boot easily on 
multiple types of hardware makes lots of sense in this environment.  
Dbus is about hardware enumeration, both cold and hot plug.  And there 
are servers with hotplug PCIe, even hotplug CPU's. Dbus makes hotplug 
HDD support smoother, for instance, and hotplug isn't limited to USB or 
firewire (eSATA and external SAS, even fibre channel, can be hotplugged 
in most cases).


I still remember having to rebuild initrds when moving a clone from a 
server with one type of disk controller to another.  It should work a 
lot better with dynamic hardware detection in the initrd.  (I wont's say 
it's prefect, because I haven't personally tried every possible 
combination of hardware, but it has worked lately when I needed it to work.)


A SAN storage processor, for instance, must be able to hotplug drives, 
enclosures, front end and back end interfaces, power supplies, and 
sometimes even processors while staying up.



Systemd was just the latest development, and not the worst. Yes, it
could have gone better, and some of the devs have had more
head-in-the-clouds than feet-on-the-ground.

Looking back, systemd is the only "big" change since 2.6 that makes
sense for servers. ...


I would agree.


What was the jump forward for linux servers in this 16 years?
Better hardware support, ease of virtualization (as a guest and as a 
host), and dynamic hardware detection for rapid redeployment/hardware 
upgrade, just to mention three.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] PHP version not enough for developers

[Keith Keller]

On 2015-10-24, Johnny Hughes  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 systemd (so far).

Johnny, thank you for your efforts in trying to keep the mailing list
on-topic.  :)

--keith

-- 
kkel...@wombat.san-francisco.ca.us


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] PHP version not enough for developers

[Lamar Owen]

On 10/24/2015 10:08 AM, Lamar Owen wrote:


Was it?  Many servers are deployed as standard images, both physical 
and virtual, and having a single, standard, cloned image boot easily 
on multiple types of hardware makes lots of sense in this 
environment.  Dbus is about hardware enumeration, both cold and hot 
plug.  And there are servers with hotplug PCIe, even hotplug CPU's. 
Dbus makes hotplug HDD support smoother, for instance, and hotplug 
isn't limited to USB or firewire (eSATA and external SAS, even fibre 
channel, can be hotplugged in most cases).

s/Dbus/Udev/g

Argh. Long morning already.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Re: PHP version not enough for developers

[Nicholas Geovanis]

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 agreed. I believe that there is a perceived convergence of "needs"
between (call it...) more-mobile personal linux and _virtualised_ server
linux.
If we can create a linux VM in under 5 minutes, "we" expect that it will
boot-up
without the sys admin's intervention. Then "we" expect that we can migrate
it
to newer hardware without manual reconfiguration.

But returning to PHP: If apps are developed without real separation between
user interface and back-end, then the back-end will be victimised by the
relative and inherent instability of the front-end. The web servers then
really
become part of the front-end and must be handled as such. I would argue that
this lack of separation between front-end and web server is a feature of
the WWW
and its protocols, we cannot escape it. So no surprise that most data
centers
leave the web servers outside or mostly-outside the network perimeter.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] PHP version not enough for developers

[Johnny Hughes]

On 10/23/2015 03:44 PM, m.r...@5-cent.us wrote:
> Jonathan Billings wrote:
>> On Oct 23, 2015, at 9:46 AM, m.r...@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 part or an actual change in the environment.

 Apparently it is the later.
>>>
>>> So systemd moves Linux to more resemble Windows?
>>
>> No.  If anything, systemd handles upgrades better than SysV init, since it
>> handles re-execing better.  Please stop spreading FUD.
> 
> What FUD? It adds *binary* logfiles, readable only with a separate
> program; when I restart a service, it does not *tell* me what's going on,
> just worked or didn't, so I don't know, if it fails, where, the messages
> from journalctl are extremely unhelpful, and when it boots, if I want to
> watch, it tends to hide much info. It's much less informative in most ways
> in helping me solve problems.
> 

Jesus Christ .. do we really have to start ANOTHER systemd thread.

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.
 CentOS-7 contains systemd and where ever Red Hat puts it, CentOS will
rebuild the source code.

If people don't like the distro, then use something else.

These lists are for providing USEFUL information to CentOS users ..
flame threads will result in list users who are moderated.




signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] OpenSSL and OpenSSH on CentOS (FIPS enabled)

[Gordon Messmer]

On 10/22/2015 09:12 PM, Ning Liu (niliu2) wrote:

(1) Is that true for OpenSSL ?


http://stackoverflow.com/questions/18616573/how-to-check-fips-140-2-support-in-openssl

But, having said that, you should note that FIPS is a certification that 
applies to specific products.  You can enable "FIPS mode" but no CentOS 
systems are FIPS certified.  If you require certification, you must use 
a Red Hat product.



(2) How about OpenSSH, since we are using SSH for administration, but there is 
not too much document mentioning OpenSSH Vs. FIPS.


Look at the document you linked to, again.  It describes specifics with 
regard to OpenSSH.  Verify that sshd is configured according to the 
documentation, and follow the advice when generating host and user keys.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] PHP version not enough for developers

[Valeri Galtsev]

On Sat, October 24, 2015 12:23 pm, Keith Keller wrote:
> On 2015-10-24, Johnny Hughes  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 systemd (so far).

Or switch away from Linux, say, to (Free|Opnen|Net|PC-|...)BSD just to
expand options. But to take advantage of the greatness of RHEL and CentOS
life cycle you have to live with systemd and friends no matter what you
thinks about them (you see, I already have convinced myself ;-).

And yes, thanks for everybody's effort to keep discussion off the insanely
polarizing us topic(s).

Valeri

>
> Johnny, thank you for your efforts in trying to keep the mailing list
> on-topic.  :)
>
> --keith
>
> --
> kkel...@wombat.san-francisco.ca.us
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>



Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS-announce Digest, Vol 128, Issue 8

[centos-announce-request]

Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@centos.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."


Today's Topics:

   1. Release for qemu-kvm-ev from Virtualization SIG (Karanbir Singh)
   2. Release for Software Collections SIG content (Karanbir Singh)


--

Message: 1
Date: Fri, 23 Oct 2015 16:50:25 +0100
From: Karanbir Singh 
To: CentOS Announcements List 
Subject: [CentOS-announce] Release for qemu-kvm-ev from Virtualization
SIG
Message-ID: <562a5741.1050...@centos.org>
Content-Type: text/plain; charset=utf-8

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I am pleased to announce the immediate availability of qemu-kvm-ev
stack for CentOS Linux 7/x86_64. This release is delivered by the work
done in the CentOS Virtualization Special Interest Group.

In order to use this qemu-kvm version, on an updated CentOS Linux
7/x86_64 machine, you should run:
  yum install centos-release-qemu-ev
  yum install qemu-kvm-ev

This will bring in all the dependencies needed, including the updated
qemu-img tools.

This stack is curated as a part of the CentOS Virtualization SIG. You
can find more details about this group, including the technologies
they are bring to CentOS at their page
https://wiki.centos.org/SpecialInterestGroup/Virtualization . This
group meetings every alternate Tuesday in #centos-devel on
irc.freenode.net, details for the meetings can be found on their SIG pag
e.

We welcome participation in this group from anyone interested in
virtualization and technologies associated with it. Feel free to drop
into our list at https://lists.centos.org/mailman/listinfo/centos-virt
and say hi.

Thanks to Sandro Bonazzola from the oVirt team for building and
maintaining this qemu-kvm-ev stack.


- -- 
Karanbir Singh, Project Lead, The CentOS Project
+44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS
GnuPG Key : http://www.karan.org/publickey.asc
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJWKldBAAoJEI3Oi2Mx7xbtb3gIAIIF7If9daApI0cZtRPCLNC+
fz6FPpWd/OyBOkyXHFtREp32voR16eq0EMowW8P+mLAB5YJ6iauMfv7vDTHJWAnw
n3/x2MSHMsSiRCUUDnLAJHBqqJ4X1YUsNkbHE/f+Vb7AF9w2fuQE7BBUJsjGY5tQ
9V1SIkVSdzaYy2tps7Y6b9iHBk5zpMiWnFdMKfW/QTSoLp9wpi+0jlwx7aebHRAK
y1tEIljDEgwSF85IkGkNtah1LGjhiB1J4aseewjKw2azsQ1z41fh4MFnujvPXSbj
40aJoRDcLvtXtaHB5dMMXOeMFkaki4iJxH5GV3H32sGfrLm+7ZuH3n397rfuAvk=
=aU1U
-END PGP SIGNATURE-


--

Message: 2
Date: Fri, 23 Oct 2015 16:59:11 +0100
From: Karanbir Singh 
To: CentOS Announcements List 
Subject: [CentOS-announce] Release for Software Collections SIG
content
Message-ID: <562a594f.4020...@centos.org>
Content-Type: text/plain; charset=utf-8

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

The Software Collections SIG group is pleased to announce a way of
Software Collections packages availability for CentOS Linux users. The
Software Collections packages have been build in CentOS Build System
[1] and will be available soon on CentOS mirrors. Collections will be
released in stacks, as we test and validate them.

With Software Collections provided by SCLo SIG, users of CentOS Linux
as well as other SIG groups in the CentOS ecosystem will be able to
use the latest versions of popular application stacks, databases or
other content mainly focused on developers. And they are able to do
this without any impact to the system versions already installed on
their machine.

The SCLo SIG is not only meant to include packages rebuilt from
Software Collections that have been made available in Red Hat Software
Collections (RHSCL), but it is also meant to include updated content
or collections that are not part of the RHSCL portfolio at all.

So far, the collections rebuilt by SCLo SIG from RHSCL are
devassist09, devtoolset-3, git19, httpd24, mariadb55, maven30,
mongodb24, mysql55, nginx14, nginx16, nodejs010, perl516, php54,
php55, postgresql92, python27, python33, rh-java-common,
rh-mariadb100, rh-mongodb26, rh-mysql56, rh-passenger40, rh-perl520,
rh-php56, rh-postgresql94, rh-python34, rh-ror41, rh-ruby22, ror40,
ruby193, ruby200, thermostat1 and v8314.

With Software Collections that are not part of RHSCL (so far
sclo-vagrant1 collection), both CentOS Linux and RHEL users will be
provided by content that is not available on those platforms otherwise.

Getting started with Software collections:
On an updated CentOS Linux 7/x86_64 machine run:
  yum install