From owner-p4-projects@FreeBSD.ORG Sun Mar 13 21:22:58 2011 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id C2D961065673; Sun, 13 Mar 2011 21:22:57 +0000 (UTC) Delivered-To: perforce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84676106566B for ; Sun, 13 Mar 2011 21:22:57 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from skunkworks.freebsd.org (skunkworks.freebsd.org [IPv6:2001:4f8:fff6::2d]) by mx1.freebsd.org (Postfix) with ESMTP id 700658FC08 for ; Sun, 13 Mar 2011 21:22:57 +0000 (UTC) Received: from skunkworks.freebsd.org (localhost [127.0.0.1]) by skunkworks.freebsd.org (8.14.4/8.14.4) with ESMTP id p2DLMvuw010524 for ; Sun, 13 Mar 2011 21:22:57 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by skunkworks.freebsd.org (8.14.4/8.14.4/Submit) id p2DLMvEO010521 for perforce@freebsd.org; Sun, 13 Mar 2011 21:22:57 GMT (envelope-from rene@FreeBSD.org) Date: Sun, 13 Mar 2011 21:22:57 GMT Message-Id: <201103132122.p2DLMvEO010521@skunkworks.freebsd.org> X-Authentication-Warning: skunkworks.freebsd.org: perforce set sender to rene@FreeBSD.org using -f From: Rene Ladan To: Perforce Change Reviews Precedence: bulk Cc: Subject: PERFORCE change 189992 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Mar 2011 21:22:58 -0000 http://p4web.freebsd.org/@@189992?ac=10 Change 189992 by rene@rene_acer on 2011/03/13 21:22:22 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#36 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#88 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#59 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/freebsd-update-server/article.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/portbuild/article.sgml#32 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/faq/book.sgml#33 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/disks/chapter.sgml#19 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/jails/chapter.sgml#8 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml#12 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml#37 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/security/chapter.sgml#16 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#102 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/captions/2006/mckusick-kernelinternals/mckusick-kernelinternals-1.sbv#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/captions/2009/asiabsdcon/allman-internetmail.sbv#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/captions/2009/asiabsdcon/rao-kernellocking-1.sbv#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/captions/2009/dcbsdcon/mckusick-historyofbsd.sbv#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/share/sgml/authors.ent#53 integrate .. //depot/projects/docproj_nl/share/sgml/freebsd-html.dsl#6 integrate .. //depot/projects/docproj_nl/share/sgml/freebsd.ent#21 integrate .. //depot/projects/docproj_nl/www/en/administration.sgml#18 integrate .. //depot/projects/docproj_nl/www/en/developers.sgml#52 integrate .. //depot/projects/docproj_nl/www/en/platforms/alpha.sgml#2 integrate .. //depot/projects/docproj_nl/www/en/platforms/ppc.sgml#6 integrate .. //depot/projects/docproj_nl/www/en/ports/categories#4 integrate .. //depot/projects/docproj_nl/www/en/support/webresources.sgml#2 integrate .. //depot/projects/docproj_nl/www/share/sgml/commercial.software.xml#11 integrate .. //depot/projects/docproj_nl/www/share/sgml/news.xml#104 integrate .. //depot/projects/docproj_nl/www/share/sgml/press.xml#22 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#36 (text+ko) ==== @@ -9,7 +9,7 @@ The &os; Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v 1.293 2011/02/22 10:27:25 ryusuke Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v 1.296 2011/03/12 18:11:05 gjb Exp $ 1999 @@ -1762,7 +1762,7 @@ A short guide about fixes which are committed to the &os; source tree after being detected by &coverity.prevent; and - analyzed by an &os; developer. + analyzed by a &os; developer. @@ -2803,11 +2803,42 @@ - How long is a ports freeze? + What is a ports slush or + feature freeze? + + + + During a release cycle the ports tree may be in a + slush state instead of in a hard freeze. + The goal during a slush is to reach a stable ports tree + to avoid rebuilding large sets of packages for the + release and to tag the tree. During this time + sweeping changes are prohibited unless + specifically permitted by portmgr. Complete details + about what qualifies as a sweeping change can be found + on the Portmgr + Implementation page. + + The benefit of a slush as opposed to a complete + freeze is that it allows maintainers to continue adding + new ports, making routine version updates, and bug fixes + to most existing ports, as long as the number of + affected ports is minimal. For example, updating the + shared library version on a port that many other ports + depend on. + + + + + + How long is a ports freeze or slush? - Usually a week or two. + A freeze only lasts long enough to tag the tree. + A slush usually lasts a week or two, but may last + longer. @@ -2817,7 +2848,7 @@ - During the ports freeze, you are not allowed to + During a ports freeze, you are not allowed to commit anything to the tree without explicit approval from the Ports Management Team. Explicit approval here means that you send a patch to @@ -2834,43 +2865,48 @@ Note that you do not have implicit permission to fix a port during the freeze just because it is broken. + + During a ports slush, you are still allowed to + commit but you must exercise more caution in what you + commit. Furthermore a special note (typically Feature + Safe: yes) must be added to the commit message. - How do I know when the ports freeze starts? + How do I know when the ports slush starts? - The ports management team will send out warning + The Ports Management Team will send out warning messages to the &a.ports; and &a.committers; announcing the start of the impending release, usually two or three weeks in advance. The exact starting time will not be determined until a few days before the - actual release. This is because the ports freeze has to + actual release. This is because the ports slush has to be synchronized with the release, and it is usually not known until then when exactly the release will be rolled. - When the freeze starts, there will be another + When the slush starts, there will be another announcement to the &a.ports; and &a.committers;, of course. - How do I know when the ports freeze ends? + How do I know when the freeze or slush ends? - A few hours after the release, the ports management team - will send out a mail to the &a.ports; and &a.committers; - announcing the end of the ports freeze. Note that the - release being cut does not automatically end the freeze. - We have to make sure there will not be any last minute - snafus that result in an immediate re-rolling of the - release. + A few hours after the release, the Ports Management + Team will send out a mail to the &a.ports; and &a.committers; + announcing the end of the ports freeze or slush. Note + that the release being cut does not automatically indicate + the end of the freeze. We have to make sure there will + be no last minute snafus that result in an immediate + re-rolling of the release. @@ -3190,7 +3226,7 @@ any file under a subdirectory that starts with an uppercase letter (Mk/, Tools/, etc.). In particular, the - ports management team is very protective of + Ports Management Team is very protective of ports/Mk/bsd.port*.mk so do not commit changes to those files unless you want to face his wra(i)th. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#88 (text+ko) ==== @@ -1,4 +1,4 @@ - + + - + In order for &fbus.ap; to work properly, updates for both the current release and the release one wants to upgrade to need to be built. This is necessary for determining the differences of files between releases. For example, when upgrading a &os; - system from version 7.1 to 7.2, updates will need to be built - for 7.1-RELEASE as well as for 7.2-RELEASE. - + system from 7.1-RELEASE to 7.2-RELEASE, updates will need to be built + and uploaded to your distribution server for both versions. + For reference, the entire run of init.sh is ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/portbuild/article.sgml#32 (text+ko) ==== @@ -11,7 +11,7 @@ The &os; Ports Management Team - $FreeBSD: doc/en_US.ISO8859-1/articles/portbuild/article.sgml,v 1.68 2011/02/26 00:58:15 linimon Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/portbuild/article.sgml,v 1.69 2011/03/08 04:07:59 linimon Exp $ 2003 @@ -1573,8 +1573,8 @@ different, machines, you will need to put those in the override directories.) - Recommended entries: -hostname="${hostname} + Recommended entries for physical nodes: +hostname="${hostname}" inetd_enable="YES" linux_enable="YES" nfs_client_enable="YES" @@ -1591,6 +1591,43 @@ squid_pidfile="/usr2/squid/logs/squid.pid" + + Required entries for VMWare-based nodes: +vmware_guest_vmmemctl_enable="YES" +vmware_guest_guestd_enable="YES" + + + + Recommended entries for VMWare-based nodes: +hostname="" +ifconfig_em0="DHCP" +fsck_y_enable="YES" + +inetd_enable="YES" +linux_enable="YES" +nfs_client_enable="YES" +sendmail_enable="NONE" +sshd_enable="YES" +sshd_program="/usr/local/sbin/sshd" + +gmond_enable="YES" +squid_enable="YES" +squid_chdir="/usr2/squid/logs" +squid_pidfile="/usr2/squid/logs/squid.pid" + + + + &man.ntpd.8; should not + be enabled for VMWare instances. + + Also, it may be possible to leave + squid disabled by default + so as to not have + /usr2 + persistent (which should save instantiation time.) + Work is still ongoing. + + ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/faq/book.sgml#33 (text+ko) ==== @@ -12,7 +12,7 @@ The &os; Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.1132 2011/01/15 12:51:40 jkois Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.1133 2011/03/08 09:42:08 danger Exp $ 1995 @@ -31,6 +31,7 @@ 2008 2009 2010 + 2011 The &os; Documentation Project @@ -6319,7 +6320,7 @@ Single User mode, it means that the console has been marked as insecure in /etc/ttys. In this case it will be - required to boot from an &os; installation disk, choose + required to boot from a &os; installation disk, choose the Fixit shell from &man.sysinstall.8; and issue the commands mentioned above. @@ -6329,7 +6330,7 @@ If you cannot mount your root partition from Single User mode, it is possible that the partitions are encrypted and it is impossible to mount them without the - access keys. Your chances are depending on the chosen + access keys. Your chances depend on the chosen implementation. For more information see the section about encrypted disks in the &os; Handbook. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/disks/chapter.sgml#19 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -4065,7 +4065,7 @@ How to integrate CARP and - &man.devd.8;; to build a robust storage system. + &man.devd.8; to build a robust storage system. @@ -4297,11 +4297,11 @@ resource test { on hasta { local /dev/ad6 - remote 172.16.0.1 + remote 172.16.0.2 } on hastb { local /dev/ad6 - remote 172.16.0.2 + remote 172.16.0.1 } } @@ -4540,7 +4540,7 @@ # Switch roles for the HAST resources for disk in ${resources}; do - if ! mount | grep -q "^${disk} on " + if ! mount | grep -q "^/dev/hast/${disk} on " then else umount -f /hast/${disk} ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/jails/chapter.sgml#8 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -119,7 +119,7 @@ hosted (system, process, user, etc.) A process, user or other entity, whose access to resources is - restricted by an &os; jail. + restricted by a &os; jail. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml#12 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -266,6 +266,11 @@ building / installing + + It is required to have the full &os; source tree installed + to build the kernel. + + First, let us take a quick tour of the kernel build directory. All directories mentioned will be relative to the main /usr/src/sys directory, which is also @@ -287,35 +292,26 @@ directory structure, with each supported device, file system, and option in its own subdirectory. - This chapter assumes that you are using the i386 architecture - in the examples. If this is not the case for your situation, - make appropriate adjustments to the path names for your system's - architecture. + The examples in this chapter assume that you are using the i386 + architecture. If your system has a different architecture you need + to change the path names accordingly. - If there is not a - /usr/src/sys directory on your system, - then the kernel source has not been installed. The easiest - way to do this is by running - sysinstall as - root, choosing + If the directory /usr/src/ does not + exist on your system (or if it is empty), then the sources have + not been installed. The easiest way to install the full source + tree is is to run sysinstall as + root, and then choosing Configure, then Distributions, then - src, then - base and - sys. If you have an aversion to - sysinstall and you have access to - an official &os; CDROM, then you can also - install the source from the command line: + src, and finally + All. If it does not exist, you should + also create a symlink to /usr/src/sys/: - &prompt.root; mount /cdrom -&prompt.root; mkdir -p /usr/src/sys -&prompt.root; ln -s /usr/src/sys /sys -&prompt.root; cat /cdrom/src/ssys.[a-d]* | tar -xzvf - -&prompt.root; cat /cdrom/src/sbase.[a-d]* | tar -xzvf - + &prompt.root; ln -s /usr/src/sys/ /sys/ - Next, move to the + Next, change to the arch/conf directory and copy the GENERIC configuration file to the name you want to give your kernel. For example: @@ -392,6 +388,11 @@ Building a Kernel + + It is required to have the full &os; source tree installed + to build the kernel. + + Change to the /usr/src directory: @@ -412,11 +413,6 @@ - - It is required to have full &os; source tree to build the - kernel. - - By default, when you build a custom kernel, all kernel modules will be rebuilt as well. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml#37 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -1748,15 +1748,6 @@ - ports-mbone - release=cvs - - - MBone applications. - - - - ports-misc release=cvs @@ -2754,6 +2745,14 @@ + RELENG_8_2_0_RELEASE + + + &os; 8.2 + + + + RELENG_8_1_0_RELEASE @@ -2770,6 +2769,14 @@ + RELENG_7_4_0_RELEASE + + + &os; 7.4 + + + + RELENG_7_3_0_RELEASE ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/security/chapter.sgml#16 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -608,7 +608,7 @@ and the value of the kern_securelevel variable to the desired secure level. - The default secure level of an &os; system right after the startup + The default secure level of a &os; system right after the startup scripts are done is -1. This is called insecure mode because immutable file flags may be turned off, all devices may be read from or written to, and so on. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#102 (text+ko) ==== @@ -1,7 +1,7 @@ - mbone + mbone* MBone applications. @@ -2027,7 +2027,7 @@ editors, not the other way around. Also, you should not list net when the port belongs to any of irc, mail, - mbone, news, + news, security, or www, as net is included implicitly. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/captions/2006/mckusick-kernelinternals/mckusick-kernelinternals-1.sbv#2 (text+ko) ==== @@ -1445,7 +1445,7 @@ rather than just a straight 0:21:19.440,0:21:22.440 -iteration of what the the actual protocols +iteration of what the actual protocols are 0:21:22.440,0:21:24.940 @@ -2727,7 +2727,7 @@ 0:38:54.940,0:38:59.579 was you'd have to break into these steps. well -I need to run the the preprocessor +I need to run the preprocessor 0:38:59.579,0:39:04.670 and so clean out whatever gump that was left ==== //depot/projects/docproj_nl/en_US.ISO8859-1/captions/2009/asiabsdcon/allman-internetmail.sbv#3 (text+ko) ==== @@ -323,7 +323,7 @@ 0:05:22.849,0:05:27.929 they're interacting doing screen sharing -over the the internet, they're showing off the mouse for +over the internet, they're showing off the mouse for 0:05:27.929,0:05:30.380 the first time that nobody's ever seen @@ -1105,7 +1105,7 @@ Norway 0:16:51.030,0:16:54.589 -and so the the network had gone international +and so the network had gone international 0:16:54.589,0:16:55.450 sort of @@ -1538,7 +1538,7 @@ pretty much 0:23:16.870,0:23:20.880 -toward the end of the the Arpanet era +toward the end of the Arpanet era 0:23:20.880,0:23:22.520 the Arpanet @@ -2121,7 +2121,7 @@ that effectively said 0:32:18.670,0:32:23.830 -you can't use the the internet for commercial +you can't use the internet for commercial purposes at all 0:32:23.830,0:32:24.649 ==== //depot/projects/docproj_nl/en_US.ISO8859-1/captions/2009/asiabsdcon/rao-kernellocking-1.sbv#2 (text+ko) ==== @@ -431,7 +431,7 @@ a very huge step forward in this direction 0:07:12.319,0:07:18.599 -really the the SMPng has been considered closed around the end of +really the SMPng has been considered closed around the end of 0:07:18.599,0:07:20.600 2007 @@ -1847,7 +1847,7 @@ Msleep should be dropped off but they have avery nice feature which 0:30:56.220,0:31:02.669 -is the the possibility to specify a wake up priority on the sleeping threads +is the possibility to specify a wake up priority on the sleeping threads 0:31:02.669,0:31:04.740 once they are asleep ==== //depot/projects/docproj_nl/en_US.ISO8859-1/captions/2009/dcbsdcon/mckusick-historyofbsd.sbv#2 (text+ko) ==== @@ -40,7 +40,7 @@ 0:00:43.819,0:00:47.210 I'll just do quickly and then I'll concentrate -on the the one +on the one 0:00:47.210,0:00:48.010 piece that @@ -1875,7 +1875,7 @@ 0:25:44.420,0:25:49.500 Uh and he took 4.1c with him to get it -ported on to the the SUN hardware. +ported on to the SUN hardware. 0:25:49.500,0:25:51.300 and @@ -1884,7 +1884,7 @@ with this sort uh of hit 0:25:54.240,0:25:55.910 -on the the main developer +on the main developer 0:25:55.910,0:26:00.510 uh we decided that rather than trying up to get @@ -2695,7 +2695,7 @@ uh that had 0:36:56.150,0:36:59.809 -well the the class ABC type of subnets +well the class ABC type of subnets not 0:36:59.809,0:37:01.319 @@ -3450,7 +3450,7 @@ At any rate 0:47:18.679,0:47:21.629 -we eventually win the the lawsuit +we eventually win the lawsuit 0:47:21.629,0:47:26.089 And uh and we don't win it we settle the @@ -3654,7 +3654,7 @@ was 0:50:01.689,0:50:04.759 -uh the the stuff that SUN had done +uh the stuff that SUN had done 0:50:04.759,0:50:10.109 and the other was the stuff that had been done at @@ -3707,7 +3707,7 @@ 0:50:47.140,0:50:51.549 so it really got to the point where it -is needed to be signed off by the the SUN +is needed to be signed off by the SUN 0:50:51.549,0:50:52.429 lawyers @@ -3832,7 +3832,7 @@ and so got that put in and of course we 0:52:34.359,0:52:40.019 -did it onto the the Berkeley MMAP Interface +did it onto the Berkeley MMAP Interface rather than what they did 0:52:40.019,0:52:42.700 ==== //depot/projects/docproj_nl/en_US.ISO8859-1/share/sgml/authors.ent#53 (text+ko) ==== @@ -13,7 +13,7 @@ builds for the other languages, and we will poke fun of you in public. - $FreeBSD: doc/en_US.ISO8859-1/share/sgml/authors.ent,v 1.534 2011/03/05 23:06:43 kargl Exp $ + $FreeBSD: doc/en_US.ISO8859-1/share/sgml/authors.ent,v 1.535 2011/03/13 16:42:37 pawel Exp $ --> aaron@FreeBSD.org"> @@ -904,6 +904,8 @@ pav@FreeBSD.org"> +pawel@FreeBSD.org"> + pb@FreeBSD.org"> pdeuskar@FreeBSD.org"> ==== //depot/projects/docproj_nl/share/sgml/freebsd-html.dsl#6 (text+ko) ==== @@ -1,4 +1,4 @@ - + @@ -201,9 +201,9 @@ (("current") (string-append u "&" "amp;" "manpath=FreeBSD+9-current")) (("xfree86") (string-append u "&" "amp;" "manpath=XFree86+4.7.0")) (("xorg") (string-append u "&" "amp;" "manpath=X11R7.4")) - (("netbsd") (string-append u "&" "amp;" "manpath=NetBSD+5.0")) + (("netbsd") (string-append u "&" "amp;" "manpath=NetBSD+5.1")) (("openbsd") (string-append u "&" "amp;" "manpath=OpenBSD+4.7")) - (("ports") (string-append u "&" "amp;" "manpath=FreeBSD+8.1-RELEASE+and+Ports")) + (("ports") (string-append u "&" "amp;" "manpath=FreeBSD+8.2-RELEASE+and+Ports")) (else u)))) (element application ($bold-seq$)) ==== //depot/projects/docproj_nl/share/sgml/freebsd.ent#21 (text+ko) ==== @@ -1,7 +1,7 @@ - + @@ -66,7 +66,7 @@ - + ==== //depot/projects/docproj_nl/www/en/administration.sgml#18 (text+ko) ==== @@ -1,5 +1,5 @@ + %developers; @@ -131,13 +131,14 @@ Team in greater detail.

==== //depot/projects/docproj_nl/www/en/developers.sgml#52 (text+ko) ==== @@ -6,7 +6,7 @@ us to update author names, or the representation of those names (such as adding email addresses), by just editing a single file. -$FreeBSD: www/en/developers.sgml,v 1.276 2011/03/05 23:08:13 kargl Exp $ +$FreeBSD: www/en/developers.sgml,v 1.277 2011/03/13 16:47:13 pawel Exp $ --> @@ -451,6 +451,7 @@ + ==== //depot/projects/docproj_nl/www/en/platforms/alpha.sgml#2 (text+ko) ==== @@ -1,6 +1,6 @@ - + @@ -10,9 +10,7 @@ &header;

This page contains information about porting FreeBSD to HP/Compaq Alpha - systems. Discussion of the Alpha port takes place on the freebsd-alpha - mailing list.

+ systems.

Status

@@ -21,15 +19,17 @@ the hardware vendor; this combined with the widespread deployment of more mainstream 64-bit platforms, such as the AMD64 and Intel EM64T architectures, has resulted in significantly reduced user and developer - community interest. FreeBSD/alpha support will continue in maintenance - mode for future FreeBSD 6.x releases.

+ community interest.

-

FreeBSD/alpha mailing list

+

FreeBSD/alpha mailing list

-

To subscribe to this list, send an email to - or visit the mailman interface.

+

Because of the dropped support for the Alpha plattform the mailing list + freebsd-alpha has been closed. Although it is no + longer possible to send messages to this mailing list, the archives can + still be searched + or browsed.

Other Links of Interest

==== //depot/projects/docproj_nl/www/en/platforms/ppc.sgml#6 (text+ko) ==== @@ -1,6 +1,6 @@ - + @@ -70,7 +70,7 @@

How to use ports on FreeBSD/ppc?

-

The easy way to use ports on FreeBSD since 6.0-RELEASE is to use portsnap. +

The easy way to use ports on FreeBSD is to use portsnap. Refer to the Handbook if you need assistance to use the Ports Collection.

==== //depot/projects/docproj_nl/www/en/ports/categories#4 (text+ko) ==== @@ -1,5 +1,5 @@ #Originally from src/release/sysinstall/index.c,v 1.57 1998/10/15 -#$FreeBSD: www/en/ports/categories,v 1.40 2010/09/29 20:54:50 pav Exp $ +#$FreeBSD: www/en/ports/categories,v 1.41 2011/03/06 22:43:05 pav Exp $ # See categories.descriptions for the meaning of the abbrevations at the # end of each category. @@ -50,7 +50,7 @@ lisp,"Things related to pure lisp.",VC mail,"Electronic mail packages and utilities.",CCATI math,"Mathematical computation software.",SAE -mbone,"Applications and utilities for the MBONE.",CCATI +mbone,"Applications and utilities for the MBONE.",VC misc,"Miscellaneous utilities.",AOP multimedia,"Multimedia software.",EU net,"Networking utilities.",CCATI ==== //depot/projects/docproj_nl/www/en/support/webresources.sgml#2 (text+ko) ==== @@ -1,6 +1,6 @@ - + >>> TRUNCATED FOR MAIL (1000 lines) <<<