Hello!
Is the "VMware server 1.0 version " available somewhere? http://virtualappliances.eu/DLappliance-VS.zip is "404 compatible", so to say
Or does the "Regular Download v1.01 " work with VMware Server 1.04 on Linux?
BTW: If you're short on space/bandwith, how about hosting stuff on S3 from Amazon ? This way, you'd also have Torrents available directly.
Cheers,
Alexander
i took the vmware server 1.0 version (-VS) offline due to quota restrictions. i'm trying to get more space and once i do i'll update the 1.01 version for VS too. if you can't wait you can try running the regular version in vmware player, there's a post on http://communities.vmware.com/thread/120228 (somewhere in the middle of the messages) to describing how to fix the appliance for VS. only the downloads with -VS in them will work on vmware server.
as for amazon, from the bandwidth i used last month i calculated what i'd have to pay them. it came to some 1400 dollars a month to host these things. i'm a big fan of sharing but there's nobody on the internet i love enough to pay that kind of money every month
in the 1.00 i accidentally removed the mac address from the .vmx file. so when you start the appliance for the first time it'll generate a new one. this will leave you with eth1 in linux. easiest way to fix it is to edit /etc/network/interfaces and change all eth0 to eth1 in there. type '/etc/init.d/networking restart' and it should work. in the 1.01 you shouldn't have this issue.
it's still on my wishlist (somewhere down the bottom unfortunately) to find the setting that will tell linux not to mind the mac address when assigning network cards and just use the first one it finds as eth0. if anybody knows, let me know
it won't start if the share is not configured correctly but it should startup at boot after that. but if it doesn't, you could type 'update-rc.d hellanzb defaults' anyway
glad it works for you
if you have any suggestion, don't hesitate to post them here
if you have network problems it's because your host generated a new mac address. default behavior these days in linux is that it will generate a new ethernet device (ie. eth1) which is not setup in /etc/network interfaces.
all you have to do to have linux stop doing this, is to just put a # in front of the eth0 line in /etc/udev/rules.d/70-persistent-net.rules. now if you reboot with a new mac address it will just call it eth0 again. for virtual appliances, that's exactly what we want
all you have to do to have linux stop doing this, is to just put a # in front of the eth0 line in /etc/udev/rules.d/70-persistent-net.rules. now if you reboot with a new mac address it will just call it eth0 again. for virtual appliances, that's exactly what we want
Hello!
looks like a great appliance that you have here but could you upload it somewhere that we can download and try it?
I've been trying the link you provided but the domain is disabled!
rapidshare.com , megaupload.com , ... plenty of choice
Thank you!
picodon