Date: Fri, 18 Jul 2014 12:32:16 +0000 (UTC) From: Warren Block <wblock@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45337 - head/en_US.ISO8859-1/htdocs/news/status Message-ID: <201407181232.s6ICWGgJ042544@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: wblock Date: Fri Jul 18 12:32:15 2014 New Revision: 45337 URL: http://svnweb.freebsd.org/changeset/doc/45337 Log: Add more <tt> markup around man page references. Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2014-04-2014-06.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2014-04-2014-06.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2014-04-2014-06.xml Fri Jul 18 12:17:32 2014 (r45336) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2014-04-2014-06.xml Fri Jul 18 12:32:15 2014 (r45337) @@ -121,7 +121,7 @@ <body> <p>The so-called "CUSE4BSD" has been imported into the base system of &os;-11. CUSE is short for character device in - userspace. The CUSE library is a wrapper for the devfs(8) + userspace. The CUSE library is a wrapper for the <tt>devfs(8)</tt> kernel functionality which is exposed through /dev/cuse. In order to function, the CUSE kernel code must either be enabled in the kernel configuration file or loaded separately as @@ -166,7 +166,7 @@ <p>There is also ongoing work on improving CTL functionality. It was already made to support three of four VMware VAAI storage - acceleration primitives (net/istgt supports 2), while the goal + acceleration primitives (<tt>net/istgt</tt> supports 2), while the goal is to reach full VAAI support during next months.</p> <p>With all these improvements, and earlier improvements in CAM, GEOM, ZFS, @@ -608,13 +608,13 @@ added UEFI support to the &os; installer and release image creation script.</p> - <p>The EFI framebuffer requires the vt(4) system console — + <p>The EFI framebuffer requires the <tt>vt(4)</tt> system console — a framebuffer driver is not implemented for the legacy - syscons(4) console. Ed added automatic vt(4) selection to the + <tt>syscons(4)</tt> console. Ed added automatic <tt>vt(4)</tt> selection to the UEFI boot path.</p> <p>Snapshots are now built as dual-mode images, and should boot - via BIOS and UEFI. Our plan is to merge the UEFI and vt(4) + via BIOS and UEFI. Our plan is to merge the UEFI and <tt>vt(4)</tt> work to stable/10 to appear in &os; 10.1-RELEASE.</p> </body> @@ -897,7 +897,7 @@ be included in &os; 10.1.</p> <p>Work continues on the Foundation-sponsored autofs automount - daemon, UEFI boot support, the updated vt(4) system video + daemon, UEFI boot support, the updated <tt>vt(4)</tt> system video console, virtual machine images, and the Intel graphics driver update. Foundation-sponsored work resulted in 226 commits to &os; over the April to June period.</p> @@ -952,7 +952,7 @@ drivers that implement peripheral drivers and SIMs for CAM MMC. The plan is to use a modified version of BeagleBone Black SDHCI controller driver for SIM and a modified version of - mmcsd(4) as a peripheral driver.</task> + <tt>mmcsd(4)</tt> as a peripheral driver.</task> <task>Marvell SDIO WiFi: connect to the &os; network stack, write the code to implement required functions (such as @@ -1067,13 +1067,13 @@ on the L4OpenBSD code.</task> <task>Improve the port, the first task being adopting the - pmap(9) module to work with L4 microkernel memory allocation + <tt>pmap(9)</tt> module to work with L4 microkernel memory allocation services.</task> </help> </project> <project cat="proj"> - <title>pkg(8)</title> + <title><tt>pkg(8)</tt></title> <contact> <person> @@ -1115,21 +1115,21 @@ </contact> <links> - <url href="https://github.com/freebsd/pkg">The main pkg(8) git + <url href="https://github.com/freebsd/pkg">The main <tt>pkg(8)</tt> git repository.</url> <url href="https://github.com/freebsd/pkg/issues">The preferred - place to raise bug reports concerning pkg(8).</url> + place to raise bug reports concerning <tt>pkg(8)</tt>.</url> </links> <body> - <p>pkg(8) is the new package management tool for &os;. It + <p><tt>pkg(8)</tt> is the new package management tool for &os;. It is now the only supported package management tool for &os; releases from 10.0-RELEASE, including the upcoming - 9.3-RELEASE. pkg(8) is available on all currently supported + 9.3-RELEASE. <tt>pkg(8)</tt> is available on all currently supported releases. Support for the legacy pkg_tools is due to be discontinued at the beginning of September 2014.</p> - <p>The release of pkg(8) 1.3 is imminent. This includes major + <p>The release of <tt>pkg(8)</tt> 1.3 is imminent. This includes major improvements in the dependency solver. Now we can:</p> <ul> @@ -1156,13 +1156,13 @@ a selection of "foreign" package repositories, such as CPAN or CTAN or PyPi.</p> - <p>There are plans to use pkg(8) to package up the base system. + <p>There are plans to use <tt>pkg(8)</tt> to package up the base system. Along with other benefits, this will allow writing a universal installer: download one installer image and from there install any available version of &os;, including snapshots.</p> - <p>We are also intending to use pkg(8) within the ports tree at + <p>We are also intending to use <tt>pkg(8)</tt> within the ports tree at package-build time to handle fulfilling build dependencies. This opens the possibility of installing build-dependencies by downloading binary packages, which means you can install @@ -1209,7 +1209,7 @@ <p>We were generally short on time this quarter. We made less progress than expected on all fronts.</p> - <p>The alternate pkg(8) repository, built with WITH_NEW_XORG, is + <p>The alternate <tt>pkg(8)</tt> repository, built with WITH_NEW_XORG, is now available. This alleviates the need for users to rebuild their ports with WITH_NEW_XORG. See the announcement, linked above for further information.</p> @@ -1302,7 +1302,7 @@ </contact> <body> - <p>Extensive testing of tmpfs(5) using the stress2 kernel test + <p>Extensive testing of <tt>tmpfs(5)</tt> using the stress2 kernel test suite was done. The issues found were debugged and fixed.</p> <p>Most of the problems are related to the bugs in the
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201407181232.s6ICWGgJ042544>