Liquorix Kernels

Started by DeepDayze, 2011/12/23, 02:06:03

Previous topic - Next topic

DeepDayze

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

ralul

/me I would appreciate to have such a skilled discussion partner like damentz here ...
experiencing siduction runs better than my gentoo makes me know I know nothing

cryptosteve

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 ...
- born to create drama -
CS Virtual Travel Bug: VF6G5D

towo

And the liquorix-kernel can't be included in the iso, since it is not dfsg.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

ralul

And yes cryptoserve:
linux "3.1-6.towo.1-siduction-amd64" works perfectly here!
... using systemd inspite of default insserv as init.
experiencing siduction runs better than my gentoo makes me know I know nothing

DeepDayze

Quote from: "cryptosteve"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

Lanzi

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!

DeepDayze

Quote from: "Lanzi"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

piper

I might give it a whack also, I am now doing a android kernel
I have a Lucky Rabbit:    "Svoot" ..... (It's Swedish)

I am MAGA

tlmiller

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.

nadir

Quote from: "tlmiller"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

tlmiller

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.

hinto

Quote from: "cryptosteve"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

mylo

Quote from: "ralul"...

... 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

devil

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