Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

rhel 6 fustrations...

On 12/03/2010 02:16 PM, Jim Gasek wrote:
> Fedora v. RHEL:
> One thing I've noticed, Fedora leaves out much "enterprise"=20
> type stuff (the conspiracy theorist in me thinks this is =20
> so Fedora doesn't easily "Steal" too many seats from RHEL).=20
> Autofs, for example, it missing.  Fedora isn't meant to be
> "used as a server"?   I suppose I buy that logic.  Less
> tried and true.
> =20
> Upstart:
> I'm really interested in the changeover from "traditional"
> init, to "upstart" init.   Have not stumbled upon too many
> good/practical pieces that explain how the migration is
> being implemented in different *nix distros.
> >From the earlier discussion,  I think part of the reason
> for some of the popular utilities being "gone" is that the
> underlying foundation of startup/shutdown is being shifted,
> and many of the admin utils are tightly related to startup
> and shutdown.
> I'd be interested in hearing more of the "upstart" story.
> I think I understand the "goals", but the issue is the=20
> complexity and the fundamental incompatibility between the
> two paradigms.    Merging (or having available both).
> Static Linking:
> Also the "Static linking" package is noticeably missing in=20
> RHEL6.   The doco says that they're trying to extinguish=20
> bad programming practices.   I'm always curious when=20
> functionality is removed.  The doco says that they're trying=20
> to extinguish bad programming practices. =20
I'm not going to reiterate what Jarod said, but Fedora is configured by
default as a desktop workstation, not as a server, so if you want server
packages you simply need to install them, as Jarod pointed out. In
contrast RHEL is specifically an Enterprise Server and is configured by
default as a server, and many of the bells, whistles, and toys are not
installed by default and may not even be included on the distribution iso=

WRT static linking: Statically linking an application is generally not a
good practice for many reasons, but there are sometimes reasons for it.
One of the real issues that can get you into trouble is when using some
of the more critical run-time libraries, like libc. I certainly do not
like it when functionality is removed, but today it is best to link with
shared libraries. But there are certainly times when linking with a
static library might be desirable.

Jerry Feldman <gaf-mNDKBlG2WHs at>
Boston Linux and Unix
PGP key id: 537C5846
PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB  CA3B 4607 4319 537C 5846

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /