hi cuneytm,

sorry for the delay but i had some days off and i'm still trying to catch up
work. things are getting quite busy here so don't expect quick responses...

cuneytm schrieb:
>
> Thanks for the reply!
>
> Noticed few issues along the way:
>
>> if you change the mail reader command via
> gnome-default-applications-properties
>> and terminate your session by logging out your configuration is written to:
>
>> /home/tcos/.gconf/desktop/gnome/url-handlers/mailto/%gconf.xml
>
>> the easiest way to make this a default for all users/thin clients is to
> create
>> the following folder on your openthinclient server:
>
>>
<INSTALLPATH>\server\default\data\nfs\home\_USER_OVERWRITE_\.gconf\desktop\gnome\url-handlers\mailto
>
>> and copy the above stated file "%gconf.xml" into it.
>
> I have tried that and the file gets copied allright.
> However, the first time you login to the (newly created) thinclient desktop
> of a user, mailto: links is not functioning.
> The config file is there, the file is there but the mailto: handler just
> doesn't work.
>
> When i check gnome-default-applications, the mail reader still shows the old
> evolution.
>
> Without changing anything, restart the thinclient which ends the session and
> re-login.
>
> Then voila, mailto: becomes functional.
>
> I have no idea why it doesn't work in the very-first login, besides assuming
> that on-session-end the gconf xml files under
> gconf\desktop\gnome\url-handlers\ committed?
>
> Still, that sounds a bit not too convincing on why its happening.
>
> Any ideas?
>
i just gave it a try and was able to reproduce it. it seems that it's not
sufficient to just copy the following file:

.gconf/desktop/gnome/url-handlers/mailto/%gconf.xml

to me it looks like you need at least the following directory structure in your
"_USER_OVERWRITE_" to get it working at the first login:

.gconf/desktop/
.gconf/desktop/%gconf.xml
.gconf/desktop/gnome
.gconf/desktop/gnome/%gconf.xml
.gconf/desktop/gnome/url-handlers
.gconf/desktop/gnome/url-handlers/%gconf.xml
.gconf/desktop/gnome/url-handlers/mailto
.gconf/desktop/gnome/url-handlers/mailto/%gconf.xml

notice the additional (empty) files:

.gconf/desktop/%gconf.xml
.gconf/desktop/gnome/%gconf.xml
.gconf/desktop/gnome/url-handlers/%gconf.xml

>> the quick and dirty way would be to copy your shell script in the
"_USER_OVERWRITE_" directory as well and set the mail reader command to
>
> Thanks, copying of files works! I liked _USER_OVERWRITE_  to set defaults
> for firefox etc.
>
an even "better" quick and dirty way to make a shell script, document or
whatever available to the OS would be to create a directory below:

<INSTALLPATH>\server\default\data\nfs\root\

it will be "visible" by the os in "/var/tcos/".

let's say you create a the following directory/file:

<INSTALLPATH>\server\default\data\nfs\root\custom\help.pdf

you could configure the document viewer with the following parameter:

/var/tcos/custom/help.pdf


>> you can create some "magic" directories inside the
> "webmail/webmail-0.0.1/tcos"
>> directory to put additional scripts in. they will be executed by run-parts
> (see
>> man run-parts) at different points in time:
>
>> as you wish to modify gconf settings you should create the directory:
>> webmail/webmail-0.0.1/tcos/PostLogin
>> and create a setMailCommand.sh script to put it there:
>
>> this script should modify the gconf-database or create the above stated
".../%gconf.xml" file. hint: have a look at the desktop package on how to
modify the gconf-database with gconftool-2.
>
> This is great! This gives a lot of insight on how to configure packages upon
> booting stages.
>
> However, mailto: handler wont work upon -the-very-first-login even if the
> modification is done within PostLogin folder.
>
if you modify the gconf-database via gconftool-2 (not by copying the file) it
should create the above stated missing "%gconf.xml" files as well.

>> - adds the evince.desktop file to the /usr/share/applications folder
>
> Just curious, why do you need to copy the .desktop file to
> /usr/share/application ?
>
well, this is just the place where gnome applications usually store it's
*.desktop files ;-)

> In other words, what is the use for the /usr/share folder and its'
> subdirectories?
>
as the name says it's used to share files with different applications.
in detail it should hold shared architecture-independent data.
see http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard for further
informations.

>> sso
>> loggin in as user/pw: foobar/foobar would generate the following request:
>> http://intranet/login.aspx?user=foobar&pwd=000767010901040217
>
> COOL! Thank you.
>
>> don't tell anyone:
>> it's the original highly sophisticated heavily encrypted and unbreakable
> citrix
>> ica-client password algorithm reverse engineered ;-)
>
> unbreakable allright =)
>
> Out of curiosity, why and where ica-client will make use of such custom
> encryption?
>
if you enter a password in the wfcmgr (connection manager) connection dialogue
it gets stored in the home directory.
for the why you have to ask citrix ;-)

>>> via GNOME-MONITOR is advisable? How to enable/show GNOME-VOLUME CONTROL? It
complains the file is missing
>
>> this answer is simple:
>> it's just not included yet.
>
> I guess from thick client usability point-of-view, monitor and volume
> control, along with the Screen Capture tool (so that users can take
> snapshots and send for support inquiry or what not) that is available by
> default in ubuntu dabber would be really cool.
>
you already can change some GNOME-MONITOR settings via gconf-editor. just
navigate to:

/apps/panel/applets/applet_8/prefs

make your changes and execute a:

killall gnome-panel

to restart the multiload-applet-2 (GNOME-MONITOR).

a screen capture tool will come...

> The memory monitor/panel on taskbar will make it very neat for monitoring
> the performance, at least for development level.
>
> I am not very familiar with the GNOME-MONITOR, but is there a way that one
> can add a custom monitor,
>
> like for web applicaiton driven thick client will depend on the PING
> response to the server, thus a neat monitor on the taskbar showing the ping
> response to the $INTRANET_SERVER$ would be handy for them to get a visual on
> remote connectivity status.  Just a thought...
>
uuh, i don't know much about the multiload-applet-2 and didn't had a look at
the sources either.

> I am still not aware of how to install a driver and embed to the OS.
>
well this can't be told in a few sentences.
but as a hint: if you can build and install a driver for a ubuntu dapper the
integration into the openthinclient os will be the easy.

just open an issue on this one to get it included in the documentation.

> For instance, this guy created 100s of webcam drivers for linux with ony
> single .so file;
>
> That being an example, what is the simplest way to inject a driver to the
> thinclient os?
>
> This is interesting:
http://www.theinquirer.net/en/inquirer/news/2007/04/30/one-man-writes-linux-drivers-for-235-usb-webcams
>
cool guy indeed!

> Thanks. Just being curious, what is the use for squashfs-image for the long
> run?
>
saving space, increasing speed.

>> EVINCE maybe you are running out of RAM. if you download a PDF it will be
saved in /tmp which is a RAM disk. please paste the output of the command 
"free" in
> a
>> running session to see if it's a evince-bug or not.
>
> Dont think its RAM as i have plenty free (checked from top and free), guess
> an Evince bug and might be fixed with the current update version..
>
could you open an issue for this one at http://issues.openthinclient.org/ ?

> I agree with adobe being bloated, i was just trying to understand if a
> reliable pdf-viewer exist out there.
>
> Regarding the /tmp folder being written in RAMDISK, when you browse a
> company intranet with lots-and-lots of files (big in size) and click Open
> within firefox, there is no default way of saying Firefox to save it in a
> particular folder and save it. So it always goes to /tmp folder and then
> opens from there.
> I can tell Firefox to save the files on users' desktop\downloads folder only
> when user click Save in the dialog.
>
> Obviously, this will become rather problematic. the /tmp folder will keep
> growing in the user's session as he wont' logout within the day (or more)
> and keep opening files from browser...
>
> Especially with Firefox.
>
> Any ideas on how to prevent that? I experienced openoffice not working at
> times, maybe related with tmp folder handling....i will try to recreate and
> check the tmp folder at that stage.
>
please create an issue as well. we will need a solution for this.

>>> Can we assign quotas and/or warning (i.e. clear your tmp folder, you are
>>> reaching your local storage limit ...) to users' NFS folders?
>> well /tmp (the linux temp folder) is non-persistent and gets cleaned after
> the
>> user logs out.
>> the home dir is another story. to implement real quotas for the java nfs
> server
>> would be some work but you could use a linux nfs server to achieve this.
> t
> Thinking in practical terms, can we use (change the thinclient server NFS
> setting to point) those linux-embedded NFS-server-enabled multi-bay network
> storage devices?
> I am not very familiar with linux and NFS, do we need a particular version
> or features enabled for that?
>
no, should even work with only NFS v2 implementations.


cheers,
martin

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
The Open Source Thin Client Solution http://openthinclient.org
[email protected]
https://lists.sourceforge.net/lists/listinfo/openthinclient-user

Reply via email to