[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: /about/ROADMAP



»ì‚Å‚·B
¡”N‚à‚æ‚낵‚­‚¨Šè‚¢‚µ‚Ü‚·B
¦Œg‘Ñ‚©‚ç‚È‚Ì‚Å“Ç‚Ý“ï‚©‚Á‚½‚ç‚·‚Ý‚Ü‚¹‚ñB
•ª—Ê‚ª‘½‚­‚Ä‘å•Ï‚Å‚·‚ËB‚¨”æ‚ê—l‚Å‚·BŽQl–ó‚ð’Ç‹L‚µ‚Ü‚µ‚½B‚²——‚­‚¾‚³ 
‚¢B

On 31 Dec 2009, at 23:21, ŽO—ÖW( Miwa Susumu ) <miwarin@gmail.com>  
wrote:

> ŽO—Ö‚Å‚·B
>
> ”N––‚Å‚·‚ªB
> –|–ó‚ðC³‚µ‚Ü‚µ‚½B
> (complete‚Æ‚©add‚È‚Ç‚¯‚Á‚±‚¤ŠÔˆá‚Á‚Ä‚¢‚½‚Ì‚Å)
> –|–ó‚̓[ƒ‹ÅŒã‚É‘‚«‚Ü‚µ‚½B
>
> ‚½‚¾A‚Ç‚¤‚µ‚Ä‚à•ª‚©‚ç‚È‚¢‰ÓŠ‚ª‚ ‚é‚Ì‚Å‹³‚¦‚Ä‚­‚¾‚³‚¢B
> ROADMAP‚Ì‘O‚Ì‚Ù‚¤‚É‚ ‚éˆÈ‰º‚Ì•¶Í‚È‚ñ‚Å‚·‚ª....
>
> This will hopefully avoid both duplication of effort and too many
> or too-extended stalls.
>
> ‚±‚±‚Å‚¢‚¤utoo many or too-extended stallsv‚Í
> ‚‚܂è’÷‚ß؂肪Žç‚ç‚ê‚È‚¢‚±‚Ƃɂ‚¢‚ÄG‚ê‚Ä‚¢‚é‚Ì‚Å‚µ‚傤‚©H

¦‚»‚¤‚Å‚·‚ËB‚±‚ñ‚ÈŠ´‚¶‚Å‚µ‚傤‚©B

‚±‚ê‚É‚æ‚èA‚¤‚Ü‚­s‚¯‚Γw—Í‚Ìd•¡‚ÆA“xX‚Ü‚½‚Í’·ŠúŠÔƒvƒƒWƒFƒNƒg‚ª’â‘Ø 
‚·‚邱‚Æ‚Ì—¼•û‚ð”ð‚¯‚é‚±‚Æ‚ª‚Å‚«‚é‚Å‚µ‚傤B

>>>>> ‚±‚±‚©‚ç
> #    %NetBSD: ROADMAP,v 1.23 2008/08/04 15:37:05 simonb Exp %
>
> A high-level roadmap for NetBSD
> NetBSD ‚ÌãˆÊŠT”Oƒ[ƒhƒ}ƒbƒv
>
>
> This file contains a general map of where we would like to take
> NetBSD over the next N years.  It is not highly detailed or overly
> specific about each item.  There are several different "TODO" files
> and "NetBSD Projects" lists in various places that contain some
> more detailed plans.  This is the framework in which those projects
> and plans are expected to fit.
> ‚±‚̃tƒ@ƒCƒ‹‚ÍŽŸ‚Ì N ”NŠÔ‚Å NetBSD ‚ð‚ǂ̂悤‚É‚µ‚½‚¢‚©‚Æ‚¢‚¤ƒ[ƒhƒ}ƒb 
> ƒv‚ðŠÜ‚ñ‚Å‚¢‚Ü‚·B

> ‚±‚̃[ƒhƒ}ƒbƒv‚ÌŠe€–Ú‚ÍA‚Ü‚Á‚½‚­Úׂɑ‚©‚ê‚Ä‚¢‚È‚¢‚©A‚Ü‚½‚Í‚ ‚Ü 
> ‚è‚Í‚Á‚«‚è‚Æ‘‚¢‚Ä‚¢‚Ü‚¹‚ñB

‚ ‚Ü‚èÚׂɑ‚©‚ê‚Ä‚¨‚炸A‚Ü‚½ŒÂ•Ê‚Ì€–Ú‚É‚Í[“ü‚肵‚Ä‚¢‚Ü‚¹‚ñB

> ‚¢‚­‚‚©‚̈قȂÁ‚½ "TODO" ƒtƒ@ƒCƒ‹‚Æ "NetBSDƒvƒƒWƒFƒNƒg" ‚̃ŠƒXƒg‚ª•Ê 
> ‚Ìꊂɂ ‚èA‚»‚ê‚ç‚É‚Í‚æ‚èÚׂȌv‰æ‚ªŠÜ‚Ü‚ê‚Ä‚¢‚Ü‚·B

> ‚±‚̃[ƒhƒ}ƒbƒv‚ÍA‚»‚ê‚ç‚̃vƒƒWƒFƒNƒg‚ÆŒv‰æ‚ɇ‚¤‚±‚Æ‚ªŠú‘Ò‚Å‚«‚éƒt 
> ƒŒ[ƒ€ƒ[ƒN‚Å‚·B

‚»‚ê‚ç‚̃vƒƒWƒFƒNƒg‚ÆŒv‰æ‚ÍA‚±‚̃[ƒhƒ}ƒbƒv‚̘g‘g‚݂ɉˆ‚Á‚ÄŽÀŽ{‚³‚ê‚é 
—\’è‚Å‚·B

¦‚©‚È‚èˆÓ–ó‚Å‚·‚ªcc

>
>
> As this is a volunteer project, there are no specific dates beside
> these items.  These items may or may not get picked up in any order,
> and the roadmap may change as technologies and perceived needs
> change.
> ‚±‚ê‚̓{ƒ‰ƒ“ƒeƒBƒAƒvƒƒWƒFƒNƒg‚È‚Ì‚ÅA‚±‚ê‚ç‚Ì€–Ú‚ÉŠú“ú‚Í‚ ‚è‚Ü‚¹‚ñB
> ‚±‚ê‚ç‚Ì€–ڂ͇•s“¯‚É’…Žè‚³‚ê‚é‚©‚à‚µ‚ê‚È‚¢‚µA’…Žè‚³‚ê‚È‚¢‚©‚à‚µ‚ê‚Ü 
> ‚¹‚ñB
> ‚»‚µ‚ÄA‹Zp‚ƃj[ƒY‚̕ω»‚ɉž‚¶‚ÄAƒ[ƒhƒ}ƒbƒv‚͕ω»‚·‚é‚©‚à‚µ‚ê‚Ü‚¹ 
> ‚ñB
>
>
> The roadmap, of course, is constructed in the context of the
> Project's (broad) goals:
> ‚à‚¿‚ë‚ñƒ[ƒhƒ}ƒbƒv‚Í NetBSD ƒvƒƒWƒFƒNƒg‚Ì•L‚¢–Ú•W‚É‚ ‚킹‚Ä\¬‚³ 
> ‚ê‚Ü‚·:
>
>   * clean design        * stable        * fast
>   * ‚«‚ê‚¢‚ÈÝŒv        * Œ˜˜S«        * ‘¬‚³
>   * clean licensing    * portable        * interoperable
>   * ‚«‚ê‚¢‚ȃ‰ƒCƒZƒ“ƒX    * ˆÚA«        * ‰^—p«

‘ŠŒÝ‰^—p«‚ª—Ç‚¢‚Å‚·B

>   * conformant        * commercial-ready    * research-ready
>   * “K‡«        * ¤—p‚Å‚Ì—˜—p    * Œ¤‹†‚Å‚Ì—˜—p
>   * hobby-ready
>   * Žï–¡‚Å‚Ì—˜—p
>
> In general, we are headed for:
> ˆê”Ê“I‚ÉAŽ„‚½‚¿‚̃S[ƒ‹‚͈ȉº‚̂悤‚È‚à‚Ì‚Å‚·B
>   * "State of the art" tools (current (and stable) GNU tools,
>     addition of Solaris's dtrace or similar functionality, kernel
>     core dumps on all platforms and post-mortem analysis tools,
>     performance analysis tools with support for hardware assists
>     like PMCs)
>   * Å‚…€‚̃c[ƒ‹ (current‚Ì (‚»‚µ‚Ästable‚Ì) GNUƒc[ƒ‹ASolaris  
> ‚Ì dtrace
> ‚Ü‚½‚Í“¯’ö“x‚Ì‹@”\«‚̒ljÁA‚·‚ׂẴvƒ‰ƒbƒgƒtƒH[ƒ€‚̃J[ƒlƒ‹ƒRƒAƒ_ƒ“ 
> ƒv‚ÆŽ–Œã•ªÍƒc[ƒ‹APMC
> ‚̂悤‚Ƀn[ƒhƒEƒFƒA‚ð—p‚¢‚½ƒpƒtƒH[ƒ}ƒ“ƒX•ªÍƒc[ƒ‹)
>
>   * Support for all devices without encumbered code
>   * Œ —˜‚‚«ƒR[ƒh–³‚µ‚É‚·‚ׂẴfƒoƒCƒX‚̃Tƒ|[ƒg‚·‚邱‚Æ
>
>   * Managed growth of the base system
>   * Šî–{ƒVƒXƒeƒ€‚̬’·ŠÇ—
>
>   * Minimal GPL / LGPL code in the base system
>   * Šî–{ƒVƒXƒeƒ€‚ÌŬ—Ê‚ÌGPL / LGPLƒR[ƒh
>
>   * Maximal performance without compromising portability
>   * ˆÚA«‚𑹂Ȃ¤‚±‚Æ‚Ì‚È‚¢Å‚«”\
>
>   * "State of the art" technology in the kernel and userland
>   * Å‚…€‚̃J[ƒlƒ‹‚ƃ†[ƒU[ƒ‰ƒ“ƒh
>
>   * No bugs, no security vulnerabilities
>   * ƒoƒO‚È‚µAƒZƒLƒ…ƒŠƒeƒBÆŽã«‚È‚µ
>
>   * In combination with pkgsrc, a complete system for a variety
>     of users, administrators, and researchers: desktops, embedded
>     devices, servers, workstations, and portables
>   * pkgsrc (—lX‚ȃ†[ƒU[AŠÇ—ŽÒAŒ¤‹†ŽÒ‚Ì‚½‚ß‚ÌŠ®‘S‚ȃVƒXƒeƒ€) ‚ÆŒ‹ 
> ‡‚µ‚Ä: ƒfƒXƒNƒgƒbƒvA‘gžƒfƒoƒCƒXAƒT[ƒo[Aƒ[ƒNƒXƒe[ƒVƒ‡ƒ“Aƒ|[ 
> ƒ^ƒuƒ‹

  * pkgsrc‚Æ‘g‚݇‚킹‚ÄA—lX‚ȃ†[ƒU[AŠÇ—ŽÒAŒ¤‹†ŽÒ‚Ì‚½‚ß‚ÌŠ®‘S‚ȃV 
ƒXƒeƒ€: ƒfƒXƒNƒgƒbƒvA‘g‚Ýž‚݃fƒoƒCƒXAƒT[ƒo[Aƒ[ƒNƒXƒe[ƒVƒ‡ƒ“A 
ƒ|[ƒ^ƒuƒ‹‹@Ší

>
>
> This is, by no means, a comprehensive list, and purposefully  
> aggressive.
> One of the many challenges will be to achieve excellence in each arena
> we tackle and not settle for being a "jack of all trades, master of  
> none."
> ‚±‚̃ŠƒXƒg‚͕“I‚Å‚à‚È‚­AÏ‹É“I‚ÉŽæ‚è‘g‚Þ‚±‚Æ‚ðˆÓ–¡‚·‚é‚킯‚Å‚à‚ ‚è 
> ‚Ü‚¹‚ñB

‚±‚̃ŠƒXƒg‚Í‘S‚­‚à‚Á‚ĕ“I‚Å‚Í‚È‚­A‚Ü‚½ˆÓ}‚µ‚Ä–ìS“I‚É‚È‚Á‚Ä‚¢‚Ü‚·B

> ‚±‚ê‚ç‚̃S[ƒ‹‚Ì‚¤‚¿ 1
> ‚‚ÍA‰äX‚ªŽæ‚è‘g‚ÞŠeX‚Ì•ª–ì‚Å—D‚ꂽ‚à‚Ì‚ðì‚邱‚Æ‚Å‚ ‚èAuŠí—p•n 
> –Rv‚ɂȂ肽‚¢‚킯‚Å‚Í‚ ‚è‚Ü‚¹‚ñB
>
>
> The following, more specific, items are divided into rough categories:
>   1. Platform independent kernel
>   2. Platform independent userland
>   3. Platform dependent kernel
>   4. Platform dependent userland
>   5. Other
> Œãq‚·‚é‹ï‘Ì“I‚È€–Ú‚ÍA‚¨‚¨‚´‚Á‚ςȃJƒeƒSƒŠ[‚É•ª‚¯‚ç‚ê‚Ü‚·:
>   1. ƒvƒ‰ƒbƒgƒtƒH[ƒ€‚©‚ç“Æ—§‚µ‚½ƒJ[ƒlƒ‹
>   2. ƒvƒ‰ƒbƒgƒtƒH[ƒ€‚©‚ç“Æ—§‚µ‚½ƒ†[ƒU[ƒ‰ƒ“ƒh
>   3. ƒvƒ‰ƒbƒgƒtƒH[ƒ€‚Ɉˑ¶‚·‚éƒJ[ƒlƒ‹
>   4. ƒvƒ‰ƒbƒgƒtƒH[ƒ€‚Ɉˑ¶‚·‚郆[ƒU[ƒ‰ƒ“ƒh
>   5. ‚»‚Ì‘¼
>
> If you'd like to take on a project, please record your name/email,
> the date that you're claiming a project (or part of a project--if
> a part, please specify the part), and an expected completion date.
> This will hopefully avoid both duplication of effort and too many
> or too-extended stalls.
>
> ‚ ‚È‚½‚ªƒvƒƒWƒFƒNƒg‚ðˆø‚«Žó‚¯‚½‚¢‚ÆŽv‚¤‚È‚ç‚ÎA‚ ‚È‚½‚Ì–¼‘O/“dŽqƒ[ 
> ƒ‹ (‚ ‚È‚½‚ªŽå’£‚µ‚Ä‚¢‚éƒvƒƒWƒFƒNƒg
> (ƒvƒƒWƒFƒNƒg‚̈ꕔ•”•ª‚È‚ç‚ÎA‚»‚Ì•”•ª‚ðŽw’肵‚Ä‚­‚¾‚³‚¢)
> ‚ÆŠú‘Ò‚³‚ê‚銮¬“ú‚ð‹Lq‚µ‚Ä‚­‚¾‚³‚¢B‚±‚ê‚Íd•¡‚µ‚½ì‹Æ‚ÆA‚æ‚­‚ ‚鉄 
> Šú‚Ì‚½‚߂̌떂‰»‚µ‚ð”ð‚¯‚é‚½‚ß‚Å‚·B
>
>
> PLEASE NOTE THAT THIS IS A VOLUNTEER PROJECT, AND THAT NONE OF THESE
> RELEASE VERSIONS, OR NAMES, IS A GUARANTEE OF THE FUNCTIONALITY BEING
> COMPLETE OR EVEN STARTED.  INTERESTED PARTIES SHOULD CONTACT
>
>       core@NetBSD.org
>
> ‚±‚ꂪƒ{ƒ‰ƒ“ƒeƒBƒAƒvƒƒWƒFƒNƒg‚Å‚ ‚èA‚ǂ̃ŠƒŠ[ƒXƒo[ƒWƒ‡ƒ“ (‚Ü‚½‚Í–¼ 
> ‘O)
> ‚àŠ®—¹‚µ‚½‚©A‚Ü‚½‚Í’…Žè‚³‚ꂽ‚±‚Æ‚ð•ÛØ‚µ‚Ä‚¢‚é‚킯‚Å‚Í‚È‚¢‚±‚Æ‚É’ˆÓ 
> ‚µ‚Ä‚­‚¾‚³‚¢B‹»–¡‚ª‚ ‚é•û‚͈ȉº‚ɘA—‚µ‚Ä‚­‚¾‚³‚¢B
>
>       core@NetBSD.org
>
>
> FOR MORE INFORMATION.
> ÚׂÈî•ñB
>
> 1. Platform independent kernel
> 1. ƒvƒ‰ƒbƒgƒtƒH[ƒ€‚©‚ç“Æ—§‚µ‚½ƒJ[ƒlƒ‹
> ==============================
> aa. Scheduler works
>   Separation of context switching and thread scheduling.
>   Responsible: yamt
>   ETA: 5.0 (yamt-idlelwp branch)
>   Generic scheduler API for modular implementations.
>   Responsible: dsieger
>   ETA: 5.0 (merged in yamt-idlelwp branch)
>   New scheduler supporting POSIX Real-time features, CPU affinity and
>   having a better support for MP systems.
>   Responsible: rmind
>   ETA: 5.0
> aa. ƒXƒPƒWƒ…[ƒ‰‹@”\
>   ƒRƒ“ƒeƒLƒXƒgƒXƒCƒbƒ`‚Ì•ª—£‚ƃXƒŒƒbƒh‚̃XƒPƒWƒ…[ƒŠƒ“ƒOB
>   Ó”CŽÒ: yamt
>   ETA: 5.0 (yamt-idlelwp ƒuƒ‰ƒ“ƒ`)
>   ƒ‚ƒWƒ…[ƒ‹ŽÀ‘•‚Ì‚½‚߂̔ėpƒXƒPƒWƒ…[ƒ‰ APIB
>   Ó”CŽÒ: dsieger
>   ETA: 5.0 (yamt-idlelwp ƒuƒ‰ƒ“ƒ`‚Ƀ}[ƒW)
>   V‚µ‚¢ƒXƒPƒWƒ…[ƒ‰ (POSIX ƒŠƒAƒ‹ƒ^ƒCƒ€‹@”\‚ÆACPU e˜a«‚ÆAMP ƒVƒXƒe 
> ƒ€‚Ì‚½‚ß‚Ì‚æ‚è—Ç‚¢ƒTƒ|[ƒg)
>   Ó”CŽÒ: rmind
>   ETA: 5.0
>
> ab. Reduction of the giant lock
>   There are several proposals for the best way forward on this, but
>   we really need a couple of people with time to step forward and
>   lead us here.
>   Responsible: ad
>   ETA: 5.0 (vmlocking2 branch)
> ab. ƒWƒƒƒCƒAƒ“ƒgƒƒbƒN‚Ì팸
>   ‚±‚Ì‚½‚ß‚ÌÅ‘P‚Ì•û–@‚ª‚¢‚­‚‚©’ñˆÄ‚³‚ê‚Ä‚¢‚Ü‚·B‚킸‚©‚Èl”‚Å‚à‘Oi 
> ‚µA‚±‚̃S[ƒ‹‚Ö‚½‚Ç‚è’…‚­‚±‚Æ‚ð•K—v‚Æ‚µ‚Ä‚¢‚Ü‚·B
>   Ó”CŽÒ: ad
>   aETA: 5.0 (vmlocking2 ƒuƒ‰ƒ“ƒ`)
>
>
> ac. Expansion of wedge support
>   Complete the development of wedges and retire disklabels except
>   where needed for compatibility.
>   Responsible: thorpej (possibly)
>   ETA: 5.0
> ac. wedge ƒTƒ|[ƒg‚ÌŠg‘å
>   wedge ‚ÌŠJ”­‚ðŠ®—¹‚³‚¹‚Ä‚­‚¾‚³‚¢B‚»‚µ‚ÄAŒÝŠ·«‚É•K—v‚ª‚ ‚é‚̂𜂢 
> ‚Ä disklabels ‚ðˆø‘Þ‚³‚¹‚Ä‚­‚¾‚³‚¢B
>   Ó”CŽÒ: thorpej (‚¨‚»‚ç‚­)
>   ETA: 5.0
>
>
> ad. Volume management
>   Allow us to grow, shrink, and move partitions (and, where possible,
>   filesystems).
>   Responsible: TBD
>   ETA: ?
> ad. ƒ{ƒŠƒ…[ƒ€ŠÇ—
>   ƒp[ƒeƒBƒVƒ‡ƒ“‚ðŠg’£Ak¬AˆÚ“®‚Å‚«‚é‚悤‚É‚µ‚Ä‚­‚¾‚³‚¢ (‰Â”\‚ÈŒÀ‚è 
> ƒtƒ@ƒCƒ‹ƒVƒXƒeƒ€‚ª‚¨‚±‚È‚¤‚Ì‚ª‚¢‚¢‚Å‚µ‚傤)
>   Ó”CŽÒ: TBD
>   ETA: ?

¦ˆÈ‰ºAƒe[ƒ}‚ÌŒ´•¶‚Í–½—ߌ`‚Å‚·‚ªA“ú–{Œã‚Ìꇂ͕’Ê‚Ì‘ÌŒ¾Ž~‚ß(`‚·‚邱 
‚Æ)‚ªŽ©‘R‚©‚à‚µ‚ê‚Ü‚¹‚ñB

(‰Â”\‚Å‚ ‚ê‚ÎAƒtƒ@ƒCƒ‹ƒVƒXƒeƒ€‚ɂ‚¢‚Ä‚à“¯—l‚É)

  Ó”CŽÒ: –¢’è

>
>
> ae. High-performance, maybe log-based, journalled fs w/ snapshot  
> support
>   Addition of logs, journals, and snapshots to FFS is a lot, another
>   filesystem could be cleaner and faster.
>   Responsible: simonb
>   ETA: 5.0 (journaling + snapshots don't work together yet though)
> ae. ƒXƒiƒbƒvƒTƒ|[ƒg‚ª‚ ‚é‚«”\‚ÌA‚»‚µ‚ÄA‚½‚Ô‚ñƒƒOƒx[ƒX‚̃Wƒƒ[ƒi 
> ƒ‹ƒtƒ@ƒCƒ‹ƒVƒXƒeƒ€
>   FFS ‚ւ̒ljÁ‚·‚郃O‹@”\AƒWƒƒ[ƒiƒŠƒ“ƒO‹@”\AƒXƒiƒbƒvƒVƒ‡ƒbƒg‹@”\‚Í 
> ‚½‚­‚³‚ñ‚ ‚è‚Ü‚·B•Ê‚̃tƒ@ƒCƒ‹ƒVƒXƒeƒ€‚Å‚Í‚à‚Á‚ÆãY—í‚Å‘¬‚¢‚©‚à‚µ‚ê‚Ü‚¹ 
> ‚ñB

FFS‚ɃƒOAƒWƒƒ[ƒiƒ‹AƒXƒiƒbƒvƒVƒ‡ƒbƒg‹@”\‚ð’ljÁ‚·‚é‚͈̂ê‘厖‚Å‚·B‚¨‚» 
‚ç‚­•Ê‚̃tƒ@ƒCƒ‹ƒVƒXƒeƒ€‚È‚ç‚æ‚èãY—í‚Å‘¬‚¢‚Å‚µ‚傤B

>   Ó”CŽÒ: simonb
>   ETA: 5.0 (‚à‚Á‚Æ‚àAƒWƒƒ[ƒiƒŠƒ“ƒO‚ƃXƒiƒbƒv‚Ì‘g‚݇‚킹‚ÍA‚Ü‚¾“¯Žž 
> ‚É‹@”\‚µ‚Ä‚¢‚Ü‚¹‚ñ)
>
>
> af. Expansion of ieee1394 support
>   Where possible, fully support DV, disk, and network devices.
>   Responsible: TBD
>   ETA: Preliminary firewire support is in 4.0
> af. ieee1394ƒTƒ|[ƒg‚ÌŠg’£
>   ‰Â”\‚ÈŒÀ‚è DVAƒfƒBƒXƒNAƒlƒbƒgƒ[ƒNƒfƒoƒCƒX‚ðƒTƒ|[ƒg‚µ‚Ü‚·B
>   Ó”CŽÒ: TBD
>   ETA: 4.0 ‚Å‚Í Preliminary FireWire ‚ðƒTƒ|[ƒg‚µ‚Ä‚¢‚Ü‚·B

ETA: 4.0‚Å‚ÍFireWireƒTƒ|[ƒg‚Ì€”õ‚ª‚³‚ê‚Ä‚¢‚Ü‚·B

>
> ag. Generic device hotplug support
>   Support hotplug of all devices and busses that support it.  This
>   should be divided into subcategories and does cross over some into
>   platform-dependent areas.  SATA, SCSI, FC, USB, Firewire,
>   PCI (PCI-X, and PCI-Express), etc.  There is some rudimentary
>   support present, but it is far from comprehensive.
>   Responsible: bouyer
>   ETA: ?
> ag. ”Ä—pƒfƒoƒCƒX hotplug ƒTƒ|[ƒg
>   ‚·‚ׂẴfƒoƒCƒX‚Æ‚»‚̃oƒX‚Ì hotplug ‚ðƒTƒ|[ƒg‚µ‚Ä‚¢‚Ü‚·B
>   ‚±‚ê‚ÍAƒTƒuƒJƒeƒSƒŠ‚É•ªŠ„‚³‚ê‚é‚ׂ«‚Å‚ ‚èA‚¢‚­‚‚©‚̃vƒ‰ƒbƒgƒtƒH[ 
> ƒ€‚Ɉˑ¶‚·‚é—̈æ‚ð’´‚¦‚Ü‚¹‚ñB
>   SATAASCSIAFCAUSBAFireWireAPCI (PCI X ‚Æ PCI-Express)

‚±‚ê‚̓TƒuƒJƒeƒSƒŠ[‚É•ªŠ„‚³‚ê‚é‚ׂ«‚Å‚ ‚èASATAASCSIAFCAUSBA 
FireWireA PCI (PCI X ‚Æ PCI-Express)‚È‚Ç‚ÌꇂÍAƒvƒ‰ƒbƒgƒtƒH[ƒ€‚Ɉˑ¶ 
‚·‚é—̈æ‚É‚Ü‚½‚ª‚è‚Ü‚·B
‚¢‚­‚‚©‚Ì`

> ‚È‚ÇA‚¢‚­‚‚©‚̉•à“I‚ȃTƒ|[ƒg‚ª‚ ‚è‚Ü‚·‚ªA‚»‚ê‚Í‘S‚­•ïŠ‡“I‚Å‚Í‚ ‚è 
> ‚Ü‚¹‚ñB
>
>   Ó”CŽÒ: bouyer
>   ETA: ?
>
> ah. Suspend and resume support
>   We should be able to fully use suspend and resume on PCs, macppc,
>   and anyone else who supports it in hardware (sparc, hpcsh, hpcarm,  
> etc).
>   Responsible: jmcneill, joerg
>   ETA: 5.0
> ah. ƒTƒXƒyƒ“ƒh‚ƃŠƒWƒ…[ƒ€ƒTƒ|[ƒg
>   PCAMacPPCA‚»‚µ‚ăTƒXƒyƒ“ƒh‚ƃŠƒWƒ…[ƒ€‚ðƒTƒ|[ƒg‚µ‚Ä‚¢‚éƒn[ƒhƒEƒF 
> ƒA (sparcAhpcshAhpcarm‚È‚Ç) ‚È‚ç‚Ί®‘S‚ÉŽg—p‚Å‚«‚é‚Í‚¸‚Å‚·B
>   Ó”CŽÒ: jmcneillAjoerg
>   ETA: 5.0
>
> ai. Complete support for LWPs
>   There are still vestiges of the kernel that predate LWPification
>   and should be updated.  [ What other than ktrace? ]
>   Responsible: darrenr, skrll, christos did ktrace-lwp
>   ETA: 4.0
> ai. LWP ƒTƒ|[ƒg‚ðŠ®—¹‚³‚¹‚Ä‚­‚¾‚³‚¢
>   LWPification ‚Ì‚±‚ë‚Ì–¼Žc‚肪‚Ü‚¾ƒJ[ƒlƒ‹‚É‚ ‚é‚Ì‚ÅAƒAƒbƒvƒf[ƒg‚·‚× 
> ‚«‚Å‚·(ktrace ˆÈŠO?)

LWP‰»ˆÈ‘O‚̃R[ƒh‚Ì–¼Žc‚ª‚Ü‚¾ƒJ[ƒlƒ‹‚ÉŽc‚Á‚Ä‚¨‚èA‚±‚ê‚̓Aƒbƒvƒf[ƒg‚·‚× 
‚«‚Å‚·B(ktraceˆÈŠO‰½‚ª‚ ‚é?)

>   Ó”CŽÒ: darrenrAskrllAchristos ‚Í ktrace-lwp ‚ð‚µ‚Ü‚µ‚½B
>   ETA: 4.0
>
> aj. PTHREAD_CONCURRENCY > 1 support
>   A single process that uses threads should be able to reliably
>   use more than one CPU.
>   Responsible: ad
>   ETA: 5.0  (1:1 pthread come with newlock2)
> aj. PTHREAD_CONCURRENCY > 1 ƒTƒ|[ƒg
>   1 ƒvƒƒZƒX‚ªŠmŽÀ‚É 1 ‚ˆÈã‚Ì CPU ‚ðŽg—p‚Å‚«‚é‚悤‚É‚·‚é•K—v‚ª‚ ‚è‚Ü 
> ‚·B
>   Ó”CŽÒ: ad
>   ETA: 5.0 (1:1 pthread‚É‚ÍAnewlock2 ‚͂‚¢‚Ä—ˆ‚Ü‚·)
>
>
> ak. AIO support
>   POSIX aio_*() with full support for Asynchronous I/O (AIO) in the
>   kernel.
>   Responsible: rmind
>   ETA: 5.0
> ak. AIO ƒTƒ|[ƒg
>   POSIX aio_*() ‚É‚æ‚éƒJ[ƒlƒ‹‚Å‚ÌŠ®‘S‚È”ñ“¯Šú I/O (AIO) ƒTƒ|[ƒg
>   Ó”CŽÒ: rmind
>   ETA: 5.0
>
>
> al. Modern parallel port support
>   Complete support for bidirectional and "advanced" functionality
>   from parallel ports.
>   Responsible: jdolecek
>   ETA: ?
> al. ƒ‚ƒ_ƒ“‚ȃpƒ‰ƒŒƒ‹ƒ|[ƒgƒTƒ|[ƒg
>   ‘o•ûŒüƒpƒ‰ƒŒƒ‹ƒ|[ƒg‚ÆAX‚È‚éƒpƒ‰ƒŒƒ‹ƒ|[ƒg‚̃Tƒ|[ƒg‚ðŠ®—¹‚³‚¹‚Ä‚­ 
> ‚¾‚³‚¢B
>   Ó”CŽÒ: jdolecek
>   ETA: ?
>
>
> am. NFSv4
>   Bring our NFS up to current standards.
>   Responsible: TBD
>   ETA: ?
> am. NFSv4
>   Œ»Ý‚Ì NFS ‚̊܂Åã‚°‚Ä‚­‚¾‚³‚¢B
>   Ó”CŽÒ: TBD
>   ETA: ?
>
> an. Update the locking mechanisms in the kernel
>   This requires some platform support.  A good bit of work is on the
>   now-archaic "newlock" branch, from thorpej.  It requires some
>   overhaul of cpu_switch/scheduler so that mutex_*(9) and ltsleep(9)
>   can interlock.
>   Responsible: ad
>   ETA: 5.0  (newlock2)
> an. ƒJ[ƒlƒ‹‚̃ƒbƒN‹@\‚ðƒAƒbƒvƒf[ƒg‚µ‚Ä‚­‚¾‚³‚¢
>   ‚±‚ê‚Í‚¢‚­‚‚©‚̃vƒ‰ƒbƒgƒtƒH[ƒ€ƒTƒ|[ƒg‚ð•K—v‚Æ‚µ‚Ü‚·B
>   thorpej ‚É‚æ‚é "newlock" ƒuƒ‰ƒ“ƒ`‚Å‚¸‚Á‚Æì‹Æ‚µ‚Ä‚¢‚Ü‚·B

thorpel‚É‚æ‚é¡‚âŒÃ‚ß‚©‚µ‚¢newlockƒuƒ‰ƒ“ƒ`‚É—Ç‚¢ì‹ÆŒ‹‰Ê‚ª‚ ‚è‚Ü‚·B
‚±‚ê‚Í`

>   mutex_*(9) ‚Æ ltsleep(9) ‚ª˜A“®‚·‚邽‚ß‚É cpu_switch/scheduler ‚̃I[ 
> ƒo[ƒz[ƒ‹‚ª‚¢‚­‚‚©•K—v‚Å‚·B
>   Ó”CŽÒ: ad
>   ETA: 5.0 (newlock2)
>
>
> ao. Review TCP/IP developments
>   Fix NewReno
>   Responsible: mycroft
>   ETA: 3.0
>   Add SACK support to the kernel.
>   Responsible: kurahone
>   ETA: 3.0
>   Add ECN support to the kernel.
>   Responsible: rpaulo
>   ETA: 5.0
>   Look into other "recent" and current TCP/IP research. Adapt our  
> stack
>   to the more modern world.
>   Responsible: TBD
>   ETA: ?
> ao. TCP/IP ŠJ”­‚̃Œƒrƒ…[
>   NewReno ‚ðƒtƒBƒbƒNƒX‚µ‚Ä‚­‚¾‚³‚¢B
>   Ó”CŽÒ: mycroft
>   ETA: 3.0
>   SACK ƒTƒ|[ƒg‚ðƒJ[ƒlƒ‹‚ɒljÁ‚µ‚Ä‚­‚¾‚³‚¢B
>   Ó”CŽÒ: kurahone
>   ETA: 3.0
>   ECN ƒTƒ|[ƒg‚ðƒJ[ƒlƒ‹‚ɒljÁ‚µ‚Ä‚­‚¾‚³‚¢B
>   Ó”CŽÒ: rpaulo
>   ETA: 5.0
>   ‚»‚Ì‘¼‚Ì "recent" ‚âÅV‚Ì TCP/IP ‚ɂ‚¢‚Ä‚ÌŒ¤‹†‚𒲂ׂĂ­‚¾‚³‚¢B  
> TCP/IP ƒXƒ^ƒbƒN‚ð‹ß‘ã“I‚ÈŽÀ‘•‚É‘‚«Š·‚¦‚Ä‚­‚¾‚³‚¢B
>   Ó”CŽÒ: TBD
>   ETA: ?
>
> ap. Kernel linker (ala FreeBSD's kld)
>   Responsible: TBD
>   ETA: ?
> ap. ƒJ[ƒlƒ‹ƒŠƒ“ƒJ (FreeBSD —R—ˆ‚Ì kld)
>   Ó”CŽÒ: TBD
>   ETA: ?
>
>
> aq. CARP/VRRP
>   Functionality is great, but there might be some concern here over
>   Cisco patents.
>   Responsible: liamfoy
>   ETA: 4.0
> aq. CARP/VRRP
>   ‹@”\‚Í‘f°‚炵‚¢‚Å‚·‚ªAƒVƒXƒR‚Ì“Á‹–‚É‚æ‚錜”O‚ª‚¢‚­‚‚©‚ ‚è‚Ü‚·B
>   Ó”CŽÒ: liamfoy
>   ETA: 4.0
>
> ar. UDF filesystem support
>   OpenBSD has recently added this.
>   Responsible: reinoud
>   ETA: 4.0
> ar. UDF ƒtƒ@ƒCƒ‹ƒVƒXƒeƒ€ƒTƒ|[ƒg
>   Å‹ß OpenBSD ‚ª‘Ήž‚µ‚Ü‚µ‚½B
>   Ó”CŽÒ: reinoud
>   ETA: 4.0
>
>
> as. RAIDFrame support for 3-way RAID 1
>   Responsible: TBD
>   ETA: ?
> as. 3-way RAID 1 ‚Ì‚½‚ß‚Ì RAIDFrame
>   Ó”CŽÒ: TBD
>   ETA: ?
>
>
> at. RAIDFrame support for RAID 6
>   Responsible: oster
>   ETA: 5.0?
> at. RAID6 ‚Ì‚½‚ß‚Ì RAIDFrame ƒTƒ|[ƒg
>   Ó”CŽÒ: oster
>   ETA: 5.0?
>
>
> au. More modern drivers
>   We lack support for a number of more modern devices (PCI-Express,
>   RAID cards, etc.) that are supported on other open source OSes.
>   Responsible: TBD
>   ETA: ?
> au. ‚à‚Á‚Æ‘½‚­‚̃‚ƒ_ƒ“‚ȃhƒ‰ƒCƒo[
>   ‘½‚­‚Ì‘¼‚̃I[ƒvƒ“ƒ\[ƒX OS ‚ŃTƒ|[ƒg‚³‚ê‚Ä‚¢‚郂ƒ_ƒ“‚ȃfƒoƒCƒX  
> (PCI-ExpressARAIDƒJ[ƒh‚È‚Ç) ‚ªƒTƒ|[ƒg‚³‚ê‚Ä‚¢‚Ü‚¹‚ñB
>   Ó”CŽÒ: TBD
>   ETA: ?
>
>
> av. iSCSI initiator support
>   We should be able to use iSCSI volumes.
>   Responsible: agc
>   ETA: 5.0
> av. iSCSI ƒCƒjƒVƒG[ƒ^[ƒTƒ|[ƒg
>   iSCSI ƒ{ƒŠƒ…[ƒ€‚ðŽg—p‚Å‚«‚é‚Í‚¸‚Å‚·B

`Žg—p‚Å‚«‚é‚ׂ«‚Å‚·B
¦‘¼‚É‚àŠY“–•”•ª‚ª‰½‰ÓŠ‚©‚ ‚è‚Ü‚·B

>   Ó”CŽÒ: agc
>   ETA: 5.0
>
>
> aw. Run-time changeable limits to SysV IPC
>   Some of the limits for SysV IPC are hardcoded in the kernel
>   configuration--these should be changable via sysctl.
>   Responsible: rmind
>   ETA: 4.0
> aw. ŽÀsŽž‚É SysV IPC ‚ÌÝ’è’l‚ð•ÏX‚·‚é
>   SysV IPC ‚Ì‚¢‚­‚‚©‚ÌÝ’è’l‚ªƒJ[ƒlƒ‹ƒRƒ“ƒtƒBƒMƒ…ƒŒ[ƒVƒ‡ƒ“‚Ńn[ƒh 
> ƒR[ƒh‚³‚ê‚Ä‚¢‚Ü‚·B„Ÿ‚±‚ê‚ç‚Ísysctl‚Å•ÏX‰Â”\‚È‚Í‚¸‚Å‚·B
>   Ó”CŽÒ: rmind
>   ETA: 4.0
>
>
> ax. NUMA support
>   To achieve this goal, the CPU scheduler should be modified to take  
> into
>   account the distances and grouping of CPUs.  Also, support of memory
>   blocks should be implemented in the VM subsystem.
>   Responsible: TBD
>   ETA: ?
> ax. NUMA ƒTƒ|[ƒg
>   ‚±‚Ì–Ú•W‚ð’B¬‚·‚é‚È‚çACPU ƒXƒPƒWƒ…[ƒ‰‚ÍACPU ‚Ì‹——£‚ƃOƒ‹[ƒsƒ“ƒO 
> ‚ðl—¶‚É“ü‚ê‚é‚悤‚É•ÏX‚³‚ê‚é‚ׂ«‚Å‚·B
>   ‚Ü‚½Aƒƒ‚ƒŠƒuƒƒbƒN‚̃Tƒ|[ƒg‚Í VM ƒTƒuƒVƒXƒeƒ€‚ÅŽÀ‘•‚³‚ê‚é‚ׂ«‚Å 
> ‚·B
>   Ó”CŽÒ: TBD
>   ETA: ?
>
>
> 2. Platform independent userland
> 2. ƒvƒ‰ƒbƒgƒtƒH[ƒ€‚©‚ç“Æ—§‚µ‚½ƒ†[ƒU[ƒ‰ƒ“ƒh
> ================================
> aa. Keep up with the X world
>   Track X.org progress.  Maintain existing XFree86.
>   Responsible: a cast of thousands
>   ETA: ongoing
> aa. X ‚Ì•ÛŽ
>   X.org ‚Ìi’»‚É’Ç]‚µ‚Ä‚­‚¾‚³‚¢BŠù‘¶‚Ì XFree86 ‚ðˆÛŽ‚µ‚Ä‚­‚¾‚³‚¢B
>   Ó”CŽÒ: ”çl‚̃LƒƒƒXƒg
>   ETA: is’†
>
> ab. Reentrant libraries
>   Make sure that all libraries are re-entrant and usable for threaded
>   applications.
>   Responsible: ginsbach and others
>   ETA: 5.0?
> ab. ƒŠƒGƒ“ƒgƒ‰ƒ“ƒgƒ‰ƒCƒuƒ‰ƒŠ
>   ƒXƒŒƒbƒh‰»‚³‚ꂽƒAƒvƒŠƒP[ƒVƒ‡ƒ“‚É‚·‚ׂẴ‰ƒCƒuƒ‰ƒŠ‚ªŠmŽÀ‚ɃŠƒGƒ“ƒg 
> ƒ‰ƒ“ƒg‚Å‚«‚é‚悤‚É‚µ‚Ä‚­‚¾‚³‚¢B

ƒXƒŒƒbƒh‰»‚³‚ꂽƒAƒvƒŠƒP[ƒVƒ‡ƒ“‚ÅŽg‚¦‚é‚悤‚ÉA‘S‚Ẵ‰ƒCƒuƒ‰ƒŠ[‚ªŠmŽÀ 
‚ɃŠƒGƒ“ƒgƒ‰ƒ“ƒg‚Å‚ ‚é‚悤‚É‚µ‚Ä‚­‚¾‚³‚¢B

>   Ó”CŽÒ: ginsbach ‘¼
>   ETA: 5.0?
>
>
> ac. gcc updates
>   This requires some work to rework the gcc4 builds to work with BSD
>   make(1) or update BSD make(1) or consider the unthinkable.
>   Responsible: mrg, matt
>   ETA: 4.0
> ac. gcc ƒAƒbƒvƒf[ƒg
>   gcc4 ‚ð BSD make(1) ‚Å“®ì‚·‚é‚悤‚É‚·‚é‚©ABSD make(1) ‚ðƒAƒbƒvƒf[ 
> ƒg‚·‚é‚©A‚Ü‚½‚Í‘z‘œ‚ðâ‚·‚éì‹Æ‚ª•K—v‚Å‚·B
>   Ó”CŽÒ: mrg, matt
>   ETA: 4.0
>
>
> ad. gdb updates
>   Responsible: skrll
>   ETA: 5.0
> ad. gdb ƒAƒbƒvƒf[ƒg
>   Ó”CŽÒ: skrll
>   ETA: 5.0
>
>
> ae. binutils updates
>   Probably go along with gdb updates.
>   Responsible: skrll
>   ETA: 4.0
> ae. binutils ƒAƒbƒvƒf[ƒg
>   ‚¨‚»‚ç‚­ gdb ƒAƒbƒvƒf[ƒg‚Æ‹¦—Í‚µ‚Äì‹Æ‚µ‚Ü‚·B
>   Ó”CŽÒ: skrll
>   ETA: 4.0
>
>
> af. Better post-mortem debugging tools
>   It would be useful to have something between ps/*stat/etc. and
>   gdb with a core file.  Something, perhaps, like SysV(?) crash(8).
>   Responsible: TBD
>   ETA: ?
> af. ‚æ‚è—Ç‚¢ŒŸŽ€—pƒfƒoƒbƒOƒc[ƒ‹
>   ps, *stat, etc ‚̊Ԃɉ½‚©‚ ‚é‚Æ•Ö—˜‚Å‚·B‚ ‚Æ gdb ‚ƃRƒAƒtƒ@ƒCƒ‹‚àB

ps/*stat‚Ȃǂ̃c[ƒ‹‚ÆAgdb‚ɃRƒAƒtƒ@ƒCƒ‹‚Ƃ̊Ԃɉ½‚©‚ª‚ ‚é‚Æ•Ö—˜‚Å‚µ‚å 
‚¤B
‰½‚©A`

> ‚¨‚»‚ç‚­ SysV(?) ‚Ì crash(8) ‚̂悤‚È‚à‚Ì‚Å‚·B
>   Ó”CŽÒ: TBD
>   ETA: ?
>
>
> ag. Better 802.11 utilities and support
>   To truly support mobile users, we need better support for scanning
>   for base stations and affiliating with them.
>   Responsible: dyoung, skrll, scw and others
>   ETA: 4.0
> ag. ‚æ‚è—Ç‚¢ 802.11 ƒ†[ƒeƒBƒŠƒeƒB‚ƃTƒ|[ƒg
>   –{“–‚Ƀ‚ƒoƒCƒ‹ƒ†[ƒU‚ðƒTƒ|[ƒg‚·‚邽‚ß‚É‚ÍAƒx[ƒXƒXƒe[ƒVƒ‡ƒ“‚ðŒŸõ 
> ‚µ‚Ä‚»‚ê‚ç‚ɉÁ“ü‚Å‚«‚é‚悤‚É‚·‚邱‚Æ‚ª•K—v‚Å‚·B
>   Ó”CŽÒ: dyoungAskrllAscwA‘¼
>   ETA: 4.0
>
> ah. Internationalization
>   Citrus, wide-char curses (SoC integration?), collation, localized
>   printf with positional parameter support, time & currency
>   support, etc.  NetBSD has a global user and developer base and
>   our i18n support should reflect that.
>       (a) Support cond. printf fmt. 4.0 will have vfwprintf with
>       positional parameter support; 5.0 will have vfprintf with
>       positional parameter support.
>       Responsible: christos
>       ETA: 5.0
>       (b) Support LC_COLLATE
>       (c) mklocale(1) -> localedef(1)
>       (d) wchar_t in C++
>       (e) i18nize userland commands
>       (f) in-kernel iconv
>       Responsible: TBD
>       ETA: ?
> ah. ‘Û‰»
>   CitrusAƒƒCƒh•¶Žš‘Ήž curses(SoC ‚É“‡H)A•¶ŽšÆ‡AˆÊ’uƒpƒ‰ƒ[ 
> ƒ^[‘Ήž‚̃[ƒJƒ‰ƒCƒY‚³‚ꂽ
> printfƒTƒ|[ƒgAŽž‚ƒʉ݃Tƒ|[ƒgA‚»‚Ì‚Ù‚©BNetBSD ‚ɂ̓Oƒ[ƒoƒ‹‚È 
> ƒ†[ƒU[‚ÆŠJ”­ŽÒƒx[ƒX‚ª‚ ‚èA‚»‚µ‚Ä i18n
> ‚Í‚»‚ê‚ç‚𔽉f‚·‚ׂ«‚Å‚·B
>       (a) Support cond. printf fmt: 4.0 ‚É‚ÍAˆÊ’uƒpƒ‰ƒƒ^ƒTƒ|[ƒg‘Î 
> ‰ž vfwprintf ‚ª‚ ‚é‚Å‚µ‚傤B
> 5.0 ‚É‚ÍAˆÊ’uƒpƒ‰ƒƒ^ƒTƒ|[ƒg‚ª‚ ‚é vfprintf ‚ª‚ ‚é‚Å‚µ‚傤B
>       Ó”CŽÒ: christos
>       ETA: 5.0
>       (b) LC_COLLATEƒTƒ|[ƒg
>       (c) mklocale(1) -> localedef(1)
>       (d) C++ ‚É‚¨‚¯‚é wchar_t
>       (e) i18n ‰»‚³‚ꂽƒ†[ƒU[ƒ‰ƒ“ƒhƒRƒ}ƒ“ƒh
>       (f) ƒJ[ƒlƒ‹‚É‚¨‚¯‚é iconv
>       Ó”CŽÒ: TBD
>       ETA: ?
>
>
> ai. System packages
>   In some fashion, we need to support system packages.  This is at
>   least to allow for sane binary audits and binary patches.
>   Responsible: apb
>   ETA: 4.0
> ai. ƒVƒXƒeƒ€ƒpƒbƒP[ƒW
>   ‚¢‚­‚‚©‚Ì—¬‹V‚É‚æ‚èƒVƒXƒeƒ€ƒpƒb

‰½‚ç‚©‚Ì‚â‚è•û‚ŃVƒXƒeƒ€`

> ƒP[ƒW‚ðƒTƒ|[ƒg‚·‚é•K—v‚ª‚ ‚è‚Ü‚·B‚±‚ê‚ÍA­‚È‚­‚Æ‚à‚Ü‚Æ‚à‚ȃoƒCƒiƒŠ 
> ŠÄ¸‚¨‚æ‚уoƒCƒiƒŠŒ`Ž®‚̃pƒbƒ`‚ð‰Â”\‚É‚µ‚Ü‚·B
>   Ó”CŽÒ: apb
>   ETA: 4.0
>
> aj. Provide support for binary packages in install
>   We should have an integrated install that can install a desktop as
>   functional as other free operating systems.  Without sacrificing
>   the quick and clean basic installs that we have now.  An extension
>   of sysinst might fit the bill.  Or a tool that's both invoked by
>   sysinst and available on a running system, e.g. pkgsrc-wip/ 
> pkg_select.
>   Responsible: agc and others
>   ETA: 4.0
> aj. ƒCƒ“ƒXƒg[ƒ‹Žž‚É‚¨‚¯‚éƒoƒCƒiƒŠƒpƒbƒP[ƒW‚Ì’ñ‹Ÿ
>   v‘¬‚Å”ü‚µ‚¢Šù‘¶‚ÌŠî–{“I‚ȃCƒ“ƒXƒg[ƒ‹ŠÂ‹«‚ð‹]µ‚É‚¹‚¸‚ÉA‘¼‚̃tƒŠ[ 
> ‚̃IƒyƒŒ[ƒeƒBƒ“ƒOƒVƒXƒeƒ€‚Æ“¯‚¶‚­‚ç‚¢‹@”\“I‚ȃfƒXƒNƒgƒbƒv‚ðƒCƒ“ƒXƒg[ 
> ƒ‹‚Å‚«‚铇ƒCƒ“ƒXƒg[ƒ‹‚ª‚ ‚é‚ׂ«‚Å‚·Bsysinst
> ‚ÌŠg’£‚Í‚±‚Ì—v–]‚ð–ž‚½‚·‚©‚à‚µ‚ê‚Ü‚¹‚ñB‚Ü‚½‚Í sysinst ‚É‚æ‚Á‚ČĂÑo‚³ 
> ‚ê‚éƒc[ƒ‹‚âAŽÀs’†‚̃VƒXƒeƒ€‚Å—˜—p‰Â”\‚ȃc[ƒ‹‚Å‚·i—Ⴆ‚Î
> pkgsrc-wip/pkg_selectjB
>   Ó”CŽÒ: agc ‘¼
>   ETA: 4.0
>
> ak. Native signing/privacy software
>   This could be BPG (from SoC) or openpgp-sdk.
>   Responsible: agc, cjs and others
>   ETA: 4.0?
> ak. ƒlƒCƒeƒBƒu‚Ì–¼/”铽«ƒ\ƒtƒgƒEƒFƒA
>   ‚±‚ê‚Í BPG(SoC ‚©‚ç‚Ì) ‚Ü‚½‚Í openpgp-sdk ‚©‚à‚µ‚ê‚Ü‚¹‚ñB
>   Ó”CŽÒ: agcAcjsA‘¼
>   ETA: 4.0?
>
> al. Userland version identification
>   What binaries are installed?  Who really knows?  This relates at
>   least somewhat to (ai).
>   Responsible: TBD
>   ETA: ?
> al. ƒ†[ƒU[ƒ‰ƒ“ƒhƒo[ƒWƒ‡ƒ“Ž¯•Ê
>   ‚Ç‚ñ‚ȃoƒCƒiƒŠ‚ªƒCƒ“ƒXƒg[ƒ‹‚³‚ê‚Ä‚¢‚Ü‚·‚©H‚¾‚ꂪ–{“–‚É’m‚Á‚Ä‚¢‚Ü‚· 
> ‚©H ­‚È‚­‚Æ‚à‚±‚ê‚Í ai. ‚É‚¢‚­‚ç‚©ŠÖ˜A‚µ‚Ü‚·B
>   Ó”CŽÒ: TBD
>   ETA: ?
>
> 3. Platform dependent kernel
> 3. ƒvƒ‰ƒbƒgƒtƒH[ƒ€‚Ɉˑ¶‚·‚éƒJ[ƒlƒ‹
> ============================
> aa. Move evb ports to evb* if they're not already there (sandpoint)
>   The existing evb* ports are kind of catch-all ports for eval boards.
>   Some of the existing non-evb* ports really belong in the evb*  
> category.
>   Responsible: TBD
>   ETA: ?
>
> aa. evb ƒ|[ƒg‚ª‚·‚Å‚É sandpoint ƒ|[ƒg‚É–³‚¢‚È‚ç‚ÎAevb ƒ|[ƒg ‚ð  
> evb* ‚Ì•û‚Ö“®‚©‚µ‚Ä‚­‚¾‚³‚¢(sandpoint)
>   Šù‘¶‚Ì evb* ƒ|[ƒg‚ÍA‚Ç‚ñ‚ÈŽí—Þ‚Ì•]‰¿ƒ{[ƒh‚É‚à‘Ήž‚µ‚Ü‚·BŠù‘¶‚Ì 
> ”ñ evb* ƒ|[ƒg‚Ì‚¢‚­‚‚©‚ÍA–{“–‚Í evb* ƒJƒeƒSƒŠ[‚É“ü‚è‚Ü‚·B
>   Ó”CŽÒ: TBD
>   ETA: ?
>
> ab. m68k ports need to share more code
>   Some progress has been made here in recent years, but there is more
>   work to be done.
>   Responsible: TBD
>   ETA: ?
> ab. m68k ƒ|[ƒg‚ÍA‚æ‚葽‚­‚̃R[ƒh‚ð‹¤—L‚·‚é•K—v‚ª‚ ‚è‚Ü‚·
>   ‹ß”N‚¢‚­‚‚©‚Ìi•à‚ªŒ©‚ç‚ê‚Ü‚µ‚½‚ªA‚Ü‚¾‚Ü‚¾‚â‚é‚ׂ«ŽdŽ–‚ª‚ ‚è‚Ü‚·B
>   Ó”CŽÒ: TBD
>   ETA: ?
>
> ac. Kernel core dump support for all platforms
>   Some platforms (PowerPC ports, ARM ports, etc.) don't have full
>   support for kernel core dumps and post-mortem debugging through
>   libkvm.  This should be updated.
>   Responsible: TBD
>   ETA: ?
> ac. ‚·‚ׂẴvƒ‰ƒbƒgƒtƒH[ƒ€‚̃J[ƒlƒ‹ƒRƒAƒ_ƒ“ƒvƒTƒ|[ƒg
>   ‚¢‚­‚‚©‚̃vƒ‰ƒbƒgƒtƒH[ƒ€ (PowerPC ƒ|[ƒgAARM ƒ|[ƒg‚È‚Ç) ‚ÍAƒJ[ 
> ƒlƒ‹ƒRƒAƒ_ƒ“ƒv‚â libkvm
> ‚ðŽg‚Á‚½ŒŸŽ€ƒfƒoƒbƒO‚ðŠ®‘S‚ɂ̓Tƒ|[ƒg‚µ‚Ä‚¢‚Ü‚¹‚ñB‚±‚ê‚ðƒAƒbƒvƒf[ƒg 
> ‚·‚ׂ«‚Å‚·B
>   Ó”CŽÒ: TBD
>   ETA: ?
>
> ad. NDIS
>   Support for binary network drivers on x86 platforms.
>   Responsible: rittera
>   ETA: 4.0
> ad. NDIS
>   x86 ƒvƒ‰ƒbƒgƒtƒH[ƒ€ã‚̃oƒCƒiƒŠ[ƒlƒbƒgƒ[ƒNƒhƒ‰ƒCƒo[‚̃Tƒ|[ƒg
>   Ó”CŽÒ: rittera
>   ETA: 4.0
>
> 4. Platform dependent userland
> 4. ƒvƒ‰ƒbƒgƒtƒH[ƒ€‚Ɉˑ¶‚·‚郆[ƒU[ƒ‰ƒ“ƒh
> ==============================
> ab. m68k should be able to share sets
>   Some progress has been made here in recent years, but there is more
>   work to be done.
>   Responsible: TBD
>   ETA: ?
> ab. m68k ‚Í sets ‚ð‹¤—L‚Å‚«‚é‚Í‚¸‚Å‚·
>   ‹ß”N‚¢‚­‚‚©‚Ìi•à‚ªŒ©‚ç‚ê‚Ü‚µ‚½‚ªA‚Ü‚¾‚Ü‚¾‚â‚é‚ׂ«ŽdŽ–‚ª‚ ‚è‚Ü‚·B
>   Ó”CŽÒ: TBD
>   aETA: ?
>
>
> 5. Other
> 5. ‚»‚Ì‘¼
> ========
> aa. More and better regression tests
>   The suite of tests that we have now is limited.  We should expand
>   these and provide systems (or manage a volunteer pool?) to run the
>   tests on -current and release branches on a variety of platforms.
>   We also need to migrate all the tests that currently live in
>   'regress' to 'tests' so that they can make use of ATF.
>   ( Need to virtualize some with qemu or similar? )
>   Responsible: jmmv
>   ETA: 5.0 should have most of regress converted
>
> aa. ‚æ‚葽‚­‚Ì‚æ‚è—Ç‚¢‰ñ‹AƒeƒXƒg
>   Œ»Ý‚ ‚éƒeƒXƒgƒXƒC[ƒg‚ÍŒÀ‚ç‚ê‚Ä‚¢‚Ü‚·B‚³‚Ü‚´‚܂ȃvƒ‰ƒbƒgƒtƒH[ƒ€ 
> ‚Ì current ‚Æ
> ƒŠƒŠ[ƒXƒuƒ‰ƒ“ƒ`—p‚̃eƒXƒg‚ð‰^—p‚·‚邽‚ß‚ÉAƒVƒXƒeƒ€‚ð’ñ‹Ÿ‚·‚ׂ«‚Å‚·  
> (‚Ü‚½‚̓{ƒ‰ƒ“ƒeƒBƒAƒv[ƒ‹‚ðŠÇ—‚·‚é? )B‚Ü‚½AATF
> ‚ð—˜—p‚Å‚«‚é‚悤‚É‚·‚邽‚ß‚ÉŒ»Ý‚Ì 'regress' ‚©‚ç 'tests'
> ‚̊‹«‚Ì‚·‚ׂĂðƒeƒXƒg‚Å‚«‚é‚悤‚É‚·‚é•K—v‚ª‚ ‚è‚Ü‚·B(qemu ‚©“¯—l‚Ì•¨ 
> ‚ð‰¼‘z‰»‚·‚邽‚ß‚É‚à•K—v‚©? )
>   Ó”CŽÒ: jmmv
>   ETA: 5.0 ‚Å‚ÍA‘å•”•ª‚̉ñ‹AƒeƒXƒg‚ð•ÏX‚µ‚È‚¯‚ê‚΂Ȃè‚Ü‚¹‚ñB
>
> ab. Native Java on multiple platforms
>   Getting i386, amd64, sparc64, and PowerPC would be a good start,
>   although PowerPC will require more work.  We have the go-ahead,
>   but we need the people to work on it.
>   Responsible: the Java porting crew
>   ETA: ?
>
> ab. •¡”ƒvƒ‰ƒbƒgƒtƒH[ƒ€‚̃lƒCƒeƒBƒu Java
>   i386Aamd64Asparc64APowerPC ‚ð“üŽè‚·‚ê‚ÎD’²‚ɃXƒ^[ƒg‚Å‚«‚é‚Å‚µ‚å 
> ‚¤BPowerPC
> ‚ÍA‚æ‚葽‚­‚ÌŽdŽ–‚ð•K—v‚Æ‚·‚é‚Å‚µ‚傤‚¯‚ê‚ÇBƒXƒ^[ƒg‚Å‚«‚Ü‚·‚ªA—˜—p 
> ŽÒ‚ª‚±‚ê‚ÉŽæ‚è‘g‚Þ•K—v‚ª‚ ‚è‚Ü‚·B
>   Ó”CŽÒ: Java ˆÚAì‹Æˆõ
>   ETA: ?
>
> ac. Power control framework
>   Related to suspend/resume support, we should have some framework
>   for dynamically stepping processor speed, controlling fans, shutting
>   down and/or powering subsystems to conserve power and keep the  
> system
>   with thermal limits.
>   Responsible: TBD
>   ETA: ?
> ac. “dŒ¹§Œä‘•’uƒtƒŒ[ƒ€ƒ[ƒN
>   ƒTƒXƒyƒ“ƒh/ƒŠƒWƒ…[ƒ€‚ÉŠÖ˜A‚µ‚ÄAƒvƒƒZƒbƒT[‚Ì“®“IƒXƒeƒbƒvƒXƒs[ƒhA 
> ƒtƒ@ƒ“§ŒäAƒVƒƒƒbƒgƒ_ƒEƒ“‚âÈ“d—Í‚Ì‚½‚ß‚Ì“dŒ¹ƒTƒuƒVƒXƒeƒ€A”M§ŒÀ’lŽg 
> —p‚É‚æ‚éƒVƒXƒeƒ€ˆÛŽA‚Æ‚¢‚¤‚¢‚­‚‚©‚̃tƒŒ[ƒ€ƒ[ƒN‚ª‚ ‚è‚Ü‚·B
>   Ó”CŽÒ: TBD
>   ETA: ?
>
> <<<<‚±‚±‚Ü‚Å