From: "Xavier Neys" <neysx@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: gentoo-freebsd.xml
Date: Tue, 28 Mar 2006 10:30:14 +0000 [thread overview]
Message-ID: <200603281030.k2SAUFwj026842@robin.gentoo.org> (raw)
neysx 06/03/28 10:30:14
Modified: gentoo-freebsd.xml
Log:
Update from #127477
Revision Changes Path
1.15 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.15&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.15&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.14&r2=1.15&cvsroot=gentoo
Index: gentoo-freebsd.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-freebsd.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- gentoo-freebsd.xml 2 Mar 2006 13:32:47 -0000 1.14
+++ gentoo-freebsd.xml 28 Mar 2006 10:30:14 -0000 1.15
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-freebsd.xml,v 1.14 2006/03/02 13:32:47 yoswink Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-freebsd.xml,v 1.15 2006/03/28 10:30:14 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/gentoo-freebsd.xml">
@@ -28,8 +28,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2.1</version>
-<date>2006-03-02</date>
+<version>2.2</version>
+<date>2006-03-24</date>
<chapter>
<title>Introduction to FreeBSD</title>
@@ -43,11 +43,13 @@
Unix-like operating system. Back in 1993 when development of <uri
link="http://www.386bsd.org/">386BSD</uri> stopped, two projects were born:
<uri link="http://www.netbsd.org/">NetBSD</uri>, commonly known to run on a
-huge number of architetures, and FreeBSD which focuses mainly on the x86
-platform. FreeBSD is renowned for its stability, performance and security, thus
-being used from small to huge companies all over the world. FreeBSD's current
-production release version is 5.4, which is also used as the foundation for the
-Gentoo/FreeBSD project.
+huge number of architetures, and FreeBSD which supports the x86, amd64, ia64,
+sparc64 and alpha platforms.FreeBSD is renowned for its stability, performance
+and security, thus being used from small to huge companies all over the world.
+FreeBSD's current production release version is 6.0, which is also used as the
+foundation for the Gentoo/FreeBSD project. The previous 5.x branch is being
+continued by the FreeBSD project as a service release, but is no more worked on by
+the Gentoo/FreeBSD developers.
</p>
</body>
@@ -57,10 +59,10 @@
<body>
<p>
-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.
+<uri link="proj/en/gentoo-alt/bsd/fbsd/">Gentoo/FreeBSD</uri> is a subproject of the
+<uri link="proj/en/gentoo-alt/">Gentoo/Alt project</uri>, with the goal of providing
+a fully-capable FreeBSD operating system featuring the design sensibilities known from
+Gentoo Linux, like the init system and the portage package management system.
</p>
</body>
@@ -135,13 +137,29 @@
an installation medium for Gentoo/FreeBSD.
</p>
+<note>
+If you are intending to use FreeSBIE for installing Gentoo/FreeBSD, please make
+sure to use a version based on FreeBSD 6.0! Experimental versions can be downloaded
+from <uri link="http://torrent.freesbie.org/">FreeSBIE's Bittorrent tracker</uri> and
+version 20060118 has been tested to work for the purposes described in this document.
+</note>
+
<p>
Before you can begin with the installation, you have to setup a hard disk for
use with Gentoo/FreeBSD. This can either be done via <c>sysinstall</c>
(available from a current FreeBSD installation as well as from within FreeSBIE)
-or by manually using the commands <c>fdisk</c>, <c>disklabel</c> and
-<c>newfs</c>. If you have never set up a FreeBSD system before,
-<c>sysinstall</c> may be the better option for you. If you face difficulties
+or by manually using the commands <c>fdisk</c>, <c>disklabel</c> and <c>newfs</c>.
+If you have never set up a FreeBSD system before, <c>sysinstall</c> may be the
+better option for you. In that case make sure that you don't use the sysinstall
+launched by FreeBSD's or FreeSBIE's installers, but use the following command instead:
+</p>
+
+<pre caption="Partitioning with sysinstall">
+# <i>sysinstall diskPartitionEditor diskPartitionWrite diskLabelEditor diskLabelCommit</i>
+</pre>
+
+<p>
+If you face difficulties
while partitioning or formatting your hard disks, have a look at the great
<uri link="http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/">FreeBSD
Handbook</uri> or hop onto <c>#gentoo-bsd</c> on the Freenode IRC server.
@@ -159,6 +177,18 @@
</pre>
<p>
+If you're using the FreeSBIE LiveCD and you already had an UFS partition on
+your hard disk, it has already been mounted read-only to <path>/mnt/ufs.1</path>.
+If you want to use that location for your installation, you'll have to remount it
+in read-write mode:
+</p>
+
+<pre caption="Remounting a partition in read-write mode">
+# <i>ount -u -o rw /mnt/ufs.1</i>
+</pre>
+
+
+<p>
Now that you have mounted the target partition, it is time to fetch and unpack
a stage3 tarball.
</p>
@@ -166,10 +196,10 @@
<pre caption="Obtaining and unpacking a stage3 tarball">
# <i>cd /mnt/gentoo/</i>
<comment>(Any other Gentoo mirror which includes the experimental/ directory will also work.)</comment>
-# <i>wget http://gentoo.osuosl.org/experimental/x86/freebsd/stages/stage3-x86-fbsd-20051020.tar.bz2</i>
-# <i>tar -jxvpf stage3-x86-fbsd-20051020.tar.bz2</i>
+# <i>wget http://gentoo.osuosl.org/experimental/x86/freebsd/stages/gentoo-freebsd-6.0-stage-20060221.tar.bz2</i>
+# <i>tar -jxvpf gentoo-freebsd-6.0-stage-20060221</i>
<comment>(You can delete the tarball with the following command if you want to.)</comment>
-# <i>rm stage3-x86-fbsd-20051020.tar.bz2</i>
+# <i>rm gentoo-freebsd-6.0-stage-20060221</i>
</pre>
<p>
@@ -215,16 +245,21 @@
</p>
<pre caption="Setting up the profile and editing /etc/make.conf">
-# <i>ln -sf /usr/local/portage/portage-alt-overlay/profiles/default-bsd/fbsd/5.4/x86/ /etc/make.profile</i>
+# <i>ln -sf /usr/local/portage/portage-alt-overlay/profiles/default-bsd/fbsd/6.0/x86/ /etc/make.profile</i>
<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"
+CHOST="i686-gentoo-freebsd6.0"
ACCEPT_KEYWORDS="~x86-fbsd ~x86"
FEATURES="-sandbox collision-protect"
PORTDIR_OVERLAY="/usr/local/portage/portage-alt-overlay"
</pre>
+<note>
+If you're installing using an old 5.4 stage, please replace "5.4" by "6.0" when symlinking the profile and
+setting the CHOST variable.
+</note>
+
<p>
In order to boot correctly, you will need to create the <path>/proc</path>
directory.
@@ -279,9 +314,16 @@
supported on Gentoo/FreeBSD! Also note that <c>make install</c> will probably
ask you for a <path>/boot/device.hints</path> file. A default version can be
found in the <path>conf</path> subdirectory of the <c>GENERIC</c> configuration
-and is called <path>GENERIC.hints</path>
+and is called <path>GENERIC.hints</path>.
</p>
+<note>
+When building a kernel, you should use the command "make WERROR=NO_WERROR"
+because the Gentoo/FreeBSD developers have not yet been able to patch out all
+occurences of -Werror and the currently used GCC doesn't accept FreeBSD's
+extensions to the printf() funktion.
+</note>
+
<p>
Now is the time to do some basic system configuration and settings. First, we
are going to setup the filesystem mounting points in <path>/etc/fstab</path>.
@@ -353,7 +395,7 @@
<comment>(Leave the chroot environment)</comment>
# <i>exit</i>
<comment>(Issued from outside the chroot)</comment>
-# <i>fdisk -b -B /mnt/gentoo/boot/boot0 /dev/adX</i>
+# <i>fdisk -B -b /mnt/gentoo/boot/boot0 /dev/adX</i>
# <i>chroot /mnt/gentoo /bin/bash</i>
# <i>disklabel -B adXsY</i>
</pre>
@@ -403,10 +445,6 @@
<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.
- </li>
- <li>
Working on current ebuilds: this means working closely with ebuild
maintainers in order to create patches or modify ebuilds in a way that can
be accepted into the main tree.
@@ -436,63 +474,7 @@
</body>
</section>
-<section>
-<title>Building the system and dealing with issues</title>
-<body>
-
-<p>
-Although Linux and FreeBSD both are Unix-like operating systems, there are some
-important differences you have to know about if you want to contribute to our
-development effort:
-</p>
-<ul>
- <li>
- FreeBSD doesn't use the GNU autotools (autoconf, automake, autoheader).
- 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 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).
- </li>
- <li>
- Besides, due to the fact that FreeBSD is a complete operating system, you
- won't find things like a FreeBSD kernel tarball for download on a web site.
- The system is meant to be concise, thus whenever you start making an ebuild
- for something that uses system sources, you are very likely to run into
- problems when it tries to access non-existent files or directories. This
- generally occurs when a Makefile points to <path>${.CURDIR}/../sys</path>,
- or when a Makefile has a source dependency on another system package. There
- is no default rule on dealing with such issues, but generally one of the
- following procedures helps:
- <ul>
- <li>
- If the ebuild is trying to access kernel sources, patch it to point to
- <path>/usr/src/sys</path>
- </li>
- <li>
- If it's trying to access some other source that is provided by the
- system, it's easier to add it to <c>$SRC_URI</c> and unpack it to
- <c>$WORKDIR</c>
- </li>
- </ul>
- </li>
- <li>
- In order to maintain a concise buildsystem, we have several tarballs which
- are grouped by their functionality. This means that system libraries can be
- found in the freebsd-lib tarball, which contains the sources you would
- usually find in /usr/src/lib. On the other hand, freebsd-usrsbin contains
- <path>/usr/sbin/*</path> tools and consists of sources from
- <path>/usr/src/usr.sbin</path>.
- </li>
-</ul>
-
-</body>
-</section>
<section>
<title>Known issues</title>
<body>
@@ -510,6 +492,11 @@
remember to use the "Gentoo BSD" product for your submission.
</li>
<li>glib and gnome in general need a lot of fixes to be backported.</li>
+ <li>
+ The init system currently provided by Gentoo/FreeBSD's baselayout package is
+ not the same version used by Gentoo Linux and lacks some of its features. Work
+ on making newer versions working is underway.
+ </li>
</ul>
</body>
--
gentoo-doc-cvs@gentoo.org mailing list
next reply other threads:[~2006-03-28 10:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 10:30 Xavier Neys [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-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-11 16:27 Camille Huot
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=200603281030.k2SAUFwj026842@robin.gentoo.org \
--to=neysx@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