LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 03-16-2014, 02:30 PM   #1
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 3,268

Rep: Reputation: 49
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.
 
Old 03-16-2014, 02:35 PM   #2
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,902

Rep: Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963
Umm ... perhaps the site has since been updated but slackbuilds.org/repository/14.0/system/virtualbox/ links directly to README.SLACKWARE
 
Old 03-16-2014, 02:37 PM   #3
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,902

Rep: Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963
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
 
Old 03-16-2014, 02:38 PM   #4
XavierP
Moderator
 
Registered: Nov 2002
Location: Kent, England
Distribution: Lubuntu
Posts: 19,176
Blog Entries: 4

Rep: Reputation: 430Reputation: 430Reputation: 430Reputation: 430Reputation: 430
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?
 
Old 03-16-2014, 02:46 PM   #5
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,902

Rep: Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963
Quote:
Originally Posted by ruario View Post
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.
 
Old 03-16-2014, 02:49 PM   #6
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 3,268

Original Poster
Rep: Reputation: 49
@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.

Last edited by stf92; 03-16-2014 at 02:51 PM.
 
Old 03-16-2014, 04:00 PM   #7
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,380

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

Eric
 
2 members found this post helpful.
Old 03-16-2014, 04:18 PM   #8
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 3,268

Original Poster
Rep: Reputation: 49
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.

Last edited by stf92; 03-16-2014 at 04:22 PM.
 
Old 03-16-2014, 04:46 PM   #9
moisespedro
Senior Member
 
Registered: Nov 2013
Location: Brazil
Distribution: Slackware
Posts: 1,139

Rep: Reputation: 151Reputation: 151
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.
 
1 members found this post helpful.
Old 03-16-2014, 05:04 PM   #10
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 3,268

Original Poster
Rep: Reputation: 49
A short answer for a long question. But categorical. Thanks.
 
Old 03-16-2014, 05:30 PM   #11
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,380

Rep: Reputation: Disabled
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
 
1 members found this post helpful.
Old 03-16-2014, 06:26 PM   #12
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 3,268

Original Poster
Rep: Reputation: 49
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.

Last edited by stf92; 03-16-2014 at 06:33 PM.
 
Old 03-16-2014, 06:28 PM   #13
moisespedro
Senior Member
 
Registered: Nov 2013
Location: Brazil
Distribution: Slackware
Posts: 1,139

Rep: Reputation: 151Reputation: 151
su documentation doesn't talk about it (or perhaps I didn't find it) but what is the difference between "su -" and "su -l"?
 
Old 03-16-2014, 07:27 PM   #14
BroX
Member
 
Registered: Oct 2003
Location: Sweden
Distribution: Slackware64-current
Posts: 759

Rep: Reputation: 65
Quote:
Originally Posted by moisespedro View Post
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.
 
Old 03-16-2014, 08:41 PM   #15
moisespedro
Senior Member
 
Registered: Nov 2013
Location: Brazil
Distribution: Slackware
Posts: 1,139

Rep: Reputation: 151Reputation: 151
Quote:
Originally Posted by BroX View Post
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
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Suggested update to README.initrd in Slackware 14 mrascii Slackware 22 08-30-2012 02:25 PM
Slackbuilds for slackware 13.37 not working..... honeybadger Slackware 7 06-22-2012 02:54 PM
[SOLVED] Slackware 13 on slackbuilds hua Slackware 14 01-26-2010 02:13 PM
Webmin on Slackware -- w or w/o Slackbuilds GaHillBilly Slackware 1 10-27-2009 04:23 PM


All times are GMT -5. The time now is 09:45 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration