<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: installing ~x86-fbsd</title>
	<atom:link href="http://wonkabar.org/archives/285/feed" rel="self" type="application/rss+xml" />
	<link>http://wonkabar.org/archives/285</link>
	<description>linux, databases, cartoons and cornflakes</description>
	<pubDate>Thu, 20 Nov 2008 23:20:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Julian Stecklina</title>
		<link>http://wonkabar.org/archives/285#comment-12914</link>
		<dc:creator>Julian Stecklina</dc:creator>
		<pubDate>Mon, 04 Jun 2007 11:47:15 +0000</pubDate>
		<guid isPermaLink="false">http://wonkabar.org/archives/285#comment-12914</guid>
		<description>FreeBSD's disk layout is not based on DOS-style partitioning, but on disklabels which are vastly more flexible. The common practice on x86 is to create a DOS-style partition on your disk (called `slice' in FreeBSD speak, the first slice on disk 0 is ad0s1) and partition that further using a disklabel (that's where the letters come from: ad0s1a is the first partition in that slice).

FreeBSD has no problem accessing other DOS-style partitions. These look like adXsY (note the missing letter). Linux has no problem to access BSD disklabels as well, if you enable that in your kernel. The real problem with sharing your /home is selecting a filesystem. Linux has only limited UFS2 capabilities and EXT3 is not supported on FreeBSD (EXT2 is)...

Btw, kernel configuration in FreeBSD is done through a config file in /sys//conf/. You are probably running the GENERIC kernel which has almost all drivers enabled and reasonable defaults for everything else. The FreeBSD manual is the way to go if you want to compile your own kernel.</description>
		<content:encoded><![CDATA[<p>FreeBSD&#8217;s disk layout is not based on DOS-style partitioning, but on disklabels which are vastly more flexible. The common practice on x86 is to create a DOS-style partition on your disk (called `slice&#8217; in FreeBSD speak, the first slice on disk 0 is ad0s1) and partition that further using a disklabel (that&#8217;s where the letters come from: ad0s1a is the first partition in that slice).</p>
<p>FreeBSD has no problem accessing other DOS-style partitions. These look like adXsY (note the missing letter). Linux has no problem to access BSD disklabels as well, if you enable that in your kernel. The real problem with sharing your /home is selecting a filesystem. Linux has only limited UFS2 capabilities and EXT3 is not supported on FreeBSD (EXT2 is)&#8230;</p>
<p>Btw, kernel configuration in FreeBSD is done through a config file in /sys//conf/. You are probably running the GENERIC kernel which has almost all drivers enabled and reasonable defaults for everything else. The FreeBSD manual is the way to go if you want to compile your own kernel.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Spax Klettergriffe</title>
		<link>http://wonkabar.org/archives/285#comment-12372</link>
		<dc:creator>Spax Klettergriffe</dc:creator>
		<pubDate>Fri, 25 May 2007 21:55:45 +0000</pubDate>
		<guid isPermaLink="false">http://wonkabar.org/archives/285#comment-12372</guid>
		<description>Thanks for the Link to the install guide.

Thats cool.

Hans from Germany</description>
		<content:encoded><![CDATA[<p>Thanks for the Link to the install guide.</p>
<p>Thats cool.</p>
<p>Hans from Germany</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://wonkabar.org/archives/285#comment-12354</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Fri, 25 May 2007 16:08:37 +0000</pubDate>
		<guid isPermaLink="false">http://wonkabar.org/archives/285#comment-12354</guid>
		<description>I tried for *hours* to get Debian GNU/kFreeBSD up and running, but to no avail.  The dhclient refuses to pick up an IP and resolve anything, and even when I enter the networking manually during the install, it still refuses to resolve an address.  So, after many failed attempts, I decided to go with a vanilla FreeBSD install.  I would have much rather preferred used the Debian GNU toolchain and package management, rather than learn a new package manager, but I'm so curious about FreeBSD, that I guess I need to take the leap anyway.  I'll post my experiences in about a week or so, when I have a full fledged running FreeBSD system.</description>
		<content:encoded><![CDATA[<p>I tried for *hours* to get Debian GNU/kFreeBSD up and running, but to no avail.  The dhclient refuses to pick up an IP and resolve anything, and even when I enter the networking manually during the install, it still refuses to resolve an address.  So, after many failed attempts, I decided to go with a vanilla FreeBSD install.  I would have much rather preferred used the Debian GNU toolchain and package management, rather than learn a new package manager, but I&#8217;m so curious about FreeBSD, that I guess I need to take the leap anyway.  I&#8217;ll post my experiences in about a week or so, when I have a full fledged running FreeBSD system.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
