HD crashed, reinstalled OS, how did Firefox keep my Bookmarks Toolbar?
This is not really a problem, but I am wondering how this happened, if someone can explain it.
I had a hard drive crash, so I replaced it and installed openSUSE Linux. Upon rebooting after the install, I opened Firefox and my Bookmarks Toolbar was the same, with additions I had made for personal sites (some Linux help sites and job search sites I added) before the HD crash.
I do not use Sync, so that's not part of the equation, unless there's an aspect of Sync that is on by default.
My question, out of curiousity and a sense of wondering about security, is this: Is this Bookmark Toolbar information stored somewhere in the depths of a server at Mozilla/Firefox (or somewhere else) and how did my new install pick up my personally modified Bookmarks Toolbar for use in the new install?
সমাধান চয়ন করুন
That would be question for openSUSE support, if you were using the version of Firefox that comes with openSUSE.
The version of Firefox which comes directly from Mozilla [which you would have installed your self] does not have Sync enabled by default. The version from openSUSE might have their own feature for that, but I would be real surprised if it was automatically enabled without your knowledge, or if Sync was automatically enabled either.
প্রেক্ষাপটে এই উত্তরটি পড়ুন। 👍 1All Replies (2)
চয়ন করা সমাধান
That would be question for openSUSE support, if you were using the version of Firefox that comes with openSUSE.
The version of Firefox which comes directly from Mozilla [which you would have installed your self] does not have Sync enabled by default. The version from openSUSE might have their own feature for that, but I would be real surprised if it was automatically enabled without your knowledge, or if Sync was automatically enabled either.
Thanks, the-edmeister. I'll ask there. I just thought maybe there was a common Firefox version across Linux distributions, but apparently that's a false assumption.
I'm going to mark this solved since it's not really a Firefox issue. Thanks again for your help.