![[NetBSD Logo]](http://www.netbsd.org/images/NetBSD-headerlogo.png)
Recent changes to this wiki:
Index: wikisrc/tutorials.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/tutorials.mdwn,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- wikisrc/tutorials.mdwn 12 Nov 2011 16:31:08 -0000 1.16 +++ wikisrc/tutorials.mdwn 13 May 2012 10:45:06 -0000 1.17 @@ -20,6 +20,7 @@ ### Kernel * [[kernel debugging with QEMU]] +* [[NetBSD kernel development Setup]] ### Testing * [[atf]]
Index: wikisrc/pkgsrc/targets.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/pkgsrc/targets.mdwn,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- wikisrc/pkgsrc/targets.mdwn 20 Aug 2011 12:27:02 -0000 1.11 +++ wikisrc/pkgsrc/targets.mdwn 3 May 2012 01:33:02 -0000 1.12 @@ -23,6 +23,8 @@ * **package-install** to install package and build binary package * **install** to install package * **bin-install** to attempt to skip building from source and use pre-built binary package +* **show-depends** print dependencies for building +* **show-options** print available options from options.mk Cleanup targets (in separate section because of importance):
Changed pages:
ports/hpcarm
ports/sparc64
Changed by: mspo
Commit type: cvs
Date: Sunday evening 04/29/12
first attempt for sparc64 and hpcarm
--- /dev/null 2012-04-29 17:52:14.000000000 +0000 +++ wikisrc/ports/hpcarm.mdwn 2012-04-29 18:02:46.000000000 +0000 @@ -0,0 +1,227 @@ +[[!template id=port +port="hpcarm" +cur_rel="5.1.2" +future_rel="6.0" +changes_cur="5.0" +changes_future="6.0" +thumbnail="http://www.netbsd.org/images/ports/hpcarm/ipaq-ws003sh.png" +about=""" +NetBSD/hpcarm brings the NetBSD operating system to [Intel +StrongARM](http://www.intel.com/design/pca/applicationsprocessors/) and XScale +based Windows CE and Windows Mobile PDA machines. + +The port name "hpcarm" was coined from hardwares NetBSD/hpcarm runs: StrongARM +and XScale based systems in Microsoft's H/PC (Handheld PC) form factor. A H/PC +machine contains a keyboard and a touch screen, equipped with 8MB or more RAM. +The port supports the HPC form factor, as well as the H/PC Pro and PsPC +(Palmsized PC). (Many PsPC machines are used by the developers for active +development.) + +NetBSD/hpcarm is an ideal platform for mobile computing applications because +of hardware sizes. And, of course, NetBSD/hpcarm supports all the standard +features you expect NetBSD, such as IPv6 and IPsec. +""" +supported_hardware=""" +<table border="1" id="supported-table"> + <tr align="center"> + <td colspan="10" bgcolor="#b0b0b0"><a class="ulink" href="http://h10025.www1.hp.com/ewfrf/wc/prodTopCategory?product=89332" target="_top">Hewlett-Packard / Compaq Models</a></td> + </tr> + <tr> + <th>Sold in</th> + <th>Model</th> + <th>CPU</th> + <th>Video</th> + <th>RAM</th> + <th>Ports</th> + <th>Boot</th> + <th>PCMCIA Controller</th> + <th>Keymap</th> + <th>Xserver</th> + </tr> + <tr align="center"> + <td>World (disc)</td> + <td>Jornada 710</td> + <td>SA-1110 206MHz</td> + <td>640x240 64K color</td> + <td>32MB</td> + <td>Serial, (IrDA)</td> + <td>Y</td> + <td>Y</td> + <td>Y</td> + <td>Y</td> + </tr> + <tr align="center"> + <td>World (disc)</td> + <td><a class="ulink" href="http://h10025.www1.hp.com/ewfrf/wc/product?lc=en&product=61677" target="_top">Jornada 720</a></td> + <td>SA-1110 206MHz</td> + <td>640x240 64K color</td> + <td>32MB</td> + <td>Serial, (IrDA, modem)</td> + <td>Y</td> + <td>Y</td> + <td>Y</td> + <td>Y</td> + </tr> + <tr align="center"> + <td>World (disc)</td> + <td><a class="ulink" href="http://h10025.www1.hp.com/ewfrf/wc/product?lc=en&product=82118" target="_top">Jornada 728</a></td> + <td>SA-1110 206MHz</td> + <td>640x240 64K color</td> + <td>64MB</td> + <td>Serial, (IrDA, modem)</td> + <td>Y</td> + <td>Y</td> + <td>Y</td> + <td>Y</td> + </tr> + <tr align="center"> + <td>World (disc)</td> + <td><a class="ulink" href="http://h10025.www1.hp.com/ewfrf/wc/product?lc=en&product=58228" target="_top">Jornada 820</a></td> + <td>SA-1100 190MHz</td> + <td>640x480 256 color</td> + <td>16MB</td> + <td>Serial, (IrDA, modem)</td> + <td>Y (root=md)</td> + <td> </td> + <td> </td> + <td> </td> + </tr> + <tr align="center"> + <td>World (disc)</td> + <td><a class="ulink" href="http://h10025.www1.hp.com/ewfrf/wc/prodTopCategory?lc=en&product=96180" target="_top">iPAQ H3600</a></td> + <td>SA-1110 206MHz</td> + <td>240x320 4K color</td> + <td>32MB</td> + <td>Serial, (IrDA, modem)</td> + <td>Y (root=md)</td> + <td>Y</td> + <td> </td> + <td> </td> + </tr> + </table> +<table border="1" id="supported-table2"> + <tr align="center"> + <td colspan="15" bgcolor="#b0b0b0"> + <a class="ulink" href="http://www.sharp.co.jp/ws/" target="_top">WILLCOM / SHARP Mobile Smart + Phones (W-ZERO3 series)</a> +</td> + </tr> + <tr> + <th>Sold in</th> + <th>Model</th> + <th>CPU</th> + <th>Video</th> + <th>RAM</th> + <th>Boot</th> + <th>SD</th> + <th>USB</th> + <th>Wireless LAN</th> + <th>Bluetooth</th> + <th>Keymap</th> + <th>10 Key</th> + <th>touch screen</th> + <th>Xserver</th> + <th>X keymap</th> + </tr> + <tr align="center"> + <td>Japan</td> + <td><a class="ulink" href="http://www.willcom-inc.com/ja/lineup/ws/003sh/" target="_top">WS003SH + (W-ZERO3)</a></td> + <td>PXA270 416MHz</td> + <td>480x640 64K colors</td> + <td>64MB</td> + <td>Y</td> + <td>Y</td> + <td>Y <sup>[<a name="wzero3-usb-cable" href="#ftn.wzero3-usb-cable" class="footnote">a</a>]</sup> + </td> + <td>Y</td> + <td>N/A</td> + <td>Y</td> + <td>N/A</td> + <td>Y</td> + <td>Y</td> + <td>Y</td> + </tr> + + <tr align="center"> + <td>Japan</td> + <td><a class="ulink" href="http://www.willcom-inc.com/ja/lineup/ws/004sh/" target="_top">WS004SH + (W-ZERO3)</a></td> + <td>PXA270 416MHz</td> + <td>480x640 64K colors</td> + <td>64MB</td> + <td>Y</td> + <td>Y</td> + <td>Y <sup>[<a href="#ftn.wzero3-usb-cable" class="footnoteref">a</a>]</sup> +</td> + <td>Y</td> + <td>N/A</td> + <td>Y</td> + <td>N/A</td> + <td>Y</td> + <td>Y</td> + <td>Y</td> + </tr> + <tr align="center"> + <td>Japan</td> + <td><a class="ulink" href="http://www.willcom-inc.com/ja/lineup/ws/007sh/" target="_top">WS007SH + (W-ZERO3[es])</a></td> + <td>PXA270 416MHz</td> + <td>480x640 64K colors</td> + <td>64MB</td> + <td>Y</td> + <td>Y</td> + <td>Y</td> + <td>N/A</td> + <td>N/A</td> + <td>Y</td> + <td>N</td> + <td>Y</td> + <td>Y</td> + <td>Y</td> + </tr> + <tr align="center"> + <td>Japan</td> + <td><a class="ulink" href="http://www.willcom-inc.com/ja/lineup/ws/011sh/" target="_top">WS011SH + (Advanced / W-ZERO3[es])</a></td> + <td>PXA270 520MHz</td> + <td>480x800 64K colors</td> + <td>128MB</td> + <td>Y</td> + <td>Y</td> + <td>Y</td> + <td>N</td> + <td>N/A</td> + <td>Y</td> + <td>Y</td> + <td>Y</td> (Diff truncated)
markdown fixups
Index: wikisrc/ports/evbmips.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/ports/evbmips.mdwn,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- wikisrc/ports/evbmips.mdwn 29 Apr 2012 13:46:32 -0000 1.1 +++ wikisrc/ports/evbmips.mdwn 29 Apr 2012 17:52:14 -0000 1.2 @@ -10,21 +10,20 @@ evaluation boards. """ supported_hardware=""" - * [MIPS Malta evaluation board](http://www.mips.com/products/development-kits/malta/) with either the [4Kc](http://www.mips.com/ProductCatalog/P_MIPS324KFamily/productBrief) (MIPS32) or [5Kc](http://www.mips.com/ProductCatalog/P_MIPS645KFamily/productBrief) (MIPS64) CPU board (running in 32-bit mode only). - * RMI Alchemy based designs + * [MIPS Malta evaluation board](http://www.mips.com/products/development-kits/malta/) with either the [4Kc](http://www.mips.com/ProductCatalog/P_MIPS324KFamily/productBrief) (MIPS32) or [5Kc](http://www.mips.com/ProductCatalog/P_MIPS645KFamily/productBrief) (MIPS64) CPU board (running in 32-bit mode only). + * RMI Alchemy based designs + * [4G Systems MTX-1](http://www.meshcube.org/index_e.html) (MeshCube/AccessCube) + * [RMI Alchemy DBAu1500](http://www.razamicro.com/products_alchemy/au1500_db_dev_board.htm) + * [RMI Alchemy DBAu1550](http://www.razamicro.com/products_alchemy/au1550_dev_product_brief.htm) + * Plat'Home OpenMicroServer (OMSAL-400) - * [4G Systems MTX-1](http://www.meshcube.org/index_e.html) (MeshCube/AccessCube) - * [RMI Alchemy DBAu1500](http://www.razamicro.com/products_alchemy/au1500_db_dev_board.htm) - * [RMI Alchemy DBAu1550](http://www.razamicro.com/products_alchemy/au1550_dev_product_brief.htm) - * Plat'Home OpenMicroServer (OMSAL-400) +### Atheros AR531x based designs - * Atheros AR531x based designs - - * [Atheros AR5001AP](http://www.atheros.com/pt/ar5001AP.html) - * [Linksys WAP55AG 2.0](http://www.linksys.com/) - * [Linksys WRT55AG](http://www.linksys.com/) - * [Meraki Mini](http://www.meraki.net/mini.html) - * [Senao/Engenius 5354AP1 Aries2](http://datacom.engeniustech.com/products_detail.php?name=35&cat=Wireless%20AP/Client%20Bridge/Router) + * [Atheros AR5001AP](http://www.atheros.com/pt/ar5001AP.html) + * [Linksys WAP55AG 2.0](http://www.linksys.com/) + * [Linksys WRT55AG](http://www.linksys.com/) + * [Meraki Mini](http://www.meraki.net/mini.html) + * [Senao/Engenius 5354AP1 Aries2](http://datacom.engeniustech.com/products_detail.php?name=35&cat=Wireless%20AP/Client%20Bridge/Router) """ additional=""" * [Running NetBSD on emulated hardware](../emulators.html)
markdown fixups
Index: wikisrc/ports/evbppc.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/ports/evbppc.mdwn,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- wikisrc/ports/evbppc.mdwn 29 Apr 2012 13:46:32 -0000 1.1 +++ wikisrc/ports/evbppc.mdwn 29 Apr 2012 17:50:57 -0000 1.2 @@ -10,16 +10,16 @@ evaluation boards and appliances. """ supported_hardware=""" - * Network - * Serial ports - * PCI bridge - * Real time clock + * Network + * Serial ports + * PCI bridge + * Real time clock """ unsupported_hardware=""" * Flash * IIC * ROM - +<br /><br /> * IBM PowerPC 405GP based Walnut evaluation board * Marvell PowerPC 750 based [EV-64260](http://www.lynuxworks.com/board-support/marvell/ev-64260a.php) evaluation board * NCD [Explora451](http://www.ncd.com/support/explora/400/) NC
markdown fixups
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /home/wiki/cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/ports/evbarm.mdwn 29 Apr 2012 13:51:44 -0000 1.2
+++ wikisrc/ports/evbarm.mdwn 29 Apr 2012 17:48:26 -0000 1.3
@@ -14,7 +14,7 @@
Jason Thorpe is the maintainer of NetBSD/evbarm.
"""
supported_hardware="""
-* Technologic Systems **TS-7200**
+### Technologic Systems **TS-7200**
The TS-7200 is a low-cost mass-produced PC/104 embedded single board computer
intended as a general purpose core for real embedded applications. The TS-7200
@@ -26,21 +26,21 @@
Support for the TS-7200 was written by Jesse Off
- * On-CPU RS232 UARTs (2) (_epcom_)
- * On-CPU 10/100 Ethernet MAC (_epe_)
- * CompactFlash socket (_wdc_)
- * USB 1.1 ports (2) (_ohci_)
- * Watchdog timer on CPLD (_tspld_)
- * TMP124 high precision temperature sensor via sysctl
- * 64Hz system clock from on-CPU timers (_epclk_)
- * HD44780 2x24 text mode LCD (_tslcd_)
- * 4x4 16 button matrix keypad (_wskbd_)
- * TS-5620 battery backed RTC daughter-card (_tsrtc_)
- * 1,2,4 port serial TS-SER daughter cards (_com_)
- * Up to 4 10Mb TS-ETH10 daughter cards (_tscs_)
- * Other devices inserted into the PC/104 (_isa_) expansion slot
+* On-CPU RS232 UARTs (2) (_epcom_)
+* On-CPU 10/100 Ethernet MAC (_epe_)
+* CompactFlash socket (_wdc_)
+* USB 1.1 ports (2) (_ohci_)
+* Watchdog timer on CPLD (_tspld_)
+* TMP124 high precision temperature sensor via sysctl
+* 64Hz system clock from on-CPU timers (_epclk_)
+* HD44780 2x24 text mode LCD (_tslcd_)
+* 4x4 16 button matrix keypad (_wskbd_)
+* TS-5620 battery backed RTC daughter-card (_tsrtc_)
+* 1,2,4 port serial TS-SER daughter cards (_com_)
+* Up to 4 10Mb TS-ETH10 daughter cards (_tscs_)
+* Other devices inserted into the PC/104 (_isa_) expansion slot
-* ARM, Ltd. **Integrator**
+### ARM, Ltd. **Integrator**
The Integrator/AP is an ATX form-factor board that is used for development of
ARM processor-based designs. It supports up to four processors on plug-in core
@@ -56,7 +56,7 @@
* PrimeCell PL030 Real-time Clock in the System Controller FPGA (_plrtc_)
* Other devices inserted into the PCI expansion slots
-* Intel **IQ31244**
+### Intel **IQ31244**
The IQ31244 is a development platform for the Intel **IOP321** I/O Processor
chipset and the Intel **i31244** SATA controller.
@@ -73,7 +73,7 @@
* On-board compact flash reader (_wdc_)
* Other devices inserted into the PCI-X expansion slot
-* Intel **IQ80310**
+### Intel **IQ80310**
The IQ80310 is the reference platform for the Intel **IOP310** I/O Processor
chipset, which is comprised of the i80200 XScale processor and the i80312 I/O
@@ -87,7 +87,7 @@
* On-board NS16550-compatible serial ports (_com_)
* Other devices inserted into the PCI expansion slots
-* Intel **IQ80321**
+### Intel **IQ80321**
The IQ80321 is the reference platform for the Intel **IOP321** I/O Processor
(i80321 XScale processor).
@@ -102,7 +102,7 @@
* On-chip watchdog timer (_iopwdog_)
* Other devices inserted into the PCI-X expansion slots
-* Team ASA, Inc. **Npwr**
+### Team ASA, Inc. **Npwr**
The Npwr is an IOP310-based design targeted at the network-attached storage
space. The Npwr comes in several configurations (single or dual Gigabit
@@ -118,7 +118,7 @@
* On-board timer in the CPLD (used as system clock)
* On-board NS16550-compatible serial port (_com_)
-* Intel **IXM1200**
+### Intel **IXM1200**
The IXM1200 is the reference platform for the Intel **IXP1200** Network
Processor.
@@ -130,7 +130,7 @@
* On-chip timers (ixpclk0 used as system clock)
* On-chip serial port (_ixpcom_)
-* Samsung **SMDK2410**
+### Samsung **SMDK2410**
The SMDK2410 is the reference platform for the Samsung **S3C2410** processor,
which has an ARM920T core.
@@ -149,7 +149,7 @@
* 240x320 TFT LCD (_lcd_)
* keyboard. (_sskbd_)
-* Samsung **SMDK2800**
+### Samsung **SMDK2800**
The SMDK2800 is the reference platform for the **Samsung S3C2800** processor,
which has an ARM920T core.
@@ -164,7 +164,7 @@
* On-chip timers (used as system clock)
* Other devices inserted into the PCI slots
-* ADI Engineering **BRH** ("Big Red Head")
+### ADI Engineering **BRH** ("Big Red Head")
The BRH is an evaluation and development platform for the Intel **i80200**
XScale processor. The BRH is based on ADI's **BECC** ("Big Endian Companion
@@ -186,7 +186,7 @@
systems should obtain an FPGA upgrade from ADI to revision 8 or later of the
BECC.
-* NOVATEC **NTNP425B** ("ZAO425")
+### NOVATEC **NTNP425B** ("ZAO425")
NTNP425B is an evaluation and development platform for the Intel **IXP425**
XScale Core NetworkProcessor. NTNP425B is based on the reference board of
@@ -203,12 +203,10 @@
* Other devices inserted into the PCI/mPCI slot
* On-chip watchdog timer (_ixpwdog_)
-* Intel **DBPXA250** ("Lubbock")
+### Intel **DBPXA250** ("Lubbock")
DBPXA250 (a.k.a. Lubbock) is an evaluation and development platform for the
-Intel **PXA250** XScale Core application processor. More information about the
-**DBPXA250** can be found at [Intel web
-site](http://www.intel.com/design/pca/applicationsprocessors/swsup/index.htm).
+Intel **PXA250** XScale Core application processor. More information about the **DBPXA250** can be found at [Intel website](http://www.intel.com/design/pca/applicationsprocessors/swsup/index.htm).
Support for the **DBPXA250** was written by Hiroyuki Bessho, and contributed
by Genetec Corp.
@@ -221,7 +219,7 @@
* 640x480 LCD (_lcd_)
* PCMCIA and CF card slots
-* Arcom **Viper**
+### Arcom **Viper**
The Arcom Viper is a single board computer based on the PXA255 XScale
processor.
@@ -232,7 +230,7 @@
* On-chip serial ports (_com_)
* On-board SMC91C111 ethernet (_sm_)
-* Atmark Techno **Armadillo-9**
+### Atmark Techno **Armadillo-9**
The Armadillo-9 is a single board computer based on the EP9315 processor.
@@ -244,7 +242,7 @@
* CompactFlash socket (_eppcic_)
* USB 1.1 ports (_ohci_)
-* Gumstix, Inc. **gumstix**
+### Gumstix, Inc. **gumstix**
The [gumstix](http://www.gumstix.com/) is a small form-factor motherboard
based on the PXA255 and PXA270 XScale processor. Supports only PXA255 now.
@@ -261,7 +259,7 @@
When booting, it is necessary to set these with u-boot dynamically.
-> go 0xa0200000 busheader=basix
+<pre> > go 0xa0200000 busheader=basix</pre>
* audiostix
* console-st (waysmall - STUART)
Changed pages:
ports/evbarm
Changed by: mspo
Commit type: cvs
Date: at lunch time on Sunday 04/29/12
markdown fixups, mostly whitespace
Index: wikisrc/ports/evbarm.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/ports/evbarm.mdwn,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- wikisrc/ports/evbarm.mdwn 29 Apr 2012 13:46:32 -0000 1.1 +++ wikisrc/ports/evbarm.mdwn 29 Apr 2012 13:51:44 -0000 1.2 @@ -14,7 +14,7 @@ Jason Thorpe is the maintainer of NetBSD/evbarm. """ supported_hardware=""" - * Technologic Systems **TS-7200** +* Technologic Systems **TS-7200** The TS-7200 is a low-cost mass-produced PC/104 embedded single board computer intended as a general purpose core for real embedded applications. The TS-7200 @@ -26,21 +26,21 @@ Support for the TS-7200 was written by Jesse Off - * On-CPU RS232 UARTs (2) (_epcom_) - * On-CPU 10/100 Ethernet MAC (_epe_) - * CompactFlash socket (_wdc_) - * USB 1.1 ports (2) (_ohci_) - * Watchdog timer on CPLD (_tspld_) - * TMP124 high precision temperature sensor via sysctl - * 64Hz system clock from on-CPU timers (_epclk_) - * HD44780 2x24 text mode LCD (_tslcd_) - * 4x4 16 button matrix keypad (_wskbd_) - * TS-5620 battery backed RTC daughter-card (_tsrtc_) - * 1,2,4 port serial TS-SER daughter cards (_com_) - * Up to 4 10Mb TS-ETH10 daughter cards (_tscs_) - * Other devices inserted into the PC/104 (_isa_) expansion slot + * On-CPU RS232 UARTs (2) (_epcom_) + * On-CPU 10/100 Ethernet MAC (_epe_) + * CompactFlash socket (_wdc_) + * USB 1.1 ports (2) (_ohci_) + * Watchdog timer on CPLD (_tspld_) + * TMP124 high precision temperature sensor via sysctl + * 64Hz system clock from on-CPU timers (_epclk_) + * HD44780 2x24 text mode LCD (_tslcd_) + * 4x4 16 button matrix keypad (_wskbd_) + * TS-5620 battery backed RTC daughter-card (_tsrtc_) + * 1,2,4 port serial TS-SER daughter cards (_com_) + * Up to 4 10Mb TS-ETH10 daughter cards (_tscs_) + * Other devices inserted into the PC/104 (_isa_) expansion slot - * ARM, Ltd. **Integrator** +* ARM, Ltd. **Integrator** The Integrator/AP is an ATX form-factor board that is used for development of ARM processor-based designs. It supports up to four processors on plug-in core @@ -52,11 +52,11 @@ Support for the Integrator was written by Richard Earnshaw, and contributed by ARM, Ltd. - * PrimeCell PL010 UARTs in the System Controller FPGA (_plcom_) - * PrimeCell PL030 Real-time Clock in the System Controller FPGA (_plrtc_) - * Other devices inserted into the PCI expansion slots + * PrimeCell PL010 UARTs in the System Controller FPGA (_plcom_) + * PrimeCell PL030 Real-time Clock in the System Controller FPGA (_plrtc_) + * Other devices inserted into the PCI expansion slots - * Intel **IQ31244** +* Intel **IQ31244** The IQ31244 is a development platform for the Intel **IOP321** I/O Processor chipset and the Intel **i31244** SATA controller. @@ -64,16 +64,16 @@ Initial support for the IQ31244 was written by Jason Thorpe, and contributed by Wasabi Systems, Inc. - * Quad on-board Intel i31244 SATA controllers on the PCI-X bus (_artsata_) - * On-board Intel i82546EB Gigabit Ethernet on the PCI-X bus (_wm_) - * On-board NS16550-compatible serial port (_com_) - * On-chip timers (TMR0 used as system clock) - * On-chip Application Accelerator Unit (_iopaau_) - * On-chip watchdog timer (_iopwdog_) - * On-board compact flash reader (_wdc_) - * Other devices inserted into the PCI-X expansion slot + * Quad on-board Intel i31244 SATA controllers on the PCI-X bus (_artsata_) + * On-board Intel i82546EB Gigabit Ethernet on the PCI-X bus (_wm_) + * On-board NS16550-compatible serial port (_com_) + * On-chip timers (TMR0 used as system clock) + * On-chip Application Accelerator Unit (_iopaau_) + * On-chip watchdog timer (_iopwdog_) + * On-board compact flash reader (_wdc_) + * Other devices inserted into the PCI-X expansion slot - * Intel **IQ80310** +* Intel **IQ80310** The IQ80310 is the reference platform for the Intel **IOP310** I/O Processor chipset, which is comprised of the i80200 XScale processor and the i80312 I/O @@ -82,12 +82,12 @@ Support for the IQ80310 was written by Jason Thorpe and Allen Briggs, and contributed by Wasabi Systems, Inc. - * On-board Intel i82559 Ethernet on the PCI bus (_fxp_) - * On-board timer in the CPLD (used as system clock) - * On-board NS16550-compatible serial ports (_com_) - * Other devices inserted into the PCI expansion slots + * On-board Intel i82559 Ethernet on the PCI bus (_fxp_) + * On-board timer in the CPLD (used as system clock) + * On-board NS16550-compatible serial ports (_com_) + * Other devices inserted into the PCI expansion slots - * Intel **IQ80321** +* Intel **IQ80321** The IQ80321 is the reference platform for the Intel **IOP321** I/O Processor (i80321 XScale processor). @@ -95,14 +95,14 @@ Support for the IQ80321 was written by Jason Thorpe, and contributed by Wasabi Systems, Inc. - * On-board Intel i82544EI Gigabit Ethernet on the PCI-X bus (_wm_) - * On-board NS16550-compatible serial port (_com_) - * On-chip timers (TMR0 used as system clock) - * On-chip Application Accelerator Unit (_iopaau_) - * On-chip watchdog timer (_iopwdog_) - * Other devices inserted into the PCI-X expansion slots + * On-board Intel i82544EI Gigabit Ethernet on the PCI-X bus (_wm_) + * On-board NS16550-compatible serial port (_com_) + * On-chip timers (TMR0 used as system clock) + * On-chip Application Accelerator Unit (_iopaau_) + * On-chip watchdog timer (_iopwdog_) + * Other devices inserted into the PCI-X expansion slots - * Team ASA, Inc. **Npwr** +* Team ASA, Inc. **Npwr** The Npwr is an IOP310-based design targeted at the network-attached storage space. The Npwr comes in several configurations (single or dual Gigabit @@ -113,24 +113,24 @@ Support for the Npwr was written by Jason Thorpe and Allen Briggs, and contributed by Wasabi Systems, Inc. - * On-board Intel i82544 Gigabit Ethernet on the PCI bus (_wm_) - * On-board LSI Logic 53c1010 Ultra160 SCSI on the PCI bus (_siop_) - * On-board timer in the CPLD (used as system clock) - * On-board NS16550-compatible serial port (_com_) + * On-board Intel i82544 Gigabit Ethernet on the PCI bus (_wm_) + * On-board LSI Logic 53c1010 Ultra160 SCSI on the PCI bus (_siop_) + * On-board timer in the CPLD (used as system clock) + * On-board NS16550-compatible serial port (_com_) - * Intel **IXM1200** +* Intel **IXM1200** The IXM1200 is the reference platform for the Intel **IXP1200** Network Processor. Support for the IXM1200 was written by Ichiro FUKUHARA and Naoto Shimazaki. - * On-board Intel i82559 Ethernet on the PCI bus (_fxp_) - * On-board Intel i21555 Non-Transparent PCI-PCI Bridge (_nppb_) - * On-chip timers (ixpclk0 used as system clock) - * On-chip serial port (_ixpcom_) + * On-board Intel i82559 Ethernet on the PCI bus (_fxp_) + * On-board Intel i21555 Non-Transparent PCI-PCI Bridge (_nppb_) + * On-chip timers (ixpclk0 used as system clock) + * On-chip serial port (_ixpcom_) - * Samsung **SMDK2410** +* Samsung **SMDK2410** The SMDK2410 is the reference platform for the Samsung **S3C2410** processor, which has an ARM920T core. @@ -142,14 +142,14 @@ Support for the SMDK2410 was written by Hiroyuki Bessho, and contributed by Genetec Corp. - * On-chip serial ports (_sscom_) - * On-chip USB host controller (_ohc_) - * On-chip timers (used as system clock) - * On-chip SPI (_ssspi_, used for other on-board devices) - * 240x320 TFT LCD (_lcd_) - * keyboard. (_sskbd_) + * On-chip serial ports (_sscom_) + * On-chip USB host controller (_ohc_) + * On-chip timers (used as system clock) + * On-chip SPI (_ssspi_, used for other on-board devices) + * 240x320 TFT LCD (_lcd_) + * keyboard. (_sskbd_) - * Samsung **SMDK2800** +* Samsung **SMDK2800** The SMDK2800 is the reference platform for the **Samsung S3C2800** processor, which has an ARM920T core. @@ -159,12 +159,12 @@ Support for the SMDK2800 was written by Hiroyuki Bessho, and contributed by Fujitsu Component Ltd., and Genetec Corp. - * On-chip serial ports (_sscom_) - * On-chip Host-PCI bridge (_sspci_) - * On-chip timers (used as system clock) - * Other devices inserted into the PCI slots (Diff truncated)
Changed pages:
ports/amd64
ports/evbarm
ports/evbmips
ports/evbppc
ports/xen
Changed by: mspo
Commit type: cvs
Date: at lunch time on Sunday 04/29/12
more copies to port pages to markdown/ports template -- first try
Index: wikisrc/ports/amd64.mdwn
===================================================================
RCS file: /home/wiki/cvsroot/wikisrc/ports/amd64.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/ports/amd64.mdwn 17 Apr 2012 08:39:56 -0000 1.5
+++ wikisrc/ports/amd64.mdwn 29 Apr 2012 13:46:32 -0000 1.6
@@ -13,9 +13,7 @@
NetBSD/amd64 is a true 64bit operating system. Running
32bit NetBSD/i386 binaries is supported as well, see
-<a href="http://netbsd.gw.com/cgi-bin/man-cgi?compat_netbsd32+8+NetBSD-5.1+i386">compat_netbsd32(8)</a>. Running 32bit Linux emulations will
-be available in the future, the setup will be similar to
-the one described in <a href="http://netbsd.gw.com/cgi-bin/man-cgi?compat_svr4_32+8+NetBSD-5.1+i386">compat_svr4_32(8)</a>.
+<a href="http://netbsd.gw.com/cgi-bin/man-cgi?compat_netbsd32+8+NetBSD-5.1+i386">compat_netbsd32(8)</a>.
The port was first committed to the NetBSD source tree as NetBSD/x86_64
on June 19th, 2001 and renamed to NetBSD/amd64 on April 26th, 2003.
--- /dev/null 2012-04-29 06:10:10.000000000 +0000
+++ wikisrc/ports/evbarm.mdwn 2012-04-29 13:46:34.000000000 +0000
@@ -0,0 +1,278 @@
+[[!template id=port
+port="evbarm"
+cur_rel="5.1.2"
+future_rel="6.0"
+changes_cur="5.0"
+changes_future="6.0"
+thumbnail="http://www.netbsd.org/images/ports/evbarm/adi_brh.gif"
+about="""
+NetBSD/evbarm is the port of NetBSD to various evaluation and prototyping
+boards based on CPUs implementing the ARM architecture. NetBSD/evbarm also
+supports some specific embedded system products based on prototype board
+designs.
+
+Jason Thorpe is the maintainer of NetBSD/evbarm.
+"""
+supported_hardware="""
+ * Technologic Systems **TS-7200**
+
+The TS-7200 is a low-cost mass-produced PC/104 embedded single board computer
+intended as a general purpose core for real embedded applications. The TS-7200
+uses the Cirrus Logic EP9302 ARM9 system-on-chip and comes with a PC/104 (isa)
+bus and can either boot to CompactFlash or onboard flash. The board also has
+general purpose digital IO and optional multichannel analog-to-digital
+converters. More information on the TS-7200 can be found at [Technologic
+Systems](http://www.embeddedarm.com/epc/ts7200-spec-h.html).
+
+Support for the TS-7200 was written by Jesse Off
+
+ * On-CPU RS232 UARTs (2) (_epcom_)
+ * On-CPU 10/100 Ethernet MAC (_epe_)
+ * CompactFlash socket (_wdc_)
+ * USB 1.1 ports (2) (_ohci_)
+ * Watchdog timer on CPLD (_tspld_)
+ * TMP124 high precision temperature sensor via sysctl
+ * 64Hz system clock from on-CPU timers (_epclk_)
+ * HD44780 2x24 text mode LCD (_tslcd_)
+ * 4x4 16 button matrix keypad (_wskbd_)
+ * TS-5620 battery backed RTC daughter-card (_tsrtc_)
+ * 1,2,4 port serial TS-SER daughter cards (_com_)
+ * Up to 4 10Mb TS-ETH10 daughter cards (_tscs_)
+ * Other devices inserted into the PC/104 (_isa_) expansion slot
+
+ * ARM, Ltd. **Integrator**
+
+The Integrator/AP is an ATX form-factor board that is used for development of
+ARM processor-based designs. It supports up to four processors on plug-in core
+modules, and provides clocks, a bus interface, and interrupt support. The
+Integrator/AP also supports logic modules which provide additional
+peripherals, and can accommodate up to three PCI expansion cards. The
+Integrator/AP can also be inserted into a CompactPCI backplane.
+
+Support for the Integrator was written by Richard Earnshaw, and contributed by
+ARM, Ltd.
+
+ * PrimeCell PL010 UARTs in the System Controller FPGA (_plcom_)
+ * PrimeCell PL030 Real-time Clock in the System Controller FPGA (_plrtc_)
+ * Other devices inserted into the PCI expansion slots
+
+ * Intel **IQ31244**
+
+The IQ31244 is a development platform for the Intel **IOP321** I/O Processor
+chipset and the Intel **i31244** SATA controller.
+
+Initial support for the IQ31244 was written by Jason Thorpe, and contributed
+by Wasabi Systems, Inc.
+
+ * Quad on-board Intel i31244 SATA controllers on the PCI-X bus (_artsata_)
+ * On-board Intel i82546EB Gigabit Ethernet on the PCI-X bus (_wm_)
+ * On-board NS16550-compatible serial port (_com_)
+ * On-chip timers (TMR0 used as system clock)
+ * On-chip Application Accelerator Unit (_iopaau_)
+ * On-chip watchdog timer (_iopwdog_)
+ * On-board compact flash reader (_wdc_)
+ * Other devices inserted into the PCI-X expansion slot
+
+ * Intel **IQ80310**
+
+The IQ80310 is the reference platform for the Intel **IOP310** I/O Processor
+chipset, which is comprised of the i80200 XScale processor and the i80312 I/O
+Companion chip.
+
+Support for the IQ80310 was written by Jason Thorpe and Allen Briggs, and
+contributed by Wasabi Systems, Inc.
+
+ * On-board Intel i82559 Ethernet on the PCI bus (_fxp_)
+ * On-board timer in the CPLD (used as system clock)
+ * On-board NS16550-compatible serial ports (_com_)
+ * Other devices inserted into the PCI expansion slots
+
+ * Intel **IQ80321**
+
+The IQ80321 is the reference platform for the Intel **IOP321** I/O Processor
+(i80321 XScale processor).
+
+Support for the IQ80321 was written by Jason Thorpe, and contributed by Wasabi
+Systems, Inc.
+
+ * On-board Intel i82544EI Gigabit Ethernet on the PCI-X bus (_wm_)
+ * On-board NS16550-compatible serial port (_com_)
+ * On-chip timers (TMR0 used as system clock)
+ * On-chip Application Accelerator Unit (_iopaau_)
+ * On-chip watchdog timer (_iopwdog_)
+ * Other devices inserted into the PCI-X expansion slots
+
+ * Team ASA, Inc. **Npwr**
+
+The Npwr is an IOP310-based design targeted at the network-attached storage
+space. The Npwr comes in several configurations (single or dual Gigabit
+Ethernet, single or dual Ultra160 SCSI), and can be purchased as a bare board
+or as a small server appliance. More information on the Npwr can be found at
+the [Team ASA web page](http://www.teamasa.com/).
+
+Support for the Npwr was written by Jason Thorpe and Allen Briggs, and
+contributed by Wasabi Systems, Inc.
+
+ * On-board Intel i82544 Gigabit Ethernet on the PCI bus (_wm_)
+ * On-board LSI Logic 53c1010 Ultra160 SCSI on the PCI bus (_siop_)
+ * On-board timer in the CPLD (used as system clock)
+ * On-board NS16550-compatible serial port (_com_)
+
+ * Intel **IXM1200**
+
+The IXM1200 is the reference platform for the Intel **IXP1200** Network
+Processor.
+
+Support for the IXM1200 was written by Ichiro FUKUHARA and Naoto Shimazaki.
+
+ * On-board Intel i82559 Ethernet on the PCI bus (_fxp_)
+ * On-board Intel i21555 Non-Transparent PCI-PCI Bridge (_nppb_)
+ * On-chip timers (ixpclk0 used as system clock)
+ * On-chip serial port (_ixpcom_)
+
+ * Samsung **SMDK2410**
+
+The SMDK2410 is the reference platform for the Samsung **S3C2410** processor,
+which has an ARM920T core.
+
+More information on the S3C2410 can be found at [Samsung Electronics web page]
+(http://www.samsung.com/Products/Semiconductor/MobileSoC/ApplicationProcessor/
+ARM9Series/S3C2410/S3C2410.htm).
+
+Support for the SMDK2410 was written by Hiroyuki Bessho, and contributed by
+Genetec Corp.
+
+ * On-chip serial ports (_sscom_)
+ * On-chip USB host controller (_ohc_)
+ * On-chip timers (used as system clock)
+ * On-chip SPI (_ssspi_, used for other on-board devices)
+ * 240x320 TFT LCD (_lcd_)
+ * keyboard. (_sskbd_)
+
+ * Samsung **SMDK2800**
+
+The SMDK2800 is the reference platform for the **Samsung S3C2800** processor,
+which has an ARM920T core.
+
+S3C2800 has built-in PCI controller, and SMDK2800 has three PCI slots.
+
+Support for the SMDK2800 was written by Hiroyuki Bessho, and contributed by
+Fujitsu Component Ltd., and Genetec Corp.
+
+ * On-chip serial ports (_sscom_)
+ * On-chip Host-PCI bridge (_sspci_)
+ * On-chip timers (used as system clock)
+ * Other devices inserted into the PCI slots
+
+ * ADI Engineering **BRH** ("Big Red Head")
+
+The BRH is an evaluation and development platform for the Intel **i80200**
+XScale processor. The BRH is based on ADI's **BECC** ("Big Endian Companion
+Chip"). The BRH is capable of both big- and little-endian operation, although
+NetBSD currently only supports little-endian operation. More information about
+the BRH can be found on [ADI Engineering's web
+page](http://www.adiengineering.com/productsBRH.html).
+
+Support for the BRH was written by Jason Thorpe, and contributed by Wasabi
+Systems, Inc.
+
(Diff truncated)
Changed pages:
projects/project/libvirt
Changed by: jym
Commit type: web
Date: Thursday afternoon 04/26/12
Update libvirt project, now that we have a package for it in pkgsrc.
Index: wikisrc/projects/project/libvirt.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/libvirt.mdwn,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- wikisrc/projects/project/libvirt.mdwn 6 Nov 2011 19:58:46 -0000 1.1 +++ wikisrc/projects/project/libvirt.mdwn 26 Apr 2012 16:50:59 -0000 1.2 @@ -1,6 +1,6 @@ [[!template id=project -title="Add libvirt in pkgsrc" +title="Improve libvirt support in NetBSD pkgsrc" contact=""" [tech-pkg](mailto:tech-pkg@NetBSD.org), [port-xen](mailto:port-xen@NetBSD.org) @@ -12,15 +12,20 @@ category="misc" difficulty="easy" -duration="2-3 weeks" +duration="1-3 weeks, depending on targetted operating system" description=""" [Libvirt](http://www.libvirt.org) is a project that aims at bringing yet-another-level of abstraction to the management of different virtualization -technologies. It supports a wide range of systems (including Xen), however -pkgsrc does not yet offer a package to install libvirt. The purpose of this -project is to investigate what is needed to build libvirt as a standalone -package within pkgsrc, and integrate it so it can benefit from pkgsrc's -portability across many different OS. +technologies; it supports a wide range of virtualization technologies, like Xen, VMWare, KVM and containers. + +A package for +libvirt was added to pkgsrc under [[!template id=pkg category="sysutils" name="libvirt"]], however it requires more testing before +all platforms supported by pkgsrc can also seamlessly support libvirt. + +The purpose of this +project is to investigate what is missing in libvirt (in terms of patches or system integration) +so it can work out-of-the-box for platforms that can benefit from it. GNU/Linux, NetBSD, FreeBSD and +Solaris are the main targets. """ ]]
Changed pages:
amazon ec2/amis
Changed by: riz
Commit type: web
Date: in the wee hours of Saturday night 04/22/12
More updates. Fill in rest of x86_64 5.1.2 AMIs
Index: wikisrc/amazon_ec2/amis.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/amazon_ec2/amis.mdwn,v retrieving revision 1.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- wikisrc/amazon_ec2/amis.mdwn 21 Apr 2012 16:53:20 -0000 1.19 +++ wikisrc/amazon_ec2/amis.mdwn 22 Apr 2012 03:57:53 -0000 1.20 @@ -24,13 +24,13 @@ </tr> <tr> <th>NetBSD 5.1.2</th><!-- Version --> - <td></td><!-- us-east-1 --> + <td>ami-98904bf1</td><!-- us-east-1 --> <td>ami-6d267d28</td><!-- us-west-1 --> - <td></td><!-- us-west-2 --> + <td>ami-04f37f34</td><!-- us-west-2 --> <td>ami-e93d069d</td><!-- eu-west-1 --> - <td></td><!-- ap-southeast-1 --> - <td></td><!-- ap-northeast-1 --> - <td></td><!-- sa-east-1 --> + <td>ami-caa9ee98</td><!-- ap-southeast-1 --> + <td>ami-10e25211</td><!-- ap-northeast-1 --> + <td>ami-5ca17f41</td><!-- sa-east-1 --> </tr> <tr> <th>NetBSD 5.1</th> @@ -77,7 +77,7 @@ <td>ami-f0f27ec0</td><!-- us-west-2 --> <td>ami-27477c53</td><!-- eu-west-1 --> <td>ami-5c55110e</td><!-- ap-southeast-1 --> - <td>ami-9c6bdd9d</td><!-- ap-northeast-1 --> + <td>ami-a8fb4ba9</td><!-- ap-northeast-1 --> <td>ami-e6a37dfb</td><!-- sa-east-1 --> </tr> <tr>
Update 5.1.2 eu-west-1 i386, fix 5.1.2 i386 us-west-1, add some comments, add some amd64 5.1.2
Index: wikisrc/amazon_ec2/amis.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/amazon_ec2/amis.mdwn,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- wikisrc/amazon_ec2/amis.mdwn 21 Apr 2012 04:34:18 -0000 1.18 +++ wikisrc/amazon_ec2/amis.mdwn 21 Apr 2012 16:53:20 -0000 1.19 @@ -23,6 +23,16 @@ <th>sa-east-1<br />(Sao Paulo)</th> </tr> <tr> + <th>NetBSD 5.1.2</th><!-- Version --> + <td></td><!-- us-east-1 --> + <td>ami-6d267d28</td><!-- us-west-1 --> + <td></td><!-- us-west-2 --> + <td>ami-e93d069d</td><!-- eu-west-1 --> + <td></td><!-- ap-southeast-1 --> + <td></td><!-- ap-northeast-1 --> + <td></td><!-- sa-east-1 --> +</tr> +<tr> <th>NetBSD 5.1</th> <td>ami-2da67644</td> <td>ami-a7742de2</td> @@ -34,13 +44,13 @@ </tr> <tr> <th>NetBSD 6.0_BETA</th> - <td>ami-a817ccc1</td> - <td>ami-d54e1590</td> - <td>ami-288a0618</td> - <td>ami-29172c5d</td> - <td>ami-963d7ac4</td> - <td>ami-d6d464d7</td> - <td>ami-3edd0323</td> + <td>ami-a817ccc1</td><!-- us-east-1 --> + <td>ami-d54e1590</td><!-- us-west-1 --> + <td>ami-288a0618</td><!-- us-west-2 --> + <td>ami-29172c5d</td><!-- eu-west-1 --> + <td>ami-963d7ac4</td><!-- ap-southeast-1 --> + <td>ami-d6d464d7</td><!-- ap-northeast-1 --> + <td>ami-3edd0323</td><!-- sa-east-1 --> </tr> </table> @@ -61,23 +71,23 @@ <th>sa-east-1<br />(Sao Paulo)</th> </tr> <tr> - <th>NetBSD 5.1.2</th> - <td>ami-0e71a967</td> - <td>ami-472c7702</td> - <td>ami-f0f27ec0</td> - <td>ami-81d0eef5</td> - <td>ami-5c55110e</td> - <td>ami-9c6bdd9d</td> - <td>ami-e6a37dfb</td> + <th>NetBSD 5.1.2</th><!-- Version --> + <td>ami-0e71a967</td><!-- us-east-1 --> + <td>ami-472c7702</td><!-- us-west-1 --> + <td>ami-f0f27ec0</td><!-- us-west-2 --> + <td>ami-27477c53</td><!-- eu-west-1 --> + <td>ami-5c55110e</td><!-- ap-southeast-1 --> + <td>ami-9c6bdd9d</td><!-- ap-northeast-1 --> + <td>ami-e6a37dfb</td><!-- sa-east-1 --> </tr> <tr> <th>NetBSD 6.0_BETA</th> - <td>ami-37805e5e</td> - <td>ami-e3d68fa6</td> - <td>ami-eef27ede</td> - <td>ami-a72910d3</td> - <td>ami-c8a2e69a</td> - <td>ami-2405b325</td> - <td>ami-a86db2b5</td> + <td>ami-37805e5e</td><!-- us-east-1 --> + <td>ami-e3d68fa6</td><!-- us-west-1 --> + <td>ami-eef27ede</td><!-- us-west-2 --> + <td>ami-a72910d3</td><!-- eu-west-1 --> + <td>ami-c8a2e69a</td><!-- ap-southeast-1 --> + <td>ami-2405b325</td><!-- ap-northeast-1 --> + <td>ami-a86db2b5</td><!-- sa-east-1 --> </tr> </table>
Changed pages:
amazon ec2/amis
Changed by: riz
Commit type: web
Date: in the wee hours of Friday night 04/21/12
Update us-east-1 i386 5.1.2
Index: wikisrc/amazon_ec2/amis.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/amazon_ec2/amis.mdwn,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- wikisrc/amazon_ec2/amis.mdwn 21 Apr 2012 04:32:55 -0000 1.17 +++ wikisrc/amazon_ec2/amis.mdwn 21 Apr 2012 04:34:18 -0000 1.18 @@ -62,7 +62,7 @@ </tr> <tr> <th>NetBSD 5.1.2</th> - <td>ami-230fdf4a</td> + <td>ami-0e71a967</td> <td>ami-472c7702</td> <td>ami-f0f27ec0</td> <td>ami-81d0eef5</td>
Changed pages:
amazon ec2/amis
Changed by: riz
Commit type: web
Date: in the wee hours of Friday night 04/21/12
Update ap-southeast-1 6.0_BETA
Index: wikisrc/amazon_ec2/amis.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/amazon_ec2/amis.mdwn,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- wikisrc/amazon_ec2/amis.mdwn 21 Apr 2012 04:14:28 -0000 1.16 +++ wikisrc/amazon_ec2/amis.mdwn 21 Apr 2012 04:32:55 -0000 1.17 @@ -28,7 +28,7 @@ <td>ami-a7742de2</td> <td>ami-5c75f86c</td> <td>ami-9df0cee9</td> - <td>ami-a24501f0</td> + <td>ami-d2b9fe80</td> <td>ami-ac78cead</td> <td>ami-4e7ea153</td> </tr>
Changed pages:
amazon ec2/amis
Changed by: riz
Commit type: web
Date: in the wee hours of Friday night 04/21/12
Update sa-east-1 amd64 6.0_BETA and us-west-1 i386 5.1.2
Index: wikisrc/amazon_ec2/amis.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/amazon_ec2/amis.mdwn,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- wikisrc/amazon_ec2/amis.mdwn 21 Apr 2012 04:00:53 -0000 1.15 +++ wikisrc/amazon_ec2/amis.mdwn 21 Apr 2012 04:14:28 -0000 1.16 @@ -40,7 +40,7 @@ <td>ami-29172c5d</td> <td>ami-963d7ac4</td> <td>ami-d6d464d7</td> - <td>ami-5c835d41</td> + <td>ami-3edd0323</td> </tr> </table> @@ -63,7 +63,7 @@ <tr> <th>NetBSD 5.1.2</th> <td>ami-230fdf4a</td> - <td>ami-b14f16f4</td> + <td>ami-472c7702</td> <td>ami-f0f27ec0</td> <td>ami-81d0eef5</td> <td>ami-5c55110e</td>
Changed pages:
amazon ec2/amis
Changed by: riz
Commit type: web
Date: in the wee hours of Friday night 04/21/12
Update 64-bit 6.0_BETA AMIs (except sa-east-1 and ap-southeast-1)
Index: wikisrc/amazon_ec2/amis.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/amazon_ec2/amis.mdwn,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- wikisrc/amazon_ec2/amis.mdwn 17 Apr 2012 17:51:25 -0000 1.14 +++ wikisrc/amazon_ec2/amis.mdwn 21 Apr 2012 04:00:53 -0000 1.15 @@ -34,12 +34,12 @@ </tr> <tr> <th>NetBSD 6.0_BETA</th> - <td>ami-1f8b5576</td> - <td>ami-a383dbe6</td> - <td>ami-2ac04c1a</td> - <td>ami-f71b2383</td> + <td>ami-a817ccc1</td> + <td>ami-d54e1590</td> + <td>ami-288a0618</td> + <td>ami-29172c5d</td> <td>ami-963d7ac4</td> - <td>ami-e07fcee1</td> + <td>ami-d6d464d7</td> <td>ami-5c835d41</td> </tr> </table>
Changed pages:
templates/port
Changed by: mspo
Commit type: cvs
Date: in the wee hours of Tuesday night 04/18/12
whitespace issues in markdown
Index: wikisrc/templates/port.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/templates/port.mdwn,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- wikisrc/templates/port.mdwn 18 Apr 2012 02:54:54 -0000 1.8 +++ wikisrc/templates/port.mdwn 18 Apr 2012 02:56:28 -0000 1.9 @@ -20,6 +20,7 @@ | <a href="http://mail-index.NetBSD.org/port-<TMPL_VAR port>/">archive</a> ] + <a href="mailto:port-<TMPL_VAR port>-maintainer@NetBSD.org">Mail the NetBSD/<TMPL_VAR port> port maintainer</a> <TMPL_IF supported_hardware>
Changed pages:
ports/sparc
Changed by: mspo
Commit type: cvs
Date: in the wee hours of Tuesday night 04/18/12
fix up and template a little more - try to align the mailing list links with the current [ foo | bar ] look
Index: wikisrc/ports/sparc.mdwn
===================================================================
RCS file: /home/wiki/cvsroot/wikisrc/ports/sparc.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/sparc.mdwn 15 Apr 2012 21:15:42 -0000 1.1
+++ wikisrc/ports/sparc.mdwn 18 Apr 2012 02:54:39 -0000 1.2
@@ -28,8 +28,7 @@
marked </em></span>'(SMP)'<span class="emphasis"><em>can have multiple CPUs but NetBSD/sparc does not
use more than one CPU prior to release 2.0</em></span>
-<ul class="itemizedlist" type="disc">
-<li class="listitem">Sun sun4m machines (all known SuperSPARC, hyperSPARC,
+*Sun sun4m machines (all known SuperSPARC, hyperSPARC,
microSPARC, and TurboSPARC CPUs are supported):
<div class="itemizedlist"><ul class="itemizedlist" type="circle">
<li class="listitem">Sun 4/600 (<a class="ulink" href="faq.html#smp-cpus" target="_top">SMP</a>)</li>
@@ -42,20 +41,15 @@
<li class="listitem">SPARCstation Voyager
<span class="emphasis"><em>(See the <a class="ulink" href="faq.html#nell" target="_top">FAQ</a>
regarding PCMCIA support)</em></span>
-</li>
<li class="listitem">Sun '<a class="ulink" href="faq.html#fox" target="_top">Fox</a>'</li>
<li class="listitem">
<a class="ulink" href="javastation.html#mrcoffe" target="_top">JavaStation-1</a> (a.k.a.
"Mr. Coffee" or JavaStation JJ)
<span class="emphasis"><em>(2.0)</em></span>
-</li>
<li class="listitem">
<a class="ulink" href="javastation.html#krups" target="_top">JavaStation-NC</a> (a.k.a.
Krups, JavaStation JK, or JavaStation-10)
<span class="emphasis"><em>(2.0)</em></span>
-</li>
-</ul>
-</li>
<li class="listitem">Sun4m compatibles (including):
<ul class="itemizedlist" type="circle">
<li class="listitem">Axil 245 (SS5 clone), 311, 320 (SS20 clone)</li>
@@ -68,8 +62,6 @@
<li class="listitem">Twinhead TWINstation 5G (SS5 clone)</li>
<li class="listitem">TWS,SuperCOMPstation-20S</li>
<li class="listitem">Tadpole SPARCbook 3GS and 3GX</li>
-</ul>
-</li>
<li class="listitem">Sun sun4c machines:
<ul class="itemizedlist" type="circle">
<li class="listitem">SPARCstation/server 1</li>
@@ -79,8 +71,6 @@
<li class="listitem">Sun IPC</li>
<li class="listitem">Sun IPX</li>
<li class="listitem">Sun SLC</li>
-</ul>
-</li>
<li class="listitem">Sun4c compatibles (including):
<ul class="itemizedlist" type="circle">
<li class="listitem">Aries Research Inc, Parrot II (SS2 clone)</li>
@@ -90,18 +80,12 @@
(<span class="emphasis"><em>NetBSD doesn't support VME boards on this model</em></span>)</li>
<li class="listitem">FORCE SPARC CPU2e/4 VME Board (SS2 clone)
<span class="emphasis"><em>NetBSD doesn't support VME boards on this model</em></span>
-</li>
-</ul>
-</li>
<li class="listitem">Sun sun4 machines:
<ul class="itemizedlist" type="circle">
<li class="listitem">Sun 4/100 series</li>
<li class="listitem">Sun 4/200 series</li>
<li class="listitem">Sun 4/300 series</li>
<li class="listitem">Sun 4/400 series</li>
-</ul>
-</li>
-</ul>
<ul class="itemizedlist" type="disc">
<li class="listitem">All on-board and most optional Sun brand framebuffers (all
framebuffers work for text console usage)</li>
@@ -115,12 +99,7 @@
(see <a class="ulink" href="faq.html#nell" target="_top">FAQ</a>)</li>
<li class="listitem">PCMCIA devices with Tadpole ts102 ( SPARCbook 3GX and 3GS ) in -current</li>
<li class="listitem">DBRI audio in -current (output only so far)</li>
-</ul>
-
-<div id="content"><div class="fullWidth"><div class="rowOfBoxes">
<h1>NetBSD/sparc Supported Hardware</h1>
-<h3 class="title"><a name="supported">The following hardware is supported by NetBSD/sparc:</a></h3>
-<ul>
<li><a href="#sum4m-cpu">sun4m mbus CPU modules</a></li>
<li><a href="#sun4c-fb">sun4c and sun4m framebuffers</a></li>
<li><a href="#sun4-fb">sun4 framebuffers</a></li>
@@ -136,7 +115,6 @@
<li><a href="#parallel">Parallel ports</a></li>
<li><a href="#sbus">Miscellaneous sbus devices</a></li>
<li><a href="#unsupported">Devices often asked about, but not yet supported</a></li>
-</ul>
<hr>
<h3 class="title">The following hardware is supported by NetBSD/sparc:</h3>
<p>If you have a device that's not listed, it might be
@@ -160,9 +138,6 @@
SuperSPARC-II, and hyperSPARC systems are supported
with an <a class="ulink" href="faq.html#smp-cpus" target="_top">SMP</a>
kernel <font size="-1"><span class="emphasis"><em>(2.0)</em></span></font>
-</li>
-</ul></div>
-
<h4 class="title">
<a name="sun4c-fb"></a>sun4c and sun4m framebuffers (<a href="#supported">top</a>)
</h4>
@@ -186,34 +161,29 @@
SPARCstation 20, requires optional 4 or 8 MB VSIMM
<span class="bold"><strong>kernel support limited to
cgthree emulation</strong></span>
-</li>
<li class="listitem">
<span class="emphasis"><em>tcx</em></span>; S24 accelerated color
framebuffer - On-board SPARCstation 4 and JavaStation-1 (8
bpp), and optional on SPARCstation 5 (24 bpp)
<span class="bold"><strong>kernel support limited to
cgthree emulation</strong></span>
-</li>
<li class="listitem">
<span class="emphasis"><em>pnozz</em></span>; Weitek p9100 24
bpp accelerated framebuffer - On-board Tadpole SPARCbook
3GS and 3GX <font size="-1"><span class="emphasis"><em>(1.5)</em></span></font>
<span class="bold"><strong>kernel support limited to
cgthree emulation</strong></span>
-</li>
<li class="listitem">
<span class="emphasis"><em>zx</em></span>; ZX and TZX 24 bpp
accelerated framebuffer - sbus card (leo)
<font size="-1"><span class="emphasis"><em>(2.0)</em></span></font>
<span class="bold"><strong>No X server support yet</strong></span>
-</li>
<li class="listitem">
<span class="emphasis"><em>igsfb</em></span>; 24 bpp IGS C1682
accelerated framebuffer - On-board JavaStation-NC
<span class="bold"><strong>kernel support limited to text
console (no X)</strong></span>
<font size="-1"><span class="emphasis"><em>(2.0)</em></span></font>
-</li>
</ul></div>
<h4 class="title">
@@ -244,9 +214,7 @@
framebuffer with overlay - P4.
<span class="bold"><strong>Note: cgeight support is not well
tested</strong></span>
-</li>
-</ul></div>
-
+
<h4 class="title">
<a name="network-interfaces"></a>Network interfaces (<a href="#supported">top</a>)
</h4>
@@ -268,7 +236,6 @@
<span class="emphasis"><em>be</em></span>; 100 Mbps half-duplex "Big
Mac" ethernet - sbus card
<font size="-1"><span class="emphasis"><em>(1.5)</em></span></font>
-</li>
<li class="listitem">
<span class="emphasis"><em>hme</em></span>; 100 Mbps full-duplex
"Happy Meal" ethernet - On-board JavaStation-NC and sbus card
@@ -284,7 +251,6 @@
multi-function sbus cards (e.g. along with SCSI), the
ethernet interfaces will work even ifthe other functions
do not</li>
-</ul></div>
<h4 class="title">
<a name="scsi-interfaces"></a>SCSI interfaces (<a href="#supported">top</a>)
@@ -310,7 +276,6 @@
multi-function sbus cards (e.g. along with ethernet), the
SCSI isp and esp portions of those cards should work, even
if the other functions do not</li>
-</ul></div>
<h4 class="title">
<a name="vme-disk"></a>VME disk interfaces (<a href="#supported">top</a>)
@@ -384,8 +349,6 @@
(internal 14.4 kbps modem, use
<code class="filename">/dev/ttyC0</code>) and JavaStation-NC
<font size="-1"><span class="emphasis"><em>(1.5)</em></span></font>
-</li>
-</ul></div>
<h4 class="title">
<a name="input"></a>Input devices (<a href="#supported">top</a>)
@@ -419,8 +382,6 @@
controller 44 kHz, 16 bit, stereo (output only) -
On-board SPARCbook and various SPARCstations.
<font size="-1"><span class="emphasis"><em>(-current)</em></span></font>
-</li>
-</ul></div>
<h4 class="title">
<a name="parallel"></a>Parallel ports (<a href="#supported">top</a>)
Changed pages:
templates/port
Changed by: mspo
Commit type: cvs
Date: in the wee hours of Tuesday night 04/18/12
fix up and template a little more - hopefully making amd64 look better
Index: wikisrc/templates/port.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/templates/port.mdwn,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- wikisrc/templates/port.mdwn 15 Apr 2012 21:12:54 -0000 1.6 +++ wikisrc/templates/port.mdwn 18 Apr 2012 02:35:41 -0000 1.7 @@ -14,8 +14,7 @@ * [NetBSD/<TMPL_VAR port> <TMPL_VAR changes_future> changes](http://www.NetBSD.org/changes/changes-<TMPL_VAR changes_future>.html#port-<TMPL_VAR port> "NetBSD/<TMPL_VAR port> <TMPL_VAR changes_future> changes") ## Mailing List -* The [NetBSD/<TMPL_VAR port> mailing list](http://www.netbsd.org/mailinglists/#port-<TMPL_VAR port> "<TMPL_VAR port>mailing list"), covering NetBSD's port to <TMPL_VAR port> machine: - +The [NetBSD/<TMPL_VAR port> mailing list](http://www.netbsd.org/mailinglists/#port-<TMPL_VAR port> "<TMPL_VAR port>mailing list"), covering NetBSD's port to <TMPL_VAR port> machine: <table> <tr> <td> @@ -25,6 +24,7 @@ </td> </tr> </table> +<a href="mailto:port-<TMPL_VAR port>-maintainer@NetBSD.org">Mail the NetBSD/<TMPL_VAR port> port maintainer</a> <TMPL_IF supported_hardware> ## Supported Hardware
Changed pages:
amazon ec2/amis
Changed by: riz
Commit type: web
Date: late Tuesday afternoon 04/17/12
Update us-west-2 i386 6.0_BETA
Index: wikisrc/amazon_ec2/amis.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/amazon_ec2/amis.mdwn,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- wikisrc/amazon_ec2/amis.mdwn 17 Apr 2012 16:38:19 -0000 1.13 +++ wikisrc/amazon_ec2/amis.mdwn 17 Apr 2012 17:51:25 -0000 1.14 @@ -74,7 +74,7 @@ <th>NetBSD 6.0_BETA</th> <td>ami-37805e5e</td> <td>ami-e3d68fa6</td> - <td>ami-701c9140</td> + <td>ami-eef27ede</td> <td>ami-a72910d3</td> <td>ami-c8a2e69a</td> <td>ami-2405b325</td>
Update us-west-2 i386 5.1.2
Index: wikisrc/amazon_ec2/amis.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/amazon_ec2/amis.mdwn,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- wikisrc/amazon_ec2/amis.mdwn 17 Apr 2012 01:54:41 -0000 1.12 +++ wikisrc/amazon_ec2/amis.mdwn 17 Apr 2012 16:38:19 -0000 1.13 @@ -64,7 +64,7 @@ <th>NetBSD 5.1.2</th> <td>ami-230fdf4a</td> <td>ami-b14f16f4</td> - <td>ami-707ef340</td> + <td>ami-f0f27ec0</td> <td>ami-81d0eef5</td> <td>ami-5c55110e</td> <td>ami-9c6bdd9d</td>
Andrew Doran was the port maintainer.
Index: wikisrc/ports/amd64.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/ports/amd64.mdwn,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- wikisrc/ports/amd64.mdwn 15 Apr 2012 21:12:54 -0000 1.4 +++ wikisrc/ports/amd64.mdwn 17 Apr 2012 08:39:56 -0000 1.5 @@ -30,8 +30,6 @@ The port is fully functional. It has been tested on single-CPU and multiprocessor (SMP) Opteron configurations. Since the <a class="ulink" href="../../releases/formal-2.0/NetBSD-2.0.html" target="_top">release of NetBSD 2.0</a>, it is a completely supported platform. - -Andrew Doran is the maintainer of NetBSD/amd64. """ ]]
Update sa-east-1 i386 5.1.2
Index: wikisrc/amazon_ec2/amis.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/amazon_ec2/amis.mdwn,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- wikisrc/amazon_ec2/amis.mdwn 7 Apr 2012 21:30:52 -0000 1.11 +++ wikisrc/amazon_ec2/amis.mdwn 17 Apr 2012 01:54:41 -0000 1.12 @@ -68,7 +68,7 @@ <td>ami-81d0eef5</td> <td>ami-5c55110e</td> <td>ami-9c6bdd9d</td> - <td>ami-e4429df9</td> + <td>ami-e6a37dfb</td> </tr> <tr> <th>NetBSD 6.0_BETA</th>
Note some fixed issues, add a few more. (many more need adding)
Index: wikisrc/users/riz/issues-6.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/users/riz/issues-6.mdwn,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- wikisrc/users/riz/issues-6.mdwn 23 Mar 2012 20:38:42 -0000 1.6 +++ wikisrc/users/riz/issues-6.mdwn 16 Apr 2012 18:37:31 -0000 1.7 @@ -4,8 +4,8 @@ ### kmem-related: -* [[mac68k panic: pmap_enter_ptpage: can't get KPT page|http://gnats.netbsd.org/45915]] -* macppc triggers DEFAULT CATCH! while loading kernel +* <strike>[[mac68k panic: pmap_enter_ptpage: can't get KPT page|http://gnats.netbsd.org/45915]]</strike> (fixed for most, possibly all m68k) +* <strike>macppc triggers DEFAULT CATCH! while loading kernel</strike> * amiga mem sizing issue * shark issues @@ -13,7 +13,13 @@ ### toolchain bugs: * gcc 4.5.1 (optimizer) bugs on VAX [[PR 46033|http://gnats.netbsd.org/46033]], [[PR 46098|http://gnats.netbsd.org/46098]], [[PR 46251|http://gnats.netbsd.org/46251]] +### install bugs: +* [[PR 45990: sysinst uses traditional 63 sector MBR offset|http://gnats.netbsd.org/45990]] (supposedly fixed in -current, needs testing/pullup) + +### network bugs: +* [[PR 39305: loops through gre(4) cause a hang or crash|http://gnats.netbsd.org/39305]] ### misc bugs: -* [[PR 46217: CARP hangs on boot|http://gnats.netbsd.org/46217]] -* [[PR 46232: pad (audio pseudo device) locking issue|http://gnats.netbsd.org/46232]] +* <strike>[[PR 46217: CARP hangs on boot|http://gnats.netbsd.org/46217]]</strike> +* <strike>[[PR 46232: pad (audio pseudo device) locking issue|http://gnats.netbsd.org/46232]]</strike> +* [[PR 45933: fsck_ffs can't find wapbl journal on 4k-block disks|http://gnats.netbsd.org/45933]]
Changed pages:
ports/sparc.mdwm
Changed by: mspo
Commit type: cvs
Date: late Sunday evening 04/15/12
sparc page - name mdwN
--- wikisrc/ports/sparc.mdwm 2012-04-15 21:27:13.000000000 +0000 +++ /dev/null 2012-04-15 18:10:10.000000000 +0000 @@ -1,470 +0,0 @@ -[[!template id=port -port="sparc" -cur_rel="5.1.2" -future_rel="6.0" -changes_cur="5.0" -changes_future="6.0" -thumbnail="http://www.netbsd.org/images/ports/sparc/ipx.gif" -about=""" -NetBSD/sparc is based on work done at Lawrence Berkeley -Laboratory by the Computer Systems Engineering group under DARPA -contract BG 91-66, which later appeared in the 4.4BSD-Lite -distribution from the University of California, Berkeley. It was -imported into the NetBSD source tree on October 2, 1993. Special -thanks are extended to the LBL Computer Systems Engineering group -for their work. Without which, this port would not exist. - -For frequently asked questions and links to Sun hardware -information, see the <a class="ulink" href="faq.html" target="_top">NetBSD/sparc FAQ</a>. - -For newer UltraSPARC-based machines, see -<a class="ulink" href="../sparc64/" target="_top">NetBSD/sparc64</a>. -""" -supported_hardware=""" -Systems for which support was added in NetBSD 2.0 are marked -<span class="emphasis"><em>(2.0)</em></span>. - -Note:<span class="emphasis"><em>Models -marked </em></span>'(SMP)'<span class="emphasis"><em>can have multiple CPUs but NetBSD/sparc does not -use more than one CPU prior to release 2.0</em></span> - -<ul class="itemizedlist" type="disc"> -<li class="listitem">Sun sun4m machines (all known SuperSPARC, hyperSPARC, - microSPARC, and TurboSPARC CPUs are supported): - <div class="itemizedlist"><ul class="itemizedlist" type="circle"> -<li class="listitem">Sun 4/600 (<a class="ulink" href="faq.html#smp-cpus" target="_top">SMP</a>)</li> -<li class="listitem">SPARC Classic</li> -<li class="listitem">SPARC LX</li> -<li class="listitem">SPARCstation 4</li> -<li class="listitem">SPARCstation/server 5</li> -<li class="listitem">SPARCstation/server 10 (<a class="ulink" href="faq.html#smp-cpus" target="_top">SMP</a>)</li> -<li class="listitem">SPARCstation/server 20 (<a class="ulink" href="faq.html#smp-cpus" target="_top">SMP</a>)</li> -<li class="listitem">SPARCstation Voyager - <span class="emphasis"><em>(See the <a class="ulink" href="faq.html#nell" target="_top">FAQ</a> - regarding PCMCIA support)</em></span> -</li> -<li class="listitem">Sun '<a class="ulink" href="faq.html#fox" target="_top">Fox</a>'</li> -<li class="listitem"> -<a class="ulink" href="javastation.html#mrcoffe" target="_top">JavaStation-1</a> (a.k.a. - "Mr. Coffee" or JavaStation JJ) - <span class="emphasis"><em>(2.0)</em></span> -</li> -<li class="listitem"> -<a class="ulink" href="javastation.html#krups" target="_top">JavaStation-NC</a> (a.k.a. - Krups, JavaStation JK, or JavaStation-10) - <span class="emphasis"><em>(2.0)</em></span> -</li> -</ul> -</li> -<li class="listitem">Sun4m compatibles (including): -<ul class="itemizedlist" type="circle"> -<li class="listitem">Axil 245 (SS5 clone), 311, 320 (SS20 clone)</li> -<li class="listitem">Cycle C C Cycle 5-IP</li> -<li class="listitem">DTKstation/Classic+</li> -<li class="listitem">RDI,PowerLite-85, RDI,PowerLite-110, RDI,BriteLite</li> -<li class="listitem">Ross sparc 20</li> -<li class="listitem">SS5/170 Transtec</li> -<li class="listitem">TATUNG micro COMPstation 5</li> -<li class="listitem">Twinhead TWINstation 5G (SS5 clone)</li> -<li class="listitem">TWS,SuperCOMPstation-20S</li> -<li class="listitem">Tadpole SPARCbook 3GS and 3GX</li> -</ul> -</li> -<li class="listitem">Sun sun4c machines: -<ul class="itemizedlist" type="circle"> -<li class="listitem">SPARCstation/server 1</li> -<li class="listitem">SPARCstation/server 1+</li> -<li class="listitem">SPARCstation/server 2</li> -<li class="listitem">Sun ELC</li> -<li class="listitem">Sun IPC</li> -<li class="listitem">Sun IPX</li> -<li class="listitem">Sun SLC</li> -</ul> -</li> -<li class="listitem">Sun4c compatibles (including): -<ul class="itemizedlist" type="circle"> -<li class="listitem">Aries Research Inc, Parrot II (SS2 clone)</li> -<li class="listitem">Opus/5000 (SS1 clone)</li> -<li class="listitem">Opus/5250 (SS1 clone)</li> -<li class="listitem">FORCE SPARC CPU1e/4 VME Board (SS1 clone) - (<span class="emphasis"><em>NetBSD doesn't support VME boards on this model</em></span>)</li> -<li class="listitem">FORCE SPARC CPU2e/4 VME Board (SS2 clone) - <span class="emphasis"><em>NetBSD doesn't support VME boards on this model</em></span> -</li> -</ul> -</li> -<li class="listitem">Sun sun4 machines: -<ul class="itemizedlist" type="circle"> -<li class="listitem">Sun 4/100 series</li> -<li class="listitem">Sun 4/200 series</li> -<li class="listitem">Sun 4/300 series</li> -<li class="listitem">Sun 4/400 series</li> -</ul> -</li> -</ul> -<ul class="itemizedlist" type="disc"> -<li class="listitem">All on-board and most optional Sun brand framebuffers (all - framebuffers work for text console usage)</li> -<li class="listitem">All Sun brand built-in and optional network interfaces</li> -<li class="listitem">Most Sun brand SCSI interfaces</li> -<li class="listitem">All floppy drives</li> -<li class="listitem">All on-board serial ports</li> -<li class="listitem">Most input devices (keyboards, mice, trackballs)</li> -<li class="listitem">Audio on sun4c and some sun4m models</li> -<li class="listitem">PCMCIA devices with Voyager or sbus nell interface - (see <a class="ulink" href="faq.html#nell" target="_top">FAQ</a>)</li> -<li class="listitem">PCMCIA devices with Tadpole ts102 ( SPARCbook 3GX and 3GS ) in -current</li> -<li class="listitem">DBRI audio in -current (output only so far)</li> -</ul> - -<div id="content"><div class="fullWidth"><div class="rowOfBoxes"> -<h1>NetBSD/sparc Supported Hardware</h1> -<h3 class="title"><a name="supported">The following hardware is supported by NetBSD/sparc:</a></h3> -<ul> -<li><a href="#sum4m-cpu">sun4m mbus CPU modules</a></li> -<li><a href="#sun4c-fb">sun4c and sun4m framebuffers</a></li> -<li><a href="#sun4-fb">sun4 framebuffers</a></li> -<li><a href="#network-interfaces">Network interfaces</a></li> -<li><a href="#scsi-interfaces">SCSI interfaces</a></li> -<li><a href="#vme-disk">VME disk interfaces</a></li> -<li><a href="#floppy">Floppy drives</a></li> -<li><a href="#tape">Tape drives</a></li> -<li><a href="#pcmcia">PCMCIA/Cardbus devices</a></li> -<li><a href="#serial">Serial interfaces</a></li> -<li><a href="#input">Input devices</a></li> -<li><a href="#audio">Audio interfaces</a></li> -<li><a href="#parallel">Parallel ports</a></li> -<li><a href="#sbus">Miscellaneous sbus devices</a></li> -<li><a href="#unsupported">Devices often asked about, but not yet supported</a></li> -</ul> -<hr> -<h3 class="title">The following hardware is supported by NetBSD/sparc:</h3> -<p>If you have a device that's not listed, it might be - compatible with something else, or we might have simply - forgotten it. If all else fails, maybe you could write a - driver!</p> - <h4 class="title"> -<a name="sum4m-cpu"></a>sun4m mbus CPU modules (<a href="#supported">top</a>) - </h4> - - <p>Sun 4/600, SPARCstation/server 10, SPARCstation/server - 20, and clones</p> - - <div class="itemizedlist"><ul class="itemizedlist" type="disc"> -<li class="listitem"> -<span class="emphasis"><em>cpu0</em></span>; All single-CPU - systems are supported</li> -<li class="listitem"> -<span class="emphasis"><em>cpuN</em></span>; All hardware - compatible dual-, tri- and quad-CPU SuperSPARC-I, - SuperSPARC-II, and hyperSPARC systems are supported - with an <a class="ulink" href="faq.html#smp-cpus" target="_top">SMP</a> - kernel <font size="-1"><span class="emphasis"><em>(2.0)</em></span></font> -</li> -</ul></div> - - <h4 class="title"> -<a name="sun4c-fb"></a>sun4c and sun4m framebuffers (<a href="#supported">top</a>) - </h4> - - <p>On-board and sbus card.</p> - - <div class="itemizedlist"><ul class="itemizedlist" type="disc"> -<li class="listitem"> -<span class="emphasis"><em>bwtwo</em></span>; 1 bpp framebuffer - - On-board and sbus card (MG1 and MG2)</li> -<li class="listitem"> -<span class="emphasis"><em>cgthree</em></span>; 8 bpp framebuffer - - On-board and sbus card</li> -<li class="listitem"> -<span class="emphasis"><em>cgsix</em></span>; LEGO 8 bpp accelerated - framebuffer - On-board and sbus card (GX, GX+, TGX, and - TGX+)</li> -<li class="listitem"> -<span class="emphasis"><em>cgfourteen</em></span>; SX 24 bpp - accelerated framebuffer - On-board SPARCstation 10SX and - SPARCstation 20, requires optional 4 or 8 MB VSIMM - <span class="bold"><strong>kernel support limited to - cgthree emulation</strong></span> -</li> -<li class="listitem"> -<span class="emphasis"><em>tcx</em></span>; S24 accelerated color - framebuffer - On-board SPARCstation 4 and JavaStation-1 (8 - bpp), and optional on SPARCstation 5 (24 bpp) - <span class="bold"><strong>kernel support limited to - cgthree emulation</strong></span> -</li> -<li class="listitem"> (Diff truncated)
sparc page - name mdwN
--- /dev/null 2012-04-15 18:10:10.000000000 +0000 +++ wikisrc/ports/sparc.mdwn 2012-04-15 21:15:43.000000000 +0000 @@ -0,0 +1,471 @@ +[[!template id=port +port="sparc" +cur_rel="5.1.2" +future_rel="6.0" +changes_cur="5.0" +changes_future="6.0" +thumbnail="http://www.netbsd.org/images/ports/sparc/ipx.gif" +about=""" +NetBSD/sparc is based on work done at Lawrence Berkeley +Laboratory by the Computer Systems Engineering group under DARPA +contract BG 91-66, which later appeared in the 4.4BSD-Lite +distribution from the University of California, Berkeley. It was +imported into the NetBSD source tree on October 2, 1993. Special +thanks are extended to the LBL Computer Systems Engineering group +for their work. Without which, this port would not exist. + +For frequently asked questions and links to Sun hardware +information, see the <a class="ulink" href="faq.html" target="_top">NetBSD/sparc FAQ</a>. + +For newer UltraSPARC-based machines, see +<a class="ulink" href="../sparc64/" target="_top">NetBSD/sparc64</a>. +""" +supported_hardware=""" +Systems for which support was added in NetBSD 2.0 are marked +<span class="emphasis"><em>(2.0)</em></span>. + +Note:<span class="emphasis"><em>Models +marked </em></span>'(SMP)'<span class="emphasis"><em>can have multiple CPUs but NetBSD/sparc does not +use more than one CPU prior to release 2.0</em></span> + +<ul class="itemizedlist" type="disc"> +<li class="listitem">Sun sun4m machines (all known SuperSPARC, hyperSPARC, + microSPARC, and TurboSPARC CPUs are supported): + <div class="itemizedlist"><ul class="itemizedlist" type="circle"> +<li class="listitem">Sun 4/600 (<a class="ulink" href="faq.html#smp-cpus" target="_top">SMP</a>)</li> +<li class="listitem">SPARC Classic</li> +<li class="listitem">SPARC LX</li> +<li class="listitem">SPARCstation 4</li> +<li class="listitem">SPARCstation/server 5</li> +<li class="listitem">SPARCstation/server 10 (<a class="ulink" href="faq.html#smp-cpus" target="_top">SMP</a>)</li> +<li class="listitem">SPARCstation/server 20 (<a class="ulink" href="faq.html#smp-cpus" target="_top">SMP</a>)</li> +<li class="listitem">SPARCstation Voyager + <span class="emphasis"><em>(See the <a class="ulink" href="faq.html#nell" target="_top">FAQ</a> + regarding PCMCIA support)</em></span> +</li> +<li class="listitem">Sun '<a class="ulink" href="faq.html#fox" target="_top">Fox</a>'</li> +<li class="listitem"> +<a class="ulink" href="javastation.html#mrcoffe" target="_top">JavaStation-1</a> (a.k.a. + "Mr. Coffee" or JavaStation JJ) + <span class="emphasis"><em>(2.0)</em></span> +</li> +<li class="listitem"> +<a class="ulink" href="javastation.html#krups" target="_top">JavaStation-NC</a> (a.k.a. + Krups, JavaStation JK, or JavaStation-10) + <span class="emphasis"><em>(2.0)</em></span> +</li> +</ul> +</li> +<li class="listitem">Sun4m compatibles (including): +<ul class="itemizedlist" type="circle"> +<li class="listitem">Axil 245 (SS5 clone), 311, 320 (SS20 clone)</li> +<li class="listitem">Cycle C C Cycle 5-IP</li> +<li class="listitem">DTKstation/Classic+</li> +<li class="listitem">RDI,PowerLite-85, RDI,PowerLite-110, RDI,BriteLite</li> +<li class="listitem">Ross sparc 20</li> +<li class="listitem">SS5/170 Transtec</li> +<li class="listitem">TATUNG micro COMPstation 5</li> +<li class="listitem">Twinhead TWINstation 5G (SS5 clone)</li> +<li class="listitem">TWS,SuperCOMPstation-20S</li> +<li class="listitem">Tadpole SPARCbook 3GS and 3GX</li> +</ul> +</li> +<li class="listitem">Sun sun4c machines: +<ul class="itemizedlist" type="circle"> +<li class="listitem">SPARCstation/server 1</li> +<li class="listitem">SPARCstation/server 1+</li> +<li class="listitem">SPARCstation/server 2</li> +<li class="listitem">Sun ELC</li> +<li class="listitem">Sun IPC</li> +<li class="listitem">Sun IPX</li> +<li class="listitem">Sun SLC</li> +</ul> +</li> +<li class="listitem">Sun4c compatibles (including): +<ul class="itemizedlist" type="circle"> +<li class="listitem">Aries Research Inc, Parrot II (SS2 clone)</li> +<li class="listitem">Opus/5000 (SS1 clone)</li> +<li class="listitem">Opus/5250 (SS1 clone)</li> +<li class="listitem">FORCE SPARC CPU1e/4 VME Board (SS1 clone) + (<span class="emphasis"><em>NetBSD doesn't support VME boards on this model</em></span>)</li> +<li class="listitem">FORCE SPARC CPU2e/4 VME Board (SS2 clone) + <span class="emphasis"><em>NetBSD doesn't support VME boards on this model</em></span> +</li> +</ul> +</li> +<li class="listitem">Sun sun4 machines: +<ul class="itemizedlist" type="circle"> +<li class="listitem">Sun 4/100 series</li> +<li class="listitem">Sun 4/200 series</li> +<li class="listitem">Sun 4/300 series</li> +<li class="listitem">Sun 4/400 series</li> +</ul> +</li> +</ul> +<ul class="itemizedlist" type="disc"> +<li class="listitem">All on-board and most optional Sun brand framebuffers (all + framebuffers work for text console usage)</li> +<li class="listitem">All Sun brand built-in and optional network interfaces</li> +<li class="listitem">Most Sun brand SCSI interfaces</li> +<li class="listitem">All floppy drives</li> +<li class="listitem">All on-board serial ports</li> +<li class="listitem">Most input devices (keyboards, mice, trackballs)</li> +<li class="listitem">Audio on sun4c and some sun4m models</li> +<li class="listitem">PCMCIA devices with Voyager or sbus nell interface + (see <a class="ulink" href="faq.html#nell" target="_top">FAQ</a>)</li> +<li class="listitem">PCMCIA devices with Tadpole ts102 ( SPARCbook 3GX and 3GS ) in -current</li> +<li class="listitem">DBRI audio in -current (output only so far)</li> +</ul> + +<div id="content"><div class="fullWidth"><div class="rowOfBoxes"> +<h1>NetBSD/sparc Supported Hardware</h1> +<h3 class="title"><a name="supported">The following hardware is supported by NetBSD/sparc:</a></h3> +<ul> +<li><a href="#sum4m-cpu">sun4m mbus CPU modules</a></li> +<li><a href="#sun4c-fb">sun4c and sun4m framebuffers</a></li> +<li><a href="#sun4-fb">sun4 framebuffers</a></li> +<li><a href="#network-interfaces">Network interfaces</a></li> +<li><a href="#scsi-interfaces">SCSI interfaces</a></li> +<li><a href="#vme-disk">VME disk interfaces</a></li> +<li><a href="#floppy">Floppy drives</a></li> +<li><a href="#tape">Tape drives</a></li> +<li><a href="#pcmcia">PCMCIA/Cardbus devices</a></li> +<li><a href="#serial">Serial interfaces</a></li> +<li><a href="#input">Input devices</a></li> +<li><a href="#audio">Audio interfaces</a></li> +<li><a href="#parallel">Parallel ports</a></li> +<li><a href="#sbus">Miscellaneous sbus devices</a></li> +<li><a href="#unsupported">Devices often asked about, but not yet supported</a></li> +</ul> +<hr> +<h3 class="title">The following hardware is supported by NetBSD/sparc:</h3> +<p>If you have a device that's not listed, it might be + compatible with something else, or we might have simply + forgotten it. If all else fails, maybe you could write a + driver!</p> + <h4 class="title"> +<a name="sum4m-cpu"></a>sun4m mbus CPU modules (<a href="#supported">top</a>) + </h4> + + <p>Sun 4/600, SPARCstation/server 10, SPARCstation/server + 20, and clones</p> + + <div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<li class="listitem"> +<span class="emphasis"><em>cpu0</em></span>; All single-CPU + systems are supported</li> +<li class="listitem"> +<span class="emphasis"><em>cpuN</em></span>; All hardware + compatible dual-, tri- and quad-CPU SuperSPARC-I, + SuperSPARC-II, and hyperSPARC systems are supported + with an <a class="ulink" href="faq.html#smp-cpus" target="_top">SMP</a> + kernel <font size="-1"><span class="emphasis"><em>(2.0)</em></span></font> +</li> +</ul></div> + + <h4 class="title"> +<a name="sun4c-fb"></a>sun4c and sun4m framebuffers (<a href="#supported">top</a>) + </h4> + + <p>On-board and sbus card.</p> + + <div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<li class="listitem"> +<span class="emphasis"><em>bwtwo</em></span>; 1 bpp framebuffer - + On-board and sbus card (MG1 and MG2)</li> +<li class="listitem"> +<span class="emphasis"><em>cgthree</em></span>; 8 bpp framebuffer - + On-board and sbus card</li> +<li class="listitem"> +<span class="emphasis"><em>cgsix</em></span>; LEGO 8 bpp accelerated + framebuffer - On-board and sbus card (GX, GX+, TGX, and + TGX+)</li> +<li class="listitem"> +<span class="emphasis"><em>cgfourteen</em></span>; SX 24 bpp + accelerated framebuffer - On-board SPARCstation 10SX and + SPARCstation 20, requires optional 4 or 8 MB VSIMM + <span class="bold"><strong>kernel support limited to + cgthree emulation</strong></span> +</li> +<li class="listitem"> +<span class="emphasis"><em>tcx</em></span>; S24 accelerated color + framebuffer - On-board SPARCstation 4 and JavaStation-1 (8 + bpp), and optional on SPARCstation 5 (24 bpp) + <span class="bold"><strong>kernel support limited to + cgthree emulation</strong></span> +</li> +<li class="listitem"> (Diff truncated)
Changed pages:
ports/sparc.mdwm
Changed by: mspo
Commit type: cvs
Date: late Sunday evening 04/15/12
fixup for port template and add sparc port page -- still needs a ton of conversion to markdown; actually add the sparc page this time
--- /dev/null 2012-04-15 18:10:10.000000000 +0000 +++ wikisrc/ports/sparc.mdwm 2012-04-15 21:13:33.000000000 +0000 @@ -0,0 +1,470 @@ +[[!template id=port +port="sparc" +cur_rel="5.1.2" +future_rel="6.0" +changes_cur="5.0" +changes_future="6.0" +thumbnail="http://www.netbsd.org/images/ports/sparc/ipx.gif" +about=""" +NetBSD/sparc is based on work done at Lawrence Berkeley +Laboratory by the Computer Systems Engineering group under DARPA +contract BG 91-66, which later appeared in the 4.4BSD-Lite +distribution from the University of California, Berkeley. It was +imported into the NetBSD source tree on October 2, 1993. Special +thanks are extended to the LBL Computer Systems Engineering group +for their work. Without which, this port would not exist. + +For frequently asked questions and links to Sun hardware +information, see the <a class="ulink" href="faq.html" target="_top">NetBSD/sparc FAQ</a>. + +For newer UltraSPARC-based machines, see +<a class="ulink" href="../sparc64/" target="_top">NetBSD/sparc64</a>. +""" +supported_hardware=""" +Systems for which support was added in NetBSD 2.0 are marked +<span class="emphasis"><em>(2.0)</em></span>. + +Note:<span class="emphasis"><em>Models +marked </em></span>'(SMP)'<span class="emphasis"><em>can have multiple CPUs but NetBSD/sparc does not +use more than one CPU prior to release 2.0</em></span> + +<ul class="itemizedlist" type="disc"> +<li class="listitem">Sun sun4m machines (all known SuperSPARC, hyperSPARC, + microSPARC, and TurboSPARC CPUs are supported): + <div class="itemizedlist"><ul class="itemizedlist" type="circle"> +<li class="listitem">Sun 4/600 (<a class="ulink" href="faq.html#smp-cpus" target="_top">SMP</a>)</li> +<li class="listitem">SPARC Classic</li> +<li class="listitem">SPARC LX</li> +<li class="listitem">SPARCstation 4</li> +<li class="listitem">SPARCstation/server 5</li> +<li class="listitem">SPARCstation/server 10 (<a class="ulink" href="faq.html#smp-cpus" target="_top">SMP</a>)</li> +<li class="listitem">SPARCstation/server 20 (<a class="ulink" href="faq.html#smp-cpus" target="_top">SMP</a>)</li> +<li class="listitem">SPARCstation Voyager + <span class="emphasis"><em>(See the <a class="ulink" href="faq.html#nell" target="_top">FAQ</a> + regarding PCMCIA support)</em></span> +</li> +<li class="listitem">Sun '<a class="ulink" href="faq.html#fox" target="_top">Fox</a>'</li> +<li class="listitem"> +<a class="ulink" href="javastation.html#mrcoffe" target="_top">JavaStation-1</a> (a.k.a. + "Mr. Coffee" or JavaStation JJ) + <span class="emphasis"><em>(2.0)</em></span> +</li> +<li class="listitem"> +<a class="ulink" href="javastation.html#krups" target="_top">JavaStation-NC</a> (a.k.a. + Krups, JavaStation JK, or JavaStation-10) + <span class="emphasis"><em>(2.0)</em></span> +</li> +</ul> +</li> +<li class="listitem">Sun4m compatibles (including): +<ul class="itemizedlist" type="circle"> +<li class="listitem">Axil 245 (SS5 clone), 311, 320 (SS20 clone)</li> +<li class="listitem">Cycle C C Cycle 5-IP</li> +<li class="listitem">DTKstation/Classic+</li> +<li class="listitem">RDI,PowerLite-85, RDI,PowerLite-110, RDI,BriteLite</li> +<li class="listitem">Ross sparc 20</li> +<li class="listitem">SS5/170 Transtec</li> +<li class="listitem">TATUNG micro COMPstation 5</li> +<li class="listitem">Twinhead TWINstation 5G (SS5 clone)</li> +<li class="listitem">TWS,SuperCOMPstation-20S</li> +<li class="listitem">Tadpole SPARCbook 3GS and 3GX</li> +</ul> +</li> +<li class="listitem">Sun sun4c machines: +<ul class="itemizedlist" type="circle"> +<li class="listitem">SPARCstation/server 1</li> +<li class="listitem">SPARCstation/server 1+</li> +<li class="listitem">SPARCstation/server 2</li> +<li class="listitem">Sun ELC</li> +<li class="listitem">Sun IPC</li> +<li class="listitem">Sun IPX</li> +<li class="listitem">Sun SLC</li> +</ul> +</li> +<li class="listitem">Sun4c compatibles (including): +<ul class="itemizedlist" type="circle"> +<li class="listitem">Aries Research Inc, Parrot II (SS2 clone)</li> +<li class="listitem">Opus/5000 (SS1 clone)</li> +<li class="listitem">Opus/5250 (SS1 clone)</li> +<li class="listitem">FORCE SPARC CPU1e/4 VME Board (SS1 clone) + (<span class="emphasis"><em>NetBSD doesn't support VME boards on this model</em></span>)</li> +<li class="listitem">FORCE SPARC CPU2e/4 VME Board (SS2 clone) + <span class="emphasis"><em>NetBSD doesn't support VME boards on this model</em></span> +</li> +</ul> +</li> +<li class="listitem">Sun sun4 machines: +<ul class="itemizedlist" type="circle"> +<li class="listitem">Sun 4/100 series</li> +<li class="listitem">Sun 4/200 series</li> +<li class="listitem">Sun 4/300 series</li> +<li class="listitem">Sun 4/400 series</li> +</ul> +</li> +</ul> +<ul class="itemizedlist" type="disc"> +<li class="listitem">All on-board and most optional Sun brand framebuffers (all + framebuffers work for text console usage)</li> +<li class="listitem">All Sun brand built-in and optional network interfaces</li> +<li class="listitem">Most Sun brand SCSI interfaces</li> +<li class="listitem">All floppy drives</li> +<li class="listitem">All on-board serial ports</li> +<li class="listitem">Most input devices (keyboards, mice, trackballs)</li> +<li class="listitem">Audio on sun4c and some sun4m models</li> +<li class="listitem">PCMCIA devices with Voyager or sbus nell interface + (see <a class="ulink" href="faq.html#nell" target="_top">FAQ</a>)</li> +<li class="listitem">PCMCIA devices with Tadpole ts102 ( SPARCbook 3GX and 3GS ) in -current</li> +<li class="listitem">DBRI audio in -current (output only so far)</li> +</ul> + +<div id="content"><div class="fullWidth"><div class="rowOfBoxes"> +<h1>NetBSD/sparc Supported Hardware</h1> +<h3 class="title"><a name="supported">The following hardware is supported by NetBSD/sparc:</a></h3> +<ul> +<li><a href="#sum4m-cpu">sun4m mbus CPU modules</a></li> +<li><a href="#sun4c-fb">sun4c and sun4m framebuffers</a></li> +<li><a href="#sun4-fb">sun4 framebuffers</a></li> +<li><a href="#network-interfaces">Network interfaces</a></li> +<li><a href="#scsi-interfaces">SCSI interfaces</a></li> +<li><a href="#vme-disk">VME disk interfaces</a></li> +<li><a href="#floppy">Floppy drives</a></li> +<li><a href="#tape">Tape drives</a></li> +<li><a href="#pcmcia">PCMCIA/Cardbus devices</a></li> +<li><a href="#serial">Serial interfaces</a></li> +<li><a href="#input">Input devices</a></li> +<li><a href="#audio">Audio interfaces</a></li> +<li><a href="#parallel">Parallel ports</a></li> +<li><a href="#sbus">Miscellaneous sbus devices</a></li> +<li><a href="#unsupported">Devices often asked about, but not yet supported</a></li> +</ul> +<hr> +<h3 class="title">The following hardware is supported by NetBSD/sparc:</h3> +<p>If you have a device that's not listed, it might be + compatible with something else, or we might have simply + forgotten it. If all else fails, maybe you could write a + driver!</p> + <h4 class="title"> +<a name="sum4m-cpu"></a>sun4m mbus CPU modules (<a href="#supported">top</a>) + </h4> + + <p>Sun 4/600, SPARCstation/server 10, SPARCstation/server + 20, and clones</p> + + <div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<li class="listitem"> +<span class="emphasis"><em>cpu0</em></span>; All single-CPU + systems are supported</li> +<li class="listitem"> +<span class="emphasis"><em>cpuN</em></span>; All hardware + compatible dual-, tri- and quad-CPU SuperSPARC-I, + SuperSPARC-II, and hyperSPARC systems are supported + with an <a class="ulink" href="faq.html#smp-cpus" target="_top">SMP</a> + kernel <font size="-1"><span class="emphasis"><em>(2.0)</em></span></font> +</li> +</ul></div> + + <h4 class="title"> +<a name="sun4c-fb"></a>sun4c and sun4m framebuffers (<a href="#supported">top</a>) + </h4> + + <p>On-board and sbus card.</p> + + <div class="itemizedlist"><ul class="itemizedlist" type="disc"> +<li class="listitem"> +<span class="emphasis"><em>bwtwo</em></span>; 1 bpp framebuffer - + On-board and sbus card (MG1 and MG2)</li> +<li class="listitem"> +<span class="emphasis"><em>cgthree</em></span>; 8 bpp framebuffer - + On-board and sbus card</li> +<li class="listitem"> +<span class="emphasis"><em>cgsix</em></span>; LEGO 8 bpp accelerated + framebuffer - On-board and sbus card (GX, GX+, TGX, and + TGX+)</li> +<li class="listitem"> +<span class="emphasis"><em>cgfourteen</em></span>; SX 24 bpp + accelerated framebuffer - On-board SPARCstation 10SX and + SPARCstation 20, requires optional 4 or 8 MB VSIMM + <span class="bold"><strong>kernel support limited to + cgthree emulation</strong></span> +</li> +<li class="listitem"> +<span class="emphasis"><em>tcx</em></span>; S24 accelerated color + framebuffer - On-board SPARCstation 4 and JavaStation-1 (8 + bpp), and optional on SPARCstation 5 (24 bpp) + <span class="bold"><strong>kernel support limited to + cgthree emulation</strong></span> +</li> +<li class="listitem"> (Diff truncated)
Changed pages:
ports/amd64
templates/port
Changed by: mspo
Commit type: cvs
Date: late Sunday evening 04/15/12
fixup for port template and add sparc port page -- still needs a ton of conversion to markdown
Index: wikisrc/ports/amd64.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/ports/amd64.mdwn,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- wikisrc/ports/amd64.mdwn 15 Apr 2012 20:44:55 -0000 1.3 +++ wikisrc/ports/amd64.mdwn 15 Apr 2012 21:12:54 -0000 1.4 @@ -34,5 +34,5 @@ Andrew Doran is the maintainer of NetBSD/amd64. """ - ]] +[[!tag tier1port]] Index: wikisrc/templates/port.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/templates/port.mdwn,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- wikisrc/templates/port.mdwn 15 Apr 2012 21:00:17 -0000 1.5 +++ wikisrc/templates/port.mdwn 15 Apr 2012 21:12:54 -0000 1.6 @@ -31,7 +31,7 @@ <TMPL_VAR supported_hardware> </TMPL_IF> -<TMPL_IF supported_hardware> +<TMPL_IF unsupported_hardware> ## Unsupported Hardware <TMPL_VAR unsupported_hardware> </TMPL_IF>
fix the mailing list links
Index: wikisrc/templates/port.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/templates/port.mdwn,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- wikisrc/templates/port.mdwn 15 Apr 2012 20:56:19 -0000 1.4 +++ wikisrc/templates/port.mdwn 15 Apr 2012 21:00:17 -0000 1.5 @@ -19,15 +19,10 @@ <table> <tr> <td> - -[subscribe](http://www.NetBSD.org/cgi-bin/subscribe_list.pl?list=port-<TMPL_VAR port>) - +<a href="http://www.NetBSD.org/cgi-bin/subscribe_list.pl?list=port-<TMPL_VAR port>">subscribe</a> </td><td> - -[archive](http://mail-index.NetBSD.org/port-<TMPL_VAR port>/) - +<a href="http://mail-index.NetBSD.org/port-<TMPL_VAR port>/">archive</a> </td> - </tr> </table>
see if we can create the mailing list table
Index: wikisrc/templates/port.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/templates/port.mdwn,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- wikisrc/templates/port.mdwn 15 Apr 2012 20:40:26 -0000 1.3 +++ wikisrc/templates/port.mdwn 15 Apr 2012 20:56:19 -0000 1.4 @@ -1,7 +1,7 @@ <TMPL_IF NAME="port"> [[!meta title="NetBSD/<TMPL_VAR port>"]] -# <TMPL_IF thumbnail><img src=<TMPL_VAR thumbnail> alt="<TMPL_VAR port> thumbnail image"/></TMPL_IF>NetBSD/<TMPL_VAR port> +# <TMPL_IF thumbnail><img src=<TMPL_VAR thumbnail> alt="<TMPL_VAR port> thumbnail image"/></TMPL_IF> ## About NetBSD/<TMPL_VAR port> <TMPL_VAR about> @@ -13,6 +13,24 @@ * [NetBSD/<TMPL_VAR port> <TMPL_VAR changes_cur> changes](http://www.NetBSD.org/changes/changes-<TMPL_VAR changes_cur>.html#port-<TMPL_VAR port> "NetBSD/<TMPL_VAR port> <TMPL_VAR changes_cur> changes") * [NetBSD/<TMPL_VAR port> <TMPL_VAR changes_future> changes](http://www.NetBSD.org/changes/changes-<TMPL_VAR changes_future>.html#port-<TMPL_VAR port> "NetBSD/<TMPL_VAR port> <TMPL_VAR changes_future> changes") +## Mailing List +* The [NetBSD/<TMPL_VAR port> mailing list](http://www.netbsd.org/mailinglists/#port-<TMPL_VAR port> "<TMPL_VAR port>mailing list"), covering NetBSD's port to <TMPL_VAR port> machine: + +<table> +<tr> +<td> + +[subscribe](http://www.NetBSD.org/cgi-bin/subscribe_list.pl?list=port-<TMPL_VAR port>) + +</td><td> + +[archive](http://mail-index.NetBSD.org/port-<TMPL_VAR port>/) + +</td> + +</tr> +</table> + <TMPL_IF supported_hardware> ## Supported Hardware <TMPL_VAR supported_hardware> @@ -37,7 +55,6 @@ - port (required) - about (required) -- mlist (required) - cur_rel (required) - future_rel (required) - changes_cur (required)
ikiwiki syntax fixes, take two
Index: wikisrc/ports/amd64.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/ports/amd64.mdwn,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- wikisrc/ports/amd64.mdwn 15 Apr 2012 20:35:58 -0000 1.2 +++ wikisrc/ports/amd64.mdwn 15 Apr 2012 20:44:55 -0000 1.3 @@ -6,32 +6,32 @@ changes_future="6.0" thumbnail="http://www.netbsd.org/images/ports/amd64/AMD_Opteron.gif" about=""" - NetBSD/amd64 is a port to the AMD64 family of processors and - supports all other CPUs that implement the 64bit AMD64 - architecture. These currently include AMD Opteron, AMD Athlon64, - and Intel CPUs with the EM64T extension. - - NetBSD/amd64 is a true 64bit operating system. Running - 32bit NetBSD/i386 binaries is supported as well, see - <a href="http://netbsd.gw.com/cgi-bin/man-cgi?compat_netbsd32+8+NetBSD-5.1+i386">compat_netbsd32(8)</a>. Running 32bit Linux emulations will - be available in the future, the setup will be similar to - the one described in <a href="http://netbsd.gw.com/cgi-bin/man-cgi?compat_svr4_32+8+NetBSD-5.1+i386">compat_svr4_32(8)</a>. - - The port was first committed to the NetBSD source tree as NetBSD/x86_64 - on June 19th, 2001 and renamed to NetBSD/amd64 on April 26th, 2003. - - The original work to do this port was done by Frank van der Linden at - <a class="ulink" href="http://www.wasabisystems.com/" target="_top">Wasabi Systems</a>, assisted by - <a class="ulink" href="http://www.amd.com/" target="_top">AMD</a>, who provided the simulator - (Simics VirtuHammer), pre-release hardware and access to a range - of Opteron hardware through the - <a class="ulink" href="http://developer.amd.com/" target="_top">AMD Developer Center</a>. - - The port is fully functional. It has been tested on single-CPU and - multiprocessor (SMP) Opteron configurations. Since the <a class="ulink" href="../../releases/formal-2.0/NetBSD-2.0.html" target="_top">release of NetBSD 2.0</a>, - it is a completely supported platform. +NetBSD/amd64 is a port to the AMD64 family of processors and +supports all other CPUs that implement the 64bit AMD64 +architecture. These currently include AMD Opteron, AMD Athlon64, +and Intel CPUs with the EM64T extension. + +NetBSD/amd64 is a true 64bit operating system. Running +32bit NetBSD/i386 binaries is supported as well, see +<a href="http://netbsd.gw.com/cgi-bin/man-cgi?compat_netbsd32+8+NetBSD-5.1+i386">compat_netbsd32(8)</a>. Running 32bit Linux emulations will +be available in the future, the setup will be similar to +the one described in <a href="http://netbsd.gw.com/cgi-bin/man-cgi?compat_svr4_32+8+NetBSD-5.1+i386">compat_svr4_32(8)</a>. + +The port was first committed to the NetBSD source tree as NetBSD/x86_64 +on June 19th, 2001 and renamed to NetBSD/amd64 on April 26th, 2003. + +The original work to do this port was done by Frank van der Linden at +<a class="ulink" href="http://www.wasabisystems.com/" target="_top">Wasabi Systems</a>, assisted by +<a class="ulink" href="http://www.amd.com/" target="_top">AMD</a>, who provided the simulator +(Simics VirtuHammer), pre-release hardware and access to a range +of Opteron hardware through the +<a class="ulink" href="http://developer.amd.com/" target="_top">AMD Developer Center</a>. + +The port is fully functional. It has been tested on single-CPU and +multiprocessor (SMP) Opteron configurations. Since the <a class="ulink" href="../../releases/formal-2.0/NetBSD-2.0.html" target="_top">release of NetBSD 2.0</a>, +it is a completely supported platform. - Andrew Doran is the maintainer of NetBSD/amd64. +Andrew Doran is the maintainer of NetBSD/amd64. """
ikiwiki template syntax error
Index: wikisrc/templates/port.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/templates/port.mdwn,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- wikisrc/templates/port.mdwn 15 Apr 2012 20:35:58 -0000 1.2 +++ wikisrc/templates/port.mdwn 15 Apr 2012 20:40:26 -0000 1.3 @@ -1,7 +1,7 @@ <TMPL_IF NAME="port"> [[!meta title="NetBSD/<TMPL_VAR port>"]] -# <TMPL_IF thumbnail><img src=<TMPL_VAR thumbnail> alt="<TMPL_VAR port> thumbnail image"/>NetBSD/<TMPL_VAR port> +# <TMPL_IF thumbnail><img src=<TMPL_VAR thumbnail> alt="<TMPL_VAR port> thumbnail image"/></TMPL_IF>NetBSD/<TMPL_VAR port> ## About NetBSD/<TMPL_VAR port> <TMPL_VAR about>
Changed pages:
ports/amd64
templates/port
Changed by: mspo
Commit type: cvs
Date: late Sunday evening 04/15/12
continue working on new amd64 ports page test
Index: wikisrc/ports/amd64.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/ports/amd64.mdwn,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- wikisrc/ports/amd64.mdwn 15 Apr 2012 20:25:45 -0000 1.1 +++ wikisrc/ports/amd64.mdwn 15 Apr 2012 20:35:58 -0000 1.2 @@ -4,6 +4,35 @@ future_rel="6.0" changes_cur="5.0" changes_future="6.0" +thumbnail="http://www.netbsd.org/images/ports/amd64/AMD_Opteron.gif" +about=""" + NetBSD/amd64 is a port to the AMD64 family of processors and + supports all other CPUs that implement the 64bit AMD64 + architecture. These currently include AMD Opteron, AMD Athlon64, + and Intel CPUs with the EM64T extension. + + NetBSD/amd64 is a true 64bit operating system. Running + 32bit NetBSD/i386 binaries is supported as well, see + <a href="http://netbsd.gw.com/cgi-bin/man-cgi?compat_netbsd32+8+NetBSD-5.1+i386">compat_netbsd32(8)</a>. Running 32bit Linux emulations will + be available in the future, the setup will be similar to + the one described in <a href="http://netbsd.gw.com/cgi-bin/man-cgi?compat_svr4_32+8+NetBSD-5.1+i386">compat_svr4_32(8)</a>. + + The port was first committed to the NetBSD source tree as NetBSD/x86_64 + on June 19th, 2001 and renamed to NetBSD/amd64 on April 26th, 2003. + + The original work to do this port was done by Frank van der Linden at + <a class="ulink" href="http://www.wasabisystems.com/" target="_top">Wasabi Systems</a>, assisted by + <a class="ulink" href="http://www.amd.com/" target="_top">AMD</a>, who provided the simulator + (Simics VirtuHammer), pre-release hardware and access to a range + of Opteron hardware through the + <a class="ulink" href="http://developer.amd.com/" target="_top">AMD Developer Center</a>. + + The port is fully functional. It has been tested on single-CPU and + multiprocessor (SMP) Opteron configurations. Since the <a class="ulink" href="../../releases/formal-2.0/NetBSD-2.0.html" target="_top">release of NetBSD 2.0</a>, + it is a completely supported platform. + + Andrew Doran is the maintainer of NetBSD/amd64. +""" ]] Index: wikisrc/templates/port.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/templates/port.mdwn,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- wikisrc/templates/port.mdwn 15 Apr 2012 20:20:51 -0000 1.1 +++ wikisrc/templates/port.mdwn 15 Apr 2012 20:35:58 -0000 1.2 @@ -1,27 +1,30 @@ <TMPL_IF NAME="port"> [[!meta title="NetBSD/<TMPL_VAR port>"]] -# NetBSD/<TMPL_VAR port> +# <TMPL_IF thumbnail><img src=<TMPL_VAR thumbnail> alt="<TMPL_VAR port> thumbnail image"/>NetBSD/<TMPL_VAR port> ## About NetBSD/<TMPL_VAR port> +<TMPL_VAR about> ## Release Info * [NetBSD/<TMPL_VAR port> <TMPL_VAR cur_rel> via FTP](http://ftp.NetBSD.org/pub/NetBSD/NetBSD-<TMPL_VAR cur_rel>/<TMPL_VAR port>/ "NetBSD/<TMPL_VAR port> FTP") * [NetBSD/<TMPL_VAR port> <TMPL_VAR cur_rel> INSTALL notes](http://ftp.NetBSD.org/pub/NetBSD/NetBSD-<TMPL_VAR cur_rel>/<TMPL_VAR port>/INSTALL.html "NetBSD/<TMPL_VAR port> INSTALL notes") -* [NetBSD/<TMPL_VAR port> <TMPL_VAR cur_rel> pre-build binary packages from pkgsrc](http://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port>/<TMPL_VAR cur_rel>/ "NetBSD/<TMPL_VAR port> pkgsrc binary packages") -* [NetBSD/<TMPL_VAR port> <TMPL_VAR changes_cur> changes](http://www.NetBSD.org/changes/changes-<TMPL_VAR changes_cur>.html#port-<TMPL_VAR port> "NetBSD/<TMPL_VAR port> <TMPL_VAR changes_cur> changes") +* [NetBSD/<TMPL_VAR port> <TMPL_VAR cur_rel> pre-build binary packages from pkgsrc](http://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port>/<TMPL_VAR changes_cur>/ "NetBSD/<TMPL_VAR port> pkgsrc binary packages") * [NetBSD/<TMPL_VAR port> <TMPL_VAR changes_cur> changes](http://www.NetBSD.org/changes/changes-<TMPL_VAR changes_cur>.html#port-<TMPL_VAR port> "NetBSD/<TMPL_VAR port> <TMPL_VAR changes_cur> changes") * [NetBSD/<TMPL_VAR port> <TMPL_VAR changes_future> changes](http://www.NetBSD.org/changes/changes-<TMPL_VAR changes_future>.html#port-<TMPL_VAR port> "NetBSD/<TMPL_VAR port> <TMPL_VAR changes_future> changes") <TMPL_IF supported_hardware> +## Supported Hardware <TMPL_VAR supported_hardware> </TMPL_IF> <TMPL_IF supported_hardware> +## Unsupported Hardware <TMPL_VAR unsupported_hardware> </TMPL_IF> <TMPL_IF additional> +## Additional Info <TMPL_VAR additional> </TMPL_IF>
try a simple ports page first
--- /dev/null 2012-04-15 18:10:10.000000000 +0000 +++ wikisrc/ports/amd64.mdwn 2012-04-15 20:25:47.000000000 +0000 @@ -0,0 +1,9 @@ +[[!template id=port +port="amd64" +cur_rel="5.1.2" +future_rel="6.0" +changes_cur="5.0" +changes_future="6.0" + + +]]
first stab at a template for port pages
--- /dev/null 2012-04-15 18:10:10.000000000 +0000 +++ wikisrc/templates/port.mdwn 2012-04-15 20:20:52.000000000 +0000 @@ -0,0 +1,47 @@ +<TMPL_IF NAME="port"> +[[!meta title="NetBSD/<TMPL_VAR port>"]] + +# NetBSD/<TMPL_VAR port> + +## About NetBSD/<TMPL_VAR port> + +## Release Info +* [NetBSD/<TMPL_VAR port> <TMPL_VAR cur_rel> via FTP](http://ftp.NetBSD.org/pub/NetBSD/NetBSD-<TMPL_VAR cur_rel>/<TMPL_VAR port>/ "NetBSD/<TMPL_VAR port> FTP") +* [NetBSD/<TMPL_VAR port> <TMPL_VAR cur_rel> INSTALL notes](http://ftp.NetBSD.org/pub/NetBSD/NetBSD-<TMPL_VAR cur_rel>/<TMPL_VAR port>/INSTALL.html "NetBSD/<TMPL_VAR port> INSTALL notes") +* [NetBSD/<TMPL_VAR port> <TMPL_VAR cur_rel> pre-build binary packages from pkgsrc](http://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port>/<TMPL_VAR cur_rel>/ "NetBSD/<TMPL_VAR port> pkgsrc binary packages") +* [NetBSD/<TMPL_VAR port> <TMPL_VAR changes_cur> changes](http://www.NetBSD.org/changes/changes-<TMPL_VAR changes_cur>.html#port-<TMPL_VAR port> "NetBSD/<TMPL_VAR port> <TMPL_VAR changes_cur> changes") +* [NetBSD/<TMPL_VAR port> <TMPL_VAR changes_cur> changes](http://www.NetBSD.org/changes/changes-<TMPL_VAR changes_cur>.html#port-<TMPL_VAR port> "NetBSD/<TMPL_VAR port> <TMPL_VAR changes_cur> changes") +* [NetBSD/<TMPL_VAR port> <TMPL_VAR changes_future> changes](http://www.NetBSD.org/changes/changes-<TMPL_VAR changes_future>.html#port-<TMPL_VAR port> "NetBSD/<TMPL_VAR port> <TMPL_VAR changes_future> changes") + +<TMPL_IF supported_hardware> +<TMPL_VAR supported_hardware> +</TMPL_IF> + +<TMPL_IF supported_hardware> +<TMPL_VAR unsupported_hardware> +</TMPL_IF> + +<TMPL_IF additional> +<TMPL_VAR additional> +</TMPL_IF> + +<TMPL_ELSE> +# Ports page template + +The *port* template is used to make the ports pages very easy + +It supports the following parameters: + +- port (required) +- about (required) +- mlist (required) +- cur_rel (required) +- future_rel (required) +- changes_cur (required) +- changes_future (required) +- thumbnail (optional) +- supported_hardware (optional) +- unsupported_hardware (optional) +- additional (optional) + +</TMPL_IF>
add ThinkPad T500
Index: wikisrc/laptops.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/laptops.mdwn,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- wikisrc/laptops.mdwn 19 Jan 2012 23:23:07 -0000 1.11 +++ wikisrc/laptops.mdwn 9 Apr 2012 17:33:30 -0000 1.12 @@ -113,6 +113,13 @@ As close to perfect as one gets. Suspend/resume didn't work at the time; not tried it since. +## Lenovo ThinkPad T500 + +in the version with ATI graphics. Has a tendency to run hot and then to not +reboot cleanly (gets stuck after printing the mainbus line at boot); +5min off for cool-down usually fix this. This doesn't usually occur when +only the Intel on-board graphics get used. No known errors while running. + ## ThinkPad X60s Everything works. Requires `PCI_BUS_FIXUP` and `PCI_ADDR_FIXUP` [[!template
Changed pages:
projects/project/bulktracker
Changed by: dholland
Commit type: cvs
Date: late Sunday night 04/09/12
minor edits
Index: wikisrc/projects/project/bulktracker.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/bulktracker.mdwn,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- wikisrc/projects/project/bulktracker.mdwn 9 Apr 2012 00:31:53 -0000 1.1 +++ wikisrc/projects/project/bulktracker.mdwn 9 Apr 2012 00:36:13 -0000 1.2 @@ -1,13 +1,16 @@ [[!template id=project -title="Bulk Build Tracker Application" +title="Bulk build tracker application" contact=""" [tech-pkg](mailto:tech-pkg@NetBSD.org) """ +mentors="unknown" + category="pkgsrc" difficulty="medium" +duration="unknown" description=""" Currently, bulk build results are sent to the pkgsrc-bulk mailing
Changed pages:
projects/project/bulktracker
Changed by: dholland
Commit type: cvs
Date: late Sunday night 04/09/12
Describe the bulk build tracker that's been talked about on and off
for the last few years. It's too bad I didn't think of putting this
here before the gsoc deadline...
for the last few years. It's too bad I didn't think of putting this
here before the gsoc deadline...
--- /dev/null 2012-04-08 18:10:03.000000000 +0000 +++ wikisrc/projects/project/bulktracker.mdwn 2012-04-09 00:31:55.000000000 +0000 @@ -0,0 +1,79 @@ +[[!template id=project + +title="Bulk Build Tracker Application" + +contact=""" +[tech-pkg](mailto:tech-pkg@NetBSD.org) +""" + +category="pkgsrc" +difficulty="medium" + +description=""" +Currently, bulk build results are sent to the pkgsrc-bulk mailing +list. To figure out if a package is or has been building successfully, +or when it broke, one must wade through the list archives and search +the report e-mails by hand. Furthermore, to figure out what commits if +any were correlated with a breakage, one must wade through the +pkgsrc-changes archive and cross-reference manually. + +The project is to produce a web/database application that can be run +from the pkgsrc releng website on NetBSD.org that tracks bulk build +successes and failures and provides search and crossreferencing +facilities. + +The application should subscribe to the pkgsrc-bulk and pkgsrc-changes +mailing lists and ingest the data it finds into a SQL database. It +should track commits to each package (and possibly infrastructure +changes that might affect all packages) on both HEAD and the current +stable branch, and also all successful and failed build reports on a +per-platform (OS and/or machine type) basis. + +The web part of the application should be able to retrieve summaries +of currently broken packages, in general or for a specific platform +and/or specific branch. It should also be able to generate a more +detailed report about a single package, containing for example which +platforms it has been built on recently and whether it succeeded or +not; also, if it is broken, how long it has been broken, and the +history of package commits and version bumps vs. build results. There +will likely be other searches/reports wanted as well. + +The application should also have an interface for people who do +partial or individual-package check builds; that is, it should be able +to generate a list of packages that have not been built since they +were last committed, on a given platform or possibly on a per-user +basis, and accept results from attempting to build these or subsets of +these packages. It is not entirely clear what this interface should be +(and e.g. whether it should be command-line-based, web-based, or what, +and whether it should be limited to developers) and it's reasonable to +expect that some refinements or rearrangements to it will be needed +after the initial deployment. + +The application should also be able to record cross-references to the +bug database. To begin with at least it's reasonable for this to be +handled manually. + +This project should be a routine web/database application; there is +nothing particularly unusual about it from that standpoint. The part +that becomes somewhat less trivial is making all the data flows work: +for example, it is probably necessary to coordinate an improvement in +the way bulk build results are tagged by platform. It is also +necessary to avoid importing the reports that appear occasionally on +pkgsrc-bulk from misconfigured pbulk installs. + +Note also that "OS" and "machine type" are not the only variables that +can affect build outcome. There are also multiple compilers on some +platforms, for which the results should be tracked separately, plus +other factors such as non-default installation paths. Part of the +planning phase for this project should be to identify all the +variables of this type that should be tracked. + +Also remember that what constitutes a "package" is somewhat slippery +as well. The pkgsrc directory for a package is not a unique key; +multiversion packages, such as Python and Ruby extensions, generate +multiple results from a single package directory. There are also a few +packages where for whatever reason the package name does not match the +pkgsrc directory. The best key seems to be the pkgsrc directory paired +with the package-name-without-version. +""" +]]
Minor improvements/corrections provided by Bug Hunting, added point to the ideas list
Index: wikisrc/users/jdf.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/users/jdf.mdwn,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- wikisrc/users/jdf.mdwn 4 Apr 2012 12:43:17 -0000 1.2 +++ wikisrc/users/jdf.mdwn 7 Apr 2012 22:56:13 -0000 1.3 @@ -12,10 +12,11 @@ * zfs -- there was an attempt to port zfs to NetBSD, but it stalled. Somebody to take care of zfs being imported to NetBSD, and running smooth, would be *very* nice. * HAMMER -- I don't know much about it (see DragonFly BSD), but from what you can read, it seems very nice. Looking at the current state of Oracle and zfs, it might be better to care for HAMMER than zfs. On the other hand, zfs is very stable and widely distributed. * 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. * update -- imho this is being worked on, but I don't remember who it was. Like the freebsd-update tool from FreeBSD, an easy way to update NetBSD base system from binary. Currently, you have to unpack manually and run [[!template id=man section="8" name="etcupdate"]], or use [[!template id=man name="sysinst" section="8"]] for this purpose. Running something that fetches the necessary updates and updates these files would be nice. -* bdutil -- a tool for unified disk editing, and not having to use [[!template id=man name="disklable" section="8"]], [[!template id=man name="gpt" section="8"]], [[!template id=man name="fdisk" section="8"]], [[!template id=man name="dkctl" section="8"]] separately, which can be very confusing, would be very nice. This shouldn't be too difficult. The functionality and the code is there, you just had to think of a usage, rewrite the frontend, and provide a compatibility mode for the old tools. +* bdutil -- a tool for unified disk editing, and not having to use [[!template id=man name="disklabel" section="8"]], [[!template id=man name="gpt" section="8"]], [[!template id=man name="fdisk" section="8"]], and [[!template id=man name="dkctl" section="8"]] separately, which can be very confusing, would be very nice. This shouldn't be too difficult. The functionality and the code is there, you just had to think of a usage, rewrite the frontend, and provide a compatibility mode for the old tools. * 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. +* sysinst -- there is already a marked project for that, and a GSoC-applicant working on this. Generally improve sysinst, provide partitioning for gpt, etc. Perhaps think about porting [[bsdinstaller.org]]. I won't be working on this, as I'm not really into such low-level things: @@ -24,7 +25,7 @@ # My personal interests -I'm not into pkgsrc, but for the easy ones I use regularly, I try to help updating them. +I'm not into pkgsrc, but for the easy packages I use regularly, I try to help updating them. * fixing small userland bugs * importing and caring for sysutils/fscd (a daemon to check service run state) @@ -37,9 +38,9 @@ # Advocacy -Imho, NetBSD currently doesn't have a good visibility in the Open Source community. These are my observations (if I knew solutions, I would write or apply them ;): +Imho, NetBSD currently doesn't have a good visibility in the Open Source community. These are my observations (if I knew solutions, I would write or apply them ;-): * I have seen several smaller software projects which provide compiled binaries on their website, in many cases there was just a reference to "look into your system's package management, it's already there." For nearly all of them, the package is in pkgsrc, but the website doesn't reference it. -* Though NetBSD is represented at most of the larger Open Source events, the advocacy material could be updated. In central Europe, there are already new flyers, badges as giveaways, T-Shirts and badges to sell, but there could be more. If you have ideas, write to netbsd-advocacy@. -* There are many nice projects inside NetBSD, but they aren't visibile from the outside. [[!template id=man name="rump" section="3"]], [[!template id=man name="npf" section="3"]]? The new [[!template id=man name="apropos" section="1"]]? All the prestigous projects are often kept silent, commited, used, but nobody else knows about them. -* For contributors with "minor" interests, i.e. writing small articles, correcting manpages, committing small patches, it seems extraordinarily difficult to get things done. A user-commitable wiki, and some methods to improve developer-contributor communication might help here. +* Though NetBSD is represented at most of the larger Open Source events, the advocacy material could be updated. In central Europe, there are already new flyers, badges as giveaways, T-Shirts and badges to sell, but there could be more. If you have ideas, write to netbsd-advocacy (at) NetBSD (dot) org. +* There are many nice projects within NetBSD, but they aren't very visibile from the outside. [[!template id=man name="rump" section="3"]]? [[!template id=man name="npf" section="3"]]? The new [[!template id=man name="apropos" section="1"]]? All the prestigous projects are often kept silent, commited, used, but most people outside the NetBSD community (and especially *BSD) know about them. +* For contributors with "minor" interests like writing small articles, correcting manpages, and providing other types of small patches, it seems extraordinarily difficult to get things done. A user-commitable wiki, and some methods to improve developer-contributor communication, might help here.
Changed pages:
amazon ec2/amis
Changed by: riz
Commit type: web
Date: late Saturday evening 04/07/12
update one i386 ami
Index: wikisrc/amazon_ec2/amis.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/amazon_ec2/amis.mdwn,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- wikisrc/amazon_ec2/amis.mdwn 26 Mar 2012 03:59:35 -0000 1.10 +++ wikisrc/amazon_ec2/amis.mdwn 7 Apr 2012 21:30:52 -0000 1.11 @@ -72,7 +72,7 @@ </tr> <tr> <th>NetBSD 6.0_BETA</th> - <td>ami-820fddeb</td> + <td>ami-37805e5e</td> <td>ami-e3d68fa6</td> <td>ami-701c9140</td> <td>ami-a72910d3</td>
Changed pages:
users/haad/porting zfs
Changed by: haad
Commit type: web
Date: late Friday morning 04/06/12
Index: wikisrc/users/haad/porting_zfs.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/users/haad/porting_zfs.mdwn,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- wikisrc/users/haad/porting_zfs.mdwn 6 Apr 2012 11:32:45 -0000 1.13 +++ wikisrc/users/haad/porting_zfs.mdwn 6 Apr 2012 11:42:15 -0000 1.14 @@ -70,7 +70,7 @@ I think that we are hitting this bug, too. I have some patches in the tree which fixes deadlod in vnode reclaim but after that I'm getting another deadlock in VOP_FSYNC. * kmem_cache_alloc/ aka pool_cache_get panicsdue to KM_NOSLEEP flag - There are some problems in NetBSD UVM subsytem when KM_NOSLEEP allocation can fail even if system has enough memory to use. I talked with ad@ about it and he said that there is one problem in uvm where some lock is held, KM_NOSLEEP allocation will fail. + There are some problems in the NetBSD UVM subsytem when KM_NOSLEEP allocation can fail even if system has enough memory to use. I talked with ad@ about it and he said that there is one problem in uvm where some lock is held, KM_NOSLEEP allocation will fail. ## Functional bugs * Snapshots
Changed pages:
users/haad/porting zfs
Changed by: haad
Commit type: web
Date: late Friday morning 04/06/12
Index: wikisrc/users/haad/porting_zfs.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/users/haad/porting_zfs.mdwn,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- wikisrc/users/haad/porting_zfs.mdwn 6 Apr 2012 11:24:12 -0000 1.12 +++ wikisrc/users/haad/porting_zfs.mdwn 6 Apr 2012 11:32:45 -0000 1.13 @@ -70,7 +70,7 @@ I think that we are hitting this bug, too. I have some patches in the tree which fixes deadlod in vnode reclaim but after that I'm getting another deadlock in VOP_FSYNC. * kmem_cache_alloc/ aka pool_cache_get panicsdue to KM_NOSLEEP flag - There are some problems in then NetBSD UVM subsytem when KM_NOSLEEP allocation can fail even if system has enough memory to use. I talked with ad@ about it and he said that there is one problem in uvm where some lock is held, KM_NOSLEEP allocation will fail. + There are some problems in NetBSD UVM subsytem when KM_NOSLEEP allocation can fail even if system has enough memory to use. I talked with ad@ about it and he said that there is one problem in uvm where some lock is held, KM_NOSLEEP allocation will fail. ## Functional bugs * Snapshots
Changed pages:
users/haad/porting zfs
Changed by: haad
Commit type: web
Date: late Friday morning 04/06/12
Index: wikisrc/users/haad/porting_zfs.mdwn
===================================================================
RCS file: /home/wiki/cvsroot/wikisrc/users/haad/porting_zfs.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/users/haad/porting_zfs.mdwn 3 Jan 2010 01:33:44 -0000 1.11
+++ wikisrc/users/haad/porting_zfs.mdwn 6 Apr 2012 11:24:12 -0000 1.12
@@ -7,7 +7,7 @@
---
# 2. Using NetBSD ZFS port
-## Instalation
+## Installation
Use any -current build from i386 or amd64 architecture. All tools and modules should be built by default, now. There are 2 modules used for ZFS solaris.kmod and zfs.kmod. Solaris module provides solaris like interfaces to zfs on NetBSD. The second module is zfs and provides zfs file system functions.
@@ -29,7 +29,7 @@
* raidz2
* default is normal linear allocation
-device is blod device on netbsd /dev/sd0a for example.
+device is blod device on NetBSD /dev/sd0a for example.
zpool create tank mirror /dev/sd0a /dev/sd1a creates mirrored zpool between 2 disk partitions.
@@ -70,7 +70,7 @@
I think that we are hitting this bug, too. I have some patches in the tree which fixes deadlod in vnode reclaim but after that I'm getting another deadlock in VOP_FSYNC.
* kmem_cache_alloc/ aka pool_cache_get panicsdue to KM_NOSLEEP flag
- There are some problems in then NEtBSD UVM subsytem when KM_NOSLEEP allocation can fail even if system has enough memory to use. I talked with ad@ about it and he said that there is one problem in uvm where some lock is held, KM_NOSLEEP allocation will fail.
+ There are some problems in then NetBSD UVM subsytem when KM_NOSLEEP allocation can fail even if system has enough memory to use. I talked with ad@ about it and he said that there is one problem in uvm where some lock is held, KM_NOSLEEP allocation will fail.
## Functional bugs
* Snapshots
Added my interests and project ideas to my wiki page
Index: wikisrc/users/jdf.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/users/jdf.mdwn,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- wikisrc/users/jdf.mdwn 4 Apr 2012 11:08:09 -0000 1.1 +++ wikisrc/users/jdf.mdwn 4 Apr 2012 12:43:17 -0000 1.2 @@ -1,3 +1,45 @@ [[!toc ]] # jdf's wiki page + +This is just my wiki page where I want to write down my goals, project ideas, running projects and what I generally want to do. + + +# project ideas + +These project ideas are not sufficient for the [[projects]], perhaps only my own stupid ideas, but what I would like to see for NetBSD. Some of them might be redundant with the official ones, but these are the ones I might personally take care of one day. + +* zfs -- there was an attempt to port zfs to NetBSD, but it stalled. Somebody to take care of zfs being imported to NetBSD, and running smooth, would be *very* nice. +* HAMMER -- I don't know much about it (see DragonFly BSD), but from what you can read, it seems very nice. Looking at the current state of Oracle and zfs, it might be better to care for HAMMER than zfs. On the other hand, zfs is very stable and widely distributed. +* 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 +* update -- imho this is being worked on, but I don't remember who it was. Like the freebsd-update tool from FreeBSD, an easy way to update NetBSD base system from binary. Currently, you have to unpack manually and run [[!template id=man section="8" name="etcupdate"]], or use [[!template id=man name="sysinst" section="8"]] for this purpose. Running something that fetches the necessary updates and updates these files would be nice. +* bdutil -- a tool for unified disk editing, and not having to use [[!template id=man name="disklable" section="8"]], [[!template id=man name="gpt" section="8"]], [[!template id=man name="fdisk" section="8"]], [[!template id=man name="dkctl" section="8"]] separately, which can be very confusing, would be very nice. This shouldn't be too difficult. The functionality and the code is there, you just had to think of a usage, rewrite the frontend, and provide a compatibility mode for the old tools. +* 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. + +I won't be working on this, as I'm not really into such low-level things: + +* run NetBSD in a web browser. There was a project which ran Linux in a web browser. If it's possible, NetBSD should run in a web browser, too. + + +# My personal interests + +I'm not into pkgsrc, but for the easy ones I use regularly, I try to help updating them. + +* fixing small userland bugs +* importing and caring for sysutils/fscd (a daemon to check service run state) +* writing mkdumpdisk - a tool to backup the system, including restore +* caring for [[!template id=pkg category="www" name="opera"]] being up-to-date +* caring for [[!template id=pkg category="devel" name="fossil"]] being up-to-date +* keeping the events site up-to-date +* improving [[!template id=man name="sysinst" section="8"]] + + +# Advocacy + +Imho, NetBSD currently doesn't have a good visibility in the Open Source community. These are my observations (if I knew solutions, I would write or apply them ;): + +* I have seen several smaller software projects which provide compiled binaries on their website, in many cases there was just a reference to "look into your system's package management, it's already there." For nearly all of them, the package is in pkgsrc, but the website doesn't reference it. +* Though NetBSD is represented at most of the larger Open Source events, the advocacy material could be updated. In central Europe, there are already new flyers, badges as giveaways, T-Shirts and badges to sell, but there could be more. If you have ideas, write to netbsd-advocacy@. +* There are many nice projects inside NetBSD, but they aren't visibile from the outside. [[!template id=man name="rump" section="3"]], [[!template id=man name="npf" section="3"]]? The new [[!template id=man name="apropos" section="1"]]? All the prestigous projects are often kept silent, commited, used, but nobody else knows about them. +* For contributors with "minor" interests, i.e. writing small articles, correcting manpages, committing small patches, it seems extraordinarily difficult to get things done. A user-commitable wiki, and some methods to improve developer-contributor communication might help here.
Creation of my wiki page
--- /dev/null 2012-04-04 11:08:09.000000000 +0000 +++ wikisrc/users/jdf.mdwn 2012-04-04 11:08:10.000000000 +0000 @@ -0,0 +1,3 @@ +[[!toc ]] + +# jdf's wiki page
Changed pages:
projects/project/fonthandling
Changed by: dholland
Commit type: cvs
Date: Monday evening 03/26/12
mention xfontsel
Index: wikisrc/projects/project/fonthandling.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/fonthandling.mdwn,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- wikisrc/projects/project/fonthandling.mdwn 26 Mar 2012 19:33:02 -0000 1.3 +++ wikisrc/projects/project/fonthandling.mdwn 26 Mar 2012 19:47:01 -0000 1.4 @@ -31,6 +31,8 @@ 3. Integrate the new solution in base. Things in base that use fonts should use fontconfig or the replacement for fontconfig. This includes console font handling, groff, mandoc, and X11. Also, the existing fonts that are currently available only to subsets of things in base should be made available to all software through fontconfig or its replacement. +3a. It would also be useful to kill off the old xfontsel and replace it with something that interoperates fully with the new system and also has a halfway decent user interface. + 4. Deploy support in pkgsrc. If the new system does not itself provide the fontconfig API, provide support for that via a wrapper package. Teach applications in pkgsrc that use fontconfig to recognize and use the new system. (This should be fairly straightforward and not require patching anything.) Make pkgsrc font installation interoperate with the new system. (This should be fairly straightforward too.) Take an inventory of applications that use fonts but don't use fontconfig. Patch one or two of these to use the new system to show that it can be done easily. If the new system is not fontconfig and has its own better API, take an inventory of applications that would benefit from being patched to use the new API. Patch one or two of these to demonstrate that it can be done easily. (If the answers from step 1 are correct, it should be fairly easy for most ordinary applications.) 5. Persuade the rest of the world that we've done this right and try to get them to adopt the solution. This is particularly important if the solution is not fontconfig. Also, if the solution is not fontconfig, provide a (possibly limited) version of the implementation as a pkgsrc package that can be used on other platforms by packages and applications that support it.
Changed pages:
projects/project/fonthandling
Changed by: dholland
Commit type: cvs
Date: Monday evening 03/26/12
clarify, suggested by dyoung
Index: wikisrc/projects/project/fonthandling.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/fonthandling.mdwn,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- wikisrc/projects/project/fonthandling.mdwn 26 Mar 2012 00:27:56 -0000 1.2 +++ wikisrc/projects/project/fonthandling.mdwn 26 Mar 2012 19:33:02 -0000 1.3 @@ -25,6 +25,8 @@ 1. Figure out for certain if fontconfig is the right solution. Note that even if the code isn't, the model may be. If fontconfig is not the right solution, figure out what the right solution is. Also ascertain whether existing applications that use the fontconfig API can be supported easily/directly or if some kind of possibly messy wrapper layer is needed and doing things *right* requires changing applications. Convince the developer community that your conclusions are correct so that you can go on to step 2. +1a. Part of this is identifying exactly what is involved in "managing" and "handling" fonts and what applications require. + 2. Implement the infrastructure. If fontconfig is the right solution, this entails moving it from the X sources to the base sources. Also, some of the functionality/configurability of fontconfig is probably not needed in a canonicalized environment. All of this should be disabled if possible. If fontconfig is not the right solution, implement something else in base. 3. Integrate the new solution in base. Things in base that use fonts should use fontconfig or the replacement for fontconfig. This includes console font handling, groff, mandoc, and X11. Also, the existing fonts that are currently available only to subsets of things in base should be made available to all software through fontconfig or its replacement.
Changed pages:
amazon ec2/amis
Changed by: riz
Commit type: web
Date: in the wee hours of Sunday night 03/26/12
Update 64-bit 6.0_BETA AMIs
Index: wikisrc/amazon_ec2/amis.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/amazon_ec2/amis.mdwn,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- wikisrc/amazon_ec2/amis.mdwn 27 Feb 2012 02:23:21 -0000 1.9 +++ wikisrc/amazon_ec2/amis.mdwn 26 Mar 2012 03:59:35 -0000 1.10 @@ -5,7 +5,7 @@ They come with [src](http://www.netbsd.org/docs/guide/en/chap-fetch.html) and [pkgsrc](http://www.netbsd.org/docs/pkgsrc/) bundled under */usr/src/* and */usr/pkgsrc/* respectively, or a bootstrap script to help fetch them when necessary. The bootstrap script can also be used to set up binary packages support using pkgin(1). Note: these AMIs send an email to the maintainer on first launch, to -help gauge usage. +help gauge usage. Also, **6.0_BETA images are updated periodically as the beta-testing continues, and the AMIs change.** ## amd64 (x86_64) -- 64 bit AMIs @@ -34,13 +34,13 @@ </tr> <tr> <th>NetBSD 6.0_BETA</th> - <td>ami-56e4363f</td> - <td>ami-0ddf8648</td> - <td>ami-fc038ecc</td> - <td>ami-6f3c051b</td> - <td>ami-68a4e03a</td> - <td>ami-5e1bad5f</td> - <td>ami-1c6eb101</td> + <td>ami-1f8b5576</td> + <td>ami-a383dbe6</td> + <td>ami-2ac04c1a</td> + <td>ami-f71b2383</td> + <td>ami-963d7ac4</td> + <td>ami-e07fcee1</td> + <td>ami-5c835d41</td> </tr> </table>
Changed pages:
projects/project/fonthandling
Changed by: dholland
Commit type: cvs
Date: at midnight 03/26/12
minor adjustment
Index: wikisrc/projects/project/fonthandling.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/fonthandling.mdwn,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- wikisrc/projects/project/fonthandling.mdwn 26 Mar 2012 00:23:40 -0000 1.1 +++ wikisrc/projects/project/fonthandling.mdwn 26 Mar 2012 00:27:56 -0000 1.2 @@ -17,7 +17,7 @@ description=""" Font handling in Unix has long been a disgrace. Every program that needs to deal with fonts has had to do its own thing, and there has never been any system-level support, not even to the point of having a standard place to install fonts in the system. (While there was/is a place to put X11 fonts, X is only one of the many programs doing their own thing.) -Font management should be a system service. There cannot be one type of font file -- it is far too late for that -- but there should be one standardized place for fonts, one unified naming scheme for fonts and styles, and one standard way to look up and open/retrieve/use fonts. +Font management should be a system service. There cannot be one type of font file -- it is far too late for that -- but there should be one standardized place for fonts, one unified naming scheme for fonts and styles, and one standard way to look up and open/retrieve/use fonts. (Note: "one standardized place" means relative to an installation prefix, e.g. share/fonts.) Nowadays fontconfig is capable of providing much of this.
Changed pages:
projects/project/fonthandling
Changed by: dholland
Commit type: cvs
Date: at midnight 03/26/12
Write down my thoughts on system font support.
--- /dev/null 2012-03-25 18:10:02.000000000 +0000 +++ wikisrc/projects/project/fonthandling.mdwn 2012-03-26 00:23:42.000000000 +0000 @@ -0,0 +1,41 @@ +[[!template id=project + +title="System-level font handling in Unix" + +contact=""" +[tech-userlevel](mailto:tech-userlevel@NetBSD.org) +""" + +mentors=""" +[David A. Holland](mailto:dholland@NetBSD.org) +""" + +category="userland" +difficulty="medium" +duration="unknown" + +description=""" +Font handling in Unix has long been a disgrace. Every program that needs to deal with fonts has had to do its own thing, and there has never been any system-level support, not even to the point of having a standard place to install fonts in the system. (While there was/is a place to put X11 fonts, X is only one of the many programs doing their own thing.) + +Font management should be a system service. There cannot be one type of font file -- it is far too late for that -- but there should be one standardized place for fonts, one unified naming scheme for fonts and styles, and one standard way to look up and open/retrieve/use fonts. + +Nowadays fontconfig is capable of providing much of this. + +The project is: + +1. Figure out for certain if fontconfig is the right solution. Note that even if the code isn't, the model may be. If fontconfig is not the right solution, figure out what the right solution is. Also ascertain whether existing applications that use the fontconfig API can be supported easily/directly or if some kind of possibly messy wrapper layer is needed and doing things *right* requires changing applications. Convince the developer community that your conclusions are correct so that you can go on to step 2. + +2. Implement the infrastructure. If fontconfig is the right solution, this entails moving it from the X sources to the base sources. Also, some of the functionality/configurability of fontconfig is probably not needed in a canonicalized environment. All of this should be disabled if possible. If fontconfig is not the right solution, implement something else in base. + +3. Integrate the new solution in base. Things in base that use fonts should use fontconfig or the replacement for fontconfig. This includes console font handling, groff, mandoc, and X11. Also, the existing fonts that are currently available only to subsets of things in base should be made available to all software through fontconfig or its replacement. + +4. Deploy support in pkgsrc. If the new system does not itself provide the fontconfig API, provide support for that via a wrapper package. Teach applications in pkgsrc that use fontconfig to recognize and use the new system. (This should be fairly straightforward and not require patching anything.) Make pkgsrc font installation interoperate with the new system. (This should be fairly straightforward too.) Take an inventory of applications that use fonts but don't use fontconfig. Patch one or two of these to use the new system to show that it can be done easily. If the new system is not fontconfig and has its own better API, take an inventory of applications that would benefit from being patched to use the new API. Patch one or two of these to demonstrate that it can be done easily. (If the answers from step 1 are correct, it should be fairly easy for most ordinary applications.) + +5. Persuade the rest of the world that we've done this right and try to get them to adopt the solution. This is particularly important if the solution is not fontconfig. Also, if the solution is not fontconfig, provide a (possibly limited) version of the implementation as a pkgsrc package that can be used on other platforms by packages and applications that support it. + +Note that step 1 is the hard part. This project requires a good bit of experience and familiarity with Unix and operating system design to allow coming up with a good plan. If you think it's obvious that fontconfig is the right answer and/or you can't see why there might be any reason to change anything about fontconfig, then this may not be the right project for you. + +Because of this, this project is really not suitable for GSoC. + +""" +]]
Changed pages:
projects/project/anita-vms
Changed by: dholland
Commit type: cvs
Date: late Sunday evening 03/25/12
Write out "virtual machine" in the title to avoid having people read it
as "virtual memory systems".
as "virtual memory systems".
Index: wikisrc/projects/project/anita-vms.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/anita-vms.mdwn,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- wikisrc/projects/project/anita-vms.mdwn 6 Nov 2011 14:48:47 -0000 1.2 +++ wikisrc/projects/project/anita-vms.mdwn 25 Mar 2012 21:46:38 -0000 1.3 @@ -1,6 +1,6 @@ [[!template id=project -title="Make Anita support multiple VM systems" +title="Make Anita support multiple virtual machine systems" contact=""" [tech-userlevel](mailto:tech-userlevel@NetBSD.org)
Changed pages:
projects/project/lpr
Changed by: asau
Commit type: cvs
Date: late Sunday evening 03/25/12
Not for students per discussion with <dholland>.
Index: wikisrc/projects/project/lpr.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/lpr.mdwn,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- wikisrc/projects/project/lpr.mdwn 6 Nov 2011 14:48:47 -0000 1.2 +++ wikisrc/projects/project/lpr.mdwn 25 Mar 2012 21:22:32 -0000 1.3 @@ -20,5 +20,3 @@ This project is not intrinsically difficult, but will involve a rather large chunk of work to complete. """ ]] - -[[!tag gsoc]]
Changed pages:
users/ryoon/how to update www firefox
Changed by: ryoon
Commit type: cvs
Date: late Saturday night 03/25/12
Improve sentence.
Index: wikisrc/users/ryoon/how_to_update_www_firefox.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/users/ryoon/how_to_update_www_firefox.mdwn,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- wikisrc/users/ryoon/how_to_update_www_firefox.mdwn 25 Mar 2012 01:27:27 -0000 1.1 +++ wikisrc/users/ryoon/how_to_update_www_firefox.mdwn 25 Mar 2012 01:30:20 -0000 1.2 @@ -16,4 +16,4 @@ 5) Re-install all above packages with latest patches in xulrunner. 6) Apply xulrunner's patches to www/thunderbird and www/seamonkey's mozilla directory. - And add thunderbird or seamonkey specific to patches. + And add thunderbird or seamonkey specific patches to its own patches directory.
Changed pages:
users/how to update www firefox
users/ryoon/how to update www firefox
Changed by: ryoon
Commit type: cvs
Date: late Saturday night 03/25/12
Move to my subdirectory.
--- wikisrc/users/how_to_update_www_firefox.mdwn 2012-03-25 01:27:29.000000000 +0000 +++ /dev/null 2012-03-25 01:23:07.000000000 +0000 @@ -1,19 +0,0 @@ -## How to update www/firefox, mail/thunderbord, devel/xulrunner, devel/nspr, devel/nss, and www/seamonkey and their l10n package. - -1) Update devel/nspr with firefox's source. -// The source tar ball of nspr is provided. Which is better? -// Patches are prepared in xulrunner's patches directory. - -2) Update devel/nss with firefox's source. -// nss's tar ball is not provided. It must be extracted from firefox's - source tar ball. -// Patches are prepared in xulrunner's patches directory. - -3) Update devel/xulrunner with firefox's source. - -4) Update www/firefox - -5) Re-install all above packages with latest patches in xulrunner. - -6) Apply xulrunner's patches to www/thunderbird and www/seamonkey's mozilla directory. - And add thunderbird or seamonkey specific to patches. --- /dev/null 2012-03-25 01:23:07.000000000 +0000 +++ wikisrc/users/ryoon/how_to_update_www_firefox.mdwn 2012-03-25 01:27:29.000000000 +0000 @@ -0,0 +1,19 @@ +## How to update www/firefox, mail/thunderbord, devel/xulrunner, devel/nspr, devel/nss, and www/seamonkey and their l10n package. + +1) Update devel/nspr with firefox's source. +// The source tar ball of nspr is provided. Which is better? +// Patches are prepared in xulrunner's patches directory. + +2) Update devel/nss with firefox's source. +// nss's tar ball is not provided. It must be extracted from firefox's + source tar ball. +// Patches are prepared in xulrunner's patches directory. + +3) Update devel/xulrunner with firefox's source. + +4) Update www/firefox + +5) Re-install all above packages with latest patches in xulrunner. + +6) Apply xulrunner's patches to www/thunderbird and www/seamonkey's mozilla directory. + And add thunderbird or seamonkey specific to patches.
Changed pages:
users/how to update www firefox
Changed by: ryoon
Commit type: web
Date: late Saturday night 03/25/12
FIx typo.
Index: wikisrc/users/how_to_update_www_firefox.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/users/how_to_update_www_firefox.mdwn,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- wikisrc/users/how_to_update_www_firefox.mdwn 25 Mar 2012 01:22:38 -0000 1.1 +++ wikisrc/users/how_to_update_www_firefox.mdwn 25 Mar 2012 01:23:07 -0000 1.2 @@ -1,4 +1,4 @@ -## How to update www/firefox, mail/thunderbord}, devel/xulrunner, devel/nspr, devel/nss, and www/seamonkey and their l10n package. +## How to update www/firefox, mail/thunderbord, devel/xulrunner, devel/nspr, devel/nss, and www/seamonkey and their l10n package. 1) Update devel/nspr with firefox's source. // The source tar ball of nspr is provided. Which is better?
Changed pages:
users/how to update www firefox
Changed by: ryoon
Commit type: web
Date: late Saturday night 03/25/12
Add firefox update memo.
--- /dev/null 2012-03-25 01:22:38.000000000 +0000 +++ wikisrc/users/how_to_update_www_firefox.mdwn 2012-03-25 01:22:39.000000000 +0000 @@ -0,0 +1,19 @@ +## How to update www/firefox, mail/thunderbord}, devel/xulrunner, devel/nspr, devel/nss, and www/seamonkey and their l10n package. + +1) Update devel/nspr with firefox's source. +// The source tar ball of nspr is provided. Which is better? +// Patches are prepared in xulrunner's patches directory. + +2) Update devel/nss with firefox's source. +// nss's tar ball is not provided. It must be extracted from firefox's + source tar ball. +// Patches are prepared in xulrunner's patches directory. + +3) Update devel/xulrunner with firefox's source. + +4) Update www/firefox + +5) Re-install all above packages with latest patches in xulrunner. + +6) Apply xulrunner's patches to www/thunderbird and www/seamonkey's mozilla directory. + And add thunderbird or seamonkey specific to patches.
Add firefox update memo link.
Index: wikisrc/users/ryoon.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/users/ryoon.mdwn,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- wikisrc/users/ryoon.mdwn 3 Mar 2012 07:53:45 -0000 1.11 +++ wikisrc/users/ryoon.mdwn 25 Mar 2012 01:20:46 -0000 1.12 @@ -16,3 +16,4 @@ * [[How to install NetBSD emips current to Microsoft Giano]] * [[NetBSD in bloom; repository visualisation (video)|http://www.scivee.tv/node/32819]] * [[pbulk in chroot on non-NetBSD platform|pbulk_non-netbsd]] +* [[How to update www/firefox etc|how_to_update_www_firefox]]
Changed pages:
users/riz/issues-6
Changed by: martin
Commit type: web
Date: late Friday evening 03/23/12
Index: wikisrc/users/riz/issues-6.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/users/riz/issues-6.mdwn,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- wikisrc/users/riz/issues-6.mdwn 23 Mar 2012 18:59:00 -0000 1.5 +++ wikisrc/users/riz/issues-6.mdwn 23 Mar 2012 20:38:42 -0000 1.6 @@ -16,3 +16,4 @@ ### misc bugs: * [[PR 46217: CARP hangs on boot|http://gnats.netbsd.org/46217]] +* [[PR 46232: pad (audio pseudo device) locking issue|http://gnats.netbsd.org/46232]]
Index: wikisrc/users/riz/issues-6.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/users/riz/issues-6.mdwn,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- wikisrc/users/riz/issues-6.mdwn 5 Feb 2012 01:03:39 -0000 1.4 +++ wikisrc/users/riz/issues-6.mdwn 23 Mar 2012 18:59:00 -0000 1.5 @@ -9,6 +9,10 @@ * amiga mem sizing issue * shark issues -### Post-branch stuff wanted for pullup: -* Postfix 2.8.8 +### toolchain bugs: +* gcc 4.5.1 (optimizer) bugs on VAX [[PR 46033|http://gnats.netbsd.org/46033]], [[PR 46098|http://gnats.netbsd.org/46098]], [[PR 46251|http://gnats.netbsd.org/46251]] + + +### misc bugs: +* [[PR 46217: CARP hangs on boot|http://gnats.netbsd.org/46217]]
Make it easy to create (from the web) a new project page using the template.
Index: wikisrc/projects.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects.mdwn,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- wikisrc/projects.mdwn 9 Nov 2011 21:14:02 -0000 1.9 +++ wikisrc/projects.mdwn 21 Mar 2012 12:10:31 -0000 1.10 @@ -33,3 +33,19 @@ * [[Google Summer of Code|gsoc]] * [[Google Code-In|code-in]] (contains some ideas) + +# Add a project + +[[!edittemplate +template="project" +match="projects/project/*" +silent=yes +]] + +[[!inline +pages="empty and pagespec" +feeds=no +rootpage="projects/project" +postform=yes +postformtext="Add a new project page:" +]]
Changed pages:
projects/project/asan-port
Changed by: joerg
Commit type: web
Date: mid-morning Wednesday 03/21/12
Index: wikisrc/projects/project/asan-port.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/asan-port.mdwn,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- wikisrc/projects/project/asan-port.mdwn 21 Mar 2012 10:22:20 -0000 1.3 +++ wikisrc/projects/project/asan-port.mdwn 21 Mar 2012 10:22:56 -0000 1.4 @@ -3,7 +3,7 @@ title="ASAN port" contact=""" -[tech-net](mailto:tech-kern@NetBSD.org), +[tech-kern](mailto:tech-kern@NetBSD.org), [tech-userlevel](mailto:tech-userlevel@NetBSD.org) """
Changed pages:
projects/project/asan-port
Changed by: joerg
Commit type: web
Date: mid-morning Wednesday 03/21/12
Index: wikisrc/projects/project/asan-port.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/asan-port.mdwn,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- wikisrc/projects/project/asan-port.mdwn 21 Mar 2012 10:21:50 -0000 1.2 +++ wikisrc/projects/project/asan-port.mdwn 21 Mar 2012 10:22:20 -0000 1.3 @@ -13,7 +13,7 @@ duration="3 months" description=""" -The Address Sanity Checker is a part of the LLVM stack. +The Address Sanitizer is a part of the LLVM stack. It provides a feature set similar to Valgrind. The goal of this project is:
Changed pages:
projects/project/asan-port
Changed by: joerg
Commit type: web
Date: mid-morning Wednesday 03/21/12
Expand stub somewhat
Index: wikisrc/projects/project/asan-port.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/asan-port.mdwn,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- wikisrc/projects/project/asan-port.mdwn 21 Mar 2012 10:15:05 -0000 1.1 +++ wikisrc/projects/project/asan-port.mdwn 21 Mar 2012 10:21:50 -0000 1.2 @@ -3,17 +3,23 @@ title="ASAN port" contact=""" -[tech-net](mailto:tech-net@NetBSD.org), +[tech-net](mailto:tech-kern@NetBSD.org), [tech-userlevel](mailto:tech-userlevel@NetBSD.org) """ mentor="Jörg Sonnenberger" category="userland" -difficulty="easy" +difficulty="medium" duration="3 months" description=""" -Description to be created +The Address Sanity Checker is a part of the LLVM stack. +It provides a feature set similar to Valgrind. +The goal of this project is: + +- Ensure compiler_rt with ASAN works on NetBSD +- Provide the changes for libc to optionally override assembler implementations like memcpy. +- Add support for using ASAN in the kernel """ ]]
Changed pages:
projects/project/asan-port
Changed by: spz
Commit type: cvs
Date: mid-morning Wednesday 03/21/12
seed project form
--- /dev/null 2012-03-21 10:00:36.000000000 +0000 +++ wikisrc/projects/project/asan-port.mdwn 2012-03-21 10:15:27.000000000 +0000 @@ -0,0 +1,20 @@ +[[!template id=project + +title="ASAN port" + +contact=""" +[tech-net](mailto:tech-net@NetBSD.org), +[tech-userlevel](mailto:tech-userlevel@NetBSD.org) +""" + +mentor="Jörg Sonnenberger" +category="userland" +difficulty="easy" +duration="3 months" + +description=""" +Description to be created +""" +]] + +[[!tag gsoc]]
Changed pages:
projects/project/pkgsrc spawn support
Changed by: joerg
Commit type: web
Date: mid-morning Wednesday 03/21/12
The far majority of the changes necessary is easy in nature, so downgrade difficulty.
Index: wikisrc/projects/project/pkgsrc_spawn_support.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/pkgsrc_spawn_support.mdwn,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- wikisrc/projects/project/pkgsrc_spawn_support.mdwn 17 Mar 2012 22:15:40 -0000 1.8 +++ wikisrc/projects/project/pkgsrc_spawn_support.mdwn 21 Mar 2012 10:00:36 -0000 1.9 @@ -11,7 +11,7 @@ """ category="pkgsrc" -difficulty="medium" +difficulty="easy" duration="3 months" description="""
Index: wikisrc/kerberos.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/kerberos.mdwn,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- wikisrc/kerberos.mdwn 11 Nov 2009 10:33:12 -0000 1.3 +++ wikisrc/kerberos.mdwn 18 Mar 2012 17:24:50 -0000 1.4 @@ -1,3 +1,5 @@ +## NETBSD.ORG Kerberos + * [[password]] * [[system]] * [[web_browser]]
Changed pages:
projects/project/sysinst-enhancements
Changed by: martin
Commit type: web
Date: mid-morning Sunday 03/18/12
Index: wikisrc/projects/project/sysinst-enhancements.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/sysinst-enhancements.mdwn,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- wikisrc/projects/project/sysinst-enhancements.mdwn 18 Mar 2012 10:58:04 -0000 1.4 +++ wikisrc/projects/project/sysinst-enhancements.mdwn 18 Mar 2012 10:59:14 -0000 1.5 @@ -25,7 +25,7 @@ The installer currently supports installing the system to any available single disk. It is possible to select which parts (distribution sets) of the system to install, and also to customise the disk partition layout. Sysinst can also use vnode pseudo disks, so can be tested without the need to re-install the host system. -The first goal is to allow partitioning disks using the GUID partition table (GPT). The current partitioning code is tight heavily to the BSD disklabel. Fixing it is straight forward, but both methods have to be offered and only some architectures can boot from GPT disks. +The first goal is to allow partitioning disks using the GUID partition table (GPT). The current partitioning code is tied heavily to the BSD disklabel. Fixing it is straight forward, but both methods have to be offered and only some architectures can boot from GPT disks. The second goal is to allow preparing several disks. This part would also be usefull (see "other enhancements" below) as a stand-alone tool. Various disks may be partitioned using different shemes, for example when the boot disk can not use GPT, but secondary (large) disks should use it. This part also is a direct prerequisite for the following one.
Changed pages:
projects/project/sysinst-enhancements
Changed by: martin
Commit type: web
Date: mid-morning Sunday 03/18/12
Index: wikisrc/projects/project/sysinst-enhancements.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/sysinst-enhancements.mdwn,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- wikisrc/projects/project/sysinst-enhancements.mdwn 17 Mar 2012 20:21:45 -0000 1.3 +++ wikisrc/projects/project/sysinst-enhancements.mdwn 18 Mar 2012 10:58:04 -0000 1.4 @@ -17,25 +17,22 @@ description=""" The goal of this project is to enhance the NetBSD system installer (sysinst) to provide additional support for (in order): -* installation on multiple disks -* installation on RAID -* installation on GPT -* installation on cgd -* installation on LVM +* partition disks using GPT +* prepare multiple disks +* combine multiple partitions to raid/lvm volumes +* encrypt partitions via cgd * other enhancements The installer currently supports installing the system to any available single disk. It is possible to select which parts (distribution sets) of the system to install, and also to customise the disk partition layout. Sysinst can also use vnode pseudo disks, so can be tested without the need to re-install the host system. -The first goal is to add the support for multiple disks to sysinst. When this is finished, it will be possible to partition multiple disks, add filesystem mount points across the multiple disks, and to select the boot disk. +The first goal is to allow partitioning disks using the GUID partition table (GPT). The current partitioning code is tight heavily to the BSD disklabel. Fixing it is straight forward, but both methods have to be offered and only some architectures can boot from GPT disks. -The second goal is to add support for creating and installing on to RAID (levels 0, 1 and 1+0) partitions. Note, that it is currently possible to install on to an existing RAID parition, but not to create one. When installing to RAID 1 or RAID 1+0, it should be possible to install the boot code to all of the mirror disks. +The second goal is to allow preparing several disks. This part would also be usefull (see "other enhancements" below) as a stand-alone tool. Various disks may be partitioned using different shemes, for example when the boot disk can not use GPT, but secondary (large) disks should use it. This part also is a direct prerequisite for the following one. -The third goal is to add support for formatting and partitioning a disk with GPT instead of disklabel. +The third goal is to (optionally) create logical volumes from multiple partitions or disks, either using raidframe or LVM. This includes making the volumes bootable, if possible. The fourth goal is to add support for creating and installing on to cgd (encrypted) partitions. The initial support will not be for the boot partition, but other partitions should be supported. -The fifth goal is to add support for creating and installing on to LVM Volume Groups and Logical Volumes. This should be similar to the RAID goal, above. - The other enhancements that might be possible are (not in priority order): #### user interface
Converting to pkgsrc X.org step by step.
--- /dev/null 2012-03-17 20:28:49.000000000 +0000 +++ wikisrc/pkgsrc/x11.mdwn 2012-03-18 00:04:37.000000000 +0000 @@ -0,0 +1,8 @@ +# pkgsrc X.org + +Converting to pkgsrc X.org step by step: + +1. "pkg_delete -r x11-links" - to remove all packages that depend on X11 (it is needed). +2. "make clean" - for all your tree, so that you don't capture some stale dependency on native X11. +3. Set "X11_TYPE=modular" in mk.conf +4. Rebuild your packages.
Changed pages:
projects/project/pkgsrc spawn support
Changed by: wiz
Commit type: cvs
Date: Saturday night 03/17/12
Fix typo.
I do not believe this will take 3 months.
I do not believe this will take 3 months.
Index: wikisrc/projects/project/pkgsrc_spawn_support.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/pkgsrc_spawn_support.mdwn,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- wikisrc/projects/project/pkgsrc_spawn_support.mdwn 17 Mar 2012 20:54:10 -0000 1.7 +++ wikisrc/projects/project/pkgsrc_spawn_support.mdwn 17 Mar 2012 22:15:40 -0000 1.8 @@ -32,7 +32,7 @@ * NetBSD base make * NetBSD sh * NetBSD base ksh -* potentially some other tools (e.g. land/nawk, shells/bash, lang/perl5) +* potentially some other tools (e.g. lang/nawk, shells/bash, lang/perl5) Optionally, MinGW spawn support can be added as well.
Changed pages:
projects/project/pkgsrc tls support in tnftp
Changed by: asau
Commit type: cvs
Date: Saturday night 03/17/12
TLS support in net/tnftp.
--- /dev/null 2012-03-17 20:28:49.000000000 +0000 +++ wikisrc/projects/project/pkgsrc_tls_support_in_tnftp.mdwn 2012-03-17 22:12:07.000000000 +0000 @@ -0,0 +1,29 @@ +[[!template id=project + +title="TLS (HTTPS) support in net/tnftp" + +contact=""" +[tech-pkg](mailto:tech-pkg@NetBSD.org) +""" + +mentors=""" +[Aleksej Saushev](mailto:asau@NetBSD.org) +""" + +category="pkgsrc" +difficulty="medium" +duration="3 months" + +description=""" +The lack of TLS support in default file fetch program (net/tnftp) +demands employing various tricks and hacks when creating packages. +Growing number of Internet sites that use HTTPS, and software +development communities around such sites (e.g. GitHub) demands, +consequently, support for fetching files via HTTPS. + +The goal of this project is adding TLS support (HTTPS at least) +to devel/tnftp and NetBSD base ftp program. +""" +]] + +[[!tag gsoc]]
Changed pages:
projects/project/pkgsrc precise dependencies
Changed by: asau
Commit type: cvs
Date: late Saturday evening 03/17/12
Tool to find dependencies precisely.
--- /dev/null 2012-03-17 20:28:49.000000000 +0000 +++ wikisrc/projects/project/pkgsrc_precise_dependencies.mdwn 2012-03-17 21:53:10.000000000 +0000 @@ -0,0 +1,34 @@ +[[!template id=project + +title="Tool to find dependencies precisely" + +contact=""" +[tech-pkg](mailto:tech-pkg@NetBSD.org) +""" + +mentors=""" +[Aleksej Saushev](mailto:asau@NetBSD.org) +""" + +category="pkgsrc" +difficulty="hard" +duration="3 months" + +description=""" +Dependency handling in pkgsrc is rather complex task. +There exist some cases (TeX packages, Perl packages) where it is +hard to find build dependencies precisely and the whole thing is +handled conservatively. E.g. the whole TeXLive meta-package is +declared a build dependency even when rather small fraction of +it is used actually. Another case is stale heavy dependency +which is no longer required but still listed as prerequisite. + +It would be nice to have a tool (or a set of them, if necessary) +to detect which installed packages, libraries or tools were +actually used to build new package. Ideally, the tool should +report files used during configure, build, and test stages, +and packages these files are provided by. +""" +]] + +[[!tag gsoc]]
Changed pages:
projects/project/pkgsrc spawn support
Changed by: asau
Commit type: cvs
Date: late Saturday evening 03/17/12
Fix markup.
Index: wikisrc/projects/project/pkgsrc_spawn_support.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/pkgsrc_spawn_support.mdwn,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- wikisrc/projects/project/pkgsrc_spawn_support.mdwn 17 Mar 2012 20:53:21 -0000 1.6 +++ wikisrc/projects/project/pkgsrc_spawn_support.mdwn 17 Mar 2012 20:54:10 -0000 1.7 @@ -26,6 +26,7 @@ compare the efficiency of both ways of launching subprocesses and measure its effect when using pkgsrc (both in user and developer mode). In order to accomplish that, the following tools should support posix_spawn: + * devel/bmake * shells/pdksh * NetBSD base make
Changed pages:
projects/project/pkgsrc spawn support
Changed by: asau
Commit type: cvs
Date: late Saturday evening 03/17/12
More markup.
Index: wikisrc/projects/project/pkgsrc_spawn_support.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/pkgsrc_spawn_support.mdwn,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- wikisrc/projects/project/pkgsrc_spawn_support.mdwn 17 Mar 2012 20:44:32 -0000 1.5 +++ wikisrc/projects/project/pkgsrc_spawn_support.mdwn 17 Mar 2012 20:53:21 -0000 1.6 @@ -26,10 +26,14 @@ compare the efficiency of both ways of launching subprocesses and measure its effect when using pkgsrc (both in user and developer mode). In order to accomplish that, the following tools should support posix_spawn: -devel/bmake, NetBSD base make, shells/pdksh, NetBSD sh, NetBSD base ksh, -potentially some other tools (e.g. land/nawk, shells/bash, lang/perl5). +* devel/bmake +* shells/pdksh +* NetBSD base make +* NetBSD sh +* NetBSD base ksh +* potentially some other tools (e.g. land/nawk, shells/bash, lang/perl5) -Optionally, MinGW spawn support could be added as well. +Optionally, MinGW spawn support can be added as well. The main goal of this project is to support starting processes and subprocesses by posix_spawn in devel/bmake and in shells/pdksh,
Changed pages:
projects/project/pkgsrc spawn support
Changed by: asau
Commit type: cvs
Date: late Saturday evening 03/17/12
Capitalize title.
Index: wikisrc/projects/project/pkgsrc_spawn_support.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/pkgsrc_spawn_support.mdwn,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- wikisrc/projects/project/pkgsrc_spawn_support.mdwn 17 Mar 2012 20:43:45 -0000 1.4 +++ wikisrc/projects/project/pkgsrc_spawn_support.mdwn 17 Mar 2012 20:44:32 -0000 1.5 @@ -1,6 +1,6 @@ [[!template id=project -title="spawn support in pkgsrc tools" +title="Spawn support in pkgsrc tools" contact=""" [tech-pkg](mailto:tech-pkg@NetBSD.org)
Changed pages:
projects/project/pkgsrc spawn support
Changed by: asau
Commit type: cvs
Date: late Saturday evening 03/17/12
Add GSoC tag.
Index: wikisrc/projects/project/pkgsrc_spawn_support.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/pkgsrc_spawn_support.mdwn,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- wikisrc/projects/project/pkgsrc_spawn_support.mdwn 17 Mar 2012 20:40:46 -0000 1.3 +++ wikisrc/projects/project/pkgsrc_spawn_support.mdwn 17 Mar 2012 20:43:45 -0000 1.4 @@ -36,3 +36,5 @@ measure its efficiency and compare it to traditional fork+exec. """ ]] + +[[!tag gsoc]]
Changed pages:
projects/project/pkgsrc spawn support
Changed by: asau
Commit type: cvs
Date: late Saturday evening 03/17/12
Make it of medium complexity.
Index: wikisrc/projects/project/pkgsrc_spawn_support.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/pkgsrc_spawn_support.mdwn,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- wikisrc/projects/project/pkgsrc_spawn_support.mdwn 17 Mar 2012 20:39:24 -0000 1.2 +++ wikisrc/projects/project/pkgsrc_spawn_support.mdwn 17 Mar 2012 20:40:46 -0000 1.3 @@ -11,7 +11,7 @@ """ category="pkgsrc" -difficulty="easy" +difficulty="medium" duration="3 months" description="""
Changed pages:
projects/project/pkgsrc spawn support
Changed by: asau
Commit type: cvs
Date: late Saturday evening 03/17/12
Make it more general.
Index: wikisrc/projects/project/pkgsrc_spawn_support.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/pkgsrc_spawn_support.mdwn,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- wikisrc/projects/project/pkgsrc_spawn_support.mdwn 17 Mar 2012 20:34:30 -0000 1.1 +++ wikisrc/projects/project/pkgsrc_spawn_support.mdwn 17 Mar 2012 20:39:24 -0000 1.2 @@ -1,6 +1,6 @@ [[!template id=project -title="posix_spawn support in bmake and pdksh" +title="spawn support in pkgsrc tools" contact=""" [tech-pkg](mailto:tech-pkg@NetBSD.org)
Changed pages:
projects/project/pkgsrc spawn support
Changed by: asau
Commit type: cvs
Date: late Saturday evening 03/17/12
Spawn (posix_spawn) support for pkgsrc tools.
--- /dev/null 2012-03-17 20:28:49.000000000 +0000 +++ wikisrc/projects/project/pkgsrc_spawn_support.mdwn 2012-03-17 20:34:31.000000000 +0000 @@ -0,0 +1,38 @@ +[[!template id=project + +title="posix_spawn support in bmake and pdksh" + +contact=""" +[tech-pkg](mailto:tech-pkg@NetBSD.org) +""" + +mentors=""" +[Aleksej Saushev](mailto:asau@NetBSD.org) +""" + +category="pkgsrc" +difficulty="easy" +duration="3 months" + +description=""" +There exist two ways of launching processes: one is forking them +with fork or vfork and replacing the clone with exec-family function, +another is spawning process directly with procedures like posix_spawn. +Not all platforms implement fork model, and spawn model has its own merits. + +pkgsrc relies heavily on launching subprocesses when building software. +NetBSD posix_spawn support was implemented in GSoC 2011, it is included +in NetBSD 6.0. Now that NetBSD supports both ways, it would be nice to +compare the efficiency of both ways of launching subprocesses and measure +its effect when using pkgsrc (both in user and developer mode). +In order to accomplish that, the following tools should support posix_spawn: +devel/bmake, NetBSD base make, shells/pdksh, NetBSD sh, NetBSD base ksh, +potentially some other tools (e.g. land/nawk, shells/bash, lang/perl5). + +Optionally, MinGW spawn support could be added as well. + +The main goal of this project is to support starting processes and +subprocesses by posix_spawn in devel/bmake and in shells/pdksh, +measure its efficiency and compare it to traditional fork+exec. +""" +]]
Changed pages:
projects/project/live-upgrade
Changed by: spz
Commit type: web
Date: late Saturday evening 03/17/12
typo
Index: wikisrc/projects/project/live-upgrade.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/live-upgrade.mdwn,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- wikisrc/projects/project/live-upgrade.mdwn 6 Nov 2011 14:48:47 -0000 1.2 +++ wikisrc/projects/project/live-upgrade.mdwn 17 Mar 2012 20:28:49 -0000 1.3 @@ -15,7 +15,7 @@ duration="3 months" description=""" -Updating an operating system image can be fraught with danger, an error could cause the system to be unbootable and require significant work to restore the system to operation. The aim of this project is to permit a system to be updated while it is running only requiring a reboot to activate the updated system and provide the facility to rollback to a "known good" system in the even that the update causes regressions. The project should do the following: +Updating an operating system image can be fraught with danger, an error could cause the system to be unbootable and require significant work to restore the system to operation. The aim of this project is to permit a system to be updated while it is running only requiring a reboot to activate the updated system and provide the facility to rollback to a "known good" system in the event that the update causes regressions. The project should do the following: * Make a copy of the currently running system * Either apply patches, install binary sets, run a source build with the copy as the install target
Changed pages:
projects/project/sysinst-enhancements
Changed by: spz
Commit type: web
Date: late Saturday evening 03/17/12
Index: wikisrc/projects/project/sysinst-enhancements.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/sysinst-enhancements.mdwn,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- wikisrc/projects/project/sysinst-enhancements.mdwn 6 Nov 2011 14:48:47 -0000 1.2 +++ wikisrc/projects/project/sysinst-enhancements.mdwn 17 Mar 2012 20:21:45 -0000 1.3 @@ -7,7 +7,7 @@ """ mentors=""" -[Marc Balmer](mailto:mbalmer@NetBSD.org), [Martin Husemann](mailto:martin@NetBSD.org) +[Martin Husemann](mailto:martin@NetBSD.org) """ category="userland" @@ -19,19 +19,22 @@ * installation on multiple disks * installation on RAID +* installation on GPT * installation on cgd * installation on LVM * other enhancements -The installer currently suuports installing the system to any available single disk. It is possible to select which parts (distribution sets) of the system to install, and also to customise the disk partition layout. Sysinst can also use vnode psuedo disks, so can be tested without the need to re-install the host system. +The installer currently supports installing the system to any available single disk. It is possible to select which parts (distribution sets) of the system to install, and also to customise the disk partition layout. Sysinst can also use vnode pseudo disks, so can be tested without the need to re-install the host system. The first goal is to add the support for multiple disks to sysinst. When this is finished, it will be possible to partition multiple disks, add filesystem mount points across the multiple disks, and to select the boot disk. The second goal is to add support for creating and installing on to RAID (levels 0, 1 and 1+0) partitions. Note, that it is currently possible to install on to an existing RAID parition, but not to create one. When installing to RAID 1 or RAID 1+0, it should be possible to install the boot code to all of the mirror disks. -The third goal is to add support for creating and installing on to cgd (encrypted) partitions. The initial support will not be for the boot partition, but other partitions should be supported. +The third goal is to add support for formatting and partitioning a disk with GPT instead of disklabel. -The fourth goal is to add support for creating and installing on to LVM Volume Groups and Logical Volumes. This should be similar to the RAID goal, above. +The fourth goal is to add support for creating and installing on to cgd (encrypted) partitions. The initial support will not be for the boot partition, but other partitions should be supported. + +The fifth goal is to add support for creating and installing on to LVM Volume Groups and Logical Volumes. This should be similar to the RAID goal, above. The other enhancements that might be possible are (not in priority order):
Changed pages:
projects/gsoc
Changed by: jschauma
Commit type: cvs
Date: late Friday afternoon 03/16/12
let's use english
Index: wikisrc/projects/gsoc.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/gsoc.mdwn,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- wikisrc/projects/gsoc.mdwn 16 Mar 2012 17:53:53 -0000 1.8 +++ wikisrc/projects/gsoc.mdwn 16 Mar 2012 17:57:48 -0000 1.9 @@ -9,7 +9,7 @@ [2009](http://www.netbsd.org/foundation/press/soc2009.html), [2010](http://blog.netbsd.org/tnf/entry/google_summer_of_code_2010), [2011](http://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of)) and -we are please to once again participate as a mentoring organization in 2012. +we are pleased to once again participate as a mentoring organization in 2012. This page contains a list of concrete suggestions for projects we would like to see applications for in the next Summer of Code. Note that they
Changed pages:
projects/gsoc
Changed by: jschauma
Commit type: cvs
Date: late Friday afternoon 03/16/12
gsoc 2012 is on
Index: wikisrc/projects/gsoc.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/gsoc.mdwn,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- wikisrc/projects/gsoc.mdwn 4 Feb 2012 20:41:08 -0000 1.7 +++ wikisrc/projects/gsoc.mdwn 16 Mar 2012 17:53:53 -0000 1.8 @@ -9,7 +9,7 @@ [2009](http://www.netbsd.org/foundation/press/soc2009.html), [2010](http://blog.netbsd.org/tnf/entry/google_summer_of_code_2010), [2011](http://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of)) and -we are planning to apply again as a mentoring organization in 2012. +we are please to once again participate as a mentoring organization in 2012. This page contains a list of concrete suggestions for projects we would like to see applications for in the next Summer of Code. Note that they
Changed pages:
users/jun/machines
Changed by: jun
Commit type: web
Date: at lunch time on Sunday 03/04/12
fill hpcmips,hpcarm,hpcsh,zaurus status
Index: wikisrc/users/jun/machines.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/users/jun/machines.mdwn,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- wikisrc/users/jun/machines.mdwn 29 Feb 2012 04:39:41 -0000 1.6 +++ wikisrc/users/jun/machines.mdwn 4 Mar 2012 12:24:20 -0000 1.7 @@ -1,6 +1,5 @@ machine status - <TABLE FRAME=VOID CELLSPACING=0 COLS=10 RULES=NONE BORDER=0> <COLGROUP><COL WIDTH=105><COL WIDTH=91><COL WIDTH=117><COL WIDTH=47><COL WIDTH=55><COL WIDTH=92><COL WIDTH=86><COL WIDTH=86><COL WIDTH=65><COL WIDTH=298></COLGROUP> <TBODY> @@ -125,21 +124,21 @@ <TD ALIGN=LEFT>6以é™ã€ãƒ—ãƒã‚°ãƒ©ãƒ ãŒä¸è¦å‰‡ã«Seg fault.</TD> </TR> <TR> - <TD HEIGHT=16 ALIGN=LEFT><FONT FACE="Liberation Sans">Jornada 680</FONT></TD> + <TD HEIGHT=19 ALIGN=LEFT><FONT FACE="Liberation Sans">Jornada 680</FONT></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">hpcsh</FONT></TD> - <TD ALIGN=LEFT SDNUM="1041;0;@">未ç€æ‰‹</TD> - <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> + <TD ALIGN=LEFT SDNUM="1041;0;@"><FONT FACE="Liberation Sans">5.99.56/20111115</FONT></TD> <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> + <TD ALIGN=LEFT SDNUM="1041;0;@">ç‰¹è¨˜äº‹é …å‚ç…§</TD> <TD ALIGN=LEFT><BR></TD> <TD ALIGN=LEFT><BR></TD> <TD ALIGN=LEFT><BR></TD> - <TD ALIGN=LEFT><BR></TD> + <TD ALIGN=LEFT>6以é™ã€ãƒ—ãƒã‚°ãƒ©ãƒ ãŒä¸è¦å‰‡ã«Seg fault.</TD> </TR> <TR> <TD HEIGHT=16 ALIGN=LEFT><FONT FACE="Liberation Sans">Jornada 720</FONT></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">hpcarm</FONT></TD> - <TD ALIGN=LEFT SDNUM="1041;0;@">未ç€æ‰‹</TD> + <TD ALIGN=LEFT SDNUM="1041;0;@"><FONT FACE="Liberation Sans">5.99.38</FONT></TD> <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> @@ -151,7 +150,7 @@ <TR> <TD HEIGHT=16 ALIGN=LEFT><FONT FACE="Liberation Sans">Persona 30</FONT></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">hpcsh</FONT></TD> - <TD ALIGN=LEFT SDNUM="1041;0;@">未ç€æ‰‹</TD> + <TD ALIGN=LEFT SDNUM="1041;0;@"><FONT FACE="Liberation Sans">5.99.56/20111115</FONT></TD> <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD>
Clarify savecore settings.
Index: wikisrc/panic.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/panic.mdwn,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- wikisrc/panic.mdwn 3 Mar 2012 14:56:48 -0000 1.4 +++ wikisrc/panic.mdwn 3 Mar 2012 15:24:16 -0000 1.5 @@ -48,8 +48,10 @@ The dump of memory will be written to the swap partition. -At boot time, if rc.conf(5) has value "savecore=yes", -the swap file coredump will be saved to "/var/crash". +At boot time the swap file coredump will be saved to "/var/crash". +The following settings control this behaviour +(they are set by default in /etc/defaults/rc.conf), +you don't usually need to change those: savecore=yes savecore_flags="-N /netbsd -z"
Fix spelling.
From Moritz Wilhelmy via #netbsd
From Moritz Wilhelmy via #netbsd
Index: wikisrc/panic.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/panic.mdwn,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- wikisrc/panic.mdwn 2 Dec 2010 21:47:25 -0000 1.3 +++ wikisrc/panic.mdwn 3 Mar 2012 14:56:48 -0000 1.4 @@ -96,7 +96,7 @@ ## Processing the CORE Dump -Heubert Feyrer has a great guide to analyzing kernel panic core dumps at <http://www.feyrer.de/NetBSD/bx/blosxom.cgi/index.front?-tags=gdb> +Hubert Feyrer has a great guide to analyzing kernel panic core dumps at <http://www.feyrer.de/NetBSD/bx/blosxom.cgi/index.front?-tags=gdb> Additionally, the following command below can be used to create a relatively useful backtrace:
Update DragonFly test environment to 3.0.1.
Index: wikisrc/users/ryoon.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/users/ryoon.mdwn,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- wikisrc/users/ryoon.mdwn 6 Jan 2012 21:43:46 -0000 1.10 +++ wikisrc/users/ryoon.mdwn 3 Mar 2012 07:53:45 -0000 1.11 @@ -7,7 +7,7 @@ ### Test environments * NetBSD/i386 current -* DragonFly/i386 2.10.1 +* DragonFly/i386 3.0.1 * NetBSD/i386 5.1 * Gentoo Linux/i386 (version unknown) * NetBSD/cobalt 5.1
PR lib/40346 has been fixed.
Index: wikisrc/hackathon.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/hackathon.mdwn,v retrieving revision 1.34 retrieving revision 1.35 diff -u -r1.34 -r1.35 --- wikisrc/hackathon.mdwn 12 Feb 2012 20:03:03 -0000 1.34 +++ wikisrc/hackathon.mdwn 2 Mar 2012 18:47:55 -0000 1.35 @@ -77,7 +77,7 @@ * [[PR 41936|http://gnats.NetBSD.org/41936]]: gdb does not work for threaded programs on sparc64 * [[PR 41208|http://gnats.NetBSD.org/41208]]: objcopy -S -O binary aborts w/ BFD internal error * <s>[[PR 41127|http://gnats.NetBSD.org/41127]]: Update/improve newfs docs regarding raw devices</s> -* work in progress: [[PR 40346|http://gnats.NetBSD.org/40346]]: libexpat should be in base.tgz +* fixed: [[PR 40346|http://gnats.NetBSD.org/40346]]: libexpat should be in base.tgz * [[PR 9582|http://gnats.NetBSD.org/9582]]: sysinst doesn't allow source or pkgsrc installation * [[PR 38571|http://gnats.NetBSD.org/38571]]: sysinst runs "postinstall fix" * [[PR 12769|http://gnats.NetBSD.org/12769]]: clarify the upgrade notes for when the sets are on /usr
Changed pages:
users/jun/machines
Changed by: jun
Commit type: web
Date: in the wee hours of Tuesday night 02/29/12
hpcmips almost done.waiting for building ruby package.next update:hpcsh.
Index: wikisrc/users/jun/machines.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/users/jun/machines.mdwn,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- wikisrc/users/jun/machines.mdwn 27 Feb 2012 04:34:36 -0000 1.5 +++ wikisrc/users/jun/machines.mdwn 29 Feb 2012 04:39:41 -0000 1.6 @@ -1,18 +1,19 @@ machine status -<TABLE FRAME=VOID CELLSPACING=0 COLS=9 RULES=NONE BORDER=0> - <COLGROUP><COL WIDTH=105><COL WIDTH=91><COL WIDTH=117><COL WIDTH=47><COL WIDTH=55><COL WIDTH=92><COL WIDTH=86><COL WIDTH=86><COL WIDTH=298></COLGROUP> +<TABLE FRAME=VOID CELLSPACING=0 COLS=10 RULES=NONE BORDER=0> + <COLGROUP><COL WIDTH=105><COL WIDTH=91><COL WIDTH=117><COL WIDTH=47><COL WIDTH=55><COL WIDTH=92><COL WIDTH=86><COL WIDTH=86><COL WIDTH=65><COL WIDTH=298></COLGROUP> <TBODY> <TR> <TD WIDTH=105 HEIGHT=16 ALIGN=LEFT><FONT FACE="Liberation Sans">6.99.3</FONT></TD> - <TD WIDTH=91 ALIGN=RIGHT SDVAL="20120221" SDNUM="1041;"><FONT FACE="Liberation Sans">20120221</FONT></TD> + <TD WIDTH=91 ALIGN=RIGHT SDVAL="20120228" SDNUM="1041;"><FONT FACE="Liberation Sans">20120228</FONT></TD> <TD WIDTH=117 ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> <TD WIDTH=47 ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> <TD WIDTH=55 ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> <TD WIDTH=92 ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> <TD WIDTH=86 ALIGN=LEFT><BR></TD> <TD WIDTH=86 ALIGN=LEFT><BR></TD> + <TD WIDTH=65 ALIGN=LEFT><BR></TD> <TD WIDTH=298 ALIGN=LEFT><BR></TD> </TR> <TR> @@ -24,6 +25,7 @@ <TD ALIGN=LEFT SDNUM="1041;0;@"><FONT FACE="Liberation Sans">6.99.3</FONT></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">X11</FONT></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">icewm/xli/xv</FONT></TD> + <TD ALIGN=LEFT>ホストå</TD> <TD ALIGN=LEFT>ç‰¹è¨˜äº‹é …</TD> </TR> <TR> @@ -35,6 +37,7 @@ <TD ALIGN=LEFT SDNUM="1041;0;@"><FONT FACE="Liberation Sans">Boot</FONT></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">Yes</FONT></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">Yes</FONT></TD> + <TD ALIGN=LEFT><FONT FACE="Liberation Sans">amir51</FONT></TD> <TD ALIGN=LEFT><BR></TD> </TR> <TR> @@ -46,6 +49,7 @@ <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">Yes</FONT></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">Yes</FONT></TD> + <TD ALIGN=LEFT><FONT FACE="Liberation Sans">amiasp1</FONT></TD> <TD ALIGN=LEFT><BR></TD> </TR> <TR> @@ -57,17 +61,19 @@ <TD ALIGN=LEFT SDNUM="1041;0;@"><FONT FACE="Liberation Sans">Boot</FONT></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">Yes</FONT></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">Yes</FONT></TD> + <TD ALIGN=LEFT><FONT FACE="Liberation Sans">amix23</FONT></TD> <TD ALIGN=LEFT>PCI_*_FIXUP有効ã«ã™ã‚‹ã€‚Wiã§é€šä¿¡ã§ããªã„。</TD> </TR> <TR> <TD HEIGHT=16 ALIGN=LEFT><FONT FACE="Liberation Sans">Thinkpad X61</FONT></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">amd64</FONT></TD> - <TD ALIGN=LEFT SDNUM="1041;0;@">未ç€æ‰‹</TD> + <TD ALIGN=LEFT SDNUM="1041;0;@"><FONT FACE="Liberation Sans">5.99.58</FONT></TD> <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> - <TD ALIGN=LEFT><BR></TD> - <TD ALIGN=LEFT><BR></TD> + <TD ALIGN=LEFT><FONT FACE="Liberation Sans">Yes</FONT></TD> + <TD ALIGN=LEFT><FONT FACE="Liberation Sans">Yes</FONT></TD> + <TD ALIGN=LEFT><FONT FACE="Liberation Sans">amix61</FONT></TD> <TD ALIGN=LEFT><BR></TD> </TR> <TR> @@ -79,6 +85,7 @@ <TD ALIGN=LEFT SDNUM="1041;0;@"><FONT FACE="Liberation Sans">BootFail</FONT></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">Yes</FONT></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">Yes</FONT></TD> + <TD ALIGN=LEFT><FONT FACE="Liberation Sans">amiws11</FONT></TD> <TD ALIGN=LEFT><BR></TD> </TR> <TR> @@ -90,9 +97,22 @@ <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">Yes</FONT></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">Yes</FONT></TD> + <TD ALIGN=LEFT><FONT FACE="Liberation Sans">amizs1</FONT></TD> <TD ALIGN=LEFT><BR></TD> </TR> <TR> + <TD HEIGHT=16 ALIGN=LEFT><FONT FACE="Liberation Sans">Workpad Z50</FONT></TD> + <TD ALIGN=LEFT><FONT FACE="Liberation Sans">hpcmips</FONT></TD> + <TD ALIGN=LEFT SDNUM="1041;0;@"><FONT FACE="Liberation Sans">5.1.2</FONT></TD> + <TD ALIGN=LEFT SDNUM="1041;0;@">æ£å¸¸</TD> + <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> + <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> + <TD ALIGN=LEFT><FONT FACE="Liberation Sans">Yes</FONT></TD> + <TD ALIGN=LEFT> </TD> + <TD ALIGN=LEFT><FONT FACE="Liberation Sans">amips3</FONT></TD> + <TD ALIGN=LEFT>展示機</TD> + </TR> + <TR> <TD HEIGHT=19 ALIGN=LEFT><FONT FACE="Liberation Sans">Workpad Z50</FONT></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">hpcmips</FONT></TD> <TD ALIGN=LEFT SDNUM="1041;0;@"><FONT FACE="Liberation Sans">5.1.2</FONT></TD> @@ -100,7 +120,8 @@ <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> <TD ALIGN=LEFT SDNUM="1041;0;@">ç‰¹è¨˜äº‹é …å‚ç…§</TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">Yes</FONT></TD> - <TD ALIGN=LEFT><BR></TD> + <TD ALIGN=LEFT> </TD> + <TD ALIGN=LEFT><FONT FACE="Liberation Sans">amips1</FONT></TD> <TD ALIGN=LEFT>6以é™ã€ãƒ—ãƒã‚°ãƒ©ãƒ ãŒä¸è¦å‰‡ã«Seg fault.</TD> </TR> <TR> @@ -113,6 +134,7 @@ <TD ALIGN=LEFT><BR></TD> <TD ALIGN=LEFT><BR></TD> <TD ALIGN=LEFT><BR></TD> + <TD ALIGN=LEFT><BR></TD> </TR> <TR> <TD HEIGHT=16 ALIGN=LEFT><FONT FACE="Liberation Sans">Jornada 720</FONT></TD> @@ -124,6 +146,7 @@ <TD ALIGN=LEFT><BR></TD> <TD ALIGN=LEFT><BR></TD> <TD ALIGN=LEFT><BR></TD> + <TD ALIGN=LEFT><BR></TD> </TR> <TR> <TD HEIGHT=16 ALIGN=LEFT><FONT FACE="Liberation Sans">Persona 30</FONT></TD> @@ -135,41 +158,33 @@ <TD ALIGN=LEFT><BR></TD> <TD ALIGN=LEFT><BR></TD> <TD ALIGN=LEFT><BR></TD> + <TD ALIGN=LEFT><BR></TD> </TR> <TR> <TD HEIGHT=19 ALIGN=LEFT><FONT FACE="Liberation Sans">Sigmarion</FONT></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">hpcmips</FONT></TD> - <TD ALIGN=LEFT SDNUM="1041;0;@"><FONT FACE="Liberation Sans">5.1.2</FONT></TD> + <TD ALIGN=LEFT SDNUM="1041;0;@"><FONT FACE="Liberation Sans">5.99.22</FONT></TD> <TD ALIGN=LEFT SDNUM="1041;0;@">æ£å¸¸</TD> <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> <TD ALIGN=LEFT SDNUM="1041;0;@">ç‰¹è¨˜äº‹é …å‚ç…§</TD> + <TD ALIGN=LEFT><FONT FACE="Liberation Sans">Yes</FONT></TD> <TD ALIGN=LEFT><BR></TD> - <TD ALIGN=LEFT><BR></TD> + <TD ALIGN=LEFT><FONT FACE="Liberation Sans">amips4</FONT></TD> <TD ALIGN=LEFT>6以é™ã€ãƒ—ãƒã‚°ãƒ©ãƒ ãŒä¸è¦å‰‡ã«Seg fault.</TD> </TR> <TR> <TD HEIGHT=19 ALIGN=LEFT><FONT FACE="Liberation Sans">SigmarionII</FONT></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">hpcmips</FONT></TD> - <TD ALIGN=LEFT SDNUM="1041;0;@"><FONT FACE="Liberation Sans">5.99.43</FONT></TD> - <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> + <TD ALIGN=LEFT SDNUM="1041;0;@"><FONT FACE="Liberation Sans">5.1.2</FONT></TD> + <TD ALIGN=LEFT SDNUM="1041;0;@">æ£å¸¸</TD> <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> - <TD ALIGN=LEFT><FONT FACE="Liberation Sans">No</FONT></TD> - <TD ALIGN=LEFT><BR></TD> + <TD ALIGN=LEFT><FONT FACE="Liberation Sans">Yes</FONT></TD> + <TD ALIGN=LEFT> </TD> + <TD ALIGN=LEFT><FONT FACE="Liberation Sans">amips2</FONT></TD> <TD ALIGN=LEFT>5.99.43ã¾ã§ã¯è½ã¡ãªã„。Xã¯èµ·å‹•ã—ãªã„。</TD> </TR> <TR> - <TD HEIGHT=16 ALIGN=LEFT><FONT FACE="Liberation Sans">MobleGear 520</FONT></TD> - <TD ALIGN=LEFT><FONT FACE="Liberation Sans">hpcmips</FONT></TD> - <TD ALIGN=LEFT SDNUM="1041;0;@">未ç€æ‰‹</TD> - <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> - <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> - <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> - <TD ALIGN=LEFT><BR></TD> - <TD ALIGN=LEFT><BR></TD> - <TD ALIGN=LEFT><BR></TD> - </TR> - <TR> <TD HEIGHT=16 ALIGN=LEFT><FONT FACE="Liberation Sans">Dreamcast</FONT></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">dreamcast</FONT></TD> <TD ALIGN=LEFT SDNUM="1041;0;@">未ç€æ‰‹</TD> @@ -179,6 +194,7 @@ <TD ALIGN=LEFT><BR></TD> <TD ALIGN=LEFT><BR></TD> <TD ALIGN=LEFT><BR></TD> + <TD ALIGN=LEFT><BR></TD> </TR> <TR> <TD HEIGHT=16 ALIGN=LEFT><FONT FACE="Liberation Sans">XM6i</FONT></TD> @@ -190,6 +206,7 @@ <TD ALIGN=LEFT><BR></TD> <TD ALIGN=LEFT><BR></TD> <TD ALIGN=LEFT><BR></TD> + <TD ALIGN=LEFT><BR></TD> </TR> (Diff truncated)
Changed pages:
projects/project/mksysb-utility
Changed by: blymn
Commit type: web
Date: mid-morning Monday 02/27/12
removed
--- wikisrc/projects/project/mksysb-utility.mdwn 2012-02-27 10:43:10.000000000 +0000 +++ /dev/null 2012-02-27 10:43:10.000000000 +0000 @@ -1,40 +0,0 @@ -[[!template id=project - -title="MKSYSB like backup utility" - -contact=""" -[tech-userlevel](mailto:tech-userlevel@NetBSD.org) -""" - -mentors=""" -[Adam Hamsik](mailto:haad@NetBSD.org), [Brett Blymn](mailto:blymn@netbsd.org) -""" - -category="userland" -difficulty="medium" -duration="3 months" - -description=""" -NetBSD (and other BSD systems) would benefit from a utility which can be used to create a bootable backup image from the whole system and burn it to USB flash disk or write it to iso/DVD. - -Many Unixes have such a command: - -* Solaris - flasharchive -* Aix - mksysb - -Write a new tool which can use dump to flash a backup of the filesystem and will add boot, disk conditioning and restore capability, and write the result to a flash, disk or iso image. - -After booting from the created media the user should be able to restore the system to its previous state from the booted media mostly automatically. - -This project should be implemented as portable as possible so it can be later used by other BSDs with only small modifications. - -Project Timeline - -* During the first half of the project the student should write the tool to make a bootable filesystem backup that contains the necessary tools to restore the system. -* In the second half of the project, the boot code for the restore media should be adjusted to include automatic system restore; the integration into the base system should be prepared, and documentation with manual pages and in the NetBSD Guide should be written. - -As an example see the [mksysb manual page from aix](http://publib.boulder.ibm.com/infocenter/aix/v6r1/index.jsp?topic=/com.ibm.aix.cmds/doc/aixcmds3/mksysb.htm). -""" -]] - -[[!tag gsoc]]
Changed pages:
projects/project/xen4/comment 1 eace1929e77be2911e22dccfdd91dbee
Changed by: id [www.google.com/accounts/o8]
Commit type: web
Date: early Monday morning 02/27/12
Added a comment: missing gntdev
--- /dev/null 2012-02-27 09:42:47.000000000 +0000 +++ wikisrc/projects/project/xen4/comment_1_eace1929e77be2911e22dccfdd91dbee._comment 2012-02-27 09:42:48.000000000 +0000 @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmgqKnAf_1tKBJrWPW7Wt3k_aOfi3A3YbQ" + nickname="Roger" + subject="missing gntdev" + date="2012-02-27T09:42:46Z" + content=""" +NetBSD is also missing an important Xen interface, the Grant table device for allowing user-space tools to interact with memory. I think it's quite important to get this into future NetBSD releases, since some features depend on that (like qemu), maybe it will we worth adding a GSoC project for that task (although I don't know how hard it is). +"""]]
Changed pages:
projects/project/apropos
Changed by: spz
Commit type: web
Date: early Monday morning 02/27/12
Index: wikisrc/projects/project/apropos.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/apropos.mdwn,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- wikisrc/projects/project/apropos.mdwn 6 Nov 2011 14:48:47 -0000 1.2 +++ wikisrc/projects/project/apropos.mdwn 27 Feb 2012 07:44:02 -0000 1.3 @@ -13,6 +13,7 @@ category="userland" difficulty="easy" duration="3 months" +done_by="Abhinav Upadhyay" description=""" NetBSD ships a lot of useful documentation in the form of manual pages.
Changed pages:
projects/project/pkgsrc-create-other-packages
Changed by: spz
Commit type: web
Date: early Monday morning 02/27/12
Index: wikisrc/projects/project/pkgsrc-create-other-packages.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/pkgsrc-create-other-packages.mdwn,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- wikisrc/projects/project/pkgsrc-create-other-packages.mdwn 6 Nov 2011 14:48:47 -0000 1.2 +++ wikisrc/projects/project/pkgsrc-create-other-packages.mdwn 27 Feb 2012 07:43:20 -0000 1.3 @@ -13,6 +13,7 @@ category="pkgsrc" difficulty="easy" duration="3 months" +done_by="Anton Panev" description=""" In 2006 and 2007, the pkgsrc build system was abstracted to allow packaging for other package system packages. For details see [pkgsrc/mk/flavor/README](http://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/mk/flavor/README) and the [original commit message](http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/mk/flavor/bsd.flavor.mk?rev=1.1&content-type=text/x-cvsweb-markup).
Changed pages:
projects/project/putter pud puffs
Changed by: spz
Commit type: web
Date: early Monday morning 02/27/12
Index: wikisrc/projects/project/putter_pud_puffs.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/putter_pud_puffs.mdwn,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- wikisrc/projects/project/putter_pud_puffs.mdwn 6 Nov 2011 14:48:47 -0000 1.2 +++ wikisrc/projects/project/putter_pud_puffs.mdwn 27 Feb 2012 07:42:29 -0000 1.3 @@ -13,6 +13,7 @@ category="userland" difficulty="easy" duration="3 months" +done_by="Vyacheslav Matyushin" description=""" As is well-known, [puffs(3)](http://netbsd.gw.com/cgi-bin/man-cgi?puffs+3+NetBSD-5.1+i386) is the NetBSD userspace file system framework. It provides support for implementing file servers in userspace. A lesser known "cousin" of puffs is the Pass-to-Userspace Device, or [pud(4)](http://netbsd.gw.com/cgi-bin/man-cgi?pud+4+NetBSD-5.1+i386) framework, which provides support for implementing character and block device servers in userspace. Both use [putter(9)](http://netbsd.gw.com/cgi-bin/man-cgi?putter+9+NetBSD-5.1+i386) for transmitting requests to and from the kernel.
Changed pages:
projects/project/rfc6056
Changed by: spz
Commit type: web
Date: early Monday morning 02/27/12
Index: wikisrc/projects/project/rfc6056.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/projects/project/rfc6056.mdwn,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- wikisrc/projects/project/rfc6056.mdwn 6 Nov 2011 14:48:47 -0000 1.2 +++ wikisrc/projects/project/rfc6056.mdwn 27 Feb 2012 07:40:02 -0000 1.3 @@ -13,6 +13,7 @@ category="kernel" difficulty="easy" duration="3 months" +done_by="Vlad Balan" description=""" When using connect(2) to connect the client end of a socket, the system will choose the next number of the socket for you. Having an easily guessed port number can allow various attacks to take place. Choosing the next port number at random, whilst not perfect, gives more protection against these attacks.
Changed pages:
users/jun/machines
Changed by: jun
Commit type: web
Date: in the wee hours of Sunday night 02/27/12
hpcmips: SigmarionII (5.99.43 20110104 works well.after 5.99.43 huge mips changes, hpcmips port still unstable now. )
Index: wikisrc/users/jun/machines.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/users/jun/machines.mdwn,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- wikisrc/users/jun/machines.mdwn 26 Feb 2012 09:55:07 -0000 1.4 +++ wikisrc/users/jun/machines.mdwn 27 Feb 2012 04:34:36 -0000 1.5 @@ -1,6 +1,6 @@ machine status -<BODY TEXT="#000000"> + <TABLE FRAME=VOID CELLSPACING=0 COLS=9 RULES=NONE BORDER=0> <COLGROUP><COL WIDTH=105><COL WIDTH=91><COL WIDTH=117><COL WIDTH=47><COL WIDTH=55><COL WIDTH=92><COL WIDTH=86><COL WIDTH=86><COL WIDTH=298></COLGROUP> <TBODY> @@ -148,6 +148,17 @@ <TD ALIGN=LEFT>6以é™ã€ãƒ—ãƒã‚°ãƒ©ãƒ ãŒä¸è¦å‰‡ã«Seg fault.</TD> </TR> <TR> + <TD HEIGHT=19 ALIGN=LEFT><FONT FACE="Liberation Sans">SigmarionII</FONT></TD> + <TD ALIGN=LEFT><FONT FACE="Liberation Sans">hpcmips</FONT></TD> + <TD ALIGN=LEFT SDNUM="1041;0;@"><FONT FACE="Liberation Sans">5.99.43</FONT></TD> + <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> + <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> + <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> + <TD ALIGN=LEFT><FONT FACE="Liberation Sans">No</FONT></TD> + <TD ALIGN=LEFT><BR></TD> + <TD ALIGN=LEFT>5.99.43ã¾ã§ã¯è½ã¡ãªã„。Xã¯èµ·å‹•ã—ãªã„。</TD> + </TR> + <TR> <TD HEIGHT=16 ALIGN=LEFT><FONT FACE="Liberation Sans">MobleGear 520</FONT></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">hpcmips</FONT></TD> <TD ALIGN=LEFT SDNUM="1041;0;@">未ç€æ‰‹</TD>
Changed pages:
amazon ec2/amis
Changed by: riz
Commit type: cvs
Date: in the wee hours of Sunday night 02/27/12
Add i386 AMI identifiers for 6.0_BETA.
Index: wikisrc/amazon_ec2/amis.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/amazon_ec2/amis.mdwn,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- wikisrc/amazon_ec2/amis.mdwn 25 Feb 2012 18:16:43 -0000 1.8 +++ wikisrc/amazon_ec2/amis.mdwn 27 Feb 2012 02:23:21 -0000 1.9 @@ -72,12 +72,12 @@ </tr> <tr> <th>NetBSD 6.0_BETA</th> - <td>soon</td> - <td>soon</td> - <td>soon</td> - <td>soon</td> - <td>soon</td> - <td>soon</td> - <td>soon</td> + <td>ami-820fddeb</td> + <td>ami-e3d68fa6</td> + <td>ami-701c9140</td> + <td>ami-a72910d3</td> + <td>ami-c8a2e69a</td> + <td>ami-2405b325</td> + <td>ami-a86db2b5</td> </tr> </table>
Index: wikisrc/users/spz.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/users/spz.mdwn,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- wikisrc/users/spz.mdwn 16 Jan 2012 08:00:37 -0000 1.11 +++ wikisrc/users/spz.mdwn 26 Feb 2012 10:50:15 -0000 1.12 @@ -1,5 +1,3 @@ *[[Admin Notes|admin]] -*[[Security Reference List|secref]] - -*[[Security Reference List V2|spz/secref2]] +*[[Security Reference List|spz/secref2]]
Changed pages:
projects/project/posix spawn
Changed by: martin
Commit type: web
Date: mid-morning Sunday 02/26/12
removed
--- wikisrc/projects/project/posix_spawn.mdwn 2012-02-26 10:48:33.000000000 +0000 +++ /dev/null 2012-02-26 10:48:33.000000000 +0000 @@ -1,38 +0,0 @@ -[[!template id=project - -title="In-kernel implementation of posix_spawn" - -contact=""" -[tech-kern](mailto:tech-kern@NetBSD.org) -""" - -mentors=""" -[Matt Thomas](mailto:matt@NetBSD.org), [Mindaugas Rasiukevicius](mailto:rmind@NetBSD.org) -""" - -category="kernel" -difficulty="medium" -duration="3 months" - -description=""" -A few years ago NetBSD got a real vfork(2) implementation and it was shown at the time, that this offers a measurable performance benefit for fork intensive work loads like build.sh release. -vfork avoids the overhead of marking the process as copy on write. -Fast forward to the current time. -A lot of services are now implemented by multithreaded programs. -vfork(2) and multithreading don't play well with each other. -Additionally, SMP systems are the norm now and creating and shortly after killing an address space is not cheap. -Processes have also grown a lot and a plain fork() is quite expensive from a 8GB JVM. - -POSIX added an interface that for this purpose: posix_spawn. -This is a combined fork+exec and can be used to implement popen and more advanced things. -FreeBSD and some other systems have a userspace implementation, which works, but can't reap the benefits mentioned above. - -Implementing a real posix_spawn system calls could do that. -Measuring the impact for different work loads makes a nice research paper as side effect. -This includes both estimate the temporary memory used and the performance implications. - -The API is part of the [Single Unix Specification](http://pubs.opengroup.org/onlinepubs/9699919799/functions/posix_spawn.html). -""" -]] - -[[!tag gsoc]]
Changed pages:
users/jun/machines
Changed by: jun
Commit type: web
Date: early Sunday morning 02/26/12
update hpcmips status: 5.1.2(work fine),6(boot, but program randomly fall into Segmentation Fault)
Index: wikisrc/users/jun/machines.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/users/jun/machines.mdwn,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- wikisrc/users/jun/machines.mdwn 22 Feb 2012 13:31:02 -0000 1.3 +++ wikisrc/users/jun/machines.mdwn 26 Feb 2012 09:55:07 -0000 1.4 @@ -1,7 +1,8 @@ machine status +<BODY TEXT="#000000"> <TABLE FRAME=VOID CELLSPACING=0 COLS=9 RULES=NONE BORDER=0> - <COLGROUP><COL WIDTH=105><COL WIDTH=91><COL WIDTH=117><COL WIDTH=47><COL WIDTH=55><COL WIDTH=56><COL WIDTH=86><COL WIDTH=86><COL WIDTH=298></COLGROUP> + <COLGROUP><COL WIDTH=105><COL WIDTH=91><COL WIDTH=117><COL WIDTH=47><COL WIDTH=55><COL WIDTH=92><COL WIDTH=86><COL WIDTH=86><COL WIDTH=298></COLGROUP> <TBODY> <TR> <TD WIDTH=105 HEIGHT=16 ALIGN=LEFT><FONT FACE="Liberation Sans">6.99.3</FONT></TD> @@ -9,7 +10,7 @@ <TD WIDTH=117 ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> <TD WIDTH=47 ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> <TD WIDTH=55 ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> - <TD WIDTH=56 ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> + <TD WIDTH=92 ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> <TD WIDTH=86 ALIGN=LEFT><BR></TD> <TD WIDTH=86 ALIGN=LEFT><BR></TD> <TD WIDTH=298 ALIGN=LEFT><BR></TD> @@ -92,15 +93,15 @@ <TD ALIGN=LEFT><BR></TD> </TR> <TR> - <TD HEIGHT=16 ALIGN=LEFT><FONT FACE="Liberation Sans">Workpad Z50</FONT></TD> + <TD HEIGHT=19 ALIGN=LEFT><FONT FACE="Liberation Sans">Workpad Z50</FONT></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">hpcmips</FONT></TD> - <TD ALIGN=LEFT SDNUM="1041;0;@">未ç€æ‰‹</TD> - <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> - <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> + <TD ALIGN=LEFT SDNUM="1041;0;@"><FONT FACE="Liberation Sans">5.1.2</FONT></TD> + <TD ALIGN=LEFT SDNUM="1041;0;@">æ£å¸¸</TD> <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> + <TD ALIGN=LEFT SDNUM="1041;0;@">ç‰¹è¨˜äº‹é …å‚ç…§</TD> + <TD ALIGN=LEFT><FONT FACE="Liberation Sans">Yes</FONT></TD> <TD ALIGN=LEFT><BR></TD> - <TD ALIGN=LEFT><BR></TD> - <TD ALIGN=LEFT><BR></TD> + <TD ALIGN=LEFT>6以é™ã€ãƒ—ãƒã‚°ãƒ©ãƒ ãŒä¸è¦å‰‡ã«Seg fault.</TD> </TR> <TR> <TD HEIGHT=16 ALIGN=LEFT><FONT FACE="Liberation Sans">Jornada 680</FONT></TD> @@ -136,6 +137,17 @@ <TD ALIGN=LEFT><BR></TD> </TR> <TR> + <TD HEIGHT=19 ALIGN=LEFT><FONT FACE="Liberation Sans">Sigmarion</FONT></TD> + <TD ALIGN=LEFT><FONT FACE="Liberation Sans">hpcmips</FONT></TD> + <TD ALIGN=LEFT SDNUM="1041;0;@"><FONT FACE="Liberation Sans">5.1.2</FONT></TD> + <TD ALIGN=LEFT SDNUM="1041;0;@">æ£å¸¸</TD> + <TD ALIGN=LEFT SDNUM="1041;0;@"><BR></TD> + <TD ALIGN=LEFT SDNUM="1041;0;@">ç‰¹è¨˜äº‹é …å‚ç…§</TD> + <TD ALIGN=LEFT><BR></TD> + <TD ALIGN=LEFT><BR></TD> + <TD ALIGN=LEFT>6以é™ã€ãƒ—ãƒã‚°ãƒ©ãƒ ãŒä¸è¦å‰‡ã«Seg fault.</TD> + </TR> + <TR> <TD HEIGHT=16 ALIGN=LEFT><FONT FACE="Liberation Sans">MobleGear 520</FONT></TD> <TD ALIGN=LEFT><FONT FACE="Liberation Sans">hpcmips</FONT></TD> <TD ALIGN=LEFT SDNUM="1041;0;@">未ç€æ‰‹</TD>
Add NetBSD 6.0_BETA amd64 AMIs, and tweak the wording and setup.
Index: wikisrc/amazon_ec2/amis.mdwn =================================================================== RCS file: /home/wiki/cvsroot/wikisrc/amazon_ec2/amis.mdwn,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- wikisrc/amazon_ec2/amis.mdwn 12 Feb 2012 16:08:44 -0000 1.7 +++ wikisrc/amazon_ec2/amis.mdwn 25 Feb 2012 18:16:43 -0000 1.8 @@ -2,11 +2,14 @@ The following AMIs are publicly available. You can use them to [[start a NetBSD instance|/amazon_ec2/netbsd_in_5_min/]] quickly. -They come with [src](http://www.netbsd.org/docs/guide/en/chap-fetch.html) and [pkgsrc](http://www.netbsd.org/docs/pkgsrc/) bundled under */usr/src/* and */usr/pkgsrc/* respectively, or a bootstrap script to help fetch them when necessary. +They come with [src](http://www.netbsd.org/docs/guide/en/chap-fetch.html) and [pkgsrc](http://www.netbsd.org/docs/pkgsrc/) bundled under */usr/src/* and */usr/pkgsrc/* respectively, or a bootstrap script to help fetch them when necessary. The bootstrap script can also be used to set up binary packages support using pkgin(1). -## amd64 (x86_64) -- 64 bits AMIs +Note: these AMIs send an email to the maintainer on first launch, to +help gauge usage. + +## amd64 (x86_64) -- 64 bit AMIs -The following AMIs are for 64 bits instances. +The following AMIs are for 64 bit instances. <table class="center"> <tr> @@ -30,21 +33,21 @@ <td>ami-4e7ea153</td> </tr> <tr> - <th>NetBSD-HEAD (5.99.45)</th> - <td></td> - <td></td> - <td></td> - <td></td> - <td></td> + <th>NetBSD 6.0_BETA</th> + <td>ami-56e4363f</td> + <td>ami-0ddf8648</td> + <td>ami-fc038ecc</td> + <td>ami-6f3c051b</td> + <td>ami-68a4e03a</td> + <td>ami-5e1bad5f</td> + <td>ami-1c6eb101</td> </tr> </table> -## i386 -- 32 bits AMIs +## i386 -- 32 bit AMIs The following AMIs are for 32-bit instances. -Note: these AMIs send an email to the maintainer on first launch, to -help gauge usage. <table class="center"> <tr> @@ -68,11 +71,13 @@ <td>ami-e4429df9</td> </tr> <tr> - <th>NetBSD-HEAD (5.99.64)</th> - <td></td> - <td></td> - <td></td> - <td></td> - <td></td> + <th>NetBSD 6.0_BETA</th> + <td>soon</td> + <td>soon</td> + <td>soon</td> + <td>soon</td> + <td>soon</td> + <td>soon</td> + <td>soon</td> </tr> </table>