unix86.org

On Linux system, we can run /etc/init.d/network restart to restart networking servrices. But, on FreeBSD, it is different.

With FreeBSD 7, to start FreeBSD networking services, run:

/etc/rc.d/netif  start

To stop FreeBSD networking services:

/etc/rc.d/netif  stop

and restart the FreeBSD network services, run:

/etc/rc.d/netif  restart

Configure FreeBSD networking manually

Usually, on all Unix/Linux and Unix-like systems, we can use ifconfig command to configure network interface and IP address.

On FreeBSD 7, to shutdown a network interface, run:

ifconfig  em0  down

To bring up a NIC, run:

ifconfig  em0  up

You can run ifconfig -a to list all interfaces with IP address, netmask, MAC address and other NIC information.

To list all shuted down NIC, run:

ifconfig  -d

To list all up and running NIC, run:

ifconfig  -u

For more information about ifconfig, run:

man  ifconfig

FreeBSD supports three methods for installing programs/packages:

FreeBSD Ports (Source Code)
Packages
Source Codes (Download source codes)

To install package via FreeBSD ports:

1. cd /usr/ports
2. make search name="package_name"
3. cd /usr/ports/package_name
4. make
5. make install

To install package via .tgz package:

1. pkg_add -r package_name.tgz

To install package via source code:

wget http://package-site.com/package-name-version.tar.gz

tar -zxf package-name-version.tar.gz
cd package-name-version
./configure
make
make install

Q. How do I upgrade FreeBSD 7.0 server to latest 7.1 server with stock GENERIC kernel installed?

A. The freebsd-update utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.0-RELEASE, 7.1-BETA, 7.1-BETA2, 7.1-RC1, or 7.1-RC2 can be only upgrade as follows.

Login as root user and type the command:

# freebsd-update upgrade -r 7.1-RELEASE
During this process, FreeBSD Update may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly.
# freebsd-update install
The system must be rebooted with the newly installed kernel before continuing.
# reboot
After rebooting, freebsd-update needs to be run again to install the new userland components, and the system needs to be rebooted again:
# freebsd-update install
Users of Intel network interfaces which are changing their name from “em” to “igb” should make necessary changes to configuration files BEFORE running freebsd-update, since otherwise the network interface will not be configured appropriately after rebooting for the first time, especially firewall and other networking options in /etc/rc.conf file.
# reboot

Users of earlier FreeBSD releases (FreeBSD 6.x) can also use freebsd-update to upgrade to FreeBSD 7.1, but will be prompted to rebuild all third-party applications (e.g., anything installed from the ports tree) after the second invocation of “freebsd-update install”, in order to handle differences in the system libraries between FreeBSD 6.x and FreeBSD 7.x.

Upgrade all packages

You also need to update all packages, type:
# portsnap fetch update
# pkg_version -vIL=
# portupgrade -a

Notes from following Life with DJBDNS, Quick & Dirty Guide to djbDNS and DJBDNS on FreeBSD HOW-TO (thanks, guys!) to set up an authoritative and caching nameserver using FreeBSD jails.
Requirements

Normally, when setting up tinydns and dnscache on the same host, you need two IP-addressees, one for each service. In practice this hardly is an obstacle because often one of the two can be a private address or even 127.0.0.1 and the strict separation of resolver and nameserver far outweighs this.

However, this has proven to be a somewhat annoying limitation in conjunction with FreeBSD jails because a) you can only assign one IP per jail and b) you can’t use 127.0.0.1 from inside a jail.

So until someone smarter than me comes up with something sexy I’ll just assume that I’ll need two jails for a setup involving dnscache and tinydns. The general idea is to provide a local network with a caching DNS server as well as be authoritative for that domain and provide name resolution for local machines. (Believe me, setting up something like this for local networks is well worth the effort – the importance of a working, sane DNS setup simply cannot be overstated!)
DNS cache

This will be the host that all clients in the network will use as their nameserver. It will serve non-authoritative answers for foreign domains and authoritative answers for the local network (which it obtains from the DNS jail which we’ll setup below). We’re assuming the fictitional address 1.2.3.4

* install from ports /usr/ports/dns/djbdns
* add users dnscache, tinydns and dnslog:

groupadd dnsusers
pw useradd dnscache -s /bin/nologin
pw useradd dnslog -s /bin/nologin
pw groupmod dnsusers -m dnscache,dnslog
 
mkdir /var/log/dnscache
dnscache-conf dnscache dnslog /var/dnscache 1.2.3.4

*  modify /var/dnscache/log/run thus:

exec setuidgid dnslog multilog t /var/log/dnscache

* enable queries from the local network:

touch /var/dnscache/root/ip/1.2.3

* set ownership:

chown -R dnscache:dnsusers /var/dnscache ; chown -R dnslog:dnsusers /var/log/dnscache ;

* services: we need to enable svscan and create a link to the directory created by dnscache-conf

mkdir /var/service/
cat "svscan_enable="YES" >> /etc/rc.conf
ln -s /var/dnscache /var/service/
/usr/local/etc/rc.d/svscan.sh start

You should now be able to perform lookups at the 1.2.3.4 addresse: dig @1.2.3.4 tomster.org
Authoritative DNS
We’re assuming the fictitional address 1.2.3.5.
* install from ports /usr/ports/dns/djbdns
* add users tinydns, tinydns and dnslog:

groupadd dnsusers
pw useradd tinydns -s /bin/nologin
pw useradd dnslog -s /bin/nologin
pw groupmod dnsusers -m tinydns,dnslog
 
mkdir /var/log/tinydns
tinydns-conf tinydns dnslog /var/tinydns 1.2.3.5

*  modify /var/tinydns/log/run thus:

exec setuidgid dnslog multilog t /var/log/tinydns

* set ownership:

chown -R tinydns:dnsusers /var/tinydns ; chown -R dnslog:dnsusers /var/log/tinydns ;

* services: we need to enable svscan and create a link to the directory created by tinydns-conf

mkdir /var/service/
cat "svscan_enable="YES" >> /etc/rc.conf
ln -s /var/tinydns /var/service/
/usr/local/etc/rc.d/svscan.sh start

* edit /var/tinydns/root/data to create your local zones
* after editing, cd to /var/tinydns/root and run “make”. This compiles the data.cdb which tinydns reads.
Regarding reverse lookups: While it’s true, that =-entries in the data file create both A and PTR records, you will still need to add a SOA entry for the reverse domain inside your data file, i.e.:

.3.2.1.in-addr.arpa:tinydns.yourdomain.com

Otherwise, tinydns will never deliver any answers to reverse queries to your IPs.
Voila! Try some dig @1.2.3.5 queries for some of the hosts you defined.
tying it together
Now all we need to do is to tell the dnscache about tinydns and the domains (including reverse) it’s authoritative for. This is done by creating a textfile with the name of the domain containing the IP of the nameserver responsible for it inside /var/dnscache/root/servers

cat 1.2.3.5 > /var/dnscache/root/servers/yourdomain.com
cat 1.2.3.5 > /var/dnscache/root/servers/3.2.1.in-addr.arpa

https://blog.tinlans.org/2009/01/23/%E6%8A%8A-freebsd-71-%E7%9B%B4%E6%8E%A5%E5%AE%89%E8%A3%9D%E5%9C%A8-2tb-%E4%BB%A5%E4%B8%8A%E7%9A%84%E7%A1%AC%E7%A2%9F%E8%A3%A1/

http://www.freebsd.org/doc/zh_TW/books/handbook/install-diff-media.html

1. Power on the virtual machine.

2. After the guest operating system has started, prepare your virtual machine to install VMware Tools.

Choose VM > Install VMware Tools.

The remaining steps take place inside the virtual machine.

3. Be sure the guest operating system is running in text mode. You cannot install VMware Tools from a terminal in an X window session.

Some recent distributions of Linux are configured to run the X server when they boot and do not provide an easy way to stop the X server. However, you can switch to a different workspace that is still in text mode and install VMware Tools from that workspace.

To switch between Linux workspaces in a virtual machine, press Ctrl-Alt-Space, release Space without releasing Ctrl and Alt, then press the function key for the workspace you want to use — for example, F2.

Note: If you changed your hot-key combination to something other than Ctrl-Alt, use that combination with Space and the function key.

4. As root (su -), mount the VMware Tools virtual CD-ROM image, change to a working directory (for example, /tmp), uncompress the installer, then unmount the CD-ROM image.

Note: You do not use an actual CD-ROM to install VMware Tools, nor do you need to download the CD-ROM image or burn a physical CD-ROM of this image file. The GSX Server software contains an ISO image that looks like a CD-ROM to your guest operating system. This image contains all the files needed to install VMware Tools in your guest operating system.

Linux Guests: Some Linux distributions use different device names or organize the /dev directory differently. If your CD-ROM drive is not /dev/cdrom or if the mount point for a CD-ROM is not /mnt/cdrom, modify the following commands to reflect the conventions used by your distribution.

Further, some Linux distributions automatically mount CD-ROMs. If your distribution uses automounting, do not use the mount and umount commands below. You still must untar the VMware Tools installer to /tmp.

mount /dev/cdrom /mnt/cdrom
cd /tmp
tar zxf /mnt/cdrom/vmware-linux-tools.tar.gz
umount /mnt/cdrom

FreeBSD Guests: Some FreeBSD distributions automatically mount CD-ROMs. If your distribution uses automounting, do not use the mount and umount commands below. You still must untar the VMware Tools installer to /tmp.

mount /cdrom
cd /tmp
tar zxf /cdrom/vmware-freebsd-tools.tar.gz
umount /cdrom

5. Run the VMware Tools installer.

cd vmware-tools-distrib
./vmware-install.pl

6. Answer the questions about default directories.

7. Run the configuration program.
vmware-config-tools.pl

8. To change your virtual machine’s display resolution, answer yes, then enter the number that corresponds to the desired resolution.

9. Log off of the root account.

exit

10. Start X and your graphical environment.

11. In an X terminal, launch the VMware Tools background application.

vmware-toolbox &

You can run VMware Tools as root or as a normal user. To shrink virtual disks, you must run VMware Tools as root (su -).

Note: To get the greatest benefit from the features of VMware Tools, always run vmware-toolbox in the guest operating system.

Starting VMware Tools Automatically

You may find it helpful to configure your guest operating system so VMware Tools starts when you start your X server. The steps for doing so vary depending on your Linux distribution and your desktop environment. Check your operating system documentation for the appropriate steps to take.

For example, in a Red Hat Linux 7.1 guest using GNOME, follow these steps.

1. Open the Startup Programs screen in the GNOME Control Center.

Main Menu (click the foot icon in the lower left corner of the screen) > Programs > Settings > Session > Startup Programs

2. Click Add.

3. In the Startup Command field, enter vmware-toolbox.

4. Click OK, click OK again, then close the GNOME Control Center.

The next time you start X, VMware Tools starts automatically.

Starting VMware Tools in a FreeBSD 4.5 Guest Operating System

In a FreeBSD 4.5 guest operating system, sometimes VMware Tools does not start after you install VMware Tools, reboot the guest operating system or start VMware Tools on the command line in the guest. An error message appears:

Shared object ‘libc.so.3′ not found.

The required library was not installed. This does not happen with full installations of FreeBSD 4.5, but does occur for minimal installations. To fix the problem of the missing library, take the following steps:

1. Insert and mount the FreeBSD 4.5 installation CD or access the ISO image file.

2. Change directories and run the installation script.

cd /cdrom/compat3x
./install.sh

Uninstalling VMware Tools

If you need to remove VMware Tools from your Linux guest operating system, log on as root (su -) and run the following command:

vmware-uninstall-tools.pl

Mothed 1:

mount /cdrom

Method 2:

mount -t cd9660 /dev/acd0 /mnt

Mount Floppy Disk

mount -t msdos /dev/fd0 /floppy

Mount NFS

mount -t nfs remote:/directory /mnt

Mount NTFS

mount -t ntfs /dev/ad0s1 /mnt

Mount ZIP disk

mount -t msdos /dev/afd0s4 /mnt/zip

Mount USB disk (Request Kernel Support)

device scbus

device da

device cd

mount -t msdos /dev/da0 /mnt/usb

Floppy Disk

fdformat -f 1440 /dev/fd0

disklabel -B -r -w /dev/fd0 fd1440label

create New File System on Floppy Disk

newfs_msdos /dev/fd0

mount_msdosfs /dev/fd0 /floppy

Mount ISO image

mdconfig -a -t vnode -f filename.iso -u 1

mount_cd9660 /dev/md1 /cdrom

For 4.8 edition

vnconfig /dev/vn0 /home/pcman/filename.iso

mount -t cd9660 /dev/vn0 /cdrom

umount /cdrom

vnconfig -u /dev/vn0

Other MOUNT command

mount_msdosfs

mount_msdos

mount_ntfs

GNOME is a complete desktop environment (no matter what Linus says ). In GNOME, everything is easy to use, and works the way you want.

So how do you install Gnome Desktop system under FreeBSD?

These days it is quite easy to install Gnome Desktop system under FreeBSD. You have following choices (use only one of the method).

Option # 1: Fetch and install Gnome binary package from Internet

To install GNOME 2.16 from binary package over Internet or local FTP server type the command:
# pkg_add -v -r gnome2

Now proceed to post installation instructions.

Option # 2: Install Gnome binary package from CD/DVD

Login as root and type sysinstall:
# /usr/sbin/sysinstall

Select Configure > Packages > CD/DVD > Gnome

Select all packages and hit install button

Now proceed to post installation instructions.

Option # 3: Install Gnome using FreeBSD ports system

To compile and build Gnome type the following command:
# cd /usr/ports/x11/gnome2
# make clean; make install clean
Now proceed to post installation instructions.

Enable and start GNOME automatically

You need to start all of the GNOME-related services when system comes (at boot time). All you need to do is add following line to /etc/rc.conf file:
Open /etc/rc.conf file:
# vi /etc/rc.conf
Append following line:
gnome_enable="YES"
Save close the file.

If you have other system such as KDE and just want gnome as default add the following line to ~/.xsession or ~/.xinitrc file so that GNOME 2.16 can be started as soon as you type startx command:
echo 'exec gnome-session' >> ~/.xsession

How do I use Gnome?

You can login using GDM or simply type the command:
$ startx

Further recommended readings

• FreeBSD Handbook: Chapter 5 The X Window System
• You can also try out PC-BSD which is also good desktop system based on rock-solid FreeBSD.

There are two ways to install GNOME 2.14 on FreeBSD. One way is to use packages, and the other way is to use ports. Before doing either installation, you should first familiarize yourself with the GNOME 2.14 release notes.

Install GNOME 2.14 from packages.

To install GNOME 2.14 from packages, use the command:

# pkg_add -r gnome2

This will download the latest GNOME 2.14 packages from the FreeBSD FTP site, and proceed to install them on your system.

Up-to-date GNOME packages for i386 and amd64 for all supported versions of FreeBSD are also available from the GNOME Tinderbox.

To build GNOME 2.14, you must first obtain the latest ports tree skeleton. This is most easily accomplished with portsnap(8) or cvsup. Then:

# cd /usr/ports/x11/gnome2
# make clean
# make install clean

Enable File Alteration Monitor (FAM) support for your 2.14 desktop.

GNOME includes support for the File Alteration Monitor (devel/gamin) by default, in order to improve the GNOME desktop’s ability to respond to files being added, deleted, or modified by other programs.

Make GNOME 2.14 start when X starts.

Once you have the GNOME 2.14 desktop installed, GNOME 2.14 can be started by adding the following line to ~/.xsession or ~/.xinitrc, as appropriate:

exec gnome-session

Important Note

Only the core desktop is included in the gnome2 package. Here are some other GNOME meta-ports that offer convenient groupings of popular GNOME 2 software.

• GNOME 2 Fifth Toe (x11/gnome2-fifth-toe) consists of stable GNOME 2 applications that many users expect to find in a functional desktop environment. This includes image manipulation applications, chat and instant messenger applications, and music and multimedia players.
• GNOME 2 Hacker Tools (devel/gnome2-hacker-tools) consists of applications developers would need to create and maintain GNOME software projects. This includes IDEs, interface builders, “hacker” editors, and code generation tools.
• GNOME 2 Office (editors/gnome2-office) consists of applications that are commonly found in office or productivity suites. This includes a spreadsheet application, word processor, project management application, database access application, groupware suite, and diagramming application.
• GNOME 2 Power Tools (x11/gnome2-power-tools) consists of utilities and applets for the technically-minded GNOME user. It also contains many useful add-on utilities for some of the applications found in the Desktop and Fifth Toe.

To install any of these from packages:

# pkg_add -r meta-port

For example, to install the GNOME 2 Fifth Toe from packages:

# pkg_add -r gnome2-fifth-toe

To install any of these from ports:

# cd /usr/ports/category/meta-port
# make clean
# make install clean

For example, to install the GNOME 2 Fifth Toe from ports:

# cd /usr/ports/x11/gnome2-fifth-toe
# make clean
# make install clean

Method 1: (With CD-ROM or DVD disc)

1. Login into system as root

2. run /usr/sbin/sysinstall

3. Select “Configure” -> “Packages” -> CD -> GNOME

or

mount /cdrom

cd /cdrom/packages/all

pkg_add gnome2

Method 2: (Using ports and build from sources)

1. cd /usr/ports/X11/gnome2

2. make install clean

Method 3: (Using pkg_add to download gnome via ftp.freebsd.org)

pkg_add -r -v  gnome2

—–

echo “/usr/X11R6/bin/gnome-session” > ~/.xinitrc

startx

——

vi /etc/rc.config

gnome_enable=”YES”

—–

Remove GNOME

1. cd /var/db/pkg

2. pkg_delete  gnome2

-

cd /var/db/pkg/gnome2

make deinstall