How fast does your box boot?

[rickenbacherus]

My system:

XP2200+ (1.8GHz)
1G PC2700 DDR Kingston
Asus A7N266-VM mobo
1 40G IDE hdd
hdd install Kanotix
Custom 2.6.3 kernel
GUI - Fluxbox w/ ROX

Time elapsed between pressing the power-on switch to fully booted into GUI:

45 seconds 8)

[Stephen]

System:

Athlon 1333
768MB PC133
Gigabyte GA-7ZXE
120gb & 40gb HD
Debian SID
Kernel 2.6.4-rc3
KDE 3.2.1

Time to desktop 1 minute 19 seconds.

System2:

Duron 800
512 MB PC133
Some MSI MB
40 gb HD
Debian Sarge/SID
Kernel 2.4.25
KDE 3.1.5

Time to desktop 1 minute and 33 seconds.

System3:

Packard Bell P60
24mb ram
500mb HD
Debian Woody
Console

A good three minutes to the console and about 4 hours of my time when I put a net install on it earlier tonight.

[oldgeezer]

With reasonably modern kit, installed Knoppix/Debian takes around 1m 25s, 'doze takes about 50s. SuSE takes much much longer and Mandrake just a tad longer, although both of these have a bigger payload of apps. The exact flavour of hardware doesn't seem to make much difference within ~10%. All KDE.
OG.

[spiff1281]

XP2800+ (1.8GHz)
1G DDR
Asus A7N8x
60 + 40G IDE hdd
hdd install Debian Woody (I don't remember) + Knoppix source.list

about 40 secs untill kdm

[desire]

System =
Duron 1200
ECS K7S5A Pro Motherboard
256MB DDR
40 Gig Maxtor
10X4X24 HP 9300 CDRW Drive
From cold boot->fully loaded GUI
Knoppix 3.3 from CD 3mins 45secs
Mandrake 9.1-> KDE 1min 20secs
Mandrake 9.1 ->IceWM 53secs

Keep in mind the Knoppix boot was off the CDRW drive (24X at best), it would be interesting to see how it would boot off a HDD.

[CrashedAgain]

I have a Toshiba 600 mhz laptop, 160 mb ram, 6G HD and a 1.2 ghz HP Pavilion, about 280 mb ram (I forget & it's busy right now), 40 G Hd. I have used Mandrake 9.2 & Knoppix (HD install) on both of these, no really noticable difference between Mandrake & Knoppix. The laptop takes about 1min 15 to 1 min 30 & the HP about 1 min to 1 min 15. I also had a 233 mhz, Knoppix took about 2 min on it. Most noticeable change to speed things up was more ram.
Biggest operational slowdown is if you 'accidentally' click on an MSWord file while the system is loaded up with other stuff...browser running maybe two or three windows etc. Then you are stuck in a big wait (up to 4 minutes) while OpenOffice wakes up its groggy self to preview the .doc file you didn't want to see anyway. And no way to kill it 'till it's up.

[maillion]

In the evening, after work, far less time than it takes to tell it. In the morning, when I want to check my email before I have to dash off to work, forever and a day... 8)

[windos_no_thanks]

Biggest operational slowdown is if you 'accidentally' click on an MSWord file while the system is loaded up with other stuff...browser running maybe two or three windows etc. Then you are stuck in a big wait (up to 4 minutes) while OpenOffice wakes up its groggy self to preview the .doc file you didn't want to see anyway. And no way to kill it 'till it's up.

Easy ;-)



ps auxwww | grep soffice | awk {'print $2'} | xargs kill