LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 01-10-2011, 12:26 PM   #1
Miter_J
LQ Newbie
 
Registered: Jan 2011
Posts: 24

Rep: Reputation: 0
Question Questions about lilo,etc


My thread "Can't add Ubuntu into lilo.conf" was merged with this one.
That problem has been solved, thanks to you guys~

As I solved that problem, I got several more questions:
When applying the changes by run "lilo", there's a warning about "large-memory". How come and how to solve?
When loading into lilo, there's a capital character "U" in front of "Ubuntu". At the same time, there's nothing in front of Slackware or Windows. I wonder why...
And, now that lilo read the booting info from slackware, if sometimes slackware get collapsed, could I still be able to access lilo? If I can access lilo, can I still boot into the other OSes?

Last edited by Miter_J; 01-10-2011 at 12:29 PM.
 
Old 01-11-2011, 04:53 AM   #2
Ramurd
Member
 
Registered: Mar 2009
Location: Rotterdam, the Netherlands
Distribution: Slackwarelinux
Posts: 555

Rep: Reputation: 75
Quote:
When applying the changes by run "lilo", there's a warning about "large-memory". How come and how to solve?
Not sure if I understand this question correct; but I assume that Lilo sees that your initrd is too big and therefore needs the "large-memory" option (and assuming it enables this automatically and warns you about this.) You could put the "large-memory" option in your lilo.conf and see if this removes the warning.

Quote:
When loading into lilo, there's a capital character "U" in front of "Ubuntu". At the same time, there's nothing in front of Slackware or Windows. I wonder why...
I have no idea either, sorry.

Quote:
And, now that lilo read the booting info from slackware, if sometimes slackware get collapsed, could I still be able to access lilo? If I can access lilo, can I still boot into the other OSes?
Unlike grub, lilo is entirely in your MBR; therefore, if Slackware is gone kaput lilo itself is not touched. You can still fire up your other os-es. However, you will need your lilo.conf to rewrite your MBR. Keep your lilo.conf stored on an alternate location as well, just in case you accidentally format your partition that contains your lilo.conf. Apart from that you can always boot up with a bootable disk with options like root=/dev/sda1 (or so) and access your disks again.

Hope this answers your questions.
 
1 members found this post helpful.
Old 01-11-2011, 05:15 AM   #3
DonnieP
Member
 
Registered: Jan 2008
Location: Richmond, VA USA
Distribution: Slackware
Posts: 144

Rep: Reputation: 29
Quote:
Originally Posted by Miter_J View Post
When loading into lilo, there's a capital character "U" in front of "Ubuntu". At the same time, there's nothing in front of Slackware or Windows. I wonder why...
Edit /etc/lilo.conf to change this.
 
Old 01-11-2011, 06:01 AM   #4
Miter_J
LQ Newbie
 
Registered: Jan 2011
Posts: 24

Original Poster
Rep: Reputation: 0
Thx Ramurd & DonnieP. I kind of understand something now.
 
Old 01-11-2011, 10:29 AM   #5
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,282
Blog Entries: 3

Rep: Reputation: 1446Reputation: 1446Reputation: 1446Reputation: 1446Reputation: 1446Reputation: 1446Reputation: 1446Reputation: 1446Reputation: 1446Reputation: 1446
Hi,

Welcome to LQ!
Since you haven't provided the complete error message. If your speaking about 'large-memory' relative to your '/etc/lilo.conf' then;
Quote:
ecerpt from 'man lilo.conf';
large-memory
Normally any initial ramdisk (initrd) loaded with a kernel is loaded as high in memory as possible, but
never above 15Mb. This is due to a BIOS limitation on older systems. On newer systems, this option
enables using memory above 15Mb (up to a kernel imposed limit, around 768Mb) for passing the initrd to
the kernel. The presence of this option merely indicates that your system does not have the old BIOS
limitation.

This switch (or its abscence) is not passed to the kernel, and does not in any way affect the amount of
physical memory which it will use. (See the kernel documentation for the kernel command line parameter
"mem=" for limiting the memory used by the kernel.)
'man command' is your friend!

I suggest that you look at 'How to Ask Questions the Smart Way' so in the future your queries provide information that will aid us in diagnosis of the problem/query.

Just a few more useful links;



SlackwareŽ Essentials
SlackwareŽ Basics
Linux Documentation Project
Rute Tutorial & Exposition
Linux Command Guide
Bash Reference Manual
Advanced Bash-Scripting Guide
Linux Newbie Admin Guide
LinuxSelfHelp
Getting Started with Linux



The above links and others can be found at 'Slackware-Links'. More than just SlackwareŽ links!
 
  


Reply

Tags
lilo


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
lilo configuration questions orange400 Linux - General 1 06-26-2004 07:44 AM
Few questions about Lilo HoosTrax Linux - Newbie 1 02-07-2004 05:14 PM
Lilo/boot questions vexer Slackware 5 06-02-2003 04:53 AM
Questions on LILO pilot1 Linux - General 5 12-14-2002 02:55 PM
Linux Lilo questions Tuzinor Linux - General 0 03-01-2001 10:09 AM


All times are GMT -5. The time now is 10:36 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration