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.
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?
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.
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...
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.