Shortly after funzt.info was being hacked I had some trouble with my webhoster, so I decided to change. Due to this, funzt.info was down for a while.
This was my first time moving a domain to another hoster, but everything went very well and now this site should be back online again!
And again, a new design. This one was also made by headsetoptions (like the former orange/dark one), I’ve just added some minor color modifications.
And stay tuned, the promised “Installing-Sidux-HOWTO” will follow!
Two weeks ago funzt.info was hacked. Some guy called “geek hacker” managed to replace index.php with his own and this is what showed up in your browser:
I was playing a little distro-hopping lately and - having a big favor for Debian - came across “sidux”. This distro is released by former “Kanotix” developers and is based on Debian sid. Sid being the “unstable” branch of Debian is a bit of a risk when used as main OS. Though it may be more stable than some other released distro you’re still having chances it’ll break after one update or the other - and if you don’t know how to fix it you may run into trouble. This is where sidux comes in. sidux includes a script called “smxi” which handles most of the system’s maintenance. Agreed, you’ll have to use the command line, but it has never been easier! This script get’s you through system updates, installs proprietary Nvidia/Ati drivers and other third party software if desired. If some very new software releases come to sid repositories and are causing major trouble, smxi puts this software “on hold” which means that it’s not going to be installed. For example: Xorg 7.3 just hit Debian unstable and users are having a lot of problems with it. When updating sidux via smxi, you’ll receive a warning and Xorg will not be updated. You should not do a “usual” Debian dist-upgrade, because then you won’t benefit of the advanced features of sidux’ smxi script.
Gigabyte released a new BIOS for their GA-M55S3 motherboard and I couldn’t resist updating. To make it short: if you’re running Linux, don’t… After updating Linux will boot only with “noapic” as kernel option - again. I guess only BIOS version “F6” doesn’t have this error (see this post). I skipped version “F7” so I can’t say anything about this version, but all versions prior to “F6” had the same issue. If you don’t have any real needs for updating your BIOS you shouldn’t consider an update anyway.
If you’re running Debian testing (aka “Lenny”) which brings no Nvidia driver packages - only the legacy ones - or like to install the latest drivers by Nvidia for Etch, you’ll be running into a problem: the Nvdia installer won’t find everything necessary for compiling the kernel module. So, here’s a small HOWTO: