thanks, i will do that. i also remember that there was some mirror which already had nitro-sources. so i only had to add that to make.conf and then do emerge sync. this way i dont have to digest any ebuilds. so i was wondering if anyone knows of any of those mirrors. if not, then i would just follow the normal procedure. by the way, i am running amd64, any thing special for that?

thanks, i will do that. i also remember that there was some mirror which already had nitro-sources. so i only had to add that to make.conf and then do emerge sync. this way i dont have to digest any ebuilds. so i was wondering if anyone knows of any of those mirrors. if not, then i would just follow the normal procedure. by the way, i am running amd64, any thing special for that?

As far as I know all the mirrors either have files or not - that being the point of them being "mirrors"?

Emerge has just finished successfully - hopefully I'll be posting from the new kernel in a few minutes _________________What are you, stupid?

/root is reiser4. Obviously I've compiled support in, and stacks are on 8k.
I suppose it could be unable to find the hdd itself, but I can't see any reason why not - it's just a secondary IDE HDD, nothing too complex....
Any ideas?_________________What are you, stupid?

what does it mean to disable 4K stacks? how do i do that and enable 4K stacks? can i run reiser and reiser4 on two differnt partitions? how do i creat reiser4 partition, what would be my fstab entry?

Ooookay.... The size of stacks is configurable in this kernel. Typical choices are 4 and 8 - 4 minimises memory usage. Reiser4 is 8k-only so if you want to play with that I'd stick with 8k.
Yes, you can run reiser and reiser4 on different partitions.
fstab entry is pretty much normal - just use "reiser4" for the fs type.
You create a partition using fdisk as normal, then use mkfs.reiser4 on it (again, basically the same as any other filesystem)._________________What are you, stupid?

Hey Archangel,
I get these errors when i play around with my .config and choose too much stuff as modules in the block device and/or
IDE section of Kconfig, hmm , what was this again...... well, try compiling the stuff like chipset and ide that you know u have and
you know it will not change into your kernel....

cheers,

T

EDIT: I saw the patch for bogus ide numbers after the release and then, somehow, i forgot to apply it.
Will update, i hope darckness will also update the version that currently is online...._________________Retired gentoo user

I just wanted to record this so I don't forget. I'm not that much of a kernel hacker, but I've found out that my force feedback patch doesn't need to be applied - the root of my force feedback problems is in drivers/usb/input/hid-ff.c :

ANNOUNCEMENT
Because of many problems, which aparently affected EVERYONE trying rt version except the nitro devs,
the rt branch is officially DISCONTINUED

Awwwww.... I hadn't even got it working yet

Thanks for your earlier suggestion; I spotted a couple of options left unselected that look frankly pretty silly (don't know what I was thinking...), so hopefully I can make a bit more progress _________________What are you, stupid?

How much of an improvement does this offer over the 2.6.11-rc4-nitro sources? Worth the upgrade from a stable system?

My current system has been stable and happy on that since they came out almost without glitch. I was rather pleasantly suprised how painless using them with all reiser4 partitions, and pure udev. For being fairly new to gentoo I knew I was stepping into deep water but nitro seems to have done to trick!