diff options
Diffstat (limited to 'en_US.ISO8859-1/articles/laptop/article.xml')
| -rw-r--r-- | en_US.ISO8859-1/articles/laptop/article.xml | 40 |
1 files changed, 19 insertions, 21 deletions
diff --git a/en_US.ISO8859-1/articles/laptop/article.xml b/en_US.ISO8859-1/articles/laptop/article.xml index c283427099..f619424f9d 100644 --- a/en_US.ISO8859-1/articles/laptop/article.xml +++ b/en_US.ISO8859-1/articles/laptop/article.xml @@ -1,10 +1,9 @@ <?xml version="1.0" encoding="iso-8859-1"?> -<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.5-Based Extension//EN" - "../../../share/xml/freebsd45.dtd"> - -<article lang='en'> - <articleinfo> - <title>FreeBSD on Laptops</title> +<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN" + "../../../share/xml/freebsd50.dtd"> +<article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en"> + <info><title>FreeBSD on Laptops</title> + <abstract> <para>FreeBSD works fine on most laptops, with a few caveats. @@ -13,7 +12,7 @@ discussed below.</para> </abstract> - <legalnotice id="trademarks" role="trademarks"> + <legalnotice xml:id="trademarks" role="trademarks"> &tm-attrib.freebsd; &tm-attrib.linux; &tm-attrib.microsoft; @@ -23,7 +22,7 @@ <pubdate>$FreeBSD$</pubdate> <releaseinfo>$FreeBSD$</releaseinfo> - </articleinfo> + </info> <para>FreeBSD is often thought of as a server operating system, but it works just fine on the desktop, and if you want to use it on @@ -43,15 +42,15 @@ word <quote>&os;</quote> into a search engine of your choice. Additionally there is a &os;-specific online database which aims to give information on hardware issues with laptops, - <ulink url="http://laptop.bsdgroup.de/freebsd/">The &os; - Laptop Compatibility List</ulink>.</para> + <link xlink:href="http://laptop.bsdgroup.de/freebsd/">The &os; + Laptop Compatibility List</link>.</para> <para>If you want to communicate with other &os; laptop users, check out the &a.mobile.name; list. You can also get additional information about using Laptops on &os; at - <ulink url="http://tuxmobil.org/mobile_bsd.html"></ulink>.</para> + <uri xlink:href="http://tuxmobil.org/mobile_bsd.html">http://tuxmobil.org/mobile_bsd.html</uri>.</para> - <sect1 id="xorg"> + <sect1 xml:id="xorg"> <title>&xorg;</title> <para>Recent versions of <application>&xorg;</application> work with most display adapters @@ -91,7 +90,7 @@ section.</para> </sect1> - <sect1 id="modems"> + <sect1 xml:id="modems"> <title>Modems</title> <para> Laptops usually come with internal (on-board) modems. @@ -99,7 +98,7 @@ <quote>winmodems</quote> whose functionality is implemented in software, for which only &windows; drivers are normally available (though a few drivers are beginning - to show up for other operating systems; for example, if your modem has a Lucent LT chipset it might be supported by the <filename role="package">comms/ltmdm</filename> port). If that is the case, you + to show up for other operating systems; for example, if your modem has a Lucent LT chipset it might be supported by the <package>comms/ltmdm</package> port). If that is the case, you need to buy an external modem: the most compact option is probably a PC Card (PCMCIA) modem, discussed below, but serial or USB modems may be cheaper. Generally, regular @@ -108,16 +107,16 @@ </sect1> - <sect1 id="pcmcia"> + <sect1 xml:id="pcmcia"> <title>PCMCIA (PC Card) devices</title> <para> Most laptops come with PCMCIA (also called PC Card) slots; these are supported fine under FreeBSD. Look through your boot-up messages (using &man.dmesg.8;) and see whether these were detected correctly (they should appear as - <devicename>pccard0</devicename>, - <devicename>pccard1</devicename> etc on devices like - <devicename>pcic0</devicename>).</para> + <filename>pccard0</filename>, + <filename>pccard1</filename> etc on devices like + <filename>pcic0</filename>).</para> <para>&os; 4.X supports 16-bit PCMCIA cards, and &os; 5.X supports both 16-bit and @@ -156,7 +155,7 @@ </sect1> - <sect1 id="power-management"> + <sect1 xml:id="power-management"> <title>Power management</title> @@ -225,8 +224,7 @@ SC_NO_SUSPEND_VTYSWITCH</literal> in your kernel configuration file and recompile your kernel. Another workaround is to switch to a virtual console (using - <keycombo - action="simul"><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F1</keycap></keycombo> + <keycombo action="simul"><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F1</keycap></keycombo> or another function key) and then execute &man.apm.8;. You can automate this with &man.vidcontrol.1;, if you are running &man.apmd.8;. Simply edit |