hm.. ok. i switched back to the unpatched test7 for now,
since i do use the nvidia-kernel module a lot. thanks for
informing me._________________proud to be a scout and a chronic penguin hugger
Legion of Lore - site

7-prelove1 works like a champ here! using generic 'ati' driver and window shaking doesn't increase cpu usage at ALL! And X is NOT reniced JACK also works well, although it complains about not being able to lockdown memory for a RT thread, so i just renice all apps that use it...

Thank You,
sk

Last edited by sumin k'adra on Sun Oct 12, 2003 11:21 pm; edited 1 time in total

This is odd. test7-love1-DANGEROUS is MUCH slower than test5-love4, the last one i used. it also uses much more memory, so im swappen more. and this is not including cache and buffers. did i do something wrong in xconfig?_________________OH MY GOD! Kenny just killed Kenny!
That Basterd!

Probably right - the VM is very different... I told you it was experimental.

Anyways, it's my duty to announce that I'm looking for a maintainer for love-sources since other things will take up my time in the near future, and personally I think I've taken love-sources as far as I personally am able to carry it.

So once 2.6.0-test7-mm1 drops (if at all - andrew seems silent on that issue) I'll put out a love kernel based on that and then I'll step down as maintainer, I can still act as co-maintainer but the support business and reading lkml, hanging on #offtopic and #kernelnewbies, and reading bitkeeper logs is simply to much right now.

Maintaining love-sources is a fairly simple job as such, you need to know a little C, the use of diff and patch and being nice to kernel developers also helps. As I stated before it's slightly skilled monkey work, all it requires is a tiny bit of coding skills and a lot of time.

Anyways, it's my duty to announce that I'm looking for a maintainer for love-sources since other things will take up my time in the near future, and personally I think I've taken love-sources as far as I personally am able to carry it.
.

LOVE sources are great - thanks for all the great work, lovechild!
I can only hope that the love sources will continue to rock
my box

Probably right - the VM is very different... I told you it was experimental.

Anyways, it's my duty to announce that I'm looking for a maintainer for love-sources since other things will take up my time in the near future, and personally I think I've taken love-sources as far as I personally am able to carry it.

So once 2.6.0-test7-mm1 drops (if at all - andrew seems silent on that issue) I'll put out a love kernel based on that and then I'll step down as maintainer, I can still act as co-maintainer but the support business and reading lkml, hanging on #offtopic and #kernelnewbies, and reading bitkeeper logs is simply to much right now.

Maintaining love-sources is a fairly simple job as such, you need to know a little C, the use of diff and patch and being nice to kernel developers also helps. As I stated before it's slightly skilled monkey work, all it requires is a tiny bit of coding skills and a lot of time.

If at all possible I would like bssteph to take over.

Oh my! I would be interested in this... real issue for me is also time, I think I have a bit of it, but not too much. ;)
I can do it, but the caveats are that there may be times where I'll get a bit behind on the kernel, and this would be my first go at something like this so it may be rocky at start.

I just read the new news, glad to see someone can continue your work! I have had a lot of success with love sources so far and my machine will always be avaliable to test Just hollar and I can test prereleases or what not on somewhat modern hardware (used to be). I have a AMD 2200+, 1gig ram (Corsair XMS), GeForce Ti4600, and an Asus board with a via chipset... all in all fairly happy linux hardware but you never know where problems can arise. I have yet to have a single lockup while using love-sources!

If you need someone to help develop the patch I'm willing to put in some time. I can make diffs, my C isn't great but I'm working on it( I can code functional programs in C and C++, but nothing too fancy), and I do read the LKML reasonably regularly.

Right now, I'm mainly preparing for the big patches that are already around, like Nick's stuff, because we want to keep those. And then some time soon I have to scour an LKML archive and see what catches my fancy. And of course if anyone else has suggestions I'm open to them.

Of course right now I'm a bit busy with school stuff, but that will come and go.

Hmm. I just noticed that Lovechild's location is SCO HQ... and he says he'll be busy with "work"... Is he our double agent on the inside!? I smell conspiracy!

Anyway, any words/thoughts about test7-love1, or should I get going on stuff for that?

I'm planting bombs - but don't tell anyone, I'm trying to get all the CEOs and lawyers at once.

I'm still waiting for Andrew to release -mm1 as -love is normally based on his work so all the nice little patches like CFQ doesn't need to be applied seperately anymore, I would also like the IDE write barrier patch wrote Jens Axboe in this kernel aswell as the regular Nick patches. Reiser4 would be nice but is definately still unstable. But I'll stop pretending I still do this job now and get n with my task at hand... reading UML.

Last edited by Lovechild on Wed Oct 15, 2003 9:09 am; edited 1 time in total

here's the working reiser4 patch, i applied the patch 2 posts up and i had to fix it because it had problems patching arch/i386/kernel/entry.S
this works on out-of-the-box 2.6.0-test7 (no bk what-so-ever).
i'm messing with reiser4 right but for some reason it seems so much slower than reiserfs3.6 in all my tests
please someone mirror it fast, i can't keep it for long.
http://oneofone.limitlessfx.com/misc/reiser4.diff.bz2
Lovechild : good job man and hope you will get free time again soon!
<off_topic>
anyone got exec-shield to work?
i had to edit the patch and default it to off ( =0 ) or it'd sig11 the kernel after the "rootfs" line...
it sig11 most of my apps, including X/bash/most KDE apps, while kwrite/nano/mp for example works fine..
i'm not into C at all so i have no idea what's goin' on...
</off_topic>

exec-sheild clashes with nicks scheduler in various points, so you will get unresolved references at the end of the compile even though it applies cleanly. It's a cool patch but it requires us to default it to off since our binutils isn't as cool as Fedora Linux's yet (Hardened Gentoo team should be working on this I think) - and it needs some hacking to take care of some gid/pid changes should be fairly simple though.

exec-sheild clashes with nicks scheduler in various points, so you will get unresolved references at the end of the compile even though it applies cleanly. It's a cool patch but it requires us to default it to off since our binutils isn't as cool as Fedora Linux's yet (Hardened Gentoo team should be working on this I think) - and it needs some hacking to take care of some gid/pid changes should be fairly simple though.