linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Hamilton <michael@actrix.gen.nz>
To: linux-hotplug@vger.kernel.org
Subject: Re: Re linux-hotplug-devel  Re USBdesktop integration - how to guess /dev/sd* when
Date: Fri, 13 Feb 2004 12:39:00 +0000	[thread overview]
Message-ID: <200402140139.00352.michael@actrix.gen.nz> (raw)

On Sat, 14 Feb 2004 00:11, Wout Mertens wrote:
> Interesting... Where do I assume 1 partition and fat? I just let mount
> figure it out. With Linux 2.4 I iterate through all partitions, and
> with 2.6, the block event takes care of that.
>
> Apart from that, any devfs-isms that might be there should be easily
> fixable. Why don't you just give it a shot? :)
>
> Wout.
>
> Tomorrow at 00:01, Michael Hamilton wrote:
>>...

I just lept to that assumption from the comments in the 2.4 
version

  # TODO use fdisk to figure out partitions and types

and also from the loading and unloading of the vfat module.
I should have read the script though more thouroughly.
Sorry about that.  

But, I also can't see how 
 
  ls /dev/scsi/host$SCSI/

in the 2.4 version can be made to work on Redhat 9.   But I guess 
I could merge some code from my stuff to get the same effect.

Also under 2.6 my $DEVPATH contains more than the three parts
your scripts are looking for, eg /devices/pci0000:00/0000:00:11.2/usb3/3-2/3-2:1.0
So I was a bit mystified.  Getting from the above to 
/dev/sda /dev/sdb seems to be very difficult without using
something like sg_map.  Perhaps I'm wrong to be sticking with
the old /dev/sd[abc...] stuff, and for sticking with Redhat
and its hotplug - but I was hoping that I could use 2.6 without
any major changes.  I have pretty much achieved this goal - 
except that I have to install another utility, sg_map.

The reason that my script doesn't leave mount to figure
out the file system type is because of the desire to adjust
mount options depending on the file system type. Alessandro 
Fiorino's modifications to my script uses disktype to 
retrieve the fs type and set appropriate mount options.
For example: don't bother setting uid and gid options for 
ext2/ext3 - only do this for non Linux file systems.

Cheers,
Michael



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2004-02-13 12:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13 12:39 Michael Hamilton [this message]
2004-02-13 12:54 ` Re linux-hotplug-devel Re USBdesktop integration - how to guess Wout Mertens
2004-02-13 22:08 ` linux-hotplug-devel Re USBdesktop integration - how to guess /dev/sd* when Michael Hamilton

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=200402140139.00352.michael@actrix.gen.nz \
    --to=michael@actrix.gen.nz \
    --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).