Siduction Forum
Siduction Forum => Experimental => Topic started by: DeepDayze on 2011/12/23, 02:06:03
-
Anyone planning to try damentz's wonderful Liquorix kernels with siduction? In fact maybe he should be invited here :)
I remember the aptosid devs regarded him as a bit wacked but he's indeed a smart fellow...his kernels work quite well
-
/me I would appreciate to have such a skilled discussion partner like damentz here ...
-
You guys are free to invite him ... and why not try alternative kernels with siduction?
But hey, towos siduction kernel is quite cool and works perfectly here ...
-
And the liquorix-kernel can't be included in the iso, since it is not dfsg.
-
And yes cryptoserve:
linux "3.1-6.towo.1-siduction-amd64" works perfectly here!
... using systemd inspite of default insserv as init.
-
You guys are free to invite him ... and why not try alternative kernels with siduction?
But hey, towos siduction kernel is quite cool and works perfectly here ...
No not knocking towo's kernels just having choice is nice :)
@towo, not sure what license his kernels are under..but I'm sure he'd have no problem complying with the dfsg if it came down to that
-
As I appreciate the contribution of highly gifted programmers and hackers somebody who knows him could invite him. I am sure he has more to contribute.
But licensematters, as mentiond my towo have to be kept in mind!
-
As I appreciate the contribution of highly gifted programmers and hackers somebody who knows him could invite him. I am sure he has more to contribute.
But licensematters, as mentiond my towo have to be kept in mind!
I might ask him that question as to what license his kernels are under
Yes he's quite intelligent and even slh felt threatened by how smart he is
-
I might give it a whack also, I am now doing a android kernel
-
I use the liquorix kernels on my installs that are built from stock Debian. They are great kernels, but mostly I only use them because I track Debian testing, and except for a few months right after the release of a new stable, they tend to get their kernels long in the tooth.
I'm waiting for my USB to finish copying and then I'll be installing siduction on an old desktop I have around that I'm going to be selling off.
Will have to sometime try the 2 kernels maybe on some of my "problem" hardware on some of my laptops see if one or the other is actually superior.
-
I use the liquorix kernels on my installs that are built from stock Debian. They are great kernels, but mostly I only use them because I track Debian testing, and except for a few months right after the release of a new stable, they tend to get their kernels long in the tooth.
I don't think so:
http://packages.debian.org/wheezy/linux-image-2.6-686
-
yes, right now it's still up to date. But it will start slowing down with keeping up to date after they hit 3.2.
-
You guys are free to invite him ... and why not try alternative kernels with siduction?
But hey, towos siduction kernel is quite cool and works perfectly here ...
I included siduction sources.list just to get towo's kernel.
So far, it seems to out perform the liquorix one, at least the way I use linux. I have a linux host (core2 quad, 8gb ram) and run a Win7 vm guest, configured to use 4 cores and 6gb ram.
I don't see any pregnant pauses with towo's kernel (so far).
-Hinto
-
...
... using systemd inspite of default insserv as init.
Hi ralul,
is your statement a recommendation for a change?
Or is it siduction standard from installation?
Because I migrated to siduction without a complete reinstall (I know that is better), I have insserv operational.
Makes it sense to change? Is it possible to change? And if yes how (just purge and install?)?
insserv:
Installiert: 1.14.0-2.1
Kandidat: 1.14.0-2.1
Versionstabelle:
*** 1.14.0-2.1 0
500 http://ftp.de.debian.org/debian/ unstable/main amd64 Packages
100 /var/lib/dpkg/status
systemd:
Installiert: (keine)
Kandidat: 37-1
Versionstabelle:
37-1 0
500 http://ftp.de.debian.org/debian/ unstable/main amd64 Packages
-
Systemd at this moment is not for the faint at heart and would leave you mostly on your own. On a testbed: yes. productive? no way.
greetz
devil
-
thanks, so I leave it as it is.
-
...
... using systemd inspite of default insserv as init.
Hi ralul,
is your statement a recommendation for a change?
No, no! As devil said, systemd is highly experimental. What I hoped from systemd: Better control of my whole system and services.
Also my systemd enable Debian-siduction runs and starts up faster: I have nearly no control.
The problem at the moment with systemd: There is a sysv compatible layer that starts all of /etc/init.d scripts. You have ways to control but very unconvenient:
- All not, or you have to
- disable one by one (You have to make named links to /dev/null)
-
yes, right now it's still up to date. But it will start slowing down with keeping up to date after they hit 3.2.
I still don't think so, and i don't know why you think that.
btw:
that is what you wrote:
and except for a few months right after the release of a new stable, they tend to get their kernels long in the tooth.
and a few months is ago more than just a few months.
-
Okay, they stay up to date for 6-8 months before they get stale on kernels.
-
Hi everyone,
To make things clear, I don't think it's appropriate for Liquorix to be part of an ISO as a preinstalled choice. Towo pointed out the first one, it is not DFSG. And second, Liquorix contains less tested features (CK patches, BFS, BFQ, special RFC patches from LKML that could or could not improve performance and behavior of the kernel in all circumstances).
Also, I would like people trying Liquorix to know what they're getting in to, and for it to be their choice to install it (according to their own curiosity or research). Providing Liquorix as a pre-installed choice may just further confuse new users.
And last, if anyone needs help or wants something changed, you can point them to the Liquorix forums: http://techpatterns.com/forums/forum-34.html
PS. Congratulations Towo! One of many reasons I departed to work on my own kernel was that sidux's support ignored feedback on their kernel. It was very one sided and no discussing or reasoning made any difference. I'm hearing good things about you, so good luck with siduction!
-
I have yet to need a Liquorix kernel. Towo's work great, even under a heavy load such as hosting multi-core 64-bit vm guest.
Personally I left sidux because (among other reasons) VMWare became a pain to patch due to the kernel that was shipped with sidux.
The reason I have re-imaged my 2nd PC and use the siduction packages in my primary PC is the rock-solid history I've seen with the siduction guys.
-H
-
Hi damentz, good to see you here!
By the way, there is a fresh BFS for a 3.2 Liquor, have a look at
http://ck.kolivas.org/patches/3.0/3.2/3.2-ck1/patches/
-
Welcome over, damentz...and keep up the good work on your kernels as they work very well. Perhaps you could even make some contributions to siduction that you been denied with sidux and aptosid
I also remember towo getting so much flak by sidux/aptosid team for offering his packages on frickelplatz..smart move to move away from that cancerous riffraff
-
@damentz,
Glad to see you here, too. For the longest time I was running Liquorix in LMDE and #!.
-H
-
@damentz,
Glad to see you here, too. For the longest time I was running Liquorix in LMDE and #!.
-H
I've also used his kernels with great success on Semplice Linux and AntiX too. The Liquorix kernels are mainly for people who are adventurous like me :)
As for Towo's kernels they are quite solid too with none of slh's defaults that tend to break things like VMware and fglrx
-
^Yep.
-
.. Sorry, I know this thread is a bit long in the tooth..
Just wanted to add a comment as long time Liquorix user..
Haven't used a Liquorix Kernel since Squeeze froze..
However I was always impressed with his work and happy that the alternative was there to use.
That said....(I did not know until today that kernels here were the work of @towo)
One of the compelling features of Siduction is the robust and responsive kernel...Good Job!
I like the engine.
Of course should either/both kernel hackers like the notion, it could benefit each to communicate.. just a thought.