--- wikisrc/users/jdf.mdwn	2013/02/27 00:02:45	1.11
+++ wikisrc/users/jdf.mdwn	2013/03/09 00:16:05	1.26
@@ -12,60 +12,107 @@ notes I took about some topics.
 I'm currently trying to migrate the NetBSD guide to the wiki. The relevant
 files are these ones:
 
- * ap-ack
- * ap-biblio
- * ap-contrib
- * ap-xml
- * appendix
+ * chap-exinst
+ * inst-media
+ * inst
+ * mail
+ * net-intro
+ * net-practice
+ * net-services
+ * print
+ * rmmedia
+
+Already done:
+
+ * audio
  * bluetooth
  * boot
  * build
  * carp
  * ccd
  * cgd
- * chap-exinst
- * chap-intro
  * cons
  * dns
  * edit
- * fetch
  * index
  * inetd
- * inst-media
- * inst
+ * intro
+ * fetch
  * kernel
  * linux
  * lvm
- * mail
  * misc
- * net-intro
- * net-practice
- * net-services
  * pam
- * preface
- * print
+ * raidframe
  * rc
- * rf
- * rmmedia
  * tuning
  * updating
  * upgrading
  * veriexec
  * x
 
-Already done:
-
- * audio
-
 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.
 
+## 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