From: "Jim C. Brown" <jbrown106@phreaker.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: replies
Date: Sun, 27 Jun 2004 22:23:20 -0400 [thread overview]
Message-ID: <20040628022320.GA3436@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <40DF7499.8070802@tusker.org>
On Mon, Jun 28, 2004 at 09:30:01AM +0800, Damien Mascord wrote:
> Hi guys,
>
> Because it is possible that
> a new version of fdisk will change it's screen output and "wreck"
> lomount...
That's the problem that we have here. Though it would be a trivial fix, it is
still rather inconvient to have to update lomount everytime a new vesrsion
comes out.
> Excuse my ignorance, but would there be an fdisk library that you could
> just call the functions, or even duplicate the functionality that you
> need from fdisk into a binary of your own ?
Right now, lomount is basicly a wrapper. (I originally meant to write it as a
shell script in fact, but I couldn't figure out how to parse fdisk's output.
Right now that is what I'm trying to do (using awk for the actual parsing).)
The Right Thing(tm) to do would be to replace the code that parses fdisk's
output with code ripped from fdisk, qemu, or even to use libparted.so, and
use that code to read the disk image and calculate the values that we need.
(We can go futher and have lomount make the mount(2) call by itself instead
of merely calling mount(8), if we wanted to.)
This is not a trivial change. But it would certainly be worthwhile.
>
> Damien
>
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
prev parent reply other threads:[~2004-06-28 2:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-26 18:45 [Qemu-devel] VDE HOWTO version 0.1 Jim C. Brown
[not found] ` <200406271007.11404.a_mulyadi@telkom.net>
2004-06-27 5:01 ` [Qemu-devel] replies Jim C. Brown
2004-06-27 5:21 ` Renzo Davoli
2004-06-27 7:04 ` Renzo Davoli
2004-06-27 17:33 ` Jim C. Brown
2004-06-27 7:12 ` [Qemu-devel] replies Mulyadi Santosa
2004-06-27 18:26 ` Jim C. Brown
2004-06-28 1:30 ` Damien Mascord
2004-06-28 2:23 ` Jim C. Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040628022320.GA3436@jbrown.mylinuxbox.org \
--to=jbrown106@phreaker.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).