Date: Sat, 3 Dec 2011 12:01:26 GMT From: Rene Ladan <rene@FreeBSD.org> To: Perforce Change Reviews <perforce@FreeBSD.org> Subject: PERFORCE change 202541 for review Message-ID: <201112031201.pB3C1QD7004871@skunkworks.freebsd.org>
next in thread | raw e-mail | index | archive | help
http://p4web.freebsd.org/@@202541?ac=10 Change 202541 by rene@rene_acer on 2011/12/03 12:01:06 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributing-ports/article.sgml#5 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#113 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.develalumni.sgml#10 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/fdp-primer/the-website/chapter.sgml#5 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml#11 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#115 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/desktop/chapter.sgml#47 integrate .. //depot/projects/docproj_nl/www/en/platforms/sparc.sgml#8 integrate .. //depot/projects/docproj_nl/www/en/projects/newbies.sgml#6 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributing-ports/article.sgml#5 (text+ko) ==== @@ -7,7 +7,7 @@ <articleinfo> <title>Contributing to the FreeBSD Ports Collection</title> - <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/contributing-ports/article.sgml,v 1.7 2011/09/28 20:01:35 blackend Exp $</pubdate> + <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/contributing-ports/article.sgml,v 1.9 2011/11/28 15:43:34 ryusuke Exp $</pubdate> <abstract> <title>Abstract</title> @@ -130,7 +130,7 @@ <para>You can find out whether or not a port has dependencies or slave ports by looking at a master index of ports called <filename>INDEX</filename>. (The name of the file varies - by release of &os;; for instance, <filename>INDEX-6</filename>.) + by release of &os;; for instance, <filename>INDEX-8</filename>.) Some ports have conditional dependencies that are not included in a default <filename>INDEX</filename> build. We expect you to be able to recognize such ports by looking through @@ -356,7 +356,8 @@ case, at the very least, the dependent ports will need to get a <makevar>PORTREVISION</makevar> bump so that they will automatically be upgraded by - automated tools such as &man.portupgrade.1;.</para> + automated tools such as <application>portmaster</application> + or &man.portupgrade.1;.</para> </listitem> </itemizedlist> </step> @@ -418,8 +419,8 @@ <para>&os; only guarantees that the Ports Collection works on the <literal>-STABLE</literal> branches. You should be - running <literal>5-STABLE</literal> or - <literal>6-STABLE</literal>, preferably the latter. In + running <literal>7-STABLE</literal> or + <literal>8-STABLE</literal>, preferably the latter. In theory, you should be able to get by with running the latest release of each stable branch (since the ABIs are not supposed to change) but if you can run the branch, that is @@ -428,17 +429,16 @@ <para>Since the majority of &os; installations run on PC-compatible machines (what is termed the <literal>i386</literal> architecture), we expect you to keep the port working on that - architecture. However, as more and more people start using - the <literal>amd64</literal> architecture running native, it is - going to be more and more important to make sure that ports run - there as well. It is completely fair to ask for help if you + architecture. We prefer that ports also work on + the <literal>amd64</literal> architecture running native. + It is completely fair to ask for help if you do not have one of these machines.</para> <note> <para>The usual failure modes for non-<literal>i386</literal> machines are that the original programmers assumed that, for - instance, pointers are <literal>int</literal>s, or that the - relatively lax <application>gcc</application> 2.95 compiler + instance, pointers are <literal>int</literal>s, or that a + relatively lax older <application>gcc</application> compiler was being used. More and more, application authors are reworking their code to remove these assumptions — but if the author is not actively maintaining their code, @@ -568,6 +568,10 @@ 14 days, but please try not to take that long. Try to respond as soon as possible, even if it is just to say you need some more time before you can work on the PR.</para> + + <para>If you have not responded after 14 days, any committer may + commit from a PR that you have not responded to via a + <literal>maintainer-timeout</literal>.</para> </step> <step> @@ -685,7 +689,7 @@ </itemizedlist> <para>In these cases your main obligation is to respond in a - timely manner. The timeout for non-responsive maintainers is + timely manner. Again, the timeout for non-responsive maintainers is 14 days. After this period changes may be committed unapproved. They have taken the trouble to do this for you; so please try to at least respond promptly. Then review, ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#113 (text+ko) ==== @@ -1,4 +1,4 @@ -<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml,v 1.1034 2011/11/16 17:51:46 crees Exp $ --> +<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml,v 1.1036 2011/12/01 20:06:06 crees Exp $ --> <!-- NOTE TO COMMITTERS: Contributors lists are sorted in alphabetical order by first name. @@ -384,6 +384,11 @@ </listitem> <listitem> + <para>Alexander Pereira Girald + <email>girald@etcom.ufrgs.br</email></para> + </listitem> + + <listitem> <para>Alexander Gromnizki <email>gromnizki@unixdev.net</email></para> </listitem> @@ -7537,6 +7542,11 @@ </listitem> <listitem> + <para>Norberto Lopes + <email>nlopes.ml@gmail.com</email></para> + </listitem> + + <listitem> <para>Norio Suzuki <email>nosuzuki@e-mail.ne.jp</email></para> </listitem> ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.develalumni.sgml#10 (text+ko) ==== @@ -1,4 +1,4 @@ -<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.develalumni.sgml,v 1.61 2011/11/09 20:16:30 crees Exp $ --> +<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.develalumni.sgml,v 1.62 2011/11/27 18:34:52 crees Exp $ --> <itemizedlist> <listitem> <para>&a.jacula; (2010 - 2011)</para> @@ -125,7 +125,7 @@ </listitem> <listitem> - <para>&a.nik; (2003 - 2009)</para> + <para>&a.nik; (1998 - 2009)</para> </listitem> <listitem> ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/fdp-primer/the-website/chapter.sgml#5 (text+ko) ==== @@ -27,7 +27,7 @@ ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - $FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/the-website/chapter.sgml,v 1.27 2009/01/21 23:46:32 pgj Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/the-website/chapter.sgml,v 1.28 2011/11/27 16:37:30 manolis Exp $ --> <chapter id="the-website"> @@ -287,7 +287,10 @@ <step> <para>Run the &man.make.1; <maketarget>install</maketarget> target, setting the <makevar>DESTDIR</makevar> variable to the name of the - directory you want to install the files to.</para> + directory you want to install the files to. The actual files are + installed under <filename class="directory">$DESTDIR/data</filename> + which should be configured as your web server's document + root.</para> <screen>&prompt.root; <userinput><command>env</command> <makevar>DESTDIR</makevar>=<replaceable>/usr/local/www</replaceable> <command>make</command> <maketarget>install</maketarget></userinput></screen> </step> ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml#11 (text+ko) ==== @@ -1,7 +1,7 @@ <!-- The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml,v 1.25 2010/07/03 14:27:22 jkois Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml,v 1.26 2011/12/02 17:22:01 manolis Exp $ --> <chapter id="virtualization"> @@ -969,6 +969,117 @@ </sect3> </sect2> + + <sect2 id="virtualization-guest-virtualbox-guest-additions"> + <title>&virtualbox; Guest Additions on a &os; Guest</title> + + <para>The <application>&virtualbox;</application> guest additions + provide support for:</para> + + <itemizedlist> + <listitem> + <para>Clipboard sharing</para> + </listitem> + + <listitem> + <para>Mouse pointer integration</para> + </listitem> + + <listitem> + <para>Host time synchronization</para> + </listitem> + + <listitem> + <para>Window scaling</para> + </listitem> + + <listitem> + <para>Seamless mode</para> + </listitem> + </itemizedlist> + + <note> + <para>The following commands are run in the &os; guest.</para> + </note> + + <para>First, install the <filename + role="package">emulators/virtualbox-ose-additions</filename> + package in the &os; guest.</para> + + <screen>&prompt.root; <userinput>cd /usr/ports/emulators/virtualbox-ose-additions && make install clean</userinput></screen> + + <para>Add these lines to <filename>/etc/rc.conf</filename>:</para> + + <programlisting>vboxguest_enable="YES" +vboxservice_enable="YES"</programlisting> + + <para>If &man.ntpd.8; or &man.ntpdate.8; will be used, host time + synchronization should be disabled:</para> + + <programlisting>vboxservice_flags="--disable-timesync"</programlisting> + + <para>The <literal>vboxvideo_drv</literal> should be recognized by + <command>Xorg -configure</command>. If not, modify + <filename>xorg.conf</filename> for the + <application>&virtualbox;</application> video card:</para> + + <programlisting>Section "Device" + ### Available Driver options are:- + ### Values: <i>: integer, <f>: float, <bool>: "True"/"False", + ### <string>: "String", <freq>: "<f> Hz/kHz/MHz" + ### [arg]: arg optional + Identifier "Card0" + Driver "vboxvideo" + VendorName "InnoTek Systemberatung GmbH" + BoardName "VirtualBox Graphics Adapter" + BusID "PCI:0:2:0" +EndSection</programlisting> + + <para>To use <literal>vboxmouse_drv</literal>, adjust the mouse + section in your <filename>xorg.conf</filename>:</para> + + <programlisting>Section "InputDevice" + Identifier "Mouse0" + Driver "vboxmouse" +EndSection</programlisting> + + <para><acronym>HAL</acronym> users should create this file at + <filename>/usr/local/etc/hal/fdi/policy/90-vboxguest.fdi</filename> + or copy it from <filename>/usr/local/share/hal/fdi/policy/10osvendor/90-vboxguest.fdi</filename>:</para> + + <programlisting><?xml version="1.0" encoding="UTF-8"?> +<!-- +# Sun VirtualBox +# Hal driver description for the vboxmouse driver +# $Id: 90-vboxguest.fdi 21412 2009-07-08 21:18:57z vboxsync $ + + Copyright (C) 2008-2009 Sun Microsystems, Inc. + + This file is part of VirtualBox Open Source Edition (OSE, as + available from http://www.virtualbox.org. This file is free software; + you can redistribute it and/or modify it under the terms of the GNU + General Public License (GPL) as published by the Free Software + Foundation, in version 2 as it comes in the "COPYING" file of the + VirtualBox OSE distribution. VirtualBox OSE is distributed in the + hope that it will be useful, but WITHOUT ANY WARRANTY of any kind. + + Please contact Sun Microsystems, Inc., 4150 Network Circle, Santa + Clara, CA 95054 USA or visit http://www.sun.com if you need + additional information or have any questions. +--> +<deviceinfo version="0.2"> + <device> + <match key="info.subsystem" string="pci"> + <match key="info.product" string="VirtualBox guest Service"> + <append key="info.capabilities" type="strlist">input</append> + <append key="info.capabilities" type="strlist">input.mouse</append> + <merge key="input.x11_driver" type="string">vboxmouse</merge> + <merge key="input.device" type="string">/dev/vboxguest</merge> + </match> + </match> + </device> +</deviceinfo></programlisting> + </sect2> </sect1> <sect1 id="virtualization-host"> @@ -1000,8 +1111,10 @@ <title>Installing &virtualbox;</title> <para><application>&virtualbox;</application> is available as a &os; port - in <filename role="package">emulators/virtualbox-ose</filename>, and - may be installed using the following commands:</para> + in <filename role="package">emulators/virtualbox-ose</filename>. + As &virtualbox; is very actively developed, make sure your ports + tree is up to date before installing. Install using these + commands:</para> <screen>&prompt.root; <userinput>cd /usr/ports/emulators/virtualbox-ose</userinput> &prompt.root; <userinput>make install clean</userinput></screen> @@ -1028,37 +1141,14 @@ <programlisting>vboxdrv_load="YES"</programlisting> - <para>Versions of <application>&virtualbox;</application> prior to 3.1.2 - require the <filename class="directory">proc</filename> file system - to be mounted. This is not needed in recent versions, which utilize - the functions provided by the &man.sysctl.3; library.</para> + <para>To use the kernel modules that allow bridged or host-only + networking, add the following to <filename>/etc/rc.conf</filename> + and reboot the computer:</para> - <para>When using an older version of the port, follow the instructions - below to make sure <filename class="directory">proc</filename> is - mounted properly:</para> - - <screen>&prompt.root; <userinput>mount -t procfs proc /proc</userinput></screen> + <programlisting>vboxnet_enable="YES"</programlisting> - <para>To allow this setting to persist reboots, the following line - is needed in <filename>/etc/fstab</filename>:</para> - - <programlisting>proc /proc procfs rw 0 0</programlisting> - - <note> - <para>If an error message similar to the following is observed - when <application>&virtualbox;</application> is run from - the terminal:</para> - - <screen>VirtualBox: supR3HardenedExecDir: couldn't read "", errno=2 cchLink=-1</screen> - - <para>The most likely culprit will be the <filename - class="directory">proc</filename> file system. Please use the - <command>mount</command> command to check whether it is mounted - properly.</para> - </note> - <para>The <groupname>vboxusers</groupname> group is created during - the installation of <application>&virtualbox;</application>. + installation of <application>&virtualbox;</application>. All users that need access to <application>&virtualbox;</application> will have to be added as members of this group. The <command>pw</command> command may be used to add new @@ -1066,8 +1156,23 @@ <screen>&prompt.root; <userinput>pw groupmod vboxusers -m <replaceable>yourusername</replaceable></userinput></screen> + <para>The default permissions for <filename + class="devicefile">/dev/vboxnetctl</filename> are restrictive and + need to be changed for bridged networking.</para> + + <para>To test it temporarily:</para> + + <screen>&prompt.root; <userinput>chown root:vboxusers /dev/vboxnetctl</userinput> +&prompt.root; <userinput>chmod 0660 /dev/vboxnetctl</userinput></screen> + + <para>To make the permissions change permanent, add these + lines to <filename>/etc/devfs.conf</filename>: + + <programlisting>own vboxnetctl root:vboxusers +perm vboxnetctl 0660</programlisting> + <para>To launch <application>&virtualbox;</application>, either select - the <guimenuitem>Sun VirtualBox</guimenuitem> item from your + the <guimenuitem>Sun VirtualBox</guimenuitem> item from the graphic environment's menu, or type the following in a terminal:</para> @@ -1081,6 +1186,71 @@ visit the relevant page in the &os; wiki, at <ulink url="http://wiki.FreeBSD.org/VirtualBox"></ulink>.</para>; </sect2> + + <sect2 id="virtualization-virtualbox-usb-support"> + <title>&virtualbox; USB Support</title> + + <note> + <para>These steps require VirtualBox 4.0.0 or later.</para> + </note> + + <para>In order to be able to read and write to USB devices, users + need to be members of the operator group:</para> + + <screen>&prompt.root; <userinput>pw groupmod operator -m <replaceable>jerry</replaceable></userinput></screen> + + <para>Then, add the following to <filename>/etc/devfs.rules</filename> + (create it if it does not exist yet):</para> + + <programlisting>[system=10] +add path 'usb/*' mode 0660 group operator</programlisting> + + <para>To load these new rules, add the following to + <filename>/etc/rc.conf</filename>:</para> + + <programlisting>devfs_system_ruleset="system"</programlisting> + + <para>Then, restart devfs:</para> + + <screen>&prompt.root; <userinput>/etc/rc.d/devfs restart</userinput></screen> + + <para>USB can now be enabled in the guest operating system. + USB devices should be visible in the &virtualbox; preferences.</para> + </sect2> + + <sect2 id="virtualization-virtualbox-host-dvd-cd-access"> + <title>&virtualbox; Host DVD/CD Access</title> + + <para>The <command>atapicam</command> kernel module needs to be loaded + by adding the following line to + <filename>/boot/loader.conf</filename>:</para> + + <programlisting>atapicam_load="YES"</programlisting> + + <para><acronym>HAL</acronym> needs to run for + <application>&virtualbox;</application> DVD/CD functions to work, + so enable it in <filename>/etc/rc.conf</filename> and start it + (if it is not already running):</para> + + <programlisting>hald_enable="YES"</programlisting> + + <screen>&prompt.root; <userinput>/usr/local/etc/rc.d/hald start</userinput></screen> + + <para>In order for users to be able to use + <application>&virtualbox;</application> DVD/CD functions, they need + access to <filename class="devicefile">/dev/xpt0</filename>, + <filename + class="devicefile">/dev/cd<replaceable>N</replaceable></filename>, + and <filename + class="devicefile">/dev/pass<replaceable>N</replaceable></filename>. + Add the following lines to + <filename>/etc/devfs.conf</filename>:</para> + + <programlisting>perm cd0 0600 +perm xpt0 0660 +perm pass0 0660</programlisting> + </sect2> + <!-- Note: There is no working/end-user ready Xen support for FreeBSD as of 07-2010. Hide all information regarding Xen under FreeBSD. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#115 (text+ko) ==== @@ -1,7 +1,7 @@ <!-- The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/books/porters-handbook/book.sgml,v 1.1119 2011/11/04 14:28:43 pav Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/porters-handbook/book.sgml,v 1.1122 2011/12/02 22:24:30 dougb Exp $ --> <!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ @@ -8743,21 +8743,20 @@ # Set it to YES to enable doormand. # doormand_config (path): Set to %%PREFIX%%/etc/doormand/doormand.cf # by default. -# . /etc/rc.subr name="doormand" rcvar=${name}_enable -command=%%PREFIX%%/sbin/${name} -pidfile=/var/run/${name}.pid - load_rc_config $name -: ${doormand_enable="NO"} +: ${doormand_enable:="NO"} : ${doormand_config="%%PREFIX%%/etc/doormand/doormand.cf"} +command=%%PREFIX%%/sbin/${name} +pidfile=/var/run/${name}.pid + command_args="-p $pidfile -f $doormand_config" run_rc_command "$1"</programlisting> @@ -8772,7 +8771,8 @@ down cleanly when the system shuts down. If the script is not starting a persistent service this is not necessary.</para> - <para>The "=" style of default variable assignment + <para>For optional configuration elements + the "=" style of default variable assignment is preferable to the ":=" style here, since the former sets a default value only if the variable is unset, and the latter sets one if the variable is unset @@ -8799,13 +8799,119 @@ whether to stop the service on deinstall or not. Also note this affects upgrades, too.</para> - <para>Line like this goes to the <filename>pkg-plist</filename>:</para> + <para>A line like this goes in the <filename>pkg-plist</filename>:</para> <programlisting>@stopdaemon doormand</programlisting> <para>The argument must match the content of <makevar>USE_RC_SUBR</makevar> variable.</para> </sect2> + + <sect2> + <title>Pre-Commit Checklist</title> + + <para>Before contributing a port with an <filename>rc.d</filename> + script, and more importantly, before commiting one; please consult + the following checklist to be sure that it is ready.</para> + + <procedure> + <step> + <para>If this is a new file, does it have <filename>.sh</filename> + in the file name? If so that should be changed to just + <filename>file.in</filename> since new <filename>rc.d</filename> + files may not end with that extension.</para> + </step> + + <step> + <para>Does the file have a + <literal>$FreeBSD$</literal> tag?</para> + </step> + + <step> + <para>Do the name of the file (minus <filename>.in</filename>), + the PROVIDE line, and $name all match? The file name + matching PROVIDE makes debugging easier, especially for + &man.rcorder.8; issues. Matching the file name and + $name makes figuring out what variables in + rc.conf[.local] are relevant easier as well. The latter is + also what you might call "policy" for all new + scripts, including in the base.</para> + </step> + + <step> + <para>Is the REQUIRE line set to LOGIN? This is mandatory for + scripts that run as a non-root user. If it runs as root, is + there a good reason for it to run prior to LOGIN? If not, it + should run there so that we can loosely group local scripts + to a point in &man.rcorder.8; after most everything in the + base is already running.</para> + </step> + + <step> + <para>Does the script start a persistent service? If so, it + should have KEYWORD: shutdown.</para> + </step> + + <step> + <para>Make sure there is no KEYWORD: FreeBSD present. This has + not been necessary or desirable for years. It is also an + indication that the new script was copy/pasted from an old + script, so extra caution should be given to the review.</para> + </step> + + <step> + <para>Does the script use an interpreted language (perl, python, + ruby, etc.)? If so, is command_interpreter set appropriately? + If not, it is likely that + <programlisting>&man.service.8; script stop</programlisting> + will not work properly.</para> + </step> + + <step> + <para>Are all examples of /usr/local subbed out for %%PREFIX%%?</para> + </step> + + <step> + <para>Do the default variable assignments come after + load_rc_config?</para> + </step> + + <step> + <para>Are there default assignments to empty strings? + They should be removed, but double-check that the option is + documented in the comments at the top of the file.</para> + </step> + + <step> + <para>Are things that are set in variables actually used in + the script?</para> + </step> + + <step> + <para>Are options listed in the default _flags things that are + actually mandatory? If so, they should be in command_args. + The -d option is a red flag (pardon the pun) here, since it's + usually the option to "daemonize" the process, and + therefore is actually mandatory.</para> + </step> + + <step> + <para>The _flags variable should never be included in command_args + (and vice versa, although that error is less common).</para> + </step> + + <step> + <para>Does the script execute any code unconditionally? This + is frowned on. Usually these things can/should be dealt with + through a start_precmd.</para> + </step> + + <step> + <para>All boolean tests should utilize the checkyesno function. + No hand-rolled tests for [Yy][Ee][Ss], etc.</para> + </step> + </procedure> + </sect2> </sect1> <sect1 id="users-and-groups"> ==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/desktop/chapter.sgml#47 (text+ko) ==== @@ -1,7 +1,7 @@ <!-- The FreeBSD Dutch Documentation Project - $FreeBSD: doc/nl_NL.ISO8859-1/books/handbook/desktop/chapter.sgml,v 1.35 2011/11/14 20:20:38 rene Exp $ + $FreeBSD: doc/nl_NL.ISO8859-1/books/handbook/desktop/chapter.sgml,v 1.36 2011/11/29 21:48:47 rene Exp $ %SOURCE% en_US.ISO8859-1/books/handbook/desktop/chapter.sgml %SRCID% 1.118 ==== //depot/projects/docproj_nl/www/en/platforms/sparc.sgml#8 (text+ko) ==== @@ -1,6 +1,6 @@ <!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ <!ENTITY base CDATA ".."> -<!ENTITY date "$FreeBSD: www/en/platforms/sparc.sgml,v 1.40 2010/11/06 13:01:54 marius Exp $"> +<!ENTITY date "$FreeBSD: www/en/platforms/sparc.sgml,v 1.41 2011/11/27 17:38:49 marius Exp $"> <!ENTITY title "FreeBSD/sparc64 Project"> <!ENTITY email 'freebsd-sparc64'> <!ENTITY % navinclude.developers "INCLUDE"> @@ -107,11 +107,13 @@ <li>Sun Fire V210</li> <li>Sun Fire V215 (support first appeared in 7.3-RELEASE and 8.1-RELEASE)</li> <li>Sun Fire V240</li> + <li>Sun Fire V245 (support first appeared in 7.3-RELEASE and 8.1-RELEASE)</li> <li>Sun Fire V250</li> <li>Sun Fire V440 (support for the on-board NICs first appeared in 7.3-RELEASE and 8.0-RELEASE)</li> <li>Sun Fire V480 (501-6780 and 501-6790 centerplanes only, for which support - first appeared in 7.3-RELEASE and 8.1-RELEASE)</li> + first appeared in 7.3-RELEASE and 8.1-RELEASE, + other centerplanes might work beginning with 8.3-RELEASE and 9.0-RELEASE)</li> <li>Sun Fire V880</li> <li>Sun Fire V890 (support first appeared in 7.4-RELEASE and 8.1-RELEASE, non-mixed Ultrasparc IV/IV+ CPU-configurations only)</li> @@ -123,7 +125,6 @@ <ul> <li>Sun Fire V125</li> - <li>Sun Fire V245 (support first appeared in 7.3-RELEASE and 8.1-RELEASE)</li> <li>Sun Fire V490 (support first appeared in 7.4-RELEASE and 8.1-RELEASE, non-mixed Ultrasparc IV/IV+ CPU-configurations only)</li> </ul> ==== //depot/projects/docproj_nl/www/en/projects/newbies.sgml#6 (text+ko) ==== @@ -1,6 +1,6 @@ <!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [ <!ENTITY base CDATA ".."> -<!ENTITY date "$FreeBSD: www/en/projects/newbies.sgml,v 1.63 2011/05/15 19:34:14 uqs Exp $"> +<!ENTITY date "$FreeBSD: www/en/projects/newbies.sgml,v 1.64 2011/11/27 19:19:06 gjb Exp $"> <!ENTITY title 'Resources for Newbies'> <!ENTITY % navinclude.docs "INCLUDE"> <!ENTITY url.articles "&base;/doc/en_US.ISO8859-1/articles"> @@ -178,14 +178,13 @@ throughout.</p></li> <li> - <p>A <a href="http://8help.osu.edu/wks/unix_course/">UNIX + <p>A <a href="http://www.cs.duke.edu/csl/docs/unix_course/">UNIX Introductory Course</a> from Ohio State University is - available online in HTML, postscript and Acrobat PDF - formats.</p> + available online in HTML format.</p> </li> <li> - <p>A <a href="http://8help.osu.edu/wks/sysadm_course/">UNIX + <p>A <a href="http://www.cs.duke.edu/csl/docs/sysadmin_course/">UNIX System Administration Course</a> from Ohio State University is available online in HTML format.</p> </li>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201112031201.pB3C1QD7004871>