From 6eb6d5314e303379debbef82921a215ef2b00d98 Mon Sep 17 00:00:00 2001 From: Carl Fredrik Hammar Date: Wed, 10 Mar 2010 16:19:06 +0100 Subject: Fix typos and spelling on GSoC pages --- community/gsoc/project_ideas/dtrace.mdwn | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'community/gsoc/project_ideas/dtrace.mdwn') diff --git a/community/gsoc/project_ideas/dtrace.mdwn b/community/gsoc/project_ideas/dtrace.mdwn index 93c2a5f3..25e6db29 100644 --- a/community/gsoc/project_ideas/dtrace.mdwn +++ b/community/gsoc/project_ideas/dtrace.mdwn @@ -16,9 +16,9 @@ problems, these are mostly just guesses. Better understanding what really causes bad performance is necessary to improve the situation. For that, we need tools for performance measurements. While all kinds of more -or less specific profiling tools could be convieved, the most promising and +or less specific profiling tools could be conceived, the most promising and generic approach seems to be a framework for logging certain events in the -running system (both in the microkernel and in the Hurd servers). This would +running system (both in the micro kernel and in the Hurd servers). This would allow checking how much time is spent in certain modules, how often certain situations occur, how things interact, etc. It could also prove helpful in debugging some issues that are otherwise hard to find because of complex @@ -34,7 +34,7 @@ with integrating existing components as well as low-level programming. Possible mentors: Samuel Thibault (youpi) -Exercise: In lack of a good exercise directly related to this taks, just pick +Exercise: In lack of a good exercise directly related to this task, just pick one of the kernel-related or generally low-level tasks from the bug/task trackers on savannah, and make a go at it. You might not be able to finish the task in a limited amount of time, but you should at least be able to make a -- cgit v1.2.3 From 1b076ae5402eae01a4630b4a617b806806f899ce Mon Sep 17 00:00:00 2001 From: Carl Fredrik Hammar Date: Thu, 11 Mar 2010 13:23:12 +0100 Subject: Spell it `microkernel' --- community/gsoc/project_ideas/driver_glue_code.mdwn | 2 +- community/gsoc/project_ideas/dtrace.mdwn | 2 +- community/gsoc/project_ideas/gnumach_cleanup.mdwn | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) (limited to 'community/gsoc/project_ideas/dtrace.mdwn') diff --git a/community/gsoc/project_ideas/driver_glue_code.mdwn b/community/gsoc/project_ideas/driver_glue_code.mdwn index 4e1e338c..9c063e9f 100644 --- a/community/gsoc/project_ideas/driver_glue_code.mdwn +++ b/community/gsoc/project_ideas/driver_glue_code.mdwn @@ -12,7 +12,7 @@ is included in the section entitled [[!meta title="New Driver Glue Code"]] Although a driver framework in user space would be desirable, presently the Hurd -uses kernel drivers in the micro kernel, +uses kernel drivers in the microkernel, [[GNU_Mach|microkernel/mach/gnumach]]. (And changing this would be far beyond a GSoC project...) diff --git a/community/gsoc/project_ideas/dtrace.mdwn b/community/gsoc/project_ideas/dtrace.mdwn index 25e6db29..4a46cf38 100644 --- a/community/gsoc/project_ideas/dtrace.mdwn +++ b/community/gsoc/project_ideas/dtrace.mdwn @@ -18,7 +18,7 @@ causes bad performance is necessary to improve the situation. For that, we need tools for performance measurements. While all kinds of more or less specific profiling tools could be conceived, the most promising and generic approach seems to be a framework for logging certain events in the -running system (both in the micro kernel and in the Hurd servers). This would +running system (both in the microkernel and in the Hurd servers). This would allow checking how much time is spent in certain modules, how often certain situations occur, how things interact, etc. It could also prove helpful in debugging some issues that are otherwise hard to find because of complex diff --git a/community/gsoc/project_ideas/gnumach_cleanup.mdwn b/community/gsoc/project_ideas/gnumach_cleanup.mdwn index 954e1242..4aef0d1b 100644 --- a/community/gsoc/project_ideas/gnumach_cleanup.mdwn +++ b/community/gsoc/project_ideas/gnumach_cleanup.mdwn @@ -10,7 +10,7 @@ is included in the section entitled [[!meta title="GNU Mach Code Cleanup"]] -Although there are some attempts to move to a more modern micro kernel +Although there are some attempts to move to a more modern microkernel altogether, the current Hurd implementation is based on [[GNU_Mach|microkernel/mach/gnumach]], which is only a slightly modified variant of the original CMU [[microkernel/Mach]]. -- cgit v1.2.3