Date: Fri, 12 Apr 2013 15:20:05 -0700 From: Jeremy Chadwick <jdc@koitsu.org> To: freebsd-fs@freebsd.org Subject: Re: A failed drive causes system to hang Message-ID: <20130412222005.GA82884@icarus.home.lan> In-Reply-To: <5168864A.2090602@sneakertech.com> References: <mailman.11.1365681601.78138.freebsd-fs@freebsd.org> <51672164.1090908@o2.pl> <41A207817BC94167B0C94133EC0DFD68@multiplay.co.uk> <51687881.4080005@o2.pl> <20130412212207.GA81897@icarus.home.lan> <5168864A.2090602@sneakertech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 12, 2013 at 06:10:18PM -0400, Quartz wrote: > > >While PC-BSD is based on FreeBSD, > > Wait, isn't pcbsd exactly the same as vanilla freebsd except that > kde/bash/trueos/etc are pre-installed? Do they have their own > version of zfs or low level library differences or something? Off-topic, so I will not be responding past this point: Let's say I have a router maintained/made by XYZ company that runs Linux. I have problems with this device, but am unsure what the reason is or what the cause is. Do I mail the LKML about the issue or do I go to the vendor? The correct answer is: you start by going to the vendor. Alternately one can involve both (ex. vendor and CC the LKML). The fact that it's a "purchased piece of hardware" has no bearing -- the methodology of support inquiries is the same. My point is that the PC-BSD folks need to be made aware of this issue, so their iXSystems folks can help out if necessary and so on. If they're left out of the loop, then that's bad for everyone. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130412222005.GA82884>