LinuxQuestions.org - [SOLVED] Zap!!! boot slackware , how can I do it?

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Zap!!! boot slackware , how can I do it? (https://www.linuxquestions.org/questions/slackware-14/zap-boot-slackware-how-can-i-do-it-847506/)

Zap!!! boot slackware , how can I do it?

Alright guys I used slack on my system for a while(when it was new) then used openSuse 11.3..slack used to boot in 65 secs while opensuse in 32 secs! that to with login sound!!(KDE 4.4.4 SC)

Now am back on slack..how can I achieve that kind of speed with default + vbox modules installed?

OPensuse boots into KDE with login sound ~32 secs...

while slack boots in kde with login sounf ~42 secs(I have followed after http://www.linuxquestions.org/questi...t-time-820654/

can I reduce those those extra 10 secs that opensuse cuts by default?

Thanks :)

The first thing would be to uncomment/add the line 'compact' at the top of /etc/lilo.conf
Then run 'lilo'

Also check this thread
http://www.linuxquestions.org/questi...t-time-820654/

In the past I tried some of the solutions above and it really made it quicker.

Are you using the generic kernel + initrd and lilo compact ? If so, that's about as fast as it will get, or ...

You may be able to squeeze out some more seconds by using something like dash:
http://www.linuxquestions.org/questi...13-0-a-778084/

However, be careful, because you can mess things up.

Quote:

The first thing would be to uncomment/add the line 'compact' at the top of /etc/lilo.conf
Then run 'lilo'

How? I don't see any such line commented out(or existing) in default lilo.conf in slackware 13.1 x64?

Thnx

Quote:

Originally Posted by kapz (Post 4176106)

How? I don't see any such line commented out(or existing) in default lilo.conf in slackware 13.1 x64?

Thnx

Just add it. This is the top of my lilo.conf

Code:

# LILO configuration file

# generated by 'liloconfig'

#

# Start LILO global section

# Append any additional kernel parameters:

append=" vt.default_utf8=0"

boot = /dev/sda

compact

# Boot BMP Image.

# Bitmap in BMP format: 640x480x8

  bitmap = /boot/slack.bmp

# Menu colors (foreground, background, shadow, highlighted

# foreground, highlighted background, highlighted shadow):

  bmp-colors = 255,0,255,0,255,0

# Location of the option table: location x, location y, number of

# columns, lines per column (max 15), "spill" (this is how many

# entries must be in the first column before the next begins to

# be used.  We don't specify it here, as there's just one column.

  bmp-table = 60,6,1,16

# Timer location x, timer location y, foreground color,

# background color, shadow color.

  bmp-timer = 65,27,0,255

Quote:

Are you using the generic kernel + initrd and lilo compact ? If so, that's about as fast as it will get

H_TeXMeX_H : yes I am using generic kernel + initrd. But not lilo compact..

Okay now I have add compact like this:

Quote:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=1=0 quiet"
boot = /dev/sda
compact
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
# bmp-colors = 14,0,15,0,14,0
# Location of the option table: location x, location y, number of

but it has'nt changed boot time a bit..

Quote:

but it has'nt changed boot time a bit..

As root run 'lilo' to implement the changes.

oh, sorry but I did run lilo as root after the above changes...

my lilo.conf looks like this:

Code:

# LILO configuration file

# generated by 'liloconfig'

#

# Start LILO global section

# Append any additional kernel parameters:

append=" vt.default_utf8=1=0 quiet"

boot = /dev/sda

compact

# Boot BMP Image.

# Bitmap in BMP format: 640x480x8

  bitmap = /boot/slack.bmp

# Menu colors (foreground, background, shadow, highlighted

# foreground, highlighted background, highlighted shadow):

# bmp-colors = 14,0,15,0,14,0

# Location of the option table: location x, location y, number of

# columns, lines per column (max 15), "spill" (this is how many

# entries must be in the first column before the next begins to

# be used.  We don't specify it here, as there's just one column.

  bmp-table = 60,6,1,16

# Timer location x, timer location y, foreground color,

# background color, shadow color.

  bmp-timer = 1,1,1,1

#65,27,0,255 - original bmp-timer colour



# Standard menu.

# Or, you can comment out the bitmap menu above and 

# use a boot message with the standard menu:

#message = /boot/boot_message.txt



# Wait until the timeout to boot (if commented out, boot the

# first entry immediately):

prompt

# Timeout before the first entry boots.

# This is given in tenths of a second, so 600 for every minute:

timeout = 30

# Override dangerous defaults that rewrite the partition table:

change-rules

  reset

# VESA framebuffer console @ 1024x768x256

vga = 791

# Normal VGA console

# vga = normal

# VESA framebuffer console @ 1024x768x64k

# vga=791

# VESA framebuffer console @ 1024x768x32k

# vga=790

# VESA framebuffer console @ 1024x768x256

# vga=773

# VESA framebuffer console @ 800x600x64k

# vga=788

# VESA framebuffer console @ 800x600x32k

# vga=787

# VESA framebuffer console @ 800x600x256

# vga=771

# VESA framebuffer console @ 640x480x64k

# vga=785

# VESA framebuffer console @ 640x480x32k

# vga=784

# VESA framebuffer console @ 640x480x256

# vga=769

# End LILO global section





image = /boot/vmlinuz-generic-2.6.33.4

  initrd = /boot/initrd.gz

  label = Slackware

  read-only

You can add "&" to the end of some lines in /etc/rc.d/rc.M (such as the line which updates the font cache) though the benefits will probably be quite limited.

there was this bootup analyzation software that checked dependencies on the init tasks and made them execute more parallely. i don't remember the name or if it only worked on a particular distro or init-style though...

Quote:

Originally Posted by P42 (Post 4176315)

Ubuntu uses upstart to do something like that. Apparently it is quite fast.

A custom kernel can speed things up by eliminating loading modules and/or things you don't need.

Quote:

Originally Posted by H_TeXMeX_H (Post 4176105)

Are you using the generic kernel + initrd and lilo compact ?

What difference would changing from huge to the generic bring in terms of speed?

Quote:

Originally Posted by bonixavier (Post 4176472)

What difference would changing from huge to the generic bring in terms of speed?

The huge kernel has modules built in that are not normally needed but are included for maximum compatibility with hardware. The generic kernel is much smaller and loads modules only as necessary.