Date: Fri, 04 Oct 2002 16:33:15 -0400 (EDT) From: John Baldwin <jhb@FreeBSD.org> To: Julian Elischer <julian@elischer.org> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, Lars Eggert <larse@ISI.EDU>, n0go013 <ttz@blahdeblah.demon.co.uk>, current <freebsd-current@freebsd.org>, not on list - please copy <hackers@freebsd.org> Subject: Re: [ GEOM tests ] vinum drives lost Message-ID: <XFMail.20021004163315.jhb@FreeBSD.org> In-Reply-To: <Pine.BSF.4.21.0210041309120.17529-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04-Oct-2002 Julian Elischer wrote: > > > On Fri, 4 Oct 2002, John Baldwin wrote: > >> >> On 04-Oct-2002 Julian Elischer wrote: >> > >> > >> > On Fri, 4 Oct 2002, Poul-Henning Kamp wrote: >> > >> >> In message <3D9DE0D0.4050204@isi.edu>, Lars Eggert writes: >> >> >This is a cryptographically signed message in MIME format. >> >> > >> >> >--------------ms040706010906030302070807 >> >> >Content-Type: text/plain; charset=us-ascii; format=flowed >> >> >Content-Transfer-Encoding: 7bit >> >> > >> >> >Poul-Henning Kamp wrote: >> >> >> >> >> >> I would need to look at the code to be able to tell, I don't have >> >> >> time for that. >> >> > >> >> >I'd consider not having vinum work under geom a show-stopper... at least >> >> >until geom can stripe. >> >> >> >> Well, the showstopper is in vinum. The fact that ccd(4) works >> >> seamlessly with GEOM is testament to this. >> >> >> >> There are numerous architectural issues which have never been >> >> fixed in vinum, and one or more of these bits now. >> >> >> >> Whoever loves vinum will have to chase it/them down and fix it. >> > >> > No, it is established principal tha the importer of new features has the >> > responsibility to make older subsystems work. >> >> Oh, you mean like KSE on Alpha? > > What existing functionality on the alpha does KSE stop? So you agree that requiring vinum users to turn off GEOM is ok? Part of adding a new feature is providing proof of concept that it works for more than just one tiny case. Also, if you actually have to make it work on multiple cases, then you have to learn enough about other cases to better enable you to make better-informed design decisions that take other cases into account. One KSE works on i386, what are multithreaded ports like, oh, X, supposed to do when compiling with -lpthread doesn't work? -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.20021004163315.jhb>