From: Daniel Jacobowitz <drow@false.org>
To: Andrew Clausen <clausen@gnu.org>
Cc: Hollis Blanchard <hollis@amulet.co.jp>,
linuxppc-dev@lists.linuxppc.org, GNU Parted list <parted@gnu.org>
Subject: Re: GNU Parted, linuxppc support coming :-)
Date: Wed, 5 Jul 2000 13:01:58 -0700 [thread overview]
Message-ID: <20000705130158.A18557@drow.them.org> (raw)
In-Reply-To: <39626E45.E0496869@gnu.org>; from clausen@gnu.org on Wed, Jul 05, 2000 at 09:07:49AM +1000
On Wed, Jul 05, 2000 at 09:07:49AM +1000, Andrew Clausen wrote:
> Each partition gets one block (yes?). So thats 20 * 512?
> (From comments in various programs, most disks have 512 byte blocks...)
CDROMs, for example, often have 2048-byte blocks. You can get the
block size out of the disk header somewhere, IIRC.
> > There seems to be a shortage of HFS folks these days. :) But ext2
> > resizing sounds very cool.
>
> Excuse my ignorance... what FS's do people usually use with MacOS?
> HFS/HFS+?
Yes, that's right.
> (Is the point "no-one uses MacOS", or "no-one's hacking on HFS
> in Linux"?)
The latter.
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| dan@debian.org | | dmj+@andrew.cmu.edu |
\--------------------------------/ \--------------------------------/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-05 20:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-04 21:44 GNU Parted, linuxppc support coming :-) Andrew Clausen
2000-07-05 12:07 ` Hollis Blanchard
2000-07-04 23:07 ` Andrew Clausen
2000-07-05 20:01 ` Daniel Jacobowitz [this message]
2000-07-06 5:37 ` Michel Lanners
2000-07-08 5:07 ` Ethan Benson
2000-07-08 8:58 ` Timothy A. Seufert
2000-07-10 22:19 ` Michel Lanners
2000-07-05 12:26 ` Michel Dänzer
2000-07-04 23:06 ` Andrew Clausen
-- strict thread matches above, loose matches on Subject: below --
2000-07-05 14:49 Iain Sandoe
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=20000705130158.A18557@drow.them.org \
--to=drow@false.org \
--cc=clausen@gnu.org \
--cc=hollis@amulet.co.jp \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=parted@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.