I believe you can make all these changes in the default mimetypes.rdf
(/opt/<firefox/mozilla>/defaults/profile which will get copied into the
users .moz structure when you do the mozilla/firefox -CreateProfile.
Same thing for your prefs.js and other settings. You can control the
screen size by changing the default localstore.rdf
The best way to figure out these changes is to run it as a CAM user,
make your changes then merge the new entries into the default profile.
I find it far easier to manage by installing moz/ff into a different
directory. This way you don't have to worry about it being clobbered by
patches and your changes only affect CAM users.
It's far better to have a script call moz then to try to put the
commands in the CAM path to application.
i.e. your cam script would look like this:
#/bin/sh
/opt/mozilla/mozilla -CreateProfile
/opt/mozilla/mozilla
Lars. Tunkrans wrote:
Alexandros Papadopoulos wrote:
On Wednesday 20 December 2006 01:01, Lars. Tunkrans wrote:
<snip>
> Start a CAM session verify that you are USER utcu0
> Start firefox and initialize all defaults to your likeing
> Open all files that you need to automate . Run all media types
that
> you wish to
> program and select to " always Open media X with App Y" , Do NOT
Exit
> FIREFOX.
Within firefox, a kiosk user is not allowed to declare new plugins.
Choosing a helper application for TIFF images (e.g.
/opt/csw/bin/display) enables one to display the images in an
external viewer, but not within the browser, in page frames etc.
Sorry but I just proved on my system using SRSS 3.1 and Firefox
1.5.0.6 on a Sunray 1G in CAM mode.
I can klick on a unknown file and configure a helper application and
start it.
this resulted in additional entries in the mimeTypes.rdf file
Maybe you are trying to use Firefox as we used Mozilla. In firefox you
are supposed to add helper apps as you go, interactively.
when you klick on an unknown file type you get a dialoge to catalouge
the filetype and define the helper app.
THIS IS WHY YOU NEED to CREATE a PROTOTYPE with all the choices
already made for the inexperienced Kiosk user.
later versions Firefox does not even have the possibility to preconfigure
plugins via the GUI.
Otherwise something else is wrong with your installation
Permissions ? Ancient versions of software ?
From another terminal : Copy the whole
/var/opt/SUNWbb/root/home/utcu0/.mozilla/* hierarchy
to /var/opt/SUNWut/kiosk/prototypes/firefox/.mozilla
BEFORE YOU EXIT FIREFOX on the first screen.
Then you rename
/var/opt/SUNWut/kiosk/prototypes/firefox/.mozilla/firefox/*.default
to something like
/var/opt/SUNWut/kiosk/prototypes/firefox/.mozilla/firefox/*.CAM
Make sure that the whole hierarchy ( including dot-files ) is set
to read-only and owned by root:root so no-one
can change the files in /var/opt/SUNWut/kiosk/prototypes/firefox/
Then you edit your CAM application firefox parameters so that the
commandline is
/opt/sfw/bin/firefox -P CAM
The web interface on port 1660 does not seem to allow this. I passed
the said argument to the invocation command of firefox, applied and
logged out, only to find it had reverted to the default
(non-argument) command once I logged in again.
Yes it does !
A screenshot from a test server running Solaris 10 U2 with SRSS 3.1
http://hem.bredband.net/lartun/Screenshot.jpg
//Lars
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
