Community Blogs

Kill the clients.

Heres a trivia for you all. Whats the single thing that creates most of the problems in an enterprise setting and what is it that demands such high level of conformity on the workstations? Why is it so hard in getting Linux into a organisation built on Windows technology?

 Its not security, management or  costs that makes corporations spend silly sums on certifying workstations and images. Its all about making various clients for databases work on the computers. Most clients are no more than very simple logic ontop of a database. Still very many of the client software demands a specific OS, a specific version and a specific level of patches. Add to that a good likelyhood that another client application demands another set of patches and your in for some really fun game of minefield.

 If more corporations would demand web applications (not .exe files disguised as web apps like .net or ActiveX) this problem would go away pretty fast. It would also solve the problem as old as the computers themselves, how do i access my stuff from outside the office, at home or  from abroad? A web application demands nothing more of the connecting computer than a browser if done right.

 The "problem" with Linux in most corporate enviroment isnt Linux itself at all. Its that it doesnt support the client applications.  The same goes for using any other OS for that matter.  Netbooks, smartphones and pretty much any gadget with a browser is out of the question without serious money poured into a ported client application to that perticular gadget. We are prisoners to our own networks more or less and cant really use all the various new exciting technology at all. The apps keeps us ten years back in time.

 Killing the client software is essential in freeing our networks and i strongly suspect Microsoft has long since realised this. The moment the database in the backend is decoupled from specialized client software and instead coupled to a webserver the race is more or less over except for games. 

 Nobody really wants policies, profiles, patchlevels, .msi packages and the living hell it creates but its just not possible making things work with the current model of connecting to our backends.

 What we in the open source community can do to better this is to not fall for the local client model and build all our services for the web. Things like Evolution, OpenOffice Base and Thunderbird should be  thrown in the dust bin and replaced with excellent web interfaces instead. Why would we want to create the same mess thats already rampant on the other side?


A bit of opinion

Well I just joined's community and I thought it would be nice to share a bit of opinion of the whole layout.


 I think they did great setting this up, it should bring the community closter together. I do like the general site, I just have to get use to it. 


So congratulations to the employees for creating a great networking site.


To print n lines of a file

To print N lines of a file from <start> to <end>


sed -n '<start>,<end> p' filename


To print line 10 to 20 from the file knol.txt
sed -n '10,20p' knol.txt
To print line 10 to end from the file knol.txt

sed -n '10,$p' knol.txt

To print nth line of a file

sed -n 'p' filename



Linux Mint Neueinstieg

Vor einigen Tagen bin ich nun von Ubuntu 9.04 auf die aktuelle Beta-Version von Linux Mint 7 umgestiegen und muss sagen, dass ich sehr begeistert bin. Eigentlich ist Linux Mint nichts anderes als Ubuntu mit ein paar Modifikationen, wie beispielsweise das Mint-Menü oder  die veränderte Software-Verwaltung namens mintinstall.

True Blood

In the last few days i watched the first season of True Blood. The story is a bit weird but somehow it gets interesting nevertheless and i enjoyed it.

 The story basically it that japanese scientists found a way to produce blood so that vampires can have a life like everyone else except that they are immortal and sleep while the sun is shining, of course. The "heroine" of the story is Sookie Stackhouse who can read thoughts and is the only one in the town who is open minded enough to hang around with a vampire.

If you now think "Oh, i like Twilight i have to watch this.", don't watch it you will be very disappointed. For those of you how think that a vampire story could be interesting but don't like Twilight True Blood might be worth watching.

Anyway midnight just passed so i will end this post and go to bed. I have to wake up in 6 and half an hour to write my last and most important english exam for this year.

P.S.:The link stuff in this editor is definitly to complicated in 99.9% of all cases. Seriously who needs all these options?


My First Linux Install

I think I performed my first Linux install in 1995.  I know it was done using the slackware distribution.   It took about 35 floppy disks which I downloaded at the University of Kansas Herb Harris Computer Lab.   I installed on my only computer which was a 386sx with probably a 20 megabyte hard drive and about 8 megabytes of RAM.  I'm pretty sure it was only 8MB because I remember thinking that if I had 16MB then I could run X Windows.


Just got here to - Heard about it from the LinkedIn group and I think it's great!!!

 Loving it!



Sometimes, you need to kill boars to succeed

I just watched a funny South Park episode about World of Warcraft. In it, the boys need to kill a countless amount of (virtual) boars in order to become strong enough to save the World (of Warcraft).

That got me to thinking about what Linux and OSS needs a lot of right now. We've got super smart people, and great software. But to pull it all together, it'll require killing a lot of boars.

That means there needs to be better documentation (even if only consolidating wisdom that's scattered across forums), more polish, and other generally "un-fun" stuff. I've done a lot of work with printers. Considering I don't personally own a printer, that is killing a boar. Nevertheless, the printer languages, performance, and whatnot still need to be documented.

Essentially, to bring Linux to the big time, we're all going to have to kill some boars.


NOOB's adventures in Linux From Scratch


This being my second installment I'm starting to read my first prerequisite

The first problem I've run into here is there seems to be many different kinds of packaging.... tar or gz or bz2 all different programs all requiring different commands to " unpack" . Windows has been easy on me just click on it and bingo it's installed.

Not so lucky here , I have to learn about how to unpack source files.... o, O...

I'm in trouble already....

The above method of unpacking "tarballs" is equivalent to either of the following:

  • gzip -cd filename | tar xvf -
  • gunzip -c filename | tar xvf -

(The '-' causes the tar command to take its input from stdin.)

What in the heck is "stdin"? time to google....

Ok, I got it... stdin = standard input .. hrmmm.... OK..

this begs the question what's standard input?

Standard input is data (often text) going into a program. The program requests data transfers by use of the read operation. Not all programs require input. For example, the dir or ls program (which displays file names contained in a directory) performs its operation without any stream data input.

ok ... so I type the command and the computer reads what I type as "stdin" and then the program does what I told it ? I think...

but the "-" is in front of the cd in the commandline? I thought that would be part of the gzip command...

I think I need to go back to the prerequisites and look at the list again. I'm confused. Maybe another prerequisite is more important than software building at this point.


The Linux Users' Guide

As I'm reading down the page , I'm a bit overwhelmed by some of the information and jump ahead to the part that says who should read this book

Ok, I'm good .. but wait .. there's another link " what you should have done before reading this book."

Ok, I should have an intel x86 pc with Linux installed.

Next you should have created a User , not to run as the administrator.

It goes on to say that you should know some computer terms... I might be in a bit of trouble depends on the word..

This book goes on to say experiment, read the man pages installed , myself I find that man is not enough.. info pages are far better and google also has alot of information about each program , sometimes I even go to the home page of the program , I've backed up to do this blog... in my adventures so far It took me about 2 or 3 hours just to learn how to download from a list of source files using the wget program, but it was well worth it. I found it very refreshing to see all those programs download ... silly I know but it took alot of work , more than I'd ever tried on Windows. I was ignorant enough the first few times to point and click on each of ... I think it was about 80+ files to build LFS. Took a long time.... so I 'm starting to see some really neat stuff about Linux.

OK ... this looks like I've found the right place to start.... maybe I should let them know that the users guide would be better placed at the top of the list.On the LFS website.

whew, it's a bit deep... After some experience with Linux, I know one thing where it pertains to me. I can't just read something. I have to study it and If I'm ever going to properly build LFS, I 'll have to learn alot more than just what's been written on the pages of the prerequisites.

My own education it's now becoming painfully obvious is less than it needs to be as I'm studing these pages .. I'm running into words like fork, signal mask, synchronous and asynchronous...

Google to the rescue!!!

next blog- Unix Shell ...oh boy :)




NOOB's adventures in Linux From Scratch

I've played around with Linux a bit in the past, edited files and even compiled a few kernels with step by step hand holding but nothing puts the fear of God into me like the Linux Shell....

In the following chapters of the Linux User's Guide they're covering some of the commands of the Unix Shell../Linux Bash default shell. { I think I hear whispering in the background, no that's laughing... somebodies been watching me at the command prompt} Let's just say that I'm bash shell challenged and leave it at that :)

This is my second or maybe third time that I've read a User's guide where Linux commands are explained. I can only tell you from my own limited experience that precision is required. I would go on to tell you that make sure you comprehend not just read what you are learning in this part of the book because it will save you alot of aggravation in the long run. I personally would like to see some exercises added like in a math text book where you are given a problem and you have to solve it then you could go look up the answer and how the author came about getting it. I'd feel more pripaired

Shell scripts are going to be used in the LFS build, when the errors occur and believe me at one point or another they will.... the fine folks on the mailing list and the LFS support irc site will want you to know enough about what you are seeing, as you look through log files that you can decipher enough to properly select the error in that file so you can send it to them without sending the whole file.

I've read the whole section and I feel ill - pre-paired to do almost anything other than copy some files and move around in the file system.. I'm going to look ahead in this book and see what they have in store ..

  Ok, I don't understand the reason, but mine is not to question why.... leaving the Shell for now... next time we'll be peekin' into  X windows they take us back to the shell later in the book ;)




How Should I Go About This?

I am a teenage at high school and like most high schools they run Microsoft Windows.  There are some computers at the school which really do NEED to run Windows.  However, most don't.  The ones that do need to run Photoshop and Flash.  Those are in the computer lab.  However, there are the ones in the library.  These are ancient, and I mean ancient, beige boxes.  They run XP, but they can barely handle it.

 I've talked with my Computer Science/Engineering teacher and he wants to set up a Linux lab but the technical administration won't let him because they don't want to learn about Linux.

Now, I live in a mid-sized school board.  I also happen to work at the company which prepares the computers the board uses.  They would save hundreds of thousands of dollars - if not millions - if they re-equiped the computers with Linux.  The students would have more resources and faster computers.  Administrators wouldn't have to deal as much with some very clever "hackers" (not malicious, but could definitely cause headaches) at our school.

These administrators must not be dumb people.  They've set up a system that - most of the time - works.  They're switching over to ActiveDirectory (from Novell Netware, which was ancient) and AD by all accounts works just fine in Linux.  They aren't even managing a Linux server.  This is a school.  A public school.  The administration has the dual responsibilities of making sure that the money of taxpayers is being well spent and that students get what's best.  In this case, it is not Windows.

What I would like, dear community, is a link to a set of letters or something that can be given to administrators of a school or business or other such institution that has anything against Open Source Software.  If they don't exist, shouldn't they?  Shouldn't we, as a community, formulate a clear, articulate response to further our cause?

Food for thought.  If these letters or models for these letters exist please comment! 

Page 124 of 132

Upcoming Linux Foundation Courses

  1. LFS230 Linux Network Management
    06 Oct » 09 Oct - Virtual
  2. LFD331 Developing Linux Device Drivers
    13 Oct » 17 Oct - Virtual
  3. LFS430 Linux Enterprise Automation
    13 Oct » 16 Oct - Virtual

View All Upcoming Courses

Who we are ?

The Linux Foundation is a non-profit consortium dedicated to the growth of Linux.

More About the foundation...

Frequent Questions

Join / Linux Training / Board