Diff for /wikisrc/users/jdf.mdwn between versions 1.5 and 1.6

version 1.5, 2012/06/16 14:15:36 version 1.6, 2012/07/06 22:47:31
Line 14  These project ideas are not sufficient f Line 14  These project ideas are not sufficient f
 * unionfs -- there are some bugs with union I would like to see fixed. Imagine running a live CD by having a root read-only, and then simply mounting a tmpfs writable upon that.  * unionfs -- there are some bugs with union I would like to see fixed. Imagine running a live CD by having a root read-only, and then simply mounting a tmpfs writable upon that.
 * raidfs -- once unionfs is fixed, it could be possible to integrate a mirror, perhaps some redundancy checks with unionfs to have a flexible raid on vnode basis, not depending on the underlying filesystem or device.  * raidfs -- once unionfs is fixed, it could be possible to integrate a mirror, perhaps some redundancy checks with unionfs to have a flexible raid on vnode basis, not depending on the underlying filesystem or device.
 * userwiki -- I know this is a controversary topic... So no matter how and where, but having a place where users can contribute content in an ordered way (i.e., not on a mailing list), would be nice. See below for advocacy.  * userwiki -- I know this is a controversary topic... So no matter how and where, but having a place where users can contribute content in an ordered way (i.e., not on a mailing list), would be nice. See below for advocacy.
 * Security BSD derivate -- There was this teenie book, "Little Brother" from Cory Doctorow. There, they had an operating system that was actually only on a CD, and encrypted the whole hard disk, and everything ran on the hard disk. Imagine you had the same for NetBSD... A base system (Jibbed would be sufficient), which has some small wrapper scripts trying to decrypt a hard disk, and if it succeeds, mounts this as its /usr/pkg or so. You could have a completely virgin OS (the CD, which is read-only), and a completely encrypted hard disk, which carries everything variable. Updates of the base system would be just burning a new CD... I know there are close projects already done in Linux, but they all assume an USB flash drive.  * NetBSD derivates/distributions -- provide prepackaged NetBSD distributions for several applications, see below
   
 Providing a more unified, complete system:  Providing a more unified, complete system:
   
Line 40  I'm not into pkgsrc, but for the easy pa Line 40  I'm not into pkgsrc, but for the easy pa
 * caring for [[!template id=pkg category="devel" name="fossil"]] being up-to-date  * caring for [[!template id=pkg category="devel" name="fossil"]] being up-to-date
 * keeping the events site up-to-date  * keeping the events site up-to-date
   
   # NetBSD derivates
   
   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 people who then have to setup *everything* by hand.
   
   It shouldn't be much work to just package distribution sets that already include a list of packages it installs and several preconfigured configuration files, maybe also some additional wrapper scripts.
   Technically, this could also be integrated to pkgsrc as well. You just have to package everything you want (dependencies, files, etc.) into one package, and then depend on this single package. The finalized derivate would then just depend on this single package, and maybe contain all needed files already on the CD itself, as well as some configuration files for /etc.
   
   * NetBSD serve -- a compilation of tools and scripts that are useful for using NetBSD as a server. Maybe there could be even more flavours like this, packaged into single pkgsrc packages, which contain preconfigured "appliances" like an ldap package, a webserver package, etc., everything with a sane configuration default.
   * NetBSD develop -- just a compilation of some desktop tools. Telling somebody what he has to do to get a graphical environment with NetBSD (light-desktop) is annoying, so just have a distribution where light-desktop and maybe some other tools are preinstalled. I think 'develop' might be a good description of the targeted audience, as then you can choose a fairly tight set of packages to put in: light-desktop, vim, several VCSs, etc.
   * NetBSD secure -- there was this teenie book, "Little Brother" from Cory Doctorow. There, they had an operating system that was actually only on a CD, and encrypted the whole hard disk, and everything ran on the hard disk. Imagine you had the same for NetBSD... A base system (Jibbed would be sufficient), which has some small wrapper scripts trying to decrypt a hard disk, and if it succeeds, mounts this as its /usr/pkg or so. You could have a completely virgin OS (the CD, which is read-only), and a completely encrypted hard disk, which carries everything variable. Updates of the base system would be just burning a new CD... I know there are close projects already done in Linux, but they all assume an USB flash drive.
   
   
 # Advocacy  # Advocacy
   

Removed from v.1.5  
changed lines
  Added in v.1.6


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