public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Joseph C. Lininger" <jbahm@pcdesk.net>
To: speakup@braille.uwo.ca
Subject: Re: Recognizing a hard drive
Date: Tue, 15 Jul 2003 09:25:33 -0600 (Mountain Daylight Time)	[thread overview]
Message-ID: <Pine.WNT.4.56.0307150923110.1332@merlin> (raw)
In-Reply-To: <20030715093900.GB635@optusnet.com.au>

You have it mostly right. The only correction I'd make is that the extended partition is not listed as a /dev/hda<x>. Rather, /dev/hda5 is just your first logical drive. There wouldn't really be any reason to list the extended partition as a number anyway since you can't do anything with it except use it to get around the 4 partition limit.

-- 
Joseph C. Lininger
jbahm@pcdesk.net

On Tue, 15 Jul 2003, Shaun Oliver wrote:

> *SNIP*
> Use mkfs2ext, I think it is, again as root, to build the
> file systems.  I may have that second command wrong.
>
> you're right about it being wrong,
> the command is mke2fs /dev/xxx where xxx is the partition number you
> want to format.
> if I remember some of my basics correctly, and anyone feel free to jump
> down my throat and tell me to go learn it again if I have it wrong,
> your ide devices are listed as follows.
> /dev/hda the primary master,
> /dev/hda1 through 4 are the first 4 primary partitions on the disk
> /dev/hda5 is an extended partition and anything above that is a logical
> partition.
> /dev/hdb if memory serves is the second ide device on the first ide
> channel.
> and /dev/hdc is the secondary master on the second ide channel and
> /dev/hdd is the secondary slave on that second ide channel.
> I hope I got it right please god let it be so.
>
>


  reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 erik burggraaf
 ` Hugh Esco
   ` Doug
   ` Shaun Oliver
     ` Joseph C. Lininger [this message]
 ` Joseph C. Lininger
 ` Shaun Oliver

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=Pine.WNT.4.56.0307150923110.1332@merlin \
    --to=jbahm@pcdesk.net \
    --cc=speakup@braille.uwo.ca \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).