Skip to main content

flipping the linux switch

Recently , i bumped on to a site and what struck me most is its title "Flipping the Linux Switch" . There are two words that made be stop and read about the article "Linux" and "Switch". It reminded me a few years back when i was the network administrator of a university. I was part of the team that made the first move towards open source integration not only to the university but to the whole CICM schools in the Philippines. Most of the plans were focused on the shift from Microsoft based computing to Linux based computing. A move that may take several years before properly implemented. The main reason why it needs several years of transition is its effect on the overall efficiency of the workforce because of the sudden change in IT infrastructure. This means long hours of trainings and orientation .

I have been an open source fanatic since i met linux and until now , though using Microsoft technologies on the job, i still doing some things to move to the other side. I know a lot may have tried taking a second look on Linux only to go back to Microsft. The site gave 5 tips on getting easy with a new OS. It means trying it out and not getting dissapointed in the end . These includes:

1. Experiment with LiveCDs - Yes , linux comes with a LiveCD and you can simply have a taste of it without even going through the process of installing it in your machine. You can visit this site to request an Ubuntu linux for FREE. If you want more than the live CD , try making use of a free virtualization software such as VMWare . Microsoft also have a free Virtual PC software but i had a hard time making Ubuntu run on it .

2. Install /home on a separate partition .But it's probably the single most useful thing to know as a Linux user, and will make management and any subsequent installs of your system a whole lot easier.

3. When in doubt, use the vesa drivers!.Graphics support is sometimes an issue with Linux. Many distros give you the option to configure your card if it is not immediately recognized by the system. This is where a lot of new users get tripped up. They tend to pick the driver that seems closest to their graphics card model. Sometimes they're lucky, and it works. But if you're a brand new user, your safest bet is to use the vesa driver. You won't get fancy effects, and it'll look ugly, but you will have a graphical interface. You can then search for the correct drivers for your card.

4. Fear not the command line. You don't need to be a guru to use the command line. Sometimes the quickest, easiest way of getting to the root of a problem is to whip open a terminal, and type the name of the program you want to run. If it's segfaulting, or can't find a component it needs... the output will tell you. The command line often gives you hooks to dig into a problem, whereas just clicking on the launcher might just get you an endlessly bouncing cursor and nothing to go on. Linux is particularly forthcoming with useful error messages, but you need to know where to look.

5. Ask for help before you get frustrated.

Making the switch to Linux can be intimidating, but it doesn't have to be. There is a lot of advice out there, some good, some bad, and some that just won't apply to your situation. With these five tips in your arsenal, you're well on your way to a positive Linux experience.


Popular posts from this blog

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python.

The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below:
Copy and paste the lines below :


renaming default namespaces for VSTO projects in VS2008

So here is the scenario , you are starting a VSTO project and decided that your default namespace is ExcelAddInTesterApp . You created the project and started coding the project. After several days , your boss called and said "hey marvin , make use of this namespace OurCompany.ExcelAddInTesterApp , we have to add our company name to it got it?" . You get back to your machine thinking its just a simple property just like any project you've been working on. So you right clicked the VSTO project and hit properties . Boom! What the F@#$? The default namespace textbox is disabled!!!!

I've been through this and I googled for ways to do it and ended up with a blog from a Microsoft MVP telling me it can't be done because it is disabled. Then I thought of Refactoring, the beauty and grandeur of the renaming process. I selected the namespace and hit the refactor menu hoping that this would solve the problem . Unfortunately , it did not rather it displayed the message box …

Automatic Properties and Object Initializers in .Net 3.5

With the release of .Net 3.5 alongside with Visual Studio 2008 , new enhancements was again introduced . Some maybe well pronounced such as the inclusion of WCF, WPF , LINQ in .Net 3.0 and some just came unnoticed. If you have been accustomed of using a particular method or technique in implementing a certain code in .Net 2.0 , because of backward compatibility , you may not even notice that there are new ways of implementing it in .Net 3.5.

Here are two new concepts in .Net 3.5 that a developer may not notice ( at least in my opinion ) : Automatic Properties and Object Initializers . To illustrate these two , I am going to present the pre-.Net 3.5 way (.Net 2.0) and the .Net 3.5 way in creating a simple class with simple properties.

Automatic Properties

Creating a class can be tedious , especially when working with a list of properties , . One way to get around having to type the code for a private field and its public property getter and setter is to use a refactoring tool. However, …