Thanks Ross/Ed, yes we're going to dump the custom Windows app and use an open source solution using Samba's file share capability (with Samba running on OBSD of course :).
--- On Fri, 5/22/09, Ross Cameron <abal...@gmail.com> wrote: > From: Ross Cameron <abal...@gmail.com> > Subject: Re: OpenBSD ESXi VMware image on Soekris Net5501 > To: "Ed Ahlsen-Girard" <eagir...@cox.net> > Cc: misc@openbsd.org > Date: Friday, May 22, 2009, 9:05 AM > On Fri, May 22, 2009 at 5:56 PM, Ed > Ahlsen-Girard <eagir...@cox.net> > wrote: > > > On 2009-05-22 Ross Cameron wrote: > > > > > Certainly the hardware chosen isnt anywhere NEAR > potent enough,... and > > u're > > > leaving ure whole configuration open for attack > via the ESXi sub layer. > > > > > > Why not just port the custom app to OpenBSD and > run the configuration > > > natively on the hardware? > > > > There are apps on Windows for which "porting" to > OpenBSD would be roughly > > equivalent to "porting" to NetWare Virtual Loadable > Module. > > > > Maybe he doesn't mind doing it all over from scratch, > but that's about what > > it > > might turn out to be. > > > True but then again I generally find that rewriting and > targeting the code > for portability and re-use is worth the efforts in the long > run. > > Painting you're self into a corner with regards to coding > standards/languages/host OS are generally just a headache > waiting to happen > in the years to come.
