To display the most relevant entries to you in priority,
vote for the stories you are interested in
(  )
and reject those that you are not interested in
(  )
Planet Ubuntu -
2 hours and 54 minutes ago
Nearly a week after its release, I suspect most of my audience has seen the FSF's Freedom Fry
video of Stephen Fry wishing the GNU project and the free software movement a happy birthday.
While I'm not usually one for
birthdays, I thought I'd at least reflect on it briefly. Certainly, it's a wonderful video --
for which Matt Lee at others at the FSF should be proud. But it's fact that the GNU project is
now twenty-five years old that is truly noteworthy.
Wikipedia says that a
generation (i.e., the average interval between the birth of parents and of their offspring) is
somewhere between 25-30 years in most of the Western world. Twenty-five years isn't just a big
number divisible by five, it marks a generational shift.
Certainly, GNU has matured and accomplished wonderful things in last quarter-century. More
importantly perhaps, it's produced wonderful progeny. It has spawned hundreds of thousands of
free software projects, thousands of free or nearly-free operating systems, and an unbelievably
vibrant global free and open source software community. Beyond the software realm, the free
culture movement, most free licensing projects, and much of the access to knowledge movement can
trace a connection back to GNU. We are living, and building, a new generation of the free
software movement.
It's not been an entirely smooth ride, feelings have been hurt, and it's hard for GNU's
proponents -- myself included -- to not wince at some of what has been done in GNU's name and
because of its example. But even cynics must admit: the world is an undeniably better place
because of GNU and the efforts and ideas that it has motivated.
I turn 28 in December and have spent my entire computing life in world where free software was a
viable option and an active form of resistance. Here's to another generation! May we be half as
productive and positive as the last!

|
Planet Ubuntu -
6 hours and 57 minutes ago
It’s been a while since I last posted on my blog. The “downtime” had several
reasons:
- I participated in Googles Summer of Code this year and was quite busy due to that (blog post
for that is on its way).
- I didn’t want to use Wordpress any longer.
I never planned to quit blogging completely because there’s always stuff coming to my mind
that I want to make accessible to a wider audience. So now I sat down and worked on a new blog
using Zine. Zine (formerly known as TextPress) is a
python-powered blogging application similar to Wordpress. It is quite easy to write plugins and
themes for it and since I use to program in Python I chose this awesome (but not yet released)
piece of software. I didn’t migrate my old postings over from wordpress (although
there’s a converter) because I want to change my style of writing a bit (e.g. no smileys
anymore). Any link out there pointing at my old blog will be redirected to this very post. If you
want some old posting, just contact me by either mail or comment. I keep the database alive.
As of that, I also changed my hackergotchi since the old version somewhat resembled a
criminal. (Just in case you were wondering who I am.) I have to thank my fellow student and
friend Alvaro for spending several hours with me, testing his
new camera and producing the photos.
The new blog is dressed in a theme that I wrote, supported by my buddy Arne. Thanks so much for providing the graphics and coming
up with the basic layout idea! (I cannot count the many days of work he put into that. I owe you
a beer.)
Expect postings from me at a much higher rate now. I’ll try not to flood planet ubuntu too much, though. (Due to excessive testing there
should be no remaining bugs, but one can never know for sure. If you notice anything, please drop
a comment to this post.)

|
Planet Ubuntu -
7 hours and 8 minutes ago
- Microsoft
sends experts into Apple stores to educate staff about Free Software.
- The Free Software Foundation sends experts into computer stores to
educate customers about Windows Vista.
At least I think I have that right.
|
Planet Ubuntu -
14 hours and 18 minutes ago
Oh well, I was busz at work and I just wanted to go out of our office at 7pm.
This did not work out....
Upstream Sput of Quassel fame was proposing to have a beer...and somehow he proposed to watch
"Batman, The Dark Knight" ...
Well yes, super goody movie, but now, it is Saturday and I am still at Sputs place to drink beer
and watch this guy named "Jeff Dunham". Hopefully political correct north american US people know
this guy cause he is right ;)
|
Planet Ubuntu -
14 hours and 32 minutes ago
With Magifab (Fabian) as invited, navelson and an excelent grup of enthusiasts Ubunteros, in El
Salvador, they are doing a UBUNCON, you can join it in live in: http://giss.tv:8000/celvin.ogg.m3u
No doub to connect, and join
CONGRATS to UBUNTU-SV :D
|
Planet Ubuntu -
17 hours and 40 minutes ago
 I have recently set up a
small LTSP network for an association in my street. Some days
ago, I was asked if it was possible to display photos on all of the LTSP machines at the same time
to show the activities of the association. This is of course very easy to set up, but I didn't want
to leave keyboards or mice on the computers, to make sure nobody would exit the photo program or
try to reboot the machine.
The quickest solution I found to do that easily was to use synergy and wireless keyboard and mouse. Synergy allows to
share keyboards and mice between several computers, running Windows, MacOS or Linux. It actually
goes further than this, since you can also copy and paste contents (text, images, etc) from one
computer to another. The down side of it is that it's not secure, but that was not a problem in my
case at all.
So in my case, I just started synergys on the main machine (the LTSP server) having set virtual
screens in synergy.conf for all the ltsp thin clients. Then I started synergyc on each client with
synergyc --name ltsp1 localhost, adapting the name for each machine. Finally, I removed all
keyboards and mice from the computers and only left the wireless keyboard and mouse on the LTSP
server. This left me with a group of computers without any keyboards or mice plugged to them, which
could each be controlled by a wireless devide, by simply dragging the wireless mouse from a screen
to another. All that was left to do was to launch the slideshows on each machine and hide the
keyboard and mouse in a corner, to be used only when necessary.

|
Planet Ubuntu -
19 hours and 5 minutes ago
This is a very familiar question I am sure many of you have come across from your non-FOSSy
friends. I have it always coming from loads of people including my mom who asked “What is
this Linux thing you have all around and what are you getting out of it?”. As it always
happens with most moms she just doesn’t get it.
Well now, I have been replying to most of them with a standard “I dont know, may be becuase
I am having great fun??”. Now I got the answer for that question. Apt and fits me. I always
wanted to make a difference to others and myself, hence this is the answer to this golden
Question.
I am having FUN and making a DIFFERENCE
I got this answer from Pramode and Swaroop’s blog post. I
also would like to take this opportunity to appreciate and congratulate the updates Swaroop has
done to his book “Byte of
Python”. Great going Swaroop! Keep it going. You ROCK!
|
Planet Ubuntu -
1 days ago
 While the collection of
available Augeas modules is increasing dramatically, there is more and more of a need for a good
documentation. Some time ago, R. I. Pienaar (aka Volcane) made a proposition to write standard
inline documentation in Puppet modules, using
the NaturalDocs tool. I thought I would just try to see
if it could easily be used to document Augeas modules.
After few attempts, I found that I was rewriting all my code in the comments, and that was not very
optimized, so I wrote to NaturalDocs's developer, Greg Valure, to ask him about how hard it would
be to support the Augeas language in ND. Not only did he answer quickly, but he provided better configuration files ND, aswell as a Perl Module to enhance Augeas's support
in ND! Thank you very much Greg, you are a great help!
So I spent some more time trying to enhance the commentaries in the example modules I chose. After talking with
David about it, we still feel like it would be better if we didn't have to prefix every declaration
with a comment to get it included in the documentation, and if parameters and parameter types could
be detected automatically
by parsing the code. From what I understand, all this should be possible with ND by improving the
Augeas.pm and ideally turning it into a full language support Perl Module. One down side of this is
that ND is currently being rewritten in .Net/Mono, so the current work on Perl modules will not
work with ND 2.0 anymore.
I spent quite a few hours yesterday modifying the CSS stylesheet to match the Augeas website.
Now for the demo: you can see it here!

|
Planet Ubuntu -
1 days and 2 hours ago
Augeas 0.3.1 is out! This is the announcement from the augeas-devel
mailing-list:
I am pleased to announce the release of Augeas 0.3.1; it has been much
longer than I'd like since the last release, and this release contains
many more changes than is betrayed by the small change in version
numbers.
There has been a tremendous amount of activity both in enhancing
existing lenses and in writing new ones. I have tried to keep track of
all the contributors in the NEWS - if you sent a patch and didn't get
credit for it, please remind me (gently ;) With that much activity in
lens-writing, I feel that we need to figure out a way to indicate which
lenses we consider 'finished' and which ones we consider 'experimental',
so that users know where changes in the tree are likely.
The release can be downloaded from:
Tarball: http://augeas.net/download/augeas-0.3.1.tar.gz
Fedora RPM's are making their way through the build system
Detailed NEWS:
- Major performance improvement when processing huge files, reducing
some O(n^2) behavior to O(n) behavior. It's now entirely feasible
to manipulate for example /etc/hosts files with 65k lines
- Handle character escapes 'x' in regular expressions in compliance
with Posix ERE
- aug_mv: fix bug when moving at the root level
- Fix endless loop when using a mixed-case module name like
MyMod.lns
- Typecheck del lens: for 'del RE STR', STR must match RE
- Properly typecheck the '?' operator, especially the atype; also
allow '?' to be applied to lenses that contain only 'store', and
do not produce tree nodes.
- Many new/improved lenses
* many lenses now map comments as '#comment' nodes instead of just
deleting them
* Sudoers: added (Raphael Pinson)
* Hosts: map comments into tree, handle whitespace and comments
at the end of a line (Kjetil Homme)
* Xinetd: allow indented comments and spaces around "}" (Raphael Pinson)
* Pam: allow comments at the end of lines and leading spaces
(Raphael Pinson)
* Fstab: map comments and support empty lines (Raphael Pinson)
* Inifile: major revamp (Raphael Pinson)
* Puppet: new lens for /etc/puppet.conf (Raphael Pinson)
* Shellvars: handle quoted strings and arrays (Nahum Shalman)
* Php: map entries outside of sections to a '.anon' section
(Raphael Pinson)
* Ldap: new lens for /etc/ldap.conf (Free Ekanayaka)
* Dput: add allowed_distributions entry (Free Ekanayaka)
* OpenVPN: new lens for /etc/openvpn/{client,server}.conf (Raphael Pinson)
* Dhclient: new lens for /etc/dhcp3/dhclient.conf (Free Ekanayaka)
* Samba: new lens for /etc/samba/smb.conf (Free Ekanayaka)
* Dnsmasq: new lens for /etc/dnsmasq.conf (Free Ekanayaka)
* Slapd: new lens for /etc/ldap/slapd.conf (Free Ekanayaka)
* Sysctl: new lens for /etc/sysctl.conf (Sean Millichamp)
David
An updated package is already in Debian, thanks to Free, and Nicolas (aka nxvl) will try to get an
exception to include it in Intrepid before it's too late.
In other news, I'm likely to give a talk on Augeas at the JM2l in Sophia Antipolis.

|
Planet Ubuntu -
1 days and 4 hours ago
I love the Ubuntu Wiki, and I think the Official Ubuntu Documentation is great! These are two
important reasons why Ubuntu has been such a successful Linux distribution.
But at the end of the day, I’m a terminal-and-manpage kind of a guy.
Earlier this year, I found myself on IRC answering basic questions from an Ubuntu user about some
random utility, and I asked him if he had read the manpage yet. He responded that he
had read whatever he could find on the web, but he didn’t really dabble on the command line
in general.
It occurred to me that there may well be a contingent of Ubuntu users who are entirely
disconnected from the wealth of resources so many developers have poured into manpage-based
documentation.
A cursory search turned up a couple of RH-based, or advertisement-riddled Linux manpage
websites. I also found manpages.debian.net,
which is closer to the Ubuntu target, but unfortunately, the pages are CGI-generated and thus not
indexable by Google/Yahoo.
So I submitted a request-for-comments to the
Ubuntu Documentation team, and no one could point me to an existing web repository of
Ubuntu’s manpages. I started the obligatory Launchpad
Blueprint, Wiki Specification,
and Bazaar project.
And as of today, the Ubuntu Manpage Repository is live at:
This site contains nearly 300,000 HTML viewable manpages included in Ubuntu releases (Dapper,
Feisty, Gutsy, Hardy, Intrepid) and across all of (main, universe, restricted,
multiverse) and across all languages where manpages are available. It is
automatically updated daily.
I expect there are some remaining issues, or oddball manpages missing from the archive due to not
matching my regular expressions. I invite you to file bugs against the
ubuntu-manpage-repository Launchpad project.
The site also hosts the gzipped manpages too, and I’m working on a patch to man(1) that would optionally
fail over to remotely retrieve a requested manpage if not found on the local system.
Thanks to Kees Cook, Jamie Strandboge, and Colin Watson for their patches and code review, as
well as LaMont Jones for helping bring the site online!
:-Dustin


|
Planet Ubuntu -
1 days and 5 hours ago
 *tap, tap*
Hello to everyone on the Planet!
I am diving into this thing called blogging, lets see how I do.
My name is Clay Weber, claydoh on freenode
and just about everywhere on the intarwebs I can.
I am a 42 year old restaurant manager from Brewer, Maine, US and have been using Linux since 2000,
and made the complete switch in February of 2002.
As a confirmed KDE user, Kubuntu became my distro of choice
sometime after Hoary's release, and I am a moderator at kubuntuforums
I became a Kubuntu member back in February, but have just recently decided to try out blogging. I
do not have any coding, development, or artistic talents so my viewpoint is that of the average Joe
User, at least as much as someone using Linux daily for more than six years can be considered
'average'.
In my spare time (such as it is after 50+ hours a week at work) I run a website for our local
flyball team as well as
one for our Agility team. Yes, that does mean I am a Dog Person :)
That pretty much sums me up.
Feel free to look me up if you have any questions or comments.
And, yes I do plan to get a proper hackergotchi at some point. Honest.
Thanks!
claydoh

|
Planet Ubuntu -
1 days and 7 hours ago
The linux client for Dropbox is now available.
To put it simply - you run a client on your computers, and it syncs a ~/Dropbox directory with
the Dropbox web service (which uses Amazon's S3 as their backend). You now have all the stuff you
cared about synced with your desktop, your laptop, etc. As a bonus you can share directories with
friends AND the web interface has built in per-file rollback version control. It's pretty hot.
More info
here. I use it for my wallpapers, documents, and even some dotfiles that I want on all my
PCs.
Anyway this tool is a godsend if you have multiple PCs and whatnot, and it's the only tool in
this space that I've seen so far that even tries to support Linux, and it's the simplest tool of
its kind I've seen so far, so I give it a thumbs up.
Download here. (Note, you need an invite, and I am
out, but I've given a bunch out yesterday and today to a bunch of Ubuntu people on identi.ca, so
either ask around or check out their forums or something - and yes, only the nautilus plugin is
GPL, the client and server are closed; so before you lecture at me go fix iFolder first plskthx.)

|
Planet Ubuntu -
1 days and 12 hours ago
Question:
What is the different between:
fd = open("/tmp/foobar.bin") while True: chunk=fd.read(CHUNK_SIZE) if not chunk: break print
len(chunk)
and
fd = open("c:/tmp/foobar.bin") while True: chunk=fd.read(CHUNK_SIZE) if not chunk: break print
len(chunk)
Just in case, the answer "c:" is not wanted, that's too obvious.
Another hint, both files are non-ascii files.
Answer:
Ok, the answer. First of all, as you can see, one of the open directives is running on Unix (in
this special case on Linux).
The other one runs with the same version of Python on Windows XP.
Both files are non-ascii files, which means, somewhere in between there is a character which
could lead to problems on windows, while reading the file.
Now on Linux somehow this file is opened correctly as binary. The official syntax for opening
binary files in Python is open(<filename>,"rb") (well, to be more precise "read binary").
On Linux, as said this file is opened correctly in binary mode, while on Windows the default
opening mode is ASCII.
You can see the difference when you follow the "print len(chunk)" data. Somehow, if you have the
"EOF" character somewhere in the file when opened in ASCII, python stops reading the file and
thinks the file ended. Which is somehow not the real truth.
This behaviour had cost me now at least 2 hours of debugging, because I was in the thought,
Python2.5's behaviour should be the same on Windows as on Linux. I was mistaken.
But why? Shouldn't it be the same? Is there any rational why it's different on Linux and on
Windows?
If some Python guru can enlighten me, so that I can understand...that would be great :)

|
Planet Ubuntu -
1 days and 14 hours ago
Akademy talks are in the process of going up. Here are the video (Stream, OGG 76MB) and
slides (PDF
88KB) for my talk on The KDE Usability Project.
|
Planet Ubuntu -
1 days and 16 hours ago
 Intro
In my last post I discussed the gathering of requirements, and the organization of those
requirements. In this post I will be moving to the next step, case creation based on those
requirements.
Getting Started
Now that we have requirements collected and numbered, we can begin creating cases to exercise the
features described. So where to begin? Let's take a simple requirement from the example we used in
the last post here
1.1 Select "Featured Content" to see content we highlight that changes on a regular basis
So to best exercise this feature there are several things to consider. The first is the name of the
section where the feature exists. In this example that is "Featured Content". So our first test
case would be to confirm that this area is named correctly:
1) Launch Vuze
2) Confirm main application window contains "Featured Content" area
3) Confirm spelling and grammar of "Featured Content" area is correct
The next section of the requirement is "to see content we highlight". This means there should be
something there by default. So, next case:
1) Launch Vuze
2) Open Featured Content area
3) Confirm Featured Content area is populated with links to various resources by default
Along with having content available, we also need to check that the content is functioning as
expected. To do this, we need to explore each of the links provided in the content area.
1) Launch Vuze
2) Open Featured Content area
3) Click each content link
4) Confirm that each link launches a service
Lastly, there is the closing part of the requirement "that changes on a regular basis". For this
one we may need to contact the developer to find out what regular basis means, or if he/she can
trigger a change so we can test that feature. Either way, our case will be the same.
1) Launch Vuze
2) Open Featured Content area
3) Click each content link
4) Confirm that each link launches a service
5) Close Vuze
6) Trigger content shift or wait X hours for normal system cycle
7) Launch Vuze
8) Open Featured Content area
9) Click each content link
10) Confirm that each link launches a service
Now, I did something a little different here. In the previous cases I did one feature at a time.
This gets you the best results and makes tracking cases much easier. However, it is also very time
consuming. To save a bit, you can often combine cases in a logical way. For instance in this one, I
combined the cycling of links and the case previous to it where we checked the links.
Be Careful here. You really only want to combine a new case with ones already run. If you start
combining too many unique steps you risk losing focus on what you are actually testing, and the
tracking of which cases have passed and which have failed becomes a nasty situation. Any time you
have saved writing the cases, quickly evaporates when you try to collect statistics on your testing
results.
Mapping
Ok, So we have some cases now. The next step is to ensure that all requirements are covered by
cases. We do this by mapping cases to the requirement they were written to explore. This is
accomplished by simply referencing the requirement number next to the case. So for the cases we
wrote above, each would reference the 1.1 requirement. Having multiple cases for each requirement
is very common. If you have several requirements with only a single cases, spend a little more time
thinking about how the user might interact with the feature, and I'm sure some more cases will come
to mind.
Pulling It All Together
We now have requirements, numbered and organized, and cases created for each or our requirements.
The last stage is organizing these into a format that is easy to read, follow, and track. Most QA
houses use a table to to this. An example of the cases created in this post can be found here
You'll notice that there are several additional columns in the table to help with tracking. These
include a case number, description, and date/build. These help the tester easily find the cases
that need to be executed. The pass/fail, bug, and date/build columns help with tracking the state
of each feature. These give the reader an idea which areas of the program need the most work and
what are the major issues with those areas.
Put all of these together and you have a very efficient way of organizing your cases into a simple
format that can be used by both technical and non-technical readers.
Next: Execution
Join me next time for the fun part! Executing the cases, finding bugs, and tracking the fixes
through the software development process. Thanks for reading and Happy Hunting.

|
Planet Ubuntu -
1 days and 16 hours ago
I’d like this comment to go
out to everybody who held sessions, helped organising Ubuntu Developer Week, participated and helped
to make this an AWESOME event:
I was able to make Monday’s sessions, since it was Labor Day here in the US, and all the
sessions were absolutely awesome. I had to work the rest of the week, but I’ve been
faithfully refreshing the #ubuntu-classroom logs every hour (no IRC at work).
I want to seriously thank all the people who held/are holding sessions this week. While I’m
not following live in the room, I’ll be going back through the sessions one by one and
working through them when I have the chance. I have enough of an attention deficit anyway, so I
highly doubt I’d ever have the patience to wade through all the tutorials and respective
reference documentation for them. Last week, I thought Launchpad was just yet another bug
tracking suite (that rabbit hole’s looking quite deep now ).
Take care, and hopefully I’ll see you around.
Today’s the last day,
tune in, participate,
enjoy.

|
Planet Ubuntu -
1 days and 16 hours ago
 As I talked about in my
last blog post we are considering moving to 2.6.27 for Ubuntu Intrepid Ibex. Ben posted this
RFC to the
ubuntu-devel list which outlines the rationale and technical benefits. This came late in the
Intrepid development cycle and as such comes with risk and lots of questions such as:
- What are the regressions from 2.6.26 upstream and Ubuntu specific?
- Whats the plan "B" or fall back plan? When does it get invoked?
- What new "critical" bugs does 2.6.27 introduce?
- What existing 2.6.26 bugs does 2.6.27 fix?
We have and will continue to issue calls for testing and our QA team has been all over this
since day one. We have been tracking all of these issues and then some. For those of you who wish
to follow along at home here is my list of links:
I published the plan "B" with overlaid decision points here: https://wiki.ubuntu.com/KernelTeam/2.6.27-kernel-plan
As it stands now we shipped 2.6.27rc4 with Intrepid Alpha5. We noticed some big suspend/resume issues with
Alpha5. I noticed these issues on the 3 dell notebooks that I have. We will be updating to
2.6.27rc5 shortly which should resolve the issues and fix even more bugs.
Hope folks find this useful...
~pete

|
|