Archive for the ‘Mandriva’ Category

Day Planner 0.9, and looking forward

Saturday, May 3rd, 2008

Day Planner 0.9 has been released. It is available for download as a Mandriva RPM, Ubuntu deb, Debian deb, generic installer and source tarball.

The release focused primarily on fixes and cleanups. A bunch of minor bugs were fixed, and I rewrote most of the iCalendar back-end. It should be faster now and preserves files better than it used to.

This release includes a dummy maemo interface. It can currently fully display a Day Planner calendar, and has a UI quite similar to the desktop edition. However, it can not edit or add any events, and is as such not as useful as it might have been. The plan is for the maemo port to be ready for 0.11.

0.10 will (among other things) feature a new HTML exporting module (which has been in the works for quite a while), a cleaner, object-oriented version of the add/edit event windows (to simplify their use and maintainance. The current code that handles it is a bit ugly).

The major user-facing change will be the addition of a GUI for calendar subscriptions. 0.9 includes support for them (though it isn’t really announced because the feature isn’t ready), but one has to manually edit the config file.

Microdia (0c45:624f) webcam on Linux

Sunday, April 27th, 2008

(Re: Proprietary Webcam driver wonders).

I recently discovered a free driver for my GF’s builtin Microdia webcam. It works very nicely (better than the crappy proprietary one did when I tested the “trial”). So if you’ve got a Microdia webcam, at least the 0c45:624f one, now you can have it working properly, with good quality without paying a load of money for a one-time one-kernel one-arch license for a proprietary one.

git clone http://repo.or.cz/r/microdia.git
cd microdia
make
sudo insmod ./microdia.ko

Then just launch Cheese or your favourite webcam program and off you go.

Thanks a lot to those that took the time to develop a proper driver. If you’ve got a paypal account, I’ll donate some money for your hard work.

Update: the module is now named sn9c20x.ko, so the last line becomes sudo insmod ./sn9c20x.ko

Update 2: According to brandon in the comments, the kernel module is in the upstream kernel as of 2.6.31.6

Proprietary webcam driver wonders

Monday, December 10th, 2007

My girlfriend has a builtin webcam on her new x86_64 laptop.
The webcam has no free drivers, but there is a proprietary one available on linux-projects.org.

Pay 10EUR and you get the driver. Okay, doesn’t sound /so/ bad. But the driver is only available for x86 ubuntu gutsy, no other arch, no other distro, no other kernel. If you want it for /your/ kernel you have to pay 100EUR. Wonderful. There’s no way I’m paying 100EUR for a proprietary webcam driver. Buying a new, working, webcam would even be cheaper! She runs x86_64 so there’s no way to get that driver working there, without paying that 100EUR. The camera is Bus 005 Device 002: ID 0c45:624f Microdia.

If someone does decide to write a free GPLd driver for it, I’ll donate some money to that person (I don’t have 100EUR to give away, but I can do at least 30-50EUR).

This again goes to show the pain of proprietary drivers. I don’t mind *paying* for drivers, but when the drivers cost more than the device did, and a device working equally well would be cheaper than buying the drivers it has gone too far. I would have easily donated money if the page said “here’s the driver, it’s GPL so do what you want, but please donate 10EUR if you can” (and I have donated to FOSS projects before).

Update, see: http://blog.zerodogg.org/2008/04/27/microdia-0c45624f-webcam-on-linux/

Ubuntu/Mandriva comparison

Tuesday, October 30th, 2007

I know you’re probably sick and tired of these comparisions. If so, don’t continue to read, and definetely don’t troll in the comments :).

I had so many various problems with 2008.0 that I felt it might be prudent to try some alternatives (I’ve upgraded to 2008.0 on 4 boxes so far, with not a single one going smoothly without issues). My choice fell on Ubuntu. Was considering to try out Debian too, but I know Debian is good – but not quite end-user desktop-friendly.

I live on the commandline. So just about all I do is identical on all distros since I just carry my configs with me. However I still see hw-detection and general usability and integration. So, I’m going to just start with a little comparison, and we’ll see where we go from here. The comparison is seperated into positive (+) and negative (-) comments.

This is all my personal opinions.

Ubuntu (7.10):
+ Live installer works very well. Especially nice that it removes unneeded locales and downloads missing ones during installation.
+ GNOME default desktop
+ sudo-only actually works quite well
+ Very well integrated into GNOME (ie. 3d-effects can be set up in the appearance applet in GNOME)
+ Clean, empty GNOME desktop by default
+ apt-get is great and shows how much it needs to download
+ aptitude looks good
+ integrated distribution-upgrade system
+ detected all the HW and worked nicely
+ Quite polished
+ Appears quite stable
+ gnome-app-install is pretty
+ Firefox patched to use native package manager to find plugins
+ Totem automatically finds missing plugins
+ More progress shared with other distros (ie. networkManager)
+ Progressbars when installing software (always in the GUI)
+ Ability to see verbose installation messages in the GUI
- Missing some translations
- Some of the translations isn’t of the best quality
- Synaptic is very ugly
- For some reason when I removed evolution, the menu item didn’t get removed (not even when using apt-get purge)
- Uses a white mouse pointer by default (I don’t like it, but luckily that can be easily changed)
- No profile.d
- Told me it needed to reboot after installing the nvidia driver

Mandriva (2008.0):
+ urpmi is also good
+ Well translated
+ Good hw detection
+ Has a tool for /everything/
+ PLF
+ RPMDrake is good (better than synaptic, not close to gnome-app-install)
+ Great perl module packaging
+ MP3 playback by default
- GNOME Live CD not published along with the rest of the distro
- GNOME Live CD not advertised for new users, they only get the option of KDE
- No beta of the GNOME Live CD
- Not as well integrated into the DE
- The tools aren’t as “polished”. Ie. when a drak* tool needs to install something it pops ups 3-4 small windows informing about what it’s doing – none of them has a progressbar, and sometimes they say the same. Also the windows aren’t refreshed as often, but block and become unresponsive.
- Although urpmi got improved it still doesn’t say how much it needs to download. Something other distros have had for ages, and that I opened a wishlist bug for in 2005
- I haven’t installed one 2008.0 machine without various issues (sound stopping to work, performance bad, sound not working properly, X driver not set up properly)
- Live CD set up autologin by default without asking about it
- No Mandriva Flash GNOME (except GUADEC edition)

Trolls and flames in the comments will be deleted.

Update:
Note that I made no conclusion on which distro was better. I’m simply attempting to write a simple and incomplete comparison. The comparison is also mostly based upon first impressions, and should be treated as such.

I’m also not saying I’m switching camps for those wondering ;).

Concerning GNOME Flash. Well, maybe that isn’t really fair. Flash is good, and GUADEC flash is good. However I did get annoyed that only a KDE was made available.
Also, no, the point isn’t /really/ that Mandriva prefers KDE for LiveCDs – it so happens I prefer GNOME and thus see GNOME as a plus.

When I talk about “better” integration, what I mean is basically that Ubuntu is more centered around the desktop environment than Mandriva is (which can be good and bad I guess).
In Mandriva to configure stuff you would use drakconf, in Ubuntu most is in the GNOME System menu. Granted, some stuff from Mandriva is available there too, but Ubuntu has everything.
However, Mandriva has, like stated, tools for just about everything. Ubuntu does not. They’re quite differently structured. The Ubuntu tools look like they are /made/ for GNOME and part of GNOME (which I guess they are). The Mandriva tools look like a seperate app, which they are, and is probably also good considering the wealth of tools available. It just feels a bit easier to just System -> Administration and select whatever you want to do there. Don’t get me wrong, Mandrivas GNOME is good. Kudos goes to Mandriva for giving a GNOME LiveCD, I’d just like to see it better marketed (not like on mandriva.com right now where you only get the option of KDE. KDE is good but imho you should be able to chose, as Mandriva One now appears to be the preferred version to download).

Concerning autologin, if I recall correctly, the previous versions of Mandriva One did not activate autologin by default, which is why I reacted negatively to that this time.

Update 2:
Yes, urpmi displays how much it needs to /install/. But it doesn’t (and can’t, since the information isn’t available in the current hdlist formats) display how much it needs to download. Which is often a good deal less than what it will take when installed.

drakSimpleConf

Saturday, September 16th, 2006

I’ve been thinking of a method of creating simple configuration UIs.

Take the following config file:
RunMode = Inetd
AuthMode = Closed
Restricted = true

To create a simple configuration GUI for this I would write something like this:
filename is /etc/example.conf
setting RUNMODE can be (Inetd, Daemon)
setting AUTHMODE can be (Closed, Open)
option RunMode is RUNMODE with name "Run mode" and tooltip "Which mode to run in"
option AuthMode is AUTHMODE with name "Authentication mode" and tooltip "Which mode to use for authentication"
option Restricted is BOOLEAN with name "Enable restriction" and tooltip "Enable this if you want to enable restriction of user rights"

The initial filename option selects which file the config file is.
The first “setting” defines a type of entry in the config file that can be either of the value “Inetd” or “Daemon”. This would create a drop-down widget where you can select “Inetd” and “Daemon”.
The second setting defines the same for “Closed” and “Open”.
The first “option” defines that the option in the config file “RunMode” is of the type “RUNMODE” and the name of the option that is displayed in the GUI is “Run mode” and it has a tooltip saying “Which mode to run in”
The second is the same.
The third one defines that the option “Restricted” is of the predefined type “BOOLEAN” (which is predefined to be true/false, this creates a checkbox instead of a drop-down box).

Now begin your slaughtering. This is still just an idea. There is no code yet. What do you think of the concept of creating a whole configuration GUI for an app using a single file like this? I’m thinking it would be okay for daemons and such.
What do you think of the syntax? I just grabbed it out of my head today and thought it might work. I want the syntax to be simple and human-readable. The point is that you should be able to hack together a GUI for any program with a simple configuration file in a few minutes.

Flame me.

Italian ssh tips translation

Wednesday, January 18th, 2006

Now this is quite cool, Davide Duina (I think I spelled it right! :) of http://mandrakeitalia.org/ has posted an Italian translation of my SSH tips and tricks.

Original at: http://zerodogg.iamaturtle.org/index.php?type=docs&page=sshtips
Italian at: http://www.mandrakeitalia.org/modules/wfsection/article.php?articleid=151

Where is the madness police?!

Friday, December 16th, 2005

Okay, I was just made aware of the Brazillian Mandriva store by Claudio. The DARNED THING USES ASP! AFAIK it isn’t Mandriva that runs it (duh), but STILL!
For a little more clarification:

[0 zerodogg@drizzt html]$ HEAD mandrivastore.com.br
...junk...
Server: Microsoft-IIS/6.0
...junk...
X-Powered-By: ASP.NET

Someone tell me I’m dreaming! *cries*

Common configuration parser (CCP)

Thursday, September 29th, 2005

I’ve been thinking about ways to upgrade configuration files lately and I’ve come up with the idea for CCP (common configuration parser). The idea is to take one template file, one old configuration file, one definition file and one mode. To give a better example of how this would work:
ccp --type basic --mode rpmnew --template /usr/share/example/config.ccptemplate --oldfile /etc/example.conf
This here would tell ccp to work with the configuration type “basic”, in the mode rpmnew (upgrade if a rpmnew file is found), use the template file /usr/share/example/config.ccptemplate and upgrade the old configuration file /etc/example.conf. Settings not found in /etc/example.conf would then be taken from /etc/example.conf.rpmnew. For an even better understanding of the idea lets look at it some more. For example before the upgrade /etc/example.conf could look like this:

# Example configuration file
SystemVersion = 0.1
Mode = public
Extensions = off

/etc/example.conf.rpmnew could look like this:
# Example configuration file
SystemVersion = 0.1
Mode = private
Extensions = on
AllowUsers = yes

/usr/share/example/config.ccptemplate could look something like this:
# Example configuration file
SystemVersion = $CCP::CONF:SystemVersion
Mode = $CCP::CONF::Mode
Extensions = $CCP::CONF::Extensions
AllowUsers = $CCP::CONF::AllowUsers

ccp would read these files and write the new /etc/example.conf as:
# Example configuration file
SystemVersion = 0.1
Mode = public
Extensions = off
AllowUsers = yes

More advanced files could be supported by different –type’s. This is still mostly an idea that’s growing in my head but this is the basic thought of it. Quite possibly –template wouldn’t be needed and it would autogenerate a template on-the-fly by using the .rpmnew (or whichever file is the new one – ccp is not rpm specific, it is just one of multiple modes it would be able to run in).

Nexuiz

Friday, June 10th, 2005

I finally finished the nexuiz package! Got Michael to do a patch for it that makes it compile properly and split it into 4 subpackages (one nexuiz, nexuiz-glx, nexuiz-sdl and nexuiz-data). Now it’s time for me to have a break!