Could be version dependant.....
I have implemented a site that uses Firefox 1.5.0.6 with CAM
protoptype with no problems.
Also a truss(1m) of a firefox 2.0 startup shows that it
accesses .mozilla/firefox/profiles.ini
and not ./mozilla/appreg
$ cd .mozilla
$ cd firefox
$ more profiles.ini
[General]
StartWithLastProfile=0
[Profile0]
Name=default
IsRelative=1
Path=e4qd75vw.default
Craig Bender wrote:
Guess it depends on the version:
# strings appreg
ADdv
Users
Common
Version Registry
Private Arenas
Profiles
Version
HavePregInfo
AutoStartWithLast
default
migrated
NCProfileName
NCServiceDenial
NCEmailAddress
NCHavePregInfo
CreationTime
;M{4
LastModTime
directory
/export/craig/.mozilla/default/y6lksy15.slt
CurrentProfile
default
Lars. Tunkrans wrote:
Mmm, Mozilla/Seamonkey users $home/.mozilla/appreg Firefox
uses $home/.mozilla/firefox/profiles.ini
which is not user dependant , it only has the relative path name of
the userprofile(s)
Craig Bender wrote:
The problem with prototoypes is the appreg file is hard coded to the
user that created it.
Lars. Tunkrans wrote:
Craig Bender wrote:
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.
Yes, provided that you want the same setup for Real users and
CAM users.
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.
Yes If you install Firefox twice , say once in
/opt/sfw/lib/firefox for Realusers and once in /opt/firefox
for CAMusers you can have separate
configs for the different user categories. It will deliver the
same functionality as a CAM prototype
//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
_______________________________________________
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
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
