DapSync

slef-reflections on Device Drivers

Oracom ORC-200M Media Player
USB Flash Sticks

Home page(/) Latest blog(./all.html) # slef-reflections on Device Drivers. Oracom ORC-200M Media Player. Samsung GDI driver used for my ML-4500(./software. Remove the ldapSync folder. Start the Symantec VIP Enterprise Gateway service from Services.msc. Upon logging back into the EG console the default activation options should appear under User Store LDAP Directory Synchronization.

USB Flash Sticks

Fringe Benefits of LUGs: USB Flash Stick Devices

2007-09-03 (Permalink): Here's my latest silly trick with the udev rulesdiscussed previously.

Add a udev rule of ACTION'add', KERNEL'sd*[!0-9]',ENV{ID_SERIAL}'10d6_USB_2.0(HS)_Flash_Disk_A00000000001',RUN+='/usr/local/bin/dapsync' where dapsync is something like this script:-

and fstab has a line for /Mount/USB-DAP pointing to the right device/locationthing in /dev/disk/by-id

Then, build up podcasts under /opt/Podcasts, plug the audio player10d6_USB_2.0(HS)_Flash_Disk_A00000000001 into the right port and wait for thethree notes to play...

Comment on this

2007-08-17 (Permalink): I might be the last to notice, but when trying toanswer the LUG question

'All I want to do is mount a particular USB stick to a directory/mnt/particular_usb_stick/ without having to go check on what device it is andediting the script that does the mounting every time.'

I discovered that I seem to have a /dev/disk/by-id/usb-0930_USB_Flash_Memory_LONGHEXSTRING-part1 and an even less meaningful (buthopefully globally unique) /dev/disk/by-uuid/ device by default already.

That'll make a lot of things much simpler.

Didier Raboud commented:

'For the USB Flash disks, why not use udev rules ? It allows to createcorrect /dev/* nodes and then automatic mounters (KDE's, ...) mount them onthe right place...

I once had a device I wanted to be mounted under /media/iaudio. I createdthe correct udev rule to get /dev/iaudio addressing always the same device andpartition, when connected. KDE was then able to mount it on /media/iaudio(visibly taken from node name).

Hope it helps, regards,

Didier'

Dep Sync Intune

Thanks. The by-id device is created by udev rules, but who needs KDE to auto-mount it? I added a line to my udev rules.d/99-local

'ACTION'add', KERNEL'sd*[0-9]',ENV{ID_SERIAL}'0930_USB_Flash_Memory_LOGHEXSTRING', RUN+='/sbin/mount/Mount/BlueKey'

and a matching line to fstab

'/dev/disk/by-id/usb-0930_USB_Flash_Memory_LOGHEXSTRING-part1 /Mount/BlueKeyauto rw,noauto,users,uid=1000,noexec,iocharset=utf8 1 0'

and that seems to work. It would be clever to use automount, which would alsosync and unmount it after inactivity, but I don't have it installed on thatmachine.

Simon Ward commented:

Dap Incoterms-2010

'usbmount is a package I find useful, and doesn't depend on your choice ofdesktop environment. When a USB storage device is inserted, it will getmounted. Hooks can be used to create symlinks at mount time. There is one thatlinks by model name included in the package. I also have another hook thatcreates a symlink based on the volume label.'

Its homepage suggests itsauthor has abandoned it:

'Many distributions are now adequately handling usb - so I haven't spentmuch time improving usb-mount.'

What does usbmount give that automount wouldn't?

Simon Ward commented:

'(I did not realise that usb-mount is no longer maintained.) usb-mount'smain advantage is that it did something useful without configuration: simplyby installing it you get USB devices automatically mounted when they areplugged in, and symlinks created based on model name. A mere copy-paste-modifywas required to get symlinks created for volume labels.

Daps Inc Placement Service

I think automount can do just as well (better, given that it will unmountthe device after inactivity), but requires a little more thought to set up.'

Ben Hutchings commented:

'The identifiers used under /dev/disk/by-id encode location, including inthis case which USB port is being used. You will probably do better to use thefilesystem's label or UUID. Rather than writing out /dev/disk/... you canspecify LABEL=<label> or UUID=<uuid> in place of a device name infstab (or on a mount command line, though this doesn't seem to bedocumented).'

Appsync Pricing

I always seem to plug devices into the same ports, so it didn't bother memuch.

Comment on this
Start of this section
Start of this page

Oracom ORC-200M Media Player with Linux 2.6.21.5 usb-storage driver

2007-07-03: Now that my Samsung YP-U2 wasdestroyed, I'm leftwith the Oracom ORC-200M USB Audio Player that I was given a whileago.

It seems that this doesn't work with recent 2.6 kernels. Tales of brokennessabound onlivejournal,in ubuntu forums, and inGentoo forums.

Its USB ID (in lsusb or /proc/bus/usb/devices) is 0f19:0103 and there is apatch available for0f19:0101, which is thesimilar ORC-100 and DION-MX player. Simply changing the ID and using thatpatch didn't work for me. I could see the device appear in /proc/scsi/usb-storage (which was new), but still nothing in /proc/scsi/scsi, so I updatedthe patch slightly.

Daps Inc

The new patch for linux-2.6.21.5 is:

Hope that helps someone else. Leave a comment if you have any improvements,please. I don't really know what I'm doing with USB and I didn't finddescriptions of the usb-storage flags (US_FL_ right?). I just experimenteduntil it worked.

If you need to learn how to patch, here are the notes that I sent anintroduction to koha-devel in March:

2007-03-17:

'I can't find the guide that I mentioned on IRC, but those looking for tipson better use of diff and patch may find them in this book

'Comparing and Merging Files with GNU diff and patch'

by David MacKenzie, Paul Eggert, and Richard Stallman http://www.network-theory.co.uk/docs/diff/Overview.html

My most frequent commands are:

1. generating a patch of changes to one file: cp file file.orig ; edit file; diff -u file.orig file | tee file.patch

2. generating a patch of all changes in a directory: diff -ruN dir.origdir.mod > all-changes-in-dir.patch

3. applying a patch to a file: patch file < file.patch

4. applying a patch to a directory: cd dir && patch -p1 < /tmp/all-changes-in-dir.patch

5. reversing that patch out again when it doesn't work: cd dir &&patch -Rp1 < /tmp/all-changes-in-dir.patch

There are some handy cvs diff commands:

1. cvs diff -u file # changes since last commit

2. cvs diff -r1.1 -r1.2 -u file # changes between given revisions

and with git:

1. git diff -u file # changes since last commit

2. git diff -u rel22 master file # changes between given branches

This can also give a crude way to reverse a change: use diff to make a patchfile and then feed it to patch -R... but there are usually better ways, likecvs update's merge options and git revert.

If you are using patch files without revision control much, you may findwiggle helpful.

Ask questions and I'll try to answer. Mangling files is one thing I have hadfar too much practice at!'

Comment on this
Start of this section
Start of this page

Comment form for non-frame browsers.

Comments are moderated (damn spammers) but almost anything sensible getsapproved (albeit eventually). If you give a web address, I'll link it. I won'tpublish your email address unless you ask me to, but I'll email you a linkwhen the comment is posted, or the reason why it's not posted.