What's the purpose of links in a filesystem that go nowhere?
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Apparently it isn't the dumbest thing I've ever seen. I'd delete it but you might want to wait for answers from Suse gurus. Something somewhere might actually make use of it.
I wouldn't be too quick to remove it!
Seems to be a Suse thingy as I see it in my 10.1 version.
Also noticed it is near time to backup_mbr in my box too.
The OP didn't say anything about an error message ....
Quote:
I noticed a link in my /boot directory that doesn't seem to go anywhere:
and as I mentioned, seems to be related to the backup_mbr which is likely to be used if you want to restore the mbr. If I recall, that is a feature in the YAST control center.
andy@op3n:~> cd /boot
andy@op3n:/boot> cd boot
andy@op3n:/boot/boot> cd boot
andy@op3n:/boot/boot/boot> cd boot
andy@op3n:/boot/boot/boot/boot> cd boot
andy@op3n:/boot/boot/boot/boot/boot> cd boot
I mean, WTF's this all about?
Yep, you are screwed. You'll never get out of this.
This symlink is needed if there is separate boot partition. Then GRUB can still find the kernel in /boot/somekernel. You can't say it leads nowhere, it leads to same directory with /boot added on path.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.