/[gentoo]/xml/htdocs/doc/en/gentoo-freebsd.xml
Gentoo

Diff of /xml/htdocs/doc/en/gentoo-freebsd.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.4 Revision 1.5
1<?xml version="1.0" encoding="UTF-8"?> 1<?xml version="1.0" encoding="UTF-8"?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-freebsd.xml,v 1.4 2005/09/11 16:27:55 cam Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-freebsd.xml,v 1.5 2005/09/21 19:04:05 jkt Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 4
5<guide link="/doc/en/gentoo-freebsd.xml"> 5<guide link="/doc/en/gentoo-freebsd.xml">
6<title>A short guide to Gentoo/FreeBSD</title> 6<title>A short guide to Gentoo/FreeBSD</title>
7 7
8<author title="Author"> 8<author title="Author">
9 <mail link="ignacio.arquelatour@gmail.com">Ignacio Arque-Latour</mail> 9 <mail link="ignacio.arquelatour@gmail.com">Ignacio Arque-Latour</mail>
10</author> 10</author>
11<author title="Author"> 11<author title="Author">
12 <mail link="citizen428@gentoo.org">Michael Kohl</mail> 12 <mail link="citizen428@gentoo.org">Michael Kohl</mail>
13</author> 13</author>
14<author title="Author"> 14<author title="Author">
15 Otavio R. Piske 15 Otavio R. Piske
16</author> 16</author>
17<author title="Author"> 17<author title="Author">
18 <mail link="ka0ttic@gentoo.org">Aaron Walker</mail> 18 <mail link="ka0ttic@gentoo.org">Aaron Walker</mail>
19</author> 19</author>
20 20
21<abstract> 21<abstract>
22This document gives some general information on FreeBSD, as well as 22This document gives some general information on FreeBSD, as well as
23installation instructions for Gentoo/FreeBSD. It also includes some reference 23installation instructions for Gentoo/FreeBSD. It also includes some reference
24for people interested in helping out with development. 24for people interested in helping out with development.
25</abstract> 25</abstract>
26 26
27<!-- The content of this document is licensed under the CC-BY-SA license --> 27<!-- The content of this document is licensed under the CC-BY-SA license -->
28<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 28<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
29<license/> 29<license/>
30 30
31<version>1.2</version> 31<version>1.3</version>
32<date>2005-09-10</date> 32<date>2005-09-21</date>
33 33
34<chapter> 34<chapter>
35<title>Introduction to FreeBSD</title> 35<title>Introduction to FreeBSD</title>
36<section> 36<section>
37<title>What is FreeBSD?</title> 37<title>What is FreeBSD?</title>
38<body> 38<body>
39 39
40<p> 40<p>
41<uri link="http://www.freebsd.org/">FreeBSD</uri> is a free (<uri 41<uri link="http://www.freebsd.org/">FreeBSD</uri> is a free (<uri
42link="http://www.freebsd.org/copyright/freebsd-license.html">license</uri>) 42link="http://www.freebsd.org/copyright/freebsd-license.html">license</uri>)
43Unix-like operating system. Back in 1993 when development of <uri 43Unix-like operating system. Back in 1993 when development of <uri
44link="http://www.386bsd.org/">386BSD</uri> stopped, two projects were born: 44link="http://www.386bsd.org/">386BSD</uri> stopped, two projects were born:
45<uri link="http://www.netbsd.org/">NetBSD</uri>, commonly known to run on a 45<uri link="http://www.netbsd.org/">NetBSD</uri>, commonly known to run on a
46huge number of architetures, and FreeBSD which focuses mainly on the x86 46huge number of architetures, and FreeBSD which focuses mainly on the x86
47platform. FreeBSD is renowned for its stability, performance and security, thus 47platform. FreeBSD is renowned for its stability, performance and security, thus
308<section> 308<section>
309<title>How to help</title> 309<title>How to help</title>
310<body> 310<body>
311 311
312<p> 312<p>
313There are many things you could help with, depending on your skill level and 313There are many things you could help with, depending on your skill level and
314spare time: 314spare time:
315</p> 315</p>
316 316
317<ul> 317<ul>
318 <li> 318 <li>
319 We need GCC and binutils hackers who are able to port FreeBSD's patches to 319 We need GCC and binutils hackers who are able to port FreeBSD's patches to
320 the original versions of these tools provided by our main Portage tree. 320 the original versions of these tools provided by our main Portage tree.
321 </li> 321 </li>
322 <li> 322 <li>
323 Working with userland ebuilds: this means working closely with other 323 Working on current ebuilds: this means working closely with ebuild maintainers
324 developers in order to have our changes/patches accepted into the main tree. 324 in order to create patches or modify ebuilds in a way that can be accepted
325 into the main tree.
325 </li> 326 </li>
326 <li> 327 <li>
327 Security: if you are into security, we need you! Although security 328 Security: if you are into security, we need you! Although security
328 advisories from the FreeBSD project are tracked and fixed, we can always 329 advisories from the FreeBSD project are tracked and fixed, we can always
329 use help in this area. 330 use help in this area.
330 </li> 331 </li>
331 <li> 332 <li>
332 Contacts: we need people who can get in touch with FreeBSD developers to 333 Contacts: we need people who can get in touch with FreeBSD developers to
333 maintain contacts between us and the original project to exchange patches 334 maintain contacts between us and the original project to exchange patches
334 and discuss various problems and their solutions. Note that this should 335 and discuss various problems and their solutions. Note that this should
335 never involve any kind of spamming of mailing lists or IRC channels. 336 never involve any kind of spamming of mailing lists or IRC channels.
336 </li> 337 </li>
337 <li> 338 <li>
338 Testing: the more people are actively using Gentoo/FreeBSD, the more bugs 339 Testing: the more people are actively using Gentoo/FreeBSD, the more bugs
339 will be discovered, which helps us improving the quality of the port. If 340 will be discovered, which helps us improving the quality of the port. If
411 412
412<p> 413<p>
413At the moment, there are still quite a lot of known issues. Here are the ones 414At the moment, there are still quite a lot of known issues. Here are the ones
414really worth noting: 415really worth noting:
415</p> 416</p>
416 417
417<ul> 418<ul>
418 <li> 419 <li>
419 Some init scripts depend on the clock service which we don't provide right 420 Some init scripts depend on the clock service which we don't provide right
420 now. You can just remove it from the dependencies of the script and report 421 now. You can just remove it from the dependencies of the script and report
421 that on our <uri link="http://bugs.gentoo.org/">bugzilla</uri>. Please 422 that on our <uri link="http://bugs.gentoo.org/">bugzilla</uri>. Please
422 remember to use the "Gentoo BSD" product for your submission. 423 remember to use the "Gentoo BSD" product for your submission.
423 </li> 424 </li>
424 <li> 425 <li>
425 Some ebuilds have hardcoded -ldl flags to link against libdl to get 426 Some ebuilds have hardcoded -ldl flags to link against libdl to get
426 <c>dlopen()</c>. This needs to be fixed. 427 <c>dlopen()</c>. This needs to be fixed (for further information, please
427 </li> 428 consult our <uri link="/proj/en/gentoo-alt/bsd/maintnotes.xml#doc_chap3">
428 <li> 429 our Gentoo/*BSD Technotes Guide</uri>.
429 xorg-x11 6.8.99.14 and .15 won't build. Until this has been fixed, you can
430 revert to xorg-x11-6.8.99.13. An ebuild can be obtained via <uri
431 link="http://viewcvs.gentoo.org">ViewCVS</uri>.
432 </li> 430 </li>
433 <li>glib and gnome in general need a lot of fixes to be backported.</li> 431 <li>glib and gnome in general need a lot of fixes to be backported.</li>
434</ul> 432</ul>
435 433
436</body> 434</body>
437</section> 435</section>
438</chapter> 436</chapter>
439 437
440<chapter> 438<chapter>
441<title>Contact</title> 439<title>Contact</title>
442<section> 440<section>
443<body> 441<body>
444 442
445<p> 443<p>
446A list of Gentoo/FreeBSD developers can be found at the <uri 444A list of Gentoo/FreeBSD developers can be found at the <uri

Legend:
Removed from v.1.4  
changed lines
  Added in v.1.5

  ViewVC Help
Powered by ViewVC 1.1.20