Date: Wed, 20 Apr 2005 03:43:32 -0000 From: "Ballance, Robert T" <tyler@neo.tamu.edu> To: "Daniel O'Connor" <doconnor@gsoft.com.au>, <freebsd-current@freebsd.org> Subject: Re: New driver loading scheme for Project Evil, need input Message-ID: <200504200343.j3K3hWxH092001@xyzzy-5.tamu.edu> In-Reply-To: <200504201221.39355.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> > You still end up needing the C compiler, objcopy, ndiscvt and (optionally) > > iconv, but the script automates the use of all these tooks and explains > > to the user what's going on while it's working. > > It's certainly simpler than the current state of afairs and unless the kernel > NDIS grows the ability to directly read .sys & .inf files from your disk > (which would be very cool :) it's about a simple as it's going to get.. I think it's small enough as such, given that Project Evil isn't the only thing that needs a C compiler, and iconv...how much does Project Evil require that isn't in the base FreeBSD install anyways? > > - What should the script be called? wintobsd.sh sounds kind of lame. > > encappe > win2elf > pe2elf > exorcist.sh ;) ndisload.sh driverload.sh windriver.sh pureevil.sh >=] -R. Tyler Ballance ..and back to work..
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200504200343.j3K3hWxH092001>