Stories
Slash Boxes
Comments

SoylentNews is people

posted by n1 on Friday August 29 2014, @07:53AM   Printer-friendly
from the a-tip-of-the-fedora dept.

Longtime employee and CTO of RedHat is leaving the company.

“We want to thank Brian for his years of service and numerous contributions to Red Hat’s business. We wish him well in his future endeavors,” said Jim Whitehurst, President and CEO of Red Hat.

ZDNet reports:

Stevens' eyes may have been wandering elsewhere because of conflicts with Red Hat's president of products and technologies Paul Cormier. Cormier will be taking over the office of the CTO for the time being.

His future? It's unclear but it's possible he's moving to greener pastures, "a major California-based technology company."

Commence wild speculation! What does this mean for RedHat and GNU/Linux? Anything?

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by Marand on Saturday August 30 2014, @12:45AM

    by Marand (1081) on Saturday August 30 2014, @12:45AM (#87408) Journal

    I found that RedHat and most of its derivatives all installed insecurely at that time, (I'm told this hasn't changed much since), and all sorts of services and ports were open out of the box. I got one redhat machine pwned on the internet. My fault, for not securing it. But after installing several other distros previously and having to manually go in and turn on services, etc, I just assumed all distors installed locked down.

    Noticed that myself. Fighting with Redhat's "every port is open, pwn me plz" design back when I was a newbie was a pain in the ass and one of the reasons I looked into alternatives.

    I ended up with SuSE, still using Opensuse today, as well as a few installations of SLES. Not happy with SystemD, but I'm sticking with opensuse while at the same time putting up OpenBSD as my new principal file server.

    I've mentioned this elsewhere, but you can still avoid systemd as init in Debian, even in the testing/unstable releases currently, by installing systemd-shim. With that package installed, the other parts of systemd (logind, primarily) that are being tied to bits like udev still function without systemd being the init. The init part is what I'm most opposed to, so I run sysv-init and ignore the rest.

    My preference would be to not have any part of systemd, but as long as it's not the init, I can tolerate it in the same I tolerate some other parts of the system I don't necessarily agree with or want.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2