I've tried to follow the suggestions made on this list to get access
to a USB disk-on-key device locally on a client.
I've done this:
Moved floppyd to /opt/ltsp/i386/bin
Created a file called usbdok in /opt/ltsp/i386/etc/rc.d/, it contains:
#!/bin/bash
chmod 777 /tmp
modprobe usb-uhci
modprobe usb-storage
mknod /dev/sda b 8 0
mknod /dev/sda1 b 8 1
chmod 666 /dev/sda
chmod 666 /dev/sda1
floppyd -d /dev/sda1
In lts.conf:
[ltsp011]
RCFILE_01 = usbdok
RUNLEVEL = 3
The client starts up, shows the modules inserted:
sd_mod
usb-storage
scsi_mod
usb-uhci
usbcore
The device files are created OK, owned by root.root and have
the permissions indicated in the usbdok file.
I can mount the device locally in run level 3 using
mount -t vfat /dev/sda1 /tmp/mnt
and the access it is expected. -t msdos also works.
I then proceed to umount the device.
All seems well so far.
But once I start the GUI on the client, and run mdir a:, the happiness
vanishes. The first time I di mdir a:, the disk-on-key flashes a bit
(so there is something going on), but reports to the shell:
floppyd_io: Input/output error
Subsequent attempts to access the device results in the message:
Permission denied, authentication failed!
Auth failed: Device locked!
Drive 'A:' not supported
Cannot initialize 'A:'
I don't know how to proceed from here, any suggestions welcome.
--
Mvh Ragnar Wisl�ff
------------------
life is a reach. then you gybe.
-------------------------------------------------------
This SF.net email is sponsored by Dice.com.
Did you know that Dice has over 25,000 tech jobs available today? From
careers in IT to Engineering to Tech Sales, Dice has tech jobs from the
best hiring companies. http://www.dice.com/index.epl?rel_code=104
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
