boot time
Ndrocchietto |Sono un cattomassocomunista liberale a favore delle minoranze e delle maggiorate.
Loki Harfagr
> from 0 to login?
congratulations!
Nikos Chantziaras
minoranze e delle maggiorate. wrote:
> from 0 to login?
9 inches.
Ndrocchietto |Sono un cattomassocomunista liberale a favore delle minoranze e delle maggiorate.
;) ok, ok I can deserve it, but I didn't never find nothing about
slackware optimization, My box start in 2 minutes and I think that
advertise how to have a fast boot could be important for enlarge
slackware community
Jerry Peters
2 minutes! My old Dell D300 laptop starts in less time than that
and it only has 128MB of memory and a 300MHz processor.
Once you've mounted the filesystems much of the startup can run in
parallel. You don't need to wait for sendmail or most of the other
daemons to start before you get a login window.
Jerry
ndrocc...@gmail.com
> 2 minutes! My old Dell D300 laptop starts in less time than that
> and it only has 128MB of memory and a 300MHz processor.
>
> Once you've mounted the filesystems much of the startup can run in
> parallel. You don't need to wait for sendmail or most of the other
> daemons to start before you get a login window.
>
> Jerry
there are process, rendudancies in the modules, library
incompatibilities, gcc like symbolic link, wpa_supplicant and
wlanassistant that start without found the symbolic links etc etc, I
need to ricompile but before I have to update to 12:1, I want to
arrive around the 15 , also with the startup in parallel, I have seen
something in the web
Michael Black
But how much of that is the computer booting up? I've not given
it much thought, but buying an Aspire One has made me think about it.
One still has to go through the BIOS stuff, even though nothing uses
the BIOS after booting. The BIOS loads the bootloader, which then
loads actual Linux.
And that bulky process is a result of having a universal computer.
It it could just boot Linux directly, and it could if it was arranged
to do than doing a general boot in order to handle various operating
systems.
Michael
Dan C
>> 2 minutes! My old Dell D300 laptop starts in less time than that and it
>> only has 128MB of memory and a 300MHz processor.
>>
>> Once you've mounted the filesystems much of the startup can run in
>> parallel. You don't need to wait for sendmail or most of the other
>> daemons to start before you get a login window.
> there are process, rendudancies in the modules, library
> incompatibilities, gcc like symbolic link, wpa_supplicant and
> wlanassistant that start without found the symbolic links etc etc, I
> need to ricompile but before I have to update to 12:1, I want to arrive
> around the 15 , also with the startup in parallel, I have seen something
> in the web
What the fuck are you smoking?
--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
The Usenet Improvement Project: http://improve-usenet.org
danube
cattomassocomunista liberale a favore delle minoranze e delle maggiorate.
wrote:
> from 0 to login?
I think you should ask from 0 to the command prompt, no graphical
environment as yet. The graphical environment will be hugely different,
depending on your window manager (especially these monsters KDE and
Gnome). A short boot time is indicative of a well-taylored kernel,
without much unnecessary components compiled in. I usually aim for 20
seconds or less on a desktop computer.
JB
geep
cattomassocomunista liberale a favore delle minoranze e delle maggiorate.
wrote:
> from 0 to login?
Hi,
Logged 47 secs with Slackware current huge kernel, see:
http://tinyurl.com/5bpv2h
using: http://www.bootchart.org/
Cheers,
Peter
Michael Black
If you're going to have drag races here, you have to equalize the
results.
Time means nothing, since the variable of the computer's CPU speed
is a factor. The slower it is, the slower the boot. Use an old
enough computer, and the ISA bus comes into play, further slowing things
down.
Hence you need to include the CPU speed, and figure out some way of
factoring that into an equation, to give a standard boot time independent
of the CPU speed.
Michael
geep
> If you're going to have drag races here, you have to equalize the
> results.
>
> Time means nothing, since the variable of the computer's CPU speed is a
> factor. The slower it is, the slower the boot. Use an old enough
> computer, and the ISA bus comes into play, further slowing things down.
>
> Hence you need to include the CPU speed, and figure out some way of
> factoring that into an equation, to give a standard boot time
> independent of the CPU speed.
>
> Michael
Hi Michael,
Certainly not my intention start drag-racing!
I just found bootchart to be interesting as it shows the various
processes starting up at boot-time.
I still have the bootchart file from my old 350MHz Pentium II running
Slackware 10 with 2.4.26 kernel back in 2004. It booted in 50 secs.
So 1 extra core and an extra 2Ghz have gained me 3 seconds :)
http://tinyurl.com/5pqzop
Cheers,
Peter
Frank Bell
> My box start in 2 minutes and I think that
> advertise how to have a fast boot could be important for enlarge
> slackware community
I read the whole thread up till about 2 p. m. today. I think the whole
boot speed thing is overrated. But I also think it's a legit question,
despite the ration of--er--stuff you got.
Two minutes 15 seconds from LILO to login. Long enough to pour a drink.
Slackware 12.1, default kernel, Dell Inspiron 6000 laptop, Celeron chip, 2
GB RAM, 40 GB harddrive, Pioneer external USB DVD reader/writer, external
Western Digital USB 250 GB harddrive.
Haven't timed my other computers, but the P4s do boot faster.
--
Blogging from Pine View Farm (http://www.pineviewfarm.net)
Updates daily. Worthwhile updates occasionally.
Opera (http://www.opera.com), Fluxbox (http://www.fluxbox.org), and
Slackware (http://www.slackware.com)--
the ultimate internet experience.
Cann0n
I'd be caring about it too much and make unwanted sacrifices as far as
services. I hear you can boot some services simultaneous with the boot
process, but I haven't looked into that at.
Simple fixes to speed things up include adding compact in your
lilo.conf, properly configuring and building a kernel, and disabling
services you dont need. I also commented out the ldconfig, fc-cache
and icon-cache lines in my rc.M (make sure you run them when you need
too). I also set DHCP_TIMEOUT="1" in my rc.inet1.conf.
As far as that, I haven't done much else.
goarilla
aah 18 cm's he :D we europeans don't accept
your dots as decimal seperators :D
goarilla
> On Sat, 22 Nov 2008 15:30:45 -0500, Ndrocchietto |Sono un
> cattomassocomunista liberale a favore delle minoranze e delle
> maggiorate. <Ndrocchie...@gmail.com> wrote:
>
>> My box start in 2 minutes and I think that advertise how to have a fast
>> boot could be important for enlarge slackware community
>
> I read the whole thread up till about 2 p. m. today. I think the whole
> boot speed thing is overrated. But I also think it's a legit question,
> despite the ration of--er--stuff you got.
>
> Two minutes 15 seconds from LILO to login. Long enough to pour a drink.
>
> Slackware 12.1, default kernel, Dell Inspiron 6000 laptop, Celeron chip,
> 2 GB RAM, 40 GB harddrive, Pioneer external USB DVD reader/writer,
> external Western Digital USB 250 GB harddrive.
>
> Haven't timed my other computers, but the P4s do boot faster.
odd realy odd (i got 47 seconds on a stock huge-smp kernel)
do you've got much services: sendmail, ssh, mysql, httpd running
commenting shit out of /etc/rc.d/rc.M like pcmcia does help (i suppose
this is on a desktop and not a laptop)
also commenting out ldconfig and fc-cache or fc-config helps a lot !
goarilla
you could run your custom services with an &