bug-parted
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: amiga partitioning support for parted


From: Andrew Clausen
Subject: Re: amiga partitioning support for parted
Date: Tue, 22 Jul 2003 08:26:32 +1000
User-agent: Mutt/1.5.4i

On Mon, Jul 21, 2003 at 09:04:23PM +0200, Sven Luther wrote:
> BTW, as i understand it, parted is mostly 512 bytes only, while it is
> possible to use blocks of any size on amiga partitions. Possibly there
> are some people around using 1024 sized blocks.

In this case, you'll have to do some maths to support them.
(i.e. use appropriate PedConstraint's, and multiply/divide everything
by 2)

> > > Also, is there a way to telling the higher levels
> > > that we are looking at a partition on block n, and not have to search
> > > for it each time ?
> > 
> > Do you mean ped_disk_get_partition_by_sector() ?
> > I don't really understand your question.
> 
> The amiga partition table can be found on any of the 16 first sectors of
> the disk. So, when doing a probe, i have to look at all the 16 first
> blocks, and search for an amiga partition table. The ped_probe function
> returns the partition type, but could also return the blcok number where
> the partition was found, so i have not to search it again when doing a
> read. But then, maybe it is cheap partition access, and not really all
> that important to worry about.

It's *really* cheap.  If I were you, I'd allocate a 16 sector buffer,
and slurp it all up.  Besides, it'll all be cached.

> Maybe if i will have time i will try to write all such stuff i
> discovered in a nice howto or something.

That would be nice :)

> BTW, parted is a GNU project, right, so i do have to assign the
> copyright of my fixes to the FSF or something such ? And also do some
> paper work with my employer (on whose time i write the stuff) ?

That is desirable, yes :)  I attached the form that starts the process.
(There are other options... ask me if you're interested)

Cheers,
Andrew

Attachment: assign.future
Description: Text document


reply via email to

[Prev in Thread] Current Thread [Next in Thread]