Linux.com

Home Linux Community Community Blogs

Community Blogs



The Insufferable State of Linux Documentation

I've been waiting for a response from anyone from The Linux Documentation Project (tldp.org). Ghost town projects are normally not such a bad thing - often the page goes down and that's the end of it. Some projects are worth abandoning, as they become obsolete and are replaced by better things.

However, The Linux Documentation Project has been an institution in the Linux Community since 1992. Many of its guides and howtos are still relevant - Linux.com using them is proof enough of that.

The project is in bad need of an overhaul, though. There's little stylistic consistency between pages, the IRC channel (#tldp on freenode) is empty, the mailing lists are no longer a hotbed of activity. The simple steps of getting on the mailing list is made difficult by using an obsolete list program (Mailman could make signing up a snap). You cannot even get anonymous CVS access outside of their ancient CVS viewer.

Half of getting TLDP back on its feet won't even be working with the guides or howto's - it will be addressing the antiquated infrasture of the project itself.

 

Zhu8 On Linux

  就是想来测试一下,貌似新的Linux.com功能很齐全啊!看到kDolphin已经来留了一爪子了。

„ÄÄ„ÄÄPSÔºöË≤剺ºBloggerÂèàÊålj∫ÜÔºåÂîâ……ÂêåÊó∂ÊàëÁúãÂà∞Linux.comÔºåËÆ©ÊàëÊÉ≥Âà∞‰∫ÜOperaÁöÑBlogÊ∞∏‰πÖË¢´GFWԺ剺∞ËÆ°ËøôÈáå……‰∏ç˶ÅËØ¥Êàë‰πåÈ∏¶Âò¥Âïä……

 

A way to find a text string inside all files

# find / -type f -exec grep -l "word" {} \;
 

Learn How to Choose the CMS that’s right for you

Choosing an Open Source CMS is a new book from Packt that guides readers through understanding the different types of CMSs and selecting the one that best fits their needs. Written by Nirav Mehta, this book will help users assess their technical skill level and choose a CMS that combines ease of use with flexibility and power.

Open Source CMSs are the best way to create and manage sophisticated websites. Users can create a website that precisely meets their business goals, and keep the website up-to-date easily because these systems give them full control over every aspect of their website. Open Source CMSs are free to download, and have a vast choice between the various systems.

This book will show users how to avoid choosing the wrong CMS. It will guide users through assessing their website requirements, and based on this assessment, will help identify the CMS that will best fit their needs. It then talks about the major CMSs and the issues that users should consider when choosing, such as their complexity to use, their features, and the power they offer. Users will also be introduced to technical considerations such as programming languages, and compliance with best practice standards in a clear and friendly way.

Additionally, the book highlights many quick-start guides and examples for the most popular CMSs such as WordPress, Joomla! and Drupal. This allows users to experiment with these CMSs, get a feel of how they work, and start using them to build their website. The book also teaches users how to install and customize a CMS with themes and plug-ins. In addition to this, it covers practical tips on hosting, project management, working with specialists and communities, and finding experts.

Developers interested in creating a website by using a good CMS will find this book useful. This book is out now and is available from Packt. For more information, please visit: http://www.packtpub.com/choosing-an-open-source-cms-beginners-guide/book

 

Hello World

Hello World.

–ü—Ä–∏–≤–µ—Ç –ú–∏—Ä.

 

Intro Post

I guess I ought to have an introduction post here on Linux.com.

 I'm a mechanical engineer who loves Linux and has been using it (mostly) full time since 2005.  I got started on Ubuntu using Hoary Hedghog and I haven't looked back.

 I'm currently running Ubuntu Jaunty Jackalope (as of March 2009).  This is the first Ubuntu pre-release I've tried.  It ran well on both my laptop and my desktop.

 I've tried out various incantations of Linux on my laptop in the hopes of getting it working with Linux.  I tried (in no particular order): Mandriva, OpenSUSE, Ubuntu, Kubuntu, Xubuntu, Mint, Fedora, Zenwalk,  Linspire, Freespire,Debian, and PCLinuxOS.  I learned how to fix a lot from that laptop; from wireless drivers that just don't work, to graphics cards that act up, to sound issues.

 Now, I'm happily running Ubuntu.  I prefer Gnome to KDE.

I'm an evangelist for the Flock browser; it's my browser of choice when I have a choice.

Well, that's about it... I like using Ubuntu because it's fun to see what my computer can do under Linux, and to show Windows fans what this old hardware can produce.

 

About Sugar!

Sugar is the graphical user interface originally developed for the One Laptop per Child computer/education project and as of May 2008 being developed under the umbrella of Sugar Labs.

Sugar is used on the OLPC XO-1 laptop computer and is also available as a session option on Debian, Ubuntu and Fedora. Unlike more traditional desktop environments, it does not use a "desktop" metaphor and only focuses on one task at a time.

Main contributors to the project include Christopher Blizzard and Marco Pesenti Gritti, Eben Eliason, Tomeu Vizoso, Simon Schampijer, Dan Williams, Walter Bender, Christian Schmidt, Lisa Strausfeld, and Takaaki Okada. The free software community has also contributed greatly to Sugar. Released under the GNU GPL, Sugar is free software.

It is written in the interpreted Python programming language, whereas most other environments are written in a compiled language such as C. Sugar is also referred to as the OLPC Python Environment. It is composed of the Python language, GTK GUI and Gecko HTML engine.

If you want to get involved with it, search by Sugar Group!

 

Disable write

To disable the write command for a user, add the following line in his .bashrc file:
mesg off
You can turn it back by using mesg on or by simply deleting the line from .bashrc.
 

Nagios - A Fork in the Road

Nagios Founder Ethan Galstad comments on the recent fork of Nagios

http://community.nagios.org/2009/05/11/nagios-a-fork-in-the-road/

"Nagios-A fork in the Road"

As many of you know, a recent fork of Nagios has been announced, accompanied with a flurry of activity in both the community and press. An email thread titled "Nagios is dead! Long live Icinga!" began last week on the nagios-devel mailing list to kick this off.

What are my thoughts on this announcement? I think its one of the best things to ever happen to Nagios.

Why? The announcement of the fork, along with the community's reaction to it has brought to light several things:

  • Community interest in furthering Nagios is at an all-time high
  • Community developers want to get more directly involved in the future project direction
  • Nagios development has been slowed by some bottlenecks
  • When the community perceives a problem, the community reacts
  • Communication within the community needs to be improved

This entire event has seen some ugly misconceptions and half-truths lobbed in the direction of Nagios Enterprises, the Nagios Project, the Nagios Community, and myself as an individual. That's unfortunate.

I am disappointed that no one from the Icinga project contacted me directly about this before the decision to fork was made. One of the reasons that was stated for the fork was lack of communication on my part. The unexpected announcement of this fork clearly demonstrates that there are communication problems on both sides of the issue.

 

Many of the individual developers in the Icinga project did what they felt was best in the situation they believed to be true. They appreciated Nagios, wanted to see it succeed, and wanted to play a direct role in its evolution. Many of them have been very active in the Nagios project and community over the years. Their efforts have been much appreciated by both myself and the community as a whole. To those individuals, I pose this question - If what you wanted to do was help create "the" new Nagios interface and be materially involved in the future development of Nagios, why didn't you just ask? It's apparent that we all need to improve our communication and demonstrate better understanding of each other.

In the course of discussions about this fork within the Nagios community, many concerns have been raised, including: the future of Nagios, the Nagios trademark policy, and the commercialization of Nagios.

In an effort to begin to address these concerns, I have penned some of my thoughts in the following write-ups:

Open Source communities are not a panacea. The sky is not always blue. Anyone who tells you otherwise is likely delusional. Community can be great, and community can be frustrating. Ask anyone with long-term involvement in an Open Source project.

It's interesting to watch how individuals and companies react to situations of distress and change. Challenges can bring out the best and worst in all of us. True intentions, motivations, and personal character are often brought to light. I'm sure that the result of all of this will be a stronger Nagios project and community that endures far into the future.

To those of you who would complain about the state of things now or in the future, the time has come to "put up or shut up". If you see the need for change, you must be willing to materially involve yourself and commit your time, effort, and resources to affect that change. Don't assume that someone else will do things for you, and don't complain if they don't.

As things move forward, I can almost certainly guarantee you that you will not always get what you want and things will not always be done the way you want them to. Neither I, nor anyone else involved in the Nagios project, will attempt to please everyone. That is neither possible, nor beneficial to the overall effort.

I would suggest that we need one more fork for Nagios. That being a mental fork - a change in mindset - rather than a code fork. Lets all work together to improve the way we think, communicate, and affect the direction of Nagios for the better.

Are changes necessary? Yes. Will changes happen? Yes. Is Nagios dead? Hardly.

 Author:  Ethan Galstad

http://community.nagios.org/2009/05/11/nagios-a-fork-in-the-road/

 

 

 

The Importance of Keeping Notes

All Linux Adventurers, but most especially new ones, will find it beneficial in the extreme to keep notes of their adventures as they progress in GNU/Linux Land.

My Linux Notebook is a simple bound composition book that you can buy in any grocery or general merchandise store. It looks like this...

 

... and costs a buck or so. If I had known then what I know now, I would have chosen a loose leaf version. I have many additions to my current notebook. I just slide in loose leaf pages within this existing composition notebook. A loose leaf binder would have been neater.

I divided up my notebook with stick on tabs. They divide the notebook into "General Linux" and "<insert name here>" distributions. I have a tab for each distribution that I've ever installed on any of my systems.

From the very start of the particular Linux adventure, the downloading/burning of the CD/DVD, I am taking notes. I write down the source of the download, the date of the CD/DVD creation, the method and means of partitioning, etc. After that, I take notes on everything that I do to setup and customize the operating system. 

As I continue to use and learn more about the particular distro, I maintain my notes for that distribution. Not only is it helpful in learning the particular ins and outs of a distribution, but it's very handy to have these notes when helping others or when reinstalling months later.

In the General Linux area, I keep all my notes about BASH, general scripting, init script tricks, tweaks for hardware, tweaks for GUI interfaces, etc. Basically, anything that is useful across Linux platforms gets jotted down in this area.

I cannot tell you the number of times in the past 3+ years that having these notes has saved my rear end. If my house caught on fire, I'd grab four things...my three cats and my Linux notebook!

Best of luck with your Linux Adventure!

Until next time...

~V. T. Eric Layton

***Tempus Fugits***

 

Flash, Kongregate, Web browsers and evil dependencies

It seems that for some reson, Firefox (or Conkeror (and from that I reson any xlrunner based browser)) running on Arch Linux x86_64 will not run the Kongregate (www.kongregate.com) flash api that they inseart to their games. However, using midori they all run fine. So the obviouse answer is to install midori, or, if I don't like midori enough for every day useage, install it, and only use it for kongregate.com. Personaly I don't like midori at all, and thus I am using Conkeror to write this blog. But this leaves me in the uncomfterbal situation of having aproximatly 5 browsers install. I have Conkeror for my every day browsing, Firefox for the extensions I can't do without and midori for playing games. I also have konquor for some reson (I don't mind especialy, I love kdemod3) and a couple of other browsers that I was playing about with, trying to get them to comile, and I cba to find the relevent files and remove them now, 6 months down the line. I know, it's shadmin, but it's how I've lived my life so far, and I see no reson to change. But anyway, back to the question. Like president kennedy when it came to the cuban missile crises, I have 3 choices, all of wich leave me unsatisfied. I can continue doing what I do now, using 3 browsers, and adding more as I see fit, thus gradualy losing controll of my machine, and giving the power over to the beast that is dependency tracking, or I can only use one browser, Conkeror, thus missing out on many of the firefox spesific extensions and using a site that isn't kongregate for flash games, or finaly, I can go and mone at adobe or whoever is responicble for the firefox-kongregate incompatibility (kongreagte blame adobe) and see if it gets patched. My current feeling is the first, as I'm lazy, the second one will never happen (I love kongregate and xmarks) and the third will probabaly be done by someone somewhere (I know, not the right attitude, but who cares). Also, out of my pick, Conkeror, Firefox, Midori and Konqueror, which do people like. I never could get into Konqueror, as I felt it was a below standard web-browser, and a below standard filemanager. Someone, please prove me wrong.

 
Page 134 of 146

Upcoming Linux Foundation Courses

  1. LFD211 Introduction to Linux for Developers
    08 Dec » 09 Dec - Virtual
    Details
  2. LFS220 Linux System Administration
    08 Dec » 11 Dec - Virtual
    Details
  3. LFD331 Developing Linux Device Drivers
    15 Dec » 19 Dec - Virtual
    Details

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