Talk page harvest

From PC-BSD Wiki
Revision as of 05:03, 30 January 2012 by Tigersharke (Talk | contribs)

Jump to: navigation, search
This page exists solely to facilitate handbook improvement,
by allowing an easy 1-step view of talk pages associated with the handbook and 'Main Page' documentation pages.

Main Page

Cannot file a bug on the trac + The bug

Hi all!

I logged in and registered to as "shlomif", but I cannot start a new bug. It says:

Context Navigation
Warning: <acct_mgr.web_ui.MessageWrapper object at 0x87e2de90>
Error: Forbidden

TICKET_CREATE privileges are required to perform this operation

TracGuide — The Trac User and Administration Guide

Please fix it so that non-privileged users will be able to report bugs.

And here's the bug I wanted to report: I have been unable to install PC-BSD 7.1.1 on a Virtual Box VM (running on top of a Pentium 4 2.4GHz with 2.5GB of RAM running Mandriva Linux Cooker ) either from the first CD or both the first and second CD. It keeps asking me for the next CD with only an "OK" button and if I don't give it this CD, then the installation needs to be aborted, and the installed partition is left at an unusable state. As far as I recall, no installation of any Linux distribution I tried ever required more than one essential CD, and could always finish with just one CD, including today, so I think PC-BSD should follow suit, and not require more than one CD for installation.

I realise that if you make your software more idiot-proof, then nature will come up with better idiots, but eventually you can deal with a large number of complaints by eliminating many common stumbling blocks.

Please contact me at my contact page., though I'll try to monitor this wiki on my RSS reader.

Shlomif 11:30, 28 November 2009 (UTC)

Accessibility of handbook & possible confusion

Houston we have a problem. There are a few things we may not have considered that may cause trouble for users seeking help, especially those who either prefer to use google or online help, and/or those who have not yet installed it and therefore do not have the pdf or link on their desktop. There are further problems in the situation where a firewall is involved, since the most accurate version of the handbook (8.2) for anyone not working with/on the eventual upcoming release (v9.0) may be denied them due to its location on ftp.

I have tried to improve clarity on the pcbsd users handbook page but that only helps when reaching that page from other wiki links or the main wiki url. When google is used to locate help for example: 'google pcbsd multimedia' then your first result is a link within the new v9.0 handbook. This may be for two reasons, the v9.0 is using the same former locations (urls) of the 8.2 handbook, and secondly, Google may not (or does not) reference/"crawl" ftp sites.

It seems something should be changed, but I am not certain what/how, some ideas:

  • An indication in the sidebar for versions of the handbook.
  • A background image for the v9.0 handbook to indicate 'not for prime-time' but this would need to be a global background only affecting the unfinished/unpublished v9.0 handbook and/or other non-finalized things.
  • Similar to and possibly in addition to above. A global footer (possibly a floating footer which stays on the bottom of the viewing window) that provides a notice and link to the current 8.2 handbook.
  • Give the 8.2 version a static location. This may not be necessary to prevent confusion, but there may need to be a workaround for those locked out of the ftp site by firewalls.

--Tigersharke 15:29, 10 April 2011 (PDT)

Documentation Q

Also I do not know if this is necessary to include somewhere in here about people new to unix, freebsd, and of course pcbsd. here is freebsd article about just that. There's more UNIX manuals and sites that freebsd references for users as well. I do not know if we should only reference them, incorporated into the text, or both. Personally downloaded all of them to review and summarize them. Inputs are welcomed. --"What may be obvious to you, may not be obvious to others. That's why we have to write about them." 23:23, 17 July 2011 (PDT)

UPDATE: I need an answer before 11/1/11 to make my decision.

Removal of Old Posts Vote

I ask permission for deletion of the following posts grouped in comment tags < ! - - MfD Start - - > < ! - - MfD End - - > . I only need one member to agree of the changes. Me or the next member may make the edit. (MfD = marked for deletion). "What may be obvious to you, may not be obvious to others. That's why we have to write about them." 15:40, 19 October 2011 (PDT)


I have made some adjustments to the NavHeader which should remove the need for the localized version. Please take a look at how the newer NavHeader template reacts when traversing within the localized segment, such as /de. I switched Ziele und Funktionen to use the standard NavHeader. As you may notice, the new templates 'Next' and 'Previous' and 'returnTOC' and 'TOC' will contain a list of the appropriate translated words for each language id.

I plan to add further refinements for the rest of the wiki as needed. I had been attempting to solve the challenges of localizing the wiki when a site malfunction seemed to have taken away all my efforts, but I happen to have run across some breadcrumbs that survived. I have also been away from doing much editing or template work on the wiki for quite some time- at least in part due to sorrow over the loss of hard gained success (with a template relating to localized links).

I noticed how you have managed to translate many different things by using "custompagename" and other similar variables that exist in a number of templates. I hope to make further improvements on the wiki so that those changes might not be needed. I have to think a bit more on some wrinkles as they appear.

An additional new template 'References' is now available to localize the word "References" and is used (transcluded) by the Refheading template. As with the other templates which exist to localize specific words, it will give a message directed toward translators instructing them where and what to localize.

Some odd template issues

We may have to fly with what we have for the moment. As near as I can tell, the /en pages have some small template-induced errors with the hover link text on the NavHeader but this is due to the translation system's lag time which acts like a cache. Once the system catches up, I will look at it again to verify whether it is still an issue. I hope that everything continues to work properly in Ziele und Funktionen.

I am currently baffled and must be getting hindered by cache somewhere. The one /de page that I switched back to the standard NavHeader continues to work regardless of the modifications I make, while the 'base' page and /en page continue to have the weird bug. The main good news is that it is not a functional problem, only an aesthetic one.

Ok. I solved the challenge for the hover text (for the left) but I've discovered another bit of oddness. The wiki allows the pagename to be localized, BUT, the magicword I am using in the NavHeader template to shift the title below the icons does not work, it does not get localized (seems to take it from the URL). This is undoubtedly the reason for using the custompagename. I want to solve this issue as well, and see if the same translated data could be used for other templates. Currently using the standard NavHeader template without 'custompagename' causes a duplication of the pagename though non-localized. The real solution may be an adjustment to site CSS somehow. It will take a bit of exploration and effort.. so until then I will adjust the 'right' side of the NavHeader template effect to match the left. I found a solution to the localized page name issue, this: {{#if: {{getLang}}|{{:Translations:{{#titleparts: {{PAGENAME}}|1|1}}/Page display title/{{getLang}}}}|{{#titleparts: {{{custompagename|{{PAGENAME}}}}}|1}}}}

Just when i think everything is solved, the cache effect seems to bite me. I will have to look at the "solved" problems again and see whats going on.

I have done some exploration and experimentation with the wiki CSS, but I still have not figured out how to get things working as I desire. The NavHeader has been adjusted to be one large table instead of two, and some other tweaks.

There must be an easier way. I discovered another way (via CSS) to hide the page title but this affects the entire site entirely, so I will have to find another way or some method of limiting it to the handbook pages portion of the wiki. Trial and error lead me to ways of limiting the effect of this CSS attribute as well as others that I have added after.

Ok. It looks like most of the troubles have a solution. I am a bit unclear about categories, but it seems as though they ought to follow a similar rule as the translated wiki pages. This also leads me to believe that I may need to adjust some of the auto-categorizing markup in the navigation templates.

Localization infrastructure

  1. template local allows link auto-localization and includes a method to handle anchors.
  2. NavHeader and NavHome auto-localize and includes a method to localize descriptive text (ie "Next")
  3. mechanism for References list text localization.

The bulk of the work is now complete. Although I am aware of a few areas that still need to be revised:

  • Tables: table headings
  • and probably other things I cannot think of right now.

translation into German

::[ {{orangelight|'''Security WARNING'''}} for  users of Unsupported versions of FreeBSD.]{{nbsp|7}}
{| cellspacing="0" cellpadding="0" align="center" style="margin-left:auto; margin-right:auto; top:-10px; border-collapse: collapse;"
<!-- DOCUMENTATION header-->
| align="center" style="text-align:center; margin:.5em; margin-top:.1em; border-bottom:1; font-weight:bold; font-size: 148%" width="28%" height="50px"|Documentation
<!-- PROJECTS header-->
| align="center" style=" text-align:center; margin:.5em; margin-top:.1em; border-bottom:1; font-weight:bold; font-size: 148%" width="28%" height="50px"|Projects
<!-- DEVELOPMENT header-->
| align="center" style="text-align:center; margin:.5em; margin-top:.1em; border-bottom:1; font-weight:bold; font-size: 148%" width="28%" height="50px"|Development
<!-- DOCUMENTATION Column -->
| align="center" style="width:30%; padding:1em; text-align:center;" valign="top"|
<span style="font-size: 138%;">{{local|link=Wireless Testing}}</span><br/>
Driver Function & Compatability<br/><br/>
<!-- <span style="font-size: 138%;">{{local|link=Game Testing}}</span><br/>
Discovering what works and how<br/><br/> -->
<span style="font-size: 145%;">{{local|link=PC-BSD{{RM}} Users Handbook/{{release}}|PC-BSD{{r}} Users Handbook}}</span><br/>
Release ({{release}}) ''wiki'' publication<br/><br/>
<span style="font-size: 145%;">{{local|link=PC-BSD{{RM}} Users Handbook|Wiki bookshelf}}</span><br/>
Prior ''wiki'' publications<br/><br/>
<span style="font-size: 138%;">{{local|link=Pkgsrc in PC-BSD|Pkgsrc in PC-BSD{{r}}}}</span><br/>
Exploring NetBSD pkgsrc potential<br/><br/>
<span style="font-size: 138%;">{{local|link=Turn FreeBSD into PC-BSD{{RM}}|Turn FreeBSD{{r}} into PC-BSD{{r}}}}</span><br/>
Conversion instructions?<br/><br/>
<span style="font-size: 138%;">{{local|link=:Category:Troubleshooting|Troubleshooting}}</span><br/>
Solving some problems<br/><br/>
<span style="font-size: 138%;">{{local|link=Finding Help/{{release}}|Where to find help}}</span><br/>
Various resources for assistance<br/><br/><!--
<span style="font-size: 138%;">{{local|link=Press And Legal|Press/Legal}}</span><br/>
Press, licensing and other queries -->
<!-- PROJECTS Column -->
| align="center" style="width:31%; padding:1em; text-align:center;" valign="top"|
<span style="font-size: 138%;">{{local|link=Warden{{RM}}/{{release}}|Warden{{r}}}}</span><br/>
A Jail Management Tool<br/><br/>
<span style="font-size: 138%;">{{local|link=PBI Manager/{{release}}|PBI Manager}}</span><br/>
A Command line Tool Suite<br/><br/>
<span style="font-size: 138%;">{{local|link=PCDM}}</span><br/>
PC-BSD's Login Manager<br/><br/>
<span style="font-size: 145%;">{{local|link=PC-BSD{{RM}} Users Handbook/{{upcoming}}|PC-BSD{{r}} Documentation}}</span><br/>
Handbook version under development<br/><br/>
<span style="font-size: 138%;">{{local|link=Errata|Handbook Errata}}</span><br/>
Corrections after publishing<br/><br/>
<span style="font-size: 138%;">[ FreeBSD{{r}} Ideas page]</span><br/>
Concepts for possible development<br/><br/>
<span style="font-size: 138%;">[ FreeBSD{{r}} Wifi Ideas page]</span><br/>
Concepts for possible development<br/><br/>
<!-- DEVELOPMENT column-->
| align="center" style="width:30%; padding:1em; text-align:center;" valign="top"|
<span style="font-size: 138%;">[ PC-BSD{{r}} Trac]</span><br/>
Source, Reports, or Requests<br/><br/>
<span style="font-size: 138%;">{{local|link=Become a Developer/{{release}}|Become a Developer}}</span><br/>
How to help with code<br/><br/>
<span style="font-size: 138%;">{{local|link=EasyPBI2/{{release}}|EasyPBI2}}</span><br/>
Simplifying the PBI creation process<br/><br/>
<span style="font-size: 138%;">{{local|link=Bluetooth Testing}}</span><br/>
How to help development<br/><br/>
<span style="font-size: 138%;">{{local|link=PBI9 Format|The PBI9 Format}}</span><br/>
Improved for 9.0 and beyond<br/><br/>
<span style="font-size: 138%;">{{local|link=PBI Build Testing}}</span><br/>
Getting ports turned into PBIs<br/><br/>
<span style="font-size: 138%;">{{local|link=PC-BSD{{RM}} TODO/{{upcoming}}|PC-BSD{{r}} {{upcoming}} Task List}}</span><br/>
Things to do for the next Version
{| cellspacing="0" cellpadding="0" align="center" style="text-align:center; margin:.5em; margin-top:.1em; margin-left:auto; margin-right:auto;" width="35%"<!-- TASKS ADVERT -->
| align="center" style="border: 2px solid #FF3333"|
<span style=" font-weight:bold; font-size: 138%;" height="50px">{{local|link=Tasks Looking for People}}</span><br />
How YOU can contribute
|<br /><span style="font-size: 138%;">{{local|link=Press And Legal|Press/Legal}}</span>
|Press, licensing and other queries
|[[category:PC-BSD{{RM}} Wiki]]


::[ {{orangelight|'''{{Word-warning}} zur Sicherheit'''}} für Benutzerinnen und Benutzer von nicht unterstützen Versionen von FreeBSD.]{{nbsp|7}}
{| cellspacing="0" cellpadding="0" align="center" style="margin-left:auto; margin-right:auto; top:-10px; border-collapse: collapse;"
<!-- DOCUMENTATION header-->
| align="center" style="text-align:center; margin:.5em; margin-top:.1em; border-bottom:1; font-weight:bold; font-size: 148%" width="28%" height="50px"|Dokumentation
<!-- PROJECTS header-->
| align="center" style=" text-align:center; margin:.5em; margin-top:.1em; border-bottom:1; font-weight:bold; font-size: 148%" width="28%" height="50px"|Projekte
<!-- DEVELOPMENT header-->
| align="center" style="text-align:center; margin:.5em; margin-top:.1em; border-bottom:1; font-weight:bold; font-size: 148%" width="28%" height="50px"|Entwicklung
<!-- DOCUMENTATION Column -->
| align="center" style="width:30%; padding:1em; text-align:center;" valign="top"|
<span style="font-size: 138%;">{{local|link=Testen zu Drahtlosen}}</span><br/>
Funktion und Kompatibilität von Treibern<br/><br/>
<!-- <span style="font-size: 138%;">{{local|link=Testen zu Spielen}}</span><br/>
Herausfinden was funktioniert und wie<br/><br/> -->
<span style="font-size: 145%;">{{local|link=PC-BSD{{RM}} Users Handbook/{{release}}|PC-BSD{{r}} Benutzungshandbuch}}</span><br/>
Veröffentlichung im Wiki zur Ausgabe ({{release}})<br/><br/>
<span style="font-size: 145%;">{{local|link=PC-BSD{{RM}} Users Handbook|Bücherregal im Wiki}}</span><br/>
vorherige Veröffentlichungen im Wiki<br/><br/>
<span style="font-size: 138%;">{{local|link=Pkgsrc in PC-BSD|Pkgsrc in PC-BSD{{r}}}}</span><br/>
Entdecken des Potentials von pkgsrc von NetBSD<br/><br/>
<span style="font-size: 138%;">{{local|link=Turn FreeBSD into PC-BSD{{RM}}|Wandeln FreeBSD{{r}} in PC-BSD{{r}}}}</span><br/>
Anleitung zum Umbau?<br/><br/>
<span style="font-size: 138%;">{{local|link=:Category:Troubleshooting|Fehlerbehebung}}</span><br/>
Lösen von einigen Problemen<br/><br/>
<span style="font-size: 138%;">{{local|link=Finding Help/{{release}}|Wo zu finden ist}}</span><br/>
Verschiedenste Quellen für Unterstützung<br/><br/><!--
<span style="font-size: 138%;">{{local|link=Press And Legal|Presse/Rechtliches}}</span><br/>
Presse, Lizenzierung und andere Anfragen -->
<!-- PROJECTS Column -->
| align="center" style="width:31%; padding:1em; text-align:center;" valign="top"|
<span style="font-size: 138%;">{{local|link=Warden{{RM}}/{{release}}|Warden{{r}}}}</span><br/>
Ein Werkzeug zur Verwaltung von Jails<br/><br/>
<span style="font-size: 138%;">{{local|link=PBI Manager/{{release}}|Verwaltung von PBI}}</span><br/>
Ein Werkzeugkasten für die  Kommandozeile<br/><br/>
<span style="font-size: 138%;">{{local|link=PCDM}}</span><br/>
Die Verwaltung zum Anmelden von PC-BSD<br/><br/>
<span style="font-size: 145%;">{{local|link=PC-BSD{{RM}} Users Handbook/{{upcoming}}|Dokumentation zu PC-BSD{{r}}}}</span><br/>
in der Entwicklung befindliche Version des Handbuchs<br/><br/>
<span style="font-size: 138%;">{{local|link=Errata|Fehlerverzeichnis des Handbuches}}</span><br/>
Berichtigungen nach der Veröffentlichung<br/><br/>
<span style="font-size: 138%;">[ Seite zu Ideen bei FreeBSD{{r}}]</span><br/>
Konzepte für mögliche Entwicklung<br/><br/>
<span style="font-size: 138%;">[ Seite zu Ideen für WLAN bei FreeBSD{{r}}]</span><br/>
Konzepte für mögliche Entwicklung<br/><br/>
<!-- DEVELOPMENT column-->
| align="center" style="width:30%; padding:1em; text-align:center;" valign="top"|
<span style="font-size: 138%;">[ PC-BSD{{r}} Trac]</span><br/>
Quellen, Berichte oder Anfragen<br/><br/>
<span style="font-size: 138%;">{{local|link=Become a Developer/{{release}}|Werde Entwicklerin oder Entwickler}}</span><br/>
Wie mit Code geholfen werden kann<br/><br/>
<span style="font-size: 138%;">{{local|link=EasyPBI2/{{release}}|EasyPBI2}}</span><br/>
Vereinfachung des Prozesses zu Erstellung von PBI<br/><br/>
<span style="font-size: 138%;">{{local|link=Testen von Bluetooth}}</span><br/>
Wie beim Entwickeln geholfen werden kann<br/><br/>
<span style="font-size: 138%;">{{local|link=PBI9 Format|Das Format PBI9}}</span><br/>
Verbessern von 9.0 und danach<br/><br/>
<span style="font-size: 138%;">{{local|link=Testen des Bauens von PBI}}</span><br/>
Gewandelt bekommen von Ports in PBIs<br/><br/>
<span style="font-size: 138%;">{{local|link=PC-BSD{{RM}} TODO/{{upcoming}}|PC-BSD{{r}} {{upcoming}} Liste von Aufgaben}}</span><br/>
Dinge, die für die nächste Version gemacht werden
{| cellspacing="0" cellpadding="0" align="center" style="text-align:center; margin:.5em; margin-top:.1em; margin-left:auto; margin-right:auto;" width="35%"<!-- TASKS ADVERT -->
| align="center" style="border: 2px solid #FF3333"|
<span style=" font-weight:bold; font-size: 138%;" height="50px">{{local|link=Aufgaben, die nach Leuten brauchen}}</span><br />
Wie DU mitwirken kannst
|<br /><span style="font-size: 138%;">{{local|link=Press And Legal|Presse/Rechtliches}}</span>
|Presse, Lizenzierung und andere Anfragen
|[[category:PC-BSD{{RM}} Wiki]]

BlueTooth GUI Discussion

Talk:BlueTooth GUI Discussion 



Game Testing

Talk:Game Testing 

Google Summer of Code 2011

Talk:Google Summer of Code 2011 



PBI Build Testing

Talk:PBI Build Testing 

PBI9 Format

Talk:PBI9 Format 

PC-BSD version task list

Talk:PC-BSD version task list 

Pkgsrc in PC-BSD

Talk:Pkgsrc in PC-BSD 

Press And Legal

Talk:Press And Legal 

Tasks Looking for People

== Translation of the Handbook - ideas from left field ==
Is it possible to have a dual-pane wiki?
In this arrangement, the left pane would always be the English version, and the right pane would be an identical but translated version. This might allow earlier access for the translators while continuing access to further the changes to the original. It could help in some cases where the original English is not worded clearly enough to allow a coherent translation. To further this concept would be similar to the Google translate how it highlights on mouse-over the words/phrase that are meant to be equivalent. Of course, being that any page might not be finalized until the system itself has been frozen, it may mean more repeated work but then with anything in transition it implies continued work.
✔ Yes. There is a Mediawiki extension which enables such a feature.
A cvsup sort of situation
This could be an alternative to the previous thought, or perhaps used in conjunction with it. This perceived solution is to allow quicker updates specific to the translation process. This way the entire handbook that the translator works with is kept current locally and also remotely.
Dual language pdf?
How is the conversion to pdf handled? Could this be configured to have each set of facing pages be, left English and right its translation or blank for editing? This is functionally identical to the dual-pane wiki concept above, but would both more easily mesh with the cvs idea and a local/remote environment.
This is to say that a nearly constant internet connection would not be required. It would only be necessary to update periodically.
Also, though I do not propose any official translation to 'Swedish chef,' the concept of encheferization may be helpful as described at wikipedia below.
Whereas it could not be expected that a test team would know every language to which a product might be aimed, by translating the parts that were supposed to be internationalized through the encheferizer to produce a localized version for Swedish Chef speakers, testers could immediately spot mistakes in the internationalization – parts that had been missed – as anything that had not been localized (encheferized) would show up in the language of the original author of the text. All the same, a tester would be able to test the product functionally, as it takes little language skill, and no software, to be able to decheferize the text: its meaning is clear even when encheferized.

Well.. those are some thoughts I had rattling in my ballpark :) Translation of the handbook may not be going slowly but it gives me that impression. I hope that this could be done more easily or more efficiently, and also address the possible lack of a current translated handbook especially for those testing but not English fluent.

--Tigersharke 22:29, 12 April 2011 (PDT)

for tigersharke

1. kinda: (??) (!)

2. Obviously... svn. just not enabled yet.

3. the pdf export? There's an option for that on pdf to do just that. However, I prefer that the user download the pdf of the locale handbook, instead of doing that. To parse the other language pages and publish the pdf, there's another extension for that.

4. Use the wiki api to connect to external editors. update via svn or the regular method.

5. will learn

for now, read the mediawiki documentation and watch youtube videos

PS with love and concern --Bebuxe 22:33, 27 July 2011 (PDT)



Wireless Testing


I am surprised no one has used this discussion page to talk about stuff in the wireless section. Even if you have doubts something works. Well for the first post I will confirm on x86 bwn-firmware-kmod works for bcm4311. I will try later on on amd64 arch of pcbsd when i reinstall the os for tutorial purposes (and that will be when i get a decent manual focusing camera that is good on close ups (even extreme ones)). Unless you like to share another method of doing so without rewiteing on my /dev/ada0 . Well until later!


I have tested the ndis driver for RTL8185 on i386. Don't use the most recent version of the driver, I could not get it to work. Instead use XP version 1.10, It is 290,944 bytes in size. Could not get it to automatically initialize the device at boot time, I have to manually load it. I'll be looking into remedying that. You might also have to manually configure your network settings as the graphical network manager did not work for me. I'll be testing it on amd64 once I download and install it. Until then Happy Wireless Configuring!

Just finished setting up amd64 system. XP64 driver version 1.10 does work (using it now). Driver is 385,536 bytes in size (before conversion). Follow the same procedures as the i386 driver to set it up.


Double fault panic with NDIS drivers

In case you encounter double fault panic when loading NDIS drivers that most likely point to small KSTACK_PAGES. Some Windows NDIS(r) drivers expect much bigger stack. On FreeBSD i386 KSTACK_PAGES is only 2, on FreeBSD amd64 it is 4. Increasing it to 12 and recompiling kernel(not just ndis modules) should be enough.

To change KSTACK_PAGES in your custom kernel add following line:

option KSTACK_PAGES 12

Page edits to make

Where 'this' as a link is used for a pastebin location that contains things such as lines to add to loader.conf, the content ought to be txtboxed (if possible, otherwise inline) instead of the link.

test for prior edit error






PC-BSD's Goals and Features

Talk:PC-BSD's Goals and Features 

What's New in 9

Talk:What's New in 9 

PC-BSD Releases

dru@ I really hate the layout of this page :-)

Also, the release list needs to point to the wiki copy, not the original URL as these are now deprecated. Where did you get the notes to make the wiki copies?

Dru: The original plan was for the links to be on the righthand side and be mostly static, with the content of the remaining space be the release notes. The release note content from the olden days is via the wayback machine. The links didn't get switched because some things were not available from the wayback machine, I couldn't do what i wanted as far as having the release notes become the main content of the page, and I guess I kinda shelved this.

--Tigersharke 10:01, 6 July 2011 (PDT)

dru@ I actually like the idea of having a separate page for each release notes on the wiki--makes it easy to link to from other sites and in theory the URL won't change, unlike on the website. There is a way to suck the info out of the database for the old website backup if wayback won't find them.

Dru: I think I was also sidetracked by something I could succeed at, the pretty tables in various places in the wiki. I might try looking around on other wiki sites to see how others have done things. The help pages for the wiki markup are useful, but not usually specific enough- certainly not where examples to match my crazy ideas are concerned. :) I *think* I may have gotten most of what is available via wayback machine.. all should be marked with category:historical.

--Tigersharke 20:08, 6 July 2011 (PDT)

Actually working on it currently.. try staging_area1 and template:testing1 ..I may have finally brainstormed how to accomplish what I wanted. --Tigersharke 00:53, 7 July 2011 (PDT)

"The change logs for each PC-BSD® release are" not "available online"


All the links ($number) are broken. :-(

My try to replace with wasn't successful. Damn!

Does anyone can help to fix it?

--Rg 18:15, 12 September 2012 (PDT)

PC-BSD for Linux Users

Found a source for some info to include in this section:

Unix Toolbox

Started with more necessary/common commands that have nearly identical results, but are invoked differently.

--Tigersharke 05:08, 24 June 2011 (PDT)

Since tigersharke asked, here is the link to the freebsd article for linux users to migrate

it's at anyone's discretion how that URL will be used in this wiki page. so use it wisely. --"What may be obvious to you, may not be obvious to others. That's why we have to write about them." 23:12, 17 July 2011 (PDT)

Other links to similar pages (added):

lsdev vs. dmesg

I have been a full-time Linux user for five years. I have never heard of lsdev, and typing it at the command line (both as normal user and as root) on my Debian 6.0 system produces a command not found error, yet typing dmesg spits out the expected hardware-related kernel messages. I have always used dmesg regardless of distribution (some Debian based, some based on other distributions, some independent), and have never gotten a command not found error. Since I have not used any of the BSDs (I plan to when I can replace my dead hard disk), I cannot say if dmesg exists in PC-BSD, so I do not feel comfortable editing the table. Piki 15:23, 22 January 2012 (PST)

A storage place for this info which has vastly changed.


If you're comfortable with the command line, you may find that some of the commands that you are used to have different names on BSD. Table 1.4c lists some common commands and their equivalents.

Table 1.4c: Common BSD and Linux Commands

PC-BSD Linux Result
dmesg dmesg
lsdev (Is this used anywhere?)
discover what hardware was detected by the kernel
sysctl dev cat /proc/devices display configured devices
pciconf -l -cv lspci -tv show PCI devices
dmesg | grep usb lsusb -tv show USB devices
kldstat lsmod list all modules loaded in the kernel
kldload <module> modprobe <module> load a kernel module for the current session
pbi_add -r <pbiname> rpm -i <package>.rpm install software from the command line
sysctl hw.realmem cat /proc/meminfo hardware memory
sysctl hw.model cat /proc/cpuinfo CPU model
sysctl hw.machine_arch uname -m CPU Architecture
sysctl hw.ncpu getconf _NPROCESSORS_ONLN number of CPUs
uname -vm lsb_release -a
cat /etc/*release
cat /etc/*version
get release version information
gpart show fdisk -l
parted -l
show device partition information
fuser lsof list IDs of all processes that have one or more files open

Pre-Installation Tasks

Talk:Pre-Installation Tasks 

Migrating to PC-BSD

Talk:Migrating to PC-BSD 

Minimum Hardware Requirements

Talk:Minimum Hardware Requirements 

Hardware Compatibility

== Firewire issue on some motherboard models ==

Not sure where to put this, right now:

Trouble booting 8.2 with motherboard model "Gigabyte GA-X58A-UD (revision 1)" is fixed by disabling the built-in Firewire from BIOS. The error message at boot is "run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config" and seems to be an old issue also affecting 7.2 since May. Also, since the exact trouble does not seem to have been traced, the above motherboard had an "intel core i7" processor installed.

Do you know if this is still an issue in 9.0 or has it been fixed?

Nope. I don't know that it has been corrected, but I think I may have still seen mention of the above as a solution. We'll have to check again to see if fixed in the RCs.

I had posted the firewire issue here that someone else had. I hope those who have the firewire trouble can be contacted. :)

Likely hardware notes for this upcoming release (currently 404):


It would be helpful to have any idea what some of the errors these various problems give as output, even if it is a panic shortly after an attempted boot. Knowing what the problem looks like in those situations where the hardware may not be fully known, would be a great help in making suggestions for possible fixes- and also might help with generalizing with errors that have similar solutions.

A truly odd situation with CQ62-410us compaq/hp laptop which fails due to some kind of apparent BIOS error- pressing escape in order to cause a boot device selection of DVD seems to solve the problem and allow boot to continue. Reference forum post near the end, last 2-3 comments,

Some have issues with suspend ob lind close which may be solved by an edit to /boot/loader.conf

#trying to disable suspend on lid close

Partitioning the Hard Drive

Talk:Partitioning the Hard Drive 

Obtaining PC-BSD

This will need to be adjusted to a new hash checking program when sha256 replaces md5. Md5deep at is compatible with Windows(7, Vista, XP, 2003, 2000), Mac OS X(DarwinPorts, Fink), Linux (Ubuntu, Fedora, Gentoo, Slackware), and FreeBSD, plus it has been updated recently.

--Tigersharke 19:58, 7 April 2011 (PDT)


On (my) Linux the command line tool is md5sum. Maybe the text can be changed to "md5 or md5sum".
✔Thanks for the comment, page adjusted.--Tigersharke 03:36, 1 February 2012 (PST)

Burning the Installation Media

==helpful for USB sticks==
  • no need to zero the entire thing, can be a limited zero that will be as effective- dd if=/dev/zero of=/dev/usbstick bs=1024 count=10
  • If KDE or Dolphin or Device Notifier succeed to mount a USB stick but you cannot unmount it, even when you are not actively using it, switch to root and then issue the shell command.
  • A USB stick can be subdivided as any other HDD could: first gpart create, then newfs. So, gpart create -s MBR /dev/usbstick then gpart add -t freebsd -s <size you want> /dev/usbstick and finally, mount -t ufs /dev/usbstick /mount/point. If a USB stick might be used for an installer image, one slice could be 5120M and the remaining space is chosen by leaving off the size designation, such as gpart add -t freebsd /dev/usbstick. To use the first partition of the usb stick for the image, use dd if=<image> of=/dev/da0s1 bs=512M.
  • Dolphin/Device Notifier caveat: It may allow a mount point within /media to be created, but it is possible that the ownership or permissions could be wrong. Best case is that /media/mountname is owned by you and wheel group. chown username:wheel /media/mountname.
  • Live media caveat: This method may not be compatible with booting the usb on any random system. In that situation, simply zero and then dd the image to the stick. Perhaps if the BSD boot selector is added it may work, but that has not yet been verified.

Of course the above is generic and some adjustments are needed.

PC-BSD Live Mode

Talk:PC-BSD Live Mode 

Using VirtualBox

Talk:Using VirtualBox 

Installing PC-BSD

Talk:Installing PC-BSD 

Starting the PC-BSD Installation

Talk:Starting the PC-BSD Installation 

Language Selection Screen

== Possible feature request: time server configuration ==

Some may recognize the following from a pc-bsd testing mailing list entry.

I am wondering about how we could include configuration for ntpd (ntp.conf) in a way that is more specific to the localization setting chosen by the user during installation. I am also thinking that this could be set automatically without interaction or only to choose a more specific server.

We have the ntp.conf file which includes the FreeBSD time server pools, but also in there is mention of how specific country time server pools could be defined, which I did manually as in the snippet below: ( 'us' had been 'CC' )

 #server iburst maxpoll 9
 #server iburst maxpoll 9
 #server iburst maxpoll 9
 #server iburst maxpoll 9

 # If you want to pick yourself which country's public NTP server
 # you want sync against, comment out the above servers, uncomment
 # the next ones and replace CC with the country's abbreviation.
 # Make sure that the hostnames resolve to a proper IP address!
  server iburst maxpoll 9
  server iburst maxpoll 9
  server iburst maxpoll 9

The site seems to suggest that time server pools can be chosen in varying degrees of exactness, from worldwide down to continent down to subcontinent/country.

Potentially it could be arranged similar to and there seems to be enough space for inclusion here

In my opinion, it may be best to keep the numbers of questions or options and configurations during installation to a minimum. I see the potential for this time server pool to be chosen automatically, based upon the user's choice of localization.. at least it seems perfectly reasonable to me.

So, anyone who would be implementing this or has knowledge of what is involved, is welcomed/encouraged to chime in.. I suppose this is at heart a feature request/suggestion.

--Tigersharke 11:42, 12 April 2011 (PDT)

Using Alt when window is to large for screen.

The installer window is to big to fit in some smaller screens. The result is you can't see the buttons at the bottom of the window.

The simple solution is that you can move the window by holding Alt and using the mouse. You can also use Alt+N for the Next button etc.

I think a note about this in the handbook should be included because if you don't know about it your stuck.

✔ Thanks for the suggestion. The above addition has been made to the wiki page, near the bottom. --Tigersharke 16:49, 2 February 2012 (PST)

Keyboard Selection Screen

Talk:Keyboard Selection Screen 

System Selection Screen

== Post install changes ==
  • What would be the process of adding or changing window managers/environments?
  • Is there an automated or GUI method outside of the initial install?
  • Are other window managers/environments added via PBI or Ports or just the installer?

There should be a place in the wiki to address this situation. It is possible that someone with limited understanding could choose only one window manager and then decide later to add another or switch from one to another. In 8.2 it is an involved process and depending upon what is chosen, it can cause conflicts or instability. In 9.0 the installer offers further options during install and multiple selections can be made.

--Tigersharke 16:29, 13 May 2011 (PDT)

Listing of Desktop/window environments

Is the order of the desktop/window environments given as they are listed on the interface? If XFCE is meant to be seperate from the 'unsupported/expert' section, perhaps it should be mentioned above that.

--Tigersharke 21:40, 22 June 2011 (PDT)


Since fluxbox is included (even with v8.2) I am curious where it is actually mentioned. If it is not indicated anywhere, someone might get the impression that it is not an option- even though it is already installed by default.

--Tigersharke 20:45, 5 September 2011 (PDT)

Yes, this is in my queue to make those 2 pages clearer on how fluxbox fits in. Drulavigne Sep. 13

Disk Selection Screen

Talk:Disk Selection Screen 

Users Creation Screen

Talk:Users Creation Screen 

Desktop Selection Screen

== Post install changes ==
  • What would be the process of adding or changing window managers/environments?
  • Is there an automated or GUI method outside of the initial install?
  • Are other window managers/environments added via PBI or Ports or just the installer?

There should be a place in the wiki to address this situation. It is possible that someone with limited understanding could choose only one window manager and then decide later to add another or switch from one to another. In 8.2 it is an involved process and depending upon what is chosen, it can cause conflicts or instability. In 9.0 the installer offers further options during install and multiple selections can be made.

--Tigersharke 16:29, 13 May 2011 (PDT)

Listing of Desktop/window environments

Is the order of the desktop/window environments given as they are listed on the interface? If XFCE is meant to be seperate from the 'unsupported/expert' section, perhaps it should be mentioned above that.

--Tigersharke 21:40, 22 June 2011 (PDT)


Since fluxbox is included (even with v8.2) I am curious where it is actually mentioned. If it is not indicated anywhere, someone might get the impression that it is not an option- even though it is already installed by default.

--Tigersharke 20:45, 5 September 2011 (PDT)

Yes, this is in my queue to make those 2 pages clearer on how fluxbox fits in. Drulavigne Sep. 13

Applications Selection Screen

Installation Summary Screen

Talk:Installation Summary Screen 

Installation Progress Screen

Talk:Installation Progress Screen 

Installation Finished Screen

Talk:Installation Finished Screen 

Post Installation

Talk:Post Installation 

Installation Troubleshooting

Not sure exactly how/where to place this, but it ought to be added in some form.

Error 19

the background

(from a FreeBSD forum post)

In any event, booting to FreeBSD from Grub now leads to


Mounting from ufs:/dev/ad4s3a failed with error 19

and thereafter to a mountroot prompt. Typing '?' at the mountroot prompt provides no GEOM managed disk devices whatsoever.

At this stage, I created a re-install CD of FreeBSD 9.0-RELEASE and booted from it. However, the boot ended with


Mounting from cd9660:/dev/iso9660/FREEBSD_INSTALL failed with error 19

and then the mountroot prompt. Once again, typing a '?' at the prompt showed no GEOM managed disk devices.

the solution

(from a blog post)

Here's where I found it and all that is need is to open the loader prompt during the CD/DVD/USB boot (by pressing 2 or ESC) and adding the following line:

   set debug.acpi.disabled ="hostres"

and then booting with


Once the USB key has booted you can add the line

   debug.acpi.disabled ="hostres"

to /boot/loader.conf, if you intend to use the key again. In any event, once you have installed FreeBSD 9.0-RELEASE, you still need to add this line to /boot/loader.conf.

other refs

Also documented in Open issues of FreeBSD v9.0R errata.

Advanced Installation Topics

Talk:Advanced Installation Topics 

Use PC-BSD Installer to Install FreeBSD

Talk:Use PC-BSD Installer to Install FreeBSD 

Install PC-BSD Over a Network

You can use a PC with turn up Apache Server (from FreeBSD) for install PCBSD full in netbook [DHCP](if you haven got 4GB pendrive some reason)

You need...

2 PC (netbook and desktop) 1 PCBSD Full .iso image or burned DVD 1 PCBSD bootonly USB .iso image 1 USB key 1 Router with 2 entries

Im using FreeBSD-8.0-p6/amd64 with Apache (www/apache13)

Preparing the Server

Mount the .iso image or DVD burned (This option is high recommended if you install PCBSD over a network with too PCS, because, the file is local, is not CDROM. The CDROM driver pains and very work slow installation (Read, send the information, work very slowly)

  1. mdconfig -a -t vnode -f /directory_you_have_a_isoimage.iso -u 0
  2. mount -t cd9660 /dev/md0 /mnt

Mount the DVD burned (X is the cdrom device)

  1. mount -t cd9660 /dev/acdX /mnt

Install Apache

  1. cd /usr/ports/www/apache13 && make install clean

Edit the /usr/local/etc/apache/httpd.conf (change the DocumentRoot to mount DVD or .iso image and port)

DocumentRoot "/usr/local/www/data" -> DocumentRoot "/example"

Run apache

  1. /usr/local/sbin/apachectl start

See you local server ip

$ ifconfig -a

Preparing the netbook

Create a PCBSD live-USB

Download the bootonly-USB.iso image and create the live-USB using dd command.

  1. dd if=PCBSD-x86-bootonly-USB.iso of=/dev/da0 bs=10240 conv=sync

Setting your BIOS, USB first boot and run the live USB

Note: If you experimental ethernet card not turn up in the Auto-DHCP of install process, you can turn up ethernet card from # sysinstall in Configure->Network->Interfaces In the network installation proccess you must set your Local IP+Port and the directory "/example" in HTTP mode Example: FreeBSD Machine

  1. mount -t cd9660 /dev/acd0 /mnt
  2. cd /usr/ports/www/apache13
  3. make install clean
  4. vi /usr/local/etc/apache/httpd.conf
DocumentRoot "/mnt"
  1. /usr/local/sbin/apachectl start
  2. ifconfig -a
  1. dd if=PCBSD-USB-bootonly.iso of=/dev/da0 bs=10420 conv=sync

Netbook In Network Parameters to install PCBSD (over network)



Using a Custom Partition Layout

ZFS raidz pool install attempt.  Failed.

Attempting to create an rpool in PC-BSD using the 8.1 installer. This doesn't work, but here's what I tried - perhaps it'll work in the 9.x release

So, my machine is a Dell Optiplex 765 with 3 sata 250G drives. I'd like to get these drive all in a single raidz as I find this to be a suitable setup. Booting from a RAIDZ works as this has been done many times over in the FreeBSD 8.1 release.

What I tried to do was to boot the PC BSD disk and have it see my setup and just install to that zpool. Again, this doesn't work. I don't know how to make the gui pick up the zpool.

Here's the results of 'gpart show'

gpart add -b 34 -s 128 -t freebsd-boot ada0
gpart add -b 34 -s 128 -t freebsd-boot ada1
gpart add -b 34 -s 128 -t freebsd-boot ada2
gpart add -b 162 -s 3145728 -t freebsd-swap -l swap0 ada0
gpart add -b 162 -s 3145728 -t freebsd-swap -l swap1 ada1   # I rarely if ever see it dip into swap, but spreading
gpart add -b 162 -s 3145728 -t freebsd-swap -l swap2 ada2   # the swap over 3 drives can't hurt.
gpart add -b 3145890 -s 485244702 -t freebsd-zfs -l disk0 ada0
gpart add -b 3145890 -s 485244702 -t freebsd-zfs -l disk1 ada1
gpart add -b 3145890 -s 485244702 -t freebsd-zfs -l disk2 ada2

these were joined together with zpool create -f rpool raidz /dev/gpt/disk0 /dev/gpt/disk1 /dev/gpt/disk2

So, I was expecting the SysInstaller to find this setup and be able to use it. This isn't the case.

I would have liked for sys installer to help me out with the creation of raidz, but as such, it doesn't yet seem able to which is why I chose this route.

SysInstaller sees the slices on the drives, but doesn't seem to know what to do about them. The advanced setup presumes you want a bare drive, and doesn't show you the slices. I find this to be an incorrect assumption, as there might have been reasons for me to choose those begin marks. If i want the drive empty, I can pointy-clicky my way to deleting all the partitions.

Not sure if these are already fixed, or just plain invalid requests, but.. there it is.

ADD SECTION ON ZFS POOLS, MIRRORING At the moment the GUI portion of the installer is going to expect you to provide the raidz configuration you want from within it. For example, you would go to "custom partition", and from there create a new ZFS partition on ad0, at the bottom of the GUI, you'll be able to select your additional devices, such as ada1, ada2 for inclusion into the "raidz" pool. That should get you to an install similar to what you described. For 9 I have it on my list to improve the installer to more easily work with pre-existing partitioning, but its not in the current snapshot yet

Disk Encryption

Talk:Disk Encryption 

Dual Booting

The option to install a boot loader during PC-BSD installation is no longer present in the GUI, hence the mods to the discussion around recovering from "accidental use" of that previously available option.

Unsure exactly how/where to fit this in:


From commandline:

boot0cfg -B ada0

Grub 2

I noticed the section on Grub 2 is a little out of date. The map command is a legacy command. In Grub 2, it was renamed to drivemap. Also, the device names changed slightly in Grub 2: the partitions of the hard drive are counted from 1 instead of 0: so, (hd0,msdos1) is the first partition of the first hard drive.

drivemap isn't actually needed to boot PC-BSD if it's on the second disk, at least for me. My menuentry is something like this:

menuentry "PC-BSD 9.1" {
insmod ufs2
set root=(hd1,msdos1)
chainloader +1

I have just gone through the pain of configuring a dual boot using Grub2 for PC-BSD 9.1. FWIW, here is my experience.

Computer HDD Setup

I have Debian Linux (wheezy) on the first primary partition, with PC-BSD on the second primary partition using the zfs filesystem. When I installed PC-BSD, I installed its bootloader which overwrote Grub2 on the MBR.

Recovering Debian Grub2

To re-install Grub2 on the MBR in a Debian system, the installation cd/dvd have the tools specifically built in. Google on the Debian Wiki and it directs you to the appropriate section of the Debian installation guide.

   Boot using the Debian Install Disk
   Advanced Options
   Recovery Mode
   You will progress through various screens which are the first part of the Debian Installer - don't worry too much because none of the info will be written to the disk.  Eventually ....
   A screen will present the available partitions - select the one you want to be the root partition.
   Select the menu entry to re-install Grub

Manual Menu Entries in Debian Grub2

Debian automatically builds the Grub2 config file " /boot/grub/grub.cfg" . There is no point editing it (and they warn you about this - it is a text file that you can read) because it is over-written the next time grub.cfg is created. Instead, if you look at the end of the file, you will see that they point you to a customisation file " /etc/grub.d/40_custom " . Open it in an editor (as superuser) and you can add your manual entries to the bottom. Save the file and then once again as superuser: " update-grub " This will incorporate your custimisations in a new grub.cfg file.

Adding PC-BSD to Grub2

The entry I eventually found was for me (after piecing things together) was:

    menuentry "PC-BSD 9.1" {
    set root='(hd0,2)'
    chainloader +1

"hd0,2" -

   0 stands for the first hard disk, because you count your disks from zero.
   2 stands for the second partition because you count your partitions from one.
chainloader +1  allows grub to go to the bootloader for PC-BSD which I installed initially if you remember and which is loaded at the start of the PC-BSD partition.

Finally, to change the timeout and default menu entries, I've written previously about this here:

Upgrading PC-BSD

Talk:Upgrading PC-BSD 

Creating an Automated Installation with pc-sysinstall

  1. We should include an example, even if it is relatively basic, to give context to the variables and how they would be used.
  2. It highly bothers me that '=' is shown to be part of the variable names here. An improved explanation along with the example mentioned above, would allow the table to be fixed (removal of the '=' from variable names.)

I have a sample pc-sysinstall.cfg that could be used, if you like. It's a little more complex than normal, but it does show how multiple network interfaces are configured:

# Sample configuration file for an installation using pc-sysinstall


# Set the disk parameters - 1st disk

# Set the disk parameters - 2nd disk

# Setup the disk label - 1st disk
# All sizes are expressed in MB
# Avail FS Types, UFS, UFS+S, UFS+J, ZFS, SWAP
disk0-part=UFS+S 1024 / 
disk0-part=SWAP.eli 2048 none
disk0-part=UFS+S 1024 /tmp
disk0-part=UFS+S 1024 /var
disk0-part=UFS+S 0 /usr
# Size 0 means use the rest of the slice size
# Do it now!

# Setup the disk label - 2nd disk
# All sizes are expressed in MB
# Avail FS Types, UFS, UFS+S, UFS+J, ZFS, SWAP
disk1-part=UFS+S 1024 /usr/src 
disk1-part=UFS+S 4096 /usr/local
disk1-part=UFS+S 0 /usr/ports
# Size 0 means use the rest of the slice size
# Do it now!

netSaveDev=em0 em1 

# Set if we are installing via optical, USB, or FTP

# List our components to install

# Set the root pass

# Setup our users
userComment=Demo User

# Set up date/time
runCommand=cp /usr/share/zoneinfo/EST5EDT /etc/localtime
runCommand=touch /etc/wall_cmos_clock
runCommand=adjkerntz -a

# Install packages required for VMware Tools installation/configuration
runCommand=pkg_add -r compat6x-amd64
runCommand=pkg_add -r perl
runCommand=pkg_add -r pcre
runCommand=pkg_add -r puppet
runCommand=pkg_add -r sysrc

# Fetch/install VMware Tools
runCommand=fetch -o /tmp/vmtools.tar.gz
runCommand=zcat /tmp/vmtools.tar.gz | tar -C /tmp -xvf -
runCommand=/tmp/vmware-tools-distrib/ -d
runCommand=rm -rf /tmp/vmware-tools-distrib
runCommand=/usr/local/sbin/sysrc puppet_enable=YES
# Generate the certificate to be signed by the master
runCommand=/usr/local/bin/puppet agent -t

--Glarkin 07:11, 22 August 2012 (PDT)



A fluxbox page does exist, but is it considered supported or similar to Awesome and therefore grouped with it? Fluxbox is not mentioned on this page, but it is also included by default. (This is not the only talk page I mentioned fluxbox)

--Tigersharke 20:53, 5 September 2011 (PDT)






== page about PC-BSD in the wiki of LXDE ==

Does anyone can place it right (in the text of the article)?

--Rg (talk) 12:03, 7 September 2013 (PDT)

Nice! I am not sure it can be easily added to the text but I am trying to create a way to add it among the references without it needing to be part of the content above them.

Tigersharke (talk) 14:33, 7 September 2013 (PDT)















Window Maker

Talk:Window Maker 

Installing Applications and Keeping PC-BSD Updated

Another item to consider is installation of rpm files.

Some things that are designed as rpm may load as from ports and install in their proper location. However, other items (most notably flash) are an rpm file downloaded from a 3rd party site which requires an understanding of how to get it installed and/or where to drop it so it will get recognized.

Using AppCafe™

Talk:Using AppCafe™ 

PBI Manager

Clarity issue?

Umm.. between 'PBI Module builder guide' and 'PBI Manager' wiki pages, there seems to be some disagreement of duplicated topics- specifically the pbi.conf file. One may be incomplete, therefore only tells of like 5 variables to use within the pbi.conf file, while the other shows the firefox pbi.conf file containing those and more stuff.


My *primary* need, is to know how to build a PBI from a port, and have it use the options I choose (as 'make config' would allow) if building directly from ports. I have tried unsuccessfully to get Quassel (irc client/core/mono suite) to successfully build just the mono[lithic] version.

--Tigersharke 01:03, 26 September 2011 (PDT)

Answer via mailing list:

At this time, you would need to add additional ports or make options into a PBI module by hand.
For your example:
1) Use EasyPBI to create a module for mail/claws-mail
2) Open up (home-dir)/EasyPBI/Modules/claws-mail/pbi.conf
3) Edit the PBI_MAKEOPTS line to read: [PBI_MAKEOPTS="WITH_SPAMASSASSIN=yes"] (quotes needed)
4) Save the file and then use that module to build your PBI with EasyPBI
(in our example freshports only lists SPAMASSASSIN as a make option, the actual makefile shows the actual variable that needs to be set is WITH_SPAMASSASSIN).

--Tigersharke 01:04, 7 February 2012 (PST)

Update Manager

Talk:Update Manager 

Control Panel

Ports Jail

==System vs Jail ports tree confusion==

I believe the system manager needs some adjustment. There needs to be better clarification. We give two options: One under Ports Console, 'Fetch ports tree' and under System tasks advanced users,'Fetch system ports tree'. The first option needs to be explicitly defined as for the jail, such as "Fetch ports tree for jail" and the other may be fine as is.. but myself and others have not realized the distinction until the tree is not setup when trying to use the standard FreeBSD ports tree to install something. Perhaps if the ports jail is the only option/action under that 'Ports Console' heading, the heading could also be revised or removed. --Tigersharke 20:26, 8 July 2011 (PDT)

Service Manager

Talk:Service Manager 

System Manager

Talk:System Manager 

User Manager

Talk:User Manager 





Network Configuration

Recently a user wanted to be sure that Ethernet over USB worked, which leads to these:
  • What drivers/kernel objects are loaded on the 'live' pseudo-install?
  • A step by step to troubleshoot the 'live' pseudo-install such as to enable other features or devices.

  • Internet connection sharing is not specifically named and does not seem to be described.
  • How to setup a ether to wifi hotspot/sharing is also not mentioned.

Freebsd handbook 32.3.5 describes this configuration but its a reasonable expectation for a laptop to be able to share out its wifi while attached by ethernet cable.

This section should no longer be needed in 9.0 as both modules are included with the base system.

bwn(4) and bwi(4) Drivers

Due to licensing restrictions, the bwn and bwi drivers require that their firmware is compiled on the individual's computer. This means that Broadcom BCM43xx IEEE 802.11b/g wireless network adapters will not “just work” after installing PC-BSD.

To compile the firmware, you will need to install both the ports tree and source on your PC-BSD system. You can do so by going to Control Panel -> System Manager. After inputting the administrative password, click on the Tasks tab, seen in Figure 7.7p:

Figure 7.7p: Using System Manager to Install Ports and Source


In the "System Tasks - Advanced Users Only" section, click "Fetch System Source" if /usr/src does not currently exist on your system.

In the "System Tasks - Advanced Users Only" section, click "Fetch System Ports Tree" if /usr/ports does not currently exist on your system.

Both src and ports are large so it will take a few minutes for each fetch to finish. When the fetch is finished, compile the firmware using the instructions for the driver that you need. You will need to be the superuser in order to compile the firmware.

For the bwn driver:

cd /usr/ports/net/bwn-firmware-kmod && make install clean

This will create two kernel modules:

  • bwn_v4_ucode module (used by most adapters)
  • bwn_v4_lp_ucode (used by low power PHY adapters)

It's a good idea to test which module is used by your adapter, so type:

kldload bwn_v4_ucode

If that command just gives your prompt back without an error, that is the correct module. If you receive an error, try loading the low power module instead which should just give you your prompt back without an error:

kldload bwn_v4_lp_ucode

Now carefully add the following two lines to /boot/loader.conf:


Note: replace bwn_v4_ucode_load="YES" with bwn_v4_lp_ucode_load="YES" if your adapter is a low power one.

For the bwi driver:

cd /usr/ports/net/bwi-firmware-kmod && make install clean

This will create the following kernel module:

  • bwi_v3_ucode.ko

To load the module:

kldload bwi_v3_ucode.ko

And carefully add the following line to /boot/loader.conf so the module will automatically load whenever you boot:


Firewall Manager

Talk:Firewall Manager 

Life Preserver

Talk:Life Preserver 


When prompted to enter the nic, it is rather less than explanatory, even with it being more spelled out as below. Is the interface name /dev/re0 or simply re0? A mouse-over of the ethernet or wifi icons in the system tray gives the detail "Device Name: /dev/re0". There is also no feedback on whether the correct information was given, though note the bad syntax caused by the omission of what is being used, in the last line.
Which network interface do you want to run jails on?
nic: input your interface name here
Using for jails

This may be more of an adjustment to the script, than a significant documentation change. Perhaps 'network device' may be better than nic. Entering simply re0 may in fact not work but there is no indication of it other than the entry not being explicitly acknowledged.

--Tigersharke 00:01, 19 April 2011 (PDT)

What is needed is re0 of /dev/re0, so if "/dev/" were already present on the input line for nic, it would add clarity.
The acknowledgement "Using X for jails" where X is absent, is an error that will be fixed.

--Tigersharke 21:00, 19 April 2011 (PDT)

Old Version with Ncurses Menu info

Thin Client

This darn bugger has the weird error, so i cannot edit all sections of it. 
Everything works fine for me. So I cannot see the problem. Sorry!

The wikipedia links need to be expanded to standard url form and placed within the citelink as described in the style guidelines.

--Rg 04:28, 25 July 2012 (PDT)

Common Tasks

== Other computers/networks ==

Somewhere there ought to be a section to detail how to configure interactions with other computers including other operating systems, especially across a local network, such as:

  • File sharing/serving
    • NFS - Is this available out of the box, or just configuration, or does it need to be installed also?
    • Samba - Needs to be installed from FreeBSD ports, and configured seperately.
  • Remote desktop
    • X - Possible but requires seperate additional configuration.
    • Windows/MS equivalent.
  • Media streaming
    • VLC - Possibly would work after installing on both machines?

--Tigersharke 16:02, 1 May 2011 (PDT)

Java, Flash, and Fonts

Talk:Java, Flash, and Fonts 







using the add-topic tab

test 2 :P

Windows Emulation

This is not specific to 'Windows Emulation' but it is a large list of emulation things for BSD, so it might be included somewhere..

FreeBSD emulators

--Tigersharke 16:57, 23 June 2011 (PDT)

Files and File Sharing


The KDE info found for samba

FreeBSD documentation for samba

Official Samba GUI info

The Official Samba How-To


The KDE info found for NFS

FreeBSD documenation for NFS

What may be the Gnome interfaces for both

Remote Desktop


X - Possible but requires seperate additional configuration.

Windows/MS equivalent (KDE, other window managers?)

Removing X section as too many variables: have to edit /usr/local/etc/gdm/custom.conf, make firewall rules, set display (which varies by shell), etc. Let's stick with the GUI utilities :-)

Some temporary links (or a temporary location for them)
One source of info
General X info at wikipedia
What seems to be the most related info in the FreeBSd handbook
Access X from windows
remote desktop

SSH Info

To allow a secure shell connection into your PC-BSD/FreeBSD machine:

Create an exception for the firewall:

  • Open the PC-BSD Control Panel
  • Open the 'Firewall Manager'
    • Select the 'Exceptions' tab
    • Click the 'Add Entry' button
      • Select 'ssh' from the 'service' dropdown which will auto-fill the port with 22
      • Adjust the interface to match your network device.
    • Select the 'general' tab
      • Click the 'restart' button

Enable the secure shell daemon

  • Open the PC-BSD Control Panel
  • Open the 'Service Manager'
    • Scroll down the list to 'sshd'
      • Click 'sshd'
      • Click the 'Enable Service' button
      • Click the 'start' button

To access your machine, from a shell prompt type: ssh <ip>
It will assume the current user account exists on the remote (your) machine.

Media Streaming

Talk:Media Streaming 

Video Conferencing

Talk:Video Conferencing 



Finding Help

Talk:Finding Help 

PC-BSD Forums

Talk:PC-BSD Forums 

IRC Channel

Talk:IRC Channel 

Mailing Lists

Talk:Mailing Lists 

FreeBSD Handbook and FAQ

Talk:FreeBSD Handbook and FAQ 

Social Media

Talk:Social Media 

Search and Portals

Talk:Search and Portals 

Other Resources

Talk:Other Resources 

Supporting PC-BSD

Talk:Supporting PC-BSD 

Become a Beta Tester

Talk:Become a Beta Tester 

Become a Translator

Talk:Become a Translator 

Become a Developer

Talk:Become a Developer 

Report Bugs

Talk:Report Bugs 

Submit PBI Requests

Talk:Submit PBI Requests 

Test PBIs

The site gives links (along the left side) which seem that they would point to the testing version of the PBI as:<portname>/

but the correct layout is:<portname>/ 

Create PBIs

Left this page blank rather than adding the NavHeader, because it looks like it will be a move or merge or something from there the content currently resides. 

Purchase PC-BSD Swag

Talk:Purchase PC-BSD Swag 

Host a Mirror

Talk:Host a Mirror 

Seed a Torrent

Yet to do on the page is to flesh out some basic instruction for the given programs, some screenshots- concept overall to be similar to 'Burning install media' page. 

Become an Advocate

Talk:Become an Advocate