Mepis is 'live', fogie. Just boot the cd and run the tests you want. Won't write a darn thing to your hd. I do it all the time myself (Gasp! Me, running Mepis? Yes. Me installing mepis to my harddrive is No...But it does have SOME tools that I use rarely, and rather than compile/install/test/debug them, I just put my Mepis cd in and boot it...

Hi all,

@cw...you know that didn't occur to me that's right, it's a live cd and would have done it for me...LOL I'm such a spaz at times

Anyway, I found the web-site for memtest and downloaded there latest/greatest and I actually figured out how to get it to be part of my lilo so now when I boot up, I'm like mepis and can run the test So it wasnt' for naught.

Well I got one error after about 40 minutes. So I dropped my clock speed down then got 200 errors in 5 minutes ROFL.

Then I slowed down my memory timings a little and it ran for 2 hrs and no errors now. I changed from 2.5,3,3,6 to 2.5,3,3,7 and that did the trick.

Surprisingly, sandra, prime95 and a few others show no errrors with the original memory timings.

But I still get error's in my qemu if I enable userspace and kernel acceleration. I can only do userspace kqemu acceleration.

Maybe? and I don't know, I configured the kqemu with my fstab for "defaults" for memory, later to tell it to use "size=528M" but when I boot up, even with the "size=528M" in my fstab I get a message on screen stating"

maybe i'm trying to allocated too much of my 1024 memory total to kqemu?

UPDATE: vista using qemu

I was able to clear enough disk space to make a .img large enough for my experimental vista beta2 install via qemu. All files copied, but near the end of the "expanding files" (or some such nonsense) process I was greeted with a Blue Screen O Death annoucing an unknown hard error. Go figure... So much for my curiosity. I did find a forum dedicated to qemu, and some people claim to have successfully installed vista on a MacOSX box using qemu.
There is some good information on that site. If anyone is interested look here: http://qemu.dad-answers.com/

Thanks all.

Hi all,

I got the vmware server to install, Wow this has been an excercise in patience for me, but I got it. I'm new so it was tuff.

I'm reading the documentation here, and I dont see how you add usb support for windows clients.

I didnt install windows yet, as I'm still trying to figure that part out, and from what I read it takes a long time, so I want to do my research before I give it a go here. But as part of my research I dont see what if anything I have to do for usb. Is the usb automatically added?

First you must add a virtual machine and choose your Windows version, etc. Then after it's added click 'Edit virtual machine settings' then a new window will pop, there will be an 'Add' button there, and choose 'USB Controller'. After you do this (pressuming you have Windows installed), to connect a USB Device to a virtual machine, first power on the virtual machine and then select the device in the VM -> Removable Devices -> USB Devices menu. It's quite simple, and you shouldn't have any problems with anything, really. Good luck to you.

Thank you nykey I made a note of that for myself to do.

I have some questions for you gent's about network security with this vmware/qemu virtualizations.

1. I noticed that a default install of Slackware as a guest OS (so I assume other guests could too) in qemu can contact the internet using protocols that are turned off in my IP tables for the host. Does this sound right?

2. Alien Bob gave us this link here for installation of PAM on slackware:

http://danieldekok.blogspot.com/2006...are-linux.html

The gpg key that I'm supposed to use is from the kernel.org admin correct?

3. At the link for Pam, the writer mentions that

What exactly does he mean to tighten up permissions for PAM? Do you gent's maybe have a link or something discussing any issues?

4. I followed the guide at this how-to guide to install the vmware that nykey posted:

http://www.cs.ucr.edu/%7Ejbyrne/vmware.htm

The writer mentions:

Does that mean that vmware 'runs' as root? Is that why he makes a group for vmware? Does this tie into my Pam question like above. The group add is that done simply by adding the word "vmware" with any number you pull out of the sky and then add your user names to it?

5. This is kind of inline with my question 1 above, vmware, even with no host setup on my system, setsup a network bridge. Already, my firewall is dropping packets like crazy, as it should, but again, I'm concerned about it contacting the internet.

Honestly I don't want any of my guest OS's to contact the internet at ALL. I do however want them to be able to see only one other pc's on the lan becuase these virtual operating systems cant read/write to the host OS, so I need a place to throw files around as I use the guests.

I guess I have to install a firewall &/or antivirus for guest OS's. Is that correct.

Sorry this is long but I'm trying to be descriptive enough so as not to waste anyone's time or mis-understanding.

Any of you guys figure out how to install Slackware 10.2 into vmware?

I can install SuSe and Mepis but not my beloved slackware.

I chose for linux type, "2.4" and also "other linux" but slackware doesn't see any partitions for me to install on.

Any ideas? TY.

Ok now I'm really confused, 2 + days on this Pam thingie here

All pam is configured for, that I can see as a result of that guys guide, is that vmware is the only program configured for pam, but my actual system is not!

I dont think the PAM actually does anything here.

Here's what I did:

In the /etc/pam.d directory, the only file that goes there is "vmware-authd"; and no "chfn" "chsh" "login" "other" "passwd" "su" "xlock" according to many guides.

There is no pam.conf at all on the system when you install pam.

No binaries, rc.pam? I don't know.

LSMOD shows nothing pam related.

In fact, I edited this '/etc/pam.d/vmware-authd' file and deleted everything and typed "hello fogie" and saved, rebooted and vmware works still works.

So it appears to me is that the guide helped me to fool vmware that I had a working Pam and that's all.

So off, to play with suse and see how they do it.

Well, I can't help you with the pam issue because I'm not sure of what it is/does myself. But I can assure you that Slackware 10.2 (or any other version) works in VMware. I've installed Slack in VM using the 2.4 kernel, the 2.6 kernel, the scsi.s (2.4 with scsi support) kernel, and many more OS's and they all worked from the first try, right now I'm testing CentOS and Gnome/KDE moves prettty neet . So, you say that your install isn't seeing your virtual drive or doesn't see your partitions after you made them ? Are you using the SCSI or IDE disk option ?

oh I didnt try the scsi kernel, maybe that's why?

I just tried the bare.i kernel and it didnt see the drive at all, I'll give that a shot.

Regarding Pam. I just get nervous when I see experienced people such as the blogger there saying that stuff is going to have to be secured. I don't know my backside from a hole in the ground here in linux and security and a comment like his scares the stuff out of me LOL.

Well, it depends what option you choosed when you added the Virtual Machine into VMware. When you create your virtual drive ( I think only if you choose Custom setup) you'll have 2 options, one is IDE and second is SCSI (recommended). If you choose IDE then use bare.i if you choose SCSI use the scsi.s . If you didn't choose Custom when adding the Virtual Machine , then the virtual hard drive is added as SCSI (I think!). It should work one way or another.

Hi nykey,

Yes that worked using the scsi.s kernel.

Now I just get kernel panic LOL.

I get confused on pat's installer to be honest for anything other than using the bare.i kernel becuase of the confusing (to me at least) prompt after you do full noobie install. He prompts you for your kernel choice and mentions bare.i, and I got no clue what to do here or for scsi for lilo to be honest. It's my own in-experience to blame. I'm just going to run qemu for slackware then; and use the vmware for other distro's that guide me thru the scsi. I really can't afford to tie my machine up for 2 hrs right now when qemu runs slackware with the kqemu accelerator perfectly for slackware. Hopefully the kqemu will have some tweaks to let me run some other distro's with the accelerator. My gentoo and suse die with kqemu, but not slackware. Wierd.

there's nothing special to be done. just use the scsi.s kernel at boot prompt, then proceed to installing slackware as usual, when it ask's you to choose kernel, choose cdrom option and then scsi.s again, afterwards its exactly the same as using bare.i, test26.s, etc... you'll only have to add /dev/sdaX into liloconfig instead of /dev/hdaX which is for IDE.

Hi.
I've installed both qemu and kqemu package of Alien Bob for Slackware 11, default 2.4 kernel. And get the following error each time I run the program :
Here the output of ls -l /dev/kqemu

Just tested this on a windows file image I use under Xen, and it works fine.

What I did, is:

# dd if=/dev/zero of=zeroes bs=1M count=2048
# cat winxp.img zeroes > newxp.img

Then edited the xen config file, so that newxp.img is seen as a second disk.
Booted winxp and checked disk manager in windows to validate that a drive D is present which has 2G unused space.

Then used Microsoft KB article 325590, which describes the DISKPART.EXE tool, to increase the D: drive to use full partition

shutdown and restarted windows DomU:

# xm shutdown winxp
# mv winxp.img winxp_old.img
# mv newxp.img winxp.img
# xm create winxp

All worked fine.

Andre