On Thu, May 05, 2011 at 08:09:16AM -0400, Kenneth R Westerback wrote:
> On Thu, May 05, 2011 at 11:51:22AM +0100, Owain Ainsworth wrote:
> > On Wed, May 04, 2011 at 11:59:52PM -0400, Kenneth R Westerback wrote:
> > > And by using opendev(3) tunefs can accept disk UID's.
> > >
> > > Any actual tune
On 2011/05/05 11:51, Owain Ainsworth wrote:
> I have no idea, but a porter should probably check the distfiles.
It's not used in ports at present. (symon has a SMART stats module
which uses it, but it's only used on NetBSD).
On Thu, May 05, 2011 at 11:51:22AM +0100, Owain Ainsworth wrote:
> On Wed, May 04, 2011 at 11:59:52PM -0400, Kenneth R Westerback wrote:
> > And by using opendev(3) tunefs can accept disk UID's.
> >
> > Any actual tunefs(8) guru's out there who can explain what this
> > might break?
> >
> > Inspi
On Wed, May 04, 2011 at 11:59:52PM -0400, Kenneth R Westerback wrote:
> And by using opendev(3) tunefs can accept disk UID's.
>
> Any actual tunefs(8) guru's out there who can explain what this
> might break?
>
> Inspired by oga@'s work on atactl.
millert already provided a diff for that, the th
And by using opendev(3) tunefs can accept disk UID's.
Any actual tunefs(8) guru's out there who can explain what this
might break?
Inspired by oga@'s work on atactl.
This is the last use of opendisk(3) in the tree. Any reason to
keep it if this goes in? ports?
Ken
Index: tunefs.c
