Edit: PARTY TIME!!!!!!!
Edit: Uploaded the REAL dark1
Edit: Fixed even more mistakes....... next time I won't rush stuff
Edit: I had some compliants about openbsd-netrand.diff from a fellow kernel hacker on IRC, the complaints were that the kernel already has good enough randomization, I'd like to say that although the kernel default ISN randomization is quite good, this patch adds an extra level of security. It prevents TCP/IP OS fingerprinting, which renders nmap's -O option useless when scanning a host with the patch applied.
Edit: Hah, I just learned I didn't have the first dark-sources patchset _________________System: predatorbox
Distro: Arch Linux x86_64
Current projects: blackhole, convmedia and anything else I cook up.

Last edited by predatorfreak on Wed Mar 02, 2005 4:49 pm; edited 6 times in total

cheers_________________ "Time is a companion that goes with us on a journey. It reminds us to cherish each moment, because it will never come again. What we leave behind is not as important as how we have lived" J-L. Picard

Dang, I made too many mistakes in the info I put on the net with rushing this release, fixed all the mistakes I've found so far._________________System: predatorbox
Distro: Arch Linux x86_64
Current projects: blackhole, convmedia and anything else I cook up.

Because I rushed dark1 out I didn't get to put in mapped watermark 3 (which is a great step forward) or the semi-new schediso (con went back to schediso2, which means i'm moving back). Expect dark2 is the normal 2-day time frame, so that I can stress test and such (unixbenching it right now)._________________System: predatorbox
Distro: Arch Linux x86_64
Current projects: blackhole, convmedia and anything else I cook up.

The patch looks full of goodies and I would use it if it worked on Reiser4.

Note that i DIDN'T include Reiser4 and i have no plans too, this is due to my policy of maintaining stablity and reiser4 isn't what I'd consider stable yet. I may create a branch off called darkrr with reiser4 for reiser4 people, but as of now I do not have any reiser4 patches or branches._________________System: predatorbox
Distro: Arch Linux x86_64
Current projects: blackhole, convmedia and anything else I cook up.

Sure thing, dark-sources is targetted towards being stable, secure and scalable without introducing "fluff" into the kernel. It adds patches I find practical use in vs stuff like vesa-tng which adds fluff to the kernel. I run and test every release to its fullest, trying to ensure as much things work as possible._________________System: predatorbox
Distro: Arch Linux x86_64
Current projects: blackhole, convmedia and anything else I cook up.

Sorry, my mistake. I dunno why I had the impression that dark contains reiser4 drivers .....

Its np, your welcome to patch in reiser4 of your own free will if you please._________________System: predatorbox
Distro: Arch Linux x86_64
Current projects: blackhole, convmedia and anything else I cook up.

I'd like to make an announcement to all the reiser4 people hoping to use dark-sources, I have decided to create a darkfs branch, which will include the normal dark-sources stuff aswell as extra file-systems (from this point on SquashFS will be in the darkfs branch). I realise that I am taking a user hit by not having reiser4 support, but my preference is reiser3.6/ext3, so keep in mind, the darkfs branch will only be compile tested (I will not give the normal insurance that comes with dark-sources).

hey predatorfreak, I'm playing with your patchest with SMP.
How do you feel about the latest libata-dev bk patch in your patchset? I'm one of the unfortunate people who have a promise tx2/tx4 SATA/PATA controller but using a PATA interface hard drive. I was hoping (after reading the changelog) for 2.6.11 that I wouldn't have to patch the kernel to get my hard drive to show up, but I still do.

Guys with my setup can't even boot without it. In case you are wondering this is an issue with brand new hardware; it's not legacy or anything _________________Thie is my sig. The post is over. Now gtfo.

hey predatorfreak, I'm playing with your patchest with SMP.
How do you feel about the latest libata-dev bk patch in your patchset? I'm one of the unfortunate people who have a promise tx2/tx4 SATA/PATA controller but using a PATA interface hard drive. I was hoping (after reading the changelog) for 2.6.11 that I wouldn't have to patch the kernel to get my hard drive to show up, but I still do.

Guys with my setup can't even boot without it. In case you are wondering this is an issue with brand new hardware; it's not legacy or anything

Np, I'll add it in 2.6.11-dark2 and get that released in a few hours.

Edit: also, thanks for the link, that should save me alot of time.
Edit: Fixed stupid typo's :\
Edit: ledskof, THANK YOU FOR PROVIDING THAT PATCH. It finally solved the "hdparm hates SATA" problem's I've been having ever since my move to 2.6. I can actually use hdparm on my SATA disk now without it spitting errors!!_________________System: predatorbox
Distro: Arch Linux x86_64
Current projects: blackhole, convmedia and anything else I cook up.

Are you having any ata related problems? I'm trying to figure out why operations on my DVD drive are failing now.
unpatching libata-dev isn't really an option for me since I can't boot without it... So I'm going to try dropping smp first.

just doing a

Code:

dd if=/dev/hda of=/tmp/whatever

fails at erratic spots and I can't kill the process.

/dev/hda is my DVDRW-CDRW

EDIT:
Everything is cool when I turned off SMP.

EDIT:
Problem gone in 2.6.11-dark2_________________Thie is my sig. The post is over. Now gtfo.

Last edited by ledskof on Thu Mar 03, 2005 7:52 pm; edited 1 time in total

Are you having any ata related problems? I'm trying to figure out why operations on my DVD drive are failing now.
unpatching libata-dev isn't really an option for me since I can't boot without it... So I'm going to try dropping smp first.

just doing a

Code:

dd if=/dev/hda of=/tmp/whatever

fails at erratic spots and I can't kill the process.

/dev/hda is my DVDRW-CDRW

EDIT:
Everything is cool when I turned off SMP.

Hmm, I'll look into this and see if I can hunt this down, please give dark2 a try and see if it still happens :\. Also, whats are/is processor(s)

I'd like to know, as I follow -ck mailinglist and like to be able to test the latest with this patch - eg I patch -R your version and just add con's or jens' latest (fixes). So I don't have to add all these other minor things myself

it also makes it easier to compare to other patchsets (as I'm always looking for a nice one - maybe until I stumbled acros your's )