Date: Wed, 4 Aug 2004 07:43:50 -0700 From: John-Mark Gurney <gurney_j@resnet.uoregon.edu> To: Maxim Sobolev <sobomax@portaone.com> Cc: current@freebsd.org Subject: Re: GEOM is too verbose Message-ID: <20040804144350.GX991@funkthat.com> In-Reply-To: <20040804102742.GC55271@www.portaone.com> References: <62768.1091287144@critter.freebsd.dk> <410BBB74.9010804@portaone.com> <864qnoyv06.fsf@kamino.rfc1149.org> <410BD3BC.9090704@portaone.com> <20040803212227.GW991@funkthat.com> <20040804102742.GC55271@www.portaone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Maxim Sobolev wrote this message on Wed, Aug 04, 2004 at 12:27 +0200:
> On Tue, Aug 03, 2004 at 02:22:27PM -0700, John-Mark Gurney wrote:
> > Maxim Sobolev wrote this message on Sat, Jul 31, 2004 at 20:15 +0300:
> > > >>It is python program, so that ioctl() is out of question. Usage of
> > > >
> > > >
> > > >Hm python has ioctl support, where is the problem?
> > >
> > > Really? Anyway, I doubt that name of this ioctl is the same on the
> > > different unices, so that binary search is still the best from the
> > > portability POV.
> >
> > fcntl.ioctl... it might take some hand expansion of the ioctl macros
> > to get it though... the old pytoh that would generate these couldn't
> > handle FreeBSD's ioctl defines (but this was back in the early 4.x
> > days)... You could always write a simple C program to get the value
> > necessary..
>
> Heh, but I have other means to spend my spare time. Rewriting perfectly
> working code for perfection sake is not one of them.
I only suggested:
#include <sys/disk.h>
#include <stdio.h>
void
main()
{
printf("%ul\n", DIOCGMEDIASIZE);
}
and then use that value in python's fctl.ioctl.
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040804144350.GX991>