marekpasnikowski at interia.eu
Sun Jun 20 15:38:48 CEST 2010
Wow, looks like I accidentally poked a stick into the anthill.
I am sorry about my wrong assumptions, but really the Lunar websites give
feeling of long-dead project. Short notice somewhere on main page would do the
job. Soon I am going to replace my old laptop with a netbook. This time I will
monitor the installation and report bugs. From my last installation with newest
ISO I remember that I couldn't compile kernel myself (when chosen, a few lines
of text would print in terminal and got hidden by kernel installation menu
immediately); later, when I wanted to re-check chosen font, installer forgot all
my settings. I noticed this one after succesful DE installation, so now I am
left with generic hostnames etc.
Wiki should be filled with some info about hardware configuration. First I
wanted to write some info regarding my hardware, as I still have to do this. I
have some problems with my hardware as I don't know, what framework is used in
Lunar to configure it. I mean, should I try tips working for Gentoo or Debian or
"Which documentation are you missing - not that there would be much to document.
There's `man lfirsttime` telling you about `lin`, `lrm`, `lvu`, `lunar`
and there are a couple of interesting files in
/var/*/lunar (shell scripts, log files, moonbase, dependency-files, ...),
and there is /etc/lunar.
That's everything a full installation knows about lunar I'd say,
so why writing documentation of files everyone can read in a day..?"
I had no problems with basic installation, thanks to existing documentation
files, but it is not enough to get me through other aspects of configuration.
Now I am running basic system + kde4 + chosen dependencies + flashplugin +
opera, and I have no idea, which graphic driver is powering this. I can't run
compositing (I don't really need it, but still miss it). Other thing is, that
"search" field in Lunar Modules site (which gives impression of engine searching
the requested modules) doesn't work at all, and I don't feel like sieving all
3500 modules in search of Intel GMA driver. Also I have no idea, how to make KDE
ask for password, when changing system wide settings, so I can save them. Such
things should be pointed in Wiki. Even if it means copying text from other
distros' Wikis. I, and many others, treat Wiki pages as first info source. It
should be there. I, for instance, don't like documentation in form of example
files, as it can be very confusing (that's why I resigned from Gentoo, where I
had no idea, how to make my Broadcom wireless run with KNetworkManager.
So, my first proposition is such:
1. I kindly ask You for help configuring my hardware.
2. I write it down in Wiki.
3. I learn ways the system gets configured.
4. I continue to fill Wiki up.
I mentioned, that I will buy a netbook. I will treat it as experimental machine,
where I will try to build ultimate KDE desktop. I think this will give me great
deal of experience. I am really looking forward to it. Anyway, I still find it
amazing, how fast I got to the core. It implies some lack of technical knowledge
about the system (mainly about the system files), but now I feel that I would be
able to administrate any given Linux distro with decent documentation.
Auta kilka tysiÄcy zÅotych taniej? Przebieraj wÅrÃ³d tysiÄcy ogÅoszeÅ!
Sprawdz >>> http://linkint.pl/f2724
More information about the Lunar