FreeBSDwiki - User contributions [en]

FreeBSD ISO layout

2007-11-04T16:15:32Z

Ice: vnconfig(8) has been discontinued -> mdconfig(8)

==Sample ISO layout of 6.2-RELEASE i386==

The directory <tt>ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/6.2</tt> lists the following contents:
<pre>
6.2-RELEASE-i386-bootonly.iso 24848 KB 01/12/2007 12:00:00 AM
6.2-RELEASE-i386-disc1.iso 587138 KB 01/12/2007 12:00:00 AM
6.2-RELEASE-i386-disc2.iso 654402 KB 01/12/2007 12:00:00 AM
6.2-RELEASE-i386-docs.iso 192414 KB 01/12/2007 12:00:00 AM
CHECKSUM.MD5 1 KB 01/12/2007 12:00:00 AM
CHECKSUM.SHA256 1 KB 01/12/2007 12:00:00 AM
</pre>

The file <tt>CHECKSUM.MD5</tt> contains the following text:
<pre>
MD5 (6.2-RELEASE-i386-bootonly.iso) = 4e8701ac951bc4537f8420fdac7efbb5
MD5 (6.2-RELEASE-i386-disc1.iso) = 3d27214700687c0b5390e8b6dd3706e3
MD5 (6.2-RELEASE-i386-disc2.iso) = fd30bfc65ef8adaa67aeffd07c72bf21
MD5 (6.2-RELEASE-i386-docs.iso) = e3512834982a9beebc3670499c7f3817
</pre>

The four ISO images were downloaded to an OpenBSD host (from various mirrors) and the signatures were verified using the OpenBSD <tt>md5</tt> command. For some other systems the command is <tt>md5sum</tt> instead.

The four ISO images were then loopback mounted using svnd devices as follows:
<pre>
mkdir boot disc1 disc2 docs

sudo mdconfig -a -t vnode -f 6.2-RELEASE-i386-bootonly.iso
sudo mount -t cd9660 /dev/md0 boot

sudo mdconfig -a -t vnode -f 6.2-RELEASE-i386-disc1.iso
sudo mount -t cd9660 /dev/md1 disc1

sudo mdconfig -a -t vnode -f 6.2-RELEASE-i386-disc2.iso
sudo mount -t cd9660 /dev/md2 disc2

sudo mdconfig -a -t vnode -f 6.2-RELEASE-i386-docs.iso
sudo mount -t cd9660 /dev/md3 docs
</pre>

After mounting the four images as above, the top-level structure of the ISO images was listed out with the command:
find . -maxdepth 4 -type d
which produces the following output:
<pre>
./boot
./boot/boot
./boot/boot/defaults
./boot/boot/kernel
./boot/boot/modules
./disc1
./disc1/6.2-RELEASE
./disc1/6.2-RELEASE/base
./disc1/6.2-RELEASE/catpages
./disc1/6.2-RELEASE/dict
./disc1/6.2-RELEASE/doc
./disc1/6.2-RELEASE/games
./disc1/6.2-RELEASE/info
./disc1/6.2-RELEASE/kernels
./disc1/6.2-RELEASE/manpages
./disc1/6.2-RELEASE/ports
./disc1/6.2-RELEASE/proflibs
./disc1/6.2-RELEASE/src
./disc1/bin
./disc1/boot
./disc1/boot/defaults
./disc1/boot/kernel
./disc1/boot/modules
./disc1/dev
./disc1/etc
./disc1/etc/bluetooth
./disc1/etc/defaults
./disc1/etc/gnats
./disc1/etc/isdn
./disc1/etc/mail
./disc1/etc/mtree
./disc1/etc/ntp
./disc1/etc/pam.d
./disc1/etc/periodic
./disc1/etc/periodic/daily
./disc1/etc/periodic/monthly
./disc1/etc/periodic/security
./disc1/etc/periodic/weekly
./disc1/etc/ppp
./disc1/etc/rc.d
./disc1/etc/security
./disc1/etc/skel
./disc1/etc/ssh
./disc1/etc/ssl
./disc1/etc/X11
./disc1/floppies
./disc1/lib
./disc1/lib/geom
./disc1/libexec
./disc1/media
./disc1/mnt
./disc1/packages
./disc1/packages/All
./disc1/packages/devel
./disc1/packages/emulators
./disc1/packages/graphics
./disc1/packages/lang
./disc1/packages/linux
./disc1/packages/perl5
./disc1/packages/print
./disc1/packages/textproc
./disc1/packages/x11
./disc1/packages/x11-fonts
./disc1/packages/x11-servers
./disc1/proc
./disc1/rescue
./disc1/root
./disc1/sbin
./disc1/tmp
./disc1/tools
./disc1/tools/bsdboot
./disc1/tools/dist
./disc1/tools/srcs
./disc1/tools/srcs/bteasy
./disc1/tools/srcs/EXTIPL
./disc1/tools/srcs/fips
./disc1/tools/srcs/ide_conf
./disc1/tools/srcs/pfdisk
./disc1/tools/srcs/rawrite
./disc1/usr
./disc1/usr/bin
./disc1/usr/games
./disc1/usr/include
./disc1/usr/include/altq
./disc1/usr/include/arpa
./disc1/usr/include/bsm
./disc1/usr/include/bsnmp
./disc1/usr/include/cam
./disc1/usr/include/crypto
./disc1/usr/include/c++
./disc1/usr/include/dev
./disc1/usr/include/fs
./disc1/usr/include/geom
./disc1/usr/include/gnu
./disc1/usr/include/gpib
./disc1/usr/include/isofs
./disc1/usr/include/kadm5
./disc1/usr/include/libmilter
./disc1/usr/include/lwres
./disc1/usr/include/machine
./disc1/usr/include/net
./disc1/usr/include/net80211
./disc1/usr/include/netatalk
./disc1/usr/include/netatm
./disc1/usr/include/netgraph
./disc1/usr/include/netinet
./disc1/usr/include/netinet6
./disc1/usr/include/netipsec
./disc1/usr/include/netipx
./disc1/usr/include/netkey
./disc1/usr/include/netnatm
./disc1/usr/include/netncp
./disc1/usr/include/netsmb
./disc1/usr/include/nfs
./disc1/usr/include/nfsclient
./disc1/usr/include/nfsserver
./disc1/usr/include/objc
./disc1/usr/include/openssl
./disc1/usr/include/pccard
./disc1/usr/include/posix4
./disc1/usr/include/protocols
./disc1/usr/include/readline
./disc1/usr/include/rpc
./disc1/usr/include/rpcsvc
./disc1/usr/include/security
./disc1/usr/include/sys
./disc1/usr/include/ufs
./disc1/usr/include/vm
./disc1/usr/lib
./disc1/usr/lib/aout
./disc1/usr/lib/compat
./disc1/usr/libdata
./disc1/usr/libdata/gcc
./disc1/usr/libdata/ldscripts
./disc1/usr/libdata/lint
./disc1/usr/libexec
./disc1/usr/libexec/lpr
./disc1/usr/libexec/sendmail
./disc1/usr/libexec/sm.bin
./disc1/usr/local
./disc1/usr/obj
./disc1/usr/sbin
./disc1/usr/share
./disc1/usr/share/calendar
./disc1/usr/share/dict
./disc1/usr/share/doc
./disc1/usr/share/examples
./disc1/usr/share/games
./disc1/usr/share/groff_font
./disc1/usr/share/info
./disc1/usr/share/isdn
./disc1/usr/share/locale
./disc1/usr/share/man
./disc1/usr/share/me
./disc1/usr/share/misc
./disc1/usr/share/mk
./disc1/usr/share/nls
./disc1/usr/share/openssl
./disc1/usr/share/pcvt
./disc1/usr/share/security
./disc1/usr/share/sendmail
./disc1/usr/share/skel
./disc1/usr/share/snmp
./disc1/usr/share/syscons
./disc1/usr/share/tabset
./disc1/usr/share/tmac
./disc1/usr/share/vi
./disc1/usr/share/zoneinfo
./disc1/usr/src
./disc1/var
./disc1/var/account
./disc1/var/at
./disc1/var/at/jobs
./disc1/var/at/spool
./disc1/var/audit
./disc1/var/backups
./disc1/var/crash
./disc1/var/cron
./disc1/var/cron/tabs
./disc1/var/db
./disc1/var/db/entropy
./disc1/var/db/freebsd-update
./disc1/var/db/ipf
./disc1/var/db/pkg
./disc1/var/db/ports
./disc1/var/db/portsnap
./disc1/var/empty
./disc1/var/heimdal
./disc1/var/log
./disc1/var/mail
./disc1/var/msgs
./disc1/var/named
./disc1/var/named/dev
./disc1/var/named/etc
./disc1/var/named/var
./disc1/var/preserve
./disc1/var/run
./disc1/var/run/named
./disc1/var/run/ppp
./disc1/var/rwho
./disc1/var/spool
./disc1/var/spool/clientmqueue
./disc1/var/spool/lock
./disc1/var/spool/lpd
./disc1/var/spool/mqueue
./disc1/var/spool/opielocks
./disc1/var/spool/output
./disc1/var/tmp
./disc1/var/tmp/vi.recover
./disc1/var/yp
./disc2
./disc2/packages
./disc2/packages/accessibility
./disc2/packages/afterstep
./disc2/packages/All
./disc2/packages/archivers
./disc2/packages/astro
./disc2/packages/audio
./disc2/packages/comms
./disc2/packages/converters
./disc2/packages/databases
./disc2/packages/deskutils
./disc2/packages/devel
./disc2/packages/dns
./disc2/packages/editors
./disc2/packages/emulators
./disc2/packages/ftp
./disc2/packages/games
./disc2/packages/gnome
./disc2/packages/graphics
./disc2/packages/ipv6
./disc2/packages/irc
./disc2/packages/kde
./disc2/packages/lang
./disc2/packages/mail
./disc2/packages/math
./disc2/packages/misc
./disc2/packages/multimedia
./disc2/packages/net
./disc2/packages/net-mgmt
./disc2/packages/news
./disc2/packages/palm
./disc2/packages/perl5
./disc2/packages/print
./disc2/packages/python
./disc2/packages/ruby
./disc2/packages/scheme
./disc2/packages/security
./disc2/packages/shells
./disc2/packages/sysutils
./disc2/packages/textproc
./disc2/packages/windowmaker
./disc2/packages/www
./disc2/packages/x11
./disc2/packages/x11-clocks
./disc2/packages/x11-fm
./disc2/packages/x11-fonts
./disc2/packages/x11-themes
./disc2/packages/x11-toolkits
./disc2/packages/x11-wm
./docs
./docs/rr_moved
./docs/usr
./docs/usr/share
./docs/usr/share/doc
</pre>

The mounted size, as reported by <tt>du -shPx</tt> differs from the ISO image size:
<pre>
23.3M boot
997M disc1
638M disc2
177M docs
</pre>

Whereas the ISO file sizes are:
<pre>
6.2-RELEASE-i386-bootonly.iso 24,848 KB
6.2-RELEASE-i386-disc1.iso 587,138 KB
6.2-RELEASE-i386-disc2.iso 654,402 KB
6.2-RELEASE-i386-docs.iso 192,414 KB
</pre>

For a mirror combining the contents of disc1 and disc2, about 1.6 GB of storage would be consumed.

==FreeBSD ftp mirror layout==

For comparison, the file ftp://ftp.freebsd.org/pub/FreeBSD/dir.sizes shows the layout of a typical FreeBSD mirror, presumably giving the file sizes in multiples of KiB. The total size of the mirror for all architectures appears to be 440GB. The FreeBSD mirror documentation at [http://www.freebsd.org/doc/en_US.ISO8859-1/articles/hubs/mirror-requirements.html Requirements for FreeBSD mirrors] states that a ''Full FTP Distribution'' occupies 412 GB. Mirroring the whole of the ftp distribution is not practical for a local mirror.

==See also==

* [http://www.freebsd.org/doc/en_US.ISO8859-1/articles/hubs/index.html Mirroring FreeBSD] -- from freebsd.org
* [http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/article.html FreeBSD Release Engineering] -- also from freebsd.org

[[category:installation]]

Talk:SSH, limiting to SCP or Rsync only

2007-11-04T10:06:03Z

Ice: /* Security aspect */

==just btw==
# gcc scpsftprsynconly.c -o /usr/local/bin/scpsftprsynconly
scpsftprsynconly.c: In function â€˜mainâ€™:
scpsftprsynconly.c:48: error: expected â€˜)â€™ at end of input
scpsftprsynconly.c:48: error: expected declaration or statement at end of input
#

tried running this on a centos box and this is what I'm getting. dubl-U Tee Eff Mmm8.

--[[User:Dave|Dave]] 12:25, 22 October 2007 (EDT)

== just guessing, really ==

since I don't know shit, but I added a } before the #ifdef DEBUG section and now I'm getting:

[root@web ~]# gcc scpsftprsynconly.c -o /usr/local/bin/scpsftprsynconly
scpsftprsynconly.c:45: error: expected identifier or â€˜(â€™ before â€˜ifâ€™
scpsftprsynconly.c:49: error: expected identifier or â€˜(â€™ before â€˜ifâ€™
[root@web ~]#

which is in the first lines of
if (argc < 3) {
printf (restrictmsg);
return 1;
}
if ((strncmp (argv [2], "scp ", 4) != 0)

wha?

--[[User:Dave|Dave]] 13:41, 22 October 2007 (EDT)

== somebody oopsed on a kill-the-spam edit ==

The problem you were having was that a good samaritan who manually edited the article to remove spam accidentally damaged the code a while back. I looked through history on the article and reverted to prior to the damage. --[[User:Jimbo|Jimbo]] 15:20, 22 October 2007 (EDT)

== Security aspect ==
You should probably not rely on scpftprsynconly to PREVENT users from executing programs on your machine,
./scpsftprsynconly foo 'scp -S givemeshell asd asd:asd'
Will execute the givemeshell command with some obscure arguments. To get a shell with this inplace, upload a script/program that reverse connect or what you want then just:
ssh foo@barhost "scp -S echo asd asd:asd"

Probably should mention this in the article..

--[[User:Ice|Ice]] 04:51, 4 November 2007 (EST)

Talk:SSH, limiting to SCP or Rsync only

2007-11-04T09:51:42Z

Ice: security concern with scpftprsynconly

==just btw==
# gcc scpsftprsynconly.c -o /usr/local/bin/scpsftprsynconly
scpsftprsynconly.c: In function â€˜mainâ€™:
scpsftprsynconly.c:48: error: expected â€˜)â€™ at end of input
scpsftprsynconly.c:48: error: expected declaration or statement at end of input
#

tried running this on a centos box and this is what I'm getting. dubl-U Tee Eff Mmm8.

--[[User:Dave|Dave]] 12:25, 22 October 2007 (EDT)

== just guessing, really ==

since I don't know shit, but I added a } before the #ifdef DEBUG section and now I'm getting:

[root@web ~]# gcc scpsftprsynconly.c -o /usr/local/bin/scpsftprsynconly
scpsftprsynconly.c:45: error: expected identifier or â€˜(â€™ before â€˜ifâ€™
scpsftprsynconly.c:49: error: expected identifier or â€˜(â€™ before â€˜ifâ€™
[root@web ~]#

which is in the first lines of
if (argc < 3) {
printf (restrictmsg);
return 1;
}
if ((strncmp (argv [2], "scp ", 4) != 0)

wha?

--[[User:Dave|Dave]] 13:41, 22 October 2007 (EDT)

== somebody oopsed on a kill-the-spam edit ==

The problem you were having was that a good samaritan who manually edited the article to remove spam accidentally damaged the code a while back. I looked through history on the article and reverted to prior to the damage. --[[User:Jimbo|Jimbo]] 15:20, 22 October 2007 (EDT)

== Security aspect ==
You should probably not rely on scpftprsynconly to PREVENT users from executing programs on your machine,
./scpsftprsynconly foo 'scp -S givemeshell asd asd:asd'
Will execute the givemeshell command with some obscure arguments. I haven't tried it with scpftprsynconly installed as a shell but it should be as easy as
ssh foohost 'scp -S givemeshell'.

Probably should mention this in the article..

--[[User:Ice|Ice]] 04:51, 4 November 2007 (EST)

Installing FreeBSD with netboot

2007-11-04T09:31:17Z

Ice: added the nfs part to make it more complete..

== FreeBSD bootonly ==
The first step to installing FreeBSD via netboot is to acquire FreeBSD. We'll be using the bootonly-iso, this can be fetched at your nearest ftp.

Download the bootonly-iso:
fetch ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/6.2/6.2-RELEASE-i386-bootonly.iso
Mount the iso-image and copy the contents to some location:
mdconfig -a -t vnode -f 6.2-RELEASE-i386-bootonly.iso
mount_cd9660 /dev/md0 /mnt/cdrom
mkdir /usr/local/pxeboot
cp -r /mnt/cdrom /usr/local/pxeboot
umount /mnt/cdrom

The main reason for copying the cd is to edit the file /boot/loader.conf adding the following line:
echo 'vfs.root.mountfrom="ufs:/dev/md0c"' >> /usr/local/pxeboot/boot/loader.conf
This will cause the lovable FreeBSD sysinstall to start. The pxeboot will mount the rootfs from the file mfsroot.gz instead of the default of mounting a NFS-root.

== NIC with PXE boot ==
For the pxeboot to work you might have to update your NIC with new firmware. See your manufacturer homepage for more information.

== TFTP ==
Next up is starting a tftp-server from which the firmware can load the [http://en.wikipedia.org/wiki/Preboot_Execution_Environment#Network_Bootstrap_Program network bootstrap program] from. This is easiest done by using inetd, remove the leading # from the following line in the file /etc/inetd.conf.
#tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /tftpboot

Make the tftpboot directory and copy the boot/pxeboot file to it.
mkdir /tftpboot
cp /usr/local/pxeboot/boot/pxeboot /tftpboot/

Then start inetd by adding it to rc.conf and starting it.
echo 'inetd_enable="YES"' >> /etc/rc.conf
/etc/rc.d/inetd start

It can be a good idea to start a tail of messages and xferlog file to see what is happening. In another terminal run:
tail -f /var/log/messages /var/log/xferlog

== DHCP ==
Now it's time for the DHCP-server that the firmware will query to get address and path to the network bootstrap program.

Install isc-dhcp3-server
pkg_add -r isc-dhcp3-server

Edit /usr/local/etc/dhcpd.conf adding the following lines.
server-name "pxe-gw"; # name of the tftp-server
server-identifier 172.24.0.4; # address of the tftp-server
next-server 172.24.0.4; # address of the NFS-server

subnet 172.24.0.0 netmask 255.255.255.0 {
range 172.24.0.137 172.24.0.253;
option routers 172.24.0.1;
option root-path "/usr/local/pxeboot"; # root-path for NFS
filename "pxeboot"; # filename of NBP (network bootstrap program)
}

== NFS ==

[[Category : Installation]]
Add the pxeboot directory to nfs exports file
echo '/usr/local/pxeboot -alldirs -maproot=root -ro' >> /etc/exports

Enable NFS in rc.conf
echo 'nfs_server_enable="YES"' >> /etc/rc.conf
Start nfsd
/etc/rc.d/nfsd start

Reboot your computer and select PXE-boot you should now enter sysinstall, have a nice day!

== See also ==
* [http://gja.space4me.com/things/Using_pxeboot_Install53.html Using pxeboot to install FreeBSD 5.3]
* [http://people.freebsd.org/~dwhite/pxeboot.html Quick and Dirty PXE Boot Setup for FreeBSD 4.x and later]

Unicode

2007-09-27T15:29:08Z

Ice: /* xterm */

== Unicode ==
The simplest form of character set used on computers uses an 8-bit (one byte) numerical value to represent a letter from the English and Latin alphabets and certain accented characters (normally seen in French writing). This system is called [http://en.wikipedia.org/wiki/ASCII ASCII], the American Standard Code for Information Interchange. Almost all modern day operating systems use it as well as many older computer systems.

Unicode, in particular the UTF-8 standard, takes this concept of a numerical value representing a character and extends it to host the alphabets of (virtually) all the known languages in the world. This is around 100,000 characters and as such UTF-8 can use 1-, 2-, 3- and even 4-byte values to represent them:

* the 1-byte character set is used to cover the simple English alphabet;
* the 2-byte character set is used to cover the more common alphabets, including Arabic, Armenian, Cyrillic, Greek, Hebrew, Latin, and Syriac;
* the 3-byte character set is used to cover additional language alphabets;
* the 4-byte character set is used to cover additional, but rarer, language alphabets, as such it is not used often.

In addition to the character sets used the standard also defines "handedness", as in which way the text flows. Typically Western languages are written left-to-right (as per the text on this page) while other, typically middle-Eastern languages, write from right-to-left.

While ASCII uses one character-per-byte and so a 100 letter document would be (theoretically) 100 bytes on disk a Unicode document could be 2, 3 or 4 times that size, depending on the encoding used. The Unicode standard is backwards compatible with ASCII when used in 1-byte character set.

There is another character set typically found on older mainframes, most notably from IBM, called EBCDIC, the Extended Binary-Coded Decimal Interchange Code. There is a variation called [http://en.wikipedia.org/wiki/UTF-EBCDIC UTF-EBCDIC] to enable legacy applications running on these systems to utilise Unicode.

== Using UTF-8 in FreeBSD ==
First we need to set the LC_ALL and LANG variables, find out which locales can support UTF-8.
$ cd /usr/share/locale/; ls *UTF-8 -d

Add the following environment variable to the appropriate file, ~/.profile or ~/.login or ~/.bashrc.
export LC_ALL=sv_SE.UTF-8

Now login and logout to have the effects apply.
After that you should enable UTF-8 support in your terminal, see the application section for this.

=== Converting files ===
Now you're ready to convert some files, this is done with the command iconv, install it if you don't already have it.
# pkg_add -r libiconv

Then use the following to convert a file.
$ iconv -f iso8859-1 -t utf-8 file > file.new

This is a small script that converts a bunch of files and creates a backup of them in another directory.

== Applications ==
=== xterm ===
To make xterm play nice I added
$ echo "xterm*locale: UTF-8" >> ~/.Xdefaults

It could also be necessary to change the font see Unicode support on FreeBSD.

=== irssi + screen ===
Unfortunately I haven't found any way to get irssi+screen+FiSH to work with out a restart of irssi.
So restart screen with the new locales, this config will enable you to send ISO8859-1 by default in irssi.

/set term_charset UTF-8
/set recode_out_default_charset ISO8859-1
/set recode yes
/set recode_autodetect_utf8 no
/set recode_fallback ISO8859-1
/set recode_transliterate no
/recode add #utf8channel UTF-8

For use with FiSH (an IRC encryption module [http://fish.sekure.us/]) some more adjustment are needed.
Read instructions an apply patches from [http://iiice.net/~ice/programs/FiSH/ http://iiice.net/~ice/programs/FiSH/]

== External Links ==
* [http://opal.com/freebsd/unicode.html Unicode support on FreeBSD]

Unicode

2007-09-27T15:16:47Z

Ice:

== Unicode ==
The simplest form of character set used on computers uses an 8-bit (one byte) numerical value to represent a letter from the English and Latin alphabets and certain accented characters (normally seen in French writing). This system is called [http://en.wikipedia.org/wiki/ASCII ASCII], the American Standard Code for Information Interchange. Almost all modern day operating systems use it as well as many older computer systems.

Unicode, in particular the UTF-8 standard, takes this concept of a numerical value representing a character and extends it to host the alphabets of (virtually) all the known languages in the world. This is around 100,000 characters and as such UTF-8 can use 1-, 2-, 3- and even 4-byte values to represent them:

* the 1-byte character set is used to cover the simple English alphabet;
* the 2-byte character set is used to cover the more common alphabets, including Arabic, Armenian, Cyrillic, Greek, Hebrew, Latin, and Syriac;
* the 3-byte character set is used to cover additional language alphabets;
* the 4-byte character set is used to cover additional, but rarer, language alphabets, as such it is not used often.

In addition to the character sets used the standard also defines "handedness", as in which way the text flows. Typically Western languages are written left-to-right (as per the text on this page) while other, typically middle-Eastern languages, write from right-to-left.

While ASCII uses one character-per-byte and so a 100 letter document would be (theoretically) 100 bytes on disk a Unicode document could be 2, 3 or 4 times that size, depending on the encoding used. The Unicode standard is backwards compatible with ASCII when used in 1-byte character set.

There is another character set typically found on older mainframes, most notably from IBM, called EBCDIC, the Extended Binary-Coded Decimal Interchange Code. There is a variation called [http://en.wikipedia.org/wiki/UTF-EBCDIC UTF-EBCDIC] to enable legacy applications running on these systems to utilise Unicode.

== Using UTF-8 in FreeBSD ==
First we need to set the LC_ALL and LANG variables, find out which locales can support UTF-8.
$ cd /usr/share/locale/; ls *UTF-8 -d

Add the following environment variable to the appropriate file, ~/.profile or ~/.login or ~/.bashrc.
export LC_ALL=sv_SE.UTF-8

Now login and logout to have the effects apply.
After that you should enable UTF-8 support in your terminal, see the application section for this.

=== Converting files ===
Now you're ready to convert some files, this is done with the command iconv, install it if you don't already have it.
# pkg_add -r libiconv

Then use the following to convert a file.
$ iconv -f iso8859-1 -t utf-8 file > file.new

This is a small script that converts a bunch of files and creates a backup of them in another directory.

== Applications ==
=== xterm ===
To make xterm play nice i added
$ echo "xterm*locale: UTF-8" >> ~/.Xdefaults

=== irssi + screen ===
Unfortunately I haven't found any way to get irssi+screen+FiSH to work with out a restart of irssi.
So restart screen with the new locales, this config will enable you to send ISO8859-1 by default in irssi.

/set term_charset UTF-8
/set recode_out_default_charset ISO8859-1
/set recode yes
/set recode_autodetect_utf8 no
/set recode_fallback ISO8859-1
/set recode_transliterate no
/recode add #utf8channel UTF-8

For use with FiSH (an IRC encryption module [http://fish.sekure.us/]) some more adjustment are needed.
Read instructions an apply patches from [http://iiice.net/~ice/programs/FiSH/ http://iiice.net/~ice/programs/FiSH/]

== External Links ==
* [http://opal.com/freebsd/unicode.html Unicode support on FreeBSD]

Unicode

2007-09-27T13:56:28Z

Ice: working on irssi unicode + fish

== Unicode ==
Descriptive text what unicode / utf-8 is.

== Using UTF-8 in FreeBSD ==
First we need to set the LC_ALL and LANG variables, find out which locales can support UTF-8.
cd /usr/share/locale/; ls *UTF-8 -d

Add the following environment variables to the appropriate file, ~/.profile or ~/.login or ~/.bashrc.
export LANG=sv_SE.UTF-8
export LC_ALL=sv_SE.UTF-8

Now login and logout to have the effects apply.

== Applications ==
=== xterm ===
To make xterm play nice i added
echo "xterm*locale: UTF-8" >> ~/.Xdefaults

=== irssi + screen ===
If you're like me and don't want to restart your irssi you use the following line, otherwise screen should use the locales.
Ctrl-a : (colon) then write 'encoding UTF-8 UTF-8'

This config will enable you to send ISO8859-1 by default in irssi.
/set term_charset UTF-8
/set recode_out_default_charset ISO8859-1
/set recode yes
/set recode_autodetect_utf8 no
/set recode_fallback ISO8859-1
/set recode_transliterate no
/recode add #utf8channel UTF-8

== External Links ==
* [http://opal.com/freebsd/unicode.html Unicode support on FreeBSD]

Unicode

2007-09-27T12:59:50Z

Ice: start of unicode guide

RBL

2007-04-12T18:26:25Z

Ice: reverted to 21:04, 21 May 2006

'''RBL''' is an acronym for '''R'''eal-time '''B'''lack-hole '''L'''ist - a list of IP addresses and/or URLs that nobody wants anything to do with, updated constantly in (you guessed it) real time. RBL's are most frequently used to filter out various types of spam, including the "traditional" email variety as well as the newer but increasingly more problematic [[comment spam]].

A typical RBL server is a very simple purpose-oriented [[DNS]] server which returns "no answer" if the IP being fed to it isn't on its list, and returns a special answer - usually 127.0.0.2 - if the IP is found. In order to check against the RBL, the IP is deconstructed and put together backwards in front of the RBL server's domain name - for example, in order to check the IP address 1.2.3.4 against the fictitious RBL server rbl.spammersarebad.net, you would try to resolve the URL 4.3.2.1.rbl.spammersarebad.net.

server# '''dig +short A 4.3.2.1.rbl.spammersarebad.net'''
127.0.0.2

Aha - the RBL returned 127.0.0.2, so it looks like the IP address 1.2.3.4 is on their list. Most RBLs will give you a little information about what's on their list, if you query them for a TXT record. Usually, the TXT record gives you an URL for a webpage which will tell you more about the list, whether or not the IP is still listed, and possibly (but possibly not) something about why it's listed or for how long it is scheduled to remain listed.

server# '''dig +short TXT 4.3.2.1.rbl.spammersarebad.net'''
"Blocked - see <nowiki>http://rbl.spammersarebad.net/bl.shtml?1.2.3.4</nowiki>"

By comparison, if we ask about an address that isn't on the list, we get no answer at all for either A or TXT records:
server# '''dig +short A 5.4.3.2.rbl.spammersarebad.net'''
server# '''dig +short TXT 5.4.3.2.rbl.spammersarebad.net'''
server#

See also [[Mail toaster]], a freebsdwiki.net special configuration of [[Qmail]] and several other mail applications which includes built-in RBL filtering.

[[Category:FreeBSD Terminology]]

Flash

2007-04-12T18:25:54Z

Ice: reverted to 06:23, 18 March 2007

==How to install flash==

First install linuxpluginwrapper
# pkg_add -r linuxpluginwrapper
Or with options:
# cd /usr/ports/*/linuxpluginwrapper;make install

Next install flashplugin7
# cd /usr/ports/*/linux-flashplugin7;make install

If it cannot fetch the file download it from here:
http://freshmeat.net/projects/flashplugin/

===libmap.conf===

Add the following to /etc/libmap.conf
# Flash7 for Firefox
[/usr/local/lib/npapi/linux-flashplugin/libflashplayer.so]
libpthread.so.0 pluginwrapper/flash7.so
libdl.so.2 pluginwrapper/flash7.so
libz.so.1 libz.so.3
libstdc++-libc6.2-2.so.3 libstdc++.so.4
libm.so.6 libm.so.4
libc.so.6 pluginwrapper/flash7.so

# Flash6 for Konqueror
[/usr/X11R6/lib/linux-flashplugin6/libflashplayer.so]
libpthread.so.0 pluginwrapper/flash6.so
libdl.so.2 pluginwrapper/flash6.so
libz.so.1 libz.so.3
libstdc++-libc6.2-2.so.3 libstdc++.so.5
libm.so.6 libm.so.4
libc.so.6 pluginwrapper/flash6.so

===Konqueror===

Go to Settings -> Configure Konqueror -> plugins

Create the directory and link files
# mkdir /usr/X11R6/lib/linux-flashplugin6
# cd /usr/X11R6/lib/linux-flashplugin6
# ln -s /usr/local/lib/npapi/linux-flashplugin/flashplayer.xpt
# ln -s /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so

Now hit 'Scan for new plugins'

Now go and test it out.

===Native Firefox===

You will need to patch a file and compile it's all explained on this site:

http://www.jail.se/freebsd.html

Flash is currently usable under FreeBSD by installing the ports linux-flashplugin9 or linux-flashplugin7, linux-firefox and using linux-firefox for viewing flash content. However, flashplugin9 appears to be quite unstable resulting in frequent crashes. Therefore, using flashplugin7 is recommended instead of flashplugin9.

===Linux Opera===

I've noticed that some things work better under linux-opera than any other browser on FreeBSD. For instance the Asterisk Flash Operator Panel will only work properlly under this port and YouTube works with sound and video under opera!

All you should have to do is install it. Opera will automatically use the libmap.conf file to find the flash libraries and load them.
# pkg_add -r linux-opera

==External Links==
http://freebsd.kde.org/howtos/konqueror-flash.php

[[Category : FreeBSD Multimedia]]

Runlevels

2007-04-12T18:22:35Z

Ice: reverted to 17:22, 1 August 2005

==What's different?==
Linux runlevels define what services are available -- networking, GUI, etc. BSD runlevels define the system state -- what may be written or changed, kernel security, single user for fixing serious problems, etc. As such, BSD runlevels are used mostly for securing a server that's static (ie, once you've set everything up and nothing will need to be changed, you can bring the runlevel to 3 and no firewall rules or files will be changeable.) See man [[init]].

==So how do I start stuff automagically?==
Linux startup scripts usually live in /etc/init.d/rc.X/ where the X is the particular runlevel. BSD runlevels don't have this granularity for different services starting in different system states -- it's on or it's off, there's no dimmer switch. BSD startup scripts usually live in /etc/rc.d/ or /usr/local/etc/rc.d/ and they'll usually take the same form of commands as their linux siblings:
samizdata# '''/etc/rc.d/named start'''
on a BSD box will start up [[BIND]] [[DNS]] services, assuming the script is there and fully functional (which since it's the base system, it should be).

Certain services can be started automatically by placing certain entries in the [[/etc/rc.conf]] file -- do a [[man]] rc.conf if you want to see what you can put in there.

==Editorial -- why I think the BSD and Linux runlevels are different.==
Linux and BSD runlevels are vastly different, in part because of historical reasons (see [[SysV]] and [[BSD]]) and in part because of the very nature of BSD and Linux's origins. BSD started as a bunch of add-ons to AT&T Unix, so it had serious reasons to keep in line with Unix's [[SRV]] structures; Linux on the other hand, started as a way of getting a personal computer, a user or few users, a unix-like environment. Think of it as "business vs personal" use. So a lot of linux's differences from a more traditional unix were made from a pragmatic approach of "ok, how do we do this to make a sysadmin's life easier". BSD approached the same goal but with more of a focus on keeping the system running and stable.

So. No /etc/init.d/rc.d dirs because a BSD system's runlevels are there more for kernel and system security than for delineating what parts of the system are running. Linux runlevels say "in this runlevel, the network is up" or "in this runlevel, we're in single-user mode" or "in this runlevel, networking and X/GUI are running". BSD runlevels say "single user, emergency fix it mode" or "system tuning, don't play around".

==See also==
See Dru Lavigne's excellent article at O'Reilly Network's ONLAMP: http://www.onlamp.com/pub/a/bsd/2004/11/11/FreeBSD_Basics.html

[[Category: Linux Equivalents]]

OpenVPN

2007-04-12T18:19:58Z

Ice: reverted to older version

[http://openvpn.sourceforge.net OpenVPN] is a very useful open source, cross platform Virtual Private Networking tool. It uses SSL encryption (dynamic or 2048-bit static shared key), can use LZO stream compression, and is blindingly fast as well as much more secure compared to typical industry standard IPSEC + DES or IPSEC + 3DES solutions. Better yet, it's so simple it can be run entirely from the command line.

==Installing==
To build it on a FreeBSD machine, just:

cd /usr/ports/security/openvpn
make install clean

it's that easy. Actually doing anything with it will require a little more work. There are many MANY ways to do this, but this one's useful, simple, and clean.

First, generate yourself a private key file and '''chmod''' it so that only its owner can read it:

ph34r# '''openvpn --genkey --secret /usr/local/etc/openvpn.key'''
ph34r# '''chmod 400 /usr/local/etc/openvpn.key'''

==Starting OpenVPN==
Now you'll need a command to start it with. It can be done purely from the command line - and in fact, in one sense, that's exactly what we're going to do - but to make our lives a little easier, we'll ''actually'' use command line stuff from a shell script in '''/usr/local/etc/rc.d'''. So place this - or something similar - in your '''/usr/local/etc/rc.d''':

#!/bin/sh

case "$1" in
start)
# VPN subnets are contained in 10.10.x.x / 255.255.0.0
# port range forwarded through the router is 4900-4982

# first make sure the TAP module is loaded
kldload if_tap

# now ensure IP forwarding is enabled
/sbin/sysctl -w net.inet.ip.forwarding=1

# Now, make sure there are enough tun* / tap* devices in /dev
cd /dev
/bin/sh MAKEDEV tap0 tap1 tap2 tap3 tap4 tap5 tap6 tap7 tap8 tap9

# Finally, open up for business.
# A tunnel numbered [x] is configured as follows:
# device tun[x], port (4900 + [x]), network 10.10.(10 + [x])
# Client machine is always .2, server is always .1

# note - ping-restart on server end with disconnected clients
# seems to be the problem resulting in exhausted mbufs. Trying
# ping-restart on client end only and hoping for the best.

# 0. Server side - dynamic VPN
/usr/local/sbin/openvpn \
--dev tap0 --port 4900 --ifconfig 10.10.10.1 255.255.255.252 \
--tun-mtu 1500 --tun-mtu-extra 32 --mssfix 1450 --key-method 2 \
--secret /usr/local/etc/openvpn.key --ping 1 &

# # 1a. Client side - persistent VPN
# /usr/local/sbin/openvpn \
# --dev tap1 \
# --remote ''ip_or_hostname.to.connect.to'' \
# --secret /usr/local/etc/openvpn.key \
# --key-method 2 \
# --port 4901 \
# --ifconfig 10.10.11.2 255.255.255.252 \
# --route 192.168.1.0 255.255.255.0 10.10.11.1 \
# --tun-mtu 1500 --tun-mtu-extra 32 \
# --fragment 1300 --mssfix \
# --persist-tun --persist-key --resolv-retry 86400 \
# --ping 10 --ping-restart 15 \
# --verb 4 --mute 10 &

# 1b. Server side - persistent VPN
/usr/local/sbin/openvpn \
--dev tap1 \
--secret /usr/local/etc/openvpn.key \
--key-method 2 \
--port 4901 \
--ifconfig 10.10.11.1 255.255.255.252 \
--route 192.168.1.0 255.255.255.0 10.10.11.2 \
--tun-mtu 1500 --tun-mtu-extra 32 \
--fragment 1300 --mssfix \
--persist-tun --persist-key --resolv-retry 86400 \
--ping 10 --ping-restart 15 \
--verb 4 --mute 10 &

# end section
;;

stop)
killall openvpn
;;
*)
echo "Usage: `basename $0` {start|stop}" >&2
;;
esac

exit 0

Don't forget to '''chmod 755 /usr/local/etc/rc.d/openvpn.sh''' to make sure you can execute it.

What you've got there is a setup (which can be started up or stopped like any other rc.d script - '''/usr/local/etc/rc.d/openvpn.sh start''' or '''stop''') which provides for two tunnels - one coming from a Windows machine, probably a laptop or something (labeled "dynamic VPN"; more on that in a minute) and one (labeled "persistent VPN") from another BSD or other *nix machine.

All we'll do on the other *nix box is copy over the '''openvpn.key''' we created on this machine, copy over this same script, comment out the:

* '''# 1b. Server side - persistent VPN''' section
* ''un''comment the '''# 1a. Client side - persistent VPN''' side
* and fire it up.

Once the scripts have been started on both machines (obviously you'll need a routeable IP address for at least the machine on the "server" side), presto, you've got a tunnel!

Obviously this article is unfinished, but work beckons. More later.

[[Category:Ports and Packages]][[Category:Common Tasks]]

Installing FreeBSD - Standard Installation

2007-04-11T23:30:56Z

Ice: fixed order

'''Installing FreeBSD (article originally based on i386 [[:Category : Architecture-Specific | architecture]] / version 4.7-RELEASE)'''

First things first, you need to make sure you've got FreeBSD available - preferably (for the purposes of this chapter) a burned CD of Disc 1 of a RELEASE snapshot. If you don't already have one, you can get a RELEASE snapshot from the official FreeBSD ftp site or from a mirror - I would personally recommend that you check out the official mirror list and hit one near you. Once you've got it, burn it, and we'll move on. Note: we're assuming that this is a new FreeBSD install, and that you're installing it on a machine with a CD-ROM and a motherboard with BIOS capable of booting from CD-ROM. We're also going to assume that FreeBSD is going to be the only OS on the machine, that you've got at least a 2 gig hard drive available, and you have 64MB of RAM installed. While you can certainly install FreeBSD without a CD and on a considerably lesser machine than the one described, it will be a bit more difficult - and although I may eventually discuss overcoming those difficulties in another article, they're outside the scope of this one.

This article was based on the i386 architecture, but is applicable largely to all architectures. Important [[:Category:Architecture-Specific | architecture-specific]] notes are available [[Sparc - Installing FreeBSD | for installing FreeBSD on the Sparc architechture]].

== Initial Kernel Configuration ==

'''NOTE: Kernel configuration during installation is no longer necessary applicable as of FreeBSD 5.0 and up. If you are installing 5.x, the first thing you'll see after boot (and the section you should skip ahead to right now) is the sysinstall main interface..'''

Before we actually install FreeBSD, you can save yourself a bit of time and trouble by cracking the case open and checking a couple of things out: namely, you want to know what kind of network card you're using, and what sorts of IDE or SCSI controllers you've got. (If you're using IDE, don't sweat it - you really don't have but one option.) For example, you might be using an SMC 1211 network card and an Adaptec 152x (or compatible) SCSI controller. Whatever it is, try to figure it out now - it'll make our first real step easier. Finally, make sure you know the TCP/IP settings the machine will need - IP address, subnet mask, nameserver address, and network gateway.

Okay, so you've got your machine ready, you've set your BIOS to boot from CD-ROM, and you've stuck the CD in the drive and booted. Now what? After a bit, you'll get a prompt "press enter to boot", which you can do, or you can wait a few seconds if you're lazy. The first real chance to make a choice comes up next, and it looks like this:

[[Image: Installation_kernelconfig.png ]]

Start kernel configuration in full-screen visual mode, select "Storage", and hit "Enter." This is what you'll see:

[[Image: Installation_storagedrivers.png]]

Now you know why we identified our network and storage peripherals earlier: you're going to want to remove unnecessary stuff, while very carefully NOT removing anything you actually use. Most folks will be using the ATA/ATAPI compatible disk controllers (one for each of your motherboard's two on-board IDE controllers), and the Floppy disk controller. I personally also leave the Buslogic SCSI controller, which may or may not be necessary on IDE-only systems - one of these days I'll even get experimental and actually find out.

Once you're done deleting unused storage drivers, highlight Network and hit enter. You'll see a whole bunch of possible network cards in here - one of which may or may not be your network card type. If you don't see your card in there, DON'T PANIC! It's probably built into the kernel anyway, and just isn't one of your options to remove from this screen. The network card in the machine above is an SiS 900 chipset onboard, which is NOT listed in the Network section - so I deleted EVERYTHING out of the section. Which is fine - just make sure you DON'T get rid of the driver for your own NIC, if it's in there. If in doubt, at least leave the NE2000 compatible - it'll pick up just about anything else not explicitly covered with its own driver.

Continuing down to Communications, I personally get rid of everything - I personally haven't got the faintest use for TCP/IP over a parallel cable or a serial cable. Most likely, you don't either. You may get rid of these entries, or leave them in, at your own discretion. Once you're done with that, Input, Multimedia and Miscellaneous don't have anything in them really worth getting rid of at this point, so hit "Q" and let's move on!

After you see a couple messages about starting up holographic shells and such-like, you'll be presented with the sysinstall main interface, which looks like this:

== Sysinstall main interface ==

In newer versions of FreeBSD you will be presented with a menu choosing Country and System Console Keymap, choose something appropriate after that you will see the sysinstall main menu.

[[Image: Installation_sysinstallmain.png]]

I don't particularly recommend the Express install unless you really know what you're doing - it'll work, but it'll leave you with some GAPING problems requiring immediate fixing. So let's go with Standard, and get cracking!

The first thing FreeBSD wants to do is partition (or re-partition) your hard drive. After hitting "enter" to the splash screen that tells you this and gives you a bit of detail about the process, you'll see something like this:

[[Image: Installation_partitioning.png]]

Since we're devoting the entire hard drive to FreeBSD (what's the point of a dual-booting SERVER, anyway?), we don't really have to worry about what's on there already - in this case, an old FreeBSD installation, in your case, probably an old Windows installation. All we really need to do here is hit "A" to tell FreeBSD that we want to make one single partition that uses all of the available drive space. Once you've done that, hit "Q" to save your changes and move on.

[[Image: Installation_bootmanager.png]]

Keeping this short and sweet, since we're installing FreeBSD as a standalone OS on this system, we DON'T want to futz around with the default choice, BootMgr. Instead, we want Standard - don't bug me when I turn on the system, just boot! Highlight it, and hit "enter". Things are about to get a little more interesting...

[[Image: Installation_slicesplash.png]]

Now, while the splash screen for the slice manager tells you that you can safely hit "Auto" if you have a mere 200MB of space available, I'm going to tell you flat out that baby, it just ain't so. If you've got a tiny drive or a really miniscule amount of RAM, the defaults picked by Auto aren't going to work very well, and may in fact cripple your system badly enough to need reinstallation. Once again, while you can certainly install FreeBSD on less, it's a touchier procedure, and beyond the scope of this article. But hey, that's why we made sure we had at least 64MB and 2GB to work with, right? ... Right? OK, moving on:

[[Image: Installation_slices.png]]

OK, this is where you make slices in your partition to store various essential bits of the OS and your data. Since this is a simple install and - must I stress it again? - you have at least 64MB and 2GB to work with, we're not going to dabble about in this. Just hit "A" for Auto Defaults, and it will slice up the partition like a sushi chef, leaving you with 128MB for / (the root directory), about double your RAM size for the swap, 256MB apiece for /tmp and /var, and the remainder of the partition allocated to /usr. You may want to consult [[Hard Disk Partition Sizes]] for a review of what might be placed on these different partitions. Dandy! Hit "Q" to save your changes, and we'll keep this thing rolling right along.

Now you get to choose what install you want, for a server Kern-Developer is probably the best way to go. If you want X you can install X-Kern-Developer instead.

[[Image: Installation_choosedist.png]]

So what is this ports thing? Well i just say it's almost a must it's were all third part programs are installed from so that's a Yes. For more information about ports see [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports.html Installing Applications: Packages and Ports].

[[Image: Installation_ports.png]]

Now it's time do decide where to install FreeBSD from, if you downloaded the full disc 1 choose CD/DVD and hit enter. If you downloaded the boot-only cd you probably want to select ftp here. If you choose ftp you will be presented with a list of mirrors, choose one close to you.

[[Image: Installation_selectmedia.png]]

At this point, the system is going to want to configure network interfaces. You'll see something similar to this:

[[Image: Installation_interfaces.png]]

Generally, the top entry is your network card, which is what we want to configure at this stage. (Modem users may have a different take on things - and we're not going to get into PPP configuration here. For now, we're assuming that you DO want to configure a NIC and DON'T want to configure a modem.) Common network interfaces are sis0, rl0, ed0, xl0, and pn0, among others - the important bit is, they're generally all going to say "ethernet card" on the tag end of the description. If you DON'T have an ethernet card listed here, you're in trouble - most likely, you deleted out the driver for your NIC during kernel configuration. If you continue to have problems at this point, you might want to consider NOT deleting ANY network interfaces out of your kernel config - generally speaking, having support for the extra interfaces built into your kernel won't typically hurt anything.

The next thing it's going to want to know is if you'd like to configure IPv6. I'll put it to you this way - unless you already know perfectly well that you want and need IPv6 right now, no, you don't want to. And in particular, if you don't know what IPv6 is, select no! The next thing it wants to know is if you'd like to try DHCP configuration of the interface. For the purposes of these articles, you do not want to attempt DHCP - if the machine is going to be a server, it's going to need a static IP address. So no DHCP for you! Next, it will bring up an IPv4 configuration screen for the interface:

[[Image: Installation_network.png]]

If you didn't use DHCP - and you didn't, right? - you'll need to fill out all of the information on the screen except "Extra options to ifconfig". "Host" will be the name you want to christen this server with. "Domain" is a little trickier - if you DON'T have a pre-existing domain name server assigning DNS records to point at IP addresses on your local network (and if you don't know the answer to this, you almost certainly don't) then you'll need to make up a local domain. I strongly suggest doing so using .local for the top level domain - ie, my private network is named tehinterweb.local, as you can see above. The advantage to doing this is that you are absolutely guaranteed that you aren't using the same domain name as a real domain somewhere out there on the public internet, and you'll know at a glance whether you're looking at internal or external DNS stuff, potentially saving you a lot of confusion down the road. Once you've got the Domain field filled out, sysinstall will automatically append it to your hostname - so proof became proof.tehinterweb.local in our example above.

Later on in another article, we'll discuss setting up BIND so that other computers on your network will know where yourhost.yourdomainname.local is, and how to set up DNS records for those other computers and/or network devices too - but for right now, we're done with this screen, and it's time to select OK and move on. As soon as you hit OK, it'll immediately start moving data:

[[Image: Installation_extracting.png]]

All we're actually installing right now is the base system, so this shouldn't take but a minute or two. Once it's done, you'll get a congratulatory little message about having installed FreeBSD on your system, and once you've hit enter, things will get interesting again! It will ask you a series of questions about how to configure your machine - if you want to function as a network gateway, if you want to configure inetd, if you want anonymous FTP access, if you want to be an NFS server, if you want to be an NFS client, and if you want to use a default security profile. For right now, the answer to all these questions is "no". Yes, even if you really do want to run NFS later. Trust me on this one - for right now, just get the OS installed; you can get fancy later once you've actually got it working. Once you're done with the "no, no, no, no, no, and no" you'll get a splash screen telling you a bit about the "moderate" security settings that you got by answering "no" to the default security profile and warning you that security breaches are like forest fires; only YOU can stop them. Great. Hit enter, and we're back to telling it no again: we don't want to change the console settings. However, we DO want to set the machine's time zone, so tell it so, tell it the CMOS clock isn't set to UTC, and pick a continent, a region, and a time zone. (Note: the page down and page up keys DO work on these menus, and since they're alphabetized, they'll come in quite handy for those of us from the United States, as well as the Venezuelans in the crowd.)

Once you've picked a zone and confirmed that it looks reasonable, you'll be asked if you want to enable Linux binary compatibility. For now, the answer is "no" - if you want Linux binaries at a later date, you can always come back and install this module then. These articles are going to focus heavily on using the ports tree to compile all your own applications as native FreeBSD binaries from source code, though, so it's unnecessary for now.

Next, you'll get asked if you've got a non-USB mouse attached to the system. Answer the nice computer, and move right on along - presuming the answer is "yes", you'll get a chance to test and enable the mouse daemon. Test it, see if the arrow makes nice wigglies when you move the mouse (it won't do anything when you click, so don't worry about that), and click "Enable" if it did or "Cancel" if it didn't. If the mouse didn't work, DON'T sweat it - you're using a command-driven operating system, here, and if you're following along with these articles, you're going to be learning how to live at the command line and like it. So if the mouse doesn't seem to want to work, file it under "stuff to worry about some other day" and move right on along.

[[Image: Installation_packages.png]]

This popup gets its own screenshot because you do not, repeat, do NOT want to browse the package collection right now. Once again, we're here to install FreeBSD right now, not put a bunch of apps on it - that comes later. Be warned, if you decide to ignore me and go play through the packages collection right now anyway, you can easily screw up your installation. There are thousands of things in packages ranging from "nifty" to "inadvisable", none of which are described in enough detail in the packages menu to choose if you don't already know what they are before going in there. Finally, this is NOT the only time you'll ever be able to use that menu to install packages - you can return to it at any time once you've finished installing the OS. So please, please, don't make life difficult - select "No" and KEEP MOVING!

The next thing sysinstall wants to know is if you'd like to add another user account to the system. Yes, you would! Not only is logging in as root extremely insecure, if you do not have another user account on the system, you will not be able to remote control it. So tell it "yes", tell it you want to add another User to the system, and here we are:

[[Image: Installation_adduser.png ]]

There are a few things worth noting on this screen. UID is filled out for you (and shouldn't be changed unless you know what you're doing), Full name defaults to "User &" and is utterly unimportant (it's just a "comment" field) and Home directory defaults to /home/[whatever you put for Login ID], but the rest needs to be filled out and/or changed. In particular, make sure that you enter wheel in the Group field so that you will be able to assume root privileges using this account, and that you change your Login shell from /bin/sh to /bin/csh. (Linux expatriates, [[bash]] isn't available right now - you can install it from ports when we're done, but in the meantime, the [[c shell]], /bin/csh is what you want.) The default shell is extremely painful to work with, so don't forget to do this! Once you're done, highlight "OK" and hit enter, highlight "Exit" and hit enter in the next screen, and you'll be prompted to set the root password. Do so, tell it you don't need to visit the general configuration menu to set any last options, and you'll be back at the sysinstall main menu - and when you select "Exit Install", the system will reboot into FreeBSD!

[[Category : Installation]]

Installing FreeBSD - Standard Installation

2007-04-11T23:06:08Z

Ice: added images

'''Installing FreeBSD (article originally based on i386 [[:Category : Architecture-Specific | architecture]] / version 4.7-RELEASE)'''

First things first, you need to make sure you've got FreeBSD available - preferably (for the purposes of this chapter) a burned CD of Disc 1 of a RELEASE snapshot. If you don't already have one, you can get a RELEASE snapshot from the official FreeBSD ftp site or from a mirror - I would personally recommend that you check out the official mirror list and hit one near you. Once you've got it, burn it, and we'll move on. Note: we're assuming that this is a new FreeBSD install, and that you're installing it on a machine with a CD-ROM and a motherboard with BIOS capable of booting from CD-ROM. We're also going to assume that FreeBSD is going to be the only OS on the machine, that you've got at least a 2 gig hard drive available, and you have 64MB of RAM installed. While you can certainly install FreeBSD without a CD and on a considerably lesser machine than the one described, it will be a bit more difficult - and although I may eventually discuss overcoming those difficulties in another article, they're outside the scope of this one.

This article was based on the i386 architecture, but is applicable largely to all architectures. Important [[:Category:Architecture-Specific | architecture-specific]] notes are available [[Sparc - Installing FreeBSD | for installing FreeBSD on the Sparc architechture]].

== Initial Kernel Configuration ==

'''NOTE: Kernel configuration during installation is no longer necessary applicable as of FreeBSD 5.0 and up. If you are installing 5.x, the first thing you'll see after boot (and the section you should skip ahead to right now) is the sysinstall main interface..'''

Before we actually install FreeBSD, you can save yourself a bit of time and trouble by cracking the case open and checking a couple of things out: namely, you want to know what kind of network card you're using, and what sorts of IDE or SCSI controllers you've got. (If you're using IDE, don't sweat it - you really don't have but one option.) For example, you might be using an SMC 1211 network card and an Adaptec 152x (or compatible) SCSI controller. Whatever it is, try to figure it out now - it'll make our first real step easier. Finally, make sure you know the TCP/IP settings the machine will need - IP address, subnet mask, nameserver address, and network gateway.

Okay, so you've got your machine ready, you've set your BIOS to boot from CD-ROM, and you've stuck the CD in the drive and booted. Now what? After a bit, you'll get a prompt "press enter to boot", which you can do, or you can wait a few seconds if you're lazy. The first real chance to make a choice comes up next, and it looks like this:

[[Image: Installation_kernelconfig.png ]]

Start kernel configuration in full-screen visual mode, select "Storage", and hit "Enter." This is what you'll see:

[[Image: Installation_storagedrivers.png]]

Now you know why we identified our network and storage peripherals earlier: you're going to want to remove unnecessary stuff, while very carefully NOT removing anything you actually use. Most folks will be using the ATA/ATAPI compatible disk controllers (one for each of your motherboard's two on-board IDE controllers), and the Floppy disk controller. I personally also leave the Buslogic SCSI controller, which may or may not be necessary on IDE-only systems - one of these days I'll even get experimental and actually find out.

Once you're done deleting unused storage drivers, highlight Network and hit enter. You'll see a whole bunch of possible network cards in here - one of which may or may not be your network card type. If you don't see your card in there, DON'T PANIC! It's probably built into the kernel anyway, and just isn't one of your options to remove from this screen. The network card in the machine above is an SiS 900 chipset onboard, which is NOT listed in the Network section - so I deleted EVERYTHING out of the section. Which is fine - just make sure you DON'T get rid of the driver for your own NIC, if it's in there. If in doubt, at least leave the NE2000 compatible - it'll pick up just about anything else not explicitly covered with its own driver.

Continuing down to Communications, I personally get rid of everything - I personally haven't got the faintest use for TCP/IP over a parallel cable or a serial cable. Most likely, you don't either. You may get rid of these entries, or leave them in, at your own discretion. Once you're done with that, Input, Multimedia and Miscellaneous don't have anything in them really worth getting rid of at this point, so hit "Q" and let's move on!

After you see a couple messages about starting up holographic shells and such-like, you'll be presented with the sysinstall main interface, which looks like this:

== Sysinstall main interface ==

In newer versions of FreeBSD you will be presented with a menu choosing Country and System Console Keymap, choose something appropriate after that you will see the sysinstall main menu.

[[Image: Installation_sysinstallmain.png]]

I don't particularly recommend the Express install unless you really know what you're doing - it'll work, but it'll leave you with some GAPING problems requiring immediate fixing. So let's go with Standard, and get cracking!

The first thing FreeBSD wants to do is partition (or re-partition) your hard drive. After hitting "enter" to the splash screen that tells you this and gives you a bit of detail about the process, you'll see something like this:

[[Image: Installation_partitioning.png]]

Since we're devoting the entire hard drive to FreeBSD (what's the point of a dual-booting SERVER, anyway?), we don't really have to worry about what's on there already - in this case, an old FreeBSD installation, in your case, probably an old Windows installation. All we really need to do here is hit "A" to tell FreeBSD that we want to make one single partition that uses all of the available drive space. Once you've done that, hit "Q" to save your changes and move on.

[[Image: Installation_bootmanager.png]]

Keeping this short and sweet, since we're installing FreeBSD as a standalone OS on this system, we DON'T want to futz around with the default choice, BootMgr. Instead, we want Standard - don't bug me when I turn on the system, just boot! Highlight it, and hit "enter". Things are about to get a little more interesting...

[[Image: Installation_slicesplash.png]]

Now, while the splash screen for the slice manager tells you that you can safely hit "Auto" if you have a mere 200MB of space available, I'm going to tell you flat out that baby, it just ain't so. If you've got a tiny drive or a really miniscule amount of RAM, the defaults picked by Auto aren't going to work very well, and may in fact cripple your system badly enough to need reinstallation. Once again, while you can certainly install FreeBSD on less, it's a touchier procedure, and beyond the scope of this article. But hey, that's why we made sure we had at least 64MB and 2GB to work with, right? ... Right? OK, moving on:

[[Image: Installation_slices.png]]

OK, this is where you make slices in your partition to store various essential bits of the OS and your data. Since this is a simple install and - must I stress it again? - you have at least 64MB and 2GB to work with, we're not going to dabble about in this. Just hit "A" for Auto Defaults, and it will slice up the partition like a sushi chef, leaving you with 128MB for / (the root directory), about double your RAM size for the swap, 256MB apiece for /tmp and /var, and the remainder of the partition allocated to /usr. You may want to consult [[Hard Disk Partition Sizes]] for a review of what might be placed on these different partitions. Dandy! Hit "Q" to save your changes, and we'll keep this thing rolling right along.

Now you get to choose what install you want, for a server Kern-Developer is probably the best way to go. If you want X you can install X-Kern-Developer instead.

[[Image: Installation_choosedist.png]]

So what is this ports thing? Well i just say it's almost a must it's were all third part programs are installed from so that's a Yes. For mor information about ports see [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports.html Installing Applications: Packages and Ports].

[[Image: Installation_ports.png]]

At this point, the system is going to want to configure network interfaces. Depending on how much you did or didn't delete out of the kernel config area, you'll see something similar to this:

[[Image: Installation_interfaces.png]]

Generally, the top entry is your network card, which is what we want to configure at this stage. (Modem users may have a different take on things - and we're not going to get into PPP configuration here. For now, we're assuming that you DO want to configure a NIC and DON'T want to configure a modem.) Common network interfaces are sis0, rl0, ed0, xl0, and pn0, among others - the important bit is, they're generally all going to say "ethernet card" on the tag end of the description. If you DON'T have an ethernet card listed here, you're in trouble - most likely, you deleted out the driver for your NIC during kernel configuration. If you continue to have problems at this point, you might want to consider NOT deleting ANY network interfaces out of your kernel config - generally speaking, having support for the extra interfaces built into your kernel won't typically hurt anything.

The next thing it's going to want to know is if you'd like to configure IPv6. I'll put it to you this way - unless you already know perfectly well that you want and need IPv6 right now, no, you don't want to. And in particular, if you don't know what IPv6 is, select no! The next thing it wants to know is if you'd like to try DHCP configuration of the interface. For the purposes of these articles, you do not want to attempt DHCP - if the machine is going to be a server, it's going to need a static IP address. So no DHCP for you! Next, it will bring up an IPv4 configuration screen for the interface:

[[Image: Installation_network.png]]

If you didn't use DHCP - and you didn't, right? - you'll need to fill out all of the information on the screen except "Extra options to ifconfig". "Host" will be the name you want to christen this server with. "Domain" is a little trickier - if you DON'T have a pre-existing domain name server assigning DNS records to point at IP addresses on your local network (and if you don't know the answer to this, you almost certainly don't) then you'll need to make up a local domain. I strongly suggest doing so using .local for the top level domain - ie, my private network is named tehinterweb.local, as you can see above. The advantage to doing this is that you are absolutely guaranteed that you aren't using the same domain name as a real domain somewhere out there on the public internet, and you'll know at a glance whether you're looking at internal or external DNS stuff, potentially saving you a lot of confusion down the road. Once you've got the Domain field filled out, sysinstall will automatically append it to your hostname - so proof became proof.tehinterweb.local in our example above.

Later on in another article, we'll discuss setting up BIND so that other computers on your network will know where yourhost.yourdomainname.local is, and how to set up DNS records for those other computers and/or network devices too - but for right now, we're done with this screen, and it's time to select OK and move on.

[[Image: Installation_selectmedia.png]]

Hopefully, you don't need me to tell you to highlight CD/DVD and hit enter on this media selection screen. It's worth noting that VERY occasionally, you may run into a system in which FreeBSD has trouble identifying the CD-ROM drive at this point, even though it booted off of it - this generally has something to do with the type of emulation the motherboard and/or the CD-ROM itself uses for CD-ROM boots. If you have problems here, you can try swapping the CD-ROM drive to another IDE channel as a standalone master, trying a completely different CD-ROM drive, or - if you've got a broadband connection and an hour or three to kill - installing from FTP. But most likely, as soon as you hit OK, it'll immediately start moving data:

[[Image: Installation_extracting.png]]

All we're actually installing right now is the base system, so this shouldn't take but a minute or two. Once it's done, you'll get a congratulatory little message about having installed FreeBSD on your system, and once you've hit enter, things will get interesting again! It will ask you a series of questions about how to configure your machine - if you want to function as a network gateway, if you want to configure inetd, if you want anonymous FTP access, if you want to be an NFS server, if you want to be an NFS client, and if you want to use a default security profile. For right now, the answer to all these questions is "no". Yes, even if you really do want to run NFS later. Trust me on this one - for right now, just get the OS installed; you can get fancy later once you've actually got it working. Once you're done with the "no, no, no, no, no, and no" you'll get a splash screen telling you a bit about the "moderate" security settings that you got by answering "no" to the default security profile and warning you that security breaches are like forest fires; only YOU can stop them. Great. Hit enter, and we're back to telling it no again: we don't want to change the console settings. However, we DO want to set the machine's time zone, so tell it so, tell it the CMOS clock isn't set to UTC, and pick a continent, a region, and a time zone. (Note: the page down and page up keys DO work on these menus, and since they're alphabetized, they'll come in quite handy for those of us from the United States, as well as the Venezuelans in the crowd.)

Once you've picked a zone and confirmed that it looks reasonable, you'll be asked if you want to enable Linux binary compatibility. For now, the answer is "no" - if you want Linux binaries at a later date, you can always come back and install this module then. These articles are going to focus heavily on using the ports tree to compile all your own applications as native FreeBSD binaries from source code, though, so it's unnecessary for now.

Next, you'll get asked if you've got a non-USB mouse attached to the system. Answer the nice computer, and move right on along - presuming the answer is "yes", you'll get a chance to test and enable the mouse daemon. Test it, see if the arrow makes nice wigglies when you move the mouse (it won't do anything when you click, so don't worry about that), and click "Enable" if it did or "Cancel" if it didn't. If the mouse didn't work, DON'T sweat it - you're using a command-driven operating system, here, and if you're following along with these articles, you're going to be learning how to live at the command line and like it. So if the mouse doesn't seem to want to work, file it under "stuff to worry about some other day" and move right on along.

[[Image: Installation_packages.png]]

This popup gets its own screenshot because you do not, repeat, do NOT want to browse the package collection right now. Once again, we're here to install FreeBSD right now, not put a bunch of apps on it - that comes later. Be warned, if you decide to ignore me and go play through the packages collection right now anyway, you can easily screw up your installation. There are thousands of things in packages ranging from "nifty" to "inadvisable", none of which are described in enough detail in the packages menu to choose if you don't already know what they are before going in there. Finally, this is NOT the only time you'll ever be able to use that menu to install packages - you can return to it at any time once you've finished installing the OS. So please, please, don't make life difficult - select "No" and KEEP MOVING!

The next thing sysinstall wants to know is if you'd like to add another user account to the system. Yes, you would! Not only is logging in as root extremely insecure, if you do not have another user account on the system, you will not be able to remote control it. So tell it "yes", tell it you want to add another User to the system, and here we are:

[[Image: Installation_adduser.png ]]

There are a few things worth noting on this screen. UID is filled out for you (and shouldn't be changed unless you know what you're doing), Full name defaults to "User &" and is utterly unimportant (it's just a "comment" field) and Home directory defaults to /home/[whatever you put for Login ID], but the rest needs to be filled out and/or changed. In particular, make sure that you enter wheel in the Group field so that you will be able to assume root privileges using this account, and that you change your Login shell from /bin/sh to /bin/csh. (Linux expatriates, [[bash]] isn't available right now - you can install it from ports when we're done, but in the meantime, the [[c shell]], /bin/csh is what you want.) The default shell is extremely painful to work with, so don't forget to do this! Once you're done, highlight "OK" and hit enter, highlight "Exit" and hit enter in the next screen, and you'll be prompted to set the root password. Do so, tell it you don't need to visit the general configuration menu to set any last options, and you'll be back at the sysinstall main menu - and when you select "Exit Install", the system will reboot into FreeBSD!

[[Category : Installation]]

File:Installation ports.png

2007-04-11T23:04:29Z

Ice:

Installing FreeBSD - Standard Installation

2007-04-11T22:58:46Z

Ice: updating with installation type and so on

'''Installing FreeBSD (article originally based on i386 [[:Category : Architecture-Specific | architecture]] / version 4.7-RELEASE)'''

First things first, you need to make sure you've got FreeBSD available - preferably (for the purposes of this chapter) a burned CD of Disc 1 of a RELEASE snapshot. If you don't already have one, you can get a RELEASE snapshot from the official FreeBSD ftp site or from a mirror - I would personally recommend that you check out the official mirror list and hit one near you. Once you've got it, burn it, and we'll move on. Note: we're assuming that this is a new FreeBSD install, and that you're installing it on a machine with a CD-ROM and a motherboard with BIOS capable of booting from CD-ROM. We're also going to assume that FreeBSD is going to be the only OS on the machine, that you've got at least a 2 gig hard drive available, and you have 64MB of RAM installed. While you can certainly install FreeBSD without a CD and on a considerably lesser machine than the one described, it will be a bit more difficult - and although I may eventually discuss overcoming those difficulties in another article, they're outside the scope of this one.

This article was based on the i386 architecture, but is applicable largely to all architectures. Important [[:Category:Architecture-Specific | architecture-specific]] notes are available [[Sparc - Installing FreeBSD | for installing FreeBSD on the Sparc architechture]].

== Initial Kernel Configuration ==

'''NOTE: Kernel configuration during installation is no longer necessary applicable as of FreeBSD 5.0 and up. If you are installing 5.x, the first thing you'll see after boot (and the section you should skip ahead to right now) is the sysinstall main interface..'''

Before we actually install FreeBSD, you can save yourself a bit of time and trouble by cracking the case open and checking a couple of things out: namely, you want to know what kind of network card you're using, and what sorts of IDE or SCSI controllers you've got. (If you're using IDE, don't sweat it - you really don't have but one option.) For example, you might be using an SMC 1211 network card and an Adaptec 152x (or compatible) SCSI controller. Whatever it is, try to figure it out now - it'll make our first real step easier. Finally, make sure you know the TCP/IP settings the machine will need - IP address, subnet mask, nameserver address, and network gateway.

Okay, so you've got your machine ready, you've set your BIOS to boot from CD-ROM, and you've stuck the CD in the drive and booted. Now what? After a bit, you'll get a prompt "press enter to boot", which you can do, or you can wait a few seconds if you're lazy. The first real chance to make a choice comes up next, and it looks like this:

[[Image: Installation_kernelconfig.png ]]

Start kernel configuration in full-screen visual mode, select "Storage", and hit "Enter." This is what you'll see:

[[Image: Installation_storagedrivers.png]]

Now you know why we identified our network and storage peripherals earlier: you're going to want to remove unnecessary stuff, while very carefully NOT removing anything you actually use. Most folks will be using the ATA/ATAPI compatible disk controllers (one for each of your motherboard's two on-board IDE controllers), and the Floppy disk controller. I personally also leave the Buslogic SCSI controller, which may or may not be necessary on IDE-only systems - one of these days I'll even get experimental and actually find out.

Once you're done deleting unused storage drivers, highlight Network and hit enter. You'll see a whole bunch of possible network cards in here - one of which may or may not be your network card type. If you don't see your card in there, DON'T PANIC! It's probably built into the kernel anyway, and just isn't one of your options to remove from this screen. The network card in the machine above is an SiS 900 chipset onboard, which is NOT listed in the Network section - so I deleted EVERYTHING out of the section. Which is fine - just make sure you DON'T get rid of the driver for your own NIC, if it's in there. If in doubt, at least leave the NE2000 compatible - it'll pick up just about anything else not explicitly covered with its own driver.

Continuing down to Communications, I personally get rid of everything - I personally haven't got the faintest use for TCP/IP over a parallel cable or a serial cable. Most likely, you don't either. You may get rid of these entries, or leave them in, at your own discretion. Once you're done with that, Input, Multimedia and Miscellaneous don't have anything in them really worth getting rid of at this point, so hit "Q" and let's move on!

After you see a couple messages about starting up holographic shells and such-like, you'll be presented with the sysinstall main interface, which looks like this:

== Sysinstall main interface ==

In newer versions of FreeBSD you will be presented with a menu choosing Country and System Console Keymap, choose something appropriate after that you will see the sysinstall main menu.

[[Image: Installation_sysinstallmain.png]]

I don't particularly recommend the Express install unless you really know what you're doing - it'll work, but it'll leave you with some GAPING problems requiring immediate fixing. So let's go with Standard, and get cracking!

The first thing FreeBSD wants to do is partition (or re-partition) your hard drive. After hitting "enter" to the splash screen that tells you this and gives you a bit of detail about the process, you'll see something like this:

[[Image: Installation_partitioning.png]]

Since we're devoting the entire hard drive to FreeBSD (what's the point of a dual-booting SERVER, anyway?), we don't really have to worry about what's on there already - in this case, an old FreeBSD installation, in your case, probably an old Windows installation. All we really need to do here is hit "A" to tell FreeBSD that we want to make one single partition that uses all of the available drive space. Once you've done that, hit "Q" to save your changes and move on.

[[Image: Installation_bootmanager.png]]

Keeping this short and sweet, since we're installing FreeBSD as a standalone OS on this system, we DON'T want to futz around with the default choice, BootMgr. Instead, we want Standard - don't bug me when I turn on the system, just boot! Highlight it, and hit "enter". Things are about to get a little more interesting...

[[Image: Installation_slicesplash.png]]

Now, while the splash screen for the slice manager tells you that you can safely hit "Auto" if you have a mere 200MB of space available, I'm going to tell you flat out that baby, it just ain't so. If you've got a tiny drive or a really miniscule amount of RAM, the defaults picked by Auto aren't going to work very well, and may in fact cripple your system badly enough to need reinstallation. Once again, while you can certainly install FreeBSD on less, it's a touchier procedure, and beyond the scope of this article. But hey, that's why we made sure we had at least 64MB and 2GB to work with, right? ... Right? OK, moving on:

[[Image: Installation_slices.png]]

OK, this is where you make slices in your partition to store various essential bits of the OS and your data. Since this is a simple install and - must I stress it again? - you have at least 64MB and 2GB to work with, we're not going to dabble about in this. Just hit "A" for Auto Defaults, and it will slice up the partition like a sushi chef, leaving you with 128MB for / (the root directory), about double your RAM size for the swap, 256MB apiece for /tmp and /var, and the remainder of the partition allocated to /usr. You may want to consult [[Hard Disk Partition Sizes]] for a review of what might be placed on these different partitions. Dandy! Hit "Q" to save your changes, and we'll keep this thing rolling right along.

Now you get to choose what install you want, for a server Kern-Developer is probably the best way to go. If you want X you can install X-Kern-Developer instead.

-image-

So what is this ports thing? Well i just say it's almost a must it's were all third part programs are installed from so that's a Yes. For mor information about ports see [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports.html Installing Applications: Packages and Ports].

-image-

At this point, the system is going to want to configure network interfaces. Depending on how much you did or didn't delete out of the kernel config area, you'll see something similar to this:

[[Image: Installation_interfaces.png]]

Generally, the top entry is your network card, which is what we want to configure at this stage. (Modem users may have a different take on things - and we're not going to get into PPP configuration here. For now, we're assuming that you DO want to configure a NIC and DON'T want to configure a modem.) Common network interfaces are sis0, rl0, ed0, xl0, and pn0, among others - the important bit is, they're generally all going to say "ethernet card" on the tag end of the description. If you DON'T have an ethernet card listed here, you're in trouble - most likely, you deleted out the driver for your NIC during kernel configuration. If you continue to have problems at this point, you might want to consider NOT deleting ANY network interfaces out of your kernel config - generally speaking, having support for the extra interfaces built into your kernel won't typically hurt anything.

The next thing it's going to want to know is if you'd like to configure IPv6. I'll put it to you this way - unless you already know perfectly well that you want and need IPv6 right now, no, you don't want to. And in particular, if you don't know what IPv6 is, select no! The next thing it wants to know is if you'd like to try DHCP configuration of the interface. For the purposes of these articles, you do not want to attempt DHCP - if the machine is going to be a server, it's going to need a static IP address. So no DHCP for you! Next, it will bring up an IPv4 configuration screen for the interface:

[[Image: Installation_network.png]]

If you didn't use DHCP - and you didn't, right? - you'll need to fill out all of the information on the screen except "Extra options to ifconfig". "Host" will be the name you want to christen this server with. "Domain" is a little trickier - if you DON'T have a pre-existing domain name server assigning DNS records to point at IP addresses on your local network (and if you don't know the answer to this, you almost certainly don't) then you'll need to make up a local domain. I strongly suggest doing so using .local for the top level domain - ie, my private network is named tehinterweb.local, as you can see above. The advantage to doing this is that you are absolutely guaranteed that you aren't using the same domain name as a real domain somewhere out there on the public internet, and you'll know at a glance whether you're looking at internal or external DNS stuff, potentially saving you a lot of confusion down the road. Once you've got the Domain field filled out, sysinstall will automatically append it to your hostname - so proof became proof.tehinterweb.local in our example above.

Later on in another article, we'll discuss setting up BIND so that other computers on your network will know where yourhost.yourdomainname.local is, and how to set up DNS records for those other computers and/or network devices too - but for right now, we're done with this screen, and it's time to select OK and move on.

[[Image: Installation_selectmedia.png]]

Hopefully, you don't need me to tell you to highlight CD/DVD and hit enter on this media selection screen. It's worth noting that VERY occasionally, you may run into a system in which FreeBSD has trouble identifying the CD-ROM drive at this point, even though it booted off of it - this generally has something to do with the type of emulation the motherboard and/or the CD-ROM itself uses for CD-ROM boots. If you have problems here, you can try swapping the CD-ROM drive to another IDE channel as a standalone master, trying a completely different CD-ROM drive, or - if you've got a broadband connection and an hour or three to kill - installing from FTP. But most likely, as soon as you hit OK, it'll immediately start moving data:

[[Image: Installation_extracting.png]]

All we're actually installing right now is the base system, so this shouldn't take but a minute or two. Once it's done, you'll get a congratulatory little message about having installed FreeBSD on your system, and once you've hit enter, things will get interesting again! It will ask you a series of questions about how to configure your machine - if you want to function as a network gateway, if you want to configure inetd, if you want anonymous FTP access, if you want to be an NFS server, if you want to be an NFS client, and if you want to use a default security profile. For right now, the answer to all these questions is "no". Yes, even if you really do want to run NFS later. Trust me on this one - for right now, just get the OS installed; you can get fancy later once you've actually got it working. Once you're done with the "no, no, no, no, no, and no" you'll get a splash screen telling you a bit about the "moderate" security settings that you got by answering "no" to the default security profile and warning you that security breaches are like forest fires; only YOU can stop them. Great. Hit enter, and we're back to telling it no again: we don't want to change the console settings. However, we DO want to set the machine's time zone, so tell it so, tell it the CMOS clock isn't set to UTC, and pick a continent, a region, and a time zone. (Note: the page down and page up keys DO work on these menus, and since they're alphabetized, they'll come in quite handy for those of us from the United States, as well as the Venezuelans in the crowd.)

Once you've picked a zone and confirmed that it looks reasonable, you'll be asked if you want to enable Linux binary compatibility. For now, the answer is "no" - if you want Linux binaries at a later date, you can always come back and install this module then. These articles are going to focus heavily on using the ports tree to compile all your own applications as native FreeBSD binaries from source code, though, so it's unnecessary for now.

Next, you'll get asked if you've got a non-USB mouse attached to the system. Answer the nice computer, and move right on along - presuming the answer is "yes", you'll get a chance to test and enable the mouse daemon. Test it, see if the arrow makes nice wigglies when you move the mouse (it won't do anything when you click, so don't worry about that), and click "Enable" if it did or "Cancel" if it didn't. If the mouse didn't work, DON'T sweat it - you're using a command-driven operating system, here, and if you're following along with these articles, you're going to be learning how to live at the command line and like it. So if the mouse doesn't seem to want to work, file it under "stuff to worry about some other day" and move right on along.

[[Image: Installation_packages.png]]

This popup gets its own screenshot because you do not, repeat, do NOT want to browse the package collection right now. Once again, we're here to install FreeBSD right now, not put a bunch of apps on it - that comes later. Be warned, if you decide to ignore me and go play through the packages collection right now anyway, you can easily screw up your installation. There are thousands of things in packages ranging from "nifty" to "inadvisable", none of which are described in enough detail in the packages menu to choose if you don't already know what they are before going in there. Finally, this is NOT the only time you'll ever be able to use that menu to install packages - you can return to it at any time once you've finished installing the OS. So please, please, don't make life difficult - select "No" and KEEP MOVING!

The next thing sysinstall wants to know is if you'd like to add another user account to the system. Yes, you would! Not only is logging in as root extremely insecure, if you do not have another user account on the system, you will not be able to remote control it. So tell it "yes", tell it you want to add another User to the system, and here we are:

[[Image: Installation_adduser.png ]]

There are a few things worth noting on this screen. UID is filled out for you (and shouldn't be changed unless you know what you're doing), Full name defaults to "User &" and is utterly unimportant (it's just a "comment" field) and Home directory defaults to /home/[whatever you put for Login ID], but the rest needs to be filled out and/or changed. In particular, make sure that you enter wheel in the Group field so that you will be able to assume root privileges using this account, and that you change your Login shell from /bin/sh to /bin/csh. (Linux expatriates, [[bash]] isn't available right now - you can install it from ports when we're done, but in the meantime, the [[c shell]], /bin/csh is what you want.) The default shell is extremely painful to work with, so don't forget to do this! Once you're done, highlight "OK" and hit enter, highlight "Exit" and hit enter in the next screen, and you'll be prompted to set the root password. Do so, tell it you don't need to visit the general configuration menu to set any last options, and you'll be back at the sysinstall main menu - and when you select "Exit Install", the system will reboot into FreeBSD!

[[Category : Installation]]

File:Installation choosedist.png

2007-04-11T22:56:10Z

Ice:

Installing FreeBSD with netboot

2007-03-25T20:06:52Z

Ice:

== FreeBSD bootonly ==
The first step to installing FreeBSD via netboot is to acquire FreeBSD. We'll be using the bootonly-iso, this can be fetched at your nearest ftp.

Download the bootonly-iso:
fetch ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/6.2/6.2-RELEASE-i386-bootonly.iso
Mount the iso-image and copy the contents to some location:
mdconfig -a -t vnode -f 6.2-RELEASE-i386-bootonly.iso
mount_cd9660 /dev/md0 /mnt/cdrom
mkdir /usr/local/pxeboot
cp -r /mnt/cdrom /usr/local/pxeboot
umount /mnt/cdrom

The main reason for copying the cd is to edit the file /boot/loader.conf adding the following line:
echo 'vfs.root.mountfrom="ufs:/dev/md0c"' >> /usr/local/pxeboot/boot/loader.conf

This line will make the pxeboot-loader mount the rootfs from a memorydisk instead of the default of mounting a NFS-filesystem.

== NIC with PXE boot ==
For the pxeboot to work you might have to update your NIC with new firmware. See your manufacturer homepage for more information.

== TFTP ==
Next up is starting a tftp-server from which the firmware can load the [http://en.wikipedia.org/wiki/Preboot_Execution_Environment#Network_Bootstrap_Program network bootstrap program] from. This is easiest done by using inetd, remove the leading # from the following line in the file /etc/inetd.conf.
#tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /tftpboot

Make the tftpboot directory and copy the boot/pxeboot file to it.
mkdir /tftpboot
cp /usr/local/pxeboot/boot/pxeboot /tftpboot/

Then start inetd by adding it to rc.conf and starting it.
echo 'inetd_enable="YES"' >> /etc/rc.conf
/etc/rc.d/inetd start

It can be a good idea to start a tail of messages and xferlog file to see what is happening. In another terminal run:
tail -f /var/log/messages /var/log/xferlog

== DHCP ==
Now it's time for the DHCP-server that the firmware will query to get address and path to the network bootstrap program.

Install isc-dhcp3-server
pkg_add -r isc-dhcp3-server

Edit /usr/local/etc/dhcpd.conf adding the following lines.
server-name "pxe-gw"; # name of the tftp-server
server-identifier 172.24.0.4; # address of the tftp-server
next-server 172.24.0.4; # address of the NFS-server

subnet 172.24.0.0 netmask 255.255.255.0 {
range 172.24.0.137 172.24.0.253;
option routers 172.24.0.1;
option root-path "/usr/local/pxeboot"; # root-path for NFS
filename "pxeboot"; # filename of NBP
}

== NFS ==

[[Category : Installation]]

Installing FreeBSD with netboot

2007-03-19T15:54:45Z

Ice: save some more, end of class!

== FreeBSD bootonly ==
The first step to installing FreeBSD via netboot is to acquire FreeBSD. We'll be using the bootonly-iso, this can be fetched at your nearest ftp.

Download the bootonly-iso:
fetch ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/6.2/6.2-RELEASE-i386-bootonly.iso
Mount the iso-image and copy the contents to some location:
mdconfig -a -t vnode -f 6.2-RELEASE-i386-bootonly.iso
mount_cd9660 /dev/md0 /mnt/cdrom
mkdir /usr/local/pxeboot
cp -r /mnt/cdrom /usr/local/pxeboot
umount /mnt/cdrom

The main reason for copying the cd is to edit the file /boot/loader.conf adding the following line:
echo 'vfs.root.mountfrom="ufs:/dev/md0c"' >> /usr/local/pxeboot/boot/loader.conf

This line will make the pxeboot-loader mount the rootfs from a memorydisk instead of the default of mounting a NFS-filesystem.

== NIC with PXE boot ==
For the pxeboot to work you might have to update your NIC with new firmware. See your manufacturer homepage for more information.

== TFTP ==
Next up is starting a tftp-server from which the firmware can load the [http://en.wikipedia.org/wiki/Preboot_Execution_Environment#Network_Bootstrap_Program network bootstrap program] from. This is easiest done by using inetd, remove the leading # from the following line in the file /etc/inetd.conf.
#tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /tftpboot

Make the tftpboot directory and copy the boot/pxeboot file to it.
mkdir /tftpboot
cp /usr/local/pxeboot/boot/pxeboot /tftpboot/

Then start inetd by adding it to rc.conf and starting it.
echo 'inetd_enable="YES"' >> /etc/rc.conf
/etc/rc.d/inetd start

It can be a good idea to start a tail of messages and xferlog file to see what is happening. In another terminal run:
tail -f /var/log/messages /var/log/xferlog

== DHCP ==
Now it's time for the DHCP-server that the firmware will query to get address and path to the network bootstrap program.

Install isc-dhcp3-server
pkg_add -r isc-dhcp3-server

Edit /usr/local/etc/dhcpd.conf adding the following lines.
server-name "pxe-gw"; # name of the tftp-server
server-identifier 172.24.0.4; # address of the tftp-server
next-server 172.24.0.4; # address of the NFS-server

subnet 172.24.0.0 netmask 255.255.255.0 {
range 172.24.0.137 172.24.0.253;
option routers 172.24.0.1;
option root-path "/usr/local/pxeboot"; # root-path for NFS
filename "pxeboot"; # filename of NBP
}

== NFS ==

Installing FreeBSD with netboot

2007-03-19T15:46:36Z

Ice: some more work..

Installing FreeBSD with netboot

2007-03-19T15:36:45Z

Ice: start of freebsd netboot install