Subject: Re: NetBSD 4.0
To: Klaus Heinz <k.heinz.jul.sieben@kh-22.de>
From: =?ISO-8859-2?Q?Przemys=B3aw_Pawe=B3czyk?= <pp@kv.net.pl>
List: netbsd-users
Date: 07/01/2007 03:35:36
--Signature=_Sun__1_Jul_2007_03_35_36_-0500_hpuwW2QWWIFZ4FXb
Content-Type: text/plain; charset=ISO-8859-2
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

On Sun, 1 Jul 2007 09:39:11 +0200
Klaus Heinz <k.heinz.jul.sieben@kh-22.de> wrote:

> I encountered such a problem two times so far. Both were real
> problems in the application where Linux did not care about it.
>
>   "It doesn't happen on Linux, so it must be NetBSD's bug"
> is not a valid statement, the same as
>    "NetBSD's threads are free of bugs, it must be the application's
> fault" is invalid. It is my impression that people have encountered
> more such situations where the application was at fault.

Hi,

Thanks, perhaps you are right. But I stumbled upon the bug using NetBSD
system and an application written to the system (compilation from
pkgsrc created the same bug). It is insignificant here whether it was
originated in Linux world. The stench comes from here - NetBSD, either
the system or the application. And that's why it should be addressed
more carefully or with more attention evinced by NetBSD developers. My
post "was marked" (in reply) as "it's an application bug", and went
into....oblivion.

When you said you had encountered similar problems, let's say it -
with system threads (?) - an alarm bell should be rung. And we should
be warned/cheered up - "there's a problem with it in NetBSD, but the
problem is well recognized and some works are going on to get rid of
it". Or I would be asked for more details. Or to be faced with more
interest from NetBSD side (contrary to my side - user's side). In such
circumstances like present I really don't know if I'm further interested
whether the 4.0 release will be free of the bug or will leave it behind
to be solved in a future. Or whether the NetBSD is worth investing my
time in it at all.

But let's assume the bug is hidden in the svn application. I badly need
svn client (no server) in NetBSD. What should I do then as the only
available client RapidSVN is buggy? There are two apps of the same sort
- cvs and svn. I'd expect both of them to run smoothly on NetBSD. Is
the svn a bit worse than the cvs only because the latter is being used
by NetBSD? If yes, RapidSVN *and* subversion (server) should be
withdrawn from repo, if not the additional svn clients available
from pkgsrc should be debugged.

Regards,
pp

--
Przemysław Pawełczyk (p2o2) - pp_o2@o2.pl
P2O2 - http://pp.kv.net.pl, P2O2 Forum - http://www.p2o2.fora.pl/

--Signature=_Sun__1_Jul_2007_03_35_36_-0500_hpuwW2QWWIFZ4FXb
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (NetBSD)

iD8DBQFGh2dYD9+eS/1tsfYRAq0VAJ9iOl1lWuLNPMN0W8ABGAO69S3RZQCfVgrD
vMHwJdTQ2NtfZKb2no9tzHM=
=ums5
-----END PGP SIGNATURE-----

--Signature=_Sun__1_Jul_2007_03_35_36_-0500_hpuwW2QWWIFZ4FXb--