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.
I am planning my first Slackware installation and I would like to create a symbolic link such that /opt is recognized as /usr/local. Reason for doing this is to avoid having a separate partition for them
I understand the command is:
ln -s /usr/local /opt
(Please correct me if I am wrong.)
My main question is: what do I need to do as part of the installation to make sure that this command 'sticks' for each time I boot?
When you make a link (whether symbolic or not), you're actually creating a file that acts like a shortcut to the other directory/file. As such, you don't have to do anything to make sure it stays each time.
90% of what goes into /opt anyway is put there by the user so you can generally force it to install to /usr/local instead, but whatever works for you!
When you make a link (whether symbolic or not), you're actually creating a file that acts like a shortcut to the other directory/file. As such, you don't have to do anything to make sure it stays each time.
90% of what goes into /opt anyway is put there by the user so you can generally force it to install to /usr/local instead, but whatever works for you!
Many thanks for the reply.
I guess I could at a later date find the appropriate file and delete it if I no longer required the link.
I am planning my first Slackware installation and I would like to create a symbolic link such that /opt is recognized as /usr/local. Reason for doing this is to avoid having a separate partition for them
Beware.
Slack installs KDE under /opt, so you could have some problems doing this if you intend to use KDE.
I think I will therefore just increase the partition size for my root(/) to allow for some installation in /opt.
No, you need not. After you create (symbolic) link from /opt to /usr/local f.E. , all file operations to /opt will "transparently" write to /usr/local.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.