public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Jacob Schmude <jacobs@surferie.net>
To: speakup@braille.uwo.ca
Subject: Re: Slackware 8.0 partitioning tools.
Date: Sun, 16 Sep 2001 01:55:38 -0400	[thread overview]
Message-ID: <20010916015538.A339@jslt> (raw)
In-Reply-To: <5.1.0.14.2.20010915205534.020890a0@mail.tft-bbs.co.uk>; from gordon@tft-bbs.co.uk on Sat, Sep 15, 2001 at 09:01:13PM -0100

Hi
   The third drive? That isn't really how linux does things. Where is it connected to? Primary master/slave or secondary master/slave? This is important, as linux doesn't go in a drive1, drive2,and drive3 manner. INstead, it goes like this:
/dev/hda, /dev/hdb: primary master, primary slave
/dev/hdc, /dev/hdd: secondary master, secondary slave
etc. In fact, usually /dev/hdc is used by an IDE cdrom. Try this command on the boot disk to find out where the drive is:
dmesg | grep -i hd
   You'll see your first drive found as hda, the the second hard drive will be found somewhere. Note this will also tell you where your cdrom resides. Not having permission to write to a drive usually occurrs when trying to partition a read-only media drive, like a cdrom.

HTH


On Sat, Sep 15, 2001 at 09:01:13PM -0100, Gordon Smith wrote:
> Hi.  Problem when installing Slackware 8.0.  I have a completely 
> unpartitioned hard drive in my system, which would be /dev/hdc - meaning 
> that it is drive number 3.  CFDisk and Fdisk will not allow me to write to 
> this drive, to prepare a Linux partition.  Any ideas why this could 
> be?  CFDisk says I do not have permition to write to this drive, and FDisk 
> says there are no free sectors.  I have to say that the SuSE partitioning 
> tools seem much more intelligent, it handles it with no problem 
> whatsoever.  Assuming I cannot get this to work, is there a tool within 
> Slackware which would allow me to shrink a FAT32 Windows partition?  Better 
> still, does anybody else run SuSE with speech?  If so, could they create me 
> a boot disk image?


  parent reply	other threads:[~ UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Gordon Smith
 ` Gregory Nowak
   ` Gordon Smith
     ` Gregory Nowak
       ` Gordon Smith
         ` Kirk Wood
           ` Gordon Smith
             ` Saqib Shaikh
               ` Gordon Smith
 ` Gregory Nowak
   ` Frank Carmickle
   ` Gordon Smith
 ` Jacob Schmude [this message]
   ` Gordon Smith
     ` Frank Carmickle
     [not found]     ` <Pine.LNX.4.21.0109160640170.1418-100000@c1422183-a.ross1.p a.home.com>
       ` Gordon Smith
         ` Saqib Shaikh
           ` Gordon Smith
             ` Frank Carmickle
     [not found]             ` <Pine.LNX.4.21.0109160826040.1418-100000@c1422183-a.ross1.p a.home.com>
               ` Gordon Smith
                 ` Gregory Nowak
         ` Frank Carmickle
     [not found]         ` <Pine.LNX.4.21.0109160726140.1418-100000@c1422183-a.ross1.p a.home.com>
           ` Gordon Smith
             ` Raul A. Gallegos
         ` Gregory Nowak
           ` Gordon Smith
     ` Kirk Wood
       ` Gordon Smith
     ` Jacob Schmude
       ` Gordon Smith
         ` Kirk Wood
 ` Saqib Shaikh
   ` Gordon Smith
     ` Saqib Shaikh
       ` Gordon Smith
 Gregory Nowak

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=20010916015538.A339@jslt \
    --to=jacobs@surferie.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).