Monday, September 13, 2004

New Logo and possible consortium needed

Hey all,

Finally, I have the new logo online, designed by Andreas Nilsson, as you can see on the side menu. Hopefully this symbol will remain one in the future that represents Linux device drivers.


One thing that I have discussed about is that there are two different types of driver management systems... Ones which utilize an existing package manager, and one which utilizes its own package management system. The issues have always been that ones that don't hook into existing package managers can't easily tell which packages need installing well (there are ways of allowing them though), and the problem with using the existing ones is that many repositories will be needed, which will scare away driver developers

Jono Bacon (the brainstorm behind the article posted) agrees with me that distro developers need to step forward, representing a large amount of distro's and need to collaborate to develop a common standard this time. People would lose faith in a system if there are 600 different standards for it, so this time we need to do it right the first time (possibly use a portage like system?).

One issue with trying to make packages work on every distro has been that some distro's don't follow the Filesystem Hierarchy standard (ie. some put /etc in /config etc). My idea was to develop a bunch of standard environment variables covering all the standard locations, which make scripts would use etc.

Phase 1 of such a process would be to at least allow compile time compliance with the system, and phase 2 might be to allow full runtime compliance (would be nice to have it so that users could even move /config to wherever they dream, but that's not going to happen).

Someone on freedesktop mentioned that such a standard is already being designed http://freedesktop.org/Standards/basedir-spec/basedir-spec-0.6.html

It seems though that it is only for home directories, not the entire filesystem, so I am thinking of quickly spending my weekend designing one for the entire filesystem

No comments: