From 2a10524a3e0fee1e75adfdab3fba0a76960f98e3 Mon Sep 17 00:00:00 2001
From: ftigeot
Date: Thu, 21 Feb 2013 01:04:00 -0800
Subject: [PATCH] Move pie in the sky projects in a separate list: i386 ABI,
adapt pkgsrc
---
docs/developer/gsocprojectspage/index.mdwn | 74 +++++++++++++++++++-----------
1 file changed, 46 insertions(+), 28 deletions(-)
diff --git a/docs/developer/gsocprojectspage/index.mdwn b/docs/developer/gsocprojectspage/index.mdwn
index 2b06204..68add2f 100644
--- a/docs/developer/gsocprojectspage/index.mdwn
+++ b/docs/developer/gsocprojectspage/index.mdwn
@@ -39,23 +39,6 @@ Meta information:
* Contact point: kernel@crater.dragonflybsd.org
---
-##### Implement i386 32-bit ABI for x86_64 64-bit kernel
-* Add a 32-bit syscall table which translates 32-bit
- system calls to 64-bit.
-* Add support for 32 bit compatibility mode operation
- and ELF binary detection.
-
-The idea here is to support the execution of 32 bit DragonFly binaries in 64 bit DragonFly environments, something numerous other operating systems have done. Several things must be done to support this. First, the appropriate control bits must be set to execute in 32-bit compatibility mode while in usermode instead of 64-bit mode. Second, when a system call is made from 32-bit mode a translation layer is needed to translate the system call into the 64-bit requivalent within the kernel. Third, the signal handler and trampoline code needs to operate on the 32-bit signal frame. Fourth, the 32 and 64 bit ELF loaders both have to be in the kernel at the same time, which may require some messing around with procedure names and include files since originally the source was designed to be one or the other.
-
-There are several hundred system calls which translates to a great deal of 'grunt work' when it comes time to actually do all the translations.
-
-Meta information:
-
-* Prerequisites: C
-* Difficulty: Difficult (lots of moving parts, particularly the trapframes)
-* Contact point: dillon
-
----
##### Implement ARC algorithm extension for the vnode free list
* Vnode recycling is LRU and can't efficiently handle data sets which
@@ -114,17 +97,6 @@ Meta information:
---
-##### Adapt pkgsrc to create a package system with dependency independence.
-* Create a set of tools that modifies how the pkgsrc packages are installed, allowing for the ability to upgrade individual packages, without stopping applications that depend on said packages from working. One method of achieving this is detailed at http://www.dragonflybsd.org/goals/#packages but other methods may be possible. PC-BSD have written a tool called PBI Builder which modifies FreeBSD ports for their dependency independence PBI system, this could be used as a starting point for the DragonFly BSD tools.
-
-Meta information:
-
-* Prerequisites: C
-* Difficulty: ?
-* Contact point: kernel@crater.dragonflybsd.org
-
----
-
##### Make vkernels checkpointable (2011 Project)
* See checkpt(1).
@@ -437,3 +409,49 @@ Meta information:
---
(please add)
+
+
+#### Old not-so-useful project ideas, don't look here
+
+##### Implement i386 32-bit ABI for x86_64 64-bit kernel
+* Add a 32-bit syscall table which translates 32-bit
+ system calls to 64-bit.
+* Add support for 32 bit compatibility mode operation
+ and ELF binary detection.
+
+The idea here is to support the execution of 32 bit DragonFly binaries in 64 bit DragonFly environments, something numerous other operating systems have done. Several things must be done to support this. First, the appropriate control bits must be set to execute in 32-bit compatibility mode while in usermode instead of 64-bit mode. Second, when a system call is made from 32-bit mode a translation layer is needed to translate the system call into the 64-bit requivalent within the kernel. Third, the signal handler and trampoline code needs to operate on the 32-bit signal frame. Fourth, the 32 and 64 bit ELF loaders both have to be in the kernel at the same time, which may require some messing around with procedure names and include files since originally the source was designed to be one or the other.
+
+There are several hundred system calls which translates to a great deal of 'grunt work' when it comes time to actually do all the translations.
+
+Meta information:
+
+* Prerequisites: C
+* Difficulty: Difficult (lots of moving parts, particularly the trapframes)
+* Contact point: dillon
+
+Usefullness:
+
+DragonFly/x86_64 has been available for a few years, and is now
+the most used DragonFly architecture.
+There has never been an obvious need to use i386 DragonFly binaries
+with it, all available DragonFly/i386 software can be rebuilt from source code.
+
+---
+
+##### Adapt pkgsrc to create a package system with dependency independence.
+* Create a set of tools that modifies how the pkgsrc packages are installed, allowing for the ability to upgrade individual packages, without stopping applications that depend on said packages from working. One method of achieving this is detailed at http://www.dragonflybsd.org/goals/#packages but other methods may be possible. PC-BSD have written a tool called PBI Builder which modifies FreeBSD ports for their dependency independence PBI system, this could be used as a starting point for the DragonFly BSD tools.
+
+Meta information:
+
+* Prerequisites: C
+* Difficulty: ?
+* Contact point: kernel@crater.dragonflybsd.org
+
+Usefulness:
+
+A new dports/pkg packaging system based on FreeBSD ports and pkgng has
+been implemented and is far superior to pkgsrc for all practical purposes.
+Pkgsrc may not be the best base to start such a project and the time
+needed to implement it will be far greater than the regular GSoc timeframe. More like one year than two months.
+
+---
--
2.10.1