Re: **Caution-External**: Re: USB hotplug woes
I'm a retard... Changed it to sdb1 and whabam... It works as expected. Only
problem now is that the last part of the script that tells it to unmount
isn't working but that is fixable. So it seems 2.6 kernel with udev is the
solution.
On 7/21/06 11:54 AM, "Vandoorn, Yvo" <yvo_vandoorn@mcgraw-hill.com> wrote:
> Well I have since taken the complete plunge to 2.6. I was able to boot
> debian by changing the fstab & grub configuration.
>
> Ok so now I have researched on how to write udev.rules (using
> http://www.reactivated.net/writing_udev_rules.html as reference).
>
> In the guide at the bottom it recommends doing:
>
> KERNEL=="sdb", RUN+="/usr/bin/my_program"
>
> However what I am seeing in my /var/log/syslog (I modified
> /etc/udev/udev.conf to output debug logging) is that it attempts to run the
> script before it has actually done any of the volume discovery. My scripts
> first command is to mount /dev/sdb1 to /mnt/usbkey. This doesn't work of
> course since /dev/sdb1 wont be declared after the script is done.
>
> Any ideas on what I can do from here?
>
>
> On 7/21/06 10:37 AM, "Craig M. Houck" <chouck@binghamton.edu> wrote:
>
>> That is beyond me I'm afraid. Hotplug usb devices are tricky somewhat even
>> with 2.6 if you are trying to auto run scripts associated with a hot plug
>>
>> OH, yea. Sata drives and Sarge 2.6 don't mix well. I've never tried Etch on
>> a Sata machine.
>> I know that some this do work with one and not the other.
>> Sarge 2.6 does not have MegaRaid drivers
>> Etch 2.6 has MegaRaid drivers!!
>>
>> At 01:41 PM 7/20/2006 -0700, Vandoorn, Yvo wrote:
>>> I should've mentioned that there is no gui. Actually these are headless
>>> servers, which is the need for scripts.
>>>
>>> The goal is that if someone where to stick in an USB flash drive, the OS
>>> would launch the necessary script do its thing and then take out the USB key
>>> 5 minutes later. The script basically initializes the network, runs apt-get
>>> and programs the cron. It works great in the lab, however the flash drive we
>>> used is no longer produced making it a pain for wide spread production.
>>> Further more I tried the 2.6 kernel and the machine just went nuts only
>>> because the SATA drives are suddenly seen as SCSI. Yes it is fixable but I'd
>>> rather not customize it too far off the beaten path.
>>>
>>>
>>>
>>> On 7/20/06 12:53 PM, "Craig M. Houck" <chouck@binghamton.edu> wrote:
>>>
>>>> Vandoorn, Yvo;
>>>>
>>>> I have never done that. I know that with the 2.6 kernel (that I have on
>>>> many laptops) plug a usb device in and an icon appears on the desktop
>> for it.
>>>>
>>>> Do you want the script to autorun whe the usb device is pluged in? If so
>>>> do some googles on "auto run", there are some programs you can find to do
>>>> that for you.
>>>>
>>>> I have done it on windows cds that I want to start up a webpage for example
>>>>
>>>>> What will it take to have a script run once the 2.6 kernel is loaded and a
>>>>> flash drive is inserted.
>>>>>
>>>>>
>>>>> On 7/20/06 11:49 AM, "chouck@binghamton.edu" <chouck@binghamton.edu>
>> wrote:
>>>>>
>>>>>> For what it's worth...
>>>>>> I find usb hotplug impossible to do wiht the 2.4.x kernel,
>>>>>> and it happens automagically with the 2.6.x kernel.
>>>>>>
>>>>>> IF there is nothing stopping you from using a 2.6.x kernel
>>>>>> just apt-get install <2.6 kernel you need>
>>>>>> and there you have it. GRUB will show both kernels at boot time BTW..
>>>>>>
>>>>>> To check your current kernel ls -l /lib/modules
>>>>>>
>>>>>> To find the kernels avaliable
>>>>>> apt-cache search kernel-image |grep 2.6
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Hey everyone,
>>>>>>>
>>>>>>> I'll admit my knowledge in the hotplug department isn't spectacular.
>>>>>>>
>>>>>>> Currently I have a machine setup to run a script when a specific USB
>> flash
>>>>>>> drive is inserted. I did this by defining the script and vendor ID &
>>>>>>> product ID in the usb.handmap file (/etc/hotplug/usb.handmap). This
>> works
>>>>>>> great and as expected. The script tells the device to mount and do a few
>>>>>>> things.
>>>>>>>
>>>>>>> So this works as expected, great. But now I want to future proof it a
>>>> little
>>>>>>> by only looking at the Vendor ID and then just running the script.
>> However
>>>>>>> usb.handmap requires a vendor & product ID in order for it to load. I
>>>> can't
>>>>>>> get this seem to work. Sure I can add each vendor & product ID for each
>>>>>>> device I have, however that isn't really future proofing.
>>>>>>>
>>>>>>> Currently I have usb.handmap to read:
>>>>>>> key.sh 0x0003 0x054c 0x02a5 0x0100 0x0000
>>>>>>> 0x00 0x00 0x00 0x00 0x00
>>>>>>> 0x00 0x00000000
>>>>>>>
>>>>>>> And I have tried:
>>>>>>>
>>>>>>> key.sh 0x0003 0x054c 0x0000 0x0000 0x0000
>>>>>>> 0x00 0x00 0x00 0x00 0x00
>>>>>>> 0x00 0x00000000
>>>>>>>
>>>>>>> Anyone have any ideas?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>
>>>> RbtBotL
>>>> Craig - ><>
>>>>
>>>> o BU SysAdmin
>>>> /|\ 607 777 6827
>>>> ^ Tot Ziens
>>>>
>>>>
>>>
>>
>> RbtBotL
>> Craig - ><>
>>
>> o BU SysAdmin
>> /|\ 607 777 6827
>> ^ Tot Ziens
>>
>>
>
Reply to: