Date: Wed, 04 Aug 2004 17:48:04 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: John-Mark Gurney <gurney_j@resnet.uoregon.edu> Cc: current@freebsd.org Subject: Re: GEOM is too verbose Message-ID: <2890.1091634484@critter.freebsd.dk> In-Reply-To: Your message of "Wed, 04 Aug 2004 07:43:50 PDT." <20040804144350.GX991@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20040804144350.GX991@funkthat.com>, John-Mark Gurney writes:
>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.
see diskinfo(8)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2890.1091634484>