Oct 292008
 
No Gravatar

Today I posed this message to several of the LUG’s in South Africa. I am reposting it here without edits.

Hi Everybody,
Sorry for the cross-post, I promise it’s a once-off but this is a bit of a special circumstance.
In the grand tradition of GNU and later the Linux kernel, I am beginning with a mail to announce
my intentions, and a request for anybody who shares my vision to help out.
The interest in my CLUG talk about distribution creation some time ago left me thinking that
perhaps there are enough people out there (particularly here in South Africa) who may feel up to
the fun and work of helping to create something special. Having spent 5 years creating a
successful commercial distribution, I believe I have the skills for such a project to be workable, though this one is meant to be very different as you’ll see.

Starting in the next weeks I want to create a GNU/Linux distribution called kongoni. Kongoni is the
Shona word for a gnu (wildebeest) and this represents the origins of the system: firstly it is African,
secondly it is meant to be a truly free distribution of the GNU operating system.
The name in other words translates literally as: GNU Linux :) (I rather like the wordplay as well).

Fundamental to the design will be an absolute commitment to free software only. That means we will not
include in the installer, nor in the ports tree or any other officially distributed packages any piece of
software that is not under an FSF approved license.
Some degree of the workload can be shared by utilising (and contributing back to) Gnewsense’s list (and blacklist).

Development releases will have a kernel compiled with the no-taint flag – not allowing any non-free drivers to load,
which will be very useful for auditing purposes, where possible we will provide free alternate drivers.
UPDATE: I should have been more clear here. I mean ONLY development releases will have notaint, official releases will not restrict what users can or cannot load.

Where possible I want the system to actively contribute to high-priority free software projects like GNASH and Nouveau,
not least by providing automated scripts in the packages to allow even non-technical users to file automated
bug reports to the projects with usefully information for their needs. Thus possibly increasing the number of testers
exponentially, the improvements that arise will in turn benefit all free software users and developers.
The system will never be commercial, I have no problem with commercial free software (in fact I run a commercial free
software company) but this project would best benefit from being a true community project. If the need arises to
formalize structures, I pledge that it will be done by registering a charity organisation, or joining an existing one
– not by starting a company. If people some day want to start companies that sell services related to the system however
more power to them.

Now on to the initial technical details. First off, I don’t think there is any room in the market for yet another Ubuntu
respin. Ubuntu is a nice system in many ways, but the need is met – and Gnewsense already provides a fully free alternative
to fans of Ubuntu. Instead I believe there is room for new ideas and new thinking.
To this end I want to start with a slackware/bluewhite64 baseline initially targeting x86_32 and x86_64 platforms.
Slackware has many advantages as a baseline and offers enormous power of (easy) customization to give the system a real
unique identity while staying true to standards.
The biggest catch is addressing slackware’s number one shortcoming for desktop users: the limited package manager.
To address this, and also minimise the workload of multiple platforms, I intend to use portpkg to provide a ports tree
that is fully tracked for dependencies. Among my first coding tasks will be a full graphical frontend for portpkg as well
as a series of patches to portpkg itself to allow us to maintain our own ports trees as default. These will consist
of license-audited and dependency-mapped clones of the slackware/bluewhite64 repositories for upstream, and source-only
ports for 3rd-party packages. It is important to maintain our own ports tree since unfortunately all the default ports
available in portpkg include non-free software in their package lists. While we cannot (and should not) prevent users
adding those repositories and installing such proprietary packages – we should not give this action any official support.

The initial default desktop will be KDE4 with intention of including KDE4.2 (due in February) in the first stable release
if possible. OpenOffice.org 3.0 is on the standard packages list, and if the promised GNU/Linux port of Chromium is available by
release time it will be the default browser, otherwise one of the free firefox forks.
An absolute must is a powerful and complete system administration and configuration tool,
utilising things like darkstarlinux’s ALICE suite to complement a full kit for user-admin,
setting up advanced Xorg settings (like multiheads) and other common admin tasks. To ensure
seamless wireless and wired network roaming, wicd will be a default package (and madwifi with the new free ath5k hal for older cards and the newly GPL’d hal from Atheros as well).

It is quite possible that if we have enough volunteers and resources future releases could include parallel versions for
Gnome,xfce,enlightenment etc. and I am happy to include these in the ports tree if somebody helps create the ports.

In terms of project admin I wish to set up a suite of easy-to-use web-apps for contributing, auditing and approving
of ports (the first should be open to all, the latter two to trusted testers only). Designed to make the task
of contributing in this manner not only as simple as possible but to minimize the time needed as far as possible so
that those who choose to contribute their spare time to it can spend as much of that time as possible doing fun stuff
and as little as possible doing drudge work.

The focus of the project is home and desktop users, there are other distro’s aiming at this market but precious few
with a stated mission to be completely free, in both senses of the word.
After freedom, our second most important design principle should be one of “it just works”.

Now of course, as I type this Kongoni is vapourware, the first line of code has yet to be written (though I’ve done
significant amounts of research to make the decisions above, and I have written an installer).
Normally, it isn’t my style to announce something until the first pieces are written but in this case I
find it crucial to the very concept that other people be involved from the start. I have proposed a vision
(not an uneditable one technically) and I want to see who shares my vision and would like to contribute to it’s
realisation. I will be happy to fund hosting for the project and contribute much of my free time to it’s realisation
but I would like to have as many people helping as possible so that this is not just my vision, but our vision.
People who can suggest ideas and improvements, people who can help realise those ideas and help with the
large workload ahead.

If just a few people say “I’m in” – then that’s a go-ahead as far as I’m concerned.

The most useful skills right now will be:
*Web-app programming and web-design
*Ports builders and co-maintainers of the tree
*Graphic design
*Testers

These will likely get official lieutenants appointed on a first-come, first-serve basis.
There is much more to do so if you feel that you can contribute something please feel free to speak up.
If any of the mirror maintainers would be willing to host local mirrors of the ports tree and ISO’s when
we get to release time, please let me know as I have learned from hard experience how even a small distro
release can hit a server.

May I request that those who wish to contribute also reply to me directly as I do not want any
names to get lost in the noise as people discuss the idea.
Finally, I would like to suggest that those who are in Cape Town (once we have a list) meet up
for a face-to-face planning session. Perhaps over coffee on Saturday somewhere in Rondebosch ?

Thank you for reading this far :)
I hope to hear from you.

Ciao
A.J.

Oct 272008
 
No Gravatar

I finally decided last week to take the plunge and try the nouveau driver out. My feelings on proprietary drivers like nvidia’s are well known by now so I doubt there is anybody who will be much surprised except that I took so long.
RMS has said many times that the only time it is acceptable for somebody who believes in free software to use proprietary software is when (1) there are no usable free alternative and (2) you are also contributing to the creation of such an alternative. Thus the use of the proprietary only program is just a temporary stopgap – and you are making an effort according to your abilities to ensure it remains temporary.

Well there are four pieces of proprietary software on my computer (that I know about – if something else slipped through I haven’t found it but even gnewsense has trouble finding it all – and if I haven’t found it then the implications if that I don’t use it). The first is the BIOS, well there isn’t much I can do about that right now, opencore doesn’t support my motherboard yet, and since it’s not a dual-bios motherboard there is no way I can help fix this without bricking my computer. The second is java, which is not major concern to me since it’s 90% GPL’d already and the remaining ten percent will be GPL’d by April if SUN keeps their word.

The last two are the nvidia driver and the adobe flash player. So those two are things that I can start helping to get rid off, and I am doing just that. For flash, I am running gnash as well, my coding skills do not extend to what gnash needs but I can contribute bug reports and I am doing so as I have been for several years. Gnash is fast approaching a usable state. I see too many ‘opensource’ people cheering because Adobe finally ‘saw the light’ and released the GNU/Linux flash-10 alongside the windows version. Wake-up people. They didn’t see the light, they didn’t do this because they are nice ! They did it because gnash is fast approaching a usable state for everybody (it already works for almost everybody) and they want to try and stop it’s momentum by cementing their position with an early release.
Please folks, if you care about free software, see through this piece of pure marketing strategy. Adobe didn’t do this to make it easier on new GNU/Linux users, they did it because GNASH represents a threat to them on Windows and on GNU/Linux, so stopping it where it is currently strongest is their best bet to try and prevent it replacing them on both.
I believe however that they will come to learn that the only way they really could have stopped gnash and made it irrelevant would have been to make flash free software.

But back to the topic at hand, there is one project out there to try and create a free replacement for nvidia’s proprietary driver and I am now running it. At this stage you will need to have xorg1.5 installed to make the most of it, the 1.4 3D and compositing support requires the gallium driver for it which is … very broken. But not long ago, all of nouveau was pretty broken. It’s impressive how the driver has come along in a short period of time. Already it outperforms the nv driver a hundred times over on my system.
I will be upgrading to xorg 1.5 as soon as it’s practical to test it on that (particularly it’s 3D support) but I can vouch that if you follow the wiki instructions for installation nouveau works pretty well for 2D on most setups. There are some quirks which I will post on more fully as I discover them, but well done to the nouveau folks, I have already offered them what help I can give because contributing to this is the only way I can rid myself of a driver that has proven unstable, badly designed and thoroughly proven that proprietary software always comes back to bite you in the ass sooner or later.

Oct 222008
 
No Gravatar

Microsoft made headlines yesterday with it’s global anti-piracy day ‘celebration’ – a kind of Microsoft version of a hallmark anti-holiday (if you’ll excuse the anti-pun). Tectonic has a very well written article on just how much the marketing blurb by the BSA in South Africa ignores (short version: all the actual facts) and the register had two stories on the anti-event and it’s associated black-screen-of-call-the-customer-a-thief WGA deployment.
WGA shall apparently standing for: Witch-hunt, Gossip and Accuse.
Update: or even better – Windows Guilty by Accusation

Of course as tectonic points out the picture is rather more complex than the BSA paints it. More eloquently I would say the BSA painted a stick figure with one ear (xckd style) and wants us to believe it’s the famous Van Gogh self portrait. Please note that I am NOT trying to suggest any association between XKCD and the BSA – and that I am just using a metaphor with well-known imagery, if anything the BSA’s drawing is rather crude by XKCD’s actual standards.

One particular quote stood out for me in the register articles:
Rob McKenna, Washington State Attorney General, said the trade in counterfeit software was “killing American jobs and suffocating competition”.

He claimed a third of all installed software was pirated and that a ten per cent reduction in the trade over four years would “create $41bn in economic growth and 32,000 US jobs”. McKenna said buying fake software was not like buying a fake scarf or handbag because you could not know what damage it could do to your computer.

That last line actually made me laugh out loud. Is this guy suggesting that when you buy a real copy of windows you do know what damage it will do to your computer ? Well aside from installing windows ? No you don’t. It’s closed-source proprietary software. Heck MS has a record of including malicious software in their proprietory products (of course they don’t call it malicious but that’s what I call WGA and other privacy intruding programs that phone home). They have a history of deliberately obfuscating processes to prevent non-MS applications that compete with their own from working well (how is this not harmful to end users who may prefer the non-MS application ?).
And that’s just what they did so far. FUD takes on a whole new level when Microsoft can get a bleeding Attorney General to pretend that pirated copies of Vista could cause potential harm to your computer – in completely denial of the fact that any proprietary software whether obtained legally or not has harm as a guarantee !

How about the fact that MS has update servers you cannot disable ? The ones they use to update WGA among other things. When RedHat/Fedora’s package servers were exploited, they shut down updates, came clean and made sure users knew how to protect themselves, and users were able to shut updates down themselves at any moment. If Microsoft’s update servers get pwned… well I guess every windows user out there is fsck’d … oh wait, windows doesn’t have that command – I guess they are just plain fucked.

The only way to get software that won’t harm your computer is to use software which can be and are independently audited (by other people, by you or by people you employ to do it for you). That means free software. Anything else is basically giving up your privacy, security and other rights to an untrusted party with nothing to gain from respecting it, and a habit of leaving glaring holes where other malicious (but rather less ambitious) parties like virus writers, crackers and phishers can get access to your most important private data for such uses as emptying your credit card. Of course, that’s exactly what Microsoft hopes to achieve so like I said, the others are no more malicious, just less ambitious since they don’t try to get every credit card from ever computer user in the world.

Still, here’s hoping that Microsoft stops just talking and actually starts getting a bit more heavy handed on piracy (italics because I don’t like the word). Their tactics pissed of Ernie Ball enough to switch his guitar string company (the best in the world) to GNU/Linux several years ago. The worse they get – the more people will start telling them exactly where they can stick their EULA’s and switch to something that doesn’t try to control you or rob you blind.

Oct 162008
 
No Gravatar

So, it’s been ages since I last posted, what with being incredibly busy the last week or so, so I reckoned I would make up for it by doing a few mini all-in-one posts about stuff I have been working with lately. Not everything is KDE stuff today – since I write about that all the time, I’m going to look at some other things I’ve been trying out.

ChrossoverChromium: I installed CrossOver’s wine-based port of Chromium (the free software base for google chrome) on Linux to try it out. At this stage my one remaining windows install (inside virtualbox on my company laptop, kept almost exclusively for running some backup manager software which don’t have a Linux client-interface [but we back up unix servers with it]) I use chrome quite happily when I do need to browse, it’s bleedingly fast and very stable.
This however did not hold for the wine-based port, while many such ports work just fine, I found the crossover chromium to be unstable and prone to weird rendering failures (of the browser itself, not the pages). It crashed many times and there is no way to put things like java and flashplugins into it, the moreso if you use gnash instead like me. Ultimately I uninstalled the thing about an hour after installing it. I was running it with 32-bit emulation on a 64-bit GNU/Linux though, so I would be interested if people using native 32-bit linux’s have different experiences. I’m holding out for the native chrome though because I really am impressed with the design, about the only thing I might have missed is a decent addblocker but I use privoxy anyway.

Talking of privoxy, if there is a truly underrated FOSS app out there, this is it. Privoxy is really nice, not only does it filter adds but it prevents all those nasty user-tracking, phishing and other malodorous sites on the web from harming you. The worst of them get straight out blocked, in most cases it just blocks the parts that potentially harmful. You can load it on your own machine and just set it as your proxy in your browser, or do what I did and run it on your router to protect your whole network. I used it’s proxy-forward feature to let it go through squid as well, so I get privacy filtering and caching in one suite completely transparent deal.

I’m playing around a bit with slax right now, using it to build a custom installer for a prebuilt server-image as part of a rapid-deployment system I working on. I got the idea from this great little howto which is actually installing solaris images with it !.

VirtualBox 2.0.2 has been a consistent letdown for me lately, compared to it’s predecessor I am just not impressed that much. Sure it works like the old one, but it’s stability has gone way down, especially on 64-bit but also on my 32-bit laptop. Whenever the system gets under even slightly heavy load, the VirtualBox modules tend to crash, and cause kernel panics, I haven’t had this many system-dead-hit-the-reset-switch-crashes since the days when I still ran windows 95 ! The problem seems unrelated to what guest OS you run, but does seem to be partially triggered by the guest OS doing any kind of fairly heavy disk access – synaptic in a pclinuxOS guest brings it down consistently for me. Furthermore the most touted feature of the new version doesn’t seem to work. I still cannot get a 64-bit guest to boot on a 64-bit host. VBox emulates a 32-bit CPU and I cannot find any place to tell it I want to use the new 64-bit feature. VBox remains a very good product with enormous potential and a much needed one in the FOSS world, but I hope the next update fixes some of these rather terrible regressions.

I downloaded the newly released Bluewhite64 KDE4 LiveDVD and installed it, replacing my older Bluewhite64-current CD based install. This fixed some small things I had broken over time and not gotten around to but it’s essentially the same system. Most annoying about the DVD for me is that there is just too damn much of it. The KDE4 DVD also contains XFCE, FluxBox and even WindowMaker packages. I spent some time cleaning up some of these things I will probably never use, though I must admit I logged into WM once for old times sake and a reminder of the time many years ago when it actually was my preferred desktop. Still, the DVD is nicely put together and tends to just work. About the only thing I had to add to get a setup I’m really happy to work on was wicd. Which is currently about the only nice tool for doing roaming networking (especially encrypted WIFI) without all the bloat of a pregnant elephant that’s been eating wheatgrass. Wicd installs on slackware likes (Robbie Workman did a noarch packages for it) with virtually no other dependencies and just works.

I used the slackbuild.org packages and built a copy of E17 the other day, just to see what the fuss is about. It is a nice looking little desktop, fast as lightning with very pretty effects and a decent feature set, but at least with those packages – the applications menu was entirely unpopulated. Apparently E17 doesn’t fully comprehend the freedesktop.org xdg menu standards. I did not feel like figuring out the cause – this kind of thing in this day and age should just work. I can understand something like windowmaker or icewm needing custom menu systems – they are old and deliberately tiny, but E17 is starting to play with the big boys. I appologize if the problem is with packaging rather than E17 itself but that was my experience of it. If somebody can provide more insight, I would love to know – if only to know, and such a comment could be useful to people reading this later in making up their own minds. As for me – I uninstalled it about 30-seconds after I saw the empty menu.

Oct 082008
 
No Gravatar

I got my hands on a copy of NeverWinterNights for Linux the other day, and I’ve been playing it whenever I have spare time at night – what a great RPG. Now before the flame comments start, I’m on record as saying I don’t think it’s ethically crucial that games be free software because they aren’t software to begin with – they are art. At least, they art part is far more important than the programming part.
Which is not to say it’s not very good (and certainly a lot better) when they are free software, but like with music it’s good when it happens, but not evil when it doesn’t.

So back on topic, I really enjoy NWN. It’s rules are familiar to anybody who knows even the basics of DnD or has played Nethack for that matter, and it’s filled with tremendous flexibility of gameplay (as befits an RPG). I haven’t tried the online version at all I must admit, but the single player version is really nice. A compelling storyline with the kind of environment that allows you to live that storyline out.

NWN is of course, 32-bit only but I had no real trouble running it on Bluewhite64, all I had to do was grab the 32-bit SDL packages from slackware.com install them in a temp root and copy the usr/lib files into /usr/lib32 and it worked fine ever since.

I did find one nasty – it doesn’t play (no pun intended) nicely with twinview, putting itself in the middle of the two screens spanning halfway onto each. With Xinerama, it works perfectly. Of course Xinerama on NVidia means no compiz effects but I have also found that with twinview enabled my system is really slow and unstable, using Xinerama instead is much faster and works way better under KDE4.

I made one change though, I don’t run it under KDE at all, seeing as I have two screens, KDE needs to keep managing the one NWN is not on, and it’s not like I can multitask that way since the mouse is trapped inside NWN, so that was just a waste of resources, instead I created a .desktop file to launch NWN by itself and copied it into /usr/share/xsessions, now when I want to play it I just select “Neverwinter Nights” from my session menu on the login screen and log in, when I exit the game I’m back at the login screen. I tend to do this with most heavy-on-resource games anyway and I highly recommend it. Being able to completely switch off your desktop while playing games is just part of the real power that GNU/Linux with it’s immense customization offers over other OS’s.

Oct 072008
 
No Gravatar

Arny has just announced the availability of new live DVD’s for Bluewhite64. There are now both KDE3 and KDE4 live DVD’s available and both sets have received a number of crucial security and stability updates.

Most exciting to me (and I hope a lot of users however) is the inclusion of bw64installer. For those who do not know yet, bw64installer is a complete, flexible, powerful and above all ease to use live system installer I wrote for bluewhite64. The code has been under development for some time (the official releases are shipping with version 0.0.5 which could be considered the first fully stable version).

This puts the LIVE versions of bluewhite64 completely on par with most other live distributions. Bluewhite64 has taken the interesting approach of buiding what is essentially a pure 64-bit port of slackware on one hand, and then being truly creative in their LIVE setups on the other, which ship a solid and easy to use preconfigured desktop system with a very impressive suite of applications, many of which are not included in the default (slackware ported) images, one example of which being the ALICE administration suite from the darklinux team.

As I mentioned in an earlier post, bw64installer is now part of the playground repository of DarkLinux which should allow it to grow even more. In the meantime, I have achieve my initial major goal with it- to make the creative and unique BW64 LIVE systems capable of acting as easy-to-use and desktop-friendly installable operating systems. This allows bluewhite64 a best-of-both worlds approach with full compatibility to slackware on one hand, and an easy preconfigured and modern desktop distribution on the other.

While merely writing an installer is not such a huge contribution, the fact is that nobody had done it – and writing a good installer for a distro isn’t easy. I had done it in the past and I could draw on my old experience (and some of my old code) which allowed me to write it faster than most people could with a solid set of features.

There are two new feature requests which I didn’t have time to finish before the release-freeze but they will be in the next update, along with any other sensible once I can come up with (a crucial thing about installers is that bloat is even more evil than usual – more steps means more difficulty and slower installs, so you have to be careful about which features you actually choose to include).

One side-note: please note that the current release does not support ReiserFS without some tweaking, so please install on ext3 partitions.

Oct 022008
 
No Gravatar

Today I installed Kubuntu on my new work laptop (have I mentioned that I have taken a new job ? I’m now the new Unix administrator at Intec). The laptop is not a latest and greatest but still a pretty nice buy. Of course Del’s come in all flavors and sizes, this one has an Intel 965 graphics card and about 3Gb of RAM on an 80Gb hard drive.
The only major hurdle was that ubuntu refused to recognize the intel card, turns out that the Xorg driver for it wasn’t installed but even after installing it, it still only detected VESA support – that made it impossible to get dual-display support working well at all (especially since the laptop has a widescreen 1280×800 screen and the LCD external at work does not – it does 1280×1024) it would clone but then half the image on the left screen was cut off at the bottom.

I spent some time in various places on the Ubuntu forums and found no working solution, though I did get a hint that let me get another document that worked. I found a very good howto at Intel Linux Graphics which helped me to get a fully working setup using xrandr rather than xinerama for the dual display. KDE4 works fine on it, though the OpenGL support is flakey (not just in KDE in general), right now XRender based compositing with kwin is working well but I would like to see if I can get the OpenGL to work better (I am guessing that like many Intel cards you can adjust the video memory in the BIOS but I haven’t had a chance to look yet).
One nasty bug was that when I tried to enable OpenGL based compositing it crashed the system, and despite me not being able to click on the “keep this setting” button, it also trashed the settings and I had to remove my .kde4 directory to make it work again.
I do need some windows apps as part of my job, so I loaded virtualbox and stuck windows XP in there, works perfectly (for the limited use I need it for anyway).

Right now it seems that sound isn’t working, but I found some mention of this online so I will look at those pages (it wasn’t important today and I had work to do) later on and report on the results.