Date: Mon, 6 Jun 2005 22:48:36 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk> To: "Daniel Eriksson" <daniel_k_eriksson@telia.com> Cc: freebsd-current@FreeBSD.org Subject: Re: 'atacontrol cap' not working under recent CURRENT? Message-ID: <E75725A6-356C-46E0-85B3-592F3E326A29@DeepCore.dk> In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0VcX9IoJqUaXPS8MjT1PdsKAAAAQAAAA9Yz0mlJr6kWGRMAUYqVRSgEAAAAA@telia.com> References: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0VcX9IoJqUaXPS8MjT1PdsKAAAAQAAAA9Yz0mlJr6kWGRMAUYqVRSgEAAAAA@telia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/06/2005, at 22:29, Daniel Eriksson wrote:
>
> I cannot seem to get 'atacontrol cap' to work on an up-to-date 6-
> CURRENT
> system.
>
> The manpage says it only takes one parameter ("device"), but no
> matter what
> I pass it fails. This used to work many moons ago, but I haven't
> tested it
> in the last 6 months or so.
It still does, however due to GEOM's intervention it wont work on a
device thats already open as RW. I just committed a workaround for
that. With the workaround "atacontrol cap ad0" works again even if
ad0 is in use.
- Søren
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E75725A6-356C-46E0-85B3-592F3E326A29>