Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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: I have an old Dragon Linux distribution based on Slackware 7.1. This booted from an DOS/Windows O.S. I created a new partition, moved a file BZIMAGE to /boot and installpkg'd the packages. The system performs OK. However, it includes a package ide.tgz, with another kernel image: vmlinuz.
Code:
$ file BZIMAGE
Linux kernel boot executable bzImage, version 2.2.16 (root@bigkitty) #16 Fri, RO-rootFS, root_dev=0x303, Normal VGA
$file vmlinuz
Linux kernel boot executable bzImage, version 2.2.16 (root@bigkitty) #97 Fri, RW-rootFS, root_dev=0x303, Normal VGA
In fact there also is a scsi.tgz.
The thing is that the ide.tgz package not only includes vmlinuz but System.map and config. My question is: of these two kernels, which should I use and should I use an initrd? The machine has both IDE and SATA controllers, though at this time I only use IDE (PATA).
I looked on the kernel archives website and I didn't find kernel 2.2.16-
The long term mentioned is the 2.6.32.63 version of the kernel. https://www.kernel.org/
I have a more important question I think: Why doesn't BZIMAGE need the System.map and config files? I know System.map is kind of a symbol table (wikipedia). About config I know nothing. Another question would be: how does lilo know what System.map and config files to use? In lilo.conf I only write the path for the kernel image, and the name of this file could be anything, as long as it matches the name given in lilo.conf.
"A map file (/boot/map) containing the location of the kernel, and the lilo command (/sbin/lilo), which reads the configuration file and uses the information to create or update the map file and to install the files LILO needs." http://docstore.mik.ua/orelly/linux/lnut/ch04_02.htm
Quote:
how does lilo know what System.map and config files to use?
Evidently there is only one other map file. (/boot/map) (unless I misunderstand)
There is only one other map file that specifies an alternative map file.
The map installer program /sbin/lilo updates the boot sector and creates the mapfile.
A new map is created for the images described in the configuration file /etc/lilo.conf and registered in the boot sector.
/sbin/lilo with (-v) list's the currently mapped files. Notice it says "files" How many is what I'm having trouble finding out--
If the (-c) option is omitted than the /etc/lilo.conf is used.
Even after finding the info. on initrd and initramfs it's not exactly clear which you should use-
Perhaps this is about preference?
Both initrd and ramfs are zipped at compile time, but the difference is, initrd is a block device unpacked to be mounted by the kernel at booting, while ramfs is unpacked via cpio into memory-
Both initrd and ramfs are zipped at compile time, but the difference is, initrd is a block device unpacked to be mounted by the kernel at booting, while ramfs is unpacked via cpio into memory
Exactly. But what can confuse people is that files /syslinux/initrd.img in a Slackware media as well as /boot/initrd.gz output of /sbin/mkinitrd are actually initramfs, despite their names
Exactly. But what can confuse people is that files /syslinux/initrd.img in a Slackware media as well as /boot/initrd.gz output of /sbin/mkinitrd are actually initramfs, despite their names
I can see where it could be a tad confusing:-
Thanks!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.