How to preload firefox during boot

MrSavage · 01-09-2005, 11:32 PM

Hi i'd like firefox to be able to preload during boot like what microsoft did for ie.
Is this possible?

would this be applicable for any app.

I am using SUSE 9.2 and kde.

uman · 01-09-2005, 11:59 PM

What distribution do you use?
EDIT: Duh I'm dumb you use suse...in that case I'm not sure. try going to a command line and typing "rc-update" (without the quotes) and see if it finds it. If so, I'll explain what to do. If not, I don't know.

JanusPaul · 10-01-2005, 12:41 PM

What about Debian/KDE users?

Ahmed · 10-01-2005, 02:46 PM

Ever tried a task manager? I suppose there might be an option for issuing commands at startup. Or if you have KAlarm you can use that. (Insert the command "firefox" and set the recurrence to every login)

-A

JanusPaul · 10-01-2005, 03:07 PM

KAlarm is unavailable until the Debian package for it gets upgraded to KDE 3.4 (currently dependency lists link to KDE 3.3 libraries). KDE has an autostart feature, but preloading an application and starting an application are not entirely the same thing. I would like to know myself where a list of preloaded applications can be found for kdeinit's startup session. How would a task manager assist in this situation? Or what would I have to do inorder to accomplish preloading firefox o.O?

cs-cam · 10-02-2005, 12:10 AM

Why do you want to do this? Faster startup? What's the point of saving a couple of seconds, once every boot? That said, if you'd Googled the question like I just did you'd have found plenty of articles on the subject. The main suggestion for linux seems to be mounting some of your libs into RAM. Probably a complete waste of time but best of luck to you

JanusPaul · 10-02-2005, 12:16 AM

Quote:

Originally posted by cs-cam
Why do you want to do this? Faster startup? What's the point of saving a couple of seconds, once every boot? That said, if you'd Googled the question like I just did you'd have found plenty of articles on the subject. The main suggestion for linux seems to be mounting some of your libs into RAM. Probably a complete waste of time but best of luck to you

I have googled this subject, with many different keywords. Coming here to LQ is usually my last resort.

cs-cam · 10-02-2005, 07:59 AM

The best answer I could find was to make a new partition in your RAM (how-to), copy the firefox libraries to the new partition and either tell firefox to look in the new spot for them or mount the RAM disk to where firefox will expect it's libs to be. The reason this would speed things up is because RAM access is many times faster than your average hard drive.

I'm still struggling to figure out how this is a really good idea, you'd have to figure out a lot of what you need to do on your own as I couldn't find anyone who'd done it before or if they have, nobody has written a tutorial that I could find.

If you run into trouble post back and we'll help

craigevil · 10-02-2005, 09:13 AM

Not sure about Suse 9.2, but in 10.0 you can use "preloading".
SUPER preloading - OpenSUSE,

Quote:

What does preloading do? The basic idea is to load files into the cache that are used by certain applications, e.g. OpenOffice. This makes OpenOffice start up much faster because it reads most of its data from cache, not from the slow harddisk. Once KDE has completely started, the preloading is done in the background. This will not affect bootup speed at all.

Debian users can use "prelink" to load Firefox faster. It opens almost instantly on my system with a Anthlon 1.8 with 512 MB ram.

If you are using KDE you can add Firefox to the Start-up apps. You can do the same thing in Xfce. For Gnome users here is a guide (looks a little old)
Session

Adding the comand to .xinitrc should work also

JanusPaul · 10-02-2005, 01:18 PM

Quote:

Originally posted by cs-cam
The best answer I could find was to make a new partition in your RAM (how-to), copy the firefox libraries to the new partition and either tell firefox to look in the new spot for them or mount the RAM disk to where firefox will expect it's libs to be. The reason this would speed things up is because RAM access is many times faster than your average hard drive.

I'm still struggling to figure out how this is a really good idea, you'd have to figure out a lot of what you need to do on your own as I couldn't find anyone who'd done it before or if they have, nobody has written a tutorial that I could find.

If you run into trouble post back and we'll help

When is anything in Linux ever a good idea? Oh wait, I thought learning stuff just for the sake of learning was a good thing! Isn't that what Linux is all about? Freedom to learn! Who cares if it's a complete waste of time 'in your eyes', does that make it any less worth learning just for the sake of learning?