Transition Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About ralphte

  • Rank
  1. Performance is better then you might imagine. Not to give away the spoiler but if configured right it's all most on par with a physical box. Thinks for the heads up on the old Firefox. I will look in to this.
  2. Very nice tutorials, keep up the good work. Is the SMART status working in DSM when you run gnoBoot and Synology DSM 5.0 in ESXi 5.5 with Raw Disk Mapping? Thanks No SMART does not work with Raw Disk Mapping. BUT if you use ESXi pass though with VT-d it does work. Will be doing a video on this as well. Also this might get fixed in a future version of gnoBoot.
  3. I have started posting guides for gnoboot on my site http://www.thedarkcloud.net . I have my first videos posted with hard copy instructions to follow. MANY more guides to come!! Please let me know what you all think Thanks
  4. I have posted a mirror for gnoboot. No ads, login or anything. I will keep this site updated with gnoboot as a mirror. I will also be putting up some how-to's and keeping them up to date. http://thedarkcloud.net/downloads-5/
  5. Well gnoBoot is pretty sweet. Alpha 10 is really good. Turn key on my HP Proliant micro server. Works great with ESXi 5.5 will be posting a guide for setup on ESXi.
  6. Well To do what as been asked I will give mine below. Since I was unable to get alpha9 working at all in ESXi 5.5 the only release that I was able to test was alpha 5. Alpha 9: after installing it would cause a grub error. I tried everything I could and could not fix this. I spent over 6 hours and one upset girl friend and still no luck. The only way to not get the grub error was to install alpha5 Alpha 5: It installed fine but I could not get iSCSI to work. Windows files share worked and where very fast. Did not get to test NFS. This was using version 5 of the DSM. I am hoping th
  7. Could yo send me the alpha 8 update or the link to it. I would like to try what you have done.
  8. I have the fix for this issue will submit here in a few.
  9. I was using windows programs to do it, but they are PIA to get working correctly, so I figured out how to do it in linux. fdisk -l image.img. you'll see it has a partition that starts at sector 63. And that each sector is 512 bytes. so then setup a loop device of the image file starting at that offset (so you can access the partition). Then mount it. delete the old zImage, copy over new one. Sync (not sure if needed - can't hurt?). unmount it. delete the loop device. you now have updated image file I created a little script that does it for me and shows the stats of the old zImage and