The patch appears to be a bz2 and if you have it in /usr/src, that's the parent of the Love directory. I'd also point the /usr/src/linux link to the Love folder before starting, so try these commands to patch:

The patch appears to be a bz2 and if you have it in /usr/src, that's the parent of the Love directory. I'd also point the /usr/src/linux link to the Love folder before starting, so try these commands to patch:

What is your opinion of the current state of reiser4 on this kernel? Did it work better with 2.6.6-love4?

I am still using it on 2.6.6-love4 without pbs but I have not pushed it too hard: I only have /protage as r4 so far.

Any chance of putting 2.6.6-love4 up on your site since Steel seems to have pulled everything off his space. I still have a copy but I think it would be a useful asset for some.

I am still running this kernel because it seems very good and poss a bit more stable than the current offering. But I'm keen to move to 2.6.7 once the dust has cleared.

Thanks for the taking over the helm from Steel, keep it coming.

Make love not war

well, i've never used love4 to be honest so i can't judge, but this works better than speedy except for the locks up after heavy load (not during heavy load).
so if you can live without ut2004/emerging big stuff for a while, use this love.
enemy-territory seems to work fine here.
peace

Duh , sorry for being such a moron, but can someone guiode me as of how do i patch the love patch ?

some step's would be very useful, actually i'm returning to linux after 5 months and i've forgotten everything..

Bye,
jazz_________________In 2010, M$ Windows will be a quantum processing emulation layer for a 128-bit mod of a 64-bit hack of a 32-bit patch to a 16-bit GUI for an 8-bit operating system written for a 4-bit processor from a 2-bit company that can't stand 1 bit of competition.

Duh , sorry for being such a moron, but can someone guiode me as of how do i patch the love patch ?

some step's would be very useful, actually i'm returning to linux after 5 months and i've forgotten everything..

Bye,
jazz

get the ebuild, put it in /usr/local/portage/sys-kernel/love-sources/ (make it if it doesnt exist), ebuild blah.ebuild digest then emerge love-sources.
@alari it might lock under heavy load, please come on irc sometime.
@VolcomPimp bootsplash works fine here

i'm testing the new reiser4 snapshot, for some reason my snd-emu10k1 oops and doesnt work with it, i'm trying to find out why...

Basically, the c1 patch is not general enough. I think that C1 was meant to refer to the chipset revision model. I have an early nforce2 with chipset revision A, and I'm still getting random hangups with this kernel. (Hopefully, I'm not the only one.)

The bugzilla page seems to be down ATM, but I'm sure it will come back.

Ok, i was looking for something kinda similar, the situation is that say i plugin my usb-stick, then the power is turned on and i get the /dev/sdaX, but even if i unmount it the power dosent go off.. in winxp when u remove the hardware, the power turns off too..

How do u do that in linux ? any ideas

Bye,
Jazz_________________In 2010, M$ Windows will be a quantum processing emulation layer for a 128-bit mod of a 64-bit hack of a 32-bit patch to a 16-bit GUI for an 8-bit operating system written for a 4-bit processor from a 2-bit company that can't stand 1 bit of competition.

I get the following error when I try to compile with acx100 support...weird....

Yes, ACX100 is broken. You have two options:
(1) rename drivers/net/wireless/acx100 to drivers/net/wireless/acx, the edit drivers/net/wireless/Makefile, replacing 'acx100/' with 'acx/'. Then recompile. Note that this will produce a driver module named 'acx_pci' instead of 'acx100_pci'.
(2) Copy the drivers/net/wireless/acx100 directory from a previous love release. I did this since I found that the version in this love wouldn't associate with the rest of my network.

This kernel works great for me (its snappy and submount is great), but I noticed a big difference between this one and ck-sources (2.6.3, which I used before) and that is that my load goes way up and the system goes very unresponsive when copying stuff to my hd (either from an other physical disc or cdrom) and when I burn cds/dvds, in the latter case it became almost unuseable

chipset nforce2/ultra400 with the nforce/amd ide driver and dma on for disks (hdparm gives that same scores as with ck-sources)

Anyone else experiencing this?_________________In "old" Europe we already have a word for "pre-emptive strikes" mr Bush: its called "war"

I get the following error when I try to compile with acx100 support...weird....

Yes, ACX100 is broken. You have two options:
(1) rename drivers/net/wireless/acx100 to drivers/net/wireless/acx, the edit drivers/net/wireless/Makefile, replacing 'acx100/' with 'acx/'. Then recompile. Note that this will produce a driver module named 'acx_pci' instead of 'acx100_pci'.
(2) Copy the drivers/net/wireless/acx100 directory from a previous love release. I did this since I found that the version in this love wouldn't associate with the rest of my network.

umm how do i go about getting my partions to reiser4 ? do i need to patch something or the love does it for me ?

also, what r the steps next ?

BYe,
jazz_________________In 2010, M$ Windows will be a quantum processing emulation layer for a 128-bit mod of a 64-bit hack of a 32-bit patch to a 16-bit GUI for an 8-bit operating system written for a 4-bit processor from a 2-bit company that can't stand 1 bit of competition.