DriveDroid

DriveDroid

This seems handy.  Description from the app page:

DriveDroid allows you to boot your PC from ISO/IMG files stored on your phone. This is ideal for trying Linux distributions or always having a rescue-system on the go… without the need to burn different CDs or USB pendrives.

DriveDroid also includes a convenient download menu where you can download USB-images of a number of operating systems from your phone.

You can also create USB-images which allows you to have a blank USB-drive where you can store files in. Another possibility is to use tools on your PC to make a bootable USB-drive out of the blank image that DriveDroid created.

Major Linux Problems or Why Linux is not (yet) Ready for the Desktop, 2012 edition

Major Linux Problems or Why Linux is not (yet) Ready for the Desktop, 2012 edition

Every operating system has its problems.  Some things work better than in others, some do worse.  Here is an interesting (and very up-to-date) overview of the problems in the Linux space.  The good thing about it is that it’s not just bashing Linux over Windows or Mac and it doesn’tjust wine about minor things here and there.  There are issues all over, some are being worked on, and some are not, for a variety of reasons.  But just knowning these issues is already a good start in fixing them.

The purpose of an operating system

I came across a good reminder of the operating system’s purpose in this Slashdot comment:

The point of an OS is to make the software independent of the underlying hardware. Windows lost that independence a LONG while ago (Windows NT / 95). Linux still has it because of the underlying design of the whole thing.

The same comment also brought back some memories of the times when I was working as a system administrator at what is now known as PrimeTel.

Move a Windows server – you can be in for a world of hurt unless you want to fresh-deploy it every time. Move a Windows-client, historically you’d be prepared for blue-screens because you have the “wrong” processor type (Intel vs AMD – requires disabling some randomly named service via the recovery console, for example), reinstalling the vast majority of the drivers (probably from a 640×480 safe mode) and even then can’t be guaranteed to get anything back and working – not to mention activation, DRM, different boot hardware (e.g. IDE vs SATA), etc.

Move a Linux server – unless your OWN scripts do something incredibly precise and stupid with an exact piece of hardware, it will just move over. At worst, you’ll have to reassign your eth ports to the names you expect using their MAC address (two seconds in Linux, up to 20 minutes in Windows and a couple of reboots).

It’s been a few years since I did that.  But I remember vividly how we used to move servers from one piece of hardware to another, and since we used a mixture of Windows and Linux servers, the difference was obvious.  With everything else being equal, we could migrate a dozen of Linux servers in two-three hours, moving them in parallel.  Windows machines took days and had to be approached with very little concurrency.

How far is a desktop from a server?

There is an interesting post at The Open Source Advocate blog – “Win the desktop, and you will win the server“.  Tristan Rhodes, the author of the blog, suggests that in order for an operating system to conquer the server market, it should first conquer (or fight reasonable well for) the desktop market.

I have to admit that when I just read the article, I felt almost like agreeing.  But something kept buzzing me from the inside, so I kept that tab open for a few days.  Now that the post was processed at the back of my brain, I have to say that I don’t agree with that point.

There is, of course, a correlation.  Once sysadmins start using something they like on the desktop, it’s pretty soon that they try to see how well that thing handles server tasks.  So, of course, people using Windows on the desktop were checking out how to make a server out of it.

But.  I don’t think that conquering the desktop is the only way to the server.  Not at all. There are more ways, I somehow feel that those other ways are actually simpler.  For one thing, Linux has never been particularly good with desktops.  However, only the stubbornest and the most ignorant of sysadmins will argue against Linux server superpowers.

Furthermore, real sysadmins (which are, of course, in the minority) clearly understand the differences between a desktop computer and a server.  What’s good for one might not be so good for the other.

And then there is this whole “enterprise” issue.  Big companies (aka “enterprises”) aren’t about desktops.  They are about support services, customizations, and having someone to blame.  If there is someone on the other end of the twisted phone cord, they’ll grab him with both hands.

The historical examples in the Open Source Advocate’s blog post might be related or they might not.  The times were different anyway.  But even if these examples are related, they aren’t as heavy as they seem.  There are many factors to consider (prices, distrubution, documentation, hardware requirements, etc).

What do you guys think?

Recursively renaming files in Linux

One thing I liked about Linux is it’s hidden simplicity. When in a hurry, I usually go for the first working solution of a given problem. If the same problem appears often, I can get used to the first solution so much that I don’t even think about simplifying it.

Continue reading Recursively renaming files in Linux