Welcome to the Ubuntu Weekly Newsletter, Issue #147 for the week June 15th – June 21st, 2009 is available.

In this issue we cover:

* Ubuntu Free Culture Showcase competition
* 3 New Members of the Americas Region Membership Board
* Bootchart testing for UNR
* Empathy to replace Pidgin in Karmic Koala
* Ubuntu Global Jam 2nd – 4th October 2009
* New freenode webchat (and why to use it)
* Ubuntu Stats
* In the Press & Blogosphere
* Upcoming Meetings & Events
* Updates & Security

The Ubuntu Weekly Newsletter is brought to you by:

* Dave Bush
* Sayak Banerjee
* Kenny McHenry
* Liraz Siri
* Craig A. Eddy
* And many others

If you have a story idea for the Weekly News, join the Ubuntu News Team mailing list and submit it. Ideas can also be added to the wiki!

Except where otherwise noted, content in this issue is licensed under a Creative Commons Attribution 3.0 License BY SA License

Welcome to the Ubuntu Weekly Newsletter, Issue #146 for the week June 8th – June 14th, 2009 is available.

In this issue we cover:

* SanDisk collaborates to improve Ubuntu netbook SSD performance
* MOTU Council Results
* Ubuntu Stats
* Calling all LoCo Teams!
* In the Press & Blogosphere
* Upcoming Meetings & Events
* Updates & Security

The Ubuntu Weekly Newsletter is brought to you by:

* Dave Bush
* Jeff Martin
* Sayak Banerjee
* Liraz Siri
* Nathan Handler
* Craig A. Eddy
* And many others

If you have a story idea for the Weekly News, join the Ubuntu News Team mailing list and submit it. Ideas can also be added to the wiki!

Except where otherwise noted, content in this issue is licensed under a Creative Commons Attribution 3.0 License Creative Commons License Attribution 3.0 BY SA

Welcome to the Ubuntu Weekly Newsletter, Issue #145 for the week June 1st – June 7th, 2009 is available.

In this issue we cover:

* Ubuntu Hall of Fame: Adi Roiban
* Ubuntu Stats
* Ubuntazo In Venezuela
* Ubuntu Forums Tutorial of the Week
* In the Press & Blogosphere
* Upcoming Meetings & Events
* Updates & Security

The Ubuntu Weekly Newsletter is brought to you by:

* Dave Bush
* Jeff Martin
* Isabelle Duchatelle
* Craig A. Eddy
* Sayak Banerjee
* Kenny McHenry
* Liraz Siri
* And many others

If you have a story idea for the Weekly News, join the Ubuntu News Team mailing list and submit it. Ideas can also be added to the wiki!

Except where otherwise noted, content in this issue is licensed under a Creative Commons Attribution 3.0 License BY SA Creative Commons LicenseAttribution 3.0 License

Everyone has heard, and may have used, the expression that Linux is free.  Actually, that’s wrong.  There is a price to Linux.  In fact there are two prices for Linux, which depend on the individual and his/her relationship to it.

1. The cost in time of the people that develop, test, debug and package it for individual consumption.
2. The cost in time of the people that use it, in learning a new operating system, in setting it up each time a new release comes out, in learning to use the many and varied programs that run on it, and in explaining to others WHY they chose to use Linux.

Linux may not have a monitary cost, but that doesn’t mean that it has NO cost.  How much does a programmer make in the commercial market?  Is her/his time any less valuable simply because he/she chooses to work on a program for which she/he will receive no remuneration?  Of course not.  That person could easily be working on some other commercial program as a contractor, or acting as a consultant to a company.  But because that programmer has chosen to work on “free” software he/she is labled with the most obnoxious lables, considered some sort of anti-social person with no concept of true value, and that his/her work is therefore without value.

Without value.  How that rankles me.  If it had no value then why are major companies using it?  Many of them using it exclusively.  And making lots of money doing so.  If it is without value then why are manufacturers using it in embeded products, like desk-top units, etc.  This is not some sort of socialism.  These companies see true value Linux, and make use of it, and make money from it.  Enough money that many of these outfits find ways to contribute, themselves.  IBM, for example, pays programmers to work on Linux and associated programs because the company makes money from them.  It is in there best interest to see Linux improve, because then their own products improve.  I could go on and on about such companies, but if you honestly take a look at what’s going on instead of buying into someones ADVERTISING, then you will see it for yourself.  Linux has value, and that value has proven itself in the marketplace.

What is true of the core operating system, of Linux, is also true of the vast number of “non-commercial” programs that ride on top of it.  Programs like OpenOffice.org, GIMP, GNOME, KDE, VLC media player, and Firefox . . . and the list goes on.  These all have value.  The value is in how you use them and how you respect them.  I do not claim to be a computer guru, but I can sit down at a computer and hammer out a spreadsheet or a simple database, or even write a story or a blog because I took the time to learn the tools with which to do so.  Nor is it the first time that I’ve done so.  I’ve worked with computers for about 18 1/2 years as a CAD operator – a Computer Assisted Draftsman, operating on commercial programs and operating system.  I had to learn them all by my self.  I didn’t go to school for it.  Then had to relearn when the company I worked for tossed me onto a UNIX system.  Then relearn again when they went back to their original OS manufacturer.  In fact, my whole working life has been one round of learning new things in order to do my job and do it, not just to the satisfaction of my employers, but to the satisfaction of myself.  so when I hear people say that they don’t want to use Linux because it’s not what they’re used to, I have to wonder why they are being paid.  Are they so afraid of a little work, the true cost of ANYTHING, that they refuse to crawl out of their holes and look toward the horizon?  If so, I feel sorry for them, for they will never feel that they are a success.  At anything.

No, Linux is not free.  It is without cost, if you choose to accept it that way, though there are distributions that charge for it (mainly, they are charging for the packaging and a certain limited amount of support), or that charge for service contracts.  But that’s not “buying” Linux.  It’s buying the service contracts or the pretty packaging.  It’s up to the individual to free himself or herself of the advertising claims of commercial operating system manufacturers that only see money as having value, and ignore the fact that the OS they are producing costs even more in time and money due to viruses and the like.

I offer you the hand of freedom.  Freedom to choose for yourself where your money will be spent.  Freedom to learn new things and find new ways of producing value for which you CAN charge.  Freedom to decide what you will have on your computer and how you can use it.  A computer is a tool, a versital tool that can be reconfigured to meet the needs of whatever job is out there.  But it’s up to the individual to decide how to use it, not up to some faceless manufacturer that doesn’t understand the needs of the individual.  So, when I hand you a disk and say, “here, it’s free”, I’m only referring to the monitary cost.  It will still cost you some time and effort on your part.  Pay the price.  It’s worth it.

This posting is not about Ubuntu, directly. This is about security: what is is and how does one achieve it. Certainly, having an operating system that is not subject to the assorted malware that’s out there is helpful. But the FIRST thing one must have is the proper attitude toward security.

.

There is a story going around that a certain software manufacturer managed to get a particular operating system certified as secure by NOT having it attached to the Internet. Opponents of that operating system made comments about it being even more secure if one never turned that computer on. Despite the humor of the situation, it’s not far wrong. There is NOTHING secure about the Internet. To believe that there is is to delude yourself. There is NO way that I can over-emphasize this:

.

THERE IS NOTHING SECURE ABOUT THE INTERNET.

.

If you put something on the Internet it will be accessed. If it interests somebody, it will be copied. This goes back to the simple maxim, “Tell one person a secret, and it’s no longer a secret”. This is true of not only the Internet, but of anything at all. If you don’t want people to read, view, hear or otherwise access something then don’t make it available in the first place.

.

But does this simply mean that one shouldn’t post private information on the Internet? Not at all. ANY security can be broken by dedicated people with the proper tools and the will. And there are those who definitely have the will and the tools. Hard drives and CDs with vital information can be stolen or even “mislaid”. Books can be scanned. Music CDs and video DVDs can be copied. Artwork can be copied. State and corporate “secrets” can be accessed by dedicated professionals. It’s all there and available.

.

So, what can one do about it? It’s called “risk management”:

1. If there’s no need to put something out there, don’t do it. If you want people to NOT be able to access something, then don’t put it where they can gain access to it. This includes music and movies.

2. Have a plan worked out in advance for the security of “hard” information, such as papers, hard drives, CDs during any movement or storage. Sending something by way of the government post-office is a good way to have it “ripped off”. Secure currier with signatures and receipts for any changes in possession is a must. First, it gives you a chain to follow if something DOES go wrong. Second, it impresses the seriousness of the situation on the individuals involved.

3. If it is something of commercial value, then take a thought to how others might gain access to it, copy it, and/or otherwise try to get around the monetary aspects of it. It will be done. But instead of fighting it one might find it better to turn a weakness into a strength. Instead of the failed system of DRM, choose to make access easier for a reasonable price. Recognize that file-sharing actually gets your works into more hands – hands that will pay money for higher quality versions of what they’ve downloaded. And, where you’re attempting to foist off on an unsuspecting public some trash, you’ll quickly find out what the public considers trash. It is the opinions of the public that actually drive your profits. If they’re displeased, they won’t buy. If they are pleased they’ll happily pay a reasonable fee to own a valid copy.

4. Before all else, consider how much risk there is in the dissemination of your material. If the risk is too great for you then DON’T PUT IT OUT THERE. Listen to the people who are security experts when they tell you that something isn’t working (if you’re only listening to people who agree with you – marketing people, “yes-men”, managers that haven’t worked their way up through the ranks of IT or the like – then you WILL fail to find appropriate solutions to your security problems). When you don’t know something it pays to listen to those who do.

In short, don’t blame others for your material getting away from you. They are YOUR secrets. Making them available to others is YOUR choice. Don’t blame people for being people. You’re simply attempting to transfer your OWN guilt to somebody else because you’re too immature in your attitude to accept your own responsibility.

Welcome to the Ubuntu Weekly Newsletter, Issue 141 for the weeks May 3rd – May 9th, 2009.  Available here.

In this issue we cover:

* Monthly BugSquad Meeting: May 12th
* Jaunty Jackalope Release parties
* What’s a build score, then?
* byobu 2.0 released
* In The Press and Blogosphere
* Ubuntu Podcast #27
* Meeting Summaries of Technical Board and Ubuntu Server Teams
* Upcoming Meetings and Events
* Updates and Security for 6.06, 8.04, 8.10 and 9.04
and much, much more.

The Ubuntu Weekly Newsletter is brought to you by:

* John Crawford
* Craig A. Eddy
* Dave Bush
* Jeff Martin
* Keny McHenry
* Liraz Siri
* Nathan Handler
* And many others

Contrary to what it looks like, this really isn’t about bashing any particular FUD, just FUD in general about Linux.  Now, obviously, since I use Ubuntu, my responses will be restricted to what I’ve seen in that, but I’m sure a lot of it will be common to many of the Linux distributions.  So, let’s look at some of the things that are said about Linux, and what the reality is about them:

1.  Installing new software and updating existing software in Linux isn’t for the faint-hearted, and most people won’t be able to figure out how to do it.

1. REALITY – The hardest way would be to use “sudo apt-get install [name of application]“.  The way I usually do it is to simply go to Synaptic and install the package and all dependencies that it needs.  That covers installation.  Now what about updates?  Update Manager goes looking every morning at about 8:00 LOCAL TIME.  If there are any updates to ANYTHING from the initial install, or installed subsequently through Synaptic or apt-get, it will offer to download and install them.

2. In addition, Windows 7 has eye candy and extra features that Linux lacks.

2. REALITY – You want eye-candy?  I’m running Kubuntu Jaunty RC right now.  When I shift desktops (I’ve got 4 set up to use, right now) you can see the cube of desktops circle around to the newly selected one.  There are other ways I could do that, as well as all sorts of ways that I could have windows maximize, minimize, or close out.  I don’t bother with them, though.  I’m a bit of a conservative.  Then there’s screensavers.  How about a fiber-optic lamp that rotates and changes color?  That’s only one of many, some of them very “retro” style and old fashioned, and some that are quite modern and attractive.  I could even have swimming whales, if I wanted.  Eye-candy?  You want some?  See Linux.

3. Since no one company owns Linux, there won’t be any marketing muscle for Linux.

3. REALITY – There are computer manufacturers that have learned the value of Linux, from major ones, like System76 to small refurbishing shops like RedSeven.  Since Linux doesn’t require the latest, most expensive hardware, manufacturers can put together systems that cost THEM less, and offer them for less than the cost of a Windows machine, and STILL get a good return for their investment.  They’re the ones that will be doing the pushing.  And that’s not counting the various forms of marketing engaged in by such as Red Hat and Canonical (to say nothing of all the LoCos that help push Linux).

4. Linux is for techies, and is difficult to learn.

4. REALITY – I really wish people would get off the “techie” schtick.  Its comedy value was never great, and has dropped off remarkably over some 10 years or more.  I’m not a techie.  I’m not a geek.  I’m simply a guy that wants to use a computer that doesn’t frustrate me.  I want to be able to visit my favorite web sites, get my email, chat with fellow travelers.  I want to be able to write articles for this blog, or do summaries for newsletters.  I want to have “productivity tools” available for doing presentations or spreadsheets.  I want to be able to build a database for my library or music collection.  Occasionally, I want to be able to stretch beyond myself and try new things.  I can do all of that quickly and effectively in Linux, without having to learn esoteric commands or know how many sectors are in a hard drive.  And, as for difficult to learn, well, my wife was a dedicated Microsoft user.  She offered to try Ubuntu.  Now, the three computers in the household all run Linux.  Even the Dell Mini 9.  She’s had no trouble learning to use it, and very few questions.

So, I hope this answers, once and for all, some of the FUD that’s been touted about Linux.  And I would hope that it would also cause one to do the REAL research about other things one hears.  There’s a lot of garbage out there (I won’t even dignify it with the term “spin”).  This garbage is being planted by people who are in the pay of commercial enterprises that want you to believe that Linux is no good.  Don’t believe their words, try it for yourself.

The last few releases of Ubuntu have left me scratching my head, and not just because of dandruff.  The Developers and MOTUs for Ubuntu have seen fit to add PulseAudio to the audio stack.  And I do mean add it to the stack.  It sits on top of Alsa and attempts to manage the way people use their audio.  And yes, it sits on top of Alsa, not replaces it.  Alsa is still there and functioning properly.

But then, PulseAudio comes in and makes further decisions about what’s available and what you can do with it.  This might not be too bad, except that PulseAudio STILL hasn’t reached 1.0.0 state.  It has been functionally broken since it was first put into Ubuntu and activated by default, and it remains so, today.  Originally, one could find PulseAudio in the Sessions Boot Start-Up, and turn it off.  Likewise on could remove it from the services that are run.  Now, however, it’s rather well hidden.  Somewhat in the manner of a Microsoft activity that someone is ashamed of.

My disgust with the fact that PulseAudio was arbitrarily relegating my audio to monaural, despite the abilities of my sound card, caused me to file the following bug report on March 30.

==========

Bug #352164

PROBLEM:  PulseAudio is unable to determine basic information about my sound system, despite the fact that the information is readily available.

System is a Dell Inspiron 530N
Processor – Intel Core2, 1.60GHz
Memory – 1 Gig
Video Card – NVidia GeForce 7300LE
Sound Card – Intel 82801I (ICH 9 family) HD Audio Controller
Operating System: Ubuntu 9.04 Beta (Jaunty Jackalope)
Linux Kernel – 2.6.28-11-generic
This system is up-to-date with package updates as of March 30, 2009, 10:54 PM Mountain Standard Time (UTC -7), or April 1, 2009, 05:54 UTC

This card is capable of AT LEAST 44100 Hz sampling and AT LEAST 5.1 Surround Sound.  Yet what I get from PulseAudio (via the system log) is:

Mar 30 16:18:51 tyche-jaunty pulseaudio[3270]: alsa-util.c: Device hw:1 doesn’t support 44100 Hz, changed to 22050 Hz.
Mar 30 16:18:51 tyche-jaunty pulseaudio[3270]: alsa-util.c: Device hw:1 doesn’t support 2 channels, changed to 1.

This is an unacceptable situation, made worse by the fact that it takes extraordinary measures  to turn off PulseAudio so that Alsa (which IS installed) can do it’s job.  Monaural sound, to someone listening to serious, Classical music is unacceptable.  Installing PulseAudio and initializing it by default is a regression of ability.  Installing it and initializing it by default then hiding any ability to kill it is Microsoft style thinking.  We are supposed to be better than that.

SOLUTION:  Stop initializing PulseAudio by default.  If people want to install it and use it, it should be a choice.

==========

My purpose in publicly voicing my contempt for PulseAudio as a “sound manager” is to draw attention to the fact that, in all this time, it STILL is functionally broken to the point that use of it constitutes a regression in the ability of my system to produce reasonable and pleasing sound.  And no, this is NOT the first time that I’ve filed a bug report or question with Launchpad on this subject.  I grow rather tired of being ignored when I suggest that it not be activated by default.  With something like this that lacks the functionality that people need and want, it should be up to the individual to make the choice of whether or not to use it.  Activating it by default is unconscionable.  Activating it by default and hiding it, to make turning it off an extremely difficult procedure for the uninitiate goes beyond that into the sort of thinking that have moved people away from Microsoft operating systems.

So, I ask once again – and publicly.  Turn it off.  Provide a means of allowing the individual to turn it on IF THEY WISH.  But please don’t foist broken applications on an unsuspecting public and uninitiate new users simply because it’s the “new thing”.

Oh, and for those of you that are stuck with it running, and can’t find a way of turning it off, enter “killall -9 pulseaudio” into the Sessions and reboot.

“Welcome to the first meeting in a long time!  We plan on having these meetings on a regular basis.  At least monthly.  These meetings are a chance for all LoCos to share experiences so we can motivate each other and learn from each other, see how LoCos are doing, discuss any problems we might be facing.”

Thus Nick Ali (boredandblogging) started an IRC meeting that may well prove to be the most momentous one in a long time.  78 nicks from all over the world were found to be in channel by the end of it, and numerous people spoke up with questions, suggestions, observations and other information.  Among the things discussed were:

1. The amount of support that the LoCo teams were receiving.
2. What could be done better.
3. Sharing between LoCo’s.
4. The need for LoCo’s to make presentations.
5. Focusing on different LoCo activities, such as a meeting about release parties – a meeting about participation at conferences.
6. Looking forward in a more timely basis at future events: getting started planning earlier.
7. ‘Global’ events to rally teams together.
8. #ubuntu-locoteams channel should be overflowing with loco people, ideas, “hey I think we should do this” kind of things.
9. This channel should definitely be on everyones auto-join and we do need to promote this channel as a place to hang out.
10. The use of identi.ca to promote this channel.
11. Alternating meeting times, to accommodate other time zones, so everyone can attend them at least once every other month.
12. The location of where locoteams news would be posted.
13. What teams do to increase membership.
14. Translations for non-English speaking countries/loco’s/individuals.
15. Coordination of and use of LUG contacts, and other local open source contacts.
16. More collaboration around events, trying to get the teams together more (which I realize is the purpose of this channel), but it all comes down to communication.
17. Creating a best practice guide for loco’s.
18. How we can help ourselves to be more efficient and organized?
19. The results of Open Docs Day.
20. nixternal reported on LoCo Directory — Right now will be a database of all teams, approved and unapproved…future enhancements include a place to post your events, do some team sharing, and whatever other mashups people come up with.  It is being done with django and postresql, will include the django GIS stuff so you can mash it up with Google Maps and what not.  It will be the one-stop-shop for LoCo teams.

A great deal of discussion took place, and for that hour the channel was really jumping.  Congratulations to the LoCoTeams for an informative meeting.

The new server for the Arizona LoCo has just gone live with it’s new website.  Located at AZ-LoCo (or for the purists http://www.azloco.com/), there are links to our Launchpad page, our wiki page, our forums and mailing list and newsletter (all on Canonical servers) as well as a wealth of links on our new site.  There’s even a way to connect to our IRC channel without an IRC client (look in the upper right hand corner).

We’re a bit new, so you won’t see a lot of blog content on the site, yet.  But we’ll get there.  In the mean time, from the introduction on the front page by our team leader,  John Crawford:

“There are several people, or groups that we need to thank for making this website possible. Devry has donated the rack space and Internet connection for our team. Shane Lofgren has donated the servers. Craig, Kenny, Shane and myself did all the site setup, and will be the site administrators. Without all of these folks working together this website would not have been possible. Thanks!!”

Come take a look and, if you’re an Arizona LoCo Team member, register with the site.  We’d love to see you there.