Subject: Re: Device minor numbers conversion in COMPAT_NETBSD32
To: Quentin Garnier <cube@cubidou.net>
From: David Laight <david@l8s.co.uk>
List: tech-kern
Date: 01/05/2006 20:53:13
On Wed, Jan 04, 2006 at 11:46:35AM +0100, Quentin Garnier wrote:
> > 
> > Have a mount option that specifies how to interpret (or "emulate") 
> > device numbers. Then each kernel can map the device numbers to his 
> > internal representation. So an i386 kernel can map amd64 dev entries
> > and vice versa. And an i386 kernel (or amd64) could map linux i*86 
> > device numbers to its internal representation and all I'd have to
> > do to run an existing linux installation under emulation is to specify
> > a mount option for the linux partition with the dev entries.
> 
> I like that idea.  That would indeed answer the question of what
> processes intend to see.  David's idea solves the numbering issues for
> netbsd32 in 4.0, and under COMPAT_30, COMPAT_NETBSD32 would use
> Joachim's idea for proper work...

Or just write devfs ... Even if it generates major/minor numbers (which
it probably has to), the kernel generates the numbers.

Or do you want to be anly to run the i386 MAKEDEV on an amd64 kernel...

	David

-- 
David Laight: david@l8s.co.uk