--- wikisrc/users/jdf.mdwn	2012/12/22 13:18:43	1.8
+++ wikisrc/users/jdf.mdwn	2013/03/14 23:20:58	1.32
@@ -1,3 +1,5 @@
+**Contents**
+
 [[!toc levels=2 ]]
 
 # jdf's wiki page
@@ -5,11 +7,64 @@
 Note: This is not what I'm really working on, it's just a place to gather some 
 notes I took about some topics.
 
+## The new NetBSD guide
+
+The NetBSD guide, as well as its contents, is outdated. Of course there's 
+current documentation as well in it, but many parts of it are outdated.
+The question is: What is the future of the NetBSD guide?
+
+Should we continue having something ordered by *book chapters*? Or should we 
+make it completely unordered with many howtos inside a wiki, which is also 
+printable, but not in a useful order?
+
+In my opinion, we should continue having a set of articles where the basic 
+subsystems of NetBSD are explained, but in the wiki. It shouldn't be too 
+difficult to create a book from that if you want to.
+From all these subsystems, imho, the following topics should be covered:
+
+System basics:
+
+ * Installation
+ * Security (CGD, PGP, veriexec, PAM)
+ * Disk handling (GPT, disklabel, MBR), creating filesystems, handling USB 
+   flashdrives, automounting, CDs
+ * RAIDs with raidframe
+ * LVM
+ * Audio setup
+ * Keeping a NetBSD installation up-to-date
+ * The rc system, as compared to systemd and SysV
+ * Editing with vi
+ * X setup, graphics drivers, console drivers
+ * Backups with dump/restore and other options
+ * Printing (with cups?)
+
+Networking:
+
+ * Basic network setup
+ * inetd setup
+ * Bluetooth
+ * DNS server setup and related issues
+ * Firewalling (describing *all* or linking guide of others)
+
+Building NetBSD:
+
+ * Building the system with `build.sh`
+ * Configuring the kernel
+ * Fetching sources, staying -current
+
+Using extra packages:
+
+ * Emulating Linux
+ * Using pkgsrc
+ * Using binary packages, using pkgin
+ * Installing a desktop environment
+ * Things to remember (e.g., no mplayer)
+
 ## 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 +82,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