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.
Yeh the first time I did it, it was kinda rough, but the second time was way easy and been running ever since, I run Fedora(for Nagios) and FreeBSD(DNS, MySQL replication etc) within it.
Back to the question(sorry OP not trying to steal thread) I asked at the beggining of this thread, why the any to any patch... I run a very new kernel > 2.6.15 usually and never had issues. Just asking...don't know if there is someting I am missing err.
@Chuck56 When you reboot, do you have to rerun vmware-config.pl or? I can't seem to have vmmon and the devices load, although they are present... just asking.
You need an any-any update if your running a new kernel. 2.6.15 is hardly new. vmware craps out when trying to build the modules if your running 2.6.20 or 2.6.21... Thus the any-any update fixes this.
When you reboot, do you have to rerun vmware-config.pl or? I can't seem to have vmmon and the devices load, although they are present... just asking.
That happened to me on a couple of my early installs. It doesn't happen anymore. I don't remember the specific fix but my notes around that time had me focused on PAM by creating links to the VMWare PAM files ( pam_unix_acct.so & pam_unix_auth ) after adding the directory /lib/security. It also may have been the way I set up the init.d directories under rc.d instead of directly under etc.
and also I left the init.d files in UNTIL After I got it running. Securities I had a tough time with as I connect from other machines and outside of my network but I have it working =D -- Works after reboot too.
the above script looks promising too.
(I think I have all my steps documented if interested.)
@Micah If you want to post your steps that would be cool, I have vmware working just have to rerun configure after every reboot(which thankfully is not often), but I think with what you and Chuck56 have said it is a pam issue, I can figure it out over the long weekend.
I followed this guide the last time I set it up.
Sorry to repost to a couple week old thread. I had a chance to reconfigure vmware server on my desktop and this time, did everything under /etc/rc.d and this fixed the problem of needing to recompile after reboot.
I also had a chance to upgrade the kernel to 2.6.21 and indeed needed to run the any-to-any patch.
I know we did, thats why I asked why it was being covered again.
I simply added to the post what I did to fix recompiles after reboots, and reiterated what you said about the any to any patch.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.