--- wikisrc/users/jdf.mdwn	2012/12/22 13:16:53	1.7
+++ wikisrc/users/jdf.mdwn	2013/03/04 00:33:23	1.17
@@ -1,15 +1,65 @@
-[[!toc ]]
+**Contents**
+
+[[!toc levels=2 ]]
 
 # jdf's wiki page
 
 Note: This is not what I'm really working on, it's just a place to gather some 
 notes I took about some topics.
 
+## Guide migration
+
+I'm currently trying to migrate the NetBSD guide to the wiki. The relevant
+files are these ones:
+
+ * bluetooth
+ * build
+ * carp
+ * ccd
+ * cgd
+ * chap-exinst
+ * cons
+ * dns
+ * edit
+ * fetch
+ * inetd
+ * inst-media
+ * inst
+ * linux
+ * lvm
+ * mail
+ * misc
+ * net-intro
+ * net-practice
+ * net-services
+ * pam
+ * print
+ * rmmedia
+ * tuning
+
+Already done:
+
+ * audio
+ * boot
+ * index
+ * intro
+ * kernel
+ * raidframe
+ * rc
+ * updating
+ * upgrading
+ * veriexec
+ * x
+
+I started working on it in `guide/`, though the original proposal
+was to store it in `guide/netbsd`. However, whoever wants to change the
+directory can do so.
+
 ## NetBSD flavoured
 
 Currently, NetBSD is a very generic operating system, leaving almost all
 choices up to the user. While some consider this a strength, and it
-definetly is for people who know what they're doing, it's an obstacle for
+definitely is for people who know what they're doing, it's an obstacle for
 people who then have to setup *everything* by hand.
 
 Creating a *NetBSD flavoured* distribution shouldn't be much work, and require 
@@ -27,6 +77,7 @@ are *very* specific. You cannot really p
 installation except for some basic things like installing a vim, but that's all.
 My current idea is to provide just one, maybe named *NetBSD flavoured*, with at 
 least the following tools on board:
+
  * vim
  * pkgin
  * git
@@ -47,8 +98,9 @@ least the following tools on board:
 
 ## NetBSD documentation
 
-In [http://mail-index.netbsd.org/netbsd-docs/2012/09/20/msg000295.html](this 
-post) I shared some ideas about what to do with documentation. Though much of it 
+In [this 
+post](http://mail-index.netbsd.org/netbsd-docs/2012/09/20/msg000295.html)
+I shared some ideas about what to do with documentation. Though much of it 
 was proven not practical by the replies, I still have one idea: Unify 
 documentation of NetBSD, and provide it all on a NetBSD system.