Diff for /wikisrc/projects/code-in.mdwn between versions 1.29 and 1.30

version 1.29, 2012/10/18 20:30:14 version 1.30, 2012/10/18 20:38:58
Line 74  Used tags are (categories are not tagged Line 74  Used tags are (categories are not tagged
 * **Task: Howto: Update the system from binaries**: There is the new tool written in shell named sysupgrade (to be found in pkgsrc/sysutils/sysupgrade), which updates the system in binaries for you. Though it is nice, you may have reasons to not use it for an update (e.g. non-standard systems, or some components may not change).    * **Task: Howto: Update the system from binaries**: There is the new tool written in shell named sysupgrade (to be found in pkgsrc/sysutils/sysupgrade), which updates the system in binaries for you. Though it is nice, you may have reasons to not use it for an update (e.g. non-standard systems, or some components may not change).  
   This is why you should document the single tasks sysupgrade does (and why) and fill it with examples, in the end creating an howto which resembles the work done by sysupgrade.      This is why you should document the single tasks sysupgrade does (and why) and fill it with examples, in the end creating an howto which resembles the work done by sysupgrade.  
   [sysupgrade usage](http://www.netbsd.org/docs/guide/en/chap-upgrading.html)      [sysupgrade usage](http://www.netbsd.org/docs/guide/en/chap-upgrading.html)  
   *Tag*: howto    *Tag*: howto  
   *Tag*: research    *Tag*: research
   
 * **Task: Howto: Install additional software in NetBSD**: With NetBSD, you have three major ways to install additional software: pkgsrc, pkg_add and pkgin.    * **Task: Howto: Install additional software in NetBSD**: With NetBSD, you have three major ways to install additional software: pkgsrc, pkg_add and pkgin.  
   Which one is to use for which use case, what are their benefits, their merits? Document them, and give a small introduction of the needed tools and their usage (package installation, package deletion, package information).      Which one is to use for which use case, what are their benefits, their merits? Document them, and give a small introduction of the needed tools and their usage (package installation, package deletion, package information).  
   *Tag*: howto      *Tag*: howto  
   *Tag*: system    *Tag*: system  
   *Tag*: service    *Tag*: service
   
 * **Task: Howto: Dual-boot NetBSD**: Having NetBSD not only as the single operating system, even if only for trying, is a common setup.    * **Task: Howto: Dual-boot NetBSD**: Having NetBSD not only as the single operating system, even if only for trying, is a common setup.  
Line 99  Used tags are (categories are not tagged Line 99  Used tags are (categories are not tagged
 * **Task: Howto: Running usermanagement with LDAP and Kerberos**: Having NetBSD being a server is a common setup. Additionally to all the LDAP and Kerberos setup tutorials in the web, an explicit tutorial how to use NetBSD as an LDAP and Kerberos server would be nice.    * **Task: Howto: Running usermanagement with LDAP and Kerberos**: Having NetBSD being a server is a common setup. Additionally to all the LDAP and Kerberos setup tutorials in the web, an explicit tutorial how to use NetBSD as an LDAP and Kerberos server would be nice.  
   This means you shouldn't reproduce all the other tutorials about the gory internals, but rather describe what has to be done which is NetBSD-specific (which packages have to be installed, where their configuration files lie, etc.) and just a short chapter about what is needed for the rest, with a reference to the original OpenLDAP and Heimdal/MIT documentation.      This means you shouldn't reproduce all the other tutorials about the gory internals, but rather describe what has to be done which is NetBSD-specific (which packages have to be installed, where their configuration files lie, etc.) and just a short chapter about what is needed for the rest, with a reference to the original OpenLDAP and Heimdal/MIT documentation.  
   *Tag*: howto      *Tag*: howto  
   *Tag*: service    *Tag*: service  
   *Tag*: system    *Tag*: system
   
 * **Task: Howto: Running a webserver with Apache**: As well as the aforementioned task with OpenLDAP and Kerberos, a howto what to do with Apache in NetBSD would be good.    * **Task: Howto: Running a webserver with Apache**: As well as the aforementioned task with OpenLDAP and Kerberos, a howto what to do with Apache in NetBSD would be good.  
   This should also include a reference to the already included bozohttpd, which may be suited better in some cases.      This should also include a reference to the already included bozohttpd, which may be suited better in some cases.  
   *Tag*: howto    *Tag*: howto  
   *Tag*: service    *Tag*: service  
   *Tag*: system    *Tag*: system
   
 * **Task: Howto: Using LVM to manage your disks**: There is already a [chapter about the logical volume manager in NetBSD](http://netbsd.org/docs/guide/en/chap-lvm.html).    * **Task: Howto: Using LVM to manage your disks**: There is already a [chapter about the logical volume manager in NetBSD](http://netbsd.org/docs/guide/en/chap-lvm.html).  
Line 121  Used tags are (categories are not tagged Line 121  Used tags are (categories are not tagged
 * **Task: Rewrite system configuration in the guide**: January this year, we got a [new configuration menu for the installer](http://mail-index.netbsd.org/tech-install/2012/01/23/msg000223.html)  * **Task: Rewrite system configuration in the guide**: January this year, we got a [new configuration menu for the installer](http://mail-index.netbsd.org/tech-install/2012/01/23/msg000223.html)
   The chapter in the guide about system configuration is still [the old one](http://netbsd.org/docs/guide/en/chap-exinst.html#exinst-system-configuration)    The chapter in the guide about system configuration is still [the old one](http://netbsd.org/docs/guide/en/chap-exinst.html#exinst-system-configuration)
   Your task is to rewrite this paragraph, add a new screenshot such that it fits the new configuration menu.      Your task is to rewrite this paragraph, add a new screenshot such that it fits the new configuration menu.  
   *Tag*: howto    *Tag*: howto  
   *Tag*: ui    *Tag*: ui
   
 * **Task: Convert articles from the website to wiki articles**: There are several articles on the website (like [this one](http://netbsd.org/docs/misc/index.html)) which should be converted to wiki articles.    * **Task: Convert articles from the website to wiki articles**: There are several articles on the website (like [this one](http://netbsd.org/docs/misc/index.html)) which should be converted to wiki articles.  
Line 136  Used tags are (categories are not tagged Line 136  Used tags are (categories are not tagged
 * **Task: Convert installation notes to markdown**: Currently, the [installation notes](http://ftp.netbsd.org/pub/NetBSD/NetBSD-5.1.2/i386/INSTALL.html) are constructed with mdoc from distrib/notes.    * **Task: Convert installation notes to markdown**: Currently, the [installation notes](http://ftp.netbsd.org/pub/NetBSD/NetBSD-5.1.2/i386/INSTALL.html) are constructed with mdoc from distrib/notes.  
   The task is to research whether it is possible to convert these articles to markdown, and, if possible, do so.      The task is to research whether it is possible to convert these articles to markdown, and, if possible, do so.  
   There might be many inclusions etc. to get the original structure, but even the result of *what* has to be done without the actual conversion would be neat.      There might be many inclusions etc. to get the original structure, but even the result of *what* has to be done without the actual conversion would be neat.  
   *Tag*: wiki    *Tag*: wiki  
   *Tag*: man    *Tag*: man
   
 * **Task: Describe how to run NetBSD headless**: For any server usage, you want to use NetBSD without access to keyboard, mouse or monitor. For these usages, you want to have access via ssh (or something similar, document that) or serial console.    * **Task: Describe how to run NetBSD headless**: For any server usage, you want to use NetBSD without access to keyboard, mouse or monitor. For these usages, you want to have access via ssh (or something similar, document that) or serial console.  
   Your task is to describe the steps which are necessary to run a NetBSD system headless, i.e. printing boot messages to serial port, enabling the bootloader on serial, enabling the serial port, describing the possible options how to do so, which security measures should  be taken.      Your task is to describe the steps which are necessary to run a NetBSD system headless, i.e. printing boot messages to serial port, enabling the bootloader on serial, enabling the serial port, describing the possible options how to do so, which security measures should  be taken.  
   You should also consider systems which don't even have a serial port, i.e. what has to be done if you cannot watch a device start, but you *must* go sure it will come up and you have some sort of access (like a router).      You should also consider systems which don't even have a serial port, i.e. what has to be done if you cannot watch a device start, but you *must* go sure it will come up and you have some sort of access (like a router).  
   *Tag*: howto    *Tag*: howto  
   *Tag*: system    *Tag*: system
   
 * **Task: Describe how to use NetBSD as a bluetooth access point**: With bluetooth, you can easily connect your computer to a mobile phone and let the phone use the network connection of the computer.    * **Task: Describe how to use NetBSD as a bluetooth access point**: With bluetooth, you can easily connect your computer to a mobile phone and let the phone use the network connection of the computer.  
   Your task is to describe how to do this: Connecting NetBSD via bluetooth to your phone and then provide different services (especially file transfer and network connection).      Your task is to describe how to do this: Connecting NetBSD via bluetooth to your phone and then provide different services (especially file transfer and network connection).  
   *Tag*: howto    *Tag*: howto  
   *Tag*: system    *Tag*: system  
   *Tag*: network    *Tag*: network  
   *Tag*: service    *Tag*: service
   
 * **Task: Describe how to use NetBSD as an appliance**: NetBSD is often used for appliances, i.e. a small server serving only one single purpose. Though, there are no howtos describing how to set up a single appliance serving only one cause.    * **Task: Describe how to use NetBSD as an appliance**: NetBSD is often used for appliances, i.e. a small server serving only one single purpose. Though, there are no howtos describing how to set up a single appliance serving only one cause.  
Line 159  Used tags are (categories are not tagged Line 159  Used tags are (categories are not tagged
   * **file server** - NetBSD is also excellent as a file server, may it be either with nfs, smb, http, ftp or ftp over ssh as the transfer protocol. Your task would be to describe the packages which exist in pkgsrc and in NetBSD's base, and choose one special scenario for each protocol and give example configurations of the services. You should also mention RAIDframe, lvm and cgd briefly and what their use cases are. A good example for an existing appliance is FreeNAS or Apple Time Capsule (already running NetBSD).    * **file server** - NetBSD is also excellent as a file server, may it be either with nfs, smb, http, ftp or ftp over ssh as the transfer protocol. Your task would be to describe the packages which exist in pkgsrc and in NetBSD's base, and choose one special scenario for each protocol and give example configurations of the services. You should also mention RAIDframe, lvm and cgd briefly and what their use cases are. A good example for an existing appliance is FreeNAS or Apple Time Capsule (already running NetBSD).
   Every howto for an appliance is considered a single task.      Every howto for an appliance is considered a single task.  
   * **backup server** - though somewhat similar to a file server, a backup server has different requirements. On the one hand, you have to think about how to connect effectively for backups, e.g. with rsync or other special backup protocols. On the other hand, you have to take special care for data integrity and data security. You should also take file system snapshots into account.    * **backup server** - though somewhat similar to a file server, a backup server has different requirements. On the one hand, you have to think about how to connect effectively for backups, e.g. with rsync or other special backup protocols. On the other hand, you have to take special care for data integrity and data security. You should also take file system snapshots into account.
   
   As a special task, you could also create a shell script that fulfills the steps you mentioned in your howto, such that the user only has to execute this script to get an appliance. The prerequisite is only for this task.      As a special task, you could also create a shell script that fulfills the steps you mentioned in your howto, such that the user only has to execute this script to get an appliance. The prerequisite is only for this task.  
   If you can think of more possible appliances, maybe you can also use this as a task. If you want to work on a larger project (i.e. providing a whole derivate with one of these tasks), just tell us.      If you can think of more possible appliances, maybe you can also use this as a task. If you want to work on a larger project (i.e. providing a whole derivate with one of these tasks), just tell us.  
   *Prerequisites*: sh      *Prerequisites*: sh  
   *Tag*: howto      *Tag*: howto  
   *Tag*: research      *Tag*: research  
   *Tag*: service    *Tag*: service  
   *Tag*: system    *Tag*: system  
   *Tag*: network    *Tag*: network
   
 * **Task: Describe how to backup NetBSD**: Though NetBSD is much like other Unixes in this respect, backup is still something you should consider specially for every operating system. Which tools are available in the base distribution for backupping, like dump(8) and restore(8)?    * **Task: Describe how to backup NetBSD**: Though NetBSD is much like other Unixes in this respect, backup is still something you should consider specially for every operating system. Which tools are available in the base distribution for backupping, like dump(8) and restore(8)?  
Line 173  Used tags are (categories are not tagged Line 174  Used tags are (categories are not tagged
   What is a full, a differential, an incremental backup? What is the estimated space usage of them, depending on the backups?      What is a full, a differential, an incremental backup? What is the estimated space usage of them, depending on the backups?  
   How would you restore your system after a crash, which steps have to be taken to get a working system again?      How would you restore your system after a crash, which steps have to be taken to get a working system again?  
   After reading the resulting article, the reader should be able to decide for a backup scheme and solution and implement it without further research.      After reading the resulting article, the reader should be able to decide for a backup scheme and solution and implement it without further research.  
   *Tag*: howto    *Tag*: howto  
   *Tag*: system    *Tag*: system  
   *Tag*: research    *Tag*: research
   
 * **Task: Describe how to create a NetBSD live flash drive**: Flash drives become increasingly the source for operating system installations.    * **Task: Describe how to create a NetBSD live flash drive**: Flash drives become increasingly the source for operating system installations.  
   Though, you might want to try the operating system first by using a live system.      Though, you might want to try the operating system first by using a live system.  
   In this task you should create a live USB flash drive from NetBSD. You can use Jibbed or the installation USB flash drive images as an example how to do this.      In this task you should create a live USB flash drive from NetBSD. You can use Jibbed or the installation USB flash drive images as an example how to do this.  
   In the end, there should be a howto which steps have to be taken to enable NetBSD to boot from a flash drive.      In the end, there should be a howto which steps have to be taken to enable NetBSD to boot from a flash drive.  
   *Tag*: howto    *Tag*: howto  
   *Tag*: research    *Tag*: research  
   *Tag*: system    *Tag*: system
   
 * **Task: Describe how to become a voip provider**: Sip is a protocol used for VoIP communications.    * **Task: Describe how to become a voip provider**: Sip is a protocol used for VoIP communications.  
   NetBSD was sometimes tried as a VoIP server, but there has been no howto yet how to do this.      NetBSD was sometimes tried as a VoIP server, but there has been no howto yet how to do this.  
   So, install an Asterisk or FreeSwitch or something else like that and describe how to use NetBSD as a VoIP server.      So, install an Asterisk or FreeSwitch or something else like that and describe how to use NetBSD as a VoIP server.  
   *Tag*: howto    *Tag*: howto  
   *Tag*: service    *Tag*: service
   
   
Line 197  Used tags are (categories are not tagged Line 198  Used tags are (categories are not tagged
 * **Task: Howto: Getting in touch with NetBSD**: If you have a problem, there are several ways to get in touch with NetBSD people: BSD user groups, mailing lists, IRC, problem reports... Which one is the best for which issue?    * **Task: Howto: Getting in touch with NetBSD**: If you have a problem, there are several ways to get in touch with NetBSD people: BSD user groups, mailing lists, IRC, problem reports... Which one is the best for which issue?  
   Document the single methods for contacting others and categorize them by the task they're useful for.      Document the single methods for contacting others and categorize them by the task they're useful for.  
   *Tag*: howto      *Tag*: howto  
   *Tag*: research    *Tag*: research  
   *Tag*: overview    *Tag*: overview
   
 * **Task: Compare init systems with each other**: Additional to the historical ones (SysV and BSD), systemd recently added another init system to the Unix world.    * **Task: Compare init systems with each other**: Additional to the historical ones (SysV and BSD), systemd recently added another init system to the Unix world.  
   An objective comparison of these three systems (if there are other major ones, add them, maybe upstart?) would be nice. Not in the sense of showing their features side-by-side, but simply describing how they work and how you do things yourself.      An objective comparison of these three systems (if there are other major ones, add them, maybe upstart?) would be nice. Not in the sense of showing their features side-by-side, but simply describing how they work and how you do things yourself.  
   In the end, you should have created a small article that enables anyone using one of these systems to switch to the other one just by reading this article.      In the end, you should have created a small article that enables anyone using one of these systems to switch to the other one just by reading this article.  
   *Tag*: comparison      *Tag*: comparison  
   *Tag*: research    *Tag*: research  
   *Tag*: system    *Tag*: system
   
 * **Task: Investigate and document Markdown to PDF and text conversion**: Propose a method for converting NetBSD Guide Markdown pages into PDF and text, so that they can be delivered with releases. Note the information (description, source location, home page, build method) so that a pkgsrc package (or packages) can be built using the proposed tools (the tools chosen must be compilable for NetBSD, and other free Unix-like systems).    * **Task: Investigate and document Markdown to PDF and text conversion**: Propose a method for converting NetBSD Guide Markdown pages into PDF and text, so that they can be delivered with releases. Note the information (description, source location, home page, build method) so that a pkgsrc package (or packages) can be built using the proposed tools (the tools chosen must be compilable for NetBSD, and other free Unix-like systems).  
Line 227  Used tags are (categories are not tagged Line 228  Used tags are (categories are not tagged
   This task does not have to be about analyzation, but could also be simply the research how you could do this, which statistical methods. Maybe the student is not able to do the actual computation because of a lack of sources and computing power.      This task does not have to be about analyzation, but could also be simply the research how you could do this, which statistical methods. Maybe the student is not able to do the actual computation because of a lack of sources and computing power.  
   Besides being a gci task, thinking about these statistics, you could also create a nice website analyzing distributions based on statistical methods.      Besides being a gci task, thinking about these statistics, you could also create a nice website analyzing distributions based on statistical methods.  
   *Tag*: research      *Tag*: research  
   *Tag*: comparison    *Tag*: comparison  
   *Tag*: system    *Tag*: system  
   *Tag*: overview    *Tag*: overview
   
 * **Task: Compare firewall solutions in NetBSD**: NetBSD has several firewall solutions on board: ipf, npf, pf, even more (you should research that).    * **Task: Compare firewall solutions in NetBSD**: NetBSD has several firewall solutions on board: ipf, npf, pf, even more (you should research that).  
   For the beginner, it is not clear what they are capable of, how fast they are and what their syntaxes look like.      For the beginner, it is not clear what they are capable of, how fast they are and what their syntaxes look like.  
   In this task you should research the differences of these firewalls, create some examples that do the same (so you can view them side-by-side) and provide links to further documentation.      In this task you should research the differences of these firewalls, create some examples that do the same (so you can view them side-by-side) and provide links to further documentation.  
   *Tag*: comparison      *Tag*: comparison  
   *Tag*: network    *Tag*: network  
   *Tag*: research    *Tag*: research
   
   
Line 256  Used tags are (categories are not tagged Line 257  Used tags are (categories are not tagged
 * **Task: Make NetBSD a music or video player**: NetBSD could as well serve as a music (mpd) or video player. You have to research which packages are needed for such a use case, and document it in a tutorial.    * **Task: Make NetBSD a music or video player**: NetBSD could as well serve as a music (mpd) or video player. You have to research which packages are needed for such a use case, and document it in a tutorial.  
   Ideally, create a pkgsrc meta package including all the dependencies.      Ideally, create a pkgsrc meta package including all the dependencies.  
   Report bugs you find on the way.      Report bugs you find on the way.  
   *Tag*: ui    *Tag*: ui  
   *Tag*: research    *Tag*: research
   
 * **Task: Create ATF tests**: [[atf]] is the automatic test framework for NetBSD. We strive to have automatic tests for all the important parts of our system: libraries, syscalls, binaries, etc.    * **Task: Create ATF tests**: [[atf]] is the automatic test framework for NetBSD. We strive to have automatic tests for all the important parts of our system: libraries, syscalls, binaries, etc.  
Line 268  Used tags are (categories are not tagged Line 269  Used tags are (categories are not tagged
   * [[!template id=man name="ethers" section="3"]], [[!template id=man name="iso_addr" section="3"]] and [[!template id=man name="link_addr" section="3"]]    * [[!template id=man name="ethers" section="3"]], [[!template id=man name="iso_addr" section="3"]] and [[!template id=man name="link_addr" section="3"]]
   * [[!template id=man name="strtol" section="3"]], [[!template id=man name="strtoul" section="3"]] and [[!template id=man name="strtoull" section="3"]]    * [[!template id=man name="strtol" section="3"]], [[!template id=man name="strtoul" section="3"]] and [[!template id=man name="strtoull" section="3"]]
   * [[!template id=man name="uuid" section="3"]]    * [[!template id=man name="uuid" section="3"]]
   
   Every *single written test* is considered as **one task**. If you think there is another test that should be added, but is not listed here, feel free to contact us.      Every *single written test* is considered as **one task**. If you think there is another test that should be added, but is not listed here, feel free to contact us.  
   The tests should be written in either C or sh.      The tests should be written in either C or sh.  
   *Prerequisites*: sh or C      *Prerequisites*: sh or C  
Line 282  Used tags are (categories are not tagged Line 284  Used tags are (categories are not tagged
   * disklabel(8)    * disklabel(8)
   * gpt(8)    * gpt(8)
   In the end of this task, a small howto and some corrections for the manpages of the affected tools should be there.      In the end of this task, a small howto and some corrections for the manpages of the affected tools should be there.  
   *Tag*: system    *Tag*: system  
   *Tag*: howto    *Tag*: howto
   
 * **Task: Describe how to boot NetBSD on a gpt disk**: Currently, NetBSD supports booting from a gpt partition, but you cannot know how.    * **Task: Describe how to boot NetBSD on a gpt disk**: Currently, NetBSD supports booting from a gpt partition, but you cannot know how.  
Line 303  Used tags are (categories are not tagged Line 305  Used tags are (categories are not tagged
   
 * **Task: Document different time structures**: We have several time structures like `time_t`, `struct timespec`, `struct timeval`, `struct tm` and so on. Document all of them as a time(5) manpage such that a programmer can see all of them at once, in comparison. As we have time zone sensitive and time zone independent representations, figuring out conversions between local time and UTC from manual pages is hard and should also be documented in that manpage.    * **Task: Document different time structures**: We have several time structures like `time_t`, `struct timespec`, `struct timeval`, `struct tm` and so on. Document all of them as a time(5) manpage such that a programmer can see all of them at once, in comparison. As we have time zone sensitive and time zone independent representations, figuring out conversions between local time and UTC from manual pages is hard and should also be documented in that manpage.  
   *Prerequisites*: C coding skills (just reading)    *Prerequisites*: C coding skills (just reading)
   *Tag*: man    *Tag*: man  
   *Tag*: system    *Tag*: system
   
 * **Task: Add an web interface to apropos**: Last year's Google Summer Of Code project was creating a new apropos(1). Though the current version already has a web interface, adding CSS and appropriate HTML to the web interface would be nice to integrate it to other websites.    * **Task: Add an web interface to apropos**: Last year's Google Summer Of Code project was creating a new apropos(1). Though the current version already has a web interface, adding CSS and appropriate HTML to the web interface would be nice to integrate it to other websites.  
   Though the source code is written in C, C knowledge is not necessary. You just have to extract the HTML and pseudo-understand what the code around it does, i.e. in which cases the single actions are taken.      Though the source code is written in C, C knowledge is not necessary. You just have to extract the HTML and pseudo-understand what the code around it does, i.e. in which cases the single actions are taken.  
   The file which would be modified is [apropos-utils.c](https://github.com/abhinav-upadhyay/apropos_replacement/tree/cgi).      The file which would be modified is [apropos-utils.c](https://github.com/abhinav-upadhyay/apropos_replacement/tree/cgi).  
   *Prerequisites*: C CSS HTML    *Prerequisites*: C CSS HTML
   *Tag*: ui    *Tag*: ui  
   *Tag*: graphics    *Tag*: graphics
   
 * **Task: Create a pkgsrc package to get the wiki offline**: The NetBSD wiki can be fetched via cvs or rsync. As it is going to be filled up with information, you might want to have it offline.    * **Task: Create a pkgsrc package to get the wiki offline**: The NetBSD wiki can be fetched via cvs or rsync. As it is going to be filled up with information, you might want to have it offline.  
   The goal of this task is to create a pkgsrc package which depends on the tools necessary for offline-viewing of the wiki (this could also be just the integrated if you consider Markdown readable enough) and fetches the wiki.      The goal of this task is to create a pkgsrc package which depends on the tools necessary for offline-viewing of the wiki (this could also be just the integrated if you consider Markdown readable enough) and fetches the wiki.  
   All in all a simple package with few dependencies if any and one or two wrapper scripts.      All in all a simple package with few dependencies if any and one or two wrapper scripts.  
   *Prerequisites*: C or sh    *Prerequisites*: C or sh
   *Tag*: wiki    *Tag*: wiki  
   *Tag*: research    *Tag*: research
   
 * **Task: Describe all MK* variables**: Describe all the MK* variables and how they affect the builds.    * **Task: Describe all MK* variables**: Describe all the MK* variables and how they affect the builds.  

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


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