From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BfOn6-0002sA-1A for qemu-devel@nongnu.org; Tue, 29 Jun 2004 16:01:16 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BfOn2-0002n4-Dy for qemu-devel@nongnu.org; Tue, 29 Jun 2004 16:01:15 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BfOn1-0002mZ-GJ for qemu-devel@nongnu.org; Tue, 29 Jun 2004 16:01:11 -0400 Received: from [38.113.3.61] (helo=babyruth.hotpop.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BfOky-0005cx-G2 for qemu-devel@nongnu.org; Tue, 29 Jun 2004 15:59:04 -0400 Received: from phreaker.net (kubrick.hotpop.com [38.113.3.103]) by babyruth.hotpop.com (Postfix) with SMTP id 9CF2F635C6B for ; Tue, 29 Jun 2004 19:17:19 +0000 (UTC) Date: Tue, 29 Jun 2004 15:54:39 -0400 From: "Jim C. Brown" Message-ID: <20040629195439.GA16876@jbrown.mylinuxbox.org> References: <200406291803.46651.bobb@absamail.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200406291803.46651.bobb@absamail.co.za> Subject: [Qemu-devel] Re: coping with fdisk mutation (was Re: replies) Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Bob Barry Cc: qemu-devel@nongnu.org On Tue, Jun 29, 2004 at 07:51:52PM +0200, Bob Barry wrote: > Jim - > > On Sun, 27 Jun 2004 22:23, you wrote (to Damien Mascord): > > > 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. > > Consider sfdisk - it's intended for non-interactive (script) use. > It is in the util-linux package (though some high-handed > distributions omit it). See file "sfdisk.examples" in the tarball. > > Bob It would still have the same problem: the screen output of sfdisk -l could change and lomount would no longer work. Futhermore, there is the problem that fdisk/sfdisk will output junk like: start: (c,h,s) expected (0,1,1) found (0,0,3) end: (c,h,s) expected (53,9,2) found (1,26,2) which we otherwise don't care about, but which messes up the format of output. However someone else submitted to me a program which can read the necessary information from the disk image itself. I have merged this into lomount, so the latest bleeding-edge version of lomount (not yet released) will work w/o any dependences on the version of fdisk that you have. Obviously, lomount still requires a version of mount that supports using loop (as well as losetup) but just about everyone has that. -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.