Red Hat Releases RHEL 6

alphadogg writes "Red Hat on Wednesday released version 6 of its Red Hat Enterprise Linux (RHEL) distribution. 'RHEL 6 is the culmination of 10 years of learning and partnering,' said Paul Cormier, Red Hat's president of products and technologies, in a webcast announcing the launch. Cormier positioned the OS both as a foundation for cloud deployments and a potential replacement for Windows Server. 'We want to drive Linux deeper into every single IT organization. It is a great product to erode the Microsoft Server ecosystem,' he said. Overall, RHEL 6 has more than 2,000 packages, and an 85 percent increase in the amount of code from the previous version, said Jim Totton, vice president of Red Hat's platform business unit. The company has added 1,800 features to the OS and resolved more than 14,000 bug issues."

Comments

Still the gold standard of long-supported releases

[proxima]

RHEL provides a 7 year lifecycle, which is unmatched by the other major distributions I know about (even Debian). This is crucial for the enterprise; I know of a number of systems which are still running RHEL3 after 6-7 years. Upgrading production computers is not a trivial process, and 2-3 year lifecycles just don't cut it in some situations.

Re:erode Windows server how?

[Nerdfest]

I've always thought that one should pay for support on a per-incident basis for software that one considers reliable. Count your incidents per year for the last few years and do the math.

85% increase in code?

[onyxruby]

I distinctly remember when a lack of bloat was one of Linux's bragging points. What happened to Red Hat? Time was they were also once cheaper than the windows servers they lampooned.

Re:erode Windows server how?

[h4rr4r]

Redhat would never make a dime.
Truth is lots of places use Centos as it is now.

RHEL should offer site licenses or something like that. No need to be cheaper just even more easy to deal with. The lack of CALs and different levels of the OS already makes them easier to deal with than windows licensing.

Re:RHEL comes with free CALs

[seifried]

Or you can just install CentOS which is Red Hat minus the artwork and the word "Red Hat" like most of us. I find Linux generally stable/reliable enough that I don't need support (I can't even remember my last Linux server crash, it's been years and stuff "just works").

Re:RHEL comes with free CALs

[cduffy]

That's fine and dandy if it's just your own server hooked up to your cable, but when it matters, going without support isn't a realistic option no matter how good the software is.

It's also fine and dandy if you have an in-house systems engineering team who can hack anything from the kernel through the app layer.

I've been part of that team at multiple shops. It's a pretty fun role -- lots of variety (everything from patching buggy DSDTs in the firmware of the servers we were using to extending the virtualization libraries with features we needed and pushing those upstream... and everything inbetween).

Not everyone needs a support contract, even if they're doing Serious Business. Indeed, if you're running tens of thousands of relatively cheap servers, those support contracts can be pretty expensive. (Not nearly as expensive as power and cooling, to be sure, but not entirely trivial either).

Windows network effect

[Craig Ringer]

Alas, right now I'm moving many services from RHEL to Windows 2008 Server.

Why? Group Policy, and Volume Shadow Copy Service.

I cannot overstate the importance of Group Policy in simplifying the management of a client network. Especially when combined with Windows Software Update Services, it's been wonderful. I've been a Linux guy since forever, but I'm really being swayed against my will toward the Windows server stuff for managing Windows clients.

As for the Volume Shadow Copy Service - it's all well and good to have 10-minutely Bacula incrementals thoughout the day, but nothing beats near-zero-cost snapshots that automatically age out when space is exhausted and that are very space efficient because they're done at the file system level. No, LVM cannot do this, it's block level and thus wastes a lot of space snapshotting changes to "free" space etc. Additionally, snapshots must be mounted, and old snapshots age out rather ungracefully. I've had a server fail to boot because of a broken LVM snapshot multiple times, and it's a major piss-off. It can't touch versioned files in NTFS. Maybe BTRFS will be there in 5 years.

Truly, though, it's Samba's quirks/limitations, and the lack of Group Policy, that's driven me to drop Linux for managing Windows clients. This isn't surprising, as Microsoft doesn't want to make it easy to manage Windows clients with anything other than Windows servers, and while the Samba folks are doing a heroic job there's only so much they can do.

Re:Windows network effect

[CAIMLAS]

There are a couple ways around doing this, but none of them seem to make much sense from a time investment perspective - your's included.

There's something to be said for 'knowing' through GPOs and the like, what's on a system. You can't do this with registry hacks.

As for LVM2... I've avoided it like the plague that it is: slow/inefficient and buggy are good words for it. It's also awkward to manage.

This is what I've done... we've got a Windows domain for our Windows servers (mostly terminal servers), and a domain for our Windows workstations. The Windows servers are all virtualized, and workstations are locked down to a bare minimum - most of what they use now is either online or on the terminal servers. Heavy, non-networked applications, like Office, remain on the workstations.

The virtual hosts, as well as a mess of BSD and OpenSol/Nexenta servers, are all on Kerberos + LDAP. Samba is on systems where it is appropriate to allow one or more domain to access files. Anything important goes on in Unixland, and the ZFS snapshots kick the snot out of VSS. In fact, with the ZFS SAN and XenServer, I'm able to integrate VSS into ZFS to take snapshots at the SAN level transparently. I can ship those over the network to another system for backup using the snapshot mechanisms.

Currently, I'm playing with the idea of Samba 4 on the Unix machines, because it's easier to handle (though the maturity isn't there yet for AD master, and you sort of need to know what you're doing - while having a fairly intimate understanding of krb5 and ldap in the process). I might be able to do away with the use of a handful of pricey CALs for the Windows servers while improving network file transfer performance for the users by doing this: somehow, beta Samba still manages to trump W2k8R2 for CIFS performance.