:Hi!
:I'm the GSoC student doing the amd64 port.
:About the status of my project: I'm so much behind schedule, that I'd
:better not think about it.
:As is just natural, instead of reinventing the wheel, while doing my
:project, I can borrow a lot of code from FreeBSD.
:I'd like to here your advice on the following:
:1) which FreeBSD code can be reused
:2) which FreeBSD code should be reused
:3) which FreeBSD code should *not* be reused, i.e. it's better if
:DragonFly gets some from-scratch implementation, rather than using
:FreeBSD code
Well, a lot of code can certainly be borrowed, but almost none of it
will be a drop-in replacement.
What I recommend you do is not worry about doing a full port and instead
just make a big dent by getting the boot sequence to bootstrap into a
64-bit built DragonFly kernel. Even if you can't get it much past that
it would be progress. Just getting it to boot that far is probably
a big job unto itself.
-Matt
Matthew Dillon
<dillon@backplane.com>| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| James Bottomley | Re: Announce: Linux-next (Or Andrew's dream :-)) |
| Trent Piepho | Re: [PATCH] fakephp: Allocate PCI resources before adding the device |
| Antonio Almeida | HTB accuracy for high speed |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
git: | |
