SRL Archive - Help and Support

I'm going to be using Debian, I was wondering if there's any fancy things to optimize it while running in wine

I'm building some VM's for people to use, since I have a bit of extra computer power that is always on but doesn't get used

Also any other tips lmk

You can run it in a separate X server. Use tigervnc or another ``Xvnc'' provider.
That way you don't even need to use smart; and it might save drawing (cpu) operations (but I'm not sure).

Something like:

Xvnc :1 # :0 is default display, use +1 for each new Xvnc

# (In another shell)
export DISPLAY=:1
wine Simba.exe # Will start it in the Xvnc session.

Customising Xvnc to use the right resolution isn't really hard, too. Use something like vinagre of vncviewer to view the Xvnc session. (You might need to set a password first with vncpasswd)

Xvnc also works great if you don't have something like SMART at your disposal, or just want to run it in the background where no one can physically see it. (I used it on my University for some time)

To view it remotely, you can do vnc forwarding over ssh.

Another nice trick is the WINEPREFIX environment variable:

mkdir /tmp/test
export WINEPREFIX=/tmp/test
winecfg

Will create a new WINE instance in /tmp/test. I'm not sure if this is useful for you while botting, but I often use it to test Simba installs on a clean ``install''. ;)

Interesting thought, so instead of someone always seeing their bots when connected in, they would only be seeing simba?

I was also thinking of having 1 install that is mounted in the VM's memory whenever a person logs in, using a tmpfs. An easy script to just lets say pull the whole simba install and copy it into some directory while the persons logged in, this would allow a total reset whenever someone uses the VM so no one would ever somehow stumble on someone elses password or something (also it could just be in /tmp and not in memory, but with how small simba is, I figure putting it all in mem wouldn't do much at all)


But to add to my first question, I'm not very familiar with the separate X servers as I usually don't use a GUI when I'm on a linux machine. So it would basically be like


that is one understanding I have of what you said.. with my lack of experience I interpreted it like 3 different ways lol

You should look into http://virt-manager.org/. I used it for a bit in debian for this purpose. Seemed pretty easy to setup and get going.

You can have the VMs running without actually having to be looking at each one. So after you started Simba you Could close the viewer and save on CPU that way I believe. Worth a shot IMHO.

From: grats
Interesting thought, so instead of someone always seeing their bots when connected in, they would only be seeing simba?

Well, no. Simba is started with DISPLAY=:1, and so is SMART, etc. You probably want to launch a window manager for the display, too. I'm just saying it because it's more lightweight that virtualising an entire (or multiple) OS just for a display.

From: grats

I was also thinking of having 1 install that is mounted in the VM's memory whenever a person logs in, using a tmpfs. An easy script to just lets say pull the whole simba install and copy it into some directory while the persons logged in, this would allow a total reset whenever someone uses the VM so no one would ever somehow stumble on someone elses password or something (also it could just be in /tmp and not in memory, but with how small simba is, I figure putting it all in mem wouldn't do much at all)

Well, you could just make the files of each user only accessible to them. A simple chmod should do the trick.

From: grats

But to add to my first question, I'm not very familiar with the separate X servers as I usually don't use a GUI when I'm on a linux machine. So it would basically be like


that is one understanding I have of what you said.. with my lack of experience I interpreted it like 3 different ways lol

Well, if each user has their own account, they can just have their own Xvnc's. As for the picture, they all need their own Xvnc server running. (Just start it three times, with different passwords or something)

Unrelated, it is actually possible to run Simba on a different X server than SMART (or Simba's target), but I haven't added support for this in Simba Linux yet.

@Silent_Spy of course you can. The thing is that with a VM you virtualise an entire OS as well.
Detachable VM with qemu:

qemu-kvm -vnc :1 -enable-kvm <foo.img>

Ah I get what you meant

also I just was meaning like, one simba installation, so whoever updates it, updates it.. and then upon startup they get the recent updated one without having to worry about it.

Although it looks like I'll be having someone who is going to do like 20 accounts on my machines so I won't have much room to let others in for a while :P but I'll definitely be testing the setups etc on machines, maybe set something up at my office so more simbas can be ran without proxies