glad it worked for you. but you shouldn't have to edit /etc/network/interfaces.

what probably happened is that, once you start the appliance for the first time, it generates a new eth because the rules.d hasn't changed yet. if you just remark the line with eth0, the new eth1 line will still be in there. so a reboot doesn't help because it'll still have the eth1 line. if you edit the interfaces file, changing eth0 to eth1 will work but you'll end up with a eth1.

the way to go is to not only put a # in front of the eth0 lines in the file in /etc/udev/rules.d but in front of all of them. now if you reboot it'll generate a new eth and since it has no rules yet, it'll be eth0.

this appliance is different in the fact that i removed all audio and multimedia related applications and some others that nobody needs in a virtual appliance. also, the harddisk has been repackaged and with some smart disk and filejuggling, manually defragmented. so instead of a default install and application removal which would leave you with a 300mb zipfile, this one is only 70mb.

as for canonical, i think they only add payed support to ubuntu and some tools to manage multiple servers at the same time. no specific appliance or jeos stuff.

the whole purpose of creating the jeos appliance for me was to have a solid base to create other appliances on. i created several appliances on this one (like the Hasslefree download appliance). at the moment i'm working on a pure esx deployment appliance that we use at my company to role out esx servers by the 100s. i think i'll post that on the here some day soon, it's very intuitive and quick to setup and has built in script-building features which would probably help a lot of people setting up their environment in no time at all.

i know about the virtualappliances.net site. tested some of the appliances too. didn't check the forum yet but i think i'll have a look.

funny sidenote; i host http://virtualappliances.eu. no relation to their site