Re: Hints on kernel config for a dula pII/450 system anyone?

[Gergo Szakal <bastyaelvtars@xxxxxxxxx>]

onflybsd.org> <450DE1EA.7090303@xxxxxxxxx> <450de68a$0$789$415eb37d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <450de82f$0$790$415eb37d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <450dedb2$0$787$415eb37d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <450e79fe$0$787$415eb37d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <450e8785$0$786$415eb37d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
In-Reply-To: <450e8785$0$786$415eb37d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 14
Message-ID: <450e8df6$0$786$415eb37d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
NNTP-Posting-Host: 160.114.118.67
X-Trace: 1158581751 crater_reader.dragonflybsd.org 786 160.114.118.67
Xref: crater_reader.dragonflybsd.org dragonfly.users:7257

Sorry, but I don't want to continue this type of discussion.
Of course I will test by putting the HDD into another computer and fire 
it up, and see if the problem occurs there as well (no time now, need to 
get a UP kernel, as the SMP one does not like UP machines :-P). Thought 
I could help in testing the stable branch by setting up a production MP 
machine, since this is the only way I can contribute right now.
As previously stated, I'd be the happiest to throw this piece of hw out 
(or create a linux desktop from it, muhaha) and get a brand new machine 
to run the firewall on.
If you can prove that the problem is caused by the machine itself, 
please do it (I don't consider statements like 'It's old cr*p' as 
proof), else let's wait for someone else who dug into the problematic 
code. Sorry for being a bit harsh, no offense meant, but somehow the 
countless appearance of sentences like 'get a new box' frustrates me. :-(