On Sat, Nov 11, 2006 at 09:00:09AM +0100, Petric Frank wrote > I made a test install on a VMware Server installation (Host: AMD64 + Gentoo > 2006.1). I created a VM (OS type other). Then i exit the console, changed in > the *.vmx file the key "guestOS" to guestOS="os2experimental" and start the > installation of OS/2 Warp 4 (german) from CD. Somewhere in between i got two > SYS... messages. After a reboot the install completes and seems to be ok now.
Before I go ahead, a few more questions... 1) I have to allow a couple of ~x86 packages in package.keywords first (yes, I did an "emerge --sync"). Is this expected? =app-emulation/vmware-server-1.0.1.29996-r4 ~x86 =app-emulation/vmware-modules-1.0.0.15-r1 ~x86 2) I notice that sys-libs/pam is loaded as a dependancy. I don't mind the file sitting there, being used by vmware. Does it just affect vmware? If pam kicks in for other programs, it's a showstopper for me. [m3000][root][~] emerge --ask vmware-server These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] app-emulation/vmware-modules-1.0.0.15-r1 [ebuild N ] sys-apps/xinetd-2.3.14 USE="-perl -tcpd" [ebuild N ] sys-libs/pam-0.78-r3 USE="-berkdb -nis -pam_chroot -pam_console -pam_timestamp -pwdb (-selinux)" [ebuild N ] app-emulation/vmware-server-1.0.1.29996-r4 Would you like to merge these packages? [Yes/No] no 3) My current OS/2 machine is an old PII with a 3.2 gig harddrive. Can I short-circuit the install by copying the working OS/2 system to an empty VM? Think of it as a "stage 3 install for OS/2" <g>. -- Walter Dnes <[EMAIL PROTECTED]> In linux /sbin/init is Job #1 My musings on technology and security at http://techsec.blog.ca -- [email protected] mailing list
