linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Malinovich <demonbane@the-love-shack.net>
To: linux-hotplug@vger.kernel.org
Subject: udev and Iomega Zip drives
Date: Thu, 11 Mar 2004 10:42:33 +0000	[thread overview]
Message-ID: <1079001753.2109.6.camel@Thief> (raw)

[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]

I just started using udev and I'm really thrilled so far. Having 4 USB
drives always appearing on the correct /dev/ entry is REALLY nice. Well,
make that 3. The 4th one is my Iomega Zip drive. And while it appears at
the correct /dev/ entry, it doesn't create any partition entries unless
the drive was plugged in with a disk already inside.

If I add a disk later, I have to access the drive in order for the disk
to be detected (fdisk -l /dev/iomega-zip for example). The problem is
that Zip drives ONLY use partition 4. So in order to mount the disk, I
have to mount /dev/iomega-zip4. I want that entry to be created as soon
as /dev/iomega-zip is created, regardless of whether there is a disk or
not so that when there IS a disk inside, I won't have to run fdisk -l or
anything else first. Unfortunately, using NAME{all_partitions} doesn't
work because it creates 15 partitions. This causes the drive to get VERY
confused and to spew out all sorts of invalid partition errors.

So is there a way to create just the partition 4 device as soon as the
device entry is created? Thanks in advance for any help.
-- 
Alex Malinovich
Support Free Software, delete your Windows partition TODAY!
Encrypted mail preferred. You can get my public key from any of the
pgp.net keyservers. Key ID: A6D24837


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-03-11 10:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-11 10:42 Alex Malinovich [this message]
2004-03-11 10:55 ` udev and Iomega Zip drives Michal Čihař

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=1079001753.2109.6.camel@Thief \
    --to=demonbane@the-love-shack.net \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).