Windows Vs Linux – One more time

Tux, as originally drawn by Larry Ewing
Image via Wikipedia

One of the most written and commented articles has to be Linux vs Windows (of course there are competitors like vim vs emacs) but none has been covered so much as Linux vs Windows. So, what am I going to write here which is not covered earlier in so many other posts. Well a little different perspective 🙂


We will take this post in points so that we do not divert and its easier for you to comment with quotes to point number 🙂

1) These are for complete different segments of users.

Windows is for everyone and Linux is for geeks and fan-boy‘s. Well, not that I agree with this but lets face the fact. Windows is OS on which all the drivers works and you dont have to worry about which Webcam I need to buy or which scanner will work.

The reason for this is multi-fold but does that matter to everyday users.

2) Cost factor.

This is something that keeps popping up every time there is some discussion like this. I don’t think that anyone using Linux is using it because it is free. If there is someone using the FREE OS just because it is free then I for one would definitely like to understand if the same person would use Windows if it was free.

BTW, I guess in China people don’t even know that Windows license’s are paid.

3) Ease of Use

People using Windows have always this notion that Linux is difficult to use. I found it the other way round. I find myself limited in ways to work on Windows (Oh and yes, I am stuck with Windows here for last around 2 months). Its mostly a question of perception. There are still things in Linux that you might have to do in the so called bash/console/terminal/command prompt, call it what you want to. But mostly that is the case for doing things faster and otherwise you probably would not need to open a terminal ever.

But if you go to any of the forums, you will definitely get suggestions to open a terminal first. Why, because you will be getting suggestions from veterans in the field. These guys have been using Linux since the days when there was no GUI or using GUI was considered sin. Just kidding but seriously you can do things much faster in a “command window”.

4) Different Filesystems.

Windows uses FAT/vFAT/NTFS and so on whereas Linux uses some 83 other types of FS. Mostly widely used being ext2, ext3, ext4 and reiser (I guess ). Why does it matter to you? Because you can use (read as read/write) any of the windows Filesystems on the Linux box natively but not the other way round. So, be careful with this.

5) File-type and associations.

Files and folders are same on Linux and Windows. Does not make much of a difference. Both are handled in similar manner. Not the same if you look a little deeper. This is one thing that confuses most who are new to Linux.

In Windows the File type and the action of double click is based on the extension of the filename. So, if I have a file with name “a.txt” then the default text editor would be used. That is not the case in Linux (well the File Manager uses similar concept , see I told you it is confusing). The file type in linux is determined by the header in the file that is stored along with the files and not seen by us normally. Thus allowing you to store a pdf file with “.txt” extension and still be able to use pdf viewer to open the file. How cool is that 🙂 or how confusing is that 🙁

6) Applications

Some would say that the number of applications available on Windows is much more that available on Linux. Oh yeah, surely and how many of them you can use or rather how many of them are required. If not all, most of the useful ones are paid. So, you need to buy a license to use it. This is not the case with Linux, you have some couple of thousands of applications with mostly very decent GUI’s developed by Open Source advocates. And they were actually generous enough to compile it to “.exe” for the windows also.

7) Fanboys

The main reason for liking any one of the OS is probably because you met a Windows fanboy first so you also became a Windows fanboy. If you met a Linux fanboy first then you would become a Linux fan. Okay, there are chances that you met a more hardcore fanboy of the other side of the war, then he might convert you to his side and win over you.

I will leave it at abrupt end, so that it can tickle some more thoughts in both you and me 🙂

Enhanced by Zemanta

Easily monitor and archive your system log reports.

If you want to monitor your server logs and also like them to be emailed then just Logwatch may not be sufficient. It sends you a mail but does not archive them, so head over to epylog

Name        : epylog
Arch        : noarch
Epoch       : 0
Version     : 1.0.7
Release     : 9.fc22
Size        : 151 k
Repo        : fedora
Summary     : New logs analyzer and parser
URL         :
License     : GPLv2+
Description : Epylog is a new log notifier and parser which runs periodically out of
: cron, looks at your logs, processes the entries in order to present
: them in a more comprehensive format, and then provides you with the
: output. It is written specifically with large network clusters in mind
: where a lot of machines (around 50 and upwards) log to the same
: loghost using syslog or syslog-ng.

To install :

dnf install epylog

After this you need to configure the directory for the archiving and also the means of transport, that could be just File or File with email. In the second case, the reports are archived and email sent with link to the report.


Here is the sample configuration that I am using

cfgdir = /etc/epylog
tmpdir = /var/tmp
vardir = /var/lib/epylog

title = [Cron] ubu  @@HOSTNAME@@ system events: @@LOCALTIME@@
template = /etc/epylog/report_template.html
include_unparsed = yes
publishers = file

method = mail
smtpserv = /usr/sbin/sendmail -t
mailto = root
format = html
lynx = /usr/bin/lynx
include_rawlogs = no
rawlogs_limit = 200
# GPG encryption requires pygpgme installed
gpg_encrypt = no
# If gpg_keyringdir is omitted, we’ll use the default ~/.gnupg for the
# user running epylog (/root/.gnupg, usually).
#gpg_keyringdir = /etc/epylog/gpg/
# List key ids, can be emails or fingerprints. If omitted, we’ll
# encrypt to all keys found in the pubring.
#gpg_recipients =,
# List key ids that we should use to sign the report.
# If omitted, the report will not be signed, only encrypted.
#gpg_signers =

method = file
path = /var/www/epylog
dirmask = %Y-%b-%d_%a
filemask = %H%M
save_rawlogs = no
expire_in = 700
notify = root@localhost
smtpserv = /usr/sbin/sendmail -t
pubroot =

After you are done, you might want to head over to Fedora Wiki for Epylog and then download the weed_local file and file. The weed local file is a file containing the regex for common errors that you do not want to see in reports. So, feel free to add yours. And file sets up a pager. Download that and put it in the cgi-bin directory and configure the epylog data directory, and you are done.

Fedora/Ubuntu issue with assigned IP by dhcp server.

In the recent versions of Fedora/Ubuntu, I found that if the DHCP server assigns a reserved address, the address is not applied to the system. Finally I found that adding the below in /etc/dhcp/dhclient.conf, would fix the issue.

send dh-client-identifier = hardware;