Gentoo Archives: gentoo-doc-cvs

From: Camille Huot <cam@×××××××××××.org>
To: gentoo-doc-cvs@l.g.o
Subject: [gentoo-doc-cvs] cvs commit: gentoo-freebsd.xml
Date: Sun, 11 Sep 2005 16:28:23
Message-Id: 200509111623.j8BGNtkl011725@robin.gentoo.org
1 cam 05/09/11 16:27:55
2
3 Modified: xml/htdocs/doc/en gentoo-freebsd.xml
4 Log:
5 Fixed minor typos, no content changes.
6
7 Revision Changes Path
8 1.4 +26 -26 xml/htdocs/doc/en/gentoo-freebsd.xml
9
10 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
11 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
12 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
13
14 Index: gentoo-freebsd.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-freebsd.xml,v
17 retrieving revision 1.3
18 retrieving revision 1.4
19 diff -u -r1.3 -r1.4
20 --- gentoo-freebsd.xml 10 Sep 2005 21:09:01 -0000 1.3
21 +++ gentoo-freebsd.xml 11 Sep 2005 16:27:55 -0000 1.4
22 @@ -1,5 +1,5 @@
23 -<?xml version='1.0' encoding="UTF-8"?>
24 -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-freebsd.xml,v 1.3 2005/09/10 21:09:01 rane Exp $ -->
25 +<?xml version="1.0" encoding="UTF-8"?>
26 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-freebsd.xml,v 1.4 2005/09/11 16:27:55 cam Exp $ -->
27 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
28
29 <guide link="/doc/en/gentoo-freebsd.xml">
30 @@ -57,10 +57,10 @@
31 <body>
32
33 <p>
34 -Gentoo/FreeBSD is an effort effort to provide a fully-capable FreeBSD operating
35 -system with Gentoo's design sensibilities. The long-term goal of the Gentoo/BSD
36 -project is to allow users to choose any combination of *BSD or Linux kernels,
37 -*BSD or GNU libc, and *BSD or GNU userland tools.
38 +Gentoo/FreeBSD is an effort to provide a fully-capable FreeBSD operating system
39 +with Gentoo's design sensibilities. The long-term goal of the Gentoo/BSD project
40 +is to allow users to choose any combination of *BSD or Linux kernels, *BSD or
41 +GNU libc, and *BSD or GNU userland tools.
42 </p>
43
44 </body>
45 @@ -81,7 +81,7 @@
46 Contrary to Linux, which actually only refers to the kernel, FreeBSD is a
47 complete operating system, consisting of a C library, userland tools and
48 much more. This development approach makes the overall system very
49 - consistent
50 + consistent.
51 </li>
52 <li>
53 Contrary to the Linux kernel, FreeBSD development is not led by one person,
54 @@ -99,19 +99,19 @@
55
56 <ul>
57 <li>
58 - To get run-time dynamic linking fuctions like <c>dlopen()</c>, programs do
59 + To get run-time dynamic linking functions like <c>dlopen()</c>, programs do
60 not need to be linked against libdl like on GNU/Linux. Instead they are
61 - linked against libc
62 + linked against libc.
63 </li>
64 <li>
65 FreeBSD doesn't have an official tool for kernel compilation, thus you'll
66 - have to resolve feature dependecies on your own
67 + have to resolve feature dependencies on your own.
68 </li>
69 <li>
70 FreeBSD uses UFS/UFS-2 as its filesystems and has no official support for
71 e.g. ReiserFS or XFS. However, there are projects for adding read-only
72 - support for these filesystems. However, accessing ext2/ext3 partitions is
73 - already possible, but you cannot install your system on them.
74 + support for these filesystems. Accessing ext2/ext3 partitions is already
75 + possible, but you cannot install your system on them.
76 </li>
77 </ul>
78
79 @@ -210,8 +210,8 @@
80 <comment>(FreeBSD's standard editor is ee, which is used to edit /etc/make.conf)</comment>
81 # <i>ee /etc/make.conf</i>
82 <comment>(Please make sure you add at least the following entries:)</comment>
83 -CHOST="i686-gentoo-freebsd5.4"
84 -ACCEPT_KEYWORDS="~x86-fbsd ~x86"
85 +CHOST="i686-gentoo-freebsd5.4"
86 +ACCEPT_KEYWORDS="~x86-fbsd ~x86"
87 FEATURES="-sandbox collision-protect"
88 PORTDIR_OVERLAY="/usr/local/portage/gentoo-freebsd"
89 </pre>
90 @@ -306,7 +306,7 @@
91 <chapter>
92 <title>Developing for Gentoo/FreeBSD</title>
93 <section>
94 -<title>How to help </title>
95 +<title>How to help</title>
96 <body>
97
98 <p>
99 @@ -317,28 +317,28 @@
100 <ul>
101 <li>
102 We need GCC and binutils hackers who are able to port FreeBSD's patches to
103 - the original versions of these tools provided by our main Portage tree
104 + the original versions of these tools provided by our main Portage tree.
105 </li>
106 <li>
107 Working with userland ebuilds: this means working closely with other
108 - developers in order to have our changes/patches accepted into the main tree
109 + developers in order to have our changes/patches accepted into the main tree.
110 </li>
111 <li>
112 Security: if you are into security, we need you! Although security
113 advisories from the FreeBSD project are tracked and fixed, we can always
114 - use help in this area
115 + use help in this area.
116 </li>
117 <li>
118 Contacts: we need people who can get in touch with FreeBSD developers to
119 maintain contacts between us and the original project to exchange patches
120 and discuss various problems and their solutions. Note that this should
121 - never involve any kind of spamming of mailing lists or IRC channels
122 + never involve any kind of spamming of mailing lists or IRC channels.
123 </li>
124 <li>
125 Testing: the more people are actively using Gentoo/FreeBSD, the more bugs
126 will be discovered, which helps us improving the quality of the port. If
127 you are good at describing bugs or problems, we definitely want to hear
128 - from you
129 + from you.
130 </li>
131 <li>
132 Other areas where we need help include: system ebuilds, baselayout,
133 @@ -364,12 +364,12 @@
134 Instead, it uses its own implementation of <c>make</c>, putting
135 configuration options in external files and some .mk files that are
136 included with each Makefile. Although a lot of work has been put into
137 - those .mk files, it is not hard to find some installations failling due to
138 + those .mk files, it is not hard to find some installations failing due to
139 a missing <c>${INSTALL}&nbsp;-d</c> somewhere. The easy way to deal with
140 this kind of problem is to read the Makefile to find the accompanying .mk
141 file, then open that file and try to figure out which part failed (this is
142 not really hard once you figure out where in the installation process it
143 - stopped)
144 + stopped).
145 </li>
146 <li>
147 Besides, due to the fact that FreeBSD is a complete operating system, you
148 @@ -419,16 +419,16 @@
149 Some init scripts depend on the clock service which we don't provide right
150 now. You can just remove it from the dependencies of the script and report
151 that on our <uri link="http://bugs.gentoo.org/">bugzilla</uri>. Please
152 - remember to use the "Gentoo BSD" product for your submission
153 + remember to use the "Gentoo BSD" product for your submission.
154 </li>
155 <li>
156 Some ebuilds have hardcoded -ldl flags to link against libdl to get
157 - <c>dlopen()</c>. This needs to be fixed
158 + <c>dlopen()</c>. This needs to be fixed.
159 </li>
160 <li>
161 xorg-x11 6.8.99.14 and .15 won't build. Until this has been fixed, you can
162 revert to xorg-x11-6.8.99.13. An ebuild can be obtained via <uri
163 - link="http://viewcvs.gentoo.org">ViewCVS</uri>
164 + link="http://viewcvs.gentoo.org">ViewCVS</uri>.
165 </li>
166 <li>glib and gnome in general need a lot of fixes to be backported.</li>
167 </ul>
168 @@ -443,7 +443,7 @@
169 <body>
170
171 <p>
172 -At list of Gentoo/FreeBSD developers can be found at the <uri
173 +A list of Gentoo/FreeBSD developers can be found at the <uri
174 link="/proj/en/gentoo-alt/bsd/fbsd/">project page</uri>. Other ways to contact
175 Gentoo/FreeBSD developers include our IRC Channel <c>#gentoo-bsd</c> on
176 Freenode, as well as the mailing list <mail>gentoo-bsd@g.o</mail>. To
177
178
179
180 --
181 gentoo-doc-cvs@g.o mailing list