On Mon, Nov 29, 1999 at 05:21:36PM -0500, Kurt Kehler wrote:
> I'm trying to install vmware 1.1.2 under Slackware 4.  At one point in the
> install script I am asked:
> 
> "What is the directory under which the init scripts reside (it should
> contain init.d/, and from rc0.d/ to rc6.d/)?"
> 
> And I reply: /etc/rc.d
> 
> Then I'm told: "The path "/etc/rc.d" is a directory which does not contain
> a init.d directory." 
> and: "What is the directory under which the init
> scripts reside (it should contain init.d/, and from rc0.d/ to rc6.d/)?"
> 
> I think that Slackware doesn't have an /etc/init.d directory.  Is it
> possible to fool the VMWare install script into thinking it does, maybe by
> creating /etc/init.d and linking it to point to /etc/rc.d?
> 
> Thanks,
> Kurt Kehler
 The ideas is along the right lines. Slackware uses BSD style startup
 scripts (all?)most other Linux distributions use SYSV style scripts.

 Slackware keeps all it's scripts in /etc/rc.d

 SYSV startup keeps all the scripts in either /etc/rc.d/init.d
 or /etc/init.d, then has a directory for each runlevel, rc0.d through
 rc6.d, and symlinks the appropriate scripts for each runlevel into
 the associated directory.

 Now. To solve the slackware problems try this:
 
 make a directory under /tmp that has seven directories in it.
 i.e.:
        cd /tmp
        mkdir myrcdir
        cd myrcdir
        mkdir init.d rc0.d rc1.d rc2.d rc3.d rc4.d rc5.d rc6.d

 when you go through the VMWare install, tell it to put the scripts
 in /tmp/myrcdir

 then, when the install finishes, 
 
        mv /tmp/myrcdir/init.d/vmware /etc/rc.d

 add 2 lines to /etc/rc.d/rc.local
 which read
 
        #Starting VMWare stuff
        /etc/rc.d/vmware start

 There should be 2 lines in /etc/rc.d/rc.6 that read

        # Try to turn off quota and accounting
        if [ -x /usr/sbin/quotaoff ]

 right before these, add a line that says

        /etc/rc.d/vmare stop


 and I believe it should work ok. Please let me know either
 way.

 Hope this helps

 greg
-- 
this is not here

Reply via email to