OK, here's what I have learned about fedora-bookmarks .. fedora-bookmarks.rpm contains a single file, default-bookmarks.html which is installed into /usr/share/bookmarks. The first time a user runs Firefox, that file is copied into ~/.mozilla/firefox/<randomnumber>.default/bookmarks.html. Links in that file are entered into places.sqlite in that directory. As far as I can tell, once the database is created, bookmarks.html is never used. On my systems, the file has the date on which Firefox was first run. There are a number of other sqlite databases in that directory, none of which contain the Release Notes URL. Issuing: sqlite3 places.sqlite "UPDATE moz_places SET url='http://docs.fedoraproject.org/en-US/Fedora/14/html-single/Releas... WHERE url='http://docs.fedoraproject.org/release-notes/';" will cause the bookmark in Firefox to point to the correct place. The same scheme seems to apply in ~/.mozilla/seamonkey/<randomnumber>.default/, except that in older versions of Fedora there is no link to Release Notes or other Fedora websites. They are, however, the same as Firefox in Fedora 13 and 14. None of the other browsers (there are perhaps a dozen in Fedora) seem to use this file. So it would appear that an update RPM should: - Install the new default-bookmarks.html in /usr/share/bookmarks - Copy that file to bookmarks.html in ~/.mozilla for both browsers for all users. - Issue the sqlite update for both browsers o Note that if the sqlite command fails, i.e. the user has edited that bookmark, no harm is done --McD