Diff for /wikisrc/users/jdf.mdwn between versions 1.8 and 1.29

version 1.8, 2012/12/22 13:18:43 version 1.29, 2013/03/11 21:03:09
Line 1 Line 1
   **Contents**
   
 [[!toc levels=2 ]]  [[!toc levels=2 ]]
   
 # jdf's wiki page  # jdf's wiki page
Line 5 Line 7
 Note: This is not what I'm really working on, it's just a place to gather some   Note: This is not what I'm really working on, it's just a place to gather some 
 notes I took about some topics.  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:
   
    * chap-exinst
    * inst-media
    * net-practice
   
   Already done:
   
    * audio
    * bluetooth
    * boot
    * build
    * carp
    * ccd
    * cgd
    * cons
    * dns
    * edit
    * index
    * inetd
    * intro
    * fetch
    * kernel
    * linux
    * lvm
    * mail
    * misc
    * net-intro
    * net-services
    * pam
    * print
    * raidframe
    * rmmedia
    * rc
    * tuning
    * 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.
   
   ## 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  ## NetBSD flavoured
   
 Currently, NetBSD is a very generic operating system, leaving almost all  Currently, NetBSD is a very generic operating system, leaving almost all
 choices up to the user. While some consider this a strength, and it  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.  people who then have to setup *everything* by hand.
   
 Creating a *NetBSD flavoured* distribution shouldn't be much work, and require   Creating a *NetBSD flavoured* distribution shouldn't be much work, and require 
Line 27  are *very* specific. You cannot really p Line 129  are *very* specific. You cannot really p
 installation except for some basic things like installing a vim, but that's all.  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   My current idea is to provide just one, maybe named *NetBSD flavoured*, with at 
 least the following tools on board:  least the following tools on board:
   
  * vim   * vim
  * pkgin   * pkgin
  * git   * git

Removed from v.1.8  
changed lines
  Added in v.1.29


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb