From owner-svn-doc-all@FreeBSD.ORG Thu Jan 17 01:06:40 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E4058617; Thu, 17 Jan 2013 01:06:40 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id D452ECF4; Thu, 17 Jan 2013 01:06:40 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0H16eoe031916; Thu, 17 Jan 2013 01:06:40 GMT (envelope-from gjb@svn.freebsd.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0H16e0Z031915; Thu, 17 Jan 2013 01:06:40 GMT (envelope-from gjb@svn.freebsd.org) Message-Id: <201301170106.r0H16e0Z031915@svn.freebsd.org> From: Glen Barber Date: Thu, 17 Jan 2013 01:06:40 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40661 - head/en_US.ISO8859-1/books/handbook/eresources X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2013 01:06:41 -0000 Author: gjb Date: Thu Jan 17 01:06:40 2013 New Revision: 40661 URL: http://svnweb.freebsd.org/changeset/doc/40661 Log: Style/whitespace fixes for the eresources chapter. Translators please ignore. Submitted by: Dru Lavigne (via -doc, original) Modified: head/en_US.ISO8859-1/books/handbook/eresources/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/eresources/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/eresources/chapter.xml Thu Jan 17 00:21:13 2013 (r40660) +++ head/en_US.ISO8859-1/books/handbook/eresources/chapter.xml Thu Jan 17 01:06:40 2013 (r40661) @@ -8,18 +8,19 @@ Resources on the Internet - The rapid pace of FreeBSD progress makes print media impractical as a - means of following the latest developments. Electronic resources are the - best, if not often the only, way to stay informed of the latest advances. - Since FreeBSD is a volunteer effort, the user community itself also - generally serves as a technical support department of sorts, - with electronic mail, web forums, and USENET news being the most + The rapid pace of FreeBSD progress makes print media + impractical as a means of following the latest developments. + Electronic resources are the best, if not often the only, way + to stay informed of the latest advances. Since FreeBSD is a + volunteer effort, the user community itself also generally serves + as a technical support department of sorts, with + electronic mail, web forums, and USENET news being the most effective way of reaching that community. - The most important points of contact with the FreeBSD user community - are outlined below. If you are aware of other resources not mentioned - here, please send them to the &a.doc; so that they may also be - included. + The most important points of contact with the FreeBSD user + community are outlined below. If you are aware of other resources + not mentioned here, please send them to the &a.doc; so that they + may also be included. Mailing Lists @@ -31,45 +32,50 @@ most appropriate mailing list will invariably assure a faster and more accurate response. - The charters for the various lists are given at the bottom of this - document. Please read the charter before joining or sending - mail to any list. Most of our list subscribers now receive - many hundreds of FreeBSD related messages every day, and by setting down - charters and rules for proper use we are striving to keep the - signal-to-noise ratio of the lists high. To do less would see the - mailing lists ultimately fail as an effective communications medium for - the project. + The charters for the various lists are given at the bottom + of this document. Please read the charter before + joining or sending mail to any list. Most of our + list subscribers now receive many hundreds of FreeBSD related + messages every day, and by setting down charters and rules for + proper use we are striving to keep the signal-to-noise ratio + of the lists high. To do less would see the mailing lists + ultimately fail as an effective communications medium for the + project. If you wish to test your ability to send to - &os; lists, send a test message to &a.test.name;. + &os; lists, send a test message to &a.test.name;. Please do not send test messages to any other list. - When in doubt about what list to post a question to, see How to get best results from - the FreeBSD-questions mailing list. - - Before posting to any list, please learn about how to best use - the mailing lists, such as how to help avoid frequently-repeated - discussions, by reading the - Mailing List Frequently Asked Questions (FAQ) document. - - Archives are kept for all of the mailing lists and can be searched - using the FreeBSD World - Wide Web server. The keyword searchable archive offers an - excellent way of finding answers to frequently asked questions and - should be consulted before posting a question. Note that this - also means that messages sent to FreeBSD mailing lists are - archived in perpetuity. When protecting privacy is a - concern, consider using a disposable secondary email address and - posting only public information. + When in doubt about what list to post a question to, see + How to get best + results from the FreeBSD-questions mailing + list. + + Before posting to any list, please learn about how to + best use the mailing lists, such as how to help avoid + frequently-repeated discussions, by reading the Mailing List Frequently + Asked Questions (FAQ) document. + + Archives are kept for all of the mailing lists and can be + searched using the FreeBSD World Wide Web + server. The keyword searchable archive offers an + excellent way of finding answers to frequently asked questions + and should be consulted before posting a question. Note that + this also means that messages sent to FreeBSD mailing lists + are archived in perpetuity. When protecting privacy is a + concern, consider using a disposable secondary email address + and posting only public information. List Summary - General lists: The following are general - lists which anyone is free (and encouraged) to join: + General lists: The following are + general lists which anyone is free (and encouraged) to + join: @@ -98,11 +104,12 @@ &a.bugbusters.name; - Discussions pertaining to the maintenance of the FreeBSD - problem report database and related tools + Discussions pertaining to the maintenance of + the FreeBSD problem report database and related + tools - + &a.bugs.name; Bug reports @@ -154,17 +161,18 @@ &a.test.name; - Where to send your test messages instead of one of - the actual lists + Where to send your test messages instead of + one of the actual lists - Technical lists: The following lists are for - technical discussion. You should read the charter for each list - carefully before joining or sending mail to one as there are firm - guidelines for their use and content. + Technical lists: The following + lists are for technical discussion. You should read the + charter for each list carefully before joining or sending + mail to one as there are firm guidelines for their use and + content. @@ -188,7 +196,8 @@ &a.aic7xxx.name; - Developing drivers for the &adaptec; AIC 7xxx + Developing drivers for the &adaptec; + AIC 7xxx @@ -198,7 +207,9 @@ &a.apache.name; - Discussion about Apache related ports + Discussion about + Apache related + ports @@ -250,7 +261,7 @@ &a.eclipse.name; FreeBSD users of Eclipse IDE, tools, rich client - applications and ports. + applications and ports. @@ -283,17 +294,20 @@ &a.gecko.name; - Gecko Rendering Engine issues + Gecko Rendering + Engine issues &a.geom.name; - GEOM-specific discussions and implementations + GEOM-specific discussions and + implementations &a.gnome.name; - Porting GNOME and GNOME applications + Porting GNOME and + GNOME applications @@ -314,12 +328,14 @@ &a.ia32.name; - FreeBSD on the IA-32 (&intel; x86) platform + FreeBSD on the IA-32 (&intel; x86) + platform &a.ia64.name; - Porting FreeBSD to &intel;'s upcoming IA64 systems + Porting FreeBSD to &intel;'s upcoming IA64 + systems @@ -329,8 +345,8 @@ &a.ipfw.name; - Technical discussion concerning the redesign of the IP - firewall code + Technical discussion concerning the redesign + of the IP firewall code @@ -340,7 +356,8 @@ &a.jail.name; - Discussion about the &man.jail.8; facility + Discussion about the &man.jail.8; + facility @@ -351,7 +368,8 @@ &a.kde.name; - Porting KDE and KDE applications + Porting KDE and + KDE applications @@ -376,7 +394,8 @@ &a.mozilla.name; - Porting Mozilla to FreeBSD + Porting Mozilla to + FreeBSD @@ -386,17 +405,20 @@ &a.newbus.name; - Technical discussions about bus architecture + Technical discussions about bus + architecture &a.net.name; - Networking discussion and TCP/IP source code + Networking discussion and TCP/IP source + code &a.numerics.name; - Discussions of high quality implementation of libm functions + Discussions of high quality implementation of + libm functions @@ -435,7 +457,8 @@ &a.ports-announce.name; - Important news and instructions about the Ports Collection + Important news and instructions about the Ports + Collection @@ -450,7 +473,8 @@ &a.proliant.name; - Technical discussion of FreeBSD on HP ProLiant server platforms + Technical discussion of FreeBSD on HP ProLiant + server platforms @@ -460,12 +484,15 @@ &a.rc.name; - Discussion related to the rc.d system and its development + Discussion related to the + rc.d system and its + development &a.realtime.name; - Development of realtime extensions to FreeBSD + Development of realtime extensions to + FreeBSD @@ -522,7 +549,8 @@ &a.tilera.name; - Porting FreeBSD to the Tilera family of CPUs + Porting FreeBSD to the Tilera family of + CPUs @@ -532,7 +560,8 @@ &a.toolchain.name; - Maintenance of &os;'s integrated toolchain + Maintenance of &os;'s integrated + toolchain @@ -542,8 +571,8 @@ &a.virtualization.name; - Discussion of various virtualization techniques supported - by &os; + Discussion of various virtualization techniques + supported by &os; @@ -558,12 +587,14 @@ &a.xen.name; - Discussion of the &os; port to &xen; — implementation and usage + Discussion of the &os; port to &xen; — + implementation and usage &a.xfce.name; - XFCE for &os; — porting and maintaining + XFCE for &os; — + porting and maintaining @@ -575,11 +606,12 @@ - Limited lists: The following lists are for - more specialized (and demanding) audiences and are probably not of - interest to the general public. It is also a good idea to establish a - presence in the technical lists before joining one of these limited - lists so that you will understand the communications etiquette involved. + Limited lists: The following lists + are for more specialized (and demanding) audiences and are + probably not of interest to the general public. It is also + a good idea to establish a presence in the technical lists + before joining one of these limited lists so that you will + understand the communications etiquette involved. @@ -620,7 +652,9 @@ &a.www.name; - Maintainers of www.FreeBSD.org + Maintainers of + www.FreeBSD.org @@ -632,10 +666,10 @@ section. SVN lists: The following lists - are for people interested in seeing the log messages for changes to - various areas of the source tree. They are - Read-Only lists and should not have mail sent to - them. + are for people interested in seeing the log messages for + changes to various areas of the source tree. They are + Read-Only lists and should not have + mail sent to them. @@ -651,10 +685,10 @@ &a.svn-doc-all.name; /usr/doc - All changes to the doc Subversion repository (except - for user, - projects - and translations) + All changes to the doc Subversion repository + (except for user, + projects + and translations) @@ -682,14 +716,15 @@ &a.svn-ports-all.name; /usr/ports - All changes to the ports Subversion repository + All changes to the ports Subversion + repository &a.svn-ports-head.name; /usr/ports - All changes to the head branch of - the ports Subversion repository + All changes to the head branch + of the ports Subversion repository @@ -703,16 +738,16 @@ &a.svn-src-all.name; /usr/src - All changes to the src Subversion repository (except - for user + All changes to the src Subversion repository + (except for user and projects) &a.svn-src-head.name; /usr/src - All changes to the head branch of - the src Subversion repository (the &os;-CURRENT + All changes to the head branch + of the src Subversion repository (the &os;-CURRENT branch) @@ -812,85 +847,90 @@ How to Subscribe To subscribe to a list, click on the list name above or - go to &a.mailman.lists.link; - and click on the list that you are interested in. The list - page should contain all of the necessary subscription - instructions. + go to &a.mailman.lists.link; and click on the list that you + are interested in. The list page should contain all of the + necessary subscription instructions. To actually post to a given list, send mail to - listname@FreeBSD.org. It will then - be redistributed to mailing list members world-wide. + listname@FreeBSD.org. + It will then be redistributed to mailing list members + world-wide. To unsubscribe yourself from a list, click on the URL - found at the bottom of every email received from the list. It - is also possible to send an email to - listname-unsubscribe@FreeBSD.org to unsubscribe - yourself. - - Again, we would like to request that you keep discussion in the - technical mailing lists on a technical track. If you are only - interested in important announcements then it is suggested that - you join the &a.announce;, which is intended only for infrequent - traffic. + found at the bottom of every email received from the list. + It is also possible to send an email to + listname-unsubscribe@FreeBSD.org + to unsubscribe yourself. + + Again, we would like to request that you keep discussion + in the technical mailing lists on a technical track. If you + are only interested in important announcements then it is + suggested that you join the &a.announce;, which is intended + only for infrequent traffic. List Charters - All FreeBSD mailing lists have certain basic - rules which must be adhered to by anyone using them. Failure to comply - with these guidelines will result in two (2) written warnings from the - FreeBSD Postmaster postmaster@FreeBSD.org, after which, - on a third offense, the poster will removed from all FreeBSD mailing - lists and filtered from further posting to them. We regret that such - rules and measures are necessary at all, but today's Internet is a - pretty harsh environment, it would seem, and many fail to appreciate - just how fragile some of its mechanisms are. + All FreeBSD mailing lists have + certain basic rules which must be adhered to by anyone using + them. Failure to comply with these guidelines will result + in two (2) written warnings from the FreeBSD Postmaster + postmaster@FreeBSD.org, after which, on a + third offense, the poster will removed from all FreeBSD + mailing lists and filtered from further posting to them. We + regret that such rules and measures are necessary at all, + but today's Internet is a pretty harsh environment, it would + seem, and many fail to appreciate just how fragile some of + its mechanisms are. Rules of the road: - The topic of any posting should adhere to the basic charter of - the list it is posted to, e.g., if the list is about technical - issues then your posting should contain technical discussion. - Ongoing irrelevant chatter or flaming only detracts from the value - of the mailing list for everyone on it and will not be tolerated. - For free-form discussion on no particular topic, the &a.chat; + The topic of any posting should adhere to the basic + charter of the list it is posted to, e.g., if the list + is about technical issues then your posting should contain + technical discussion. Ongoing irrelevant chatter or + flaming only detracts from the value of the mailing list + for everyone on it and will not be tolerated. For + free-form discussion on no particular topic, the &a.chat; is freely available and should be used instead. - No posting should be made to more than 2 mailing lists, and - only to 2 when a clear and obvious need to post to both lists - exists. For most lists, there is already a great deal of - subscriber overlap and except for the most esoteric mixes (say - -stable & -scsi), there really is no reason to post to more - than one list at a time. If a message is sent to you in such a - way that multiple mailing lists appear on the - Cc line then the Cc - line should also be trimmed before sending it out again. - You are still responsible for your - own cross-postings, no matter who the originator might have - been. + No posting should be made to more than 2 mailing + lists, and only to 2 when a clear and obvious need to post + to both lists exists. For most lists, there is already + a great deal of subscriber overlap and except for the most + esoteric mixes (say -stable & -scsi), + there really is no reason to post to more than one list at + a time. If a message is sent to you in such a way that + multiple mailing lists appear on the Cc + line then the Cc line should also be + trimmed before sending it out again. You are + still responsible for your own cross-postings, no matter + who the originator might have been. - Personal attacks and profanity (in the context of an argument) - are not allowed, and that includes users and developers alike. - Gross breaches of netiquette, like excerpting or reposting private - mail when permission to do so was not and would not be - forthcoming, are frowned upon but not specifically enforced. - However, there are also very few cases where - such content would fit within the charter of a list and it would - therefore probably rate a warning (or ban) on that basis - alone. + Personal attacks and profanity (in the context of + an argument) are not allowed, and that includes users + and developers alike. Gross breaches of netiquette, + like excerpting or reposting private mail when permission + to do so was not and would not be forthcoming, are frowned + upon but not specifically enforced. + However, there are also very few + cases where such content would fit within the charter + of a list and it would therefore probably rate a warning + (or ban) on that basis alone. - Advertising of non-FreeBSD related products or services is - strictly prohibited and will result in an immediate ban if it is - clear that the offender is advertising by spam. + Advertising of non-FreeBSD related products or + services is strictly prohibited and will result in an + immediate ban if it is clear that the offender is + advertising by spam. @@ -903,7 +943,7 @@ ACPI and power management - development + development @@ -913,8 +953,8 @@ Andrew File System - This list is for discussion on porting and using AFS from - CMU/Transarc + This list is for discussion on porting and using + AFS from CMU/Transarc @@ -922,13 +962,15 @@ &a.announce.name; - Important events / milestones + Important events / + milestones - This is the mailing list for people interested only in - occasional announcements of significant FreeBSD events. This - includes announcements about snapshots and other releases. It - contains announcements of new FreeBSD capabilities. It may - contain calls for volunteers etc. This is a low volume, strictly + This is the mailing list for people interested + only in occasional announcements of significant FreeBSD + events. This includes announcements about snapshots + and other releases. It contains announcements of new + FreeBSD capabilities. It may contain calls for + volunteers etc. This is a low volume, strictly moderated mailing list. @@ -940,7 +982,7 @@ Architecture and design discussions - This list is for discussion of the FreeBSD + This list is for discussion of the FreeBSD architecture. Messages will mostly be kept strictly technical in nature. Examples of suitable topics are: @@ -952,14 +994,14 @@ - What needs to be fixed with VFS to make Heidemann layers - work. - + What needs to be fixed with VFS to make + Heidemann layers work. + - How do we change the device driver interface to be able - to use the same drivers cleanly on many buses and - architectures. + How do we change the device driver interface + to be able to use the same drivers cleanly on many + buses and architectures. @@ -976,10 +1018,10 @@ &bluetooth; in FreeBSD This is the forum where FreeBSD's &bluetooth; users - congregate. Design issues, implementation details, - patches, bug reports, status reports, feature requests, - and all matters related to &bluetooth; are fair - game. + congregate. Design issues, implementation details, + patches, bug reports, status reports, feature requests, + and all matters related to &bluetooth; are fair + game. @@ -987,12 +1029,14 @@ &a.bugbusters.name; - Coordination of the Problem Report handling effort + Coordination of the Problem Report + handling effort - The purpose of this list is to serve as a coordination and - discussion forum for the Bugmeister, his Bugbusters, and any other - parties who have a genuine interest in the PR database. This list - is not for discussions about specific bugs, patches or PRs. + The purpose of this list is to serve as a + coordination and discussion forum for the Bugmeister, + his Bugbusters, and any other parties who have a genuine + interest in the PR database. This list is not for + discussions about specific bugs, patches or PRs. @@ -1002,10 +1046,9 @@ Bug reports - This is the mailing list for reporting bugs in FreeBSD. - Whenever possible, bugs should be submitted using the - &man.send-pr.1; - command or the This is the mailing list for reporting bugs in + FreeBSD. Whenever possible, bugs should be submitted + using the &man.send-pr.1; command or the WEB interface to it. @@ -1018,15 +1061,16 @@ Non technical items related to the FreeBSD community - This list contains the overflow from the other lists about - non-technical, social information. It includes discussion about - whether Jordan looks like a toon ferret or not, whether or not - to type in capitals, who is drinking too much coffee, where the - best beer is brewed, who is brewing beer in their basement, and - so on. Occasional announcements of important events (such as - upcoming parties, weddings, births, new jobs, etc) can be made - to the technical lists, but the follow ups should be directed to - this -chat list. + This list contains the overflow from the other + lists about non-technical, social information. It + includes discussion about whether Jordan looks like a + toon ferret or not, whether or not to type in capitals, + who is drinking too much coffee, where the best beer + is brewed, who is brewing beer in their basement, and + so on. Occasional announcements of important events + (such as upcoming parties, weddings, births, new jobs, + etc) can be made to the technical lists, but the follow + ups should be directed to this -chat list. @@ -1034,11 +1078,12 @@ &a.chromium.name; - FreeBSD-specific Chromium issues + FreeBSD-specific Chromium + issues This is a list for the discussion of Chromium - support for FreeBSD. This is a technical list to discuss - development and installation of Chromium. + support for FreeBSD. This is a technical list to + discuss development and installation of Chromium. @@ -1050,8 +1095,8 @@ This is an internal mailing list for use by the core members. Messages can be sent to it when a serious - FreeBSD-related matter requires arbitration or high-level - scrutiny. + FreeBSD-related matter requires arbitration or + high-level scrutiny. @@ -1062,12 +1107,13 @@ Discussions about the use of &os.current; - This is the mailing list for users of &os.current;. It - includes warnings about new features coming out in -CURRENT that - will affect the users, and instructions on steps that must be - taken to remain -CURRENT. Anyone running CURRENT - must subscribe to this list. This is a technical mailing list - for which strictly technical content is expected. + This is the mailing list for users of &os.current;. + It includes warnings about new features coming out in + -CURRENT that will affect the users, and instructions + on steps that must be taken to remain -CURRENT. Anyone + running CURRENT must subscribe to this + list. This is a technical mailing list for which + strictly technical content is expected. @@ -1077,8 +1123,8 @@ FreeBSD CVSweb Project - Technical discussions about use, development and maintenance - of FreeBSD-CVSweb. + Technical discussions about use, development and + maintenance of FreeBSD-CVSweb. @@ -1086,7 +1132,8 @@ &a.desktop.name; - Using and improving &os; on the desktop + Using and improving &os; on the + desktop This is a forum for discussion of &os; on the desktop. It is primarily a place for desktop porters @@ -1101,11 +1148,12 @@ Documentation project - This mailing list is for the discussion of issues and - projects related to the creation of documentation for FreeBSD. - The members of this mailing list are collectively referred to as - The FreeBSD Documentation Project. It is an open - list; feel free to join and contribute! + This mailing list is for the discussion of issues + and projects related to the creation of documentation + for FreeBSD. The members of this mailing list are + collectively referred to as The FreeBSD + Documentation Project. It is an open list; + feel free to join and contribute! @@ -1113,13 +1161,14 @@ &a.drivers.name; - Writing device drivers for &os; + Writing device drivers for + &os; - This is a forum for technical discussions related to - device drivers on &os;. It is primarily a place - for device driver writers to ask questions about - how to write device drivers using the APIs in the - &os; kernel. + This is a forum for technical discussions related + to device drivers on &os;. It is primarily a place + for device driver writers to ask questions about how + to write device drivers using the APIs in the &os; + kernel. @@ -1128,7 +1177,7 @@ &os; users of Eclipse IDE, tools, rich - client applications and ports. + client applications and ports. The intention of this list is to provide mutual support for everything to do with choosing, installing, @@ -1144,8 +1193,7 @@ Although this list is focused primarily on the needs of Eclipse users it will also provide a forum for those who would like to develop &os; specific applications - using the Eclipse framework. - + using the Eclipse framework. @@ -1154,18 +1202,19 @@ Using FreeBSD in embedded - applications + applications - This list discusses topics related to using FreeBSD in - embedded systems. This is a technical mailing list for which - strictly technical content is expected. For the purpose of - this list we define embedded systems as those computing - devices which are not desktops and which usually serve a - single purpose as opposed to being general computing - environments. Examples include, but are not limited to, - all kinds of phone handsets, network equipment such as - routers, switches and PBXs, remote measuring equipment, - PDAs, Point Of Sale systems, and so on. + This list discusses topics related to using FreeBSD + in embedded systems. This is a technical mailing list + for which strictly technical content is expected. For + the purpose of this list we define embedded systems as + those computing devices which are not desktops and which + usually serve a single purpose as opposed to being + general computing environments. Examples include, but + are not limited to, all kinds of phone handsets, network + equipment such as routers, switches and PBXs, remote + measuring equipment, PDAs, Point Of Sale systems, and + so on. @@ -1176,9 +1225,9 @@ Emulation of other systems such as Linux/&ms-dos;/&windows; - This is a forum for technical discussions related to - running programs written for other operating systems on &os;. - + This is a forum for technical discussions related + to running programs written for other operating systems + on &os;. @@ -1186,13 +1235,15 @@ &a.eol.name; - Peer support of FreeBSD-related software that is - no longer supported by the FreeBSD project. - - This list is for those interested in providing or making use - of peer support of FreeBSD-related software for which the - FreeBSD project no longer provides official support (e.g., in - the form of security advisories and patches). + Peer support of FreeBSD-related software + that is no longer supported by the FreeBSD + project. + + This list is for those interested in providing or + making use of peer support of FreeBSD-related software + for which the FreeBSD project no longer provides + official support (e.g., in the form of security + advisories and patches). @@ -1200,7 +1251,8 @@ &a.firewire.name; - &firewire; (iLink, IEEE 1394) + &firewire; (iLink, IEEE + 1394) This is a mailing list for discussion of the design and implementation of a &firewire; (aka IEEE 1394 aka @@ -1218,9 +1270,9 @@ File systems - Discussions concerning FreeBSD file systems. This is a - technical mailing list for which strictly technical content is - expected. + Discussions concerning FreeBSD file systems. + This is a technical mailing list for which strictly + technical content is expected. @@ -1230,8 +1282,9 @@ Gecko Rendering Engine - This is a forum about Gecko - applications using &os;. + This is a forum about + Gecko applications using + &os;. Discussion centers around Gecko Ports applications, their installation, their development and their support @@ -1245,9 +1298,9 @@ GEOM - Discussions specific to GEOM and related implementations. *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***