> If the way you do something take too long.
> Seems like that is a bug.
> Most likely in the way you are doing it.
> A lot of things, you can do them wrong and get away with it for a while.
> Getting away with doing something wrong is far from proof that you were
> doing it right.
That's for sure right but I somehow think I know how to use vnconfig.
And 'course the devs LOVE ME they'd flamed more then they did if would
have done something wrong.
vnconfig -cK 52527 -S saltfile /dev/sd0k /dev/svnd1c
Creates: a svnd, why svnd1 and not 0? 'course of make build and make
release.
disklabel -E svnd1
-> a a
-> r
-> w
-> q
You can use svnd1c direct but then be sure you get flamed by the
developers so I choosed to validate it even with a partition (which I
normaly never do use nor used in the past, it wont matter for the
result).
newfs /dev/rsvnd1a *wait some time.. for me it was a 220G partition*
mount -o noatime,softdep /dev/svnd1a /home
cd /home
Benchmark it like you want.. with whateve rmakes your horny.. dd,
bonniee++....
I get awefull slow results with:
i386, AMD64, different {CPUs,Motherboards,RAM,HDDs,NICs},
oBSD-stable/current
It's all the same: writing speed about 2-4MB/s
I was already asked by people how to encrypt a partition and all I can
tell them for now is: Sorry that wont make you happy with OpenBSD
because of a speed issue nobody admits (or you get a 2nd HDD because
softraid works perfectly).
So why do devs just listen if it wents security critical like the stuff
with PF..
> I reserve the right to be as annoying on this list as you are.
Good argument, and a valid one.
At least you're no retard who starts to talk in a way making you belief
you entered a digital gh3tt0 :-D
Sebastian
