more sidux trickery and unbelievable stupidity

You would think that with entire riot regarding sidux where many of the users finally took it upon themselves to yell at the developers in the forums for acting deceptively, their actions would change.

That's not the case.

I bumped up an old thread of mine asking the kernel packager for sidux named Steffan-Lippers Hollman to enable a kernel option named TIMER_STATISTICS. This would allow you to view which threads and processes cause the most wakeups per second via powertop.

slam, another puppet developer of sidux promptly answered my response with something reminiscent of blind faith, putting full trust in a kernel packager that thinks TIMER_STATISTICS causes a measurable performance penalty, enough to increase power consumption.

An explanation was given as to why their reasoning was unbelievably stupid, but apparently they don't answer in relation to your posts if they are wrong - so the thread moved, locked, then deleted. (link to deleted post)

Speaking of deleted! It seems that sidux has also removed an essential part of their distro support, smxi. The entire sub-forum was deleted in, what seems like, another step in their plan to quell the voice in their "community".

Users also seem to be splitting with sidux and switching to other distributions like Arch. How can you tell, damentz? Well, take a look at the sidux front page now. They no longer receive donations frequently enough to post a widget expressing their income with pride. In order to subvert this quick observation, they show only the top 3 donations (which is, in essence, very useless for data in any statistics).

In an also very childish manner, they ban all users that mention a few keywords (such as smxi, liquorix, or help) in their forums or irc chat. However, they are not very clever so it's easy to work around these artificial rules that bear benefits to nobody.

Continuing an observation to their juvenile behavior, the following thread should have never happened and exhibits their inability to handle their users.

http://sidux.com/PNphpBB2-viewtopic-t-16940.html

That thread could have been reduced to 5 posts or less if the developers actually read the posts. There are many instances through out this thread which show that many of them actually do not comprehend what is written, and out of desperation, a separate unrelated response is posted that attacks the original author indirectly with lies and other undomesticated thoughts.

To put it simply, the following quote describes sidux in a very concise manner:

"We're a ban first, don't ask questions anyway kind of an organization." - sidux

new branches and honky sources

Out of thin air, through the kinetic energy of pure boredom, I have cast a spell accelerating the tumor of another branch from the Liquorix tree called past.

Past is not a branch to remember your relatives birthdays or to dwell on things that just depress you, but to support the previously stable version of the Linux kernel so you can stay supported with ugly hacks like fglrx and provide 3 months lapse before any other unusual module or bug prevents you from using the currently stable kernel.

You can use this branch by adding past to your deb line, like this:

deb http://liquorix.net/debian sid main past

At the moment, this branch currently contains my old 2.6.30 kernels with a large set of backports to fix some logic with the CFS process scheduler (ingo's sched-core-for-linus branch).

I also wrote a script to help automate the publishing of raw sources to http://liquorix.net/sources. The script itself is located in that directory for anyone interested.

#sidux support is garbage

<damentz> cheater-conrad, what did you need?
<damentz> cheater-conrad, if you run compiz --replace from a terminal, do you get anything about gtk-window-decorator?
<etorix> damentz: not here pls
<etorix> damentz: hes already there
<damentz> etorix, you're splitting support unnecessarily which makes something that should be supported, unsupported
<etorix> damentz: ...
<damentz> it's really just a package set, why should we split it into another chatroom subsection
* ChanServ gives channel operator status to etorix
<damentz> it's the same thing as helping someone with recordmydesktop
* etorix sets ban on *!*damentz@*.austin.res.rr.com
<etorix> damentz: not here pls


Please discard any attempts at receiving any real help in the #sidux channel or forum, the signal to noise ratio has dropped lower than Ubuntu's. In fact, the sidux team created a forum specifically for "unsupported" items (really things they are too stupid to understand or burst their ego bubble) which has recently become much more helpful than the absurd amount of split topics which make getting correct support impossible.

For anyone interested in this distribution, check out #smxi or #linux-smokers-club on irc.oftc.net for an accurate overview of the benefits this distribution may offer. The official sidux irc channel has acquired a case of bull shit and can no longer be trusted to make decisions beneficial to most users.

Also, some of you may have noticed that the kernel of sidux has been steadily losing features and performance due to bad configuration choices on the kernel maintainer's end...

Try adding the kernel described at http://liquorix.net if you value your desktop usability. It features patches from Con Kolivas, zen-sources, and a configuration designed for low latency performance, a little like the sidux kernel but much more throughput which is essential for gaming.

Included is the ramzswap module which allows you to send your swap blocks to a virtual device stored in ram. All data entering this device is passed through an LZO function, effectively reducing the size of the cache stored in ram.

Besides this the BFQ scheduler is currently the basic disk scheduler until io-controller replaces the current defunct disk scheduling infrastructure. To minimize the effect of greedy disk copying, a patch from CK reduces the effect of bulk data writes and reads to allow fair use of non volatile media.

If there are any questions, ask me on #smxi!

brood before the storm

Hey everyone, I try to keep my posts as quintessential as possible but I have not blogged anything new lately - here's an update to quell the silence.

The Liquorix project is proceeding well except for the zen maintainers who rotate according external pressure. The current maintainers are not updating patch sets on time or maintaining the correct patch sets, vital ones like madwifi. Due to these circumstances, I'll be learning over the weeks the tricks and mysteries to seamless kernel patching with git from foreign and unusual sources to part this dependency.

This and last week has been painful though, I'm retaking the Red Hat exam to get RHCE this time (no flaw). This exam didn't incur any stress penalties I'm aware of, but the laptop I work on most frequently simply decided to break the die of the nvidia GPU. So, apparently this is common for Dell laptops manufactured last year and I'm an unlucky victim.

I also scored an awesome job (which will remain undisclosed) that I enjoy working at - thus most of my daily energy is spent the first 10 hours I'm awake. Falling asleep 2 hours earlier is saving my life though, I'll keep that up so I can kick ass and chew bubble gum when I get home :).

So, I'm satisfied. Payment for my education and a logical future share space under an umbrella I control.