From: "Camille Huot" <cam@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: gentoo-freebsd.xml
Date: Sun, 11 Sep 2005 16:27:55 +0000 [thread overview]
Message-ID: <200509111623.j8BGNtkl011725@robin.gentoo.org> (raw)
cam 05/09/11 16:27:55
Modified: xml/htdocs/doc/en gentoo-freebsd.xml
Log:
Fixed minor typos, no content changes.
Revision Changes Path
1.4 +26 -26 xml/htdocs/doc/en/gentoo-freebsd.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-freebsd.xml?rev=1.4&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-freebsd.xml?rev=1.4&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-freebsd.xml.diff?r1=1.3&r2=1.4&cvsroot=gentoo
Index: gentoo-freebsd.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-freebsd.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- gentoo-freebsd.xml 10 Sep 2005 21:09:01 -0000 1.3
+++ gentoo-freebsd.xml 11 Sep 2005 16:27:55 -0000 1.4
@@ -1,5 +1,5 @@
-<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-freebsd.xml,v 1.3 2005/09/10 21:09:01 rane Exp $ -->
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-freebsd.xml,v 1.4 2005/09/11 16:27:55 cam Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/gentoo-freebsd.xml">
@@ -57,10 +57,10 @@
<body>
<p>
-Gentoo/FreeBSD is an effort effort to provide a fully-capable FreeBSD operating
-system with Gentoo's design sensibilities. The long-term goal of the Gentoo/BSD
-project is to allow users to choose any combination of *BSD or Linux kernels,
-*BSD or GNU libc, and *BSD or GNU userland tools.
+Gentoo/FreeBSD is an effort to provide a fully-capable FreeBSD operating system
+with Gentoo's design sensibilities. The long-term goal of the Gentoo/BSD project
+is to allow users to choose any combination of *BSD or Linux kernels, *BSD or
+GNU libc, and *BSD or GNU userland tools.
</p>
</body>
@@ -81,7 +81,7 @@
Contrary to Linux, which actually only refers to the kernel, FreeBSD is a
complete operating system, consisting of a C library, userland tools and
much more. This development approach makes the overall system very
- consistent
+ consistent.
</li>
<li>
Contrary to the Linux kernel, FreeBSD development is not led by one person,
@@ -99,19 +99,19 @@
<ul>
<li>
- To get run-time dynamic linking fuctions like <c>dlopen()</c>, programs do
+ To get run-time dynamic linking functions like <c>dlopen()</c>, programs do
not need to be linked against libdl like on GNU/Linux. Instead they are
- linked against libc
+ linked against libc.
</li>
<li>
FreeBSD doesn't have an official tool for kernel compilation, thus you'll
- have to resolve feature dependecies on your own
+ have to resolve feature dependencies on your own.
</li>
<li>
FreeBSD uses UFS/UFS-2 as its filesystems and has no official support for
e.g. ReiserFS or XFS. However, there are projects for adding read-only
- support for these filesystems. However, accessing ext2/ext3 partitions is
- already possible, but you cannot install your system on them.
+ support for these filesystems. Accessing ext2/ext3 partitions is already
+ possible, but you cannot install your system on them.
</li>
</ul>
@@ -210,8 +210,8 @@
<comment>(FreeBSD's standard editor is ee, which is used to edit /etc/make.conf)</comment>
# <i>ee /etc/make.conf</i>
<comment>(Please make sure you add at least the following entries:)</comment>
-CHOST="i686-gentoo-freebsd5.4"
-ACCEPT_KEYWORDS="~x86-fbsd ~x86"
+CHOST="i686-gentoo-freebsd5.4"
+ACCEPT_KEYWORDS="~x86-fbsd ~x86"
FEATURES="-sandbox collision-protect"
PORTDIR_OVERLAY="/usr/local/portage/gentoo-freebsd"
</pre>
@@ -306,7 +306,7 @@
<chapter>
<title>Developing for Gentoo/FreeBSD</title>
<section>
-<title>How to help </title>
+<title>How to help</title>
<body>
<p>
@@ -317,28 +317,28 @@
<ul>
<li>
We need GCC and binutils hackers who are able to port FreeBSD's patches to
- the original versions of these tools provided by our main Portage tree
+ the original versions of these tools provided by our main Portage tree.
</li>
<li>
Working with userland ebuilds: this means working closely with other
- developers in order to have our changes/patches accepted into the main tree
+ developers in order to have our changes/patches accepted into the main tree.
</li>
<li>
Security: if you are into security, we need you! Although security
advisories from the FreeBSD project are tracked and fixed, we can always
- use help in this area
+ use help in this area.
</li>
<li>
Contacts: we need people who can get in touch with FreeBSD developers to
maintain contacts between us and the original project to exchange patches
and discuss various problems and their solutions. Note that this should
- never involve any kind of spamming of mailing lists or IRC channels
+ never involve any kind of spamming of mailing lists or IRC channels.
</li>
<li>
Testing: the more people are actively using Gentoo/FreeBSD, the more bugs
will be discovered, which helps us improving the quality of the port. If
you are good at describing bugs or problems, we definitely want to hear
- from you
+ from you.
</li>
<li>
Other areas where we need help include: system ebuilds, baselayout,
@@ -364,12 +364,12 @@
Instead, it uses its own implementation of <c>make</c>, putting
configuration options in external files and some .mk files that are
included with each Makefile. Although a lot of work has been put into
- those .mk files, it is not hard to find some installations failling due to
+ those .mk files, it is not hard to find some installations failing due to
a missing <c>${INSTALL} -d</c> somewhere. The easy way to deal with
this kind of problem is to read the Makefile to find the accompanying .mk
file, then open that file and try to figure out which part failed (this is
not really hard once you figure out where in the installation process it
- stopped)
+ stopped).
</li>
<li>
Besides, due to the fact that FreeBSD is a complete operating system, you
@@ -419,16 +419,16 @@
Some init scripts depend on the clock service which we don't provide right
now. You can just remove it from the dependencies of the script and report
that on our <uri link="http://bugs.gentoo.org/">bugzilla</uri>. Please
- remember to use the "Gentoo BSD" product for your submission
+ remember to use the "Gentoo BSD" product for your submission.
</li>
<li>
Some ebuilds have hardcoded -ldl flags to link against libdl to get
- <c>dlopen()</c>. This needs to be fixed
+ <c>dlopen()</c>. This needs to be fixed.
</li>
<li>
xorg-x11 6.8.99.14 and .15 won't build. Until this has been fixed, you can
revert to xorg-x11-6.8.99.13. An ebuild can be obtained via <uri
- link="http://viewcvs.gentoo.org">ViewCVS</uri>
+ link="http://viewcvs.gentoo.org">ViewCVS</uri>.
</li>
<li>glib and gnome in general need a lot of fixes to be backported.</li>
</ul>
@@ -443,7 +443,7 @@
<body>
<p>
-At list of Gentoo/FreeBSD developers can be found at the <uri
+A list of Gentoo/FreeBSD developers can be found at the <uri
link="/proj/en/gentoo-alt/bsd/fbsd/">project page</uri>. Other ways to contact
Gentoo/FreeBSD developers include our IRC Channel <c>#gentoo-bsd</c> on
Freenode, as well as the mailing list <mail>gentoo-bsd@gentoo.org</mail>. To
--
gentoo-doc-cvs@gentoo.org mailing list
next reply other threads:[~2005-09-11 16:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 16:27 Camille Huot [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-02 18:58 [gentoo-doc-cvs] cvs commit: gentoo-freebsd.xml Camille Huot
2008-05-20 18:38 Sven Vermeulen
2007-05-11 0:11 Camille Huot
2007-05-10 23:59 Camille Huot
2007-05-10 22:00 Camille Huot
2007-04-08 21:55 Josh Saddler
2007-04-04 14:22 Josh Saddler
2007-01-03 3:08 Josh Saddler
2006-11-25 4:04 Josh Saddler
2006-10-06 21:48 Josh Saddler
2006-05-26 19:29 Josh Saddler
2006-05-26 19:21 Josh Saddler
2006-05-03 1:03 Lukasz Damentko
2006-05-03 1:01 Lukasz Damentko
2006-03-30 8:41 Xavier Neys
2006-03-28 10:30 Xavier Neys
2006-03-02 13:32 Jose Luis Rivero
2006-01-10 21:15 Marcelo Goes
2005-12-20 19:12 Camille Huot
2005-12-06 12:32 Jan Kundrat
2005-10-21 10:45 Xavier Neys
2005-10-16 15:31 Xavier Neys
2005-10-11 14:03 Lukasz Damentko
2005-10-06 15:58 Jan Kundrat
2005-09-21 19:16 Jan Kundrat
2005-09-21 19:04 Jan Kundrat
2005-09-10 21:09 Lukasz Damentko
2005-09-09 11:09 Shyam Mani
2005-08-31 14:19 Xavier Neys
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200509111623.j8BGNtkl011725@robin.gentoo.org \
--to=cam@lark.gentoo.org \
--cc=docs-team@lists.gentoo.org \
--cc=gentoo-doc-cvs@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox