SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi
Maybe I repeating.....sorry in advance
I an not going to compile my kernel in soon time, so practically I won't need LILO booting every time. I wan to close it:
Can I do it commenting 'prompt' line in lilo.conf and setting timeout=1 (if I'll need that)?
ideas?
what do you mean "every time"?? just leave it there, it's always useful incase something goes wrong. wether you are going to compile a kernel or not is pretty irrelevant.
hide? well set the timeout to zero then... or change the boot message to be text, it'll at least look a lot more subtle. but like i said, you should *always* be able to get into lilo in case of problems
look, the manpage says that without prompt it will instantly boot to the default. but that is a pretty dumb thing to do, especially for a newbie like yourself.
delay=tsecs
Specifies the number of tenths of a second the boot loader should wait before booting the first image. This is useful on systems that immediately boot from the hard disk after enabling the keyboard. The boot loader doesn't wait if `delay' is omitted or is set to zero.
uhhhhhh....
Ok here it is:
If you ever seen winbloze it starts automatically after BIOS initializes all hardware, blahblah (I think you know this routine) So I want Linux to start the same way.....
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
Posts: 1,152
Rep:
edit your /etc/lilo.conf file and comment out any reference to a delay,
prompt, or timeout, and when you are done with that, run /sbin/lilo
from the man page:
(man lilo.conf)
Code:
.
.
.
delay=<tsecs>
Specifies the number of tenths of a second the boot
loader should wait before automatically booting a
locked command line, a command line pre-stored by
"lilo -R", or the default `image=' or `other='.
When `delay' is non-zero, the boot loader will wait
for an interrupt for the specified interval. If an
interrupt is received, or is already waiting, the
boot: prompt will be be issued, and no automatic
boot will take place. The setting of CAPS LOCK or
SCROLL LOCK, or any of the keys ALT, CTRL, or
SHIFT, when held down, are taken as interrupts.
This action is modified by specifying `prompt' (see
below).
.
.
.
prompt Automatic booting (see `delay' above) will not take
place unless a locked or pre-stored ("lilo -R")
command line is present. Instead, the boot loader
will issue the boot: prompt and wait for user input
before proceeding (see timeout below). Unattended
default image reboots are impossible if `prompt' is
set and `timeout' is not, or the default image is
password protected at a higher level than
`restricted'.
.
.
.
timeout=<tsecs>
sets a timeout (in tenths of a second) for keyboard
input at the boot: prompt. "timeout" only has
meaning if "prompt" is mentioned. If no key is
pressed for the specified time, the default image
is automatically booted. The default timeout is
infinite.
Just so you know, Windows doesn't just boot immediatly after bios, it goes through it's own boot loader but covers it with a graphic. A good idea is probably to cover yours with a graphic (like you said you wanted to in a previous post). Get ride of prompt, and make a short delay (but not 0). That way if you do have a problem you can hit tab and boot off another kernel if you wish.
As was said before, it is very dangerous to not leave yourself any way of getting into lilo and doing something manually.....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.