Friday, April 21, 2006

Short Notice Savior

Before my departure to Desktop Linux Summit, I needed to get my laptop updated with something new and snazzy in regards to a distro. My first thought was to go with the usual, opensuse. Little did I know that the 10.1 RC1 was still a bit rough unlike the 10.0 RC1 that I had on it. Yast had a mind of its own most of the time and would decide when it wanted to open the software management dialog so that I could install rpms. Fighting with this repetedly while trying to compile KDE from SVN proved difficult, too dificult in the crunch that I was in.

I decided to "run away" (a la monty python) and find something else that could possible run better and have 3.5.2 on it since my chances at compiling it on my 650mhz laptop in 2 days were close to nil. Enter Kanotix! It is a Debian-Sid based live cd with a quick (and I mean under 20 mins full install on my slower than life laptop) graphical installer. Only problem I really had was that the network card I have worked fine in the live cd boot, but not after the install. I new what modules to load to get it running, but others may have difficulties with that. I'd also like to say a big "THANK YOU" to devil in #kanotix. Their community left a nice impression on me in their desire to help _everyone_ in the channel. Those guys were just non stop with others even while helping me in my dire times. I'd definitely suggest checking it out to anyone reading this.

If anyone attending the summit reads this, please feel free to come up to the KDE booth provided by Linspire and say "Hi". We're always interested in chatting it up, or answering any questions you may have, especially SuperKaramba related questions. ;)


  • Network card working when booted as Live CD, but not working after harddisk install?

    I had the same issue once.

    The problem was, that the Live CD used the "eth0" as the interface name, while the harddisk install used "lan0" (or was it the other way round?).

    I *think* it has to do with the new "udev" method of assigning device names, which somehow doesn't cleanly transfer to the harddisk installation.

    Sorry, can't remember details right now. But this hint may help you find the exact solution yourself.

    By pipitas, at 10:03 AM  

Post a Comment

<< Home