public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
Cc: linux-kernel@vger.kernel.org, joeja@mindspring.com
Subject: Re: 2.4.9 to 2.4.14 bug & workaround
Date: Tue, 13 Nov 2001 13:11:01 +0100	[thread overview]
Message-ID: <3BF10DD5.9461C2F@loewe-komp.de> (raw)
In-Reply-To: <Springmail.105.1005600219.0.18983900@www.springmail.com> <20011113124519.G3949@emma1.emma.line.org>

Matthias Andree wrote:
> 
> On Mon, 12 Nov 2001, joeja@mindspring.com wrote:
> 
> (reformatted quote to heed line length provisions)
> > I have an internal iomega 'type' (not iomega) IDE zip drive.  It
> > mounts as /dev/hdd instead of /dev/hdd4.  Mounting as /dev/hdd seems
> > okay.
> >
> > Mounting as /dev/hdd4 will hang my kernel( 2.4.9-2.4.14).  I have read
> > that on some MB you can change the bios to none for the ide device and
> > this works on certain mb.  I tried this and it did not change
> > anything.
> 
> Well, all this depends on how the media has been formatted. From what I
> heard (I have no exchangable drives since I sold my SyQuest crap), some
> ZIP (presumably) media are partitioned and have their fourth partition
> formatted, giving your data as /dev/hdd4 or /dev/sdb4 or something other
> with 4 to the end. Then, the entire media might be formatted "raw" with
> Linux, so you'd have to mount /dev/hdd instead.
> 

Yes, in theory ;-)
I have an internal IDE 100MB Zip @home.
In the office I have a 250MB USB ZIP.

The media is partitioned, with the 4th primary partition formatted
as VFAT.

On the IDE I mount /dev/hdb, on the USB thing I mount sd[ab]4
depending if the flash reader is there or not.
Hmh?

# fdisk -l /dev/sdb
 
Disk /dev/sdb: 4 heads, 32 sectors, 1536 cylinders
Units = cylinders of 128 * 512 bytes
 
   Device Boot    Start       End    Blocks   Id  System
/dev/sdb4             1      1536     98288    6  FAT16



Of course I use different kernels, @home: 2.4.9ac18 and 2.4.1[34]-xfs;
@office for now 2.4.9ac3+bcl.

Until now I thought it had something to do with the different gendisk,
LDM or so.

  reply	other threads:[~2001-11-13 12:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-12 21:23 2.4.9 to 2.4.14 bug & workaround joeja
2001-11-13 11:45 ` Matthias Andree
2001-11-13 12:11   ` Peter Wächtler [this message]
2001-11-13 12:56     ` Matthias Andree
2001-11-13 21:54       ` Peter Wächtler

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=3BF10DD5.9461C2F@loewe-komp.de \
    --to=pwaechtler@loewe-komp.de \
    --cc=joeja@mindspring.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.andree@stud.uni-dortmund.de \
    /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