difference redhat sv debian

By OK -
Main Difference is Ubuntu is based on Debian system. It uses .deb packages. While redhat uses it own package system .rpm (red hat package manager ).
Redhat is free but it is charged for support (updates), when Ubuntu is totally free with support for desktop users only professional support is chargeable.

1. RedHat is Most Widely used Distribution for servers.
Debian is widely used Distribution next to RedHat.
2. RedHat is Commercial Linux Distribution.
Debian is Non-commercial Linux Distribution.
3. RedHat contains roughly 3000 packages.
Latest Debian Release (Wheezy) contains well over 38000 packages.
It means Debian contains nearly 80% more packages than RedHat and this is the reason Debian contains packages like openoffice, Transmission bittorrent client, mp3 codecs, etc which a RedHat like distribution lacks and is required to be installed manually or from 3rd party repository.
4. RedHat bug fixing takes considerable time, since it is controlled by a small group of people-RedHat Employee.
Bug fixing in Debian is very much quick as people all around the globe from Debian community, working from different geographical location simultaneously fixes it.
5. RedHat don’t release package updates, till next release, means you have to wait for the next release be it minor.
Debian community believes – software is a continuous evolution process, hence updates are released on Daily Basis.
6. RedHat releases major updates every six month and nothing in between. Installing new updates in RedHatbased System is a tuff task, where you need to reinstall everything.
Installing the Debian updates being released everyday is a pretty easy task barely 3-4 clicks away.
7. RedHat is rock solid stable distribution released after continuous testing.
Debian contains packages from stable, unstable and testing Repository. Stable contains rock solid stablerelease packages. Unstable contains more updated packages ready to be pushed into stable repository. Testing contains packages already tested and marked safe.
8. RedHat package manager Yum is less mature and is not able to solve dependencies automatically, many a times.
Debian package manager Apt is very mature and solve dependency automatically, most of the times.
9. Installing VLC in RedHat Beta Release 6.1, is a very difficult task which requires installing tens of packages manually.
In Debian it is as simple as apt-get install vlc*
10. Debian is intelligent in differentiating Configuration files with other files. This makes upgradation easy. The virgin (untouched) configuration files are updated automatically and the one modified, requires users interaction as the package manager ask what to do, but this is not the case with RedHat.
11. RedHat uses the rpm packages.
Debian uses the deb packages.
12. RedHat uses the RPM package manager.
Debian uses the dpkg package manager.
13. RedHat uses the yum dependency resolver.
Debian uses the apt-get dependency resolver.
14. Fedora uses single global repository which contains free software’s only.
Debian contains contribute and Non-free repository along with free software repository.
15. According to Wikipedia, Ubuntu is a based on the unstable branch of Debian but Fedora is not a derivative and has a more direct relationship and stays close to many upstream projects.
16. Fedora uses ‘su‘ whereas Ubuntu uses ‘sudo‘ by default.
17. Fedora ships with SELinux installed and enabled by default along with some other ‘hardening’ software to make things more secure by default, unlike Debian.
18. Debian is a community based distribution, unlike RedHat.

Comments

Post a Comment

Popular posts from this blog

HAproxy logging

By OK -
ubuntu@ubuntu:/etc/haproxy$ cat /etc/rsyslog.d/haproxy.conf # Create an additional socket in haproxy's chroot in order to allow logging via # /dev/log to chroot'ed HAProxy processes $ModLoad imudp $UDPServerRun 514 local0.* -/var/log/haproxy-0.log local1.* -/var/log/haproxy-1.log ### keep logs in localhost ## $AddUnixListenSocket /var/lib/haproxy/dev/log ------------------- ubuntu@ubuntu:/etc/haproxy$ cat /etc/haproxy/haproxy.cfg global chroot /var/lib/haproxy user haproxy group haproxy log 127.0.0.1   local0         log 127.0.0.1   local1 notice daemon frontend www     bind 192.168.40.128:8282    # haproxy public IP     default_backend as-backend    # backend used backend as-backend    balance leastconn    mode http  server as1 192.168.40.128:8082 check    # application srv 1 defaults log global mode http option httplog option dontlognull         contimeout 5000    
Read more

tomcat catalina coyote jasper cluster

By OK -
Tomcat Component are Catalina Coyote Jasper Cluster Catalina :  Catalina is the name of the servlet container of Apache Tomcat since version 4.x. Tomcat implements Sun Microsystems' specifications for servlet and JavaServer Pages (JSP), which are important Java-based Web technologies. Tomcat's servlet container was redesigned as Catalina in Tomcat version 4.x. other components of the Tomcat engine are: Tomcat Jasper which converts the code portions within JavaServer Pages into servlets and pass them to Catalina to process. Tomcat Coyote which is an HTTP connector based on HTTP/1.1 specifications that receives and transmits web requests to the Tomcat engine by listening to a TCP/IP port and returns requests back to the requesting client. Coyote :  The Coyote JK Connector element represents a Connector component that communicates with a web connector via the JK protocol (also known as the AJP protocol). This is used for cases where you wish to invisibly integr
Read more

NFS mount add in fstab _netdev instead of default | firewall-cmd --list-all

By OK -
Redhat recommends us to add  _netdev  option for NFS file system in /etc/fstab. So that they can be mounted after starting the networking service. Alternative ways to refer to partitions: Label : LABEL=label Network ID Samba : //server/share NFS : server:/share SSHFS : sshfs#user@server:/share Device : /dev/sdxy (not recommended) Example #1 //192.168.1.134/share_name /mnt/share_name cifs username=server_user,password=server_password,_netdev 0 0 ^ Path to your share ^ Mountpoint ^ Username ^ Password ^ See note A Note A: The  _netdev  options makes sure the mount is only attempted AFTER a network connection has been established. Example #2 10.10.10.1:/vol1/fs1 /data nfs defaults,_netdev 0 0 ============================ [root@localhost ~]# firewall-cmd --list-all public   target: default   icmp-block-inversion: no   interfaces:   sources:   services: dhcpv6-client high-availability ssh   ports:   protocols:   masquera
Read more