Date: Sat, 13 Apr 2013 04:10:08 -0400 From: Quartz <quartz@sneakertech.com> To: freebsd-fs@freebsd.org Subject: Re: A failed drive causes system to hang Message-ID: <516912E0.8080708@sneakertech.com> In-Reply-To: <20130412222005.GA82884@icarus.home.lan> 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> <20130412222005.GA82884@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. I was under the impression that pcbsd was entirely an "apps and UI" thing, and that low level stuff like cam or zfs wouldn't be their area of expertise, or even really their responsibility since they're not messing with any of that. I don't think your embedded linux analogy is necessarily relevant, since in those cases the vendor definitely WILL be making low level changes to the base system. Unless you're saying pcbsd does something besides just adding packages to a base install and changing a few config files. ______________________________________ it has a certain smooth-brained appeal
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?516912E0.8080708>