README.SLACKWARE from Slackbuilds nowhere to be seen.

stf92 · 03-16-2014, 02:30 PM

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.

ruario · 03-16-2014, 02:35 PM

Umm ... perhaps the site has since been updated but slackbuilds.org/repository/14.0/system/virtualbox/ links directly to README.SLACKWARE

ruario · 03-16-2014, 02:37 PM

Also, the file is in the SlackBuild package:

Code:

$ wget -qO- http://slackbuilds.org/slackbuilds/14.0/system/virtualbox.tar.gz | tar zt | grep README.SLACKWARE
virtualbox/README.SLACKWARE

XavierP · 03-16-2014, 02:38 PM

Reading down the page you linked to gave this: http://slackbuilds.org/slackbuilds/1...ADME.SLACKWARE

And that page gives this:

Quote:

You'll need to add the following lines to /etc/rc.d/rc.local:

# Start vboxdrv
if [ -x /etc/rc.d/rc.vboxdrv ]; then
/etc/rc.d/rc.vboxdrv start
fi

This will load the support kernel module for VirtualBox.

You'll then need to add the following lines to /etc/rc.d/rc.local_shutdown:

# Stop vboxdrv
if [ -x /etc/rc.d/rc.vboxdrv ]; then
/etc/rc.d/rc.vboxdrv stop
fi

Any user accounts that plan to use virtualbox will need to be members
of the "vboxusers" group.

In order to use USB devices in VirtualBox Guests you may have to restart
your host system after installing the virtualbox package.

It's headed Individual Files and called README.SLACKWARE. Is this what you meant?

ruario · 03-16-2014, 02:46 PM

Quote:

Originally Posted by ruario

Umm ... perhaps the site has since been updated ...

Nope, the SlackBuild (virtualbox.tar.gz) has not been updated:

Code:

$ curl -sI http://slackbuilds.org/slackbuilds/14.0/system/virtualbox.tar.gz | grep Last-Modified
Last-Modified: Sat, 12 Oct 2013 19:49:29 GMT

Looks like you just missed it somehow.

stf92 · 03-16-2014, 02:49 PM

@XavierP:

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.

Alien Bob · 03-16-2014, 04:00 PM

You should not have to ask a thousand questions here if you first did your homework...

Eric

stf92 · 03-16-2014, 04:18 PM

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.

moisespedro · 03-16-2014, 04:46 PM

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 · 03-16-2014, 05:04 PM

A short answer for a long question. But categorical. Thanks.

Alien Bob · 03-16-2014, 05:30 PM

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:

http://slackbuilds.org/howto/

Eric

stf92 · 03-16-2014, 06:26 PM

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.

moisespedro · 03-16-2014, 06:28 PM

su documentation doesn't talk about it (or perhaps I didn't find it) but what is the difference between "su -" and "su -l"?

BroX · 03-16-2014, 07:27 PM

Quote:

Originally Posted by moisespedro

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.

moisespedro · 03-16-2014, 08:41 PM

Quote:

Originally Posted by BroX

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.

Didn't see the "-" lol