From: chuck gelm <chuck@gelm.net>
To: Hal MacArgle <haltec@kvinet.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Cfdisk VS Fdisk??
Date: Sun, 13 Mar 2005 17:05:09 -0500 [thread overview]
Message-ID: <4234B915.4080503@gelm.net> (raw)
In-Reply-To: <5.1.0.14.1.20050313094742.01fe9ba0@celine>
Ray Olszewski wrote:
<snip>
> I don't know what version of fdisk Slackware is shipping. MY Debian-Sid
> system
> is perhaps six months out of date, and it has fdisk version 2.12 ("fdisk
> -v") and cfdisk and cfdisk 2.12 (cfdisk -v"). With these versions, I've
> seen no problems with drives up to 250 GB or so.
My Slackware v9.1, kernel 2.4.22, has
fdisk v2.12 &
cfdisk v 2.12
;-)
HTH, Chuck
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2005-03-13 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 13:15 Cfdisk VS Fdisk?? Hal MacArgle
2005-03-13 17:54 ` Ray Olszewski
2005-03-13 22:05 ` chuck gelm [this message]
2005-03-15 15:21 ` Hal MacArgle
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=4234B915.4080503@gelm.net \
--to=chuck@gelm.net \
--cc=haltec@kvinet.com \
--cc=linux-newbie@vger.kernel.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