From 49fbd30e4a54c687530b9a3566d1463e5f638ddc Mon Sep 17 00:00:00 2001 From: antrik Date: Thu, 12 Mar 2009 03:52:14 +0100 Subject: mtab GSoC task: fix typos --- community/gsoc/project_ideas/mtab.mdwn | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'community/gsoc') diff --git a/community/gsoc/project_ideas/mtab.mdwn b/community/gsoc/project_ideas/mtab.mdwn index 056ed042..99b37655 100644 --- a/community/gsoc/project_ideas/mtab.mdwn +++ b/community/gsoc/project_ideas/mtab.mdwn @@ -26,10 +26,10 @@ explicitely specified mountpoints, instead of displaying the usual listing. One possible solution to this would be for the translator startup mechanism to update the `mtab` on any `mount`/`unmount`, like in traditional systems. -However, there are same problems with this approach. Most notably: what to do +However, there are some problems with this approach. Most notably: what to do with passive translators, i.e., translators that are not presently running, but set up to be started automatically whenever the node is accessed? Probably -these should be counted an among the mounted filesystems; but how to handle the +these should be counted among the mounted filesystems; but how to handle the `mtab` updates for a translator that is not started yet? Generally, being centralized and event-based, this is a pretty unelegant, non-hurdish solution. -- cgit v1.2.3