linux emulation

[Zane C.B.]

On Thu, 20 Mar 2008 19:52:14 +1000
Da Rock <rock_on_the_web at comcen.com.au> wrote:

> 
> > On 20/03/2008, Da Rock <rock_on_the_web at comcen.com.au> wrote:
> > >
> > >  On Thu, 2008-03-20 at 08:50 +0100, Wojciech Puchar wrote:
> > >  > > I've read the handbook and just about anything on linux
> > >  > > compat under freebsd. I am particularly interested in
> > >  > > drivers under linux compat.
> > >  >
> > >  > emulation allows execution of normal linux programs, not
> > >  > drivers
> > >
> > >
> > > Ok. So input devices won't work either? I refer to this page
> > > here:
> > > http://people.freebsd.org/~3d/apps/games/unreal_tournament/
> > >
> > >  What is the driver mentioned here?
> > >
> > >  Incidentally, what is the difference between linux and bsd
> > > drivers? The drivers in question are manufacturers binaries for
> > > linux in an RPM; hence the question. Plus I came across several
> > > notations regarding building or using drivers from linux in bsd
> > > (linux-kmod-compat port, the above link, and more).
> > >
> > >  For reference I'm merely very curious, not argumentative on
> > > this. Cheers for any answers offered.
> > >
> 
> 
> On Thu, 2008-03-20 at 02:14 -0700, Patrick C wrote:
> > A binary is compiled assembly/code. The binary still needs to
> > interact with low-level hardware using system calls, handling
> > interrupts, etc. in a way that the operating system understands.
> > Applications are more portable and less operating- and
> > hardware-specific than drivers, which require a good
> > understanding of the operating system and the hardware.
> > 
> > Please read the current status of linux-kmod-compat, it
> > specifically indicates it is for USB drivers. USB is a simplified
> > bus where the low-level access is handled in the same manner for
> > every device so it's simpler to port the driver.
> > 
> > Glide in your case is an API/Library, not an actual driver.
> > Libraries are very similar to applications in how they act with
> > the operating system/environment, and are a must-have on running
> > Linux binaries. This is supported and works well.
> > 
> > -Patrick
> > 
> 
> Ok, got that. I read that about the linux-kmod-compat, but I thought
> that it might have been the beginning of something beautiful (pardon
> poetics...). I was unaware of the glide situation though.

I though glide has been long since past usefulness given the cards it
was for no longer are effectively around outside ebay and peoples
hardware drawers.

I regards to running UT on FreeBSD it runs nicely, other than it
requires a hackish manner to install 2007 if you have it on CD.

> Does anyone know what the differences are between linux and bsd at
> the system calls, interrupts, etc? I understand that there are some
> software which accesses hardware at this sort of level which has
> been adapted as well (raid controllers mainly), so surely there
> must be some information on what can enable this to work.
> 
> What this discussion has got me thinking on is a "wrapper" (ie
> NDIS), since the drivers are not from the linux oss community but
> from the actual manufacturer I'm assuming (forgive me,
> please... :) ) that this may be a feasible solution. In which case,
> then, I'm going to have to "map" calls and create device nodes.
> Should be simple then, no? ;P!
> 
> I'd love to hear any more suggestions or links to info on any of
> this, thanks guys.
> 
> Also, on the linux compat- am I correct in my observation that you
> have to actually chroot to enable the running of a linux binary?
> Enter the file structure of the linux compat? Or can you just run
> it?