README.SLACKWARE from Slackbuilds nowhere to be seen.
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.
README.SLACKWARE from Slackbuilds nowhere to be seen.
Hi: This Slackbuild package suggests reading README.SLACKWARE. But that file is nowhere to be seen in the package. What should I do?
I found a file by that name googling with the filename and the package name as search string but would prefer accessing the file from within Slackbuilds or said package itself.
Well thanks! The individual files linked to below, of course. But I anyways, sorry for having rushed to post, discovered the file within a tarball. I know I'll do a thousand questions in the process of this compilation and wouldn't want to start as many threads. So, as far as it's possible, I'll stick to this one.
First question: is it worthwhile to do the entire build in /root. While for the installation final step I can do sudo root, or 'su -', slackbuilds, for some of his packages, ask for an environment identical to that of root, and so one of their hints, for that special case (do not remember the package name), is to compile being plain root, that is, in root's directory. I repeat, this is an exceptional case and I've only seen it for only one of their packages.
But my question is different. Somewhere in the VirtualBox site, I read that one should _compile_ as root this piece of software. But I am not quite sure. Hence: is it worthwhile to compile Virtualbox straight in /root? Of course, and the rest of the build.
I might not have the best english in the world and I not bashing yours but excluding your final sentence I didn't understand a thing. Anyways, all SlackBuilds found on SlackBuilds.org are meant to be run as root.
stf92, you are listed on linuxquestions.org as a "senior member" with thousands of posts. And you want to have us believe that you have never before used one of the scripts at SlackBuilds.org? It could be true, but in that case why not read the fine manual first? We are not here to hold your hand, the documentation is written for a reasdon:
Eric, I don't know why I'm so explicit in my posts when it seems some people does not bother to read them. Please listen: I've used many a Slackbuilds script, true. Also true, I've meticulously read the instructions from the first of them I downloaded (the very first was mplayer I think) and they performed well, though mplayer itself might be (past tense) an exception, understandable in such a complex, almost monstrous program. So your admonition does not properly apply to me!
That said, I already know several posts are coming to support you and spoil the thread. Again, please listen: I am not necessarily aiming at you with this remark.
su documentation doesn't talk about it (or perhaps I didn't find it) but what is the difference between "su -" and "su -l"?
It's in the man page:
Code:
OPTIONS
The options which apply to the su command are:
-, -l, --login
Provide an environment similar to what the user would expect had the user logged in directly.
When - is used, it must be specified as the last su option. The other forms (-l and --login) do
not have this restriction.
OPTIONS
The options which apply to the su command are:
-, -l, --login
Provide an environment similar to what the user would expect had the user logged in directly.
When - is used, it must be specified as the last su option. The other forms (-l and --login) do
not have this restriction.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.