While I wasn’t there from the very start of Linux. I was an early adopter. Even before Linux, though, I was a Unix desktop user ranging from the early character interfaces such as the Bourne shell to graphic Unix desktops such as SCO’s Open Desktop—better known back in the day as Open Deathtrap—and Solaris’s Looking Glass. In the last twenty years I’ve used almost every significant Linux desktop out there, and was the editor-in-chief for many years of Desktop Linux. In short, I know what I’m talking about.
Before giving you my list of favorites though, if you don’t know my work, you should know where I’m coming from. First, I’m a big believe in What Works. I use Linux on my desktop not because I find its free and open-source software foundations morally superior to the proprietary competition from Apple and Microsoft. I use it because it works better for me. When it comes to technology, I’m a pragmatist, not an idealist.
That said, I do think open-source is ethically better than other methods of creating software, or anything else. But given a choice between an open-source program that doesn’t do its job and a proprietary program that does the same job superbly, I’m going to use the latter.
That’s why, for example, I use Adobe Flash Player for Flash video rather than Gnash. The Adobe player is, for now, clearly the better player. That’s also why I use commercial audio and video codecs. It would be great if everyone used open media codecs such as Ogg Theora, but they don’t, and I’m not going to annoy myself or anyone to whom I recommend Linux by telling them they must use only open codecs. Maybe HTML5 will finally get it act together on this point and we won’t need to worry with proprietary codecs, but I’m not holding my breath.
I also like operating systems that are both easy to use and give me the option of digging deep into their mechanisms so that I can set them up to work exactly the way I want them to work. That’s why, generally speaking, I prefer KDE to GNOME for my Linux desktop.
5) SystemRescueCD.
OK, so this one isn’t a Linux desktop per se. I have to mention it though because regardless of what desktop you use, if you’re at all tech. savvy you must have a copy of SystemRescueCD. Just like the name says this is aa system rescue operating system. You can use it as a bootable CD-ROM, USB stick, or even over a network connection. While you can use it as a desktop in own right, its real job is repairing crashed systems. In particular, with its disk and file system repair tools, it’s great for bring dead hard drives back to life.
With Linux disk and file tools like parted, partimage, fstools and many others, and support for almost all Linux, Unix and Windows file systems, such as ext2/ext3/ext4, FAT, JFS, NTFS, ReiserFS, Reiser4, and XFS, I have yet to find a hard drive that could still spin that I couldn’t at least pull data from with SystemRescueCD.
I’ve managed to get data out of Windows systems with rootkits on their boot sectors and other disasters where the usual suggestion is to blast the hard disk down to its cold, dead magnetic surface. This is no tool for a casual user, but if you’re a technician or play one for your family and friends, you must have this distribution.
4) OpenSUSE 11.4
I used to love openSUSE. I wish I could say I love openSUSE 11.4, but I can’t. It’s just feels a little too… klutzy. That said, I like its KDE 4.6 interface.
While I’m not crazy about openSUSE as a pure desktop, I love it as a server. While I have lots of good things I can say about Red Hat Enterprise Linux (RHEL) and its clones such as CentOS, for working with a server at its desktop, I like the openSUSE approach. That’s why while I use CentOS for my Web and other outward facing servers, I use openSUSE for all my intranet Linux servers. It just makes managing server software so darn easy.
3) MEPIS 11
I’ve always had a soft spot for MEPIS . It’s a Debian-based desktop Linux distribution that uses the KDE desktop. I like it a lot because it simply works. I almost never have any trouble with it—and when you beat up on desktops the way I do I always find the bugs! All Linux distributions tend to be stable. MEPIS is bedrock stable.
The only reason I don’t rate MEPIS any higher is that it’s a one-man shop. Warren Woodford, and his fans and supporters, are the only “organization” behind this Linux distribution. That means it’s fine for experienced Linux users who can handle their own support. But, if you’re new to Linux, or just not sure of yourself, I can’t recommend MEPIS. If you know what you’re doing, though, check it out. MEPIS is a great distro.
2) Ubuntu 11.04
This one may surprise some of you since a lot of people don’t like Ubuntu 11.04’s new Unity interface. I do like it. Oh, I’m not crazy about it for me. It’s way too simple for my tastes. I want a Lot more control over how the Unity application dock.
So why do I like it, because if the Linux desktop is to have any chance of pushing Linux over the 1% mark of total desktop use, it’s going to be because of Ubuntu in general and Unity in specific. Unity is meant to tempt Windows and Mac users to Linux. I think it has a shot at doing it.
Unity will never be my favorite interface, but if it can bring more users to Linux than I’m all for it.
1) Mint 11
Yes, it’s GNOME-based, but it uses, to my eye, the superior older GNOME 2.32 instead of GNOME 3.0. What I like most about Mint 11, is that its interface is easy to use, but I can get my hands dirty when I need to tune it up.
I also like that it’s built on Ubuntu. This means that it gets support for the most popular open-source programs, such as Firefox and LibreOffice, as soon as they’re available. As far as I’m concerned, if you’re an experienced Linux user, and you’re not wedded to KDE, Mint’s the best of the current Linux desktop lot.
Click Here to Read more!
Hacking tools tips and tricks for hacks,hardware,software,OS,Windows,XP,Vista,Linux,Troubleshooting,Computer Repair,Data Recovery,Online tools
Showing posts with label Linux. Show all posts
Showing posts with label Linux. Show all posts
Wednesday, July 6, 2011
Friday, December 3, 2010
Red Hat Tips and Tricks
1) Wiping a hard Drive
Have you ever needed to completely wipe out critical data from a hard drive? As we all know, mkfs doesn’t
erase a lot. (You already knew this, right?) mkfs and its variants (e.g., mkfs.ext3 and mke2fs) only get rid of a few important data structures on the filesystem, but the data is still there! For a SCSI disk connected as /dev/sdb, a quick
dd if=/dev/sdb | strings
will let anyone recover text data from a supposedly erased hard drive. Binary data is more complicated to
retrieve, but the same basic principle applies: the data was not completely erased. To make things harder for the bad guys, an old trick was to use the ‘dd’ command as a way to erase a drive.
Note: This command will erase your disk!
dd if=/dev/zero of=/dev/sdb
There’s one problem with this: newer, more advanced, techniques make it possible to retrieve data that were
replaced with a bunch of 0s. To make it more difficult, if not impossible, for the bad guys to read data that was previously stored on a disk, Red Hat ships the “shred” utility as part of the coreutils RPM package. Launching “shred” on a disk or a partition will write repeatedly (25 times by default) to all locations on the disk.
Note: Be careful with this one too!
shred /dev/sdb
This is currently known to be a very safe way to delete data from a hard drive
2) USB when the Drivers not available
As a way to save a few valuable pennies on newer PCs, manufacturers are increasingly getting rid of the good old PS/2 keyboard and mouse interfaces. As a result, some recent systems only ship with USB ports to which we need to connect a USB keyboard and mouse. USB is all well and good, but what if the driver for your USB controller is not loaded? In practice, this is not a problem, as Red Hat loads the ehci- hcd and uhci-hcd drivers automatically at boot time. There are situations, namely in emergency mode, where the USB drivers won't be available. So you won't even be able to enter a command. This is due to the fact that in emergency mode all drivers need to be provided in the initrd file under /boot, and USB is not there by default. The trick is to add those drivers, so that they will be available earlier. The 'mkinitrd' command can do precisely that with the '--with' argument (this only works under RHEL4):
mkinitrd --with=ehci-hcd --with=uhci-hcd /boot/newinitrd-`uname -
r`.img
`uname -r`
Add a new entry in your grub.conf file (always do backups!) that points to this new initrd image, and you're
done! Your USB keyboard now works in emergency mode.
Click Here to Read more!
Subscribe to:
Posts (Atom)