PC-BSD Wiki - User contributions [en]

Convert a FreeBSD System to PC-BSD®

2013-06-17T08:32:33Z

Tigersharke:

<noinclude><translate>


{{NavHeader|back=Install a Server |forward=Using a Rolling Release|custompagename=Convert a FreeBSD System to PC-BSD{{R}}|custompagecategory=Convert a FreeBSD System to PC-BSD{{RM}}}}</noinclude>


Beginning in February, 2013, the PC-BSD® utilities dealing with software installation and upgrades were converted to [https://wiki.freebsd.org/pkgng pkgng], FreeBSD's Next Generation package management tool. Part of this change included the creation of a custom PC-BSD® package repository which contains all of the packages that can be built using pkgng. Since the FreeBSD project does not yet have an official pkgng repository, FreeBSD users who wish to use pkgng are welcome to use the PC-BSD® package repository.


This package repository contains a custom package, called ''pcbsd-base'', which can be used to easily convert an existing FreeBSD installation into a PC-BSD® desktop. It also contains a custom package called ''trueos-base'' which can be used to convert an existing FreeBSD installation into a TrueOS® server. The converted desktop will contain all of the graphical utilities that come with PC-BSD® and the converted server will contain all of their command line equivalents.


This section describes how to:


* Configure a FreeBSD or PC-BSD® system to use the pkgng repository.


* Convert a FreeBSD system to a PC-BSD® desktop.


* Convert a FreeBSD system to a TrueOS® server.

== Switching to the PC-BSD{{R}} pkgng Repository == 


If you are running PC-BSD® 9.1-RELEASE or FreeBSD 9.1, you will need to first install {{citelink|url=http://www.freshports.org/ports-mgmt/pkg/|txt=ports-mgmt/pkg}} as a port or package.


After installing pkg, run the command '''pkg2ng''' to import your existing package database from the old format to the new pkgng format.


Next, configure access to the PC-BSD® repository. Start by creating the file ''/usr/local/etc/pkg.conf'' with the following contents:


{{txtbox|box=packagesite: {{ftp}}ftp.pcbsd.org/pub/mirror/packages/9.1-RELEASE/amd64
PUBKEY: /usr/local/etc/pkg-pubkey.cert
PKG_CACHEDIR: /usr/local/tmp}}


Note that the ''packagesite:'' variable should be changed to a PC-BSD® mirror close to your geographic location. Additionally, ''9.1-RELEASE'' and ''amd64'' can be changed to indicate the release version and architecture you want to use. Click [http://www.pcbsd.org/getmirrors.php?url=packages here] to get a list of the available mirrors and package sets.


Next, download the repository's [http://trac.pcbsd.org/export/780f3da562b72643c04b47a59d277102a09abbca/src-sh/pc-extractoverlay/desktop-overlay/usr/local/etc/pkg-pubkey.cert public key cert file], and copy it to ''/usr/local/etc/pkg-pubkey.cert''.


The system is now configured and you now update your packages to the latest versions from the pkgng repository using the following command:


{{txtbox|box= '''pkg upgrade -fy'''}}


Depending upon what is already installed, you may have to resolve some error messages in order to successfully upgrade all packages.


To install and delete packages use the '''pkg''' command. This command differs in usage from the original package format version. You can learn more about how to use this command in [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/pkgng-intro.html Section 5.5.3 of the FreeBSD Handbook].

== Converting FreeBSD to a PC-BSD{{R}} Desktop == 


Once the repository configuration is complete, it is now easy to convert a FreeBSD system into a PC-BSD® desktop using the following commands as the superuser:


{{txtbox|box= '''pkg install -fy pcbsd-base'''
'''rehash'''
'''pbreg set /PC-BSD/SysType PCBSD'''
'''pc-extractoverlay desktop'''
'''pc-extractoverlay ports'''}}


Next, reboot the system and the PC-BSD® login manager will start, allowing you to login to the desktop. If you want the [Post Installation Configuration and Installation Troubleshooting |PC-BSD® display wizard and first boot wizards] to run first, run these commands before rebooting:


{{txtbox|box= '''touch /var/.runxsetup'''
'''touch /var/.pcbsd-firstboot'''
'''touch /var/.pcbsd-firstgui'''}}


If you are running FreeBSD 10-CURRENT, specify the PBI version to pull from. To do so, edit ''/usr/local/etc/pbi.conf'' and add this line:

{{txtbox|box=PBI_FBSDMAJOR: 9}}


{{note|icon64= If you are using NVIDIA video hardware, load the driver before rebooting into the display wizard by running the command '''pc-metapkgmanager add NVIDIA'''.}}

== Converting FreeBSD to a TrueOS{{R}} Server == 


If you wish to convert a FreeBSD server to TrueOS®, use the following commands:


{{txtbox|box= '''pkg install -fy trueos-base'''
'''rehash'''
'''pbreg set /PC-BSD/SysType TRUEOS'''
'''pc-extractoverlay server'''
'''pc-extractoverlay ports'''}}


The installation of the ''trueos-base'' package will install the following: [[PBI Manager]], the command line version of '''[[Warden®#Using the Command Line Version of Warden® | warden]]''', and the command line versions of most of the [[Control Panel]] utilities. You will find those utilities in ''/usr/local/bin/pc-*''. It also installs this {{citelink|url=http://trac.pcbsd.org/browser/pcbsd/branches/9.1/build-files/metapkgsets/warden/pkgset/base-system/ports-list|txt=list}} of additional shells and utilities.
</translate>
<noinclude>
{{refheading}}
[[category:Convert a FreeBSD System to PC-BSD®]]
[[category:Advanced Installation Topics]]
[[category:handbook]]
<languages/>
</noinclude>

Turn FreeBSD into PC-BSD®

2013-06-17T08:19:41Z

Tigersharke:

{{navHome|custompagename=Turn FreeBSD into PC-BSD{{R}}|custompagecategory=Turn FreeBSD into PC-BSD{{RM}}}}
{{:Convert a FreeBSD System to PC-BSD®}}
{{refheading}}

Convert a FreeBSD System to PC-BSD®

2013-06-17T08:18:30Z

Tigersharke:

<noinclude><translate>


{{NavHeader|back=Install a Server |forward=Using a Rolling Release|custompagename=Convert a FreeBSD System to PC-BSD{{R}}|custompagecategory=Convert a FreeBSD System to PC-BSD{{RM}}}}</noinclude>


Beginning in February, 2013, the PC-BSD® utilities dealing with software installation and upgrades were converted to [https://wiki.freebsd.org/pkgng pkgng], FreeBSD's Next Generation package management tool. Part of this change included the creation of a custom PC-BSD® package repository which contains all of the packages that can be built using pkgng. Since the FreeBSD project does not yet have an official pkgng repository, FreeBSD users who wish to use pkgng are welcome to use the PC-BSD® package repository.


This package repository contains a custom package, called ''pcbsd-base'', which can be used to easily convert an existing FreeBSD installation into a PC-BSD® desktop. It also contains a custom package called ''trueos-base'' which can be used to convert an existing FreeBSD installation into a TrueOS® server. The converted desktop will contain all of the graphical utilities that come with PC-BSD® and the converted server will contain all of their command line equivalents.


This section describes how to:


* Configure a FreeBSD or PC-BSD® system to use the pkgng repository.


* Convert a FreeBSD system to a PC-BSD® desktop.


* Convert a FreeBSD system to a TrueOS® server.

== Switching to the PC-BSD{{R}} pkgng Repository == 


If you are running PC-BSD® 9.1-RELEASE or FreeBSD 9.1, you will need to first install the {{citelink|url=http://www.freshports.org/ports-mgmt/pkg/|txt=port or package}}.


After installing pkg, run the command '''pkg2ng''' to import your existing package database from the old format to the new pkgng format.


Next, configure access to the PC-BSD® repository. Start by creating the file ''/usr/local/etc/pkg.conf'' with the following contents:


{{txtbox|box=packagesite: {{ftp}}ftp.pcbsd.org/pub/mirror/packages/9.1-RELEASE/amd64
PUBKEY: /usr/local/etc/pkg-pubkey.cert
PKG_CACHEDIR: /usr/local/tmp}}


Note that the ''packagesite:'' variable should be changed to a PC-BSD® mirror close to your geographic location. Additionally, ''9.1-RELEASE'' and ''amd64'' can be changed to indicate the release version and architecture you want to use. Click [http://www.pcbsd.org/getmirrors.php?url=packages here] to get a list of the available mirrors and package sets.


Next, download the repository's [http://trac.pcbsd.org/export/780f3da562b72643c04b47a59d277102a09abbca/src-sh/pc-extractoverlay/desktop-overlay/usr/local/etc/pkg-pubkey.cert public key cert file], and copy it to ''/usr/local/etc/pkg-pubkey.cert''.


The system is now configured and you now update your packages to the latest versions from the pkgng repository using the following command:


{{txtbox|box= '''pkg upgrade -fy'''}}


Depending upon what is already installed, you may have to resolve some error messages in order to successfully upgrade all packages.


To install and delete packages use the '''pkg''' command. This command differs in usage from the original package format version. You can learn more about how to use this command in [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/pkgng-intro.html Section 5.5.3 of the FreeBSD Handbook].

== Converting FreeBSD to a PC-BSD{{R}} Desktop == 


Once the repository configuration is complete, it is now easy to convert a FreeBSD system into a PC-BSD® desktop using the following commands as the superuser:


{{txtbox|box= '''pkg install -fy pcbsd-base'''
'''rehash'''
'''pbreg set /PC-BSD/SysType PCBSD'''
'''pc-extractoverlay desktop'''
'''pc-extractoverlay ports'''}}


Next, reboot the system and the PC-BSD® login manager will start, allowing you to login to the desktop. If you want the [Post Installation Configuration and Installation Troubleshooting |PC-BSD® display wizard and first boot wizards] to run first, run these commands before rebooting:


{{txtbox|box= '''touch /var/.runxsetup'''
'''touch /var/.pcbsd-firstboot'''
'''touch /var/.pcbsd-firstgui'''}}


If you are running FreeBSD 10-CURRENT, specify the PBI version to pull from. To do so, edit ''/usr/local/etc/pbi.conf'' and add this line:

{{txtbox|box=PBI_FBSDMAJOR: 9}}


{{note|icon64= If you are using NVIDIA video hardware, load the driver before rebooting into the display wizard by running the command '''pc-metapkgmanager add NVIDIA'''.}}

== Converting FreeBSD to a TrueOS{{R}} Server == 


If you wish to convert a FreeBSD server to TrueOS®, use the following commands:


{{txtbox|box= '''pkg install -fy trueos-base'''
'''rehash'''
'''pbreg set /PC-BSD/SysType TRUEOS'''
'''pc-extractoverlay server'''
'''pc-extractoverlay ports'''}}


The installation of the ''trueos-base'' package will install the following: [[PBI Manager]], the command line version of '''[[Warden®#Using the Command Line Version of Warden® | warden]]''', and the command line versions of most of the [[Control Panel]] utilities. You will find those utilities in ''/usr/local/bin/pc-*''. It also installs this {{citelink|url=http://trac.pcbsd.org/browser/pcbsd/branches/9.1/build-files/metapkgsets/warden/pkgset/base-system/ports-list|txt=list}} of additional shells and utilities.
</translate>
<noinclude>
{{refheading}}
[[category:Convert a FreeBSD System to PC-BSD®]]
[[category:Advanced Installation Topics]]
[[category:handbook]]
<languages/>
</noinclude>

Convert a FreeBSD System to PC-BSD®

2013-06-17T08:16:33Z

Tigersharke:

<noinclude><translate>


{{NavHeader|back=Install a Server |forward=Using a Rolling Release|custompagename=Convert a FreeBSD System to PC-BSD{{R}}|custompagecategory=Convert a FreeBSD System to PC-BSD{{RM}}}}</noinclude>


Beginning in February, 2013, the PC-BSD® utilities dealing with software installation and upgrades were converted to [https://wiki.freebsd.org/pkgng pkgng], FreeBSD's Next Generation package management tool. Part of this change included the creation of a custom PC-BSD® package repository which contains all of the packages that can be built using pkgng. Since the FreeBSD project does not yet have an official pkgng repository, FreeBSD users who wish to use pkgng are welcome to use the PC-BSD® package repository.


This package repository contains a custom package, called ''pcbsd-base'', which can be used to easily convert an existing FreeBSD installation into a PC-BSD® desktop. It also contains a custom package called ''trueos-base'' which can be used to convert an existing FreeBSD installation into a TrueOS® server. The converted desktop will contain all of the graphical utilities that come with PC-BSD® and the converted server will contain all of their command line equivalents.


This section describes how to:


* Configure a FreeBSD or PC-BSD® system to use the pkgng repository.


* Convert a FreeBSD system to a PC-BSD® desktop.


* Convert a FreeBSD system to a TrueOS® server.

== Switching to the PC-BSD{{R}} pkgng Repository == 


If you are running PC-BSD® 9.1-RELEASE or FreeBSD 9.1, you will need to first install the {{citelink|url=http://www.freshports.org/ports-mgmt/pkg/|txt=port or package}}.


After installing pkg, run the command '''pkg2ng''' to import your existing package database from the old format to the new pkgng format.


Next, configure access to the PC-BSD® repository. Start by creating the file ''/usr/local/etc/pkg.conf'' with the following contents:


{{txtbox|box=packagesite: {{ftp}}ftp.pcbsd.org/pub/mirror/packages/9.1-RELEASE/amd64
PUBKEY: /usr/local/etc/pkg-pubkey.cert
PKG_CACHEDIR: /usr/local/tmp}}


Note that the ''packagesite:'' variable should be changed to a PC-BSD® mirror close to your geographic location. Additionally, ''9.1-RELEASE'' and ''amd64'' can be changed to indicate the release version and architecture you want to use. Click [http://www.pcbsd.org/getmirrors.php?url=packages here] to get a list of the available mirrors and package sets.


Next, download the repository's [http://trac.pcbsd.org/export/780f3da562b72643c04b47a59d277102a09abbca/src-sh/pc-extractoverlay/desktop-overlay/usr/local/etc/pkg-pubkey.cert public key cert file], and copy it to ''/usr/local/etc/pkg-pubkey.cert''.


The system is now configured and you now update your packages to the latest versions from the pkgng repository using the following command:


{{txtbox|box= '''pkg upgrade -fy'''}}


Depending upon what is already installed, you may have to resolve some error messages in order to successfully upgrade all packages.


To install and delete packages use the '''pkg''' command. This command differs in usage from the original package format version. You can learn more about how to use this command in [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/pkgng-intro.html Section 5.5.3 of the FreeBSD Handbook].

== Converting FreeBSD to a PC-BSD{{R}} Desktop == 


Once the repository configuration is complete, it is now easy to convert a FreeBSD system into a PC-BSD® desktop using the following commands as the superuser:


{{txtbox|box= '''pkg install -fy pcbsd-base'''
'''rehash'''
'''pbreg set /PC-BSD/SysType PCBSD'''
'''pc-extractoverlay desktop'''
'''pc-extractoverlay ports'''}}


Next, reboot the system and the PC-BSD® login manager will start, allowing you to login to the desktop. If you want the [Post Installation Configuration and Installation Troubleshooting |PC-BSD® display wizard and first boot wizards] to run first, run these commands before rebooting:


{{txtbox|box= '''touch /var/.runxsetup'''
'''touch /var/.pcbsd-firstboot'''
'''touch /var/.pcbsd-firstgui'''}}


If you are running FreeBSD 10-CURRENT, specify the PBI version to pull from. To do so, edit ''/usr/local/etc/pbi.conf'' and add this line:

{{txtbox|box=PBI_FBSDMAJOR: 9}}


{{note|icon64= If you are using NVIDIA video hardware, load the driver before rebooting into the display wizard by running the command '''pc-metapkgmanager add NVIDIA'''.}}

== Converting FreeBSD to a TrueOS{{R}} Server == 


If you wish to convert a FreeBSD server to TrueOS®, use the following commands:


{{txtbox|box= '''pkg install -fy trueos-base'''
'''rehash'''
'''pbreg set /PC-BSD/SysType TRUEOS'''
'''pc-extractoverlay server'''
'''pc-extractoverlay ports'''}}


The installation of the ''trueos-base'' package will install the following: [[PBI Manager]], the command line version of '''[[Warden®#Using the Command Line Version of Warden® | warden]]''', and the command line versions of most of the [[Control Panel]] utilities. You will find those utilities in ''/usr/local/bin/pc-*''. It also installs this {{citelink|url=http://trac.pcbsd.org/browser/pcbsd/branches/9.1/build-files/metapkgsets/warden/pkgset/base-system/ports-list|txt=list}} of additional shells and utilities.
</translate>
<noinclude>

[[category:Convert a FreeBSD System to PC-BSD®]]
[[category:Advanced Installation Topics]]
[[category:handbook]]
<languages/>
</noinclude>

Installing PC-BSD®/fr

2013-06-11T21:47:56Z

Tigersharke:

<noinclude>
{{NavHeader|back=à l'Aide de VirtualBox|forward=Démarrage du PC-BSD® Installation|custompagename=Installation de PC-BSD{{r}}|custompagecategory={{PAGENAME}}}}</noinclude>

PC-BSD® can be installed from the installation media directly onto a hard drive or into a virtual machine using virtualization software such as {{citelink|url=http://www.virtualbox.org/|txt=Virtualbox}}. You can also try PC-BSD® without installing it by using a [[PC-BSD® Live Mode|Live version]].

L'installation de PC-BSD® est un moyen rapide, facile et un processus simple. L'installateur graphique va vous guider étape par étape à travers le processus entier en posant quelques questions simples. En une courte période, votre système PC-BSD® va être installé, configuré et prêt à l'usage. Cette section vous guidera à travers les étapes d'installation suivantes:

* [[Le démarrage de l'installation de PC-BSD®]]

* [[Écran de Sélection du langage]]

* [[Écran de sélection du système]]

* [[Écran de sélection du disque]]

* [[Écran de progression de l'installation]]

* [[Écran d'installation Terminée]]

<noinclude>
{{refheading}}
[[catégorie:Installation de PC-BSD®]]
[[catégorie:manuel]]
<languages />
</noinclude>

Translations:Installing PC-BSD®/1/fr

2013-06-11T21:47:53Z

Tigersharke:

{{NavHeader|back=à l'Aide de VirtualBox|forward=Démarrage du PC-BSD® Installation|custompagename=Installation de PC-BSD{{r}}|custompagecategory={{PAGENAME}}}}</noinclude>

Fast boot

2013-05-29T03:27:44Z

Tigersharke: Redirected page to Booting Into PC-BSD®#Fast Boot

#REDIRECT [[Booting_Into_PC-BSD®#Fast_Boot]]

Pkgsrc in PC-BSD®

2013-05-26T09:21:30Z

Tigersharke:

{{NavHome|custompagename=Pkgsrc in PC-BSD{{R}}|custompagecategory=Pkgsrc in PC-BSD{{RM}}}}

Available to PC-BSD® is its own PBI collection, FreeBSD ports, and FreeBSD packages. However, it is also possible to use the NetBSD pkgsrc system to build software. This is not (yet) a pre-configured feature, which means there are some special instructions to follow for this functionality to be enabled. '''This is not an official feature.''' This section will describe how to configure and use NetBSD pkgsrc from PC-BSD®. '''NOTE:''' Although these instructions seem complete and look polished, there may still be ommissions or inaccuracies, so be wary.

== Setting things up ==

# Obtain the NetBSD pkgsrc tree by the following commands: 
#: {{pound}} ftp {{ftp}}ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz 
#: {{pound}} tar -xzf pkgsrc.tar.gz -C /usr 
# Bootstrap pkgsrc. FreeBSD stores its ports pkg database in /var/db/pkg/. It is therefore recommended to use /var/db/pkgsrc/ with the --pkgdbdir flag as below: 
#: {{pound}} cd /usr/pkgsrc/bootstrap/ {{pound}} ./bootstrap --pkgdbdir /var/db/pkgsrc 
# The NetBSD pkg tools and FreeBSD pkg tools have identical names. It is recommended to change the name of the NetBSD set to match 'bmake' by prepending a 'b' to each, as follows:
#: {{pound}} cd /usr/pkg/sbin/ {{pound}} mv pkg_add bpkg_add {{pound}} mv pkg_create bpkg_create
#: {{pound}} mv pkg_delete bpkg_delete {{pound}} mv pkg_info bpkg_info
# If the FreeBSD ports tools will not be used, they can be moved out of the way entirely, as follows:
#: {{pound}} cd /usr/sbin/ {{pound}} mv pkg_add pkg_add.orig 
#: {{pound}} mv pkg_create pkg_create.orig {{pound}} mv pkg_delete pkg_delete.orig {{pound}} mv pkg_info pkg_info.orig 
# Add the location of bmake (/usr/pkg/bin) and NetBSD pkg tools (/usr/pkg/sbin) to the user's search path variable. Edit the file .cshrc in the user's home directory to modify the following line:
#: set path = (/sbin /bin /usr/sbin /usr/bin /usr/games /usr/local/sbin /usr/local/bin '''/usr/pkg/sbin /usr/pkg/bin''' $HOME/bin) 
# Add the PKG_PATH definition for the latest collection of pkgsrc packages (5.1_2011Q4) to the user's .cshrc file with the following line:
#: <nowiki>setenv PKG_PATH ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/`uname -m`/5.1_2011Q4/All/</nowiki> 
# Obtain the vulnerabilities file: 
#: {{pound}} /usr/pkg/sbin/pkg_admin -K fetch-pkg-vulnerabilities 
#: This prevents the non-fatal error below: 
#:: WARNING: No /var/db/pkg/pkg-vulnerabilities file found. 
#:: WARNING: To fix run: `/usr/sbin/pkg_admin -K /var/db/pkg fetch-pkg-vulnerabilities'. 
# The vulnerabilities of some ports (ie Firefox) may prevent them from being built. An example mk.conf file will be placed in /etc/mk.conf.example file when you use the bootstrap script. Adjust /usr/pkg/etc/mk.conf to allow vulnerable programs to be built by adding the following line:
#: ALLOW_VULNERABLE_PACKAGES=TRUE

== Keeping pkgsrc up to date ==

# The process for using tar files is very much the same as when obtaining them originally, except that the old tree must be erased first 
#: {{pound}} rm -rf /usr/pkgsrc/ 
#: {{pound}} ftp {{ftp}}ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc.tar.gz 
#: {{pound}} tar -xzf pkgsrc.tar.gz -C /usr 
# Next bootstrap pkgsrc again 
#: {{pound}} cd /usr/pkgsrc/bootstrap/ 
#: {{pound}} ./bootstrap --pkgdbdir /var/db/pkgsrc 
# Update the bootstrap-mk-files 
#: {{pound}} cd /usr/pkgsrc/pkgtools/bootstrap-mk-files/
#: {{pound}} /usr/pkgsrc/bootstrap/work/bin/bmake update 
# And if that does not work (such as on a standard NetBSD install) try: 
#: {{pound}} /usr/pkgsrc/bootstrap/work/bin/bmake replace 
#: {{pound}} /usr/pkgsrc/bootstrap/work/bin/bmake update 

<nowiki>
===> Installing for bootstrap-mk-files-20111205
ERROR: bootstrap-mk-files-20111106 is already installed - perhaps an older version?
ERROR: If so, you may use either of:
ERROR: - "pkg_delete bootstrap-mk-files-20111106" and "/usr/pkgsrc/bootstrap/work/bin/bmake reinstall" to upgrade properly
ERROR:
ERROR: - "/usr/pkgsrc/bootstrap/work/bin/bmake update" to rebuild the package and all of its dependencies
ERROR:
ERROR: - "/usr/pkgsrc/bootstrap/work/bin/bmake replace" to replace only the package without re-linking dependencies,
ERROR: risking various problems.
</nowiki>

== Using pkgsrc to build ==

Much like using the FreeBSD ports system, building with the NetBSD pkgsrc system is a rather simple matter of going to the location of the application within the pkgsrc tree, and then using bmake, for example:

: {{percent}} su -m
: {{pound}} unsetenv PKG_PATH
: {{pound}} cd /usr/pkgsrc/www/firefox/
: {{pound}} bmake install clean

However, if there may be options that would modify what is built, how it is installed, or the features enabled. The additional steps for options adjustment is done prior to invoking ''bmake install clean.'' Discover whether there are options:

{{cli|xterm=
{{pound}} bmake show-options 

Any of the following general options may be selected: 
: official-mozilla-branding       Use official Mozilla reg. trademarks and logos.

These options are enabled by default:

These options are currently enabled:

You can select which build options to use by setting PKG_DEFAULT_OPTIONS
or PKG_OPTIONS.firefox.
}}

== Adding a NetBSD pkg ==
: {{percent}} su -m
: {{pound}} bpkg_add firefox

The above probably should simply work, or the NetBSD documentation would not mention renaming the FreeBSD pkg tools. However, for the moment, testing this throws the following type of error:

{{cli|xterm=
pkg_add: Warning: package `firefox-3.6.16' was built for a platform: 
pkg_add: NetBSD/x86_64 5.1 (pkg) vs. FreeBSD/x86_64 9.0 (this host) 
pkg_add: 1 package addition failed 
}}

Category:PC-BSD® 9.2 TODO

2013-05-26T08:15:17Z

Tigersharke:

{{SwapTitle|custompagename=Category:PC-BSD{{R}} 9.2 TODO|custompagecategory=categories}}
[[category:categories]]

Category:PC-BSD® 9.2 TODO

2013-05-26T08:11:03Z

Tigersharke: Created page with "category:categories"

[[category:categories]]

PC-BSD® 9.2 TODO

2013-05-26T08:10:17Z

Tigersharke:

{{SwapTitle|custompagename=PC-BSD{{R}} 9.2 TODO|custompagecategory=PC-BSD{{RM}} 9.2 TODO}}
==== New Features / Tools planned for 9.2 ====
{| class="spiffy_table"
! Feature
! Owner
! Skills
! Status
! Completion Date
|-
| Enable PEFS via User-Manager, allowing encrypted home directories
| kmoore
| QT4/Shell/Sys
|
|
|-
| add iSCSI initiator GUI front-end to iscontrol(8) for connecting to FreeNAS™ systems
|
|
|
|
|-
| replace firewall GUI with fwbuilder and document how to use
| dru
|
|
|
|-
| add Info button to Service Manager containing description
|
|
| should really be a DESCRIPTION field in rc.d scripts
|
|-
| Animated splash screen
|
|
|
|
|-
| Add help buttons to custom menus, write help text and add to Pootle
| dru
|
|
|
|-
| Front-end to text installer
| jhixson
|
|
|
|-
| Create new Disk Management GUI for post-install usage, ZFS, Advanced FS tasks such as ZFS snapshots, ZFS quota/compression
|
| C++ / QT4
|
|
|-
| Add option to play some simple games while waiting for installation
| kris
| C++ / QT4 / shell
|
|
|-
| Add ability to backup ZFS datasets (in life preserver?)
|
|
|
|
|-
| Add password strength meter to installer and warn if root / user are same.
| kmoore
| C++ / QT4
|
|
|-
| Localize the meta-pkg descriptions
| kmoore
| C++ / Shell
|
|
|-
| C++ / QT CUPS GUI
| Loic Maury
| C++ / C
|
|
|-
| Switch LifePreserver to use /var/ for its backend files
| kmoore
| C++ / Shell
|
|
|-
| changing default language / locale for GDM in pc-sysinstall
|
|
|
|
|-
| add Update All to Appcafe
|
|
|
|
|-
| add option to wireless settings in network manager to select country code
|
|
|
|
|-
| Add directory tree to AppCafe. On app page, at top show Home -> Category -> AppName, clickable
|
| C++ / QT4
|
|
|-
| Add enable / disable startup warden buttons
|
| C++ / QT4
|
|
|-
| Display fetch size / speed on warden downloads
|
| C++ / QT4
|
|
|-
| Display more info about devices in hardware compat GUI
|
| C++ / QT4
|
|
|-
| the psk for WPA networks should be hashed with wpa_passphrase(8)
|
| C++ / QT4
|
|
|-
| Add some kind of low disk space framework that detects both UFS + ZFS space
| Ken Moore
| C++ / Shell / libpcbsd
| Complete: Added to Mount-Tray
| Mid-April 2013
|-
| Improve system update mechanism to update rc.conf / loader.conf defaults (Perhaps with /etc/defaults/rc.conf)
| kmoore
| Shell
|
|
|-
| add bug reporting tool
|
|
|
|
|-
| add a mass delete snapshot function for warden to delete snapshots no longer needed beyond a certain date. (from the command line not GUI)
|
|
|
|
|-
| Add VPN functionality. If not enough time push back to 10.0.
|
|
|
|
|}

[[category:PC-BSD® Wiki]]
[[category:TODO Lists]]

TrueOS

2013-05-26T07:50:18Z

Tigersharke: eliminate double redirect

#REDIRECT [[Install a Server]]

Install a Server

2013-05-26T03:57:29Z

Tigersharke: Link is broken - commented out as temporary fix, not sure where same info exists now.

<noinclude><translate>


{{NavHeader|back=Advanced Installation Topics|forward=Convert a FreeBSD System to PC-BSD®}}</noinclude>


The [[System Selection Screen]] of the PC-BSD® installer can be used to install a FreeBSD-based server operating system, rather than a PC-BSD® desktop operating system. This screen provides two server options:


[[File:Freebsd1c.png|thumb|393px|'''Figure 5.1a: Selecting to Install TrueOS®''']]


* '''FreeBSD Server:''' installs a basic, vanilla installation of FreeBSD. While the installation routine is different, the end result is the same as if one had installed FreeBSD from a FreeBSD media as it results in a minimal, command-line only FreeBSD server installation.


* '''{{citelink|website|url=trueos/|txt=TrueOS®}}:''' adds the following to a vanilla installation of FreeBSD: [[PBI Manager]], the command line version of '''[[Warden®#Using the Command Line Version of Warden® | warden]]''', and the command line versions of most of the [[Control Panel]] utilities. You will find those utilities in ''/usr/local/bin/pc-*''. It also installs  additional shells and utilities.


For a server installation, using the PC-BSD® installer rather than the FreeBSD installer offers several benefits:


* the ability to easily [[Disk Selection Screen#ZFS Layout | configure ZFS]] during installation


* the ability to configure encryption during installation


* the ability to configure ZFS [[Multiple Boot Environments]]


* a wizard (described in this section) is provided during installation to configure the server for first use.


To perform a server installation, [[Installing PC-BSD® | start the PC-BSD® installation]] as usual. When you get to the [[System Selection Screen]] of the installer, click the left arrow until either FreeBSD or TrueOS® is selected. In the example shown as in Figure 5.1a, the user has selected TrueOS® and the FreeBSD option is to the left of the selection.


Once selected, press "Next" to start the "Server Setup Wizard". The wizard is the same for either a FreeBSD or a TrueOS® installation.


Click "Next" to see the screen shown in Figure 5.1b.


[[File:Freebsd1b.png|thumb|393px|'''Figure 5.1b: Set the Root Password''']]


Input and confirm the root password which will be used for administrative or "superuser" access to the server, then click "Next" to proceed to the screen shown in Figure 5.1c.


[[File:Freebsd2a.png|thumb|393px|'''Figure 5.1c: Create the Primary User Account''']]


For security reasons, you should not login as the ''root'' user. For this reason, the wizard requires you to create a primary user account that will be used to login to the FreeBSD system. This account will automatically be added to the ''wheel'' group, allowing that user to '''su''' to the root account when administrative access is required.


This screen contains the following fields:


* '''Name:''' can contain capital letters and spaces.


* '''Username:''' the name used when logging in. Can not contain spaces and is case sensitive (e.g. Kris is a different username than kris).


* '''Password:''' the password used when logging in. You must type it twice in order to confirm it.


* '''Default shell:''' use the drop-down menu to select the '''csh''', '''tcsh''', or '''sh''' login shell.


When finished, click "Next" to proceed to the screen shown in Figure 5.1d.


[[File:Freebsd3a.png|thumb|393px|'''Figure 5.1d: Set the Hostname''']]


Input the system's hostname. If you will be using '''ssh''' to administer the system, check the box "Enable remote SSH login". Click "Next" to proceed to the network configuration screen shown in Figure 5.1e.


[[File:Freebsd4a.png|thumb|393px|'''Figure 5.1e: Configure the Network''']]


Use the "Network Interface" drop-down menu to select from the following:


* '''AUTO-DHCP-SLAAC:''' (default) will configure every active interface configured for DHCP and both IPv4 and IPv6


* '''AUTO-DHCP:''' will configure every active interface for DHCP and IPv4


* '''IPv6-SLAAC:''' will configure every active interface for DHCP and IPv6


Alternately, select the device name for the interface that you wish to manually configure and input the IPv4 and/or IPv6 addressing information. When finished, click "Next" to proceed to the screen shown in Figure 5.1f.


[[File:Freebsd5a.png|thumb|393px|'''Figure 5.1f: Install Source or Ports''']]


If you wish to install FreeBSD source or ports, check the associated box(es) then click "Finish" to exit the wizard.


If you are installing TrueOS®, you can use the "Customize" button to install server meta-packages. This screen, shown in Figure 5.1g, can be used to install packages such as MySQL, PostgreSQL, Samba, PHP, VirtualBox, Apache, and Lighttp.


[[File:Apps.png|thumb|393px|'''Figure 5.1g: Installing Server Applications into TrueOS®''']]


When you have saved your selections, click "Next" to proceed to the [[Disk Selection Screen]] in order to configure the system's disk(s).


Once the system is installed, it will boot to a command-line login prompt. Login using the primary user account that was configured during installation. You can now configure and use the server as you would any other FreeBSD server installation. The
{{citelink|fbsdh|url=|txt=FreeBSD Handbook}} is an excellent reference for performing common FreeBSD server tasks.


<noinclude>
{{refheading}}
[[category:Install a Server]]
[[category:Advanced Installation Topics]]
[[category:handbook]]
</translate>
<languages/>
</noinclude>

Convert a FreeBSD System to PC-BSD®

2013-05-26T03:44:29Z

Tigersharke:

<noinclude><translate>


{{NavHeader|back=Install a Server |forward=Using a Rolling Release|custompagename=Convert a FreeBSD System to PC-BSD{{R}}|custompagecategory=Convert a FreeBSD System to PC-BSD{{RM}}}}</noinclude>


Beginning in February, 2013, the PC-BSD® utilities dealing with software installation and upgrades were converted to [https://wiki.freebsd.org/pkgng pkgng], FreeBSD's Next Generation package management tool. Part of this change included the creation of a custom PC-BSD® package repository which contains all of the packages that can be built using pkgng. Since the FreeBSD project does not yet have an official pkgng repository, FreeBSD users who wish to use pkgng are welcome to use the PC-BSD® package repository.


This package repository contains a custom package, called ''pcbsd-base'', which can be used to easily convert an existing FreeBSD installation into a PC-BSD® desktop. It also contains a custom package called ''trueos-base'' which can be used to convert an existing FreeBSD installation into a TrueOS® server. The converted desktop will contain all of the graphical utilities that come with PC-BSD® and the converted server will contain all of their command line equivalents.


This section describes how to:


* Configure a FreeBSD or PC-BSD® system to use the pkgng repository.


* Convert a FreeBSD system to a PC-BSD® desktop.


* Convert a FreeBSD system to a TrueOS® server.

== Switching to the PC-BSD{{R}} pkgng Repository == 


If you are running PC-BSD® 9.1-RELEASE or FreeBSD 9.1, you will need to first install the {{citelink|url=http://www.freshports.org/ports-mgmt/pkg/|txt=port or package}}.


After installing pkg, run the command '''pkg2ng''' to import your existing package database from the old format to the new pkgng format.


Next, configure access to the PC-BSD® repository. Start by creating the file ''/usr/local/etc/pkg.conf'' with the following contents:


{{txtbox|box=packagesite: {{ftp}}ftp.pcbsd.org/pub/mirror/packages/9.1-RELEASE/amd64
PUBKEY: /usr/local/etc/pkg-pubkey.cert
PKG_CACHEDIR: /usr/local/tmp}}


Note that the ''packagesite:'' variable should be changed to a PC-BSD® mirror close to your geographic location. Additionally, ''9.1-RELEASE'' and ''amd64'' can be changed to indicate the release version and architecture you want to use. Click [http://www.pcbsd.org/getmirrors.php?url=packages here] to get a list of the available mirrors and package sets.


Next, download the repository's [http://trac.pcbsd.org/export/780f3da562b72643c04b47a59d277102a09abbca/src-sh/pc-extractoverlay/desktop-overlay/usr/local/etc/pkg-pubkey.cert public key cert file], and copy it to ''/usr/local/etc/pkg-pubkey.cert''.


The system is now configured and you now update your packages to the latest versions from the pkgng repository using the following command:


{{txtbox|box= '''pkg upgrade -fy'''}}


Depending upon what is already installed, you may have to resolve some error messages in order to successfully upgrade all packages.


To install and delete packages use the '''pkg''' command. This command differs in usage from the original package format version. You can learn more about how to use this command in [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/pkgng-intro.html Section 5.5.3 of the FreeBSD Handbook].

== Converting FreeBSD to a PC-BSD{{R}} Desktop == 


Once the repository configuration is complete, it is now easy to convert a FreeBSD system into a PC-BSD® desktop using the following commands as the superuser:


{{txtbox|box= '''pkg install -fy pcbsd-base'''
'''rehash'''
'''pbreg set /PC-BSD/SysType PCBSD'''
'''pc-extractoverlay desktop'''
'''pc-extractoverlay ports'''}}


Next, reboot the system and the PC-BSD® login manager will start, allowing you to login to the desktop. If you want the [Post Installation Configuration and Installation Troubleshooting |PC-BSD® display wizard and first boot wizards] to run first, run these commands before rebooting:


{{txtbox|box= '''touch /var/.runxsetup'''
'''touch /var/.pcbsd-firstboot'''
'''touch /var/.pcbsd-firstgui'''}}


If you are running FreeBSD 10-CURRENT, specify the PBI version to pull from. To do so, edit ''/usr/local/etc/pbi.conf'' and add this line:

{{txtbox|box=PBI_FBSDMAJOR: 9}}


{{note|icon64= If you are using NVIDIA video hardware, load the driver before rebooting into the display wizard by running the command '''pc-metapkgmanager add NVIDIA'''.}}

== Converting FreeBSD to a TrueOS{{R}} Server == 


If you wish to convert a FreeBSD server to TrueOS®, use the following commands:


{{txtbox|box= '''pkg install -fy trueos-base'''
'''rehash'''
'''pbreg set /PC-BSD/SysType TRUEOS'''
'''pc-extractoverlay server'''
'''pc-extractoverlay ports'''}}


The installation of the ''trueos-base'' package will install the following: [[PBI Manager]], the command line version of '''[[Warden®#Using the Command Line Version of Warden® | warden]]''', and the command line versions of most of the [[Control Panel]] utilities. You will find those utilities in ''/usr/local/bin/pc-*''. It also installs this {{citelink|url=http://trac.pcbsd.org/browser/pcbsd/branches/9.1/build-files/metapkgsets/warden/pkgset/base-system/ports-list|txt=list}} of additional shells and utilities.
</translate>
<noinclude>
{{refheading}}
[[category:Convert a FreeBSD System to PC-BSD®]]
[[category:Advanced Installation Topics]]
[[category:handbook]]
<languages/>
</noinclude>

Convert a FreeBSD System to PC-BSD®

2013-05-26T03:43:00Z

Tigersharke:

<noinclude><translate>


{{NavHeader|back=Install a Server |forward=Using a Rolling Release|custompagename=Convert a FreeBSD System to PC-BSD{{R}}|custompagecategory=Convert a FreeBSD System to PC-BSD{{RM}}}}</noinclude>


Beginning in February, 2013, the PC-BSD® utilities dealing with software installation and upgrades were converted to [https://wiki.freebsd.org/pkgng pkgng], FreeBSD's Next Generation package management tool. Part of this change included the creation of a custom PC-BSD® package repository which contains all of the packages that can be built using pkgng. Since the FreeBSD project does not yet have an official pkgng repository, FreeBSD users who wish to use pkgng are welcome to use the PC-BSD® package repository.


This package repository contains a custom package, called ''pcbsd-base'', which can be used to easily convert an existing FreeBSD installation into a PC-BSD® desktop. It also contains a custom package called ''trueos-base'' which can be used to convert an existing FreeBSD installation into a TrueOS® server. The converted desktop will contain all of the graphical utilities that come with PC-BSD® and the converted server will contain all of their command line equivalents.


This section describes how to:


* Configure a FreeBSD or PC-BSD® system to use the pkgng repository.


* Convert a FreeBSD system to a PC-BSD® desktop.


* Convert a FreeBSD system to a TrueOS® server.

== Switching to the PC-BSD{{R}} pkgng Repository == 


If you are running PC-BSD® 9.1-RELEASE or FreeBSD 9.1, you will need to first install the {{citelink|url=http://www.freshports.org/ports-mgmt/pkg/ ports-mgmt/pkg|txt=port or package}}.


After installing pkg, run the command '''pkg2ng''' to import your existing package database from the old format to the new pkgng format.


Next, configure access to the PC-BSD® repository. Start by creating the file ''/usr/local/etc/pkg.conf'' with the following contents:


{{txtbox|box=packagesite: {{ftp}}ftp.pcbsd.org/pub/mirror/packages/9.1-RELEASE/amd64
PUBKEY: /usr/local/etc/pkg-pubkey.cert
PKG_CACHEDIR: /usr/local/tmp}}


Note that the ''packagesite:'' variable should be changed to a PC-BSD® mirror close to your geographic location. Additionally, ''9.1-RELEASE'' and ''amd64'' can be changed to indicate the release version and architecture you want to use. Click [http://www.pcbsd.org/getmirrors.php?url=packages here] to get a list of the available mirrors and package sets.


Next, download the repository's [http://trac.pcbsd.org/export/780f3da562b72643c04b47a59d277102a09abbca/src-sh/pc-extractoverlay/desktop-overlay/usr/local/etc/pkg-pubkey.cert public key cert file], and copy it to ''/usr/local/etc/pkg-pubkey.cert''.


The system is now configured and you now update your packages to the latest versions from the pkgng repository using the following command:


{{txtbox|box= '''pkg upgrade -fy'''}}


Depending upon what is already installed, you may have to resolve some error messages in order to successfully upgrade all packages.


To install and delete packages use the '''pkg''' command. This command differs in usage from the original package format version. You can learn more about how to use this command in [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/pkgng-intro.html Section 5.5.3 of the FreeBSD Handbook].

== Converting FreeBSD to a PC-BSD{{R}} Desktop == 


Once the repository configuration is complete, it is now easy to convert a FreeBSD system into a PC-BSD® desktop using the following commands as the superuser:


{{txtbox|box= '''pkg install -fy pcbsd-base'''
'''rehash'''
'''pbreg set /PC-BSD/SysType PCBSD'''
'''pc-extractoverlay desktop'''
'''pc-extractoverlay ports'''}}


Next, reboot the system and the PC-BSD® login manager will start, allowing you to login to the desktop. If you want the [Post Installation Configuration and Installation Troubleshooting |PC-BSD® display wizard and first boot wizards] to run first, run these commands before rebooting:


{{txtbox|box= '''touch /var/.runxsetup'''
'''touch /var/.pcbsd-firstboot'''
'''touch /var/.pcbsd-firstgui'''}}


If you are running FreeBSD 10-CURRENT, specify the PBI version to pull from. To do so, edit ''/usr/local/etc/pbi.conf'' and add this line:

{{txtbox|box=PBI_FBSDMAJOR: 9}}


{{note|icon64= If you are using NVIDIA video hardware, load the driver before rebooting into the display wizard by running the command '''pc-metapkgmanager add NVIDIA'''.}}

== Converting FreeBSD to a TrueOS{{R}} Server == 


If you wish to convert a FreeBSD server to TrueOS®, use the following commands:


{{txtbox|box= '''pkg install -fy trueos-base'''
'''rehash'''
'''pbreg set /PC-BSD/SysType TRUEOS'''
'''pc-extractoverlay server'''
'''pc-extractoverlay ports'''}}


The installation of the ''trueos-base'' package will install the following: [[PBI Manager]], the command line version of '''[[Warden®#Using the Command Line Version of Warden® | warden]]''', and the command line versions of most of the [[Control Panel]] utilities. You will find those utilities in ''/usr/local/bin/pc-*''. It also installs this {{citelink|url=http://trac.pcbsd.org/browser/pcbsd/branches/9.1/build-files/metapkgsets/warden/pkgset/base-system/ports-list|txt=list}} of additional shells and utilities.
</translate>
<noinclude>
{{refheading}}
[[category:Convert a FreeBSD System to PC-BSD®]]
[[category:Advanced Installation Topics]]
[[category:handbook]]
<languages/>
</noinclude>

Convert a FreeBSD System to PC-BSD®

2013-05-26T03:42:24Z

Tigersharke:

<noinclude><translate>


{{NavHeader|back=Install a Server |forward=Using a Rolling Release|custompagename=Convert a FreeBSD System to PC-BSD{{R}}|custompagecategory=Convert a FreeBSD System to PC-BSD{{RM}}}}</noinclude>


Beginning in February, 2013, the PC-BSD® utilities dealing with software installation and upgrades were converted to [https://wiki.freebsd.org/pkgng pkgng], FreeBSD's Next Generation package management tool. Part of this change included the creation of a custom PC-BSD® package repository which contains all of the packages that can be built using pkgng. Since the FreeBSD project does not yet have an official pkgng repository, FreeBSD users who wish to use pkgng are welcome to use the PC-BSD® package repository.


This package repository contains a custom package, called ''pcbsd-base'', which can be used to easily convert an existing FreeBSD installation into a PC-BSD® desktop. It also contains a custom package called ''trueos-base'' which can be used to convert an existing FreeBSD installation into a TrueOS® server. The converted desktop will contain all of the graphical utilities that come with PC-BSD® and the converted server will contain all of their command line equivalents.


This section describes how to:


* Configure a FreeBSD or PC-BSD® system to use the pkgng repository.


* Convert a FreeBSD system to a PC-BSD® desktop.


* Convert a FreeBSD system to a TrueOS® server.

== Switching to the PC-BSD{{R}} pkgng Repository == 


If you are running PC-BSD® 9.1-RELEASE or FreeBSD 9.1, you will need to first install the {{citelink|url=http://www.freshports.org/ports-mgmt/pkg/ ports-mgmt/pkg|txt=port or package}}.


After installing pkg, run the command '''pkg2ng''' to import your existing package database from the old format to the new pkgng format.


Next, configure access to the PC-BSD® repository. Start by creating the file ''/usr/local/etc/pkg.conf'' with the following contents:


{{txtbox|box=packagesite: {{ftp}}ftp.pcbsd.org/pub/mirror/packages/9.1-RELEASE/amd64
PUBKEY: /usr/local/etc/pkg-pubkey.cert
PKG_CACHEDIR: /usr/local/tmp}}


Note that the ''packagesite:'' variable should be changed to a PC-BSD® mirror close to your geographic location. Additionally, ''9.1-RELEASE'' and ''amd64'' can be changed to indicate the release version and architecture you want to use. Click [http://www.pcbsd.org/getmirrors.php?url=packages here] to get a list of the available mirrors and package sets.


Next, download the repository's [http://trac.pcbsd.org/export/780f3da562b72643c04b47a59d277102a09abbca/src-sh/pc-extractoverlay/desktop-overlay/usr/local/etc/pkg-pubkey.cert public key cert file], and copy it to ''/usr/local/etc/pkg-pubkey.cert''.


The system is now configured and you now update your packages to the latest versions from the pkgng repository using the following command:


{{txtbox|box= '''pkg upgrade -fy'''}}


Depending upon what is already installed, you may have to resolve some error messages in order to successfully upgrade all packages.


To install and delete packages use the '''pkg''' command. This command differs in usage from the original package format version. You can learn more about how to use this command in [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/pkgng-intro.html Section 5.5.3 of the FreeBSD Handbook].

== Converting FreeBSD to a PC-BSD{{R}} Desktop == 


Once the repository configuration is complete, it is now easy to convert a FreeBSD system into a PC-BSD® desktop using the following commands as the superuser:


{{txtbox|box= '''pkg install -fy pcbsd-base'''
'''rehash'''
'''pbreg set /PC-BSD/SysType PCBSD'''
'''pc-extractoverlay desktop'''
'''pc-extractoverlay ports'''}}


Next, reboot the system and the PC-BSD® login manager will start, allowing you to login to the desktop. If you want the [Post Installation Configuration and Installation Troubleshooting |PC-BSD® display wizard and first boot wizards] to run first, run these commands before rebooting:


{{txtbox|box= '''touch /var/.runxsetup'''
'''touch /var/.pcbsd-firstboot'''
'''touch /var/.pcbsd-firstgui'''}}


If you are running FreeBSD 10-CURRENT, specify the PBI version to pull from. To do so, edit ''/usr/local/etc/pbi.conf'' and add this line:

{{txtbox|box=PBI_FBSDMAJOR: 9}}


{{note|icon64= If you are using NVIDIA video hardware, load the driver before rebooting into the display wizard by running the command '''pc-metapkgmanager add NVIDIA'''.}}

== Converting FreeBSD to a TrueOS® Server == 


If you wish to convert a FreeBSD server to TrueOS®, use the following commands:


{{txtbox|box= '''pkg install -fy trueos-base'''
'''rehash'''
'''pbreg set /PC-BSD/SysType TRUEOS'''
'''pc-extractoverlay server'''
'''pc-extractoverlay ports'''}}


The installation of the ''trueos-base'' package will install the following: [[PBI Manager]], the command line version of '''[[Warden®#Using the Command Line Version of Warden® | warden]]''', and the command line versions of most of the [[Control Panel]] utilities. You will find those utilities in ''/usr/local/bin/pc-*''. It also installs this {{citelink|url=http://trac.pcbsd.org/browser/pcbsd/branches/9.1/build-files/metapkgsets/warden/pkgset/base-system/ports-list|txt=list}} of additional shells and utilities.
</translate>
<noinclude>
{{refheading}}
[[category:Convert a FreeBSD System to PC-BSD®]]
[[category:Advanced Installation Topics]]
[[category:handbook]]
<languages/>
</noinclude>

Convert a FreeBSD System to PC-BSD®

2013-05-26T03:40:52Z

Tigersharke:

<noinclude><translate>


{{NavHeader|back=Install a Server |forward=Using a Rolling Release}}</noinclude>


Beginning in February, 2013, the PC-BSD® utilities dealing with software installation and upgrades were converted to [https://wiki.freebsd.org/pkgng pkgng], FreeBSD's Next Generation package management tool. Part of this change included the creation of a custom PC-BSD® package repository which contains all of the packages that can be built using pkgng. Since the FreeBSD project does not yet have an official pkgng repository, FreeBSD users who wish to use pkgng are welcome to use the PC-BSD® package repository.


This package repository contains a custom package, called ''pcbsd-base'', which can be used to easily convert an existing FreeBSD installation into a PC-BSD® desktop. It also contains a custom package called ''trueos-base'' which can be used to convert an existing FreeBSD installation into a TrueOS® server. The converted desktop will contain all of the graphical utilities that come with PC-BSD® and the converted server will contain all of their command line equivalents.


This section describes how to:


* Configure a FreeBSD or PC-BSD® system to use the pkgng repository.


* Convert a FreeBSD system to a PC-BSD® desktop.


* Convert a FreeBSD system to a TrueOS® server.

== Switching to the PC-BSD{{R}} pkgng Repository == 


If you are running PC-BSD® 9.1-RELEASE or FreeBSD 9.1, you will need to first install the {{citelink|url=http://www.freshports.org/ports-mgmt/pkg/ ports-mgmt/pkg|txt=port or package}}.


After installing pkg, run the command '''pkg2ng''' to import your existing package database from the old format to the new pkgng format.


Next, configure access to the PC-BSD® repository. Start by creating the file ''/usr/local/etc/pkg.conf'' with the following contents:


{{txtbox|box=packagesite: {{ftp}}ftp.pcbsd.org/pub/mirror/packages/9.1-RELEASE/amd64
PUBKEY: /usr/local/etc/pkg-pubkey.cert
PKG_CACHEDIR: /usr/local/tmp}}


Note that the ''packagesite:'' variable should be changed to a PC-BSD® mirror close to your geographic location. Additionally, ''9.1-RELEASE'' and ''amd64'' can be changed to indicate the release version and architecture you want to use. Click [http://www.pcbsd.org/getmirrors.php?url=packages here] to get a list of the available mirrors and package sets.


Next, download the repository's [http://trac.pcbsd.org/export/780f3da562b72643c04b47a59d277102a09abbca/src-sh/pc-extractoverlay/desktop-overlay/usr/local/etc/pkg-pubkey.cert public key cert file], and copy it to ''/usr/local/etc/pkg-pubkey.cert''.


The system is now configured and you now update your packages to the latest versions from the pkgng repository using the following command:


{{txtbox|box= '''pkg upgrade -fy'''}}


Depending upon what is already installed, you may have to resolve some error messages in order to successfully upgrade all packages.


To install and delete packages use the '''pkg''' command. This command differs in usage from the original package format version. You can learn more about how to use this command in [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/pkgng-intro.html Section 5.5.3 of the FreeBSD Handbook].

== Converting FreeBSD to a PC-BSD{{R}} Desktop == 


Once the repository configuration is complete, it is now easy to convert a FreeBSD system into a PC-BSD® desktop using the following commands as the superuser:


{{txtbox|box= '''pkg install -fy pcbsd-base'''
'''rehash'''
'''pbreg set /PC-BSD/SysType PCBSD'''
'''pc-extractoverlay desktop'''
'''pc-extractoverlay ports'''}}


Next, reboot the system and the PC-BSD® login manager will start, allowing you to login to the desktop. If you want the [Post Installation Configuration and Installation Troubleshooting |PC-BSD® display wizard and first boot wizards] to run first, run these commands before rebooting:


{{txtbox|box= '''touch /var/.runxsetup'''
'''touch /var/.pcbsd-firstboot'''
'''touch /var/.pcbsd-firstgui'''}}


If you are running FreeBSD 10-CURRENT, specify the PBI version to pull from. To do so, edit ''/usr/local/etc/pbi.conf'' and add this line:

{{txtbox|box=PBI_FBSDMAJOR: 9}}


{{note|icon64= If you are using NVIDIA video hardware, load the driver before rebooting into the display wizard by running the command '''pc-metapkgmanager add NVIDIA'''.}}

== Converting FreeBSD to a TrueOS® Server == 


If you wish to convert a FreeBSD server to TrueOS®, use the following commands:


{{txtbox|box= '''pkg install -fy trueos-base'''
'''rehash'''
'''pbreg set /PC-BSD/SysType TRUEOS'''
'''pc-extractoverlay server'''
'''pc-extractoverlay ports'''}}


The installation of the ''trueos-base'' package will install the following: [[PBI Manager]], the command line version of '''[[Warden®#Using the Command Line Version of Warden® | warden]]''', and the command line versions of most of the [[Control Panel]] utilities. You will find those utilities in ''/usr/local/bin/pc-*''. It also installs this {{citelink|url=http://trac.pcbsd.org/browser/pcbsd/branches/9.1/build-files/metapkgsets/warden/pkgset/base-system/ports-list|txt=list}} of additional shells and utilities.
</translate>
<noinclude>
{{refheading}}
[[category:Convert a FreeBSD System to PC-BSD®]]
[[category:Advanced Installation Topics]]
[[category:handbook]]
<languages/>
</noinclude>

Convert a FreeBSD System to PC-BSD®

2013-05-26T03:40:04Z

Tigersharke:

<noinclude><translate>


{{NavHeader|back=Install a Server |forward=Using a Rolling Release}}</noinclude>


Beginning in February, 2013, the PC-BSD® utilities dealing with software installation and upgrades were converted to [https://wiki.freebsd.org/pkgng pkgng], FreeBSD's Next Generation package management tool. Part of this change included the creation of a custom PC-BSD® package repository which contains all of the packages that can be built using pkgng. Since the FreeBSD project does not yet have an official pkgng repository, FreeBSD users who wish to use pkgng are welcome to use the PC-BSD® package repository.


This package repository contains a custom package, called ''pcbsd-base'', which can be used to easily convert an existing FreeBSD installation into a PC-BSD® desktop. It also contains a custom package called ''trueos-base'' which can be used to convert an existing FreeBSD installation into a TrueOS® server. The converted desktop will contain all of the graphical utilities that come with PC-BSD® and the converted server will contain all of their command line equivalents.


This section describes how to:


* Configure a FreeBSD or PC-BSD® system to use the pkgng repository.


* Convert a FreeBSD system to a PC-BSD® desktop.


* Convert a FreeBSD system to a TrueOS® server.

== Switching to the PC-BSD® pkgng Repository == 


If you are running PC-BSD® 9.1-RELEASE or FreeBSD 9.1, you will need to first install the {{citelink|url=http://www.freshports.org/ports-mgmt/pkg/ ports-mgmt/pkg|txt=port or package}}.


After installing pkg, run the command '''pkg2ng''' to import your existing package database from the old format to the new pkgng format.


Next, configure access to the PC-BSD® repository. Start by creating the file ''/usr/local/etc/pkg.conf'' with the following contents:


{{txtbox|box=packagesite: {{ftp}}ftp.pcbsd.org/pub/mirror/packages/9.1-RELEASE/amd64
PUBKEY: /usr/local/etc/pkg-pubkey.cert
PKG_CACHEDIR: /usr/local/tmp}}


Note that the ''packagesite:'' variable should be changed to a PC-BSD® mirror close to your geographic location. Additionally, ''9.1-RELEASE'' and ''amd64'' can be changed to indicate the release version and architecture you want to use. Click [http://www.pcbsd.org/getmirrors.php?url=packages here] to get a list of the available mirrors and package sets.


Next, download the repository's [http://trac.pcbsd.org/export/780f3da562b72643c04b47a59d277102a09abbca/src-sh/pc-extractoverlay/desktop-overlay/usr/local/etc/pkg-pubkey.cert public key cert file], and copy it to ''/usr/local/etc/pkg-pubkey.cert''.


The system is now configured and you now update your packages to the latest versions from the pkgng repository using the following command:


{{txtbox|box= '''pkg upgrade -fy'''}}


Depending upon what is already installed, you may have to resolve some error messages in order to successfully upgrade all packages.


To install and delete packages use the '''pkg''' command. This command differs in usage from the original package format version. You can learn more about how to use this command in [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/pkgng-intro.html Section 5.5.3 of the FreeBSD Handbook].

== Converting FreeBSD to a PC-BSD{{R}} Desktop == 


Once the repository configuration is complete, it is now easy to convert a FreeBSD system into a PC-BSD® desktop using the following commands as the superuser:


{{txtbox|box= '''pkg install -fy pcbsd-base'''
'''rehash'''
'''pbreg set /PC-BSD/SysType PCBSD'''
'''pc-extractoverlay desktop'''
'''pc-extractoverlay ports'''}}


Next, reboot the system and the PC-BSD® login manager will start, allowing you to login to the desktop. If you want the [Post Installation Configuration and Installation Troubleshooting |PC-BSD® display wizard and first boot wizards] to run first, run these commands before rebooting:


{{txtbox|box= '''touch /var/.runxsetup'''
'''touch /var/.pcbsd-firstboot'''
'''touch /var/.pcbsd-firstgui'''}}


If you are running FreeBSD 10-CURRENT, specify the PBI version to pull from. To do so, edit ''/usr/local/etc/pbi.conf'' and add this line:

{{txtbox|box=PBI_FBSDMAJOR: 9}}


{{note|icon64= If you are using NVIDIA video hardware, load the driver before rebooting into the display wizard by running the command '''pc-metapkgmanager add NVIDIA'''.}}

== Converting FreeBSD to a TrueOS® Server == 


If you wish to convert a FreeBSD server to TrueOS®, use the following commands:


{{txtbox|box= '''pkg install -fy trueos-base'''
'''rehash'''
'''pbreg set /PC-BSD/SysType TRUEOS'''
'''pc-extractoverlay server'''
'''pc-extractoverlay ports'''}}


The installation of the ''trueos-base'' package will install the following: [[PBI Manager]], the command line version of '''[[Warden®#Using the Command Line Version of Warden® | warden]]''', and the command line versions of most of the [[Control Panel]] utilities. You will find those utilities in ''/usr/local/bin/pc-*''. It also installs this {{citelink|url=http://trac.pcbsd.org/browser/pcbsd/branches/9.1/build-files/metapkgsets/warden/pkgset/base-system/ports-list|txt=list}} of additional shells and utilities.
</translate>
<noinclude>
{{refheading}}
[[category:Convert a FreeBSD System to PC-BSD®]]
[[category:Advanced Installation Topics]]
[[category:handbook]]
<languages/>
</noinclude>

Turn FreeBSD into PC-BSD®

2013-05-26T03:39:02Z

Tigersharke:

{{navHome|custompagename=Turn FreeBSD into PC-BSD{{R}}|custompagecategory=Turn FreeBSD into PC-BSD{{RM}}}}
{{:Convert a FreeBSD System to PC-BSD®}}

Main Page

2013-05-26T03:28:13Z

Tigersharke:

__NOTOC__
{{DISPLAYTITLE:{{FULLPAGENAME}}}} 
[[File:Watermark-772x923.png|link=|alt=watermark background image|772px|]]
<translate>

<div style="position:relative; left: 0px; top: -810px; height: 100px;">
{|style="position:absolute; border: #ffffff solid; border-width: 15px 0px 0px 0px; align: center; border-collapse: collapse; margin-top: -70px; top: -75px; margin-left:0px; margin-right:0px; width: 100%; height: 42px;"
|style="margin:.5em; margin-top:-10px; border-bottom:0; font-weight:bold;" align="center"|Welcome to the PC-BSD{{r}} Wiki!
|} 
:::[http://blog.pcbsd.org/2013/04/important-notice-for-pc-bsd-9-1-32bit-users/ {{redlight|'''Important notice for 32bit users'''}}]
::[http://www.freebsd.org/security/security.html#sup {{orangelight|'''Security WARNING'''}} for users of version 8.1, 8.2, and 9.0.]       [http://lists.freebsd.org/pipermail/freebsd-announce/2013-May/001476.html {{highlight|''' Update '''}} about FreeBSD packages.]
{| cellspacing="0" cellpadding="0" align="center" style="margin-left:auto; margin-right:auto; margin-top:10px; border-collapse: collapse;"

| 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

| 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

| 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
|-

| align="center" style="width:30%; padding:1em; text-align:center;" valign="top"|
[[Wireless Testing]] 
Driver Function & Compatability 
[[Game Testing|Game Testing]] 
Discovering what works and how 
[[EasyPBI2]] 
Simplifying the PBI creation process 
[[Pkgsrc in PC-BSD®|Pkgsrc in PC-BSD{{r}}]] 
Exploring NetBSD pkgsrc potential 
[[Turn FreeBSD into PC-BSD{{RM}}|Turn FreeBSD into PC-BSD{{r}}]] 
Conversion instructions? 
[[:Category:Troubleshooting|Troubleshooting]] 
Solving some problems 
[[Finding Help|Where to find help]] 
Various resources for assistance 
[[Press And Legal|Press/Legal]] 
Press, licensing and other queries

| align="center" style="width:31%; padding:1em; text-align:center;" valign="top"|
[[Warden®|Warden{{r}}]] 
A Jail Management Tool 
[[PBI Manager|The PBI Manager]] 
A Command line Tool Suite 
[[PCDM]] 
PC-BSD's Login Manager 
[[PC-BSD® Users Handbook|PC-BSD{{r}} Users Handbook]] 
Currently under development 
[[Errata|Handbook Errata]] 
Corrections after publishing 
[[Wiki Site TODO]] 
Suggested/implemented changes 
[http://wiki.freebsd.org/IdeasPage FreeBSD{{r}} Ideas page] 
Concepts for possible development 
[http://wiki.freebsd.org/WifiIdeasPage FreeBSD{{r}} Wifi Ideas page] 
Concepts for possible development 

| align="center" style="width:30%; padding:1em; text-align:center;" valign="top"|
[http://trac.pcbsd.org/ PC-BSD{{r}} Trac] 
Source, Reports, or Requests 
[[Become a Developer]] 
How to help with code 
[[Bluetooth Testing]] 
How to help development 
[[PBI9 Format|The PBI9 Format]] 
Improved for 9.0 and beyond 
[[PBI Build Testing]] 
Getting ports turned into PBIs 
[[PC-BSD{{RM}} 9.2 TODO|PC-BSD{{r}} 9.2 Task List]] 
Things to do for the next Version 
[[Google Summer of Code 2011|Google Summer of Code]] 
Application and Information 
|}
 
{| cellspacing="0" cellpadding="0" align="center" style="text-align:center; border:solid #FF3333; border-width:2px 2px 2px 2px; margin:.5em; margin-top:.1em; margin-left:auto; margin-right:auto; margin-top:10px;" width="35%"

| align="center"|
[[Tasks Looking for People]] 
How YOU can contribute
|}
</div>
[[category:PC-BSD® Wiki]]
</translate>
<languages />

Turn FreeBSD into PC-BSD®

2013-05-26T03:25:54Z

Tigersharke:

{{navHome|custompagename=Turn FreeBSD into PC-BSD{{R}}}}
{{:Convert a FreeBSD System to PC-BSD®}}

User:Tigersharke

2013-05-16T21:59:39Z

Tigersharke:

{{DISPLAYTITLE:{{FULLPAGENAME}}}}
{{{custompagename|Tigersharke's User Page}}}

← Hello there → 



;Some Icons developed for the wiki
{|
|-
|[[File:Translate-icon-64x44.png|frame|64px|translate icon 64 pixels]]
|[[File:Translate-icon-32x22.png|frame|32px|32 pixels]]
|[[File:note-msg-icon3.png|frame|64px|'''NOTE:''']]
|[[File:warning-msg-icon.png|frame|64px|'''WARNING''']]
|[[File:danger-msg-icon.png|frame|64px|'''DANGER!''']]
|[[File:Page-left-icon49x48.png|frame|48px|nav icon left]]
|[[File:Page-center-icon38x48.png|frame|nav icon]]
|[[File:Page-right-icon49x48.png|frame|48px|nav icon right]]
|}

;Background
:I used FreeBSD (2.2.6) for a short while a long long time ago, and now have returned to FreeBSD but to the PC-BSD (8.0 ~Feb 2010) version. Once upon a time I managed to get X windows running in BeOS, and in the olden days I had Gno/Me on my Apple IIgs. When I was in school, I took classes in BASIC, LOGO, Pascal, and C. Most of my programming was for class assignments.. and although I was highly interested in writing my own software, I got sidetracked with playing computer games.

;Present
:These days I am hoping to retain all that I learn (or re-learn?!) and add to my skill(s). I'm sometimes troubleshooting, and trying to be of some service to the PC-BSD community. You may have read my blog, {{Citelink|url=http://wiki.spreadpcbsd.org/tiki-view_blog.php?blogId=2|A Little Daemon on My Desktop}} at the {{Citelink|url=http://wiki.spreadpcbsd.org/|PC-BSD advocacy site}}, though it has been on a back burner for quite a while now.

;Hardware
:I hope to use as much of my system's capability as possible. My original system is a Lenovo ThinkCentre A62 9705 CTO, with a Sapphire Radeon HD 5870 (Cypress XT), but I also have some old Dell Optiplex Gs and Gn machines- two have NetBSD installed. The new system that I ''built'' is an 3.40GHz AMD Phenom II X4 965 Black Edition on an ASUS Sabertooth 990FX TUF motherboard with 16GB Kingston DDR3-1866MHz RAM, and I moved the Sapphire to the new PC. A Samsung T260 HD 16:10 TV/Monitor, along with a Kensington Expert Mouse (trackball) and the Lenovo (USB) keyboard are attached to both machines via KVM switch. Audio output via SPDIF and toslink cable to a digital-analog converter and then to a boombox. SPDIF output on my machine is /dev/dsp3, while the former /dev/dsp2 was the front panel headphone jack.

:For the curious, a few speed test results: [http://speedtest.net/result/1374710852.png Jul'11], [http://www.speedtest.net/result/1589307254.png Nov'11], [http://www.speedtest.net/result/2133424881.png Aug'12], [http://www.speedtest.net/result/2477749418.png Jan '13]. Also I may be listening to [http://www.last.fm/user/tigersharke music].
;Below ''dmesg {{!}} head''

Original Lenovo "Mutant" PC:
{{cli|xterm=
Copyright (c) 1992-2011 The FreeBSD Project. 
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
::The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation. 
FreeBSD 9.0-RELEASE #3: Tue Dec 27 14:14:29 PST 2011
::<nowiki>root@build9x64.pcbsd.org:/usr/obj/builds/amd64/pcbsd-build90/fbsd-source/9.0/sys/GENERIC amd64</nowiki> 
CPU: AMD Athlon(tm) Dual Core Processor 5000B (2606.68-MHz K8-class CPU)
:Origin = "AuthenticAMD" Id = 0x60fb2 Family = f Model = 6b Stepping = 2
:Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
:Features2=0x2001<SSE3,CX16>
}}
"Mutant" upgraded:
{{cli|xterm=
Copyright (c) 1992-2012 The FreeBSD Project. 
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
::The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation. 
FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012
::root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ (2907.44-MHz K8-class CPU)
:Origin = "AuthenticAMD" Id = 0x60fb2 Family = f Model = 6b Stepping = 2
:Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
:Features2=0x2001<SSE3,CX16>
}}

The New AMD "ProfessorX" PC I built:
{{cli|xterm=
Copyright (c) 1992-2012 The FreeBSD Project. 
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
::The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation. 
FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012
::root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
CPU: AMD Phenom(tm) II X4 965 Processor (3684.45-MHz K8-class CPU)
:Origin = "AuthenticAMD" Id = 0x100f43 Family = 10 Model = 4 Stepping = 3
:Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
:Features2=0x802009<SSE3,MON,CX16,POPCNT>
}}

"ProfessorX" upgraded:
{{cli|xterm=
Copyright (c) 1992-2012 The FreeBSD Project. 
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
::The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation. 
FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012
::root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
CPU: AMD Phenom(tm) II X4 975 Processor (4013.56-MHz K8-class CPU)
:Origin = "AuthenticAMD" Id = 0x100f43 Family = 10 Model = 4 Stepping = 3
:Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
:Features2=0x802009<SSE3,MON,CX16,POPCNT>
}}

;Methodology
:I used to build/install via ports tree directly in my system, rather than use a pkg or pbi. After I discovered the ease and usefulness of testing/exploration/investigation of various things inside of a jail, I tend to install within a jail for those situations. This does not prevent all of my <nowiki>'</nowiki>''living on the edge''<nowiki>'</nowiki> ways, since there are plenty of ways I could harm myself but it is not a critical style error, and if I run into problems there is a new opportunity for learning. If I discover a port that I like, I will attempt to turn it into a PBI for myself (so that an adjustment to system packages or update doesn't cause it to vanish).

:Since I am still learning, my lack of knowledge combined with my meticulous nature, means problem solving becomes an exploration of permutations and combinations until I happen to stumble across the answer. It is definitely not the fastest method and certainly involves a bit of frustration, but when necessary I put a project away for a while and look at it again when I am not so aggravated.

:I strive for consistency and thoroughness. Where possible, I try to use the full potential of the particular tool/software, and learn what those capabilities are when the need presents itself.

;Contributions
:Of course, I have done some additions and [[Special:Contributions/Tigersharke | many edits of ''this'' site]]. I post to the blog I mentioned earlier and have started a number of topics in the forums on [http://wiki.spreadpcbsd.org/ SpreadPCBSD]. I am usually on #pcbsd on the Freenode irc server, and try to answer questions as best I can.

:One project I tried to tackle was the eventual official [https://code.google.com/p/freebsd-pyside/ port of PySide to FreeBSD]. Those who are curious can get my version of the FreeBSD makefiles etc from the [http://code.google.com/p/freebsd-pyside/source/checkout subversion area]. However, this was successfully completed by someone else as an official FreeBSD port and the work I did can be considered superfluous.

:Revised the v8.2 and v9.0 html version of the ''published'' handbook to include css and sidebar menu.

;Linux is perfectly fine until its inconsistent world of chaos encroaches upon mine.
:Anyone who has had to deal with understanding the reasoning within a Linux Makefile (or CMakelist.txt file) would know how needlessly challenging porting things to BSD can be. If the makefile determines that it isn't building for Linux, you may automatically be lumped in with Windows, or Linux, or some other weird special-case that may not work quite right. In a perfect world, they would test for BSD and let us fill-in how we need things to happen: like proper install directories, naming conventions, dependencies. If they had something much like Mk/linux.bsd_isms.mk similar to our own, we might not always scuff our foreheads so often.

;Generic rebuttal
:Why do I doubt that there are many BSD users who would seriously ask a Linux crowd, "Why should I use flavor X of Linux?"
:yet, Linux users abound who don't see a reason to use BSD and must sarcastically ask, "Why should I use flavor X of BSD?"

;Wash rinse repeat
:{{citelink|url=http://techsupt.winbatch.com/webcgi/webbatch.exe?techsupt/nffunsupt.web+Computer~Industry~Humor+The~Guru~on~OSs.txt|The Guru on Operating Systems}}

Your [[Special:EmailUser/Tigersharke | email]] is welcomed and promptly answered.

--[[User:Tigersharke|Tigersharke]]

{{refheading}}
{{GroupListHeading|group=tables}}
<languages>English
</languages>

User:Tigersharke

2013-05-16T21:58:54Z

Tigersharke:

{{DISPLAYTITLE:{{FULLPAGENAME}}}}
{{{custompagename|Tigersharke's User Page}}}

← Hello there → 



{|
|-
|[[File:Translate-icon-64x44.png|frame|64px|translate icon 64 pixels]]
|[[File:Translate-icon-32x22.png|frame|32px|32 pixels]]
|[[File:note-msg-icon3.png|frame|64px|'''NOTE:''']]
|[[File:warning-msg-icon.png|frame|64px|'''WARNING''']]
|[[File:danger-msg-icon.png|frame|64px|'''DANGER!''']]
|[[File:Page-left-icon49x48.png|frame|48px|nav icon left]]
|[[File:Page-center-icon38x48.png|frame|nav icon]]
|[[File:Page-right-icon49x48.png|frame|48px|nav icon right]]
|}

;Background
:I used FreeBSD (2.2.6) for a short while a long long time ago, and now have returned to FreeBSD but to the PC-BSD (8.0 ~Feb 2010) version. Once upon a time I managed to get X windows running in BeOS, and in the olden days I had Gno/Me on my Apple IIgs. When I was in school, I took classes in BASIC, LOGO, Pascal, and C. Most of my programming was for class assignments.. and although I was highly interested in writing my own software, I got sidetracked with playing computer games.

;Present
:These days I am hoping to retain all that I learn (or re-learn?!) and add to my skill(s). I'm sometimes troubleshooting, and trying to be of some service to the PC-BSD community. You may have read my blog, {{Citelink|url=http://wiki.spreadpcbsd.org/tiki-view_blog.php?blogId=2|A Little Daemon on My Desktop}} at the {{Citelink|url=http://wiki.spreadpcbsd.org/|PC-BSD advocacy site}}, though it has been on a back burner for quite a while now.

;Hardware
:I hope to use as much of my system's capability as possible. My original system is a Lenovo ThinkCentre A62 9705 CTO, with a Sapphire Radeon HD 5870 (Cypress XT), but I also have some old Dell Optiplex Gs and Gn machines- two have NetBSD installed. The new system that I ''built'' is an 3.40GHz AMD Phenom II X4 965 Black Edition on an ASUS Sabertooth 990FX TUF motherboard with 16GB Kingston DDR3-1866MHz RAM, and I moved the Sapphire to the new PC. A Samsung T260 HD 16:10 TV/Monitor, along with a Kensington Expert Mouse (trackball) and the Lenovo (USB) keyboard are attached to both machines via KVM switch. Audio output via SPDIF and toslink cable to a digital-analog converter and then to a boombox. SPDIF output on my machine is /dev/dsp3, while the former /dev/dsp2 was the front panel headphone jack.

:For the curious, a few speed test results: [http://speedtest.net/result/1374710852.png Jul'11], [http://www.speedtest.net/result/1589307254.png Nov'11], [http://www.speedtest.net/result/2133424881.png Aug'12], [http://www.speedtest.net/result/2477749418.png Jan '13]. Also I may be listening to [http://www.last.fm/user/tigersharke music].
;Below ''dmesg {{!}} head''

Original Lenovo "Mutant" PC:
{{cli|xterm=
Copyright (c) 1992-2011 The FreeBSD Project. 
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
::The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation. 
FreeBSD 9.0-RELEASE #3: Tue Dec 27 14:14:29 PST 2011
::<nowiki>root@build9x64.pcbsd.org:/usr/obj/builds/amd64/pcbsd-build90/fbsd-source/9.0/sys/GENERIC amd64</nowiki> 
CPU: AMD Athlon(tm) Dual Core Processor 5000B (2606.68-MHz K8-class CPU)
:Origin = "AuthenticAMD" Id = 0x60fb2 Family = f Model = 6b Stepping = 2
:Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
:Features2=0x2001<SSE3,CX16>
}}
"Mutant" upgraded:
{{cli|xterm=
Copyright (c) 1992-2012 The FreeBSD Project. 
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
::The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation. 
FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012
::root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ (2907.44-MHz K8-class CPU)
:Origin = "AuthenticAMD" Id = 0x60fb2 Family = f Model = 6b Stepping = 2
:Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
:Features2=0x2001<SSE3,CX16>
}}

The New AMD "ProfessorX" PC I built:
{{cli|xterm=
Copyright (c) 1992-2012 The FreeBSD Project. 
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
::The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation. 
FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012
::root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
CPU: AMD Phenom(tm) II X4 965 Processor (3684.45-MHz K8-class CPU)
:Origin = "AuthenticAMD" Id = 0x100f43 Family = 10 Model = 4 Stepping = 3
:Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
:Features2=0x802009<SSE3,MON,CX16,POPCNT>
}}

"ProfessorX" upgraded:
{{cli|xterm=
Copyright (c) 1992-2012 The FreeBSD Project. 
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
::The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation. 
FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012
::root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
CPU: AMD Phenom(tm) II X4 975 Processor (4013.56-MHz K8-class CPU)
:Origin = "AuthenticAMD" Id = 0x100f43 Family = 10 Model = 4 Stepping = 3
:Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
:Features2=0x802009<SSE3,MON,CX16,POPCNT>
}}

;Methodology
:I used to build/install via ports tree directly in my system, rather than use a pkg or pbi. After I discovered the ease and usefulness of testing/exploration/investigation of various things inside of a jail, I tend to install within a jail for those situations. This does not prevent all of my <nowiki>'</nowiki>''living on the edge''<nowiki>'</nowiki> ways, since there are plenty of ways I could harm myself but it is not a critical style error, and if I run into problems there is a new opportunity for learning. If I discover a port that I like, I will attempt to turn it into a PBI for myself (so that an adjustment to system packages or update doesn't cause it to vanish).

:Since I am still learning, my lack of knowledge combined with my meticulous nature, means problem solving becomes an exploration of permutations and combinations until I happen to stumble across the answer. It is definitely not the fastest method and certainly involves a bit of frustration, but when necessary I put a project away for a while and look at it again when I am not so aggravated.

:I strive for consistency and thoroughness. Where possible, I try to use the full potential of the particular tool/software, and learn what those capabilities are when the need presents itself.

;Contributions
:Of course, I have done some additions and [[Special:Contributions/Tigersharke | many edits of ''this'' site]]. I post to the blog I mentioned earlier and have started a number of topics in the forums on [http://wiki.spreadpcbsd.org/ SpreadPCBSD]. I am usually on #pcbsd on the Freenode irc server, and try to answer questions as best I can.

:One project I tried to tackle was the eventual official [https://code.google.com/p/freebsd-pyside/ port of PySide to FreeBSD]. Those who are curious can get my version of the FreeBSD makefiles etc from the [http://code.google.com/p/freebsd-pyside/source/checkout subversion area]. However, this was successfully completed by someone else as an official FreeBSD port and the work I did can be considered superfluous.

:Revised the v8.2 and v9.0 html version of the ''published'' handbook to include css and sidebar menu.

;Linux is perfectly fine until its inconsistent world of chaos encroaches upon mine.
:Anyone who has had to deal with understanding the reasoning within a Linux Makefile (or CMakelist.txt file) would know how needlessly challenging porting things to BSD can be. If the makefile determines that it isn't building for Linux, you may automatically be lumped in with Windows, or Linux, or some other weird special-case that may not work quite right. In a perfect world, they would test for BSD and let us fill-in how we need things to happen: like proper install directories, naming conventions, dependencies. If they had something much like Mk/linux.bsd_isms.mk similar to our own, we might not always scuff our foreheads so often.

;Generic rebuttal
:Why do I doubt that there are many BSD users who would seriously ask a Linux crowd, "Why should I use flavor X of Linux?"
:yet, Linux users abound who don't see a reason to use BSD and must sarcastically ask, "Why should I use flavor X of BSD?"

;Wash rinse repeat
:{{citelink|url=http://techsupt.winbatch.com/webcgi/webbatch.exe?techsupt/nffunsupt.web+Computer~Industry~Humor+The~Guru~on~OSs.txt|The Guru on Operating Systems}}

Your [[Special:EmailUser/Tigersharke | email]] is welcomed and promptly answered.

--[[User:Tigersharke|Tigersharke]]

{{refheading}}
{{GroupListHeading|group=tables}}
<languages>English
</languages>

User:Tigersharke

2013-05-16T21:58:38Z

Tigersharke:

{{DISPLAYTITLE:{{FULLPAGENAME}}}}
{{{custompagename|Tigersharke's User Page}}}

← Hello there → 

{{tbl-init|width=80%|caption= for testing appearance}}
{{tbl-title|Some example}}
!column titles
|-
{{tbl-cell|when CSS styles work}}
|Left and right shall match
|-
{{tbl-cell|simply by using}}
|class=spiffy_table (default)
|}



{|
|-
|[[File:Translate-icon-64x44.png|frame|64px|translate icon 64 pixels]]
|[[File:Translate-icon-32x22.png|frame|32px|32 pixels]]
|[[File:note-msg-icon3.png|frame|64px|'''NOTE:''']]
|[[File:warning-msg-icon.png|frame|64px|'''WARNING''']]
|[[File:danger-msg-icon.png|frame|64px|'''DANGER!''']]
|[[File:Page-left-icon49x48.png|frame|48px|nav icon left]]
|[[File:Page-center-icon38x48.png|frame|nav icon]]
|[[File:Page-right-icon49x48.png|frame|48px|nav icon right]]
|}

;Background
:I used FreeBSD (2.2.6) for a short while a long long time ago, and now have returned to FreeBSD but to the PC-BSD (8.0 ~Feb 2010) version. Once upon a time I managed to get X windows running in BeOS, and in the olden days I had Gno/Me on my Apple IIgs. When I was in school, I took classes in BASIC, LOGO, Pascal, and C. Most of my programming was for class assignments.. and although I was highly interested in writing my own software, I got sidetracked with playing computer games.

;Present
:These days I am hoping to retain all that I learn (or re-learn?!) and add to my skill(s). I'm sometimes troubleshooting, and trying to be of some service to the PC-BSD community. You may have read my blog, {{Citelink|url=http://wiki.spreadpcbsd.org/tiki-view_blog.php?blogId=2|A Little Daemon on My Desktop}} at the {{Citelink|url=http://wiki.spreadpcbsd.org/|PC-BSD advocacy site}}, though it has been on a back burner for quite a while now.

;Hardware
:I hope to use as much of my system's capability as possible. My original system is a Lenovo ThinkCentre A62 9705 CTO, with a Sapphire Radeon HD 5870 (Cypress XT), but I also have some old Dell Optiplex Gs and Gn machines- two have NetBSD installed. The new system that I ''built'' is an 3.40GHz AMD Phenom II X4 965 Black Edition on an ASUS Sabertooth 990FX TUF motherboard with 16GB Kingston DDR3-1866MHz RAM, and I moved the Sapphire to the new PC. A Samsung T260 HD 16:10 TV/Monitor, along with a Kensington Expert Mouse (trackball) and the Lenovo (USB) keyboard are attached to both machines via KVM switch. Audio output via SPDIF and toslink cable to a digital-analog converter and then to a boombox. SPDIF output on my machine is /dev/dsp3, while the former /dev/dsp2 was the front panel headphone jack.

:For the curious, a few speed test results: [http://speedtest.net/result/1374710852.png Jul'11], [http://www.speedtest.net/result/1589307254.png Nov'11], [http://www.speedtest.net/result/2133424881.png Aug'12], [http://www.speedtest.net/result/2477749418.png Jan '13]. Also I may be listening to [http://www.last.fm/user/tigersharke music].
;Below ''dmesg {{!}} head''

Original Lenovo "Mutant" PC:
{{cli|xterm=
Copyright (c) 1992-2011 The FreeBSD Project. 
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
::The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation. 
FreeBSD 9.0-RELEASE #3: Tue Dec 27 14:14:29 PST 2011
::<nowiki>root@build9x64.pcbsd.org:/usr/obj/builds/amd64/pcbsd-build90/fbsd-source/9.0/sys/GENERIC amd64</nowiki> 
CPU: AMD Athlon(tm) Dual Core Processor 5000B (2606.68-MHz K8-class CPU)
:Origin = "AuthenticAMD" Id = 0x60fb2 Family = f Model = 6b Stepping = 2
:Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
:Features2=0x2001<SSE3,CX16>
}}
"Mutant" upgraded:
{{cli|xterm=
Copyright (c) 1992-2012 The FreeBSD Project. 
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
::The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation. 
FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012
::root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ (2907.44-MHz K8-class CPU)
:Origin = "AuthenticAMD" Id = 0x60fb2 Family = f Model = 6b Stepping = 2
:Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
:Features2=0x2001<SSE3,CX16>
}}

The New AMD "ProfessorX" PC I built:
{{cli|xterm=
Copyright (c) 1992-2012 The FreeBSD Project. 
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
::The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation. 
FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012
::root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
CPU: AMD Phenom(tm) II X4 965 Processor (3684.45-MHz K8-class CPU)
:Origin = "AuthenticAMD" Id = 0x100f43 Family = 10 Model = 4 Stepping = 3
:Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
:Features2=0x802009<SSE3,MON,CX16,POPCNT>
}}

"ProfessorX" upgraded:
{{cli|xterm=
Copyright (c) 1992-2012 The FreeBSD Project. 
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
::The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation. 
FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012
::root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
CPU: AMD Phenom(tm) II X4 975 Processor (4013.56-MHz K8-class CPU)
:Origin = "AuthenticAMD" Id = 0x100f43 Family = 10 Model = 4 Stepping = 3
:Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
:Features2=0x802009<SSE3,MON,CX16,POPCNT>
}}

;Methodology
:I used to build/install via ports tree directly in my system, rather than use a pkg or pbi. After I discovered the ease and usefulness of testing/exploration/investigation of various things inside of a jail, I tend to install within a jail for those situations. This does not prevent all of my <nowiki>'</nowiki>''living on the edge''<nowiki>'</nowiki> ways, since there are plenty of ways I could harm myself but it is not a critical style error, and if I run into problems there is a new opportunity for learning. If I discover a port that I like, I will attempt to turn it into a PBI for myself (so that an adjustment to system packages or update doesn't cause it to vanish).

:Since I am still learning, my lack of knowledge combined with my meticulous nature, means problem solving becomes an exploration of permutations and combinations until I happen to stumble across the answer. It is definitely not the fastest method and certainly involves a bit of frustration, but when necessary I put a project away for a while and look at it again when I am not so aggravated.

:I strive for consistency and thoroughness. Where possible, I try to use the full potential of the particular tool/software, and learn what those capabilities are when the need presents itself.

;Contributions
:Of course, I have done some additions and [[Special:Contributions/Tigersharke | many edits of ''this'' site]]. I post to the blog I mentioned earlier and have started a number of topics in the forums on [http://wiki.spreadpcbsd.org/ SpreadPCBSD]. I am usually on #pcbsd on the Freenode irc server, and try to answer questions as best I can.

:One project I tried to tackle was the eventual official [https://code.google.com/p/freebsd-pyside/ port of PySide to FreeBSD]. Those who are curious can get my version of the FreeBSD makefiles etc from the [http://code.google.com/p/freebsd-pyside/source/checkout subversion area]. However, this was successfully completed by someone else as an official FreeBSD port and the work I did can be considered superfluous.

:Revised the v8.2 and v9.0 html version of the ''published'' handbook to include css and sidebar menu.

;Linux is perfectly fine until its inconsistent world of chaos encroaches upon mine.
:Anyone who has had to deal with understanding the reasoning within a Linux Makefile (or CMakelist.txt file) would know how needlessly challenging porting things to BSD can be. If the makefile determines that it isn't building for Linux, you may automatically be lumped in with Windows, or Linux, or some other weird special-case that may not work quite right. In a perfect world, they would test for BSD and let us fill-in how we need things to happen: like proper install directories, naming conventions, dependencies. If they had something much like Mk/linux.bsd_isms.mk similar to our own, we might not always scuff our foreheads so often.

;Generic rebuttal
:Why do I doubt that there are many BSD users who would seriously ask a Linux crowd, "Why should I use flavor X of Linux?"
:yet, Linux users abound who don't see a reason to use BSD and must sarcastically ask, "Why should I use flavor X of BSD?"

;Wash rinse repeat
:{{citelink|url=http://techsupt.winbatch.com/webcgi/webbatch.exe?techsupt/nffunsupt.web+Computer~Industry~Humor+The~Guru~on~OSs.txt|The Guru on Operating Systems}}

Your [[Special:EmailUser/Tigersharke | email]] is welcomed and promptly answered.

--[[User:Tigersharke|Tigersharke]]

{{refheading}}
{{GroupListHeading|group=tables}}
<languages>English
</languages>

MediaWiki:Deletereason-dropdown

2013-05-16T21:54:32Z

Tigersharke:

*Common delete reasons
** Author request
** Copyright violation
** Talk page link SPAM
** SPAM
** Vandalism

Main Page

2013-05-14T19:51:17Z

Tigersharke:

__NOTOC__
{{DISPLAYTITLE:{{FULLPAGENAME}}}} 
[[File:Watermark-772x923.png|link=|alt=watermark background image|772px|]]
<translate>

<div style="position:relative; left: 0px; top: -810px; height: 100px;">
{|style="position:absolute; border: #ffffff solid; border-width: 15px 0px 0px 0px; align: center; border-collapse: collapse; margin-top: -70px; top: -75px; margin-left:0px; margin-right:0px; width: 100%; height: 42px;"
|style="margin:.5em; margin-top:-10px; border-bottom:0; font-weight:bold;" align="center"|Welcome to the PC-BSD{{r}} Wiki!
|} 
:::[http://blog.pcbsd.org/2013/04/important-notice-for-pc-bsd-9-1-32bit-users/ {{redlight|'''Important notice for 32bit users'''}}]
::[http://www.freebsd.org/security/security.html#sup {{orangelight|'''Security WARNING'''}} for users of version 8.1, 8.2, and 9.0.]       [http://lists.freebsd.org/pipermail/freebsd-announce/2013-May/001476.html {{highlight|''' Update '''}} about FreeBSD packages.]
{| cellspacing="0" cellpadding="0" align="center" style="margin-left:auto; margin-right:auto; margin-top:10px; border-collapse: collapse;"

| align="center" style="text-align:center; margin:.5em; margin-top:.1em; border-bottom:1; font-weight:bold; font-size: 150%" width="28%" height="50px"|Documentation

| align="center" style=" text-align:center; margin:.5em; margin-top:.1em; border-bottom:1; font-weight:bold; font-size: 150%" width="28%" height="50px"|Projects

| align="center" style="text-align:center; margin:.5em; margin-top:.1em; border-bottom:1; font-weight:bold; font-size: 150%" width="28%" height="50px"|Development
|-

| align="center" style="width:28%; padding:1em; text-align:center;" valign="top"|
[[Wireless Testing]] 
Driver Function & Compatability 
[[Game Testing|Game Testing]] 
Discovering what works and how 
[[EasyPBI2]] 
Simplifying the PBI creation process 
[[Pkgsrc in PC-BSD®|Pkgsrc in PC-BSD{{r}}]] 
Exploring NetBSD pkgsrc potential 
[[Turn FreeBSD into PC-BSD®|Turn FreeBSD into PC-BSD{{r}}]] 
Conversion instructions? 
[[:Category:Troubleshooting|Troubleshooting]] 
Solving some problems 
[[Finding Help|Where to find help]] 
Various resources for assistance 
[[Press And Legal|Press/Legal]] 
Press, licensing and other queries

| align="center" style="width:28%; padding:1em; text-align:center;" valign="top"|
[[Warden®|Warden{{r}}]] 
A Jail Management Tool 
[[PBI Manager|The PBI Manager]] 
A Command line Tool Suite 
[[PCDM]] 
PC-BSD's Login Manager 
 
[[PC-BSD® Users Handbook|PC-BSD{{r}} Users Handbook]] 
Currently under development 
[[Errata|Handbook Errata]] 
Corrections after publishing 
[[Wiki Site TODO]] 
Suggested/implemented changes 
 
[http://wiki.freebsd.org/IdeasPage FreeBSD{{r}} Ideas page] 
Concepts for possible development 
[http://wiki.freebsd.org/WifiIdeasPage FreeBSD{{r}} Wifi Ideas page] 
Concepts for possible development 

| align="center" style="width:28%; padding:1em; text-align:center;" valign="top"|
[http://trac.pcbsd.org/ PC-BSD{{r}} Trac] 
Source, Reports, or Requests 
[[Become a Developer]] 
How to help with code 
[[Bluetooth Testing]] 
How to help development 
[[PBI9 Format|The PBI9 Format]] 
Improved for 9.0 and beyond 
[[PBI Build Testing]] 
Getting ports turned into PBIs 
[[PC-BSD{{RM}} 9.2 TODO|PC-BSD{{r}} 9.2 Task List]] 
Things to do for the next Version 
[[Google Summer of Code 2011|Google Summer of Code]] 
Application and Information 
|}
 
{| cellspacing="0" cellpadding="0" align="center" style="text-align:center; border:solid #FF3333; border-width:2px 2px 2px 2px; margin:.5em; margin-top:.1em; margin-left:auto; margin-right:auto; margin-top:10px;" width="35%"

| align="center"|
[[Tasks Looking for People]] 
How YOU can contribute
|}
</div>
[[category:PC-BSD® Wiki]]
</translate>
<languages />

Wireless Testing

2013-05-11T19:59:06Z

Tigersharke:

{{NavHome}}

This area of the wiki is for those who wish to assist by reporting non-working wireless drivers or by testing new drivers. Both reporting and testing provides valuable information to the developers of wireless drivers. It also helps to ensure that PC-BSD® and FreeBSD provide support for the wireless devices used by their users.

This page contains four tables:

* [[#Table 1: Wireless Devices Needing Drivers: Does ndisgen Work for this Device? | Table 1]]: devices in this table do not have a FreeBSD driver yet. If your device requires you to run the '''ndisgen''' script to convert a Windows driver to a FreeBSD driver module, it belongs in this table. Such devices use ndis(4) as their driver name. The goal of this table is to determine which devices need a native FreeBSD driver.

* [[#Table 2: Existing Wireless Drivers That Do not Work Well | Table 2]]: devices in this table already have a FreeBSD driver, but there are problems with the driver e.g. certain features are unavailable or the driver crashes. The goal of this table is to provide information to developers so the driver can be fixed. This means that you should reference any existing PRs or other URLs containing a description of the problem. If a PR does not exist, consider submitting one; information on how to submit a useful PR can be found at {{Citelink|url=http://www.freebsd.org/doc/en/articles/problem-reports/article.html|txt=Writing FreeBSD Problem Reports}}.

* [[#Table 3: Wireless Devices Known to Work | Table 3]]: devices in this table have a working FreeBSD driver, making it a quick reference to determine if a device is supported. If your device works and is not in the table, take a minute to create a wiki login account and add an entry for your device.

* [[#Table 4: Devices Needing Drivers | Table 4]]: devices in this table have users who desire support but lack a FreeBSD driver.

If your wireless device is not supported and is not listed in [[#Table 1: Wireless Devices Needing Drivers: Does ndisgen Work for this Device? | Table 1]], please create a wiki account and add it. However, please do a little bit of research first:

* Perform a web search for the name of the device and the word FreeBSD (for example, "freebsd broadcom 5709"). This should give you a good idea if the driver already exists--and if so, the name of the driver--or if other FreeBSD users have had problems getting their device to work.

* If you are not sure of the name and model of your internal device, try this command: '''pciconf -lv | grep -i wireless'''. If the device is USB, try '''usbconfig dump_all_config_desc'''.

* If a FreeBSD driver does not exist, download a Windows driver for the device, run the interactive script '''ndisgen''' as the superuser, and see if you can successfully use the generated driver module. Add the results for your architecture (i386 or amd64) to [[#Table 1: Wireless Devices Needing Drivers: Does ndisgen Work for this Device? | Table 1]].

'''Note:''' ndisgen currently does not support the NDIS 6.X API. In practical terms, this means that you should only try it on XP and 2003 drivers. Make sure you download and try to convert the correct driver for your architecture (32 or 64 bit). If you would like to help test the most recent version of ndisgen, follow {{Citelink|url=http://blog.pcbsd.org/2010/11/looking-for-ndis-testers-freebsd-and-pc-bsd/|txt=these instructions}}.

'''Note:''' report of ndisgen process causing a faulty situation. '''Description:''' Wireless is active, but when trying to connect to the network, the screen goes dark and the system stops responding. The black screen can be removed by restarting, but after reboot PC-BSD® does not enter the boot loader section. The system shows a prompt ''FreeBSD (Amnesia mode)''. '''Likely solution:''' {{Citelink|url=http://www.freebsd.org/cgi/query-pr.cgi?pr=165622&sourceid=opensearch|txt=FreeBSD problem report and patch}} for "Unregistered use of FPU in kernel" panic caused by miniport driver adapted via ndisgen.

'''Note to iwi(4) users:''' work is ongoing to improve this driver. Please see {{Citelink|url=http://people.freebsd.org/~bschmidt/iwi/|txt=Bernhard Schmidt's iwi wiki}} if you are interested in testing these changes.

== Table 1: Wireless Devices Needing Drivers: Does ndisgen Work for this Device? ==

{| class=spiffy_table
!Device Name
!i386
!amd64
!Comments
|-
|BCM4310
|
|NO
|
|-
|BCM4313
|YES
|YES
|Download this {{Citelink|url=http://dl.dropbox.com/u/1101857/%5Bwikidrivers.com%5D%20Broadcom_BCM43xx_5.100.235.19_win5x.exe|txt=WinXP}} driver, add bcmwl5.inf and bcmwl5.sys (bcmwl564.sys if using the amd64 version of freebsd) as driver files and both bcm43xx.cat (bcm43xx64.cat for amd64) and bcmwlcoi.dll (bcmwlcoi64.dll for amd64) as firmware files (this is important, if you do not add them through the ndisgen interface you will get a kernel panic as soon as you kldload the bcmwl5_sys.ko or bcmwl564_sys.ko file), move all the generated *.ko files to /boot/modules, add {{Citelink|url=http://pastebin.com/bRPaBS7N|txt=this}} to your /etc/rc.conf ({{Citelink|url=http://pastebin.com/qYR1wXs4|txt=this}} for amd64 users), and {{Citelink|url=http://pastebin.com/s2gBzVVQL|txt=this}} to your /boot/loader.conf, add your wpa_supplicant.conf file to /etc and finally reboot the PC to get the drivers loaded and interfaces created.
Note: The WinXP drivers mentioned above work only on FreeBSD 9.0RC3 and later, if you need to use FreeBSD 8.2 or 7.4 use the curtiebo's Win98 driver, also the drivers listed are extremelly sensitive to correct timing during installation and can brick your *BSD install, and are also very unstable and cause lots of kernel panics.
|-
|RTL8185
|YES
|YES
|Try Me driver instead of XP. Use XP driver version 1.10. Should be about 280 KiB in size. Must manually load driver. Placing it in /boot/loader.conf did not initialize device. As far as I have tested it fully works. You may have to manually configure it as well. The graphical network manager did not work for me. (More info in discussion). Just finished setting up amd64 system. XP64 driver version 1.10 does work (using it now). Follow same procedures as i386 driver.
|-
|RT3062
|YES
|Not tested
|Appears to be working, but not fully functional. Have had an issue where sometimes it will not connect on boot and I've had to reboot. Also it has serious issues with uploading. Using {{Citelink|url=http://zonetusa.net/media/import/ZEW16X2_DRxp.zipL|txt=this driver}}
|-
|RTL8191SE
|YES
|NO
|driver Vistax64: ndisgen generates rtl8192se_sys.ko . kernel load it , but module isn't used. pciconf -lv output : 
none7@pci0:10:0:0:class=0x028000 card=0x818110ec chip=0x817210ec rev=0x10 hdr=0x00 
vendor = 'Realtek Semiconductor' 
device = 'Realtek RTL8191SE wireless LAN 802.11N PCI-E NIC (RTL8191SE ?)' 
class = network 

Vista drivers are not XP drivers and will not work.
|-
|RTL8187SE
|YES
|NO
|Not kldload if_ndis, says the archive already exists. PC-BSD® (x86) is restarted after kldload rtl8187Se_sys.ko from Windows XP driver. The wireless continue to not function.
|-
|RTL8192SE
|YES
|YES, in 8.2
|use the the Windows XP driver
|-
|}

If a driver exists for your wireless device but the driver does not work well, add a description of the problem to [[#Table 2: Existing Wireless Drivers That Do not Work Well | Table 2]]. Take a minute to {{Citelink|url=http://www.freebsd.org/cgi/query-pr-summary.cgi?query|txt=query the PR database}} and add the PR number if one exists.

== Table 2: Existing Wireless Drivers That Do not Work Well ==

{| class=spiffy_table
!Driver Name
!i386
!amd64
!PR Number
!Comments
|-
|rum
|X
|X
|
|Some chip revisions have problems with poor signal strength if distance from AP is medium to high.
|-
|wpi
|
|
|
|Known issue in 8.2 (http://www.freebsd.org/cgi/query-pr.cgi?pr=143874). Updating src and rebuilding kernel as per that link or upgrading to 9.0 fixes issue.
|}

[[#Table 3: Wireless Devices Known to Work | Table 3]] provides a handy resource for checking to see if your wireless driver is known to work on FreeBSD and PC-BSD®. Devices should be added alphabetically (then numerically). Only add devices that you have successfully used (e.g. do not add devices that "should" work according to the driver man page).

== Table 3: Wireless Devices Known to Work ==

{| class=spiffy_table
!Device Name
!Driver
!i386
!amd64
!Comments
|-
|AR5001
|ath
|YES
|
|
|-
|AR9285
|ath
|YES
|YES
|works in 9.1
|-
| Belkin 54G (F5D7050)
| rum
| YES
|
| external USB
|-
|Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card (BCM4311)
|bwn
|YES
|YES
|Works in 8.1 or later, only station, adhoc-demo and monitor mode is currently supported. Must install net/bwn-firmware-kmod port. Not the bwi-firmware-kmod. 8.1 users may need to modify /usr/src/sys/kern/subr_firmware.c to read FIRMWARE_MAX 50 and recompile their kernel; this is not necessary in 8.2 or higher.
|-
|Broadcom 802.11b/g (BCM4318)
|bwn
|YES
|YES
|Same as above
|-
| Intel 5100AGN
| iwn
|
|
|Should work in 8.1 or later
|-
|Intel 6205a
|iwn
|
|
|Works in 9.0. Instructions for 8.2 at http://blog.cochard.me/2011/08/backporting-intel-prowireless-6205a.html
|-
|Intel Centrino Advanced-N 6230
|iwn
|
|
|Should work in 8.3 and later
|-
|RLT8187B
|urtw
|
|
|Should work in 8.0 or later
|-
|}

== Table 4: Devices Needing Drivers ==

The following interfaces need a FreeBSD driver:

{| class=spiffy_table
!Device Name
!Driver Sources/Notes
|-
|AR9287
|committed to HEAD May 26/11
|-
|BCM4321
|bwn(4) needs support for N PHYs
|-
|BCM4322
|
|-
|BCM43224
|http://wireless.kernel.org/en/users/Drivers/brcm80211
|-
|BCM43225
|http://wireless.kernel.org/en/users/Drivers/brcm80211
|-
|BCM4313
|http://wireless.kernel.org/en/users/Drivers/brcm80211
|-
|DW1501
|Its actually a BCM4313, PCI Id. 0x4727, thus same driver at http://wireless.kernel.org/en/users/Drivers/brcm80211
|-
|RT2760T
|does not seem to have a blob for Linux yet
|-
|RT2800
|
|-
|RT2860
|http://forums.pcbsd.org/showthread.php?t=13722&page=2
|-
|RT5390
|http://www.phoronix.com/scan.php?page=news_item&px=OTA5MA open sourced in 2/11
|-
|RTL8188CE
|OpenBSD uses urtwn
|-
|}

== Additional Information ==

=== Mobile broadband ===
{{Citelink|url=http://packages.ubuntu.com/precise/mobile-broadband-provider-info|txt=Mobile Broadband provider info}}

<noinclude>{{refheading}}</noinclude>

PC-BSD Wiki:Style Guidelines

2013-05-09T11:12:36Z

Tigersharke: /* Tables */

{{swapTitle|custompagename=PC-BSD{{r}} Wiki:Style Guidelines|custompagecategory=PC-BSD{{RM}} Wiki:Style Guidelines}}
== Objective ==

The purpose of defining how pages on the wiki should be created, is to help maintain consistency by having a set standard or model to follow, to enable easier translations of the site into other languages, and allow publishing with less modification.

== Text ==

The guideline for actual text content may be under continual refinement with frequent additions until nearly complete. In areas that are incomplete or not yet defined, a reasonable default can be taken from the [[wikipedia:Wikipedia:Manual of Style|Wikipedia:Manual of Style]].

=== Typographic Conventions ===

The PC-BSD Handbook uses the following typographic conventions:

: '''bold text:''' represents a command written at the command line. In usage examples, the font is changed with any command output displayed in unbolded text.
: ''italic text:'' used to represent device names or file name paths.
: ''' ''bold italic text:'' ''' used to emphasize an important point.

==== Emphasis ====

; Notes
: Often we need to specifically call attention to a particular caveat, or other tidbit of information that is not mission critical.
: {{note|This is an example that spans the width of the page.'''<nowiki>{{</nowiki>note{{pipe}}'''''text'''''<nowiki>}}</nowiki>'''}}
: {{note|icon64=Include an icon for larger notes by assigning the text to ''icon64'' when the template is used, such as '''<nowiki>{{</nowiki>note{{pipe}}icon64='''''text'''''<nowiki>}}</nowiki>'''. This icon is the classic ''tie a string around your finger to help remember'', the green triangle is used in hopes of implying that you can continue safely. As you can see with this text box, the message content neatly wraps around the icon. This wrapping will continue neatly around the icon, even when there is sufficient text that the position of the lines in the message fall below the it. The same effect with 64px icons and wrapping text content works for the other two icon message boxes described below.}}

; Warning
: Some instructions have frustrating or annoying consequences and therefore should be emphasized.
: {{warning|The simple quick one-line comment. Use '''<nowiki>{{</nowiki>warning{{pipe}}'''''text'''''<nowiki>}}</nowiki>''' for this.}}
: {{warning|icon64=A verbose and descriptive warning. The concept behind the icon is that something may have been missed, stop and check, investigate. '''<nowiki>{{</nowiki>warning{{pipe}}icon64='''''text'''''<nowiki>}}</nowiki>'''}}

; Dangerous
: Some instructions are critically dangerous and may result in serious harm if a mistake is made.
: {{danger|The simple quick one-line comment. It is invoked by '''<nowiki>{{</nowiki>warning{{pipe}}'''''text'''''<nowiki>}}</nowiki>'''}}
: {{danger|icon64=The text content probably should default to '''bold''' or '''''bold and italic'''''. This icon hopes to clearly indicate possible damage to the PC involved. '''<nowiki>{{</nowiki>danger{{pipe}}icon64='''''text'''''<nowiki>}}</nowiki>'''}}

; Highlighted text
: In certain circumstances, especially to show revisions such as on the [[errata]] page or on [[#Hypertext Links|this page]] to more clearly show what to replace, there is the highlight template: '''<nowiki>{{</nowiki>highlight{{pipe}}text='''''text'''''<nowiki>}}</nowiki>'''
: In the context of this sentence only {{highlight|text=this portion of text}} has the highlight effect.

; Redlighted text
: This should only have limited use for the sole purpose of adding emphasis to {{redlight|critical and dangerous}} information.
: '''<nowiki>{{</nowiki>redlight{{pipe}}text='''''text'''''<nowiki>}}</nowiki>'''

; Orangelighted text
: This should not be used except in the warning text box, but could aid in emphasis to {{orangelight|details that could cause frustration.}}
: '''<nowiki>{{</nowiki>orangelight{{pipe}}text='''''text'''''<nowiki>}}</nowiki>'''

=== Language usage and word choice ===

; Variety
: Use words and phrases with the same meaning; multiple types of sentence structure.

; Contractions: In place of: {{txtbox|override|margin-top=-5px|margin-bottom=0px|box={{nbsp|2}}'''''aren't''''' use '''''are not''''', '''''can't''''' use '''''can not''''', '''''cannot''''' use '''''can not''''',
{{nbsp|2}}'''''doesn't''''' use '''''does not''''', '''''don't''''' use '''do not''', '''''hasn't''''' use '''''has not'''''
{{nbsp|2}}'''''haven't''''' use '''''have not''''', '''''weren't''''' use '''''were not''''', '''''won't''''' use '''''will not''''',
{{nbsp|2}}'''''you'll''''' use '''''you will''''', '''''you'd''''' use '''''you would''''', '''''you're''''' use '''''you are''''',
{{nbsp|2}}'''''you've''''' use '''''you have'''''.}}

; Brand names
: Use '''''web''' search'' instead of '''''Google''' search''.

; Idioms
: Use proper and precise wording.
:: '''''Watch closely''''' should be used instead of '''''keep an eye on'''''.
:: '''''Crashes''''' or '''''fails''''' in place of '''''gets a blue screen of death'''''.
: [[wikipedia:Idiom|Idioms described on wikipedia]].

; Slang
: Use precise rather than colorful or regional terms, however some technical jargon is allowable especially if explained or defined.
:: '''''Open a browser to pcbsd.org''''' would be used instead of '''''surf to pcbsd'''''.
: [[wikipedia:Slang|Slang described on wikipedia]].
: [[wikipedia:Jargon|Jargon described on wikipedia]].

; Dates
: Given that some date formats can be problematic: (07-03-2012) Does the author mean July 3rd 2012, or March 7th 2012. The wiki offers a per-user preference for date format. This also formalizes instances of dates which may also aid translations.
:: '''<nowiki>{{</nowiki>#dateformat:'''''01 May 2012'''''}}''' should be used resulting in {{#dateformat:01 May 2012}} which conforms to each user's preferences.

; Uncapped proper names
: Some software is officially named in lowercase, yet sentences should ''usually'' begin with a capital letter. The solution is to avoid using those special proper names as the word that begins a sentence.

=== Hypertext Links ===

Within the text, it is helpful to add a link to topics, pages, and sites to further explain and allow for additional research.
; Name
: Use a descriptive word or phrase. It can be the general location (page/site) of the link, as long as the link itself is to the specific section (when ever possible). Try not to be too general/generic. Highlight and italic are used for clarity in the examples below.
:: '''Replace this:''' You can find more information about hardware compatibility {{highlight|{{citelink|url=http://forums.freebsd.org/forumdisplay.php?f=32|txt=''here.''}}}}
:: '''With this:''' You can find more information about hardware compatibility {{highlight|on the}} {{highlight|{{citelink|url=http://forums.freebsd.org/forumdisplay.php?f=32|''FreeBSD hardware forum''}}}}.

:: '''Replace this:''' {{highlight|{{citelink|url=http://forums.freebsd.org/forumdisplay.php?f=32|txt=''This forum post''}}}} explains how to properly plug the outlet tube of an inlet drain line.
:: '''With this:''' {{highlight|This}} {{highlight|{{citelink|url=http://forums.freebsd.org/forumdisplay.php?f=32|''PlumberCraft forum post''}}}} explains how to properly plug the outlet tube of an inlet drain line.

; URL
: Use an ending slash with any url that leads to a directory or non-file (such as any site name). It is prudent to verify that an adjusted link is valid since some sites do not use extensions for file names. This convention will aid with consistency and help to eliminate technically different but effectively identical URLs.
:: '''This is a valid url:''' <nowiki>http://</nowiki>forums.freebsd.org
:: '''Url with proper syntax on this wiki:''' <nowiki>http://</nowiki>forums.freebsd.org/
:: '''Example of a url that ends with a file name:''' <nowiki>http://</nowiki>www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sound-setup.html

; Internal
: The URL is within the PC-BSD wiki.
:: Use '''<nowiki>[[</nowiki>'''''page name'''''<nowiki>]]</nowiki>''' or '''<nowiki>[[</nowiki>'''''page name'''''|'''''alternate text'''''<nowiki>]]</nowiki>'''

; External
: The URL is for a location outside of wiki.pcbsd.org. Most places where an external link may be used, there is alternate text shown, which means for a printed handbook, there must be a footnote to provide the actual URL. Those rare places that do not provide alternate text but show the actual URL, do not need the ''[[template:citelink|citelink]]''. If the link text is to be '''bold''' or ''italic'' or '''''both''''' then the modifier characters must be directly around the ''alternate text'' and not around the entire ''citelink'' phrase below.
:: For the link use '''<nowiki>{{Citelink|url=</nowiki>'''''complete URL'''''|txt='''''alternate text'''''}}'''
: Also place a total of exactly one '''<nowiki><noinclude>{{refheading}}</noinclude></nowiki>''' at the bottom of the page, above the category links section.

; Special External
: The URL is for a site not part of the PC-BSD wiki, but has a defined [[mediawikiwiki:Manual:Interwiki|interwiki]] shortcut such as for wikipedia.
: Valid markup is '''<nowiki>[[</nowiki>'''wikipedia:''page name'''''<nowiki>]]</nowiki>''' or '''<nowiki>[[</nowiki>'''wikipedia:''page name'''''|'''''alternate text'''''<nowiki>]]</nowiki>''' except in the context of the handbook itself.
:: For the link use '''<nowiki>{{Citelink|</nowiki>'''''shortcut'''''|url='''''page URL'''''|txt='''''alternate text'''''}}'''
::* Current ''shortcuts'' we have defined locally can be found at (or carefully added to) [[template:OurInterwiki|OurInterwiki]].
: Also place a total of exactly one '''<nowiki><noinclude>{{refheading}}</noinclude></nowiki>''' at the bottom of the page, above the category links section.

=== Special Characters ===

; Traversal of menus or windows
: use an arrow (➜)
:: '''Replace this:''' PC-BSD control panel -> System manager -> System packages
:: '''With this:''' ''[[Control Panel]]'' ➜ [[System Manager | ''System Manager'']] ➜ [[System Manager#Install/Uninstall Desktops and System_Components |''System Packages'']]
: This is a unicode [[wikipedia:UTF-8|UTF-8]] character but may appear gibberish in other charsets such as [[wikipedia:ISO 8859-1|IS0 8859-1]].

; Trademarks
:PC-BSD®, AppCafe®, and Warden® are registered trademarks and the ® symbol must appear next to these terms ''' ''except'' ''' when the term is used as a command or in command output.

:''template:RM'' produces {{RM}} via '''<nowiki>{{RM}}</nowiki>''' which is simply an equivalent in place of typing the specific character.
:''template:r'' produces {{r}} via '''<nowiki>{{r}}</nowiki>''' which is a symbol that is 50% of the size it would be in that context and in superscript position.
'''Note:''' Special care needs to be taken because the two are not equivalent. ''NavHome'', ''NavHeader'', and ''SwapTitle'' have ''custompagename'' that may be assigned content that includes '''<nowiki>{{r}}</nowiki>''' but where that is used, ''custompagecategory'' must be defined an equivalent content that includes '''<nowiki>{{RM}}</nowiki>'''. Internal links must include '''<nowiki>{{RM}}</nowiki>''' for the page name portion, but may include '''<nowiki>{{r}}</nowiki>''' for the displayed text.

=== Named visual objects ===

Often the documentation within the handbook will describe a series of steps that includes clicking upon a button. In other places, the handbook may indicate the name of a window or folder or other object on the screen.

; These items could be further emphasized, but their names must be within quotes.
: Example: Click on the "Submit" button along the lower edge of the "Compose response" window.

=== Commandline examples ===

Frequently in the handbook we provide a series of commands or shell output. For these situations, use [[template:txtbox]]. Such content should be formatted for a width of 80 characters (spaces included).

; Replace this: (The wiki method: leftmost character per line is a space.)
Cause a box to enclose the text by starting the sentence with a space, however this has a small problem with keeping the text inside the box. For whatever reason, the text extends out of the dashed lines of this box, to the right.

; With this: '''<nowiki>{{</nowiki>txtbox{{pipe}}box='''''content'''''<nowiki>}}</nowiki>'''
{{txtbox|pre-line|width=50%|box=A much improved variation of that above method also encloses the text within a similar box. Even though the text is a short paragraph of four sentences in length, it does not have the same flaw as before. The text is neatly contained within the dashed lines of the box, and also does not require the initial space character at the start of the first sentence. If that character were included, it would display with two nested boxes. The exact wrap style can be determined when invoked; this box uses 'pre-line' style formatting.
|txt=Text to the right of the box is also possible. This is the [[template:txtbox|''txtbox'' template]] which facilitates a better result without adding a lot of extra typing. Further details including the list of format identifiers are on the template page.
}}

=== Tables ===
Presently various templates are needed to more easily result in a table with the appearance below. However, in the near future there will be an addition of a class="spiffy_table" which will further simplify creation (as shown below), the init template is already modified to include it transparently. Including a caption places it into the tables group list.

{{tbl-init|caption= of comparison}}
!width=32%|inline style via template method
!width=32%|CSS style method (minimal)
!Combination (best)
|-
|This is rather verbose and was more of a brute force method to get the job done. Every line needed a row number which is helpful for readability but also correlated to coloration: odd=white, even=grey. '''-obsolete-''' Tables should be converted from this to the other method(s).
|Clearly this method involves the least typing to produce a good result.
|This mixed method is also possible. Including '''tbl-title''' allows for defining width.
|-
|'''<nowiki>{{</nowiki>tbl-init{{pipe}}''align='''center''{{pipe}}'''caption='''''1a. The caption'''''<nowiki></nowiki>''' '''<nowiki>{{</nowiki>tbl-title{{pipe}}'''''column title'''''<nowiki>}}</nowiki> {{pipe}}-''' '''<nowiki>{{</nowiki>tbl-cell{{pipe}}row='''''1''{{pipe}}''The content'''''<nowiki>}}</nowiki>''' '''{{pipe}}- <nowiki>{{</nowiki>tbl-cell{{pipe}}row='''''2''{{pipe}}''The content'''''<nowiki>}}</nowiki> {{pipe}}<nowiki>}</nowiki>'''
|'''<nowiki>{{</nowiki>tbl-init{{pipe}}caption='''''1a. The caption'''''<nowiki>}}</nowiki>''' '''!'''''column title'' '''{{pipe}}- {{pipe}}'''''The content'' '''{{pipe}}- {{pipe}}'''''The content'' '''{{pipe}}<nowiki>}</nowiki>'''
|'''<nowiki>{{</nowiki>tbl-init{{pipe}}caption='''''1a. The caption'''''<nowiki>}}</nowiki>''' '''<nowiki>{{</nowiki>tbl-title{{pipe}}''width='''32%'''{{pipe}}'''column title'''''<nowiki>}}</nowiki> '''{{pipe}}- {{pipe}}'''''The content'' '''{{pipe}}- {{pipe}}'''''The content'' '''{{pipe}}<nowiki>}</nowiki>'''
|}
: Also place a total of exactly one '''<nowiki><noinclude>{{GroupListHeading|tables}}</noinclude></nowiki>''' at the bottom of the page, below any existing <nowiki><noinclude>{{refheading}}</noinclude></nowiki> and above the category links section. Please note a small adjustment to this rule in the ''noinclude block'' section below.

== Topics structure ==

This will directly relate to headings, but since headings on individual pages are used in a somewhat non-uniform way (due to the appearance of each level of heading), this will apply to a naming convention used with the Table of Contents.

=== Examples in context ===

'''8. Control Panel''' {{highlight|<-- Macro Topic}} (Also wiki page and "level 1")
: 8.1 EasyPBI {{highlight|<-- Topic}} (Also wiki page and "level 1")
(''Below are hidden on the wiki TOC but get shown in the published handbook html - All sub-page level'')
:: 8.1.1 Creating a PBI Module {{highlight|<-- Micro Topic}}
::: 8.1.1.1 Build the Module {{highlight|<-- Nano Topic}}
::: 8.1.1.2 Test and Fine-Tune the Module
:::: 8.1.1.2.1 pbi.conf {{highlight|<-- Pico Topic}}
:::: 8.1.1.2.2 Resources
:::: 8.1.1.2.3 Desktop/Menu Entries
:::: 8.1.1.2.4 External-Links
(''Below is not known to have been used anywhere but if they were to exist this is how they would be used/named)''
::::: 8.1.1.2.4.1 Example of external link {{highlight|<-- Femto Topic}} (''"level 5"'')
:::::: 8.1.1.2.4.1.1 This is the example {{highlight|<-- Atto Topic}} (''"level 6"'')

== [https://en.wikipedia.org/wiki/Help:List Lists] ==

=== Bullets ===

There are two types of bullets in use:
# A bulleted list which begins uppercase. Whether or not it ends in punctuation depends upon the size of the list. For example: 
#* the [[What's New in 9.1]] list uses sentences to describe the features so ends in a period. Use this type of list when the list includes a description large enough to warrant at least one sentence. 
#* the [[Minimum Hardware Requirements]] list uses few words per item. Since the individual items do not warrant a sentence, this type of list does not end in a period. 
# A bulleted list which begins with bolded text (typically the name of a menu item). The bolded section is capitalized to match the name of the menu item and followed by a colon (:). The sentence following the colon begins lowercase and should be worded so that the bolded item is the beginning of the sentence. An example is: 
#: '''Size on Disk:''' indicates the amount of space being used by the jail. 
#:: In this example, the menu item appears as "Size on Disk" (mix of upper/lowercase), "indicates" is lowercase and is worded so that it reads as one sentence (including the name of the menu item). Because it is a sentence, it ends with a period.

; Left from prior guideline
: To ensure that the PDF and EPUB versions format correctly, use a [[wikipedia:Hard return|hard enter]] between the items in a bulleted list.
:: Suggestion used in revision above, is addition of <nowiki> </nowiki>. {{highlight|text=This still needs verification whether a ''hard enter'' or <nowiki> </nowiki> are needed.}}

=== Collation ===

The information should first be placed in logical order, followed by quality or significance, then sorted in alphabetical order, next by chronological order, and finally by ordination. It may be noted that the entire ''collation'' section follows logical order, due to the order described in the first sentence. Examples below are taken from the [[PC-BSD Users Handbook#Table of Contents]]. The [[Errata]] page shows how chronological and ordinal organization may be used together. Using wiki markup in place of text (such as for numbering schemes) might allow for automatic charset substitution in relation to translations.

; Logical
: Putting things in order of precedence; from first task to last task, or first item naturally listed to last item.
:# Introduction 
:# Pre-Installation Tasks 
:# Installing PC-BSD 
:# Post Installation Configuration and Installation Troubleshooting

; Quality or significance
: Organizing according to the importance of the item or its membership in a specific group type.
: This is most visible with groups, such as ''Supported'' and unsupported desktops. In the ''Alphabetical'' example, the first four would seem out of order if the entire set of desktops were included, as below.
:: ''GNOME2''
:: ''KDE4''
:: ''LXDE''
:: ''XFCE4''
:: Awesome
:: EvilWM
:: Fluxbox
:: FVWM
:: i3
:: IceWM
:: Openbox
:: Spectrwm
:: WindowLab
:: Window Maker

; Alphabetical
: Organizing items by name according to the alphabet.
:: GNOME2
:: KDE4
:: LXDE
:: XFCE4

; Chronological
: Placing items in order according to date.
: This is distinction primarily relates to historical and archival purposes.
: Items are placed in reverse order, most recent first and oldest last.

; Ordinal
: The items are listed according to number.
: Examples are Handbook page and chapter numbers, step-by-step instruction where numbered incremental actions are listed.
: Elements are organized from smallest to largest value, or first to last step (similar to ''logical'').
:; Wiki markup
:: '''<nowiki># </nowiki>'''''first text''
:: '''<nowiki># </nowiki>'''''second text''
:;Result
:# first text
:# second text

== Images ==

It is important that the images included in the wiki, especially the handbook portion, be consistent and of a quality that would be acceptable in a professional publication. ('''Note:''' Further refinement of images should be done, including a template for images that may shorten or clarify their inclusion. There are features that exist for images that also modify the page layout which are currently too wikipage specific to describe here in general terms.)

=== Format ===

==== Required ====
* Portable Network Graphic (png).
* Must limit to a '''maximum size of 800x600''', this allows the entire image to remain visible even on a 1024x768 screen size.
* Use background transparency where things such as irregularly shaped icons or rounded window corners are used.
* '''Avoid''' window themes that include translucency or transparency of window content, title, or decorations. These can lead to less clear or unreadable titles, decorations, or content.
* Identify each graphic with a Figure number consisting of the section number of the page followed by a letter, alphabetically with 'a' for the first graphic and 'b' for the second and so forth. Directly after the letter, place a colon and a brief description, preferably more concise than its mention within other text on the page.
*: Example: '''Figure 6.1a: GNOME2 on PC-BSD'''
* Include an image on a page with the following syntax:
*: Example: '''<nowiki>[[</nowiki>File:'''''Important.png'''''{{pipe}}thumb|'''''caption'''''<nowiki>]]</nowiki>'''

==== Single windows ====
* Include the whole window frame and its title bar.
==== Multiple windows ====
These may be within the same image or screenshot if the purpose is to show one task.
* Crop to a box that contains both windows with entire window borders intact.
* Windows may overlap only if necessary details as provided by wiki text are not hidden.
* Must include in the image: options, button labels, window titles, and any other detail that allows the step-by-step to be easily followed without surprises.

==== Screenshots ====

* Must limit to a '''maximum size of 800x600''', this allows the entire image to remain visible even on a 1024x768 screen size.
* If the content is text and has no images, such as console output, then transcribe the text into a txtbox (''Do NOT'' use an image).
* Include a single image on a page with the following syntax:
: Example:
{{txtbox|margin-left=24px|box='''<nowiki>[[</nowiki>File:'''File:''GNOME2-2.png'''''{{pipe}}thumb{{pipe}}393px{{pipe}}''<nowiki>'''</nowiki>'''Figure 6.1a: GNOME2 Desktop on a PC-BSD® System'''<nowiki>'''</nowiki>''<nowiki>]]</nowiki>'''}}
* Place two images side by side on a page with this syntax:
: Example:
{{txtbox|wrap|margin-left=24px|box='''<nowiki><div</nowiki> style="overflow: hidden"><nowiki>[[File:</nowiki>'''''Login2.jpeg'''''{{pipe}}left{{pipe}}thumb{{pipe}}393px{{pipe}}<nowiki>'''</nowiki>'''''Figure 4.8c: Login Menu with User Selected'''''<nowiki>''']][[</nowiki>'''''File:start1.png'''''{{pipe}}right{{pipe}}thumb{{pipe}}393px{{pipe}}'''<nowiki>'''</nowiki>''Figure 4.8d: PC-BSD® Getting Started Screen'''''<nowiki>''']]</div></nowiki>'''}}

==== Scalable Dimensions ====
* An initial image of other 4:3 ratio can be scaled down to 800x600 without serious distortion, but care must be taken that text remains legible.

{|class="spiffy_table"
|+'''Table of Acceptable 4:3 screens'''
!width=50%|Resolution
!Multiplier
|-
|'''800x600'''
|'''1.00'''
|-
|1024x768
|1.28
|-
|1152x864
|1.44
|-
|1200x900
|1.50
|-
|1280x960
|1.60
|-
|1400x1050
|1.75
|-
|1440x1080
|1.80
|-
|1600x1200
|2.00
|-
|1920x1440
|2.40
|}

=== Capture tips ===

* Begin with an ''unmodified/default'' desktop configuration- including only the installed software to be discussed.
* '''''Emphatically'' recommended to use''' ''Virtual Box'' with a desktop of 4:3 ratio, ''Host name:'' Demo System, ''Username:'' PC-BSD_User, which would allow for consistency, universality, and genericness.

* Use a white desktop background to easily capture individual windows or icons.
* Expand the Virtualbox window to be larger than the enclosed desktop (desktop will be surrounded with a white frame).
* The excess white background of cropped images is easily selectable by contiguous shape or color. Next, either invert the selection to cut/copy then paste into a new canvas, or delete the selection so it will be replaced with the alpha transparency.
* When cropping selections, use the zoom tool to enlarge the work area to prevent loss of details or enable addition of transparency for rounded corners.
* Where possible, resize windows so that their entire content can be shown without scrollbars.

== Administrative ==

=== Categories ===
''All pages that use templates: SwapTitle, NavHome, and NavHeader, are automatically added to a category of their pagename (or custompagename where one is defined).''
; Membership
: Each wiki page (ie, [[GNOME2]]) and image page (ie, [[:File:Stub-icon.png]]) should be a member of at least one category.
: The category chosen may be determined by the description given on the individual category pages.

; Format
: Place the category link at the bottom of the page, contained within the between the <nowiki><noinclude></nowiki> block. The first category listed should be the largest group the page belongs to, followed by increasingly specific categories. Category names should be capitalized the same as the pages involved, or each individual word has its first letter capitalized. ''Some templates can auto-categorize pages into their page title category.''

; Description
: The categories themselves should have some sort of explanation to guide their use.

=== Page structure ===

; Header
: Each handbook page contains a [[template:NavHeader|3-icon navigation panel]] across the top,
{{txtbox|box=
'''<nowiki><noinclude><translate>{{NavHeader|back=</nowiki>'''page before current'''<nowiki>|forward=</nowiki>'''page after current'''<nowiki>}}</noinclude></nowiki>'''}}
: while other pages linked from the main page contain [[template:NavHome|a simplified version]].
{{txtbox|box=
'''<nowiki><noinclude><translate>{{NavHome}}</noinclude></nowiki>'''}}

; Stubs
: With relation to new pages that have minimal content, a stub warning is included to enhance visibility ''and aid with community involvement''.

; Comments
: Used in locations of the wiki markup that purposely and specifically do not follow the guideline, or places where reminders or explanations are needed or useful.
:: '''<nowiki><</nowiki>!--''' ''comment text'' '''--<nowiki>></nowiki>'''

; The <nowiki><noinclude></nowiki> block
: Each page should contain a group of category links at the bottom, along with a Refheading and GroupListHeading as applicable (may be enclosed with comment markers if not yet needed). No further text or spaces following, though in some instances a comment is present with nothing following it. The categories included here should become more general as the list continues downward, an example series in order would be: GNOME2, Desktops, Handbook. Although 'GNOME2' would be auto-included by NavHeader. The translate tag allows the page to be marked for translation, while the languages tag determines where links to translations of the current page will be displayed.
{{txtbox|box=
'''<nowiki><noinclude></nowiki>'''
'''<nowiki>{{Refheading}}</nowiki>'''
'''<nowiki>{{GroupListHeading|group=tables}}</nowiki>'''
'''<nowiki>[[</nowiki>category:'''''category 1'''''<nowiki>]]</nowiki>'''
'''<nowiki>[[</nowiki>category:'''''category 2'''''<nowiki>]]</nowiki>'''
'''<nowiki></translate></nowiki>'''
'''<nowiki><languages/></nowiki>'''
'''<nowiki></noinclude></nowiki>'''}}

=== Headings ===

Generally, the headings on a page help to outline and organize the content. It should also be noted that having identical headings or sub-headings within the entire wiki can cause trouble with future editing or navigation, and should be avoided. Include an action word or phrase or otherwise differentiate between the two locations, even if they are discussing the same content, the purpose in each case is not likely identical. (If a certain heading style is preferred though it does not match the guide below, then perhaps adjustments to the wiki site css need to be made.)

{|align="center" style=" border: #aaaaaa dashed 1px; width:97%;"
|

= Page title =

<nowiki>= Page title =</nowiki> 
This level should not be used within a page. If there is need for this level within the content of the page, then it shall be the location of a break into a new page of that title. Here is where an introductory paragraph explaining the topic or feature given by the page name.

== Level 2 ==

<nowiki>== Level 2 ==</nowiki> 
Often this level is skipped in favor of the next - likely indicating css changes should be made.

=== Level 3 ===

<nowiki>=== Level 3 ===</nowiki> 
(Since the level above gets skipped) Here is where the first major step of a process is mentioned, or the main characteristic of the feature is described.

==== Level 4 ====

<nowiki>==== Sub-heading ====</nowiki> 
This level exists but is generally unused currently.

===== Level 5 =====

<nowiki>===== Level 5 =====</nowiki> 
Usually the ''definition'' markup (''';''') is used in place of this header, such as the following:
; Term
: The above ''term'' is defined here.

====== Level 6 ======

<nowiki>====== Level 6 ======</nowiki> 
This level exists but is generally unused currently.
|}

== Resources ==

* [http://www.wikimatrix.org/show/MediaWiki Wikimatrix for mediawiki]
* The preliminary PC-BSD wiki [[stub]] example page.
* [[wikipedia:Manual of Style|Manual of Style]]
* [[wikipedia:Wikipedia:Manual of Style|Wikipedia:Manual of Style]]

{{refheading}}
{{GroupListHeading|group=tables}}
[[Category:PC-BSD Wiki standard]]

PC-BSD Wiki:Style Guidelines

2013-05-09T11:11:31Z

Tigersharke: /* Tables */

{{swapTitle|custompagename=PC-BSD{{r}} Wiki:Style Guidelines|custompagecategory=PC-BSD{{RM}} Wiki:Style Guidelines}}
== Objective ==

The purpose of defining how pages on the wiki should be created, is to help maintain consistency by having a set standard or model to follow, to enable easier translations of the site into other languages, and allow publishing with less modification.

== Text ==

The guideline for actual text content may be under continual refinement with frequent additions until nearly complete. In areas that are incomplete or not yet defined, a reasonable default can be taken from the [[wikipedia:Wikipedia:Manual of Style|Wikipedia:Manual of Style]].

=== Typographic Conventions ===

The PC-BSD Handbook uses the following typographic conventions:

: '''bold text:''' represents a command written at the command line. In usage examples, the font is changed with any command output displayed in unbolded text.
: ''italic text:'' used to represent device names or file name paths.
: ''' ''bold italic text:'' ''' used to emphasize an important point.

==== Emphasis ====

; Notes
: Often we need to specifically call attention to a particular caveat, or other tidbit of information that is not mission critical.
: {{note|This is an example that spans the width of the page.'''<nowiki>{{</nowiki>note{{pipe}}'''''text'''''<nowiki>}}</nowiki>'''}}
: {{note|icon64=Include an icon for larger notes by assigning the text to ''icon64'' when the template is used, such as '''<nowiki>{{</nowiki>note{{pipe}}icon64='''''text'''''<nowiki>}}</nowiki>'''. This icon is the classic ''tie a string around your finger to help remember'', the green triangle is used in hopes of implying that you can continue safely. As you can see with this text box, the message content neatly wraps around the icon. This wrapping will continue neatly around the icon, even when there is sufficient text that the position of the lines in the message fall below the it. The same effect with 64px icons and wrapping text content works for the other two icon message boxes described below.}}

; Warning
: Some instructions have frustrating or annoying consequences and therefore should be emphasized.
: {{warning|The simple quick one-line comment. Use '''<nowiki>{{</nowiki>warning{{pipe}}'''''text'''''<nowiki>}}</nowiki>''' for this.}}
: {{warning|icon64=A verbose and descriptive warning. The concept behind the icon is that something may have been missed, stop and check, investigate. '''<nowiki>{{</nowiki>warning{{pipe}}icon64='''''text'''''<nowiki>}}</nowiki>'''}}

; Dangerous
: Some instructions are critically dangerous and may result in serious harm if a mistake is made.
: {{danger|The simple quick one-line comment. It is invoked by '''<nowiki>{{</nowiki>warning{{pipe}}'''''text'''''<nowiki>}}</nowiki>'''}}
: {{danger|icon64=The text content probably should default to '''bold''' or '''''bold and italic'''''. This icon hopes to clearly indicate possible damage to the PC involved. '''<nowiki>{{</nowiki>danger{{pipe}}icon64='''''text'''''<nowiki>}}</nowiki>'''}}

; Highlighted text
: In certain circumstances, especially to show revisions such as on the [[errata]] page or on [[#Hypertext Links|this page]] to more clearly show what to replace, there is the highlight template: '''<nowiki>{{</nowiki>highlight{{pipe}}text='''''text'''''<nowiki>}}</nowiki>'''
: In the context of this sentence only {{highlight|text=this portion of text}} has the highlight effect.

; Redlighted text
: This should only have limited use for the sole purpose of adding emphasis to {{redlight|critical and dangerous}} information.
: '''<nowiki>{{</nowiki>redlight{{pipe}}text='''''text'''''<nowiki>}}</nowiki>'''

; Orangelighted text
: This should not be used except in the warning text box, but could aid in emphasis to {{orangelight|details that could cause frustration.}}
: '''<nowiki>{{</nowiki>orangelight{{pipe}}text='''''text'''''<nowiki>}}</nowiki>'''

=== Language usage and word choice ===

; Variety
: Use words and phrases with the same meaning; multiple types of sentence structure.

; Contractions: In place of: {{txtbox|override|margin-top=-5px|margin-bottom=0px|box={{nbsp|2}}'''''aren't''''' use '''''are not''''', '''''can't''''' use '''''can not''''', '''''cannot''''' use '''''can not''''',
{{nbsp|2}}'''''doesn't''''' use '''''does not''''', '''''don't''''' use '''do not''', '''''hasn't''''' use '''''has not'''''
{{nbsp|2}}'''''haven't''''' use '''''have not''''', '''''weren't''''' use '''''were not''''', '''''won't''''' use '''''will not''''',
{{nbsp|2}}'''''you'll''''' use '''''you will''''', '''''you'd''''' use '''''you would''''', '''''you're''''' use '''''you are''''',
{{nbsp|2}}'''''you've''''' use '''''you have'''''.}}

; Brand names
: Use '''''web''' search'' instead of '''''Google''' search''.

; Idioms
: Use proper and precise wording.
:: '''''Watch closely''''' should be used instead of '''''keep an eye on'''''.
:: '''''Crashes''''' or '''''fails''''' in place of '''''gets a blue screen of death'''''.
: [[wikipedia:Idiom|Idioms described on wikipedia]].

; Slang
: Use precise rather than colorful or regional terms, however some technical jargon is allowable especially if explained or defined.
:: '''''Open a browser to pcbsd.org''''' would be used instead of '''''surf to pcbsd'''''.
: [[wikipedia:Slang|Slang described on wikipedia]].
: [[wikipedia:Jargon|Jargon described on wikipedia]].

; Dates
: Given that some date formats can be problematic: (07-03-2012) Does the author mean July 3rd 2012, or March 7th 2012. The wiki offers a per-user preference for date format. This also formalizes instances of dates which may also aid translations.
:: '''<nowiki>{{</nowiki>#dateformat:'''''01 May 2012'''''}}''' should be used resulting in {{#dateformat:01 May 2012}} which conforms to each user's preferences.

; Uncapped proper names
: Some software is officially named in lowercase, yet sentences should ''usually'' begin with a capital letter. The solution is to avoid using those special proper names as the word that begins a sentence.

=== Hypertext Links ===

Within the text, it is helpful to add a link to topics, pages, and sites to further explain and allow for additional research.
; Name
: Use a descriptive word or phrase. It can be the general location (page/site) of the link, as long as the link itself is to the specific section (when ever possible). Try not to be too general/generic. Highlight and italic are used for clarity in the examples below.
:: '''Replace this:''' You can find more information about hardware compatibility {{highlight|{{citelink|url=http://forums.freebsd.org/forumdisplay.php?f=32|txt=''here.''}}}}
:: '''With this:''' You can find more information about hardware compatibility {{highlight|on the}} {{highlight|{{citelink|url=http://forums.freebsd.org/forumdisplay.php?f=32|''FreeBSD hardware forum''}}}}.

:: '''Replace this:''' {{highlight|{{citelink|url=http://forums.freebsd.org/forumdisplay.php?f=32|txt=''This forum post''}}}} explains how to properly plug the outlet tube of an inlet drain line.
:: '''With this:''' {{highlight|This}} {{highlight|{{citelink|url=http://forums.freebsd.org/forumdisplay.php?f=32|''PlumberCraft forum post''}}}} explains how to properly plug the outlet tube of an inlet drain line.

; URL
: Use an ending slash with any url that leads to a directory or non-file (such as any site name). It is prudent to verify that an adjusted link is valid since some sites do not use extensions for file names. This convention will aid with consistency and help to eliminate technically different but effectively identical URLs.
:: '''This is a valid url:''' <nowiki>http://</nowiki>forums.freebsd.org
:: '''Url with proper syntax on this wiki:''' <nowiki>http://</nowiki>forums.freebsd.org/
:: '''Example of a url that ends with a file name:''' <nowiki>http://</nowiki>www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sound-setup.html

; Internal
: The URL is within the PC-BSD wiki.
:: Use '''<nowiki>[[</nowiki>'''''page name'''''<nowiki>]]</nowiki>''' or '''<nowiki>[[</nowiki>'''''page name'''''|'''''alternate text'''''<nowiki>]]</nowiki>'''

; External
: The URL is for a location outside of wiki.pcbsd.org. Most places where an external link may be used, there is alternate text shown, which means for a printed handbook, there must be a footnote to provide the actual URL. Those rare places that do not provide alternate text but show the actual URL, do not need the ''[[template:citelink|citelink]]''. If the link text is to be '''bold''' or ''italic'' or '''''both''''' then the modifier characters must be directly around the ''alternate text'' and not around the entire ''citelink'' phrase below.
:: For the link use '''<nowiki>{{Citelink|url=</nowiki>'''''complete URL'''''|txt='''''alternate text'''''}}'''
: Also place a total of exactly one '''<nowiki><noinclude>{{refheading}}</noinclude></nowiki>''' at the bottom of the page, above the category links section.

; Special External
: The URL is for a site not part of the PC-BSD wiki, but has a defined [[mediawikiwiki:Manual:Interwiki|interwiki]] shortcut such as for wikipedia.
: Valid markup is '''<nowiki>[[</nowiki>'''wikipedia:''page name'''''<nowiki>]]</nowiki>''' or '''<nowiki>[[</nowiki>'''wikipedia:''page name'''''|'''''alternate text'''''<nowiki>]]</nowiki>''' except in the context of the handbook itself.
:: For the link use '''<nowiki>{{Citelink|</nowiki>'''''shortcut'''''|url='''''page URL'''''|txt='''''alternate text'''''}}'''
::* Current ''shortcuts'' we have defined locally can be found at (or carefully added to) [[template:OurInterwiki|OurInterwiki]].
: Also place a total of exactly one '''<nowiki><noinclude>{{refheading}}</noinclude></nowiki>''' at the bottom of the page, above the category links section.

=== Special Characters ===

; Traversal of menus or windows
: use an arrow (➜)
:: '''Replace this:''' PC-BSD control panel -> System manager -> System packages
:: '''With this:''' ''[[Control Panel]]'' ➜ [[System Manager | ''System Manager'']] ➜ [[System Manager#Install/Uninstall Desktops and System_Components |''System Packages'']]
: This is a unicode [[wikipedia:UTF-8|UTF-8]] character but may appear gibberish in other charsets such as [[wikipedia:ISO 8859-1|IS0 8859-1]].

; Trademarks
:PC-BSD®, AppCafe®, and Warden® are registered trademarks and the ® symbol must appear next to these terms ''' ''except'' ''' when the term is used as a command or in command output.

:''template:RM'' produces {{RM}} via '''<nowiki>{{RM}}</nowiki>''' which is simply an equivalent in place of typing the specific character.
:''template:r'' produces {{r}} via '''<nowiki>{{r}}</nowiki>''' which is a symbol that is 50% of the size it would be in that context and in superscript position.
'''Note:''' Special care needs to be taken because the two are not equivalent. ''NavHome'', ''NavHeader'', and ''SwapTitle'' have ''custompagename'' that may be assigned content that includes '''<nowiki>{{r}}</nowiki>''' but where that is used, ''custompagecategory'' must be defined an equivalent content that includes '''<nowiki>{{RM}}</nowiki>'''. Internal links must include '''<nowiki>{{RM}}</nowiki>''' for the page name portion, but may include '''<nowiki>{{r}}</nowiki>''' for the displayed text.

=== Named visual objects ===

Often the documentation within the handbook will describe a series of steps that includes clicking upon a button. In other places, the handbook may indicate the name of a window or folder or other object on the screen.

; These items could be further emphasized, but their names must be within quotes.
: Example: Click on the "Submit" button along the lower edge of the "Compose response" window.

=== Commandline examples ===

Frequently in the handbook we provide a series of commands or shell output. For these situations, use [[template:txtbox]]. Such content should be formatted for a width of 80 characters (spaces included).

; Replace this: (The wiki method: leftmost character per line is a space.)
Cause a box to enclose the text by starting the sentence with a space, however this has a small problem with keeping the text inside the box. For whatever reason, the text extends out of the dashed lines of this box, to the right.

; With this: '''<nowiki>{{</nowiki>txtbox{{pipe}}box='''''content'''''<nowiki>}}</nowiki>'''
{{txtbox|pre-line|width=50%|box=A much improved variation of that above method also encloses the text within a similar box. Even though the text is a short paragraph of four sentences in length, it does not have the same flaw as before. The text is neatly contained within the dashed lines of the box, and also does not require the initial space character at the start of the first sentence. If that character were included, it would display with two nested boxes. The exact wrap style can be determined when invoked; this box uses 'pre-line' style formatting.
|txt=Text to the right of the box is also possible. This is the [[template:txtbox|''txtbox'' template]] which facilitates a better result without adding a lot of extra typing. Further details including the list of format identifiers are on the template page.
}}

=== Tables ===
Presently various templates are needed to more easily result in a table with the appearance below. However, in the near future there will be an addition of a class="spiffy_table" which will further simplify creation (as shown below), the init template is already modified to include it transparently. Including a caption places it into the tables group list.

{{tbl-init|caption= of comparison}}
!width=32%|inline style via template method
!width=32%|CSS style method (minimal)
!Combination (best)
|-
|This is rather verbose and was more of a brute force method to get the job done. Every line needed a row number which is helpful for readability but also correlated to coloration: odd=white, even=grey. '''-obsolete-''' Tables should be converted from this to the other method(s).
|Clearly this method involves the least typing to produce a good result.
|This mixed method is also possible. Including '''tbl-title''' allows for defining width.
|-
|'''<nowiki>{{</nowiki>tbl-init{{pipe}}''align='''center''{{pipe}}'''caption='''''1a. The caption'''''<nowiki></nowiki>''' '''<nowiki>{{</nowiki>tbl-title{{pipe}}'''''column title'''''<nowiki>}}</nowiki> {{pipe}}-''' '''<nowiki>{{</nowiki>tbl-cell{{pipe}}row='''''1''{{pipe}}''The content'''''<nowiki>}}</nowiki>''' '''{{pipe}}- <nowiki>{{</nowiki>tbl-cell{{pipe}}row='''''2''{{pipe}}''The content'''''<nowiki>}}</nowiki> {{pipe}}<nowiki>}</nowiki>'''
|'''<nowiki>{{</nowiki>tbl-init{{pipe}}caption='''''1a. The caption'''''<nowiki>}}</nowiki>''' '''!'''''column title'' '''{{pipe}}- {{pipe}}'''''The content'' '''{{pipe}}- {{pipe}}'''''The content'' '''{{pipe}}<nowiki>}</nowiki>'''
|'''<nowiki>{{</nowiki>tbl-init{{pipe}}caption='''''1a. The caption'''''<nowiki>}}</nowiki>''' '''<nowiki>{{</nowiki>tbl-title{{pipe}}''width='''''32%'''{{pipe}}'''''column title'''''<nowiki>}}</nowiki> '''{{pipe}}- {{pipe}}'''''The content'' '''{{pipe}}- {{pipe}}'''''The content'' '''{{pipe}}<nowiki>}</nowiki>'''
|}
: Also place a total of exactly one '''<nowiki><noinclude>{{GroupListHeading|tables}}</noinclude></nowiki>''' at the bottom of the page, below any existing <nowiki><noinclude>{{refheading}}</noinclude></nowiki> and above the category links section. Please note a small adjustment to this rule in the ''noinclude block'' section below.

== Topics structure ==

This will directly relate to headings, but since headings on individual pages are used in a somewhat non-uniform way (due to the appearance of each level of heading), this will apply to a naming convention used with the Table of Contents.

=== Examples in context ===

'''8. Control Panel''' {{highlight|<-- Macro Topic}} (Also wiki page and "level 1")
: 8.1 EasyPBI {{highlight|<-- Topic}} (Also wiki page and "level 1")
(''Below are hidden on the wiki TOC but get shown in the published handbook html - All sub-page level'')
:: 8.1.1 Creating a PBI Module {{highlight|<-- Micro Topic}}
::: 8.1.1.1 Build the Module {{highlight|<-- Nano Topic}}
::: 8.1.1.2 Test and Fine-Tune the Module
:::: 8.1.1.2.1 pbi.conf {{highlight|<-- Pico Topic}}
:::: 8.1.1.2.2 Resources
:::: 8.1.1.2.3 Desktop/Menu Entries
:::: 8.1.1.2.4 External-Links
(''Below is not known to have been used anywhere but if they were to exist this is how they would be used/named)''
::::: 8.1.1.2.4.1 Example of external link {{highlight|<-- Femto Topic}} (''"level 5"'')
:::::: 8.1.1.2.4.1.1 This is the example {{highlight|<-- Atto Topic}} (''"level 6"'')

== [https://en.wikipedia.org/wiki/Help:List Lists] ==

=== Bullets ===

There are two types of bullets in use:
# A bulleted list which begins uppercase. Whether or not it ends in punctuation depends upon the size of the list. For example: 
#* the [[What's New in 9.1]] list uses sentences to describe the features so ends in a period. Use this type of list when the list includes a description large enough to warrant at least one sentence. 
#* the [[Minimum Hardware Requirements]] list uses few words per item. Since the individual items do not warrant a sentence, this type of list does not end in a period. 
# A bulleted list which begins with bolded text (typically the name of a menu item). The bolded section is capitalized to match the name of the menu item and followed by a colon (:). The sentence following the colon begins lowercase and should be worded so that the bolded item is the beginning of the sentence. An example is: 
#: '''Size on Disk:''' indicates the amount of space being used by the jail. 
#:: In this example, the menu item appears as "Size on Disk" (mix of upper/lowercase), "indicates" is lowercase and is worded so that it reads as one sentence (including the name of the menu item). Because it is a sentence, it ends with a period.

; Left from prior guideline
: To ensure that the PDF and EPUB versions format correctly, use a [[wikipedia:Hard return|hard enter]] between the items in a bulleted list.
:: Suggestion used in revision above, is addition of <nowiki> </nowiki>. {{highlight|text=This still needs verification whether a ''hard enter'' or <nowiki> </nowiki> are needed.}}

=== Collation ===

The information should first be placed in logical order, followed by quality or significance, then sorted in alphabetical order, next by chronological order, and finally by ordination. It may be noted that the entire ''collation'' section follows logical order, due to the order described in the first sentence. Examples below are taken from the [[PC-BSD Users Handbook#Table of Contents]]. The [[Errata]] page shows how chronological and ordinal organization may be used together. Using wiki markup in place of text (such as for numbering schemes) might allow for automatic charset substitution in relation to translations.

; Logical
: Putting things in order of precedence; from first task to last task, or first item naturally listed to last item.
:# Introduction 
:# Pre-Installation Tasks 
:# Installing PC-BSD 
:# Post Installation Configuration and Installation Troubleshooting

; Quality or significance
: Organizing according to the importance of the item or its membership in a specific group type.
: This is most visible with groups, such as ''Supported'' and unsupported desktops. In the ''Alphabetical'' example, the first four would seem out of order if the entire set of desktops were included, as below.
:: ''GNOME2''
:: ''KDE4''
:: ''LXDE''
:: ''XFCE4''
:: Awesome
:: EvilWM
:: Fluxbox
:: FVWM
:: i3
:: IceWM
:: Openbox
:: Spectrwm
:: WindowLab
:: Window Maker

; Alphabetical
: Organizing items by name according to the alphabet.
:: GNOME2
:: KDE4
:: LXDE
:: XFCE4

; Chronological
: Placing items in order according to date.
: This is distinction primarily relates to historical and archival purposes.
: Items are placed in reverse order, most recent first and oldest last.

; Ordinal
: The items are listed according to number.
: Examples are Handbook page and chapter numbers, step-by-step instruction where numbered incremental actions are listed.
: Elements are organized from smallest to largest value, or first to last step (similar to ''logical'').
:; Wiki markup
:: '''<nowiki># </nowiki>'''''first text''
:: '''<nowiki># </nowiki>'''''second text''
:;Result
:# first text
:# second text

== Images ==

It is important that the images included in the wiki, especially the handbook portion, be consistent and of a quality that would be acceptable in a professional publication. ('''Note:''' Further refinement of images should be done, including a template for images that may shorten or clarify their inclusion. There are features that exist for images that also modify the page layout which are currently too wikipage specific to describe here in general terms.)

=== Format ===

==== Required ====
* Portable Network Graphic (png).
* Must limit to a '''maximum size of 800x600''', this allows the entire image to remain visible even on a 1024x768 screen size.
* Use background transparency where things such as irregularly shaped icons or rounded window corners are used.
* '''Avoid''' window themes that include translucency or transparency of window content, title, or decorations. These can lead to less clear or unreadable titles, decorations, or content.
* Identify each graphic with a Figure number consisting of the section number of the page followed by a letter, alphabetically with 'a' for the first graphic and 'b' for the second and so forth. Directly after the letter, place a colon and a brief description, preferably more concise than its mention within other text on the page.
*: Example: '''Figure 6.1a: GNOME2 on PC-BSD'''
* Include an image on a page with the following syntax:
*: Example: '''<nowiki>[[</nowiki>File:'''''Important.png'''''{{pipe}}thumb|'''''caption'''''<nowiki>]]</nowiki>'''

==== Single windows ====
* Include the whole window frame and its title bar.
==== Multiple windows ====
These may be within the same image or screenshot if the purpose is to show one task.
* Crop to a box that contains both windows with entire window borders intact.
* Windows may overlap only if necessary details as provided by wiki text are not hidden.
* Must include in the image: options, button labels, window titles, and any other detail that allows the step-by-step to be easily followed without surprises.

==== Screenshots ====

* Must limit to a '''maximum size of 800x600''', this allows the entire image to remain visible even on a 1024x768 screen size.
* If the content is text and has no images, such as console output, then transcribe the text into a txtbox (''Do NOT'' use an image).
* Include a single image on a page with the following syntax:
: Example:
{{txtbox|margin-left=24px|box='''<nowiki>[[</nowiki>File:'''File:''GNOME2-2.png'''''{{pipe}}thumb{{pipe}}393px{{pipe}}''<nowiki>'''</nowiki>'''Figure 6.1a: GNOME2 Desktop on a PC-BSD® System'''<nowiki>'''</nowiki>''<nowiki>]]</nowiki>'''}}
* Place two images side by side on a page with this syntax:
: Example:
{{txtbox|wrap|margin-left=24px|box='''<nowiki><div</nowiki> style="overflow: hidden"><nowiki>[[File:</nowiki>'''''Login2.jpeg'''''{{pipe}}left{{pipe}}thumb{{pipe}}393px{{pipe}}<nowiki>'''</nowiki>'''''Figure 4.8c: Login Menu with User Selected'''''<nowiki>''']][[</nowiki>'''''File:start1.png'''''{{pipe}}right{{pipe}}thumb{{pipe}}393px{{pipe}}'''<nowiki>'''</nowiki>''Figure 4.8d: PC-BSD® Getting Started Screen'''''<nowiki>''']]</div></nowiki>'''}}

==== Scalable Dimensions ====
* An initial image of other 4:3 ratio can be scaled down to 800x600 without serious distortion, but care must be taken that text remains legible.

{|class="spiffy_table"
|+'''Table of Acceptable 4:3 screens'''
!width=50%|Resolution
!Multiplier
|-
|'''800x600'''
|'''1.00'''
|-
|1024x768
|1.28
|-
|1152x864
|1.44
|-
|1200x900
|1.50
|-
|1280x960
|1.60
|-
|1400x1050
|1.75
|-
|1440x1080
|1.80
|-
|1600x1200
|2.00
|-
|1920x1440
|2.40
|}

=== Capture tips ===

* Begin with an ''unmodified/default'' desktop configuration- including only the installed software to be discussed.
* '''''Emphatically'' recommended to use''' ''Virtual Box'' with a desktop of 4:3 ratio, ''Host name:'' Demo System, ''Username:'' PC-BSD_User, which would allow for consistency, universality, and genericness.

* Use a white desktop background to easily capture individual windows or icons.
* Expand the Virtualbox window to be larger than the enclosed desktop (desktop will be surrounded with a white frame).
* The excess white background of cropped images is easily selectable by contiguous shape or color. Next, either invert the selection to cut/copy then paste into a new canvas, or delete the selection so it will be replaced with the alpha transparency.
* When cropping selections, use the zoom tool to enlarge the work area to prevent loss of details or enable addition of transparency for rounded corners.
* Where possible, resize windows so that their entire content can be shown without scrollbars.

== Administrative ==

=== Categories ===
''All pages that use templates: SwapTitle, NavHome, and NavHeader, are automatically added to a category of their pagename (or custompagename where one is defined).''
; Membership
: Each wiki page (ie, [[GNOME2]]) and image page (ie, [[:File:Stub-icon.png]]) should be a member of at least one category.
: The category chosen may be determined by the description given on the individual category pages.

; Format
: Place the category link at the bottom of the page, contained within the between the <nowiki><noinclude></nowiki> block. The first category listed should be the largest group the page belongs to, followed by increasingly specific categories. Category names should be capitalized the same as the pages involved, or each individual word has its first letter capitalized. ''Some templates can auto-categorize pages into their page title category.''

; Description
: The categories themselves should have some sort of explanation to guide their use.

=== Page structure ===

; Header
: Each handbook page contains a [[template:NavHeader|3-icon navigation panel]] across the top,
{{txtbox|box=
'''<nowiki><noinclude><translate>{{NavHeader|back=</nowiki>'''page before current'''<nowiki>|forward=</nowiki>'''page after current'''<nowiki>}}</noinclude></nowiki>'''}}
: while other pages linked from the main page contain [[template:NavHome|a simplified version]].
{{txtbox|box=
'''<nowiki><noinclude><translate>{{NavHome}}</noinclude></nowiki>'''}}

; Stubs
: With relation to new pages that have minimal content, a stub warning is included to enhance visibility ''and aid with community involvement''.

; Comments
: Used in locations of the wiki markup that purposely and specifically do not follow the guideline, or places where reminders or explanations are needed or useful.
:: '''<nowiki><</nowiki>!--''' ''comment text'' '''--<nowiki>></nowiki>'''

; The <nowiki><noinclude></nowiki> block
: Each page should contain a group of category links at the bottom, along with a Refheading and GroupListHeading as applicable (may be enclosed with comment markers if not yet needed). No further text or spaces following, though in some instances a comment is present with nothing following it. The categories included here should become more general as the list continues downward, an example series in order would be: GNOME2, Desktops, Handbook. Although 'GNOME2' would be auto-included by NavHeader. The translate tag allows the page to be marked for translation, while the languages tag determines where links to translations of the current page will be displayed.
{{txtbox|box=
'''<nowiki><noinclude></nowiki>'''
'''<nowiki>{{Refheading}}</nowiki>'''
'''<nowiki>{{GroupListHeading|group=tables}}</nowiki>'''
'''<nowiki>[[</nowiki>category:'''''category 1'''''<nowiki>]]</nowiki>'''
'''<nowiki>[[</nowiki>category:'''''category 2'''''<nowiki>]]</nowiki>'''
'''<nowiki></translate></nowiki>'''
'''<nowiki><languages/></nowiki>'''
'''<nowiki></noinclude></nowiki>'''}}

=== Headings ===

Generally, the headings on a page help to outline and organize the content. It should also be noted that having identical headings or sub-headings within the entire wiki can cause trouble with future editing or navigation, and should be avoided. Include an action word or phrase or otherwise differentiate between the two locations, even if they are discussing the same content, the purpose in each case is not likely identical. (If a certain heading style is preferred though it does not match the guide below, then perhaps adjustments to the wiki site css need to be made.)

{|align="center" style=" border: #aaaaaa dashed 1px; width:97%;"
|

= Page title =

<nowiki>= Page title =</nowiki> 
This level should not be used within a page. If there is need for this level within the content of the page, then it shall be the location of a break into a new page of that title. Here is where an introductory paragraph explaining the topic or feature given by the page name.

== Level 2 ==

<nowiki>== Level 2 ==</nowiki> 
Often this level is skipped in favor of the next - likely indicating css changes should be made.

=== Level 3 ===

<nowiki>=== Level 3 ===</nowiki> 
(Since the level above gets skipped) Here is where the first major step of a process is mentioned, or the main characteristic of the feature is described.

==== Level 4 ====

<nowiki>==== Sub-heading ====</nowiki> 
This level exists but is generally unused currently.

===== Level 5 =====

<nowiki>===== Level 5 =====</nowiki> 
Usually the ''definition'' markup (''';''') is used in place of this header, such as the following:
; Term
: The above ''term'' is defined here.

====== Level 6 ======

<nowiki>====== Level 6 ======</nowiki> 
This level exists but is generally unused currently.
|}

== Resources ==

* [http://www.wikimatrix.org/show/MediaWiki Wikimatrix for mediawiki]
* The preliminary PC-BSD wiki [[stub]] example page.
* [[wikipedia:Manual of Style|Manual of Style]]
* [[wikipedia:Wikipedia:Manual of Style|Wikipedia:Manual of Style]]

{{refheading}}
{{GroupListHeading|group=tables}}
[[Category:PC-BSD Wiki standard]]

Translations:Preface/1/qqq

2013-05-01T04:30:56Z

Tigersharke:

Shouldn't all links within the language "/en" here, also remain linked to the rest of the translated pages? I wish there were a variable I could use instead, to remove this need- as yet not discovered or may not exist.

Preface/en

2013-04-30T23:55:09Z

Tigersharke:

<noinclude>
{{NavHeaderFirst|forward=Introduction/en}}</noinclude>

; PC-BSD® Users Handbook

written by users of the [http://www.pcbsd.org PC-BSD® operating system].

Version 9.1

Published {{#dateformat:30 Nov 2012}}

Copyright © 2005-2013, The PC-BSD® Project.

Welcome to PC-BSD®! This Handbook covers the installation and use of PC-BSD® 9.1. This Handbook is a work in progress and relies on the contributions of many individuals. If you are interested in assisting with the Handbook, visit {{http}}wiki.pcbsd.org and create a login account for yourself. If you use IRC Freenode, you are welcome to join the #pcbsd channel where you will find other PC-BSD® users.

Previous versions of the Handbook in various formats and languages are available from [ftp://ftp.pcbsd.org/pub/handbook/ ftp://ftp.pcbsd.org/pub/handbook/]. Errata may be found at [[Errata|{{http}}wiki.pcbsd.org/index.php/Errata]]. 
The PC-BSD® Users Handbook is freely available for sharing and redistribution under the terms of the {{citelink|url=https://creativecommons.org/licenses/by/3.0/|txt=Creative Commons Attribution License}}. This means that you have permission to copy, distribute, translate, and adapt the work as long as you attribute the PC-BSD® Project as the original source of the Handbook.

PC-BSD® and the PC-BSD® logo are registered trademarks of {{citelink|url=https://www.ixsystems.com/|txt=iXsystems}}. If you wish to use the PC-BSD® logo in your own works, ask for permission first from ''marketing'' at ''ixsystems'' dot ''com''.

; Trademarks

AMD is a trademark of Advanced Micro Devices, Inc.

Apache is a trademark of The Apache Software Foundation.

AppCafe® is a registered trademark of iXsystems.

Asus® and Eee PC® are registered trademarks of ASUSTeK® Computer Inc.

Facebook® is a registered trademark of Facebook Inc.

Flash® is a registered trademark of Adobe Systems Incorporated in the United States and/or other countries.

FreeBSD® is a registered trademark of the {{citelink|url=http://www.freebsdfoundation.org|txt=FreeBSD Foundation}}.

FreeNAS® is a registered trademark of iXsystems.

IBM® is a registered trademark of International Business Machines Corporation.

Intel, the Intel logo, Pentium Inside, and Pentium are trademarks of Intel Corporation in the U.S. and/or other countries.

Java™ is a trademark of Oracle America and/or its affiliates in the United States and other countries.

Lenovo® is a registered trademark of Lenovo.

LinkedIn® is a registered trademark of LinkedIn Corporation.

Linux® is a registered trademark of Linus Torvalds.

Mac and Mac OS are trademarks of Apple Inc., registered in the U.S. and other countries.

MacBook® is a registered trademark of Apple Inc.

MySQL is a trademark of Oracle.

NVIDIA® is a trademark and/or registered trademark of NVIDIA Corporation in the U.S. and other countries.

PostgreSQL® is a registered trademark of the PostgreSQL Global Development Group.

ThinkPad® is a registered trademark of Lenovo.

TrueOS® is a registered trademark of iXsystems.

Twitter is a trademark of Twitter, Inc. in the United States and other countries.

UNIX® is a registered trademark of The Open Group.

VirtualBox® is a registered trademark of Oracle.

VMWare® is a registered trademark of VMWare, Inc.

Warden® is a registered trademark of iXsystems.

Windows® is a registered trademark of Microsoft Corporation in the United States and other countries.

; Typographic Conventions

The PC-BSD® 9.1 Handbook uses the following typographic conventions:

'''bold text:''' represents a command written at the command line. In usage examples, the font is changed to Courier 10 with any command output displayed in unbolded text.

''italic text:'' used to represent device names or file name paths.

''' ''bold italic text:'' ''' used to emphasize an important point.
{|
|-
|[[File:note-msg-icon3.png|frame|64px|'''NOTE:''']]
|[[File:warning-msg-icon.png|frame|64px|'''WARNING''']]
|[[File:danger-msg-icon.png|frame|64px|'''DANGER!''']]
|}

<noinclude>
{{refheading}}
[[category:handbook]]
[[category:preface]]
<languages />
</noinclude>

Translations:Preface/1/en

2013-04-30T23:55:08Z

Tigersharke:

{{NavHeaderFirst|forward=Introduction/en}}</noinclude>

Translations:Preface/1/qqq

2013-04-30T23:54:31Z

Tigersharke: Created page with "Shouldn't all links within the language "/en" here, also remain linking to the rest of the translated pages? I wish there were a variable I could use instead, to remove this n..."

Shouldn't all links within the language "/en" here, also remain linking to the rest of the translated pages? I wish there were a variable I could use instead, to remove this need- as yet not discovered or may not exist.

Files and File Sharing

2013-04-30T10:29:35Z

Tigersharke:

<noinclude><translate>


{{NavHeader|back=Multimedia|forward=MythTV}}</noinclude>


This section describes the various file managers that are available for managing the files on your PC-BSD system. It then shows how you can configure your PC-BSD system to share files with other systems in your network using Samba.

== File Managers and File Structure == 


Depending upon which window managers you have installed, different graphical file manager utilities may already be installed for you. You do not need to be logged into a specific window manager to use an installed file manager. For example, if KDE is installed, you can run its file manager from any window manager by typing '''dolphin'''. KDE, GNOME, LXDE, and XFCE install their own file managers while most of the unsupported desktops assume that you will install your favorite file manager. Table 9.3a summarizes the available file managers and indicates which desktop they are installed with. Some file managers can be installed independent of a desktop using [[Using AppCafe® | AppCafe®]] to install the PBI. Once a file manager is installed, type its name if you wish to run it from another desktop.


{{Tbl-init|caption=9.3a: Available File Managers}}
!width=37%|File Manager
!Desktop/PBI
!Screenshots
!Notes
|-
|dolphin
|[[KDE4|KDE]]
|{{citelink|url=http://dolphin.kde.org/features.html|txt=http://dolphin.kde.org/features.html}}
|
|-
|emelfm2
|PBI
|{{citelink|url=http://emelfm2.net/wiki/ScreenShots|txt=http://emelfm2.net/wiki/ScreenShots}}
|
|-
|/usr/local/GNUstep/Apps/FSViewer.app/FSViewer
|[[Window Maker]]
|{{citelink|url=http://www.bayernline.de/~gscholz/linux/fsviewer/|txt=http://www.bayernline.de/~gscholz/linux/fsviewer/}}
|
|-
|krusader
|PBI
|{{citelink|url=http://www.krusader.org/screenshots.php|txt=http://www.krusader.org/screenshots.php}}
|
|-
|mucommander
|PBI
|{{citelink|url=http://www.mucommander.com/screenshots.php|txt=http://www.mucommander.com/screenshots.php}}
|
|-
|nautilus
|[[GNOME2|GNOME]]
|{{citelink|url=http://live.gnome.org/Nautilus/Screenshots|txt=http://live.gnome.org/Nautilus/Screenshots}}
|
|-
|pcmanfm
|[[LXDE]] or PBI
|{{citelink|url=http://lxde.org/easy_fast_file_management_pcmanfm|txt=http://lxde.org/easy_fast_file_management_pcmanfm}}
|
|-
|thunar
|[[XFCE4|XFCE]] or PBI
|{{citelink|url=http://www.xfce.org/projects/thunar|txt=http://www.xfce.org/projects/thunar}}
|unable to automount internal NTFS disks (try pcmanfm or emelfm2 instead)
|-
|xfe
|PBI
|{{citelink|url=http://roland65.free.fr/xfe/index.php?page=screenshots|txt=http://roland65.free.fr/xfe/index.php?page=screenshots}}
|
|-
|}


When working with files on your PC-BSD system, save your own files to your home directory. Since most of the files outside of your home directory are used by the operating system and applications, you should not delete or modify any files outside of your home directory, unless you know what you are doing.


Table 9.3b summarizes the directory structure found on a PC-BSD system. '''man hier''' explains this directory structure in more detail.


{{Tbl-init|caption=9.3b: PC-BSD Directory Structure}}
!width=18%|Directory
!Contents
|-
| /
|pronounced as "root" and represents the beginning of the directory structure
|-
| /bin/
| applications (binaries) that were installed with the operating system
|-
| /boot/
| stores the startup code, including kernel modules (such as hardware drivers)
|-
| /compat/linux/
| Linux software compatibility files
|-
| /dev/
| files which are used by the operating system to access devices
|-
| /etc/
| operating system configuration files
|-
| /etc/X11/
| the ''xorg.conf'' configuration file
|-
| /etc/rc.d/
| operating system startup scripts
|-
| /home/
| subdirectories for each user account; each user should store their files in their own home directory
|-
| /lib/
| operating system libraries needed for applications
|-
| /libexec/
| operating system libraries and binaries
|-
| /media/
| mount point for storage media such as DVDs and USB drives
|-
| /mnt/
| another mount point
|-
| /proc/
| the proc filesystem required by some Linux applications
|-
| /rescue/
|necessary programs for emergency recovery
|-
| /root/
| administrative account's home directory
|-
| /sbin/
| operating system applications; typically only the superuser can run these applications
|-
| /tmp/
| temporary file storage; files stored here may disappear when the system reboots
|-
| /usr/bin/
| contains most of the command line programs available to users
|-
| /usr/local/
| contains the binaries, libraries, startup scripts, documentation, and configuration files used by applications installed from ports or packages
|-
| /usr/pbi/
| contains the binaries, libraries, startup scripts, documentation, and configuration files used by installed PBIs
|-
| /usr/local/share/fonts/
| system wide fonts for graphical applications
|-
| /usr/local/share/icons/
| system wide icons
|-
| /usr/ports/
| location of system ports tree (if installed)
|-
| /usr/share/
| system documentation and man pages
|-
| /usr/sbin/
| command line programs for the superuser
|-
| /usr/src/
| location of system source code (if installed)
|-
| /var/
| files that change (vary), such as log files and print jobs
|-
|}

== Samba == 


{{citelink|url=http://samba.org/|txt=Samba}} allows any operating system to share volumes using Microsoft's CIFS protocol. There are two components to Samba:


* '''client libraries:''' this allows an operating system to access ''' ''existing'' ''' CIFS shares. The client is built into the Windows and Mac OS X operating systems and is installed for you during the PC-BSD installation. Most Linux distros also install the Samba client; if your Linux distro does not, search its software repository.


* '''server:''' this allows a computer to act like a Windows server in that it can ''' ''create'' ''' shares and printers that are available to any CIFS client on the same network.


This section will demonstrate how to access shares using the Samba client as well as how to configure your PC-BSD system as a Samba server.

=== Using the Samba Client === 


Since the Samba client libraries are pre-installed for you, you simply have to decide which utility you prefer to access existing Windows shares on your network. If a desktop is installed, you do not have to be logged into that desktop in order to use that utility.


Table 9.3c summarizes the available utilities (type a utility's name to launch it in any desktop), which desktop it installs with and whether or not a separate PBI is available, and a short description of how to access the available shares using that utility.


{{Tbl-init|caption=9.3c: Utilities that Support Windows Shares}}
!'''Utility'''
!'''Desktop/PBI'''
!'''How to Access Existing Shares'''
|-
|dolphin
|[[KDE4|KDE]]
|in the left frame, click on ''Network'' ➜ ''Samba Shares'', then the Workgroup name; if the network requires a username and password to browse for shares, set this in ''[[Control Panel]]'' ➜ ''System Settings'' ➜ ''Sharing'' while in [[KDE4|KDE]] or type '''systemsettings''' ➜ ''Sharing'' while in another desktop
|-
|konqueror
|[[KDE4|KDE]]
|in the location bar, type ''smb:/''
|-
|krusader
|PBI
|add Local Network to toolbar by going to ''Settings'' ➜ ''Configure Toolbars''; once in toolbar click ''Local Network'' ➜ ''Samba Shares''
|-
|mucommander
|PBI
|click on ''Go'' ➜ ''Connect to server'' ➜ ''SMB''; input the NETBIOS name of server, name of share, name of domain (or workgroup), and the share's username and password
|-
|nautilus
|[[GNOME2|GNOME]]
|click on ''Go'' ➜ ''Network'' ➜ ''Windows Network''
|-
|smb4k
|PBI
|click on the "Network Neighborhood" tab
|-
|thunar
|[[XFCE4|XFCE]] or PBI
|in the left frame, click on ''Network'' ➜ ''Windows Network'
|-
|}

=== Configuring the Samba Server === 


If you would like to share folders or a printer attached to your PC-BSD system with other users in your network, configure the built-in Samba server.


In order to create shares, Samba's configuration file, {{citelink|url=http://samba.org/samba/docs/man/manpages-3/smb.conf.5.html|txt=smb.conf}}, needs to be modified. You can either edit this file manually or use a GUI utility such as {{citelink|url=http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/SWAT.html|txt=SWAT}}. This section will demonstrate both methods.

==== Edit smb.conf Manually ==== 


To modify the file manually, become the superuser and copy the sample file to the configuration directory:


{{txtbox|box='''cp /usr/local/share/examples/samba36/smb.conf.sample /usr/local/etc/smb.conf'''}}


Open the copied file in your favorite editor and review the default settings, editing them to match your network. In particular, check these global settings:
[[File:Swat.jpeg|thumb|393px|'''Figure 9.3a: SWAT Graphical Menu''']]
* '''workgroup =''' must match the Windows workgroup or domain name; unless the administrator has changed it, the default workgroup name is WORKGROUP


* '''security =''' the security modes are described in the {{citelink|url=http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/ServerType.html#id2559114|txt=Samba HOWTO}}


* '''hosts allow =''' you should input the network address to restrict connections to the local network


In the share definitions section, review the ''[homes]'' settings. You can also define your own shares. This example will share the ''Downloads'' directory of user1 as read-only:


{{txtbox|pre|box=[Downloads]
path = /usr/home/user1/Downloads
public = yes
writable = no}}


To test your changes, restart the Samba service:


{{txtbox|pre|box='''/usr/local/etc/rc.d/samba restart'''}}


and try browsing to the share from another system. Note that you may have to first map a drive to the share in order for it to appear in Windows Explorer or within the file manager utility of another PC-BSD or Linux system.

==== Create Shares Using SWAT ==== 


SWAT provides a graphical front-end to ''smb.conf'' through a web browser.


To enable SWAT, remove the # at the beginning of this line in ''/etc/inetd<nowiki>.</nowiki>conf'':


{{txtbox|box={{pound}}swat stream tcp nowait/400 root /usr/local/sbin/swat swat}}


Add the following line to ''/etc/rc.conf'':

{{txtbox|box=inetd_enable=”YES”}}


And start '''inetd''':


{{txtbox|box='''/etc/rc.d/inetd start'''}}


To connect to SWAT, open a web browser and input the IP address of the PC-BSD computer followed by '':901''. When prompted, input the username ''root'' and the password associated with the superuser account. In the example shown in Figure 9.3a, the user has clicked on the "Globals" button in order to view the global settings.


One of the nice features of SWAT is the built-in help system. If you need more information about an option, simply click its "Help" hyperlink to access that section of the Samba documentation. The "shares" button allows you to quickly create shares and the "view" button allows you to review the current configuration.


<noinclude>
{{refheading}}
{{GroupListHeading|group=tables}}
[[category:handbook]]
[[category:Common Tasks]]
[[category:Files and File Sharing]]
</translate>
<languages/>
</noinclude>

MediaWiki:Common.css

2013-04-30T09:53:48Z

Tigersharke:

/* CSS placed here will be applied to all skins */

/**************************************************************************/
/* Here is the Spiffy Table which allows for nice colors, bold titles and */
/* alternating white/grey rows. It does not display entirely well when a */
/* rowspan=x is defined. This is used by template tbl-init or can be used */
/* alone by specifying class=spiffy_table. A plain table without any */
/* background color but otherwise similar format may be used by adding */
/* class=simple_table. */
/**************************************************************************/

table.spiffy_table, table.simple_table {
border: 2px solid rgb(186, 186, 186);
border-collapse: collapse;
}

.spiffy_table tr:nth-child(odd) > td {
background-color:#EEEEEE;
}

.spiffy_table tr:nth-child(even) > td {
background-color:#FFFFFF;
}

.spiffy_table th {
background-color:#FFFFD9;
border-color: #BABFA3;
border-style: solid;
border-width: 0 1px 2px 1px;
font-weight: bold;
padding: 5px;
text-align: center;
}

.simple_table th {
border-color: rgb(186, 186, 186);
border-style: solid;
border-width: 0 1px 2px 1px;
font-weight: bold;
padding: 5px;
text-align: center;
}

.spiffy_table caption, .simple_table caption {
font-weight: bold;
text-align: left;
}

.spiffy_table td, .simple_table td {
padding: 5px;
border-style: solid;
border-color:#BABFA3;
border-width: 1px 1px 1px 1px;
}

/**************************************************************************/
/* This prevents the wiki from insisting upon using on titles */
/* from table captions above. Not even adding a separate class to wrap */
/* around the citelink type references via span tags worked. */
/**************************************************************************/

.GroupListItem, .selflink {
font-weight: normal;
font-style: normal;
}

/**************************************************************************/
/* Various style adjustments for different kinds or levels of emphasis. */
/* Each class is named for the template that uses it. */
/**************************************************************************/

.redtxt {
color:rgb(255,0,0);
}

.highlight {
background: yellow;
color: #000000;
}

.orangelight {
background: #8B5A00;
color: #FFFFFF;
}

.redlight {
background: crimson;
color: #FFFFFF;
}

.smalltext {
font-size:small;
}

.strike {
text-decoration:line-through;
}

/**************************************************************************/
/* This is the txtbox style sheet section. Adjustments to the template */
/* can change it from using a table to a div with floats to handle the */
/* positions and wrapping, but there still exists some strange wrapping */
/* effects which mean this CSS is currently unused until solved. */
/**************************************************************************/

.txtbox {
align: center;
clear: both;
margin-bottom: 2px;
margin-top: 2px;
}

.txtbox-box {
font-family: Courier New, Courier, monospace;
border: #aaaaaa dashed 1px;
background: #f6f6f6;
text-align:left;
float:left;
position:relative;
margin-right: 6px;
margin-bottom: 12px;
margin-top: 12px;
width:auto;
padding:5px 5px 5px 5px;
}

.txtbox-txt {
float:left;
position:relative;
margin-left: 6px;
margin-right: 12px;
margin-bottom: 12px;
margin-top: 12px;
width:auto;
padding:5px 5px 5px 5px;
}

MediaWiki:Common.css

2013-04-30T09:51:39Z

Tigersharke:

Category:Uses strike

2013-04-30T09:46:22Z

Tigersharke:

[[category:categories]][[category:uses]]
__HIDDENCAT__

Creating an Automated Installation with pc-sysinstall

2013-04-30T09:20:25Z

Tigersharke:

<noinclude><translate>


{{NavHeader|back=Upgrading PC-BSD®|forward=Desktops}}</noinclude>


PC-BSD® provides a set of Bourne shell scripts that allow advanced users to create automatic or customized PC-BSD® installations. '''pc-sysinstall''' is the name of the master script; it reads a customizable configuration file and uses dozens of backend scripts to perform the installation. You can read more about this utility by typing '''man pc-sysinstall'''.


Here is a quick overview of the components used by '''pc-sysinstall''':


* '''/usr/share/pc-sysinstall/backend/''' contains the scripts used by the PC-BSD® installer. Scripts have been divided by function, such as ''functions-bsdlabel.sh'' and ''functions-installcomponents.sh''. If you have ever wondered how the PC-BSD® installer works, read through these scripts. This directory also contains the ''parseconfig.sh'' and ''startautoinstall.sh'' scripts which '''pc-sysinstall''' uses to parse the configuration file and begin the installation.


* '''/usr/share/pc-sysinstall/backend-partmanager/''' contains the scripts which are used by the installer to create and delete partitions.


* '''/usr/share/pc-sysinstall/backend-query/''' contains the scripts which are used by the installer to detect (e.g. ''detect-nics.sh'') and configure (e.g. ''enable-net.sh'') hardware.


* '''/usr/share/pc-sysinstall/components/''' contains FreeBSD ports and src and the PBIs for chromium, firefox, opera, and thunderbird.


* '''/usr/share/pc-sysinstall/conf/''' contains the configuration file ''pc-sysinstall.conf''. It also contains a file indicating which localizations are available (''avail-langs''), a list of files which are not touched during an upgrade (''exclude-from-upgrade''), and a ''license/'' subdirectory containing text files of applicable licenses (e.g. ''bsd-en.txt'' and ''nvidia-en.txt'').


* '''/usr/share/pc-sysinstall/doc/''' contains the help text that is seen if you run '''pc-sysinstall''' without any arguments.


* '''/usr/share/examples/pc-sysinstall/''' contains several example configuration files for different scenarios (e.g. ''upgrade'', ''fbsd-netinstall''). The ''README'' file in this directory should be considered as mandatory reading before using '''pc-sysinstall'''.


* '''/usr/sbin/pc-sysinstall''' this is the script that is used to perform a customized installation.


To create a custom installation, perform the following steps:


# [[#Determine which variables you wish to customize|Determine which variables you wish to customize]]. 
# [[#Create a customized configuration|Create a customized configuration]]. 
# [[#Create a custom installation media|Create a custom installation media]]. 


These steps are discussed in more detail below.

== Determine Which Variables you Wish to Customize == 


A list of possible variables can be found in ''/usr/share/examples/pc-sysinstall/README'' and in Table 5.5a. Note that the Table is meant as a quick reference to determine which variables are available. The ''README'' file contains more complete descriptions for each variable.


{{tbl-init|caption=5.5a: Available Variables for Customizing a PC-BSD® Installation}}
!width=20%|Variable
!Options
!Description
|-
|hostname=||should be unique for the network||optional as installer will auto-generate a hostname if empty
|-
|installMode=||fresh, upgrade, or extract||sets the installation type
|-
|installLocation=||/path/to/location||used only when installMode is extract and should point to an already mounted location
|-
|installInteractive=||yes or no||set to no for automated installs without user input
|-
|netDev=||AUTO-DHCP or FreeBSD interface name||type of network connection to use during the installation
|-
|netIP=||IP address of interface used during installation||only use if ''netDev'' is set to an interface name
|-
|netMask=||subnet mask of interface||only use if netDev is set to an interface name
|-
|netNameServer=||IP address of DNS server||only use if netDev is set to an interface name
|-
|netDefaultRouter=||IP address of default gateway||only use if netDev is set to an interface name
|-
|netSaveDev=||AUTO-DHCP or FreeBSD interface name(s) (multiple allowed separated by spaces)||type of network configuration to enable on the installed system; can set multiple interfaces
|-
|netSaveIP=||IP address of interface ''<interface_name>'' or DHCP||only use if netSaveDev is set to an interface name or a list of interface names (repeat for each interface)
|-
|netSaveMask=||subnet mask of interface ''<interface_name>''||only use if netSaveDev is set to an interface name or a list of interface names (repeat for each interface)
|-
|netSaveNameServer=||IP address of DNS server (multiple allowed separated by spaces)||only use if netSaveDev= is set to an interface name or a list of interface names (do not repeat for each interface)
|-
|netSaveDefaultRouter=||IP address of default gateway||only use if netSaveDev= is set to an interface name or a list of interface names (do not repeat for each interface)
|-
|disk0=||FreeBSD disk device Name, (e.g. ''ad0'')||see ''README'' for examples
|-
|partition=||all, free, s1, s2, s3, s4, image||see ''README'' for examples
|-
|partscheme=||MBR or GPT||partition scheme type
|-
|mirror=||FreeBSD disk device name (e.g. ''ad1'')||sets the target disk for the mirror (i.e. the second disk)
|-
|rmirrorbal=||load, prefer, round-robin, split||defaults to round-robin if the mirror balance method is not specified
|-
|rbootManager=||none, bsd||whether or not to install the FreeBSD boot manager
|-
|image=||/path/to/image||will write specified image file
|-
|commitDiskPart|| ||this variable is mandatory and must be placed at the end of each diskX= section; create a diskX= section for each disk you wish to configure.
|-
|encpass=||password value||at boot time, system will prompt for this password in order to mount the associated GELI encrypted partition
|-
|commitDiskLabel|| ||this variable is mandatory and must be placed at the end of disk's partitioning settings; see the ''README'' for examples on how to set the <File System Type> <Size> <Mountpoint> entries for each disk
|-
|installMedium=||dvd, local, usb, ftp, rsync, image||source to be used for installation
|-
|localPath=||e.g. usr/freebsd-dist||location of the directory containing the installation files when using installMedium=local
|-
|installType=||PCBSD, FreeBSD||determines whether this is a desktop or a server install
|-
|installFile=||e.g. fbsd-release.tbz||only set if using a customized installer archive
|-
|packageType=||tar, uzip, split, dist||the archive type on the installation media
|-
|ftpPath=||e.g. {{ftp}}ftp.pcbsd.org/pub/mirror/9.1/amd64/netinstall/||location of the installer archive when using installMedium=ftp
|-
|rsyncPath=||e.g. life-preserver/back-2011-09-12T14_53_14||location of the rsync data on the remote server when using installMedium=rsync
|-
|rsyncUser=||username||set when using installMedium=rsync
|-
|rsyncHost=||IP address of rsync server||set when using installMedium=rsync
|-
|rsyncPort=||port number||set when using installMedium=rsync
|-
|installComponents=||e.g. amarok,firefox,ports||components must exist in ''/PCBSD/pc-sysinstall/components/''
|-
|upgradeKeepDesktopProfile=||yes or no||specify if you wish to keep your existing user's desktop profile data during an upgrade
|-
|rootPass=||password||set the root password of the installed system to the specified string
|-
||rootEncPass=||encrypted string||set root password to specified encrypted string
|-
||userName=||case sensitive value||create a separate block of user values for each user you wish to create
|-
||userComment=||description||description text can include spaces
|-
|userPass=||case sensitive value|password of user
|-
|userEncPass||encrypted string||set user password to specified encrypted string
|-
|userShell=||e.g. ''/bin/csh''||path to default shell
|-
|userHome=||e.g. ''/home/username''||path to home directory
|-
|userGroups=||e.g. wheel,operator||comma separated (no spaces) list of groups
|-
|commitUser|| ||mandatory, must be last line in each user block
|-
|runCommand=||path to command||run the specified command within chroot of the installed system, after the installation is complete
|-
|runScript=||path to script||runs specified script within chroot of the installed system, after the installation is complete
|-
|runExtCommand=||path to command||runs a command outside the chroot
|-
|timeZone=||e.g. America/New_York||location must exist in ''/usr/share/zoneinfo/''
|-
|enableNTP=||yes or no||enable/disable NTP
|-
|localizeLang=||e.g. en||sets the system console and Desktop to the target language
|-
|localizeKeyLayout=||e.g. en||updates the system's Xorg config to set the keyboard layout
|-
|localizeKeyModel=||e.g. pc104||updates the system's Xorg config to set the keyboard model
|-
|localizeKeyVariant=||e.g. intl||updates the Xorg config to set the keyboard variant
|-
|autoLoginUser=||username||user will be logged in automatically without entering a password
|}

== Create a Customized Configuration == 


One way to create this file is to read through the configuration examples in ''/usr/share/examples/pc-sysinstall/'' to find the one that most closely matches your needs. Copy that file (to any location) and customize it so that it includes the variables and values you would like to use in your installation.


An alternate way to create this file is to perform an installation of the version that you wish to customize. The installer will automatically create a file containing the settings you selected during the installation to ''/root/pc-sysinstall.cfg.'' You can use that configuration file as-is, or customize it to meet an installation's needs. This method may prove easier to use if you are performing complex disk layouts.


Here is a sample configuration:


{{txtbox|box={{pound}} Sample configuration file for an installation using pc-sysinstall


installMode=fresh
installInteractive=no
hostname=myhost.mydomain.com


{{pound}} Set the disk parameters - 1st disk
disk0=da0
partition=all
bootManager=none
commitDiskPart


{{pound}} Set the disk parameters - 2nd disk
disk1=da1
partition=all
bootManager=none
commitDiskPart


{{pound}} Setup the disk label - 1st disk
{{pound}} All sizes are expressed in MB
{{pound}} 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
{{pound}} Size 0 means use the rest of the slice size
{{pound}} Do it now!
commitDiskLabel


{{pound}} Setup the disk label - 2nd disk
{{pound}} All sizes are expressed in MB
{{pound}} 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
{{pound}} Size 0 means use the rest of the slice size>
{{pound}} Do it now!
commitDiskLabel


netDev=em1
netIP=172.16.80.250
netMask=255.255.240.0
netNameServer=172.16.80.1
netDefaultRouter=172.16.80.1
netSaveDev=em0 em1
netSaveIP_em0=192.168.101.42
netSaveIP_em1=172.16.80.156
netSaveMask_em0=255.255.252.0
netSaveMask_em1=255.255.240.0
netSaveNameServer=172.16.80.1
netSaveDefaultRouter=192.168.100.1


{{pound}} Set if we are installing via optical, USB, or FTP
installType=FreeBSD
installMedium=ftp
ftpPath={{http}}pkgbuilder.mydomain.com/images/freebsd/8.2/
packageType=tar


{{pound}} List our components to install
{{pound}}installComponents=ports,src


{{pound}} Set the root pass
rootPass=root


{{pound}} Setup our users
userName=demo
userComment=Demo User
userPass=demo
userShell=/bin/sh
userHome=/home/demo
commitUser


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


{{pound}} 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


{{pound}} Fetch/install VMware Tools
runCommand=fetch -o /tmp/vmtools.tar.gz {{http}}pkgbuilder.mydomain.com/images/freebsd/vmware-freebsd-tools.tar.gz
runCommand=zcat /tmp/vmtools.tar.gz | tar -C /tmp -xvf -
runCommand=/tmp/vmware-tools-distrib/vmware-install.pl -d
runCommand=rm -rf /tmp/vmware-tools-distrib
runCommand=/usr/local/sbin/sysrc puppet_enable=YES
{{pound}} Generate the certificate to be signed by the master
runCommand=/usr/local/bin/puppet agent -t}}


If you wish to perform a fully-automated installation that does not prompt for any user input, you will also need to review ''/usr/share/examples/pc-sysinstall/pc-autoinstall.conf'' and place a customized copy of that file into ''/boot/pc-autoinstall.conf'' on your installation media.


Table 5.5b summarizes the additional variables that are available for fully automatic installations. More detailed descriptions can be found in the ''/usr/share/examples/pc-sysinstall/pc-autoinstall.conf'' file. Note that the variables in this file use a different syntax than those in Table 5.5a, in that the values follow a colon and a space rather than an equal sign.


{{tbl-init|caption=5.5b: Additional Variables for Automated Installations}}
!Variable
!Options
!Description
|-
|pc_config||URL or /path/to/file||location of customized ''pc-sysinstall.conf''
|-
|confirm_install||yes or no||should be set to yes, otherwise booting the wrong disk will result in a system wipe
|-
|shutdown_cmd||e.g. '''shutdown -p now'''||good idea to run a shutdown, but can be any command/script you wish to execute post-install
|-
|nic_config||dhcp-all or <interface name> <IP address> <subnet mask>||will attempt dhcp on all found NICs until the installation file can be fetched or will setup specified interface
|-
|nic_dns||IP address|DNS server to use
|-
|nic_gateway||IP address||default gateway to use
|}


Here is a sample ''pc-autoinstall.conf'' file:


{{txtbox|box={{pound}} pc-autoinstall.conf example
{{pound}}
{{pound}} Usage: Modify these variables, and copy the file to
{{pound}} /boot/pc-autoinstall.conf on your PC-BSD installation medium
{{pound}}
{{pound}} The conf will then be read at bootup, and your automated
{{pound}} install will take place
<nowiki>##################################################################</nowiki>


{{pound}} Where the pc-sysinstall main config is located
{{pound}} Can be either a file on the booted CD / DVD / USB media,
{{pound}} or a remote file on http / ftp
{{pound}}
{{pound}} The value %%NIC_MAC%% is special, and will be substituted with
{{pound}} the macaddress of the enabled NIC from DHCP or manually set
{{pound}} with 'nic_config:'
<nowiki>##################################################################</nowiki>


{{pound}} Examples:
{{pound}} pc_config: {{ftp}}192.168.0.2/cust-install.cfg
{{pound}} pc_config: {{http}}192.168.0.2/cust-install.cfg
{{pound}} pc_config: {{http}}192.168.0.2/%%NIC_MAC%%.cfg
{{pound}} pc_config: /boot/cust-install.cfg
pc_config:
{{http}}pkgbuilder.mydomain.com/images/freebsd/pc-sysinstall.cfg>


{{pound}} Set this to yes if we should confirm before doing an install
{{pound}} This should normally be set to yes, otherwise booting the wrong
{{pound}} disk will result in a system wipe
confirm_install: no


{{pound}} Set the command to run post-install, usually best to run shutdown
{{pound}} but this can be replaced with any other command / script you wish
{{pound}} to execute post-install 
shutdown_cmd: shutdown -r now 


{{pound}} Options for the network setup, should the cfg need to be fetched
{{pound}} from a remote location, only necessary when using ftp or http
<nowiki>##################################################################</nowiki>


{{pound}} Special option, will attempt dhcp on all found NICs
{{pound}} until the file can be fetched, or we run out of interfaces
{{pound}} nic_config: dhcp-all


{{pound}} Line to be passed to the "ifconfig" command to bring up an interface
nic_config: em1 172.16.80.250 255.255.240.0


{{pound}} DNS server to use
nic_dns: 172.16.80.1


{{pound}} Default router / gateway
nic_gateway: 172.16.80.1}}

== Create a Custom Installation Media or Installation Server == 


'''pc-sysinstall''' supports the following installation methods:


* from a CD, DVD, or USB media


* from an installation directory on an HTTP, FTP, SSH+rsync, or a [[Thin_Client#Creating a PXE Boot Install Server|PXE Boot Install]] server


The easiest way to create a custom installation media is to modify an existing installation image. For example, if you have downloaded an ISO for the PC-BSD® version that you wish to customize, the superuser can access the contents of the ISO as follows:


{{txtbox|box='''mdconfig -a -t vnode -f PCBSD9.0-x86-DVD.iso -u 1'''
'''mount -t cd9660 /dev/md1 /mnt'''}}

Make sure you have changed into a directory (use '''cd''') where you would like to copy the contents of the ISO. In the following examples, ''/tmp/custominstall/'' was created as the directory for this purpose:


{{txtbox|box='''cd /tmp/custominstall'''
'''tar -C /mnt -cf - . {{!}} tar -xvf -'''
'''umount /mnt'''}}


Alternately, if you have inserted an installation CD or DVD, you can mount the media and copy its contents to your desired directory:


{{txtbox|box='''mount -t cd9660 /dev/cd0 /mnt'''
'''cp -R /mnt/* /tmp/custominstall/'''
'''umount /mnt'''}}


If you are creating an automated installation, copy your customized ''pc-autoinstall.conf'' to ''/tmp/custominstall/boot/''.


Copy your customized configuration file to ''/tmp/custominstall/''. Double-check that the "installMedium=" variable in your customized configuration file is set to the type of media that you will be installing from.


You may also need to add some extra files if you set the following variables in your custom configuration file:


* '''installComponents=''' make sure that any extra components you wish to install exist in ''extras/PBI/'' (if they end in the ''.pbi'' extension) or ''extras/components/'' (if they end in ''.tbz'')


* '''runCommand=''' make sure the command exists in the specified path


* '''runScript=''' make sure the script exists in the specified path


* '''runExtCommand=''' make sure the command exists in the specified path


If the installation media is a CD or DVD, you will need to create a bootable media that contains the files in your directory. To create a bootable ISO:


{{txtbox|box='''cd /tmp/custominstall
'''mkisofs -V mycustominstall -J -R -b boot/cdboot -no-emul-boot -o myinstall.iso'''}}


You can then use your favorite burning utility to burn the ISO to the media.


To begin an installation that requires user interaction:


'''pc-sysinstall -c /path_to_your_config_file'''


To begin a fully automated installation, insert the installation media and reboot.


If you are using an HTTP, FTP, or SSH server as the installation media, untar or copy the required files to a directory on the server that is accessible to users. Be sure to configure the server so that the installation files are accessible to the systems that you wish to install. If you are using a PXE Boot Install server, follow the instructions at [[Thin_Client#Connecting_to_and_Customizing_the_PXE_Boot_Install_Server|Connecting to and Customizing the PXE Boot Install Server]].


<noinclude>

{{GroupListHeading|group=tables}}
[[category:Creating an Automated Installation with pc-sysinstall]]
[[category:Advanced Installation Topics]]
[[category:handbook]]
</translate>
<languages/>
</noinclude>

Template:Txtbox

2013-04-30T09:17:05Z

Tigersharke: revert this until wrap issues can be solved some way or other.

<includeonly>{|align="center" cellpadding="5px" style="border: none; margin-left:{{{margin-left|12px}}}; margin-right:{{{margin-right|12px}}}; margin-top:{{{margin-top|10px}}}; margin-bottom:{{{margin-bottom|10px}}}; border-collapse: collapse;"
|style="font-family: Courier New, Courier, monospace; border: #aaaaaa dashed 1px; background: #f6f6f6; text-align:left; width:{{{width|auto}}}; {{white-space|{{{1|}}}}} padding:5px 5px 5px 5px; {{{overrides|}}}"|{{{box|WAT box?}}}
|style="border:none; text-align:{{{txt-text-align|left}}}; padding:0px 5px 0px {{{txt-padding-left|5px}}};"|{{{txt|}}}
|}</includeonly><noinclude>
== Explanation ==
This template encloses the provided text within a dashed line box. The text to the right of the box may be some type of comment such as ''"a prompt asking for the root password will open."''. The effect will be shrink to fit but the width (depending upon wrap style) of the box can be adjusted if necessary. Note the <nowiki><nowiki></nowiki> 'prefixed with a space' formatting trick should be avoided. Other style markup like for ''italic'' or '''bold''' should be placed directly around the specific content and not around the entire template. Individual {{pound}} symbols should be replaced with <nowiki>{{pound}}</nowiki> and a series of pound symbols may be enclosed within nowiki tags or they will be parsed as numbered list elements.
=== Wrap Control ===
{{tbl-init|class=simple_table|caption=Wrap Options}}
!our code!!actual CSS!!Explanation
|-
|'''pre''' || White-space: pre; || '''default''': acts like 'pre' whitespace preserved, text wraps at box border and line breaks.
|-
|'''wrap''' || White-space: pre-wrap; || whitespace preserved, text wraps at box border and line breaks. Good for very long commands.
|-
|'''wiki''' || White-space: nowrap; || is this the brain damaged method the magic (prefix w/space) wiki text boxes use??
|-
|'''collapse''' || White-space: pre-line; || multiple white space collapses, text wraps at box border and line breaks.
|-
|'''code''' || White-space: pre; || easier to remember effect name.
|-
|'''normal''' || White-space: normal; || multiple white space collapses, text wraps at box border.
|-
|'''override''' || White-space: pre; || use for simple 'pre' style formatting
|}

{{note| there is some weirdness with unintended blank lines at the bottom. For some situations this can be fixed by using one long line that includes a <nowiki> </nowiki> to assist formatting. The default is reasonable for most situations but would require the fix to avoid the extra unneeded space/lines.}}

== Usage ==

'''<nowiki>{{</nowiki>txtbox|''width='''value'''''|box='''''content such as parens containing 5({{nbsp|5}}) spaces preserved,'' 
<nowiki>'''</nowiki>''second line'' - <nowiki>{{</nowiki>highlight|note that bold and italic and highlight/redlight<nowiki>}}'''</nowiki> 
'''|txt='''''Text to right of box''<nowiki> </nowiki><nowiki>''</nowiki>''second line<nowiki>''</nowiki> - <nowiki>{{</nowiki>redlight|are possible too.<nowiki>}}</nowiki>'''''}}'''

=== Result ===

{{txtbox|box=content such as parens containing 5( ) spaces preserved,
'''second line''' - {{highlight|note that bold and italic and highlight/redlight}}|txt=Text to right of box
''second line'' - {{redlight|are possible too.}}}}</noinclude><noinclude>
{{GroupListHeading|group=tables}}
[[category:templates]]
</noinclude>

Convert a FreeBSD System to PC-BSD®

2013-04-30T08:58:33Z

Tigersharke:

<noinclude><translate>


{{NavHeader|back=Install a Server |forward=Using a Rolling Release}}</noinclude>


Beginning in February, 2013, the PC-BSD® utilities dealing with software installation and upgrades were converted to [https://wiki.freebsd.org/pkgng pkgng], FreeBSD's Next Generation package management tool. Part of this change included the creation of a custom PC-BSD® package repository which contains all of the packages that can be built using pkgng. Since the FreeBSD project does not yet have an official pkgng repository, FreeBSD users who wish to use pkgng are welcome to use the PC-BSD® package repository.


This package repository contains a custom package, called ''pcbsd-base'', which can be used to easily convert an existing FreeBSD installation into a PC-BSD® desktop. It also contains a custom package called ''trueos-base'' which can be used to convert an existing FreeBSD installation into a TrueOS® server. The converted desktop will contain all of the graphical utilities that come with PC-BSD® and the converted server will contain all of their command line equivalents.


This section describes how to:


* Configure a FreeBSD or PC-BSD® system to use the pkgng repository.


* Convert a FreeBSD system to a PC-BSD® desktop.


* Convert a FreeBSD system to a TrueOS® server.

== Switching to the PC-BSD® pkgng Repository == 


If you are running PC-BSD® 9.1-RELEASE or FreeBSD 9.1, you will need to first install the {{citelink|url=http://www.freshports.org/ports-mgmt/pkg/ ports-mgmt/pkg|txt=port or package}}.


After installing pkg, run the command '''pkg2ng''' to import your existing package database from the old format to the new pkgng format.


Next, configure access to the PC-BSD® repository. Start by creating the file ''/usr/local/etc/pkg.conf'' with the following contents:


{{txtbox|box=packagesite: {{ftp}}ftp.pcbsd.org/pub/mirror/packages/9.1-RELEASE/amd64/
PUBKEY: /usr/local/etc/pkg-pubkey.cert
PKG_CACHEDIR: /usr/local/tmp}}


Note that the ''packagesite:'' variable should be changed to a PC-BSD® mirror close to your geographic location. Additionally, ''9.1-RELEASE'' and ''amd64'' can be changed to indicate the release version and architecture you want to use. Click [http://www.pcbsd.org/getmirrors.php?url=packages here] to get a list of the available mirrors and package sets.


Next, download the repository's [http://trac.pcbsd.org/export/21629/pcbsd/current/src-sh/pc-extractoverlay/desktop-overlay/usr/local/etc/pkg-pubkey.cert public key cert file], and copy it to ''/usr/local/etc/pkg-pubkey.cert''.


The system is now configured and you now update your packages to the latest versions from the pkgng repository using the following command:


{{txtbox|box= '''pkg upgrade -fy'''}}


Depending upon what is already installed, you may have to resolve some error messages in order to successfully upgrade all packages.


To install and delete packages use the '''pkg''' command. This command differs in usage from the original package format version. You can learn more about how to use this command in [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/pkgng-intro.html Section 5.5.3 of the FreeBSD Handbook].

== Converting FreeBSD to a PC-BSD® Desktop == 


Once the repository configuration is complete, it is now easy to convert a FreeBSD system into a PC-BSD® desktop using the following commands as the superuser:


{{txtbox|box= '''pkg install -fy pcbsd-base'''
'''rehash'''
'''pbreg set /PC-BSD/SysType PCBSD'''
'''pc-extractoverlay desktop'''
'''pc-extractoverlay ports'''}}


Next, reboot the system and the PC-BSD® login manager will start, allowing you to login to the desktop. If you want the [Post Installation Configuration and Installation Troubleshooting |PC-BSD® display wizard and first boot wizards] to run first, run these commands before rebooting:


{{txtbox|box= '''touch /var/.runxsetup'''
'''touch /var/.pcbsd-firstboot'''
'''touch /var/.pcbsd-firstgui'''}}


If you are running FreeBSD 10-CURRENT, specify the PBI version to pull from. To do so, edit ''/usr/local/etc/pbi.conf'' and add this line:

{{txtbox|box=PBI_FBSDMAJOR: 9}}


{{note|icon64= If you are using NVIDIA video hardware, load the driver before rebooting into the display wizard by running the command '''pc-metapkgmanager add NVIDIA'''.}}

== Converting FreeBSD to a TrueOS® Server == 


If you wish to convert a FreeBSD server to TrueOS®, use the following commands:


{{txtbox|box= '''pkg install -fy trueos-base'''
'''rehash'''
'''pbreg set /PC-BSD/SysType TRUEOS'''
'''pc-extractoverlay server'''
'''pc-extractoverlay ports'''}}


The installation of the ''trueos-base'' package will install the following: [[PBI Manager]], the command line version of '''[[Warden®#Using the Command Line Version of Warden® | warden]]''', and the command line versions of most of the [[Control Panel]] utilities. You will find those utilities in ''/usr/local/bin/pc-*''. It also installs this {{citelink|url=http://trac.pcbsd.org/browser/pcbsd/branches/9.1/build-files/metapkgsets/warden/pkgset/base-system/ports-list|txt=list}} of additional shells and utilities.
</translate>
<noinclude>
{{refheading}}
[[category:Convert a FreeBSD System to PC-BSD®]]
[[category:Advanced Installation Topics]]
[[category:handbook]]
<languages/>
</noinclude>

Convert a FreeBSD System to PC-BSD®

2013-04-30T08:57:09Z

Tigersharke:

<noinclude><translate>


{{NavHeader|back=Install a Server |forward=Using a Rolling Release}}</noinclude>


Beginning in February, 2013, the PC-BSD® utilities dealing with software installation and upgrades were converted to [https://wiki.freebsd.org/pkgng pkgng], FreeBSD's Next Generation package management tool. Part of this change included the creation of a custom PC-BSD® package repository which contains all of the packages that can be built using pkgng. Since the FreeBSD project does not yet have an official pkgng repository, FreeBSD users who wish to use pkgng are welcome to use the PC-BSD® package repository.


This package repository contains a custom package, called ''pcbsd-base'', which can be used to easily convert an existing FreeBSD installation into a PC-BSD® desktop. It also contains a custom package called ''trueos-base'' which can be used to convert an existing FreeBSD installation into a TrueOS® server. The converted desktop will contain all of the graphical utilities that come with PC-BSD® and the converted server will contain all of their command line equivalents.


This section describes how to:


* Configure a FreeBSD or PC-BSD® system to use the pkgng repository.


* Convert a FreeBSD system to a PC-BSD® desktop.


* Convert a FreeBSD system to a TrueOS® server.

== Switching to the PC-BSD® pkgng Repository == 


If you are running PC-BSD® 9.1-RELEASE or FreeBSD 9.1, you will need to first install the [http://www.freshports.org/ports-mgmt/pkg/ ports-mgmt/pkg] port or package.


After installing pkg, run the command '''pkg2ng''' to import your existing package database from the old format to the new pkgng format.


Next, configure access to the PC-BSD® repository. Start by creating the file ''/usr/local/etc/pkg.conf'' with the following contents:


{{txtbox|box=packagesite: {{ftp}}ftp.pcbsd.org/pub/mirror/packages/9.1-RELEASE/amd64/
PUBKEY: /usr/local/etc/pkg-pubkey.cert
PKG_CACHEDIR: /usr/local/tmp}}


Note that the ''packagesite:'' variable should be changed to a PC-BSD® mirror close to your geographic location. Additionally, ''9.1-RELEASE'' and ''amd64'' can be changed to indicate the release version and architecture you want to use. Click [http://www.pcbsd.org/getmirrors.php?url=packages here] to get a list of the available mirrors and package sets.


Next, download the repository's [http://trac.pcbsd.org/export/21629/pcbsd/current/src-sh/pc-extractoverlay/desktop-overlay/usr/local/etc/pkg-pubkey.cert public key cert file], and copy it to ''/usr/local/etc/pkg-pubkey.cert''.


The system is now configured and you now update your packages to the latest versions from the pkgng repository using the following command:


{{txtbox|box= '''pkg upgrade -fy'''}}


Depending upon what is already installed, you may have to resolve some error messages in order to successfully upgrade all packages.


To install and delete packages use the '''pkg''' command. This command differs in usage from the original package format version. You can learn more about how to use this command in [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/pkgng-intro.html Section 5.5.3 of the FreeBSD Handbook].

== Converting FreeBSD to a PC-BSD® Desktop == 


Once the repository configuration is complete, it is now easy to convert a FreeBSD system into a PC-BSD® desktop using the following commands as the superuser:


{{txtbox|box= '''pkg install -fy pcbsd-base'''
'''rehash'''
'''pbreg set /PC-BSD/SysType PCBSD'''
'''pc-extractoverlay desktop'''
'''pc-extractoverlay ports'''}}


Next, reboot the system and the PC-BSD® login manager will start, allowing you to login to the desktop. If you want the [Post Installation Configuration and Installation Troubleshooting |PC-BSD® display wizard and first boot wizards] to run first, run these commands before rebooting:


{{txtbox|box= '''touch /var/.runxsetup'''
'''touch /var/.pcbsd-firstboot'''
'''touch /var/.pcbsd-firstgui'''}}


If you are running FreeBSD 10-CURRENT, specify the PBI version to pull from. To do so, edit ''/usr/local/etc/pbi.conf'' and add this line:

{{txtbox|box=PBI_FBSDMAJOR: 9}}


{{note|icon64= If you are using NVIDIA video hardware, load the driver before rebooting into the display wizard by running the command '''pc-metapkgmanager add NVIDIA'''.}}

== Converting FreeBSD to a TrueOS® Server == 


If you wish to convert a FreeBSD server to TrueOS®, use the following commands:


{{txtbox|box= '''pkg install -fy trueos-base'''
'''rehash'''
'''pbreg set /PC-BSD/SysType TRUEOS'''
'''pc-extractoverlay server'''
'''pc-extractoverlay ports'''}}


The installation of the ''trueos-base'' package will install the following: [[PBI Manager]], the command line version of '''[[Warden®#Using the Command Line Version of Warden® | warden]]''', and the command line versions of most of the [[Control Panel]] utilities. You will find those utilities in ''/usr/local/bin/pc-*''. It also installs this {{citelink|url=http://trac.pcbsd.org/browser/pcbsd/branches/9.1/build-files/metapkgsets/warden/pkgset/base-system/ports-list|txt=list}} of additional shells and utilities.
</translate>
<noinclude>
{{refheading}}
[[category:Convert a FreeBSD System to PC-BSD®]]
[[category:Advanced Installation Topics]]
[[category:handbook]]
<languages/>
</noinclude>

MediaWiki:Common.css

2013-04-30T08:46:33Z

Tigersharke:

/* CSS placed here will be applied to all skins */

/**************************************************************************/
/* Here is the Spiffy Table which allows for nice colors, bold titles and */
/* alternating white/grey rows. It does not display entirely well when a */
/* rowspan=x is defined. This is used by template tbl-init or can be used */
/* alone by specifying class=spiffy_table. A plain table without any */
/* background color but otherwise similar format may be used by adding */
/* class=simple_table. */
/**************************************************************************/

table.spiffy_table, table.simple_table {
border: 2px solid rgb(186, 186, 186);
border-collapse: collapse;
}

.spiffy_table tr:nth-child(odd) > td {
background-color:#EEEEEE;
}

.spiffy_table tr:nth-child(even) > td {
background-color:#FFFFFF;
}

.spiffy_table th {
background-color:#FFFFD9;
border-color: #BABFA3;
border-style: solid;
border-width: 0 1px 2px 1px;
font-weight: bold;
padding: 5px;
text-align: center;
}

.simple_table th {
border-color: rgb(186, 186, 186);
border-style: solid;
border-width: 0 1px 2px 1px;
font-weight: bold;
padding: 5px;
text-align: center;
}

.spiffy_table caption, .simple_table caption {
font-weight: bold;
text-align: left;
}

.spiffy_table td, .simple_table td {
padding: 5px;
border-style: solid;
border-color:#BABFA3;
border-width: 1px 1px 1px 1px;
}

/**************************************************************************/
/* This prevents the wiki from insisting upon using on titles */
/* from table captions above. Not even adding a separate class to wrap */
/* around the citelink type references via span tags worked. */
/**************************************************************************/

.GroupListItem, .selflink {
font-weight: normal;
font-style: normal;
}

/**************************************************************************/
/* Various style adjustments for different kinds or levels of emphasis. */
/* Each class is named for the template that uses it. */
/**************************************************************************/

.redtxt {
color:rgb(255,0,0);
}

.highlight {
background: yellow;
color: #000000;
}

.orangelight {
background: #8B5A00;
color: #FFFFFF;
}

.redlight {
background: crimson;
color: #FFFFFF;
}

.smalltext {
font-size:small;
}

.strike {
text-decoration:line-through;
}

/**************************************************************************/
/* This is the txtbox style sheet section. Adjustments to the template */
/* have changed it from using a table to a div with floats to handle the */
/* positions and wrapping, but there still exists some strange wrapping */
/* effects, especially at larger browser dimensions. */
/**************************************************************************/

.txtbox {
align: center;
clear: both;
margin-bottom: 2px;
margin-top: 2px;
}

.txtbox-box {
font-family: Courier New, Courier, monospace;
border: #aaaaaa dashed 1px;
background: #f6f6f6;
text-align:left;
float:left;
position:relative;
margin-right: 6px;
margin-bottom: 12px;
margin-top: 12px;
width:auto;
padding:5px 5px 5px 5px;
}

.txtbox-txt {
float:left;
position:relative;
margin-left: 6px;
margin-right: 12px;
margin-bottom: 12px;
margin-top: 12px;
width:auto;
padding:5px 5px 5px 5px;
}

MediaWiki:Common.css

2013-04-30T08:37:23Z

Tigersharke:

/* CSS placed here will be applied to all skins */

/**************************************************************************/
/* Here is the Spiffy Table which allows for nice colors, bold titles and */
/* alternating white/grey rows. It does not display entirely well when a */
/* rowspan=x is defined. This is used by template tbl-init or can be used */
/* alone by specifying class=spiffy_table. A plain table without any */
/* background color but otherwise similar format may be used by adding */
/* class=simple_table. */
/**************************************************************************/

table.spiffy_table, table.simple_table {
border: 2px solid rgb(186, 186, 186);
border-collapse: collapse;
}

.spiffy_table tr:nth-child(odd) > td {
background-color:#EEEEEE;
}

.spiffy_table tr:nth-child(even) > td {
background-color:#FFFFFF;
}

.spiffy_table th {
background-color:#FFFFD9;
border-color: #BABFA3;
border-style: solid;
border-width: 0 1px 2px 1px;
font-weight: bold;
padding: 5px;
text-align: center;
}

.simple_table th {
border-color: rgb(186, 186, 186);
border-style: solid;
border-width: 0 1px 2px 1px;
font-weight: bold;
padding: 5px;
text-align: center;
}

.spiffy_table caption, .simple_table caption {
font-weight: bold;
text-align: left;
}

.spiffy_table td, .simple_table td {
padding: 5px;
border-style: solid;
border-color:#BABFA3;
border-width: 1px 1px 1px 1px;
}

/**************************************************************************/
/* This prevents the wiki from insisting upon using on titles */
/* from table captions above. Not even adding a separate class to wrap */
/* around the citelink type references via span tags worked. */
/**************************************************************************/

.GroupListItem, .selflink {
font-weight: normal;
font-style: normal;
}

/**************************************************************************/
/* Various style adjustments for different kinds or levels of emphasis. */
/* Each class is named for the template that uses it. */
/**************************************************************************/

.redtxt {
color:rgb(255,0,0);
}

.highlight {
background: yellow;
color: #000000;
}

.orangelight {
background: #8B5A00;
color: #FFFFFF;
}

.redlight {
background: crimson;
color: #FFFFFF;
}

.smalltext {
font-size:small;
}

.strike {
text-decoration:line-through;
}

/**************************************************************************/
/* This is the txtbox style adjustments. */
/* Each class is named for the template that uses it. */
/**************************************************************************/

.txtbox {
align: center;
clear: both;
margin-bottom: 2px;
margin-top: 2px;
}

.txtbox-box {
font-family: Courier New, Courier, monospace;
border: #aaaaaa dashed 1px;
background: #f6f6f6;
text-align:left;
float:left;
position:relative;
margin-right: 6px;
margin-bottom: 12px;
margin-top: 12px;
width:auto;
padding:5px 5px 5px 5px;
}

.txtbox-txt {
float:left;
position:relative;
margin-left: 6px;
margin-right: 12px;
margin-bottom: 12px;
margin-top: 12px;
width:auto;
padding:5px 5px 5px 5px;
}

MediaWiki:Common.css

2013-04-30T08:31:15Z

Tigersharke:

/* CSS placed here will be applied to all skins */

/**************************************************************************/
/* Here is the Spiffy Table which allows for nice colors, bold titles and */
/* alternating white/grey rows. It does not display entirely well when a */
/* rowspan=x is defined. This is used by template tbl-init or can be used */
/* alone by specifying class=spiffy_table. A plain table without any */
/* background color but otherwise similar format may be used by adding */
/* class=simple_table. */
/**************************************************************************/

table.spiffy_table, table.simple_table {
border: 2px solid rgb(186, 186, 186);
border-collapse: collapse;
}

.spiffy_table tr:nth-child(odd) > td {
background-color:#EEEEEE;
}

.spiffy_table tr:nth-child(even) > td {
background-color:#FFFFFF;
}

.spiffy_table th {
background-color:#FFFFD9;
border-color: #BABFA3;
border-style: solid;
border-width: 0 1px 2px 1px;
font-weight: bold;
padding: 5px;
text-align: center;
}

.simple_table th {
border-color: #BABFA3;
border-style: solid;
border-width: 0 1px 2px 1px;
font-weight: bold;
padding: 5px;
text-align: center;
}

.spiffy_table caption, .simple_table caption {
font-weight: bold;
text-align: left;
}

.spiffy_table td, .simple_table td {
padding: 5px;
border-style: solid;
border-color:#BABFA3;
border-width: 1px 1px 1px 1px;
}

/**************************************************************************/
/* This prevents the wiki from insisting upon using on titles */
/* from table captions above. Not even adding a separate class to wrap */
/* around the citelink type references via span tags worked. */
/**************************************************************************/

.GroupListItem, .selflink {
font-weight: normal;
font-style: normal;
}

/**************************************************************************/
/* Various style adjustments for different kinds or levels of emphasis. */
/* Each class is named for the template that uses it. */
/**************************************************************************/

.redtxt {
color:rgb(255,0,0);
}

.highlight {
background: yellow;
color: #000000;
}

.orangelight {
background: #8B5A00;
color: #FFFFFF;
}

.redlight {
background: crimson;
color: #FFFFFF;
}

.smalltext {
font-size:small;
}

.strike {
text-decoration:line-through;
}

/**************************************************************************/
/* This is the txtbox style adjustments. */
/* Each class is named for the template that uses it. */
/**************************************************************************/

.txtbox {
align: center;
clear: both;
margin-bottom: 2px;
margin-top: 2px;
}

.txtbox-box {
font-family: Courier New, Courier, monospace;
border: #aaaaaa dashed 1px;
background: #f6f6f6;
text-align:left;
float:left;
position:relative;
margin-right: 6px;
margin-bottom: 12px;
margin-top: 12px;
width:auto;
padding:5px 5px 5px 5px;
}

.txtbox-txt {
float:left;
position:relative;
margin-left: 6px;
margin-right: 12px;
margin-bottom: 12px;
margin-top: 12px;
width:auto;
padding:5px 5px 5px 5px;
}

Creating an Automated Installation with pc-sysinstall

2013-04-30T08:29:35Z

Tigersharke:

<noinclude><translate>


{{NavHeader|back=Upgrading PC-BSD®|forward=Desktops}}</noinclude>


PC-BSD® provides a set of Bourne shell scripts that allow advanced users to create automatic or customized PC-BSD® installations. '''pc-sysinstall''' is the name of the master script; it reads a customizable configuration file and uses dozens of backend scripts to perform the installation. You can read more about this utility by typing '''man pc-sysinstall'''.


Here is a quick overview of the components used by '''pc-sysinstall''':


* '''/usr/share/pc-sysinstall/backend/''' contains the scripts used by the PC-BSD® installer. Scripts have been divided by function, such as ''functions-bsdlabel.sh'' and ''functions-installcomponents.sh''. If you have ever wondered how the PC-BSD® installer works, read through these scripts. This directory also contains the ''parseconfig.sh'' and ''startautoinstall.sh'' scripts which '''pc-sysinstall''' uses to parse the configuration file and begin the installation.


* '''/usr/share/pc-sysinstall/backend-partmanager/''' contains the scripts which are used by the installer to create and delete partitions.


* '''/usr/share/pc-sysinstall/backend-query/''' contains the scripts which are used by the installer to detect (e.g. ''detect-nics.sh'') and configure (e.g. ''enable-net.sh'') hardware.


* '''/usr/share/pc-sysinstall/components/''' contains FreeBSD ports and src and the PBIs for chromium, firefox, opera, and thunderbird.


* '''/usr/share/pc-sysinstall/conf/''' contains the configuration file ''pc-sysinstall.conf''. It also contains a file indicating which localizations are available (''avail-langs''), a list of files which are not touched during an upgrade (''exclude-from-upgrade''), and a ''license/'' subdirectory containing text files of applicable licenses (e.g. ''bsd-en.txt'' and ''nvidia-en.txt'').


* '''/usr/share/pc-sysinstall/doc/''' contains the help text that is seen if you run '''pc-sysinstall''' without any arguments.


* '''/usr/share/examples/pc-sysinstall/''' contains several example configuration files for different scenarios (e.g. ''upgrade'', ''fbsd-netinstall''). The ''README'' file in this directory should be considered as mandatory reading before using '''pc-sysinstall'''.


* '''/usr/sbin/pc-sysinstall''' this is the script that is used to perform a customized installation.


To create a custom installation, perform the following steps:


# [[#Determine which variables you wish to customize|Determine which variables you wish to customize]]. 
# [[#Create a customized configuration|Create a customized configuration]]. 
# [[#Create a custom installation media|Create a custom installation media]]. 


These steps are discussed in more detail below.

== Determine Which Variables you Wish to Customize == 


A list of possible variables can be found in ''/usr/share/examples/pc-sysinstall/README'' and in Table 5.5a. Note that the Table is meant as a quick reference to determine which variables are available. The ''README'' file contains more complete descriptions for each variable.


{{tbl-init|caption=5.5a: Available Variables for Customizing a PC-BSD® Installation}}
!width=20%|Variable
!Options
!Description
|-
|hostname=||should be unique for the network||optional as installer will auto-generate a hostname if empty
|-
|installMode=||fresh, upgrade, or extract||sets the installation type
|-
|installLocation=||/path/to/location||used only when installMode is extract and should point to an already mounted location
|-
|installInteractive=||yes or no||set to no for automated installs without user input
|-
|netDev=||AUTO-DHCP or FreeBSD interface name||type of network connection to use during the installation
|-
|netIP=||IP address of interface used during installation||content=only use if ''netDev'' is set to an interface name
|-
|netMask=||subnet mask of interface||content=only use if netDev is set to an interface name
|-
|netNameServer=||IP address of DNS server||content=only use if netDev is set to an interface name
|-
|netDefaultRouter=||IP address of default gateway||content=only use if netDev is set to an interface name
|-
|netSaveDev=||AUTO-DHCP or FreeBSD interface name(s) (multiple allowed separated by spaces)||content=type of network configuration to enable on the installed system; can set multiple interfaces
|-
|netSaveIP=||IP address of interface ''<interface_name>'' or DHCP||content=only use if netSaveDev is set to an interface name or a list of interface names (repeat for each interface)
|-
|netSaveMask=||subnet mask of interface ''<interface_name>''||content=only use if netSaveDev is set to an interface name or a list of interface names (repeat for each interface)
|-
|netSaveNameServer=||IP address of DNS server (multiple allowed separated by spaces)||content=only use if netSaveDev= is set to an interface name or a list of interface names (do not repeat for each interface)
|-
|netSaveDefaultRouter=||IP address of default gateway||content=only use if netSaveDev= is set to an interface name or a list of interface names (do not repeat for each interface)
|-
|disk0=||FreeBSD disk device Name, (e.g. ''ad0'')||see ''README'' for examples
|-
|partition=||all, free, s1, s2, s3, s4, image||see ''README'' for examples
|-
|partscheme=||MBR or GPT||partition scheme type
|-
|mirror=||FreeBSD disk device name (e.g. ''ad1'')||content=sets the target disk for the mirror (i.e. the second disk)
|-
|rmirrorbal=||load, prefer, round-robin, split||defaults to round-robin if the mirror balance method is not specified
|-
|rbootManager=||none, bsd||whether or not to install the FreeBSD boot manager
|-
|image=||/path/to/image||will write specified image file
|-
|commitDiskPart|| ||this variable is mandatory and must be placed at the end of each diskX= section; create a diskX= section for each disk you wish to configure.
|-
|encpass=||password value||at boot time, system will prompt for this password in order to mount the associated GELI encrypted partition
|-
|commitDiskLabel|| ||this variable is mandatory and must be placed at the end of disk's partitioning settings; see the ''README'' for examples on how to set the <File System Type> <Size> <Mountpoint> entries for each disk
|-
|installMedium=||dvd, local, usb, ftp, rsync, image||source to be used for installation
|-
|localPath=||e.g. usr/freebsd-dist||location of the directory containing the installation files when using installMedium=local
|-
|installType=||PCBSD, FreeBSD||determines whether this is a desktop or a server install
|-
|installFile=||e.g. fbsd-release.tbz||only set if using a customized installer archive
|-
|packageType=||tar, uzip, split, dist||the archive type on the installation media
|-
|ftpPath=||e.g. {{ftp}}ftp.pcbsd.org/pub/mirror/9.1/amd64/netinstall/||location of the installer archive when using installMedium=ftp
|-
|rsyncPath=||e.g. life-preserver/back-2011-09-12T14_53_14||location of the rsync data on the remote server when using installMedium=rsync
|-
|rsyncUser=||username||set when using installMedium=rsync
|-
|rsyncHost=||IP address of rsync server||set when using installMedium=rsync
|-
|rsyncPort=||port number||set when using installMedium=rsync
|-
|installComponents=||e.g. amarok,firefox,ports||components must exist in ''/PCBSD/pc-sysinstall/components/''
|-
|upgradeKeepDesktopProfile=||yes or no||specify if you wish to keep your existing user's desktop profile data during an upgrade
|-
|rootPass=||password||set the root password of the installed system to the specified string
|-
||rootEncPass=||encrypted string||set root password to specified encrypted string
|-
||userName=||case sensitive value||create a separate block of user values for each user you wish to create
|-
||userComment=||description||description text can include spaces
|-
|userPass=||case sensitive value|password of user
|-
|userEncPass||encrypted string||set user password to specified encrypted string
|-
|userShell=||e.g. ''/bin/csh''||path to default shell
|-
|userHome=||e.g. ''/home/username''||path to home directory
|-
|userGroups=||e.g. wheel,operator||comma separated (no spaces) list of groups
|-
|commitUser|| ||mandatory, must be last line in each user block
|-
|content=runCommand=||path to command||run the specified command within chroot of the installed system, after the installation is complete
|-
|runScript=||path to script||runs specified script within chroot of the installed system, after the installation is complete
|-
|runExtCommand=||path to command||runs a command outside the chroot
|-
|timeZone=||e.g. America/New_York||location must exist in ''/usr/share/zoneinfo/''
|-
|enableNTP=||yes or no||enable/disable NTP
|-
|localizeLang=||e.g. en||sets the system console and Desktop to the target language
|-
|localizeKeyLayout=||e.g. en||updates the system's Xorg config to set the keyboard layout
|-
|localizeKeyModel=||e.g. pc104||updates the system's Xorg config to set the keyboard model
|-
|localizeKeyVariant=||e.g. intl||updates the Xorg config to set the keyboard variant
|-
|autoLoginUser=||username||user will be logged in automatically without entering a password
|}

== Create a Customized Configuration == 


One way to create this file is to read through the configuration examples in ''/usr/share/examples/pc-sysinstall/'' to find the one that most closely matches your needs. Copy that file (to any location) and customize it so that it includes the variables and values you would like to use in your installation.


An alternate way to create this file is to perform an installation of the version that you wish to customize. The installer will automatically create a file containing the settings you selected during the installation to ''/root/pc-sysinstall.cfg.'' You can use that configuration file as-is, or customize it to meet an installation's needs. This method may prove easier to use if you are performing complex disk layouts.


Here is a sample configuration:


{{txtbox|box={{pound}} Sample configuration file for an installation using pc-sysinstall


installMode=fresh
installInteractive=no
hostname=myhost.mydomain.com


{{pound}} Set the disk parameters - 1st disk
disk0=da0
partition=all
bootManager=none
commitDiskPart


{{pound}} Set the disk parameters - 2nd disk
disk1=da1
partition=all
bootManager=none
commitDiskPart


{{pound}} Setup the disk label - 1st disk
{{pound}} All sizes are expressed in MB
{{pound}} 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
{{pound}} Size 0 means use the rest of the slice size
{{pound}} Do it now!
commitDiskLabel


{{pound}} Setup the disk label - 2nd disk
{{pound}} All sizes are expressed in MB
{{pound}} 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
{{pound}} Size 0 means use the rest of the slice size>
{{pound}} Do it now!
commitDiskLabel


netDev=em1
netIP=172.16.80.250
netMask=255.255.240.0
netNameServer=172.16.80.1
netDefaultRouter=172.16.80.1
netSaveDev=em0 em1
netSaveIP_em0=192.168.101.42
netSaveIP_em1=172.16.80.156
netSaveMask_em0=255.255.252.0
netSaveMask_em1=255.255.240.0
netSaveNameServer=172.16.80.1
netSaveDefaultRouter=192.168.100.1


{{pound}} Set if we are installing via optical, USB, or FTP
installType=FreeBSD
installMedium=ftp
ftpPath={{http}}pkgbuilder.mydomain.com/images/freebsd/8.2/
packageType=tar


{{pound}} List our components to install
{{pound}}installComponents=ports,src


{{pound}} Set the root pass
rootPass=root


{{pound}} Setup our users
userName=demo
userComment=Demo User
userPass=demo
userShell=/bin/sh
userHome=/home/demo
commitUser


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


{{pound}} 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


{{pound}} Fetch/install VMware Tools
runCommand=fetch -o /tmp/vmtools.tar.gz {{http}}pkgbuilder.mydomain.com/images/freebsd/vmware-freebsd-tools.tar.gz
runCommand=zcat /tmp/vmtools.tar.gz | tar -C /tmp -xvf -
runCommand=/tmp/vmware-tools-distrib/vmware-install.pl -d
runCommand=rm -rf /tmp/vmware-tools-distrib
runCommand=/usr/local/sbin/sysrc puppet_enable=YES
{{pound}} Generate the certificate to be signed by the master
runCommand=/usr/local/bin/puppet agent -t}}


If you wish to perform a fully-automated installation that does not prompt for any user input, you will also need to review ''/usr/share/examples/pc-sysinstall/pc-autoinstall.conf'' and place a customized copy of that file into ''/boot/pc-autoinstall.conf'' on your installation media.


Table 5.5b summarizes the additional variables that are available for fully automatic installations. More detailed descriptions can be found in the ''/usr/share/examples/pc-sysinstall/pc-autoinstall.conf'' file. Note that the variables in this file use a different syntax than those in Table 5.5a, in that the values follow a colon and a space rather than an equal sign.


{{tbl-init|caption=5.5b: Additional Variables for Automated Installations}}
!Variable
!Options
!Description
|-
|pc_config||URL or /path/to/file||location of customized ''pc-sysinstall.conf''
|-
|confirm_install||yes or no||should be set to yes, otherwise booting the wrong disk will result in a system wipe
|-
|shutdown_cmd||e.g. '''shutdown -p now'''||good idea to run a shutdown, but can be any command/script you wish to execute post-install
|-
|nic_config||dhcp-all or <interface name> <IP address> <subnet mask>||will attempt dhcp on all found NICs until the installation file can be fetched or will setup specified interface
|-
|nic_dns||IP address|DNS server to use
|-
|nic_gateway||IP address||default gateway to use
|}


Here is a sample ''pc-autoinstall.conf'' file:


{{txtbox|box={{pound}} pc-autoinstall.conf example
{{pound}}
{{pound}} Usage: Modify these variables, and copy the file to
{{pound}} /boot/pc-autoinstall.conf on your PC-BSD installation medium
{{pound}}
{{pound}} The conf will then be read at bootup, and your automated
{{pound}} install will take place
<nowiki>##################################################################</nowiki>


{{pound}} Where the pc-sysinstall main config is located
{{pound}} Can be either a file on the booted CD / DVD / USB media,
{{pound}} or a remote file on http / ftp
{{pound}}
{{pound}} The value %%NIC_MAC%% is special, and will be substituted with
{{pound}} the macaddress of the enabled NIC from DHCP or manually set
{{pound}} with 'nic_config:'
<nowiki>##################################################################</nowiki>


{{pound}} Examples:
{{pound}} pc_config: {{ftp}}192.168.0.2/cust-install.cfg
{{pound}} pc_config: {{http}}192.168.0.2/cust-install.cfg
{{pound}} pc_config: {{http}}192.168.0.2/%%NIC_MAC%%.cfg
{{pound}} pc_config: /boot/cust-install.cfg
pc_config:
{{http}}pkgbuilder.mydomain.com/images/freebsd/pc-sysinstall.cfg>


{{pound}} Set this to yes if we should confirm before doing an install
{{pound}} This should normally be set to yes, otherwise booting the wrong
{{pound}} disk will result in a system wipe
confirm_install: no


{{pound}} Set the command to run post-install, usually best to run shutdown
{{pound}} but this can be replaced with any other command / script you wish
{{pound}} to execute post-install 
shutdown_cmd: shutdown -r now 


{{pound}} Options for the network setup, should the cfg need to be fetched
{{pound}} from a remote location, only necessary when using ftp or http
<nowiki>##################################################################</nowiki>


{{pound}} Special option, will attempt dhcp on all found NICs
{{pound}} until the file can be fetched, or we run out of interfaces
{{pound}} nic_config: dhcp-all


{{pound}} Line to be passed to the "ifconfig" command to bring up an interface
nic_config: em1 172.16.80.250 255.255.240.0


{{pound}} DNS server to use
nic_dns: 172.16.80.1


{{pound}} Default router / gateway
nic_gateway: 172.16.80.1}}

== Create a Custom Installation Media or Installation Server == 


'''pc-sysinstall''' supports the following installation methods:


* from a CD, DVD, or USB media


* from an installation directory on an HTTP, FTP, SSH+rsync, or a [[Thin_Client#Creating a PXE Boot Install Server|PXE Boot Install]] server


The easiest way to create a custom installation media is to modify an existing installation image. For example, if you have downloaded an ISO for the PC-BSD® version that you wish to customize, the superuser can access the contents of the ISO as follows:


{{txtbox|box='''mdconfig -a -t vnode -f PCBSD9.0-x86-DVD.iso -u 1'''
'''mount -t cd9660 /dev/md1 /mnt'''}}

Make sure you have changed into a directory (use '''cd''') where you would like to copy the contents of the ISO. In the following examples, ''/tmp/custominstall/'' was created as the directory for this purpose:


{{txtbox|box='''cd /tmp/custominstall'''
'''tar -C /mnt -cf - . {{!}} tar -xvf -'''
'''umount /mnt'''}}


Alternately, if you have inserted an installation CD or DVD, you can mount the media and copy its contents to your desired directory:


{{txtbox|box='''mount -t cd9660 /dev/cd0 /mnt'''
'''cp -R /mnt/* /tmp/custominstall/'''
'''umount /mnt'''}}


If you are creating an automated installation, copy your customized ''pc-autoinstall.conf'' to ''/tmp/custominstall/boot/''.


Copy your customized configuration file to ''/tmp/custominstall/''. Double-check that the "installMedium=" variable in your customized configuration file is set to the type of media that you will be installing from.


You may also need to add some extra files if you set the following variables in your custom configuration file:


* '''installComponents=''' make sure that any extra components you wish to install exist in ''extras/PBI/'' (if they end in the ''.pbi'' extension) or ''extras/components/'' (if they end in ''.tbz'')


* '''runCommand=''' make sure the command exists in the specified path


* '''runScript=''' make sure the script exists in the specified path


* '''runExtCommand=''' make sure the command exists in the specified path


If the installation media is a CD or DVD, you will need to create a bootable media that contains the files in your directory. To create a bootable ISO:


{{txtbox|box='''cd /tmp/custominstall
'''mkisofs -V mycustominstall -J -R -b boot/cdboot -no-emul-boot -o myinstall.iso'''}}


You can then use your favorite burning utility to burn the ISO to the media.


To begin an installation that requires user interaction:


'''pc-sysinstall -c /path_to_your_config_file'''


To begin a fully automated installation, insert the installation media and reboot.


If you are using an HTTP, FTP, or SSH server as the installation media, untar or copy the required files to a directory on the server that is accessible to users. Be sure to configure the server so that the installation files are accessible to the systems that you wish to install. If you are using a PXE Boot Install server, follow the instructions at [[Thin_Client#Connecting_to_and_Customizing_the_PXE_Boot_Install_Server|Connecting to and Customizing the PXE Boot Install Server]].


<noinclude>

{{GroupListHeading|group=tables}}
[[category:Creating an Automated Installation with pc-sysinstall]]
[[category:Advanced Installation Topics]]
[[category:handbook]]
</translate>
<languages/>
</noinclude>

MediaWiki:Common.css

2013-04-30T08:29:05Z

Tigersharke:

/* CSS placed here will be applied to all skins */

/**************************************************************************/
/* Here is the Spiffy Table which allows for nice colors, bold titles and */
/* alternating white/grey rows. It does not display entirely well when a */
/* rowspan=x is defined. This is used by template tbl-init or can be used */
/* alone by specifying class=spiffy_table. A plain table without any */
/* background color but otherwise similar format may be used by adding */
/* class=simple_table. */
/**************************************************************************/

table.spiffy_table, table.simple_table {
border: 2px solid rgb(186, 186, 186);
border-collapse: collapse;
}

.spiffy_table tr:nth-child(odd) > td {
background-color:#EEEEEE;
}

.spiffy_table tr:nth-child(even) > td {
background-color:#FFFFFF;
}

.spiffy_table th {
background-color:#FFFFD9;
border-color: #BABFA3;
border-style: solid;
border-width: 0 1px 2px 1px;
font-weight: bold;
padding: 5px;
text-align: center;
}

.simple_table th {
border-color: #BABFA3;
border-style: solid;
border-width: 0 1px 2px 1px;
font-weight: bold;
padding: 5px;
text-align: center;
}

.spiffy_table caption, .simple_table caption {
font-weight: bold;
text-align: left;
}

.spiffy_table td, .simple_table td {
padding: 5px;
border-style: solid;
border-color:#BABFA3;
border-width: 1px 1px 1px 1px;
}

/**************************************************************************/
/* This prevents the wiki from insisting upon using on titles */
/* from table captions above. Not even adding a separate class to wrap */
/* around the citelink type references via span tags worked. */
/**************************************************************************/

.GroupListItem, .selflink {
font-weight: normal;
font-style: normal;
}

/**************************************************************************/
/* Various style adjustments for different kinds or levels of emphasis. */
/* Each class is named for the template that uses it. */
/**************************************************************************/

.redtxt {
color:rgb(255,0,0);
}

.highlight {
background: yellow;
color: #000000;
}

.orangelight {
background: #8B5A00;
color: #FFFFFF;
}

.redlight {
background: crimson;
color: #FFFFFF;
}

.smalltext {
font-size:small;
}

.strike {
text-decoration:line-through;
}

/**************************************************************************/
/* This is the txtbox style adjustments. */
/* Each class is named for the template that uses it. */
/**************************************************************************/

.txtbox {
align: center;
clear: both;
}

.txtbox-right {
align: center;
clear: right;
}

.txtbox-left {
align: center;
clear: left;
}

.txtbox-box {
font-family: Courier New, Courier, monospace;
border: #aaaaaa dashed 1px;
background: #f6f6f6;
text-align:left;
float:left;
position:relative;
margin-right: 6px;
margin-bottom: 12px;
margin-top: 12px;
width:auto;
padding:5px 5px 5px 5px;
}

.txtbox-txt {
float:left;
position:relative;
margin-left: 6px;
margin-right: 12px;
margin-bottom: 12px;
margin-top: 12px;
width:auto;
padding:5px 5px 5px 5px;
}

Creating an Automated Installation with pc-sysinstall

2013-04-30T08:27:57Z

Tigersharke:

<noinclude><translate>


{{NavHeader|back=Upgrading PC-BSD®|forward=Desktops}}</noinclude>


PC-BSD® provides a set of Bourne shell scripts that allow advanced users to create automatic or customized PC-BSD® installations. '''pc-sysinstall''' is the name of the master script; it reads a customizable configuration file and uses dozens of backend scripts to perform the installation. You can read more about this utility by typing '''man pc-sysinstall'''.


Here is a quick overview of the components used by '''pc-sysinstall''':


* '''/usr/share/pc-sysinstall/backend/''' contains the scripts used by the PC-BSD® installer. Scripts have been divided by function, such as ''functions-bsdlabel.sh'' and ''functions-installcomponents.sh''. If you have ever wondered how the PC-BSD® installer works, read through these scripts. This directory also contains the ''parseconfig.sh'' and ''startautoinstall.sh'' scripts which '''pc-sysinstall''' uses to parse the configuration file and begin the installation.


* '''/usr/share/pc-sysinstall/backend-partmanager/''' contains the scripts which are used by the installer to create and delete partitions.


* '''/usr/share/pc-sysinstall/backend-query/''' contains the scripts which are used by the installer to detect (e.g. ''detect-nics.sh'') and configure (e.g. ''enable-net.sh'') hardware.


* '''/usr/share/pc-sysinstall/components/''' contains FreeBSD ports and src and the PBIs for chromium, firefox, opera, and thunderbird.


* '''/usr/share/pc-sysinstall/conf/''' contains the configuration file ''pc-sysinstall.conf''. It also contains a file indicating which localizations are available (''avail-langs''), a list of files which are not touched during an upgrade (''exclude-from-upgrade''), and a ''license/'' subdirectory containing text files of applicable licenses (e.g. ''bsd-en.txt'' and ''nvidia-en.txt'').


* '''/usr/share/pc-sysinstall/doc/''' contains the help text that is seen if you run '''pc-sysinstall''' without any arguments.


* '''/usr/share/examples/pc-sysinstall/''' contains several example configuration files for different scenarios (e.g. ''upgrade'', ''fbsd-netinstall''). The ''README'' file in this directory should be considered as mandatory reading before using '''pc-sysinstall'''.


* '''/usr/sbin/pc-sysinstall''' this is the script that is used to perform a customized installation.


To create a custom installation, perform the following steps:


# [[#Determine which variables you wish to customize|Determine which variables you wish to customize]]. 
# [[#Create a customized configuration|Create a customized configuration]]. 
# [[#Create a custom installation media|Create a custom installation media]]. 


These steps are discussed in more detail below.

== Determine Which Variables you Wish to Customize == 


A list of possible variables can be found in ''/usr/share/examples/pc-sysinstall/README'' and in Table 5.5a. Note that the Table is meant as a quick reference to determine which variables are available. The ''README'' file contains more complete descriptions for each variable.


{{tbl-init|caption=5.5a: Available Variables for Customizing a PC-BSD® Installation}}
!width=20%|Variable
!Options
!Description
|-
|hostname=||should be unique for the network||optional as installer will auto-generate a hostname if empty
|-
|installMode=||fresh, upgrade, or extract||sets the installation type
|-
|installLocation=||/path/to/location||used only when installMode is extract and should point to an already mounted location
|-
|installInteractive=||yes or no||set to no for automated installs without user input
|-
|netDev=||AUTO-DHCP or FreeBSD interface name||type of network connection to use during the installation
|-
|netIP=||IP address of interface used during installation||content=only use if ''netDev'' is set to an interface name
|-
|netMask=||subnet mask of interface||content=only use if netDev is set to an interface name
|-
|netNameServer=||IP address of DNS server||content=only use if netDev is set to an interface name
|-
|netDefaultRouter=||IP address of default gateway||content=only use if netDev is set to an interface name
|-
|netSaveDev=||AUTO-DHCP or FreeBSD interface name(s) (multiple allowed separated by spaces)||content=type of network configuration to enable on the installed system; can set multiple interfaces
|-
|netSaveIP=||IP address of interface ''<interface_name>'' or DHCP||content=only use if netSaveDev is set to an interface name or a list of interface names (repeat for each interface)
|-
|netSaveMask=||subnet mask of interface ''<interface_name>''||content=only use if netSaveDev is set to an interface name or a list of interface names (repeat for each interface)
|-
|netSaveNameServer=||IP address of DNS server (multiple allowed separated by spaces)||content=only use if netSaveDev= is set to an interface name or a list of interface names (do not repeat for each interface)
|-
|netSaveDefaultRouter=||IP address of default gateway||content=only use if netSaveDev= is set to an interface name or a list of interface names (do not repeat for each interface)
|-
|disk0=||FreeBSD disk device Name, (e.g. ''ad0'')||see ''README'' for examples
|-
|partition=||all, free, s1, s2, s3, s4, image||see ''README'' for examples
|-
|partscheme=||MBR or GPT||partition scheme type
|-
|mirror=||FreeBSD disk device name (e.g. ''ad1'')||content=sets the target disk for the mirror (i.e. the second disk)
|-
|rmirrorbal=||load, prefer, round-robin, split||defaults to round-robin if the mirror balance method is not specified
|-
|rbootManager=||none, bsd||whether or not to install the FreeBSD boot manager
|-
|image=||/path/to/image||will write specified image file
|-
|commitDiskPart|| ||this variable is mandatory and must be placed at the end of each diskX= section; create a diskX= section for each disk you wish to configure.
|-
|encpass=||password value||at boot time, system will prompt for this password in order to mount the associated GELI encrypted partition
|-
|commitDiskLabel|| ||this variable is mandatory and must be placed at the end of disk's partitioning settings; see the ''README'' for examples on how to set the <File System Type> <Size> <Mountpoint> entries for each disk
|-
|installMedium=||dvd, local, usb, ftp, rsync, image||source to be used for installation
|-
|localPath=||e.g. usr/freebsd-dist||location of the directory containing the installation files when using installMedium=local
|-
|installType=||PCBSD, FreeBSD||determines whether this is a desktop or a server install
|-
|installFile=||e.g. fbsd-release.tbz||only set if using a customized installer archive
|-
|packageType=||tar, uzip, split, dist||the archive type on the installation media
|-
|ftpPath=||e.g. {{ftp}}ftp.pcbsd.org/pub/mirror/9.1/amd64/netinstall/||location of the installer archive when using installMedium=ftp
|-
|rsyncPath=||e.g. life-preserver/back-2011-09-12T14_53_14||location of the rsync data on the remote server when using installMedium=rsync
|-
|rsyncUser=||username||set when using installMedium=rsync
|-
|rsyncHost=||IP address of rsync server||set when using installMedium=rsync
|-
|rsyncPort=||port number||set when using installMedium=rsync
|-
|installComponents=||e.g. amarok,firefox,ports||components must exist in ''/PCBSD/pc-sysinstall/components/''
|-
|upgradeKeepDesktopProfile=||yes or no||specify if you wish to keep your existing user's desktop profile data during an upgrade
|-
|rootPass=||password||set the root password of the installed system to the specified string
|-
||rootEncPass=||encrypted string||set root password to specified encrypted string
|-
||userName=||case sensitive value||create a separate block of user values for each user you wish to create
|-
||userComment=||description||description text can include spaces
|-
|userPass=||case sensitive value|password of user
|-
|userEncPass||encrypted string||set user password to specified encrypted string
|-
|userShell=||e.g. ''/bin/csh''||path to default shell
|-
|userHome=||e.g. ''/home/username''||path to home directory
|-
|userGroups=||e.g. wheel,operator||comma separated (no spaces) list of groups
|-
|commitUser|| ||mandatory, must be last line in each user block
|-
|content=runCommand=||path to command||run the specified command within chroot of the installed system, after the installation is complete
|-
|runScript=||path to script||runs specified script within chroot of the installed system, after the installation is complete
|-
|runExtCommand=||path to command||runs a command outside the chroot
|-
|timeZone=||e.g. America/New_York||location must exist in ''/usr/share/zoneinfo/''
|-
|enableNTP=||yes or no||enable/disable NTP
|-
|localizeLang=||e.g. en||sets the system console and Desktop to the target language
|-
|localizeKeyLayout=||e.g. en||updates the system's Xorg config to set the keyboard layout
|-
|localizeKeyModel=||e.g. pc104||updates the system's Xorg config to set the keyboard model
|-
|localizeKeyVariant=||e.g. intl||updates the Xorg config to set the keyboard variant
|-
|autoLoginUser=||username||user will be logged in automatically without entering a password
|}

== Create a Customized Configuration == 


One way to create this file is to read through the configuration examples in ''/usr/share/examples/pc-sysinstall/'' to find the one that most closely matches your needs. Copy that file (to any location) and customize it so that it includes the variables and values you would like to use in your installation.


An alternate way to create this file is to perform an installation of the version that you wish to customize. The installer will automatically create a file containing the settings you selected during the installation to ''/root/pc-sysinstall.cfg.'' You can use that configuration file as-is, or customize it to meet an installation's needs. This method may prove easier to use if you are performing complex disk layouts.


Here is a sample configuration:


{{txtbox|box={{pound}} Sample configuration file for an installation using pc-sysinstall


installMode=fresh
installInteractive=no
hostname=myhost.mydomain.com


{{pound}} Set the disk parameters - 1st disk
disk0=da0
partition=all
bootManager=none
commitDiskPart


{{pound}} Set the disk parameters - 2nd disk
disk1=da1
partition=all
bootManager=none
commitDiskPart


{{pound}} Setup the disk label - 1st disk
{{pound}} All sizes are expressed in MB
{{pound}} 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
{{pound}} Size 0 means use the rest of the slice size
{{pound}} Do it now!
commitDiskLabel


{{pound}} Setup the disk label - 2nd disk
{{pound}} All sizes are expressed in MB
{{pound}} 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
{{pound}} Size 0 means use the rest of the slice size>
{{pound}} Do it now!
commitDiskLabel


netDev=em1
netIP=172.16.80.250
netMask=255.255.240.0
netNameServer=172.16.80.1
netDefaultRouter=172.16.80.1
netSaveDev=em0 em1
netSaveIP_em0=192.168.101.42
netSaveIP_em1=172.16.80.156
netSaveMask_em0=255.255.252.0
netSaveMask_em1=255.255.240.0
netSaveNameServer=172.16.80.1
netSaveDefaultRouter=192.168.100.1


{{pound}} Set if we are installing via optical, USB, or FTP
installType=FreeBSD
installMedium=ftp
ftpPath={{http}}pkgbuilder.mydomain.com/images/freebsd/8.2/
packageType=tar


{{pound}} List our components to install
{{pound}}installComponents=ports,src


{{pound}} Set the root pass
rootPass=root


{{pound}} Setup our users
userName=demo
userComment=Demo User
userPass=demo
userShell=/bin/sh
userHome=/home/demo
commitUser


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


{{pound}} 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


{{pound}} Fetch/install VMware Tools
runCommand=fetch -o /tmp/vmtools.tar.gz {{http}}pkgbuilder.mydomain.com/images/freebsd/vmware-freebsd-tools.tar.gz
runCommand=zcat /tmp/vmtools.tar.gz | tar -C /tmp -xvf -
runCommand=/tmp/vmware-tools-distrib/vmware-install.pl -d
runCommand=rm -rf /tmp/vmware-tools-distrib
runCommand=/usr/local/sbin/sysrc puppet_enable=YES
{{pound}} Generate the certificate to be signed by the master
runCommand=/usr/local/bin/puppet agent -t}}


If you wish to perform a fully-automated installation that does not prompt for any user input, you will also need to review ''/usr/share/examples/pc-sysinstall/pc-autoinstall.conf'' and place a customized copy of that file into ''/boot/pc-autoinstall.conf'' on your installation media.


Table 5.5b summarizes the additional variables that are available for fully automatic installations. More detailed descriptions can be found in the ''/usr/share/examples/pc-sysinstall/pc-autoinstall.conf'' file. Note that the variables in this file use a different syntax than those in Table 5.5a, in that the values follow a colon and a space rather than an equal sign.


{{tbl-init|caption=5.5b: Additional Variables for Automated Installations}}
!Variable
!Options
!Description
|-
|pc_config||URL or /path/to/file||location of customized ''pc-sysinstall.conf''
|-
|confirm_install||yes or no||should be set to yes, otherwise booting the wrong disk will result in a system wipe
|-
|shutdown_cmd||e.g. '''shutdown -p now'''||good idea to run a shutdown, but can be any command/script you wish to execute post-install
|-
|nic_config||dhcp-all or <interface name> <IP address> <subnet mask>||will attempt dhcp on all found NICs until the installation file can be fetched or will setup specified interface
|-
|nic_dns||IP address|DNS server to use
|-
|nic_gateway||IP address||default gateway to use
|}


Here is a sample ''pc-autoinstall.conf'' file:


{{txtbox|box={{pound}} pc-autoinstall.conf example
{{pound}}
{{pound}} Usage: Modify these variables, and copy the file to
{{pound}} /boot/pc-autoinstall.conf on your PC-BSD installation medium
{{pound}}
{{pound}} The conf will then be read at bootup, and your automated
{{pound}} install will take place
<nowiki>##################################################################</nowiki>


{{pound}} Where the pc-sysinstall main config is located
{{pound}} Can be either a file on the booted CD / DVD / USB media,
{{pound}} or a remote file on http / ftp
{{pound}}
{{pound}} The value %%NIC_MAC%% is special, and will be substituted with
{{pound}} the macaddress of the enabled NIC from DHCP or manually set
{{pound}} with 'nic_config:'
<nowiki>##################################################################</nowiki>


{{pound}} Examples:
{{pound}} pc_config: {{ftp}}192.168.0.2/cust-install.cfg
{{pound}} pc_config: {{http}}192.168.0.2/cust-install.cfg
{{pound}} pc_config: {{http}}192.168.0.2/%%NIC_MAC%%.cfg
{{pound}} pc_config: /boot/cust-install.cfg
pc_config:
{{http}}pkgbuilder.mydomain.com/images/freebsd/pc-sysinstall.cfg>


{{pound}} Set this to yes if we should confirm before doing an install
{{pound}} This should normally be set to yes, otherwise booting the wrong
{{pound}} disk will result in a system wipe
confirm_install: no


{{pound}} Set the command to run post-install, usually best to run shutdown
{{pound}} but this can be replaced with any other command / script you wish
{{pound}} to execute post-install 
shutdown_cmd: shutdown -r now 


{{pound}} Options for the network setup, should the cfg need to be fetched
{{pound}} from a remote location, only necessary when using ftp or http
<nowiki>##################################################################</nowiki>


{{pound}} Special option, will attempt dhcp on all found NICs
{{pound}} until the file can be fetched, or we run out of interfaces
{{pound}} nic_config: dhcp-all


{{pound}} Line to be passed to the "ifconfig" command to bring up an interface
nic_config: em1 172.16.80.250 255.255.240.0


{{pound}} DNS server to use
nic_dns: 172.16.80.1


{{pound}} Default router / gateway
nic_gateway: 172.16.80.1}}

== Create a Custom Installation Media or Installation Server == 


'''pc-sysinstall''' supports the following installation methods:


* from a CD, DVD, or USB media


* from an installation directory on an HTTP, FTP, SSH+rsync, or a [[Thin_Client#Creating a PXE Boot Install Server|PXE Boot Install]] server


The easiest way to create a custom installation media is to modify an existing installation image. For example, if you have downloaded an ISO for the PC-BSD® version that you wish to customize, the superuser can access the contents of the ISO as follows:


{{txtbox|align=right|box='''mdconfig -a -t vnode -f PCBSD9.0-x86-DVD.iso -u 1'''
'''mount -t cd9660 /dev/md1 /mnt'''}}

Make sure you have changed into a directory (use '''cd''') where you would like to copy the contents of the ISO. In the following examples, ''/tmp/custominstall/'' was created as the directory for this purpose:


{{txtbox|align=right|box='''cd /tmp/custominstall'''
'''tar -C /mnt -cf - . {{!}} tar -xvf -'''
'''umount /mnt'''}}


Alternately, if you have inserted an installation CD or DVD, you can mount the media and copy its contents to your desired directory:


{{txtbox|align=right|box='''mount -t cd9660 /dev/cd0 /mnt'''
'''cp -R /mnt/* /tmp/custominstall/'''
'''umount /mnt'''}}


If you are creating an automated installation, copy your customized ''pc-autoinstall.conf'' to ''/tmp/custominstall/boot/''.


Copy your customized configuration file to ''/tmp/custominstall/''. Double-check that the "installMedium=" variable in your customized configuration file is set to the type of media that you will be installing from.


You may also need to add some extra files if you set the following variables in your custom configuration file:


* '''installComponents=''' make sure that any extra components you wish to install exist in ''extras/PBI/'' (if they end in the ''.pbi'' extension) or ''extras/components/'' (if they end in ''.tbz'')


* '''runCommand=''' make sure the command exists in the specified path


* '''runScript=''' make sure the script exists in the specified path


* '''runExtCommand=''' make sure the command exists in the specified path


If the installation media is a CD or DVD, you will need to create a bootable media that contains the files in your directory. To create a bootable ISO:


{{txtbox|box='''cd /tmp/custominstall
'''mkisofs -V mycustominstall -J -R -b boot/cdboot -no-emul-boot -o myinstall.iso'''}}


You can then use your favorite burning utility to burn the ISO to the media.


To begin an installation that requires user interaction:


'''pc-sysinstall -c /path_to_your_config_file'''


To begin a fully automated installation, insert the installation media and reboot.


If you are using an HTTP, FTP, or SSH server as the installation media, untar or copy the required files to a directory on the server that is accessible to users. Be sure to configure the server so that the installation files are accessible to the systems that you wish to install. If you are using a PXE Boot Install server, follow the instructions at [[Thin_Client#Connecting_to_and_Customizing_the_PXE_Boot_Install_Server|Connecting to and Customizing the PXE Boot Install Server]].


<noinclude>

{{GroupListHeading|group=tables}}
[[category:Creating an Automated Installation with pc-sysinstall]]
[[category:Advanced Installation Topics]]
[[category:handbook]]
</translate>
<languages/>
</noinclude>

Creating an Automated Installation with pc-sysinstall

2013-04-30T08:27:11Z

Tigersharke:

<noinclude><translate>


{{NavHeader|back=Upgrading PC-BSD®|forward=Desktops}}</noinclude>


PC-BSD® provides a set of Bourne shell scripts that allow advanced users to create automatic or customized PC-BSD® installations. '''pc-sysinstall''' is the name of the master script; it reads a customizable configuration file and uses dozens of backend scripts to perform the installation. You can read more about this utility by typing '''man pc-sysinstall'''.


Here is a quick overview of the components used by '''pc-sysinstall''':


* '''/usr/share/pc-sysinstall/backend/''' contains the scripts used by the PC-BSD® installer. Scripts have been divided by function, such as ''functions-bsdlabel.sh'' and ''functions-installcomponents.sh''. If you have ever wondered how the PC-BSD® installer works, read through these scripts. This directory also contains the ''parseconfig.sh'' and ''startautoinstall.sh'' scripts which '''pc-sysinstall''' uses to parse the configuration file and begin the installation.


* '''/usr/share/pc-sysinstall/backend-partmanager/''' contains the scripts which are used by the installer to create and delete partitions.


* '''/usr/share/pc-sysinstall/backend-query/''' contains the scripts which are used by the installer to detect (e.g. ''detect-nics.sh'') and configure (e.g. ''enable-net.sh'') hardware.


* '''/usr/share/pc-sysinstall/components/''' contains FreeBSD ports and src and the PBIs for chromium, firefox, opera, and thunderbird.


* '''/usr/share/pc-sysinstall/conf/''' contains the configuration file ''pc-sysinstall.conf''. It also contains a file indicating which localizations are available (''avail-langs''), a list of files which are not touched during an upgrade (''exclude-from-upgrade''), and a ''license/'' subdirectory containing text files of applicable licenses (e.g. ''bsd-en.txt'' and ''nvidia-en.txt'').


* '''/usr/share/pc-sysinstall/doc/''' contains the help text that is seen if you run '''pc-sysinstall''' without any arguments.


* '''/usr/share/examples/pc-sysinstall/''' contains several example configuration files for different scenarios (e.g. ''upgrade'', ''fbsd-netinstall''). The ''README'' file in this directory should be considered as mandatory reading before using '''pc-sysinstall'''.


* '''/usr/sbin/pc-sysinstall''' this is the script that is used to perform a customized installation.


To create a custom installation, perform the following steps:


# [[#Determine which variables you wish to customize|Determine which variables you wish to customize]]. 
# [[#Create a customized configuration|Create a customized configuration]]. 
# [[#Create a custom installation media|Create a custom installation media]]. 


These steps are discussed in more detail below.

== Determine Which Variables you Wish to Customize == 


A list of possible variables can be found in ''/usr/share/examples/pc-sysinstall/README'' and in Table 5.5a. Note that the Table is meant as a quick reference to determine which variables are available. The ''README'' file contains more complete descriptions for each variable.


{{tbl-init|caption=5.5a: Available Variables for Customizing a PC-BSD® Installation}}
!width=20%|Variable
!Options
!Description
|-
|hostname=||should be unique for the network||optional as installer will auto-generate a hostname if empty
|-
|installMode=||fresh, upgrade, or extract||sets the installation type
|-
|installLocation=||/path/to/location||used only when installMode is extract and should point to an already mounted location
|-
|installInteractive=||yes or no||set to no for automated installs without user input
|-
|netDev=||AUTO-DHCP or FreeBSD interface name||type of network connection to use during the installation
|-
|netIP=||IP address of interface used during installation||content=only use if ''netDev'' is set to an interface name
|-
|netMask=||subnet mask of interface||content=only use if netDev is set to an interface name
|-
|netNameServer=||IP address of DNS server||content=only use if netDev is set to an interface name
|-
|netDefaultRouter=||IP address of default gateway||content=only use if netDev is set to an interface name
|-
|netSaveDev=||AUTO-DHCP or FreeBSD interface name(s) (multiple allowed separated by spaces)||content=type of network configuration to enable on the installed system; can set multiple interfaces
|-
|netSaveIP=||IP address of interface ''<interface_name>'' or DHCP||content=only use if netSaveDev is set to an interface name or a list of interface names (repeat for each interface)
|-
|netSaveMask=||subnet mask of interface ''<interface_name>''||content=only use if netSaveDev is set to an interface name or a list of interface names (repeat for each interface)
|-
|netSaveNameServer=||IP address of DNS server (multiple allowed separated by spaces)||content=only use if netSaveDev= is set to an interface name or a list of interface names (do not repeat for each interface)
|-
|netSaveDefaultRouter=||IP address of default gateway||content=only use if netSaveDev= is set to an interface name or a list of interface names (do not repeat for each interface)
|-
|disk0=||FreeBSD disk device Name, (e.g. ''ad0'')||see ''README'' for examples
|-
|partition=||all, free, s1, s2, s3, s4, image||see ''README'' for examples
|-
|partscheme=||MBR or GPT||partition scheme type
|-
|mirror=||FreeBSD disk device name (e.g. ''ad1'')||content=sets the target disk for the mirror (i.e. the second disk)
|-
|rmirrorbal=||load, prefer, round-robin, split||defaults to round-robin if the mirror balance method is not specified
|-
|rbootManager=||none, bsd||whether or not to install the FreeBSD boot manager
|-
|image=||/path/to/image||will write specified image file
|-
|commitDiskPart|| ||this variable is mandatory and must be placed at the end of each diskX= section; create a diskX= section for each disk you wish to configure.
|-
|encpass=||password value||at boot time, system will prompt for this password in order to mount the associated GELI encrypted partition
|-
|commitDiskLabel|| ||this variable is mandatory and must be placed at the end of disk's partitioning settings; see the ''README'' for examples on how to set the <File System Type> <Size> <Mountpoint> entries for each disk
|-
|installMedium=||dvd, local, usb, ftp, rsync, image||source to be used for installation
|-
|localPath=||e.g. usr/freebsd-dist||location of the directory containing the installation files when using installMedium=local
|-
|installType=||PCBSD, FreeBSD||determines whether this is a desktop or a server install
|-
|installFile=||e.g. fbsd-release.tbz||only set if using a customized installer archive
|-
|packageType=||tar, uzip, split, dist||the archive type on the installation media
|-
|ftpPath=||e.g. {{ftp}}ftp.pcbsd.org/pub/mirror/9.1/amd64/netinstall/||location of the installer archive when using installMedium=ftp
|-
|rsyncPath=||e.g. life-preserver/back-2011-09-12T14_53_14||location of the rsync data on the remote server when using installMedium=rsync
|-
|rsyncUser=||username||set when using installMedium=rsync
|-
|rsyncHost=||IP address of rsync server||set when using installMedium=rsync
|-
|rsyncPort=||port number||set when using installMedium=rsync
|-
|installComponents=||e.g. amarok,firefox,ports||components must exist in ''/PCBSD/pc-sysinstall/components/''
|-
|upgradeKeepDesktopProfile=||yes or no||specify if you wish to keep your existing user's desktop profile data during an upgrade
|-
|rootPass=||password||set the root password of the installed system to the specified string
|-
||rootEncPass=||encrypted string||set root password to specified encrypted string
|-
||userName=||case sensitive value||create a separate block of user values for each user you wish to create
|-
||userComment=||description||description text can include spaces
|-
|userPass=||case sensitive value|password of user
|-
|userEncPass||encrypted string||set user password to specified encrypted string
|-
|userShell=||e.g. ''/bin/csh''||path to default shell
|-
|userHome=||e.g. ''/home/username''||path to home directory
|-
|userGroups=||e.g. wheel,operator||comma separated (no spaces) list of groups
|-
|commitUser|| ||mandatory, must be last line in each user block
|-
|content=runCommand=||path to command||run the specified command within chroot of the installed system, after the installation is complete
|-
|runScript=||path to script||runs specified script within chroot of the installed system, after the installation is complete
|-
|runExtCommand=||path to command||runs a command outside the chroot
|-
|timeZone=||e.g. America/New_York||location must exist in ''/usr/share/zoneinfo/''
|-
|enableNTP=||yes or no||enable/disable NTP
|-
|localizeLang=||e.g. en||sets the system console and Desktop to the target language
|-
|localizeKeyLayout=||e.g. en||updates the system's Xorg config to set the keyboard layout
|-
|localizeKeyModel=||e.g. pc104||updates the system's Xorg config to set the keyboard model
|-
|localizeKeyVariant=||e.g. intl||updates the Xorg config to set the keyboard variant
|-
|autoLoginUser=||username||user will be logged in automatically without entering a password
|}

== Create a Customized Configuration == 


One way to create this file is to read through the configuration examples in ''/usr/share/examples/pc-sysinstall/'' to find the one that most closely matches your needs. Copy that file (to any location) and customize it so that it includes the variables and values you would like to use in your installation.


An alternate way to create this file is to perform an installation of the version that you wish to customize. The installer will automatically create a file containing the settings you selected during the installation to ''/root/pc-sysinstall.cfg.'' You can use that configuration file as-is, or customize it to meet an installation's needs. This method may prove easier to use if you are performing complex disk layouts.


Here is a sample configuration:


{{txtbox|box={{pound}} Sample configuration file for an installation using pc-sysinstall


installMode=fresh
installInteractive=no
hostname=myhost.mydomain.com


{{pound}} Set the disk parameters - 1st disk
disk0=da0
partition=all
bootManager=none
commitDiskPart


{{pound}} Set the disk parameters - 2nd disk
disk1=da1
partition=all
bootManager=none
commitDiskPart


{{pound}} Setup the disk label - 1st disk
{{pound}} All sizes are expressed in MB
{{pound}} 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
{{pound}} Size 0 means use the rest of the slice size
{{pound}} Do it now!
commitDiskLabel


{{pound}} Setup the disk label - 2nd disk
{{pound}} All sizes are expressed in MB
{{pound}} 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
{{pound}} Size 0 means use the rest of the slice size>
{{pound}} Do it now!
commitDiskLabel


netDev=em1
netIP=172.16.80.250
netMask=255.255.240.0
netNameServer=172.16.80.1
netDefaultRouter=172.16.80.1
netSaveDev=em0 em1
netSaveIP_em0=192.168.101.42
netSaveIP_em1=172.16.80.156
netSaveMask_em0=255.255.252.0
netSaveMask_em1=255.255.240.0
netSaveNameServer=172.16.80.1
netSaveDefaultRouter=192.168.100.1


{{pound}} Set if we are installing via optical, USB, or FTP
installType=FreeBSD
installMedium=ftp
ftpPath={{http}}pkgbuilder.mydomain.com/images/freebsd/8.2/
packageType=tar


{{pound}} List our components to install
{{pound}}installComponents=ports,src


{{pound}} Set the root pass
rootPass=root


{{pound}} Setup our users
userName=demo
userComment=Demo User
userPass=demo
userShell=/bin/sh
userHome=/home/demo
commitUser


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


{{pound}} 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


{{pound}} Fetch/install VMware Tools
runCommand=fetch -o /tmp/vmtools.tar.gz {{http}}pkgbuilder.mydomain.com/images/freebsd/vmware-freebsd-tools.tar.gz
runCommand=zcat /tmp/vmtools.tar.gz | tar -C /tmp -xvf -
runCommand=/tmp/vmware-tools-distrib/vmware-install.pl -d
runCommand=rm -rf /tmp/vmware-tools-distrib
runCommand=/usr/local/sbin/sysrc puppet_enable=YES
{{pound}} Generate the certificate to be signed by the master
runCommand=/usr/local/bin/puppet agent -t}}


If you wish to perform a fully-automated installation that does not prompt for any user input, you will also need to review ''/usr/share/examples/pc-sysinstall/pc-autoinstall.conf'' and place a customized copy of that file into ''/boot/pc-autoinstall.conf'' on your installation media.


Table 5.5b summarizes the additional variables that are available for fully automatic installations. More detailed descriptions can be found in the ''/usr/share/examples/pc-sysinstall/pc-autoinstall.conf'' file. Note that the variables in this file use a different syntax than those in Table 5.5a, in that the values follow a colon and a space rather than an equal sign.


{{tbl-init|caption=5.5b: Additional Variables for Automated Installations}}
!Variable
!Options
!Description
|-
|pc_config||URL or /path/to/file||location of customized ''pc-sysinstall.conf''
|-
|confirm_install||yes or no||should be set to yes, otherwise booting the wrong disk will result in a system wipe
|-
|shutdown_cmd||e.g. '''shutdown -p now'''||good idea to run a shutdown, but can be any command/script you wish to execute post-install
|-
|nic_config||dhcp-all or <interface name> <IP address> <subnet mask>||will attempt dhcp on all found NICs until the installation file can be fetched or will setup specified interface
|-
|nic_dns||IP address|DNS server to use
|-
|nic_gateway||IP address||default gateway to use
|}


Here is a sample ''pc-autoinstall.conf'' file:


{{txtbox|box={{pound}} pc-autoinstall.conf example
{{pound}}
{{pound}} Usage: Modify these variables, and copy the file to
{{pound}} /boot/pc-autoinstall.conf on your PC-BSD installation medium
{{pound}}
{{pound}} The conf will then be read at bootup, and your automated
{{pound}} install will take place
<nowiki>##################################################################</nowiki>


{{pound}} Where the pc-sysinstall main config is located
{{pound}} Can be either a file on the booted CD / DVD / USB media,
{{pound}} or a remote file on http / ftp
{{pound}}
{{pound}} The value %%NIC_MAC%% is special, and will be substituted with
{{pound}} the macaddress of the enabled NIC from DHCP or manually set
{{pound}} with 'nic_config:'
<nowiki>##################################################################</nowiki>


{{pound}} Examples:
{{pound}} pc_config: {{ftp}}192.168.0.2/cust-install.cfg
{{pound}} pc_config: {{http}}192.168.0.2/cust-install.cfg
{{pound}} pc_config: {{http}}192.168.0.2/%%NIC_MAC%%.cfg
{{pound}} pc_config: /boot/cust-install.cfg
pc_config:
{{http}}pkgbuilder.mydomain.com/images/freebsd/pc-sysinstall.cfg>


{{pound}} Set this to yes if we should confirm before doing an install
{{pound}} This should normally be set to yes, otherwise booting the wrong
{{pound}} disk will result in a system wipe
confirm_install: no


{{pound}} Set the command to run post-install, usually best to run shutdown
{{pound}} but this can be replaced with any other command / script you wish
{{pound}} to execute post-install 
shutdown_cmd: shutdown -r now 


{{pound}} Options for the network setup, should the cfg need to be fetched
{{pound}} from a remote location, only necessary when using ftp or http
<nowiki>##################################################################</nowiki>


{{pound}} Special option, will attempt dhcp on all found NICs
{{pound}} until the file can be fetched, or we run out of interfaces
{{pound}} nic_config: dhcp-all


{{pound}} Line to be passed to the "ifconfig" command to bring up an interface
nic_config: em1 172.16.80.250 255.255.240.0


{{pound}} DNS server to use
nic_dns: 172.16.80.1


{{pound}} Default router / gateway
nic_gateway: 172.16.80.1}}

== Create a Custom Installation Media or Installation Server == 


'''pc-sysinstall''' supports the following installation methods:


* from a CD, DVD, or USB media


* from an installation directory on an HTTP, FTP, SSH+rsync, or a [[Thin_Client#Creating a PXE Boot Install Server|PXE Boot Install]] server


The easiest way to create a custom installation media is to modify an existing installation image. For example, if you have downloaded an ISO for the PC-BSD® version that you wish to customize, the superuser can access the contents of the ISO as follows:


{{txtbox|align=left|box='''mdconfig -a -t vnode -f PCBSD9.0-x86-DVD.iso -u 1'''
'''mount -t cd9660 /dev/md1 /mnt'''}}

Make sure you have changed into a directory (use '''cd''') where you would like to copy the contents of the ISO. In the following examples, ''/tmp/custominstall/'' was created as the directory for this purpose:


{{txtbox|align=left|box='''cd /tmp/custominstall'''
'''tar -C /mnt -cf - . {{!}} tar -xvf -'''
'''umount /mnt'''}}


Alternately, if you have inserted an installation CD or DVD, you can mount the media and copy its contents to your desired directory:


{{txtbox|align=left|box='''mount -t cd9660 /dev/cd0 /mnt'''
'''cp -R /mnt/* /tmp/custominstall/'''
'''umount /mnt'''}}


If you are creating an automated installation, copy your customized ''pc-autoinstall.conf'' to ''/tmp/custominstall/boot/''.


Copy your customized configuration file to ''/tmp/custominstall/''. Double-check that the "installMedium=" variable in your customized configuration file is set to the type of media that you will be installing from.


You may also need to add some extra files if you set the following variables in your custom configuration file:


* '''installComponents=''' make sure that any extra components you wish to install exist in ''extras/PBI/'' (if they end in the ''.pbi'' extension) or ''extras/components/'' (if they end in ''.tbz'')


* '''runCommand=''' make sure the command exists in the specified path


* '''runScript=''' make sure the script exists in the specified path


* '''runExtCommand=''' make sure the command exists in the specified path


If the installation media is a CD or DVD, you will need to create a bootable media that contains the files in your directory. To create a bootable ISO:


{{txtbox|box='''cd /tmp/custominstall
'''mkisofs -V mycustominstall -J -R -b boot/cdboot -no-emul-boot -o myinstall.iso'''}}


You can then use your favorite burning utility to burn the ISO to the media.


To begin an installation that requires user interaction:


'''pc-sysinstall -c /path_to_your_config_file'''


To begin a fully automated installation, insert the installation media and reboot.


If you are using an HTTP, FTP, or SSH server as the installation media, untar or copy the required files to a directory on the server that is accessible to users. Be sure to configure the server so that the installation files are accessible to the systems that you wish to install. If you are using a PXE Boot Install server, follow the instructions at [[Thin_Client#Connecting_to_and_Customizing_the_PXE_Boot_Install_Server|Connecting to and Customizing the PXE Boot Install Server]].


<noinclude>

{{GroupListHeading|group=tables}}
[[category:Creating an Automated Installation with pc-sysinstall]]
[[category:Advanced Installation Topics]]
[[category:handbook]]
</translate>
<languages/>
</noinclude>

Template:Txtbox

2013-04-30T08:25:14Z

Tigersharke:

<includeonly><div class="txtbox{{#if: {{{align|}}}|-{{{align}}}" style="{{#if: {{{margin-left|}}}|margin-left:{{{margin-left}}};|}} {{#if: {{{margin-right|}}}|margin-right:{{{margin-right}}};|}} {{#if: {{{margin-top|}}}|margin-top:{{{margin-top}}};|}} {{#if: {{{margin-bottom|}}}|margin-bottom:{{{margin-bottom}}};|}}" ><div class="txtbox-box" style="{{#if: {{{width|}}}|width:{{{width}}};|}} {{white-space|{{{1|}}}}} {{{overrides|}}}">{{{box|where is your box?}}}</div>
{{#if: {{{txt|}}}|<div class="txtbox-txt" style="text-align:{{{txt-text-align|left}}}; {{{txt-padding-left|5px}}};">{{{txt|}}}</div>|}}</div>[[category:Uses Txtbox]]</includeonly><noinclude>
== Explanation ==
This template encloses the provided text within a dashed line box. The text to the right of the box may be some type of comment such as ''"a prompt asking for the root password will open."''. The effect will be shrink to fit but the width (depending upon wrap style) of the box can be adjusted if necessary. Note the <nowiki><nowiki></nowiki> 'prefixed with a space' formatting trick should be avoided. Other style markup like for ''italic'' or '''bold''' should be placed directly around the specific content and not around the entire template. Individual {{pound}} symbols should be replaced with <nowiki>{{pound}}</nowiki> and a series of pound symbols may be enclosed within nowiki tags or they will be parsed as numbered list elements.
=== Wrap Control ===
{{tbl-init|class=simple_table|caption=Wrap Options}}
!our code!!actual CSS!!Explanation
|-
|'''pre''' || White-space: pre; || '''default''': acts like 'pre' whitespace preserved, text wraps at box border and line breaks.
|-
|'''wrap''' || White-space: pre-wrap; || whitespace preserved, text wraps at box border and line breaks. Good for very long commands.
|-
|'''wiki''' || White-space: nowrap; || is this the brain damaged method the magic (prefix w/space) wiki text boxes use??
|-
|'''collapse''' || White-space: pre-line; || multiple white space collapses, text wraps at box border and line breaks.
|-
|'''code''' || White-space: pre; || easier to remember effect name.
|-
|'''normal''' || White-space: normal; || multiple white space collapses, text wraps at box border.
|-
|'''override''' || White-space: pre; || use for simple 'pre' style formatting
|}

{{note| there is some weirdness with unintended blank lines at the bottom. For some situations this can be fixed by using one long line that includes a <nowiki> </nowiki> to assist formatting. The default is reasonable for most situations but would require the fix to avoid the extra unneeded space/lines.}}

== Usage ==

'''<nowiki>{{</nowiki>txtbox|''width='''value'''''|box='''''content such as parens containing 5({{nbsp|5}}) spaces preserved,'' 
<nowiki>'''</nowiki>''second line'' - <nowiki>{{</nowiki>highlight|note that bold and italic and highlight/redlight<nowiki>}}'''</nowiki> 
'''|txt='''''Text to right of box''<nowiki> </nowiki><nowiki>''</nowiki>''second line<nowiki>''</nowiki> - <nowiki>{{</nowiki>redlight|are possible too.<nowiki>}}</nowiki>'''''}}'''

=== Result ===

{{txtbox|box=content such as parens containing 5( ) spaces preserved,
'''second line''' - {{highlight|note that bold and italic and highlight/redlight}}|txt=Text to right of box
''second line'' - {{redlight|are possible too.}}}}</noinclude><noinclude>
{{GroupListHeading|group=tables}}
[[category:templates]]
</noinclude>

MediaWiki:Common.css

2013-04-30T08:21:51Z

Tigersharke:

/* CSS placed here will be applied to all skins */

/**************************************************************************/
/* Here is the Spiffy Table which allows for nice colors, bold titles and */
/* alternating white/grey rows. It does not display entirely well when a */
/* rowspan=x is defined. This is used by template tbl-init or can be used */
/* alone by specifying class=spiffy_table. A plain table without any */
/* background color but otherwise similar format may be used by adding */
/* class=simple_table. */
/**************************************************************************/

table.spiffy_table, table.simple_table {
border: 2px solid rgb(186, 186, 186);
border-collapse: collapse;
}

.spiffy_table tr:nth-child(odd) > td {
background-color:#EEEEEE;
}

.spiffy_table tr:nth-child(even) > td {
background-color:#FFFFFF;
}

.spiffy_table th {
background-color:#FFFFD9;
border-color: #BABFA3;
border-style: solid;
border-width: 0 1px 2px 1px;
font-weight: bold;
padding: 5px;
text-align: center;
}

.simple_table th {
border-color: #BABFA3;
border-style: solid;
border-width: 0 1px 2px 1px;
font-weight: bold;
padding: 5px;
text-align: center;
}

.spiffy_table caption, .simple_table caption {
font-weight: bold;
text-align: left;
}

.spiffy_table td, .simple_table td {
padding: 5px;
border-style: solid;
border-color:#BABFA3;
border-width: 1px 1px 1px 1px;
}

/**************************************************************************/
/* This prevents the wiki from insisting upon using on titles */
/* from table captions above. Not even adding a separate class to wrap */
/* around the citelink type references via span tags worked. */
/**************************************************************************/

.GroupListItem, .selflink {
font-weight: normal;
font-style: normal;
}

/**************************************************************************/
/* Various style adjustments for different kinds or levels of emphasis. */
/* Each class is named for the template that uses it. */
/**************************************************************************/

.redtxt {
color:rgb(255,0,0);
}

.highlight {
background: yellow;
color: #000000;
}

.orangelight {
background: #8B5A00;
color: #FFFFFF;
}

.redlight {
background: crimson;
color: #FFFFFF;
}

.smalltext {
font-size:small;
}

.strike {
text-decoration:line-through;
}

/**************************************************************************/
/* This is the txtbox style adjustments. */
/* Each class is named for the template that uses it. */
/**************************************************************************/

.txtbox {
align: center;
}

.txtbox-right {
align: center;
clear: right;
}

.txtbox-left {
align: center;
clear: left;
}

.txtbox-box {
font-family: Courier New, Courier, monospace;
border: #aaaaaa dashed 1px;
background: #f6f6f6;
text-align:left;
float:left;
position:relative;
margin-right: 6px;
margin-bottom: 12px;
margin-top: 12px;
width:auto;
padding:5px 5px 5px 5px;
}

.txtbox-txt {
float:left;
position:relative;
margin-left: 6px;
margin-right: 12px;
margin-bottom: 12px;
margin-top: 12px;
width:auto;
padding:5px 5px 5px 5px;
}

MediaWiki:Common.css

2013-04-30T08:21:06Z

Tigersharke:

/* CSS placed here will be applied to all skins */

/**************************************************************************/
/* Here is the Spiffy Table which allows for nice colors, bold titles and */
/* alternating white/grey rows. It does not display entirely well when a */
/* rowspan=x is defined. This is used by template tbl-init or can be used */
/* alone by specifying class=spiffy_table. A plain table without any */
/* background color but otherwise similar format may be used by adding */
/* class=simple_table. */
/**************************************************************************/

table.spiffy_table, table.simple_table {
border: 2px solid rgb(186, 186, 186);
border-collapse: collapse;
}

.spiffy_table tr:nth-child(odd) > td {
background-color:#EEEEEE;
}

.spiffy_table tr:nth-child(even) > td {
background-color:#FFFFFF;
}

.spiffy_table th {
background-color:#FFFFD9;
border-color: #BABFA3;
border-style: solid;
border-width: 0 1px 2px 1px;
font-weight: bold;
padding: 5px;
text-align: center;
}

.simple_table th {
border-color: #BABFA3;
border-style: solid;
border-width: 0 1px 2px 1px;
font-weight: bold;
padding: 5px;
text-align: center;
}

.spiffy_table caption, .simple_table caption {
font-weight: bold;
text-align: left;
}

.spiffy_table td, .simple_table td {
padding: 5px;
border-style: solid;
border-color:#BABFA3;
border-width: 1px 1px 1px 1px;
}

/**************************************************************************/
/* This prevents the wiki from insisting upon using on titles */
/* from table captions above. Not even adding a separate class to wrap */
/* around the citelink type references via span tags worked. */
/**************************************************************************/

.GroupListItem, .selflink {
font-weight: normal;
font-style: normal;
}

/**************************************************************************/
/* Various style adjustments for different kinds or levels of emphasis. */
/* Each class is named for the template that uses it. */
/**************************************************************************/

.redtxt {
color:rgb(255,0,0);
}

.highlight {
background: yellow;
color: #000000;
}

.orangelight {
background: #8B5A00;
color: #FFFFFF;
}

.redlight {
background: crimson;
color: #FFFFFF;
}

.smalltext {
font-size:small;
}

.strike {
text-decoration:line-through;
}

/**************************************************************************/
/* This is the txtbox style adjustments. */
/* Each class is named for the template that uses it. */
/**************************************************************************/

.txtbox {
align: center;
}

.txtbox-right {
align: center;
clear: right;
}

.txtbox-left {
align: center;
clear: left;
}

.txtbox-box {
font-family: Courier New, Courier, monospace;
border: #aaaaaa dashed 1px;
background: #f6f6f6;
text-align:left;
float:left;
position:relative;
margin-right: 6px;
margin-bottom: 12px;
margin-top: 12px;
width:auto;
padding:5px 5px 5px 5px;
}

.txtbox-txt {
border: #aaaaaa dashed 1px;
float:left;
position:relative;
margin-left: 6px;
margin-right: 12px;
margin-bottom: 12px;
margin-top: 12px;
width:auto;
padding:5px 5px 5px 5px;
}