On Tue, Nov 12, 2024 at 09:35:08AM +0100, Hans wrote: > Am Dienstag, 12. November 2024, 07:14:34 CET schrieb kindusmith: > In very early linux, as far as I remember in SuSE-Linux, the kernel was > installed in a small partition /boot (about 3 or 4 sizes of the kernel) and a > link ponting to the kernel on the root-partitiion (the one, mounted to "/") > > This got some advantages. If you have a very big root poartition and the > kernel was installed there, then it was possible, the system could not boot, > because the kernel was not found. The reason for this was, the BIOS could not > handle the size of this big partition. > > To fix this and get not in trouble, the idea was to make a small partition > which got the kernel and can be booted, then after the kernel has started, > BIOS is no more used, because the kernel is handling the paretitiions. Andthe > kernel can handle very, very big partitions. > > The sesond advantage of putting the kernel so, is , you can mount the kernel > partition read-only, so it can not be harmed by any malware. > > For the uprading procedure it is possible (with a little script), to make > this > partition writable, and automatically read-only after upgrade is done. > (If someone is interested in this, I will paste the script here, these are > only 4 lines). > > I might remember, the seperated /boot partition was also default in RedHat, > Mandriva and SLAX, but I am not quite sure. It is now a long time ago! > > However, maybe a link is alo no more needed, even with a seperated /boot > partition.
I'm afraid none of this is relevant to the question which was about garbage symlinks in /. We know how is /boot used. -- WBR, wRAR
signature.asc
Description: PGP signature
