--8w3uRX/HFJGApMzv
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 2005.12.14 00:16:10 +0100, Lasse Kliemann wrote:
| * Jaromir Dolecek writes:
| > On Tue, Dec 13, 2005 at 11:36:46PM +0100, Lasse Kliemann wrote:
| > > As I have learned, RC6 has been tagged. In the list of changes,=20
| > > nothing about vinum was said. I therefor assume that this issue is=20
| > > unsolved also in RC6.  Shouldn't we then document vinum support as=20
| > > broken in the upcoming 3.0 release? Fact is that usage of vinum (at=
=20
| > > least over USB) leads to a _system_ _crash_ even in the most simple=
=20
| > > setup possible. I tested this on two different machines.
| >=20
| > vinum is known broken. Use RaidFrame, which works fine :)
|=20
| It was not known to me that vinum was known broken, nor, for that matter,=
 that=20
| it was broken :-). If this will be documented in the manual page and the =
kernel=20
| config, others will not fall into the same pit as I did.
|=20
| Actually, I currently do not need anything like vinum or RaidFrame. I cam=
e=20
| across this rather accidentally and was worried about the quality of the=
=20
| upcoming release.

I think we should remove the Vinum include in sys/conf/files for
netbsd-3 branch and mention something like "Vinum was disable in the
3.0 release because it's not yet ready" in the release notes. What do
you think ?

I wouldn't worry if this was an experimental feature that did not
crash the kernel..

		-- Rui Paulo

--8w3uRX/HFJGApMzv
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFDn1grZPqyxs9FH4QRAlV1AJ4qKweGm2Pxibm+8trusgh9CJfn0gCfd0kz
d5EFC5+FZo89mC+JvRTBXQQ=
=v7wf
-----END PGP SIGNATURE-----

--8w3uRX/HFJGApMzv--