![](https://seccdn.libravatar.org/avatar/1a9af646da2d1aa9023e5dfbb7cd574d.jpg?s=120&d=mm&r=g)
On Monday 23 October 2006 12:22 pm, George Stoianov wrote:
I have already fund the answer thanks to Kevin from VMware. Their forum is really good. Solution link: http://www.vmware.com/community/thread.jspa? threadID=58126&messageID=494371#494371. ^ Beware of line-wrap ^
... then I looked inside "/etc/init.d/init.d" as I thought there is usually only one???
Ah Hah. One-eyed RedHat RPMs strike again. That's RH's init.d setup, happens to me every time I install slimserver for my squeezeboxes. Just look in "/etc/init.d/init.d" and reef anything useful back in to "/etc/init.d". Test your startup and delete the unwanted inner init.d The startup script you were given is probably just as RedHat centric. Have a look at a standard SuSE one and re-model it, adding the active runlevel comment block and using SuSE's better preloads. VMware used to work well out-of-the-box. Have they gone backwards? michaelj -- Michael James michael.james@csiro.au System Administrator voice: 02 6246 5040 CSIRO Bioinformatics Facility fax: 02 6246 5166 No matter how much you pay for software, you always get less than you hoped. Unless you pay nothing, then you get more.