I've noticed yesterday as I've moved between 1.1 and 1.0 many times, just how annoying the startup is and some simple things that could be corrected.
What I'm seeing is unstable bootups, specially if I try to use anything before the load settles down. I'm using an AMD 64bit X2 3800+, 2GB ram and seeing load times on boot over 6.00! If I do anything during this time, I risk a frontend crash and it will do a router-reload, starting all this process back over again, and over again, and over again, till it finally stabilizes.
On bootup, and even on a reload, everything runs. Why, for example, every time I reload does LinuxMCE feel the need to re-populate the MythTV listings database? A simple query ahead of time to see if we have atleast 24 hours of listings should be enough to decide that we don't need to re-populate the entire database and this task can be scheduled at it's normal time. This process also runs at a normal priority, shouldn't it be niced if nothing else?
Expanding a bit more on the TV listings... why does LinuxMCE feel the need to put an alert on my screen after each boot telling me I need to wait 10 minutes for listings data? I don't care.. not after the 50th time I saw it. Why also does this alert stay on the screen if it's going to pop-up? Well after the 10 minutes, this alert is still image burning my Plasma, while there is a nice screen saver running behind it. One would think it would at least go away after the mythfilldatabase was done.
The same for the flickr script, if there is at least a few pictures available, there doesn't seam to be a good reason I can think of to saturate more IO on the drive during boot. Wait 30 minutes or so for things to calm down, then get more pretty pictures when we're stable and done booting.
