Ok, i think i solved this issue :-)

1. remove /usr/local/bin/LDA-* ( you will not need them ) and their activation 
lines from the kdm/gdm scripts

2. add two new file ( one for Floppy and one for CD )
cd /usr/local/bin
touch open_floppy.sh;touch open_cd.sh
edit "open_floppy.sh" so it includes...
#!/bin/bash
exec konqueror smb://$LTSP_CLIENT/drives/floppy/

and "open_cd.sh" ...
#!/bin/bash
exec konqueror smb://$LTSP_CLIENT/drives/cdrom/

set both exec permission ( "chmod +x ./open*" )
now, add two more .desktop files into the user's Desktop folder.
( i use kde's kiosk-tool , so i just put it in the main Desktop folder which 
every one sees ) 
files: Open_Floppy.desktop and Open_CD.desktop

here what Open_Floppy.desktop includes...
[Desktop Entry]
Comment=
Comment[en_US]=
Encoding=UTF-8
Exec='/usr/local/bin/open_floppy.sh'
GenericName=open floppy drive
GenericName[en_US]=open floppy drive
Icon=3floppy_unmount
MimeType=
Name=floppy A
Name[en_US]=floppy A
Path=
StartupNotify=true
Terminal=false
TerminalOptions=
Type=Application
X-DCOP-ServiceType=
X-KDE-SubstituteUID=false
X-KDE-Username=

set open_cd.desktop too, so that it points to "open_cd.sh".

and you're set ! to go :-)

clicking (or double-clicking) on the icons will open up the local media 
directly.
and very responsive too. removing the media and inserting it again will show
media's content immediately. no mount or remount...

i hope it helps :-)

Nadav

On Friday 20 January 2006 21:39, Gustavo Guillermo PƩrez wrote:
> El Viernes, 20 de Enero de 2006 11:33, Ken Tanzer escribió:
> > Well so two of us seem to be having this problem.  I'm wondering if
> > there are people who _don't_ have this problem.  Does anyone have local
> > drives working so that it continues to work, even after trying to read
> > an empty drive?  If so, I'd like to try to zero in one the differences
> > in our setups, and hopefully get this fixed.  If this problem is just
> > inherent to this method of accessing local drives, then I won't try to
> > fix it ( :) ), but it would probably be worth mentioning on the wiki
> > page.
> >
> > If there's a better way to go about this, I'm all ears.  Getting local
> > drives working is pretty important for us, as we've got a bunch of users
> > who can't use LTSP until we've got drives working.
>
> Well, I was using supermount on the thin client kernels and samba to fall
> back to the server, tx to supermount with kernel 2.6.15 I does not have
> problems even using rdp with W2003S, and even using media with bad sectors.
>
>
> WFM
>
> > Thanks in advance.
> >
> > Ken
> >
> > Nadav Kavalerchik wrote:
> > >I'm experiencing the same problem :-(
> > >i tried many things for two weeks now and i have no idea what to try
> > > next.
> > >
> > >BTW...
> > >from the Konqueror location bar i use "smb://ws001/" and i get the samba
> > >shares. clicking one of them (CD / floppy) i get nothing, except error.
> > > but refreshing (f5) a few time shows the files eventually.
> > >i also get allllloot of smb-time-outs on the server's log.
> > >(the ones that were suppose to go away with ver 4.1.1 fixes)
> > >
> > >and another BTW.
> > >I've patched the original rc.localdev for displaying correct Hebrew
> > >codepage/iocharset when reading win98 file names.
> > >see changes on lines 72,97 in the attached file.
> > >
> > >yet, another BTW...
> > >did i mentioned how amazing the ltsp project is !!! if not ;-) ...
> > >it's absolutely AMAZING how it all works . thank you all for this
> > > beautiful work !!!
> > >
> > >Nadav :-)
> > >
> > >On 1/18/06, Ken Tanzer <[EMAIL PROTECTED]> wrote:
> > >>After getting no repsonse to this plea for help, I've looked into this
> > >>more and have some additional information.  The problems reading media
> > >>seem to happen both upon the initial mount, and also whenever a read to
> > >>an empty drive is attempted.  In these cases, I have to switch to the
> > >>local machine and read the drive, and then my mount on the server is
> > >> fine.
> > >>
> > >>If I switch one floppy out for another, though, the change is correctly
> > >>detected and read.
> > >>
> > >>This behavior happens when I do the mount outside of the LDA-setup.sh
> > >>script, so it seems definitely to be something about the way smbmount
> > >> is behaving.  Here's a "transcript" that might help illuminate this.
> > >> "desktop" is our LTSP server.
> > >>
> > >>[EMAIL PROTECTED] ~]# ls -ltr tmp/floppy/
> > >>total 982
> > >>-rwxr-xr-x  1 root root 501416 May 31  2001 0000001819-04ss.exe
> > >>-rwxr-xr-x  1 root root 503805 May 31  2001 0000001819-04ff.exe
> > >>--------------------[[ floppy switched here
> > >>]]-------------------------------
> > >>[EMAIL PROTECTED] ~]# ls -ltr tmp/floppy/
> > >>total 4
> > >>drwxr-xr-x  1 root root 4096 Dec  8  2001 DescParty2001
> > >>--------------------[[ floppy switched here
> > >>]]-------------------------------
> > >>[EMAIL PROTECTED] ~]# ls -ltr tmp/floppy/
> > >>total 982
> > >>-rwxr-xr-x  1 root root 501416 May 31  2001 0000001819-04ss.exe
> > >>-rwxr-xr-x  1 root root 503805 May 31  2001 0000001819-04ff.exe
> > >>--------------------[[ floppy removed here
> > >> ]]------------------------------- [EMAIL PROTECTED] ~]# ls -ltr
> > >> tmp/floppy/ total 0
> > >>[EMAIL PROTECTED] ~]# ls -ltr tmp/floppy/
> > >>ls: tmp/floppy/: Not a directory
> > >>--------------------[[ floppy replaced here
> > >>]]-------------------------------
> > >>[EMAIL PROTECTED] ~]# ls -ltr tmp/floppy/
> > >>ls: tmp/floppy/: Not a directory
> > >>
> > >>Let me know if I can provide additional information--we'd really love
> > >> to get this working.  Thanks!
> > >>
> > >>Ken
> > >>
> > >>>I'm trying to get local devices (floppy & cdrom) working on our thin
> > >>>clients.  We're running Fedora Core 4, plus LTSP 4.1.  Following the
> > >>>Wiki's Local Media page (and adding the line MODULE_01       =
> > >>>ide-generic) to my lts.conf, I'm able to _sort of_ get these devices
> > >>>working.  Specifically, the drives, drives/cdrom and drives/floppy
> > >>>entries are created in my home directory.  cdrom and floppy both show
> > >>>as empty, however, unless I switch to my local machine (i.e., the thin
> > >>>client), and do an "ls /tmp/drives/cdrom".  The ls works OK, and then
> > >>>my session on the server is able to see the drive contents as well.
> > >>>
> > >>>Did I miss a step, or does anyone know what might be causing this
> > >>>problem?  Thanks in advance.
> > >>>
> > >>>Ken


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_____________________________________________________________________
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

Reply via email to