If you are extremely proficient with RHEL, please stop here, thanks!

I have used Centos 6 exclusively so far, and recently I have installed both Centos 5 and Centos 7 on my virtual platform, to my surprise, Centos 5 is very pleasant to use and many tools have both GUI based and command-line based configuration [completely new to Centos 5], more pleasant to use than Centos 6, as for Centos 7, it is something I do not like (I do acknowledge some benefits listed here: http://www.infoworld.com/article/260...th-a-jolt.html), looks to me RedHat is determined to make sure their RHEL more difficult to use, thus generating far more training revenue because not only you have to learn many new things, but also everyone probaly need new traing and support contract, in the past, I have heard that RedHat is TOO COMMERCIAL, meaning everything they do exclusively for commercial reasons, often at the peril of their customers [wonder why Win8 is widely hated? because Microsoft commercial interest tell them to make it more difficult, so everyone get use to their aweful Windows Phone, who has 1.6% market share]
My apology if you don't like my comments, because you think any new change (making it more difficult to use) is intended by RedHat solely for security. I do know sometimes simple-to-use software maybe more prone to bugs, but is that the sole reason they made certain changes to RHEL7? I seriously doubt it, I also have noticed that just about every commercial software these days [most of the time new version is designed SOLELY to force people to buy newer version despite there is absolutely no benefit to customer] , the new version seemed to be more buggy, more complicated and more difficult to use [I do understand sometimes change is needed, say update video editing software to newer version where 4K is now supported], I challenge you to name 3 popular softwares that new version are better than the one came out 3-4 years ago.

oldversion.com one of my favorite website!

RHEL 7 is changing, but you can bet fedora and CentOS are following (maybe leading)...and so will the rest of Linux.... maybe slowly, but it's coming. Like everything else, change is inevitable... move forward or set on a stump and watch the world pass you by....

Not a very technical article, but a little history about where systemd came from and it's rise to power....

http://www.zdnet.com/after-linux-civ...md-7000026373/



Next to the last line on the article...


So we better get used to it...and get educated about it!!

Also, remember that RHEL is targeted completely towards the enterprise sector, where security is of paramount importance. They really could care less if it's harder to use, because they assume the companies using it will either:

1. Hire people that are Red Hat certified, and thus know how to manage it, or
2. Purchase a support contract that includes a fairly large degree of handholding from Red Hat itself.

Either way, they win multiple times, and their customers still win too. Their system gets better security (making more companies willing to trust it), they get money (either from the training SysAdmins or support contracts), and the company gets a more secure server operating system.

I so wish I could get the RHEL 7 training...

If I have good memory (I understand things, but I am not good at memorizing all the details), I can easily pass RHCE, this is about the level I am at.
I am reading the RH256-6-2-20110124 training material right now, so I have three brand new workstations, with Centos 5.4, Centos 6.4 and RHEL 6.3 (never got update, because I did not pay), so I am setting up a vsftp server where people can upload files, I'm following the instruction on pg363/364, my frustration comes from my experience: RHEL/Centos often does not work as intended, nor it is robust enough, even for very simple tasks, I never understand why sometimes things just not work as intended (these VM workstations are brand new and never messed up before), basically I could not set /var/ftp/share to have the following security context, public_content_rw_t, it is always public_content_t

[root@hpserver ~]# yum install vsftpd
[root@hpserver ~]# service vsftpd start
[root@hpserver ~]# chkconfig vsftpd on
[root@hpserver ~]# mkdir /var/ftp/share
[root@hpserver ~]# chgrp ftp /var/ftp/share
[root@hpserver ~]# chmod 730 /var/ftp/share
[root@hpserver ~]# semanage fcontext -a -t public_content_rw_t '/var/ftp/share(/.*)'
[root@hpserver ~]# restorecon -vvFR /var/ftp/share

strange thing is the directory actually has public_content_t as the context type, NOT public_content_rw_t as intended, this has been observed on all VM servers.

[root@hpserver ~]# setsebool -P allow_ftpd_anon_write on
[root@hpserver ~]# edit /etc/vsftpd/vsftpd.conf

anon_upload_enable=YES
chown_uploads=YES
chown_username=daemon
anon_umask=077

After this, I restart vsftpd, I got error message: bad bool value in config file for anon_up_load_enable, I tried "YES" and "yes", but the vsftpd just refused to restart, this happened on Centos 6.4 and Centos 5.4, but not RHEL6.4, and I only got the vsftp server work on RHEL6.4, but I can't upload anything to the ftp directory.

My own experiences with Centos and RHEL is they are extremely fragile, extremely prone to malfunction, not something as robust as you would expect from RedHat, can someone explain why I observed the above?

I dig a little further, in this file /etc/selinux/targeted/contexts/files/file_context, it says this:

/var/ftp(/.*)? system_ubject_rublic_content_t:s0

if I edit this file and change it to public_content_rw_t, save it, and when I open it, it is changed back to public_content_t, so my question is why I can't use semanage fcontext -a -t ....... to set /var/ftp/share to "public_content_rw_t"? Isn't "semanage fcontext -a -t" is a command used to permanently change SELinux context of files/directories? I am really troubled by this BS, it is just too damn complicated!

I solved the problem, in my earlier post, the command I used was this:
[root@hpserver ~]# semanage fcontext -a -t public_content_rw_t '/var/ftp/share(/.*)'

change to this
[root@hpserver ~]# semanage fcontext -a -t public_content_rw_t "/var/ftp/share(/.*)?"

by using the first command, the SELinux context was changed to public_content_t (despite I wanted public_content_rw_t), by using the 2nd command, I can change it to public_content_rw_t

I can't even tell what your complaint is besides "I don't know how to use it, so it sucks". That's not really a valid complaint. As a desktop, stock RHEL5 was atrocious for usability, stock RHEL6 only a bit better (and even then, it just didn't work well). RHEL 7 works exactly the same as Fedora 20. It is very usable, is very flexible (don't want Gnome 3? Install something different).

I don't find RHEL to be fragile, or not robust as you seem to say. Just because you are running commands out of order, or not at all correctly doesn't make the OS "fragile". SELinux isn't a straightforward protocol, and there are many different roads that take you where you want to go. Within that flexibility, there is a very large margin of error. Practice it some more, and you will learn it.

"Not easy or straightforward" doesn't mean "weak" or "fragile". It just means you need more practice.

if Gnome 3 is the issue then use KDE, or xfce, or lxde, or ice, or e17 .

look back in time at the fedora 16 ( i think it was 16 ) trolling and hate and like and love rants

when Gnome3 came out it was a MESS just like KDE3.5 VS KDE4 was

1 members found this post helpful.