Hi William! Good to hear your enthousiastic about the project! I've not been doing a lot of developing lately, but I'm in the process of going over all the different OS-es and see if they (st...
See more...
Hi William! Good to hear your enthousiastic about the project! I've not been doing a lot of developing lately, but I'm in the process of going over all the different OS-es and see if they (still) work. While I'm doing that I'm trying to see if I can get new releases of Fedora, Ubuntu, Redhat etc. to work. Answers to your questions: 1. To be honest I have not tried the ova version, the vmdk should work, at least it does on my workstation. 2. Please keep sharing your findings! I did not get around checking out new versions of clonezilla etc. I see you did and thanks for the tips! I'll see if I can put together an update soon. 3. Please let me know how you made it work e.g. * Which CD/dvd image you downloaded * what kernel and initrd you imported, where they are on the cd/dvd * the kernel commandline you've been using * How you told the kernel where to look on the network for the live files 4. The Storage->Add is for adding extra (external) iso stores that work with NFS or Windows shares (they should not only have full control on the share level, but also on the file level b the way. And If that does not work try giving 'everyone' 'Full Control' on bothe the files and the share). As for the /local share: If you startup UDA for the first time you'll have a very small /local share. I won't be of much use, since it's only a few Mb and will not hold a full ISO of any OS... You can expand it by: * Turning off UDA * Adding an extra virtual SCSI disk * Starting up UDA * System->Diskspace * Choose /local and hit 'Expand' * Choose the disk you just added and hit Apply Now /local is expanded with the disksize you just added. That is how it should work but from you comments I guess it doesn't.. Can you check out the Systems->Actions and see if you can find the expand action there and send me the results? I read you've found a workaround, so if you want to stick with that, just go with it... You're right about the tftpd not following symlinks. I've been running into the same problem over and over again... I've found though that it does go into directories that are mountpoints themselves, so you will be able to mount an iso file in there (e.g. on /var/public/tftproot/testcd ) an publish the contents over tftp in that way. 5. The problem you are describing sound like you've been facing a full system disk, so that some files were not able to save properly. I'm afraid I have no solution for that. I do hope you've made some snapshots of the UDA before the probems started... You can expand the system filesystem the same way you did with the /local filesystem, just choose system instead of local before you hit Expand.. 6. UBCD4WIN I've never tried, personally I would try to get it to work by just booting the ISO from memory. That is possible in newer releases from pxelinux (it will load the ISO into memory over tftp, mount it as a CD and boot from there), but I have not looked into that very good yet... Bartpe is a whole different story. I tried to get it to work, but it does not seem to work very good in most cases. Some things to keep in mind: * Create a bartpe iso using the bartpe tools you can find on the internet. Those tools ask you to supply it with a windows installation CD. Feed it a win2k3 install CD (I use a vanilla, so no SP1/2/3, never tested it with those since I do not have them...). * When that is done, Feed both the BARTPE.ISO (filename must be uppercase, see release notes...) and the win2k3.iso to the uda during the import bartpe os (they have to be in the same directory to be able to select them both at the same time...) Use the same windows 2003 install CD you've used to create the bartpe CD. * Then don't forget to create a template for that OS (flavor).... * These day I'm not sure lots of people are still using BartPE, I guess the recent WinPE distributions give you actually microsoft supported tools to get the same thing working.... Actually the WinPE stuff is on each windows 7/2008 DVD in boot.wim. If you import a windows7 DVD and create a template on top of it, you'll end up with a WINPE configuration over PXE that will start an installation of Windows7. You can of course replace the winpe.wim the UDA built with another winpe.wim you've built with the WAIK or with the tools at reboot.pro. Let me know if you have more questions! Carl