On Wed, May 19, 2010 at 6:00 PM, Jens Staal <[email protected]> wrote: > That the kernel API breaks that fast is only important if you want to keep > up with Linus' Linux. Let's say that you find all the drivers you ever would > like to use in version 2.6.35 - then you could basically just use modules > from this release indefinitely. A major update to support newer drivers > would only be done when it was considered needed. I have no idea how the > other OSes who tries to exploit linux drivers are doing it, though. > As for amount of work - probably lots and way over my competence. It was > basically some random musings and I just liked to know how others thought > about them.
That helps narrow things but there's still a huge amount of code that any driver can call out to. That would be a lot to port, and could be impracticable as I'd bet that drivers call out to some pretty Linux-kernel specific subsystems (sysfs, for one, which would not need to be ported to Plan 9.) Yes it would be possible to `stub' all that out, but you would have to make a potentially large framework just for stubs, since preconditions and postconditions of your stub API calls may have to be met to ensure that the drivers continue to function. All in all, pretty damn hard. Linux is a large, complicated, fast-moving code blob. > > > 2010/5/19 Jorden M <[email protected]> >> >> Oh. That's been discussed a bit on 9fans. Generally, the opinion is >> that since Linux breaks the kernel API every 3 months, it would be a >> useless effort. You'd have to provide a hell of a lot, too, since >> Linux drivers don't talk exclusively to something like Apple's >> DeviceKit. >> >> On Wed, May 19, 2010 at 5:43 PM, Jens Staal <[email protected]> wrote: >> > As far as I understood it Linuxemu is a way to run GNU/Linux >> > applications in >> > a virtualized Debian on top of Plan9. The thing I was talking about was >> > rather utilizing Linux (the kernel) for drivers etc like NDISwrapper >> > used to >> > be used to run Windows drivers in Linux until native drivers came along. >> > >> > 2010/5/19 Jorden M <[email protected]> >> >> >> >> It's called Linuxemu. I'm sure the developer would love help. >> >> >> >> On Wed, May 19, 2010 at 5:37 PM, Jens Staal <[email protected]> >> >> wrote: >> >> > [sorry about hijacking] >> >> > Actually I was thinking a bit recently.... what about an "inverse >> >> > glendix"? >> >> > That is, rather than porting Plan9 to Linux, how about porting Linux >> >> > to >> >> > Plan9? >> >> > The thought was basically - would it be possible to make some sort of >> >> > Plan9 >> >> > "NDISwrapper"/"FUSE" for Linux kernel modules for drivers, >> >> > filesystems >> >> > etc >> >> > that could be mounted/run in either Plan9 or Plan9/APE userspace? If >> >> > I >> >> > have >> >> > understood it correctly, this is what L4, Hurd and MINIX tries to do >> >> > to >> >> > get >> >> > good hardware support fast. I am not saying that this in anyway would >> >> > be >> >> > a >> >> > BETTER solution than Glendix, rather a complementary one geared >> >> > towards >> >> > people that are more Plan9 than Linux but still would like to be able >> >> > to >> >> > run >> >> > it on their toaster without writing every driver themselves. >> >> > >> >> > 2010/5/19 EBo <[email protected]> >> >> >> >> >> >> On Wed, 19 May 2010 11:51:44 -0700 (PDT), vh4x0r >> >> >> <[email protected]> wrote: >> >> >> > Hi, I'm interested in contributing to the project for creation of >> >> >> > a >> >> >> > distro based on Glendix and Gentoo. I have acquainted myself with >> >> >> > Glendix, and also have a lot of experience with Gentoo. Can you >> >> >> > please >> >> >> > provide me with some pointers about where to start ? >> >> >> >> >> >> I have an experimental ebuild on sys-kernel/glendix-sources, and >> >> >> some >> >> >> other stuff you can use as a basis to start if it would be at all >> >> >> helpful. >> >> >> For the next while I am focusing on my plan9 work which was accepted >> >> >> for >> >> >> this years GSoC. Some of that work might also be of use to backport >> >> >> to >> >> >> Glendix. >> >> >> >> >> >> EBo -- >> >> >> >> >> >> -- >> >> >> To post to this group, send email to [email protected] >> >> >> To unsubscribe from this group, send email to >> >> >> [email protected] >> >> >> For more options, visit this group at >> >> >> http://groups.google.com/group/glendix?hl=en >> >> > >> >> > -- >> >> > To post to this group, send email to [email protected] >> >> > To unsubscribe from this group, send email to >> >> > [email protected] >> >> > For more options, visit this group at >> >> > http://groups.google.com/group/glendix?hl=en >> >> >> >> -- >> >> To post to this group, send email to [email protected] >> >> To unsubscribe from this group, send email to >> >> [email protected] >> >> For more options, visit this group at >> >> http://groups.google.com/group/glendix?hl=en >> > >> > -- >> > To post to this group, send email to [email protected] >> > To unsubscribe from this group, send email to >> > [email protected] >> > For more options, visit this group at >> > http://groups.google.com/group/glendix?hl=en >> >> -- >> To post to this group, send email to [email protected] >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/glendix?hl=en > > -- > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/glendix?hl=en -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/glendix?hl=en
