My apporach on how to keep Slackware-current upgraded
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Another feature request would be to add elilo / UEFI support, which could be a bit more difficult as the Kernel and the initrd have to be copied over to /boot/efi/EFI/Slackware/ and according symlinks have to be generated there.
The thought has just crossed my mind that the EFI system partition has a FAT-something file system (unless I'm mistaken). That doesn't support symlinks, does it?
The thought has just crossed my mind that the EFI system partition has a FAT-something file system (unless I'm mistaken). That doesn't support symlinks, does it?
No, it does not support EFI, but that's not the main reason one has to copy over the kernel/initrd on every update. The other partitions are not available at this time, so you could not link from /boot/efi to e.g. /boot which would make the situation a bit easier.
No, it does not support EFI, but that's not the main reason one has to copy over the kernel/initrd on every update. The other partitions are not available at this time, so you could not link from /boot/efi to e.g. /boot which would make the situation a bit easier.
Sorry, I think you misunderstood, or I may not have expressed myself clearly enough.
The issue is not about where to make the symlinks point to (I get it that they cannot point outside the EFI partition).
The issue is about the inability to create the symlinks in the first place. To the best of my knowledge, the FAT-formatted EFI partition simply doesn't support the notion of symlinks, or does it?
The issue is about the inability to create the symlinks in the first place. To the best of my knowledge, the FAT-formatted EFI partition simply doesn't support the notion of symlinks, or does it?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
