To delete options /var/db/ports/$port/options && make install clean again.

First, you’ll want to make sure your timezone is set correctly. Check /usr/share/zoneinfo for the correct time zone file, and copy it to /etc/localtime. I.e.:

bash-2.05b# mv /usr/share/zoneinfo/zonefilehere /etc/localtime

Once you’ve done that, you will need to make sure your date and time are set within at least a few minutes of the current date and time. To do this, use the date command:

bash-2.05b# date 0408290000

The date is in YYMMDDHHMM format, the clock being a 24 hour and not 12 hour clock. To make sure the date looks correct before moving on, just type date in again:

bash-2.05b# date
Sun Aug 29 00:00:33 MDT 2004

Now that our timezone, date, and time are all set correctly, lets setup the NTP daemon to keep the system time synced-up.To do this, open /etc/rc.conf in your editor of choice, and add these lines:

ntpdate_enable=”YES”
ntpdate_program=”ntpdate”
ntpdate_flags=”-b timeserver.org”

Replace timeserver.org with a server from a public NTP timeserver list which is near you (by number of network hops, not necessarily physical location). You’ll need to Google for a list of these yourself. Voila!

== CVSup Method ==

This is a quick method for getting and keeping your copy of the Ports Collection up to date using CVSup protocol. If you want to learn more about CVSup, see Using CVSup.

Note: The implementation of CVSup protocol included with the FreeBSD system is called csup. It first appeared in FreeBSD 6.2. Users of older FreeBSD releases can install it via the net/csup port/package.

Make sure /usr/ports is empty before you run csup for the first time! If you already have the Ports Collection present, obtained from another source, csup will not prune removed patch files.

I. Run csup:

# csup -L 2 -h cvsup.FreeBSD.org /usr/share/examples/cvsup/ports-supfile

Change cvsup.FreeBSD.org to a CVSup server near you. See CVSup Mirrors (Section A.5.7) for a complete listing of mirror sites.

Note: One may want to use his own ports-supfile, for example to avoid the need of passing the CVSup server on the command line. 1. In this case, as root, copy /usr/share/examples/cvsup/ports-supfile to a new location, such as /root or your home directory.
2. Edit ports-supfile.
3. Change CHANGE_THIS.FreeBSD.org to a CVSup server near you. See CVSup Mirrors (Section A.5.7) for a complete listing of mirror sites.
4. And now to run csup, use the following:

# csup -L 2 /root/ports-supfile

II.
Running the csup(1) command later will download and apply all the recent changes to your Ports Collection, except actually rebuilding the ports for your own system.

== Portsnap Method ==

Portsnap is an alternative system for distributing the Ports Collection. It was first included in FreeBSD 6.0. On older systems, you can install it from ports-mgmt/portsnap package:

# pkg_add -r portsnap

Please refer to Using Portsnap for a detailed description of all Portsnap features.

1. Since FreeBSD 6.1-RELEASE and with recent versions of the Portsnap port or package, you can safely skip this step. The /usr/ports will be created automatically at first use of the portsnap(8) command. With previous versions of Portsnap, you will have to create an empty directory /usr/ports if it does not exists:

# mkdir /usr/ports

2. Download a compressed snapshot of the Ports Collection into /var/db/portsnap. You can disconnect from the Internet after this step, if you wish.

# portsnap fetch

3. If you are running Portsnap for the first time, extract the snapshot into /usr/ports:

# portsnap extract

If you already have a populated /usr/ports and you are just updating, run the following command instead:

# portsnap update

== Sysinstall Method ==

This method involves using sysinstall to install the Ports Collection from the installation media. Note that the old copy of Ports Collection from the date of the release will be installed. If you have Internet access, you should always use one of the methods mentioned above.

1. As root, run sysinstall (/stand/sysinstall in FreeBSD versions older than 5.2) as shown below:

# sysinstall

2. Scroll down and select Configure, press Enter.
3. Scroll down and select Distributions, press Enter.
4. Scroll down to ports, press Space.
5. Scroll up to Exit, press Enter.
6. Select your desired installation media, such as CDROM, FTP, and so on.
7. Scroll up to Exit and press Enter.
8. Press X to exit sysinstall.

== Removing Installed Ports ==

Now that you know how to install ports, you are probably wondering how to remove them, just in case you install one and later on decide that you installed the wrong port. We will remove our previous example (which was lsof for those of you not paying attention). Ports are being removed exactly the same as the packages (discussed in the Packages section), using the pkg_delete(1) command:

# pkg_delete lsof-4.57

== Upgrading Ports ==

First, list outdated ports that have a newer version available in the Ports Collection with the pkg_version(1) command:

# pkg_version -v

== Upgrading Ports using Portupgrade ==

The portupgrade utility is designed to easily upgrade installed ports. It is available from the ports-mgmt/portupgrade port. Install it like any other port, using the make install clean command:

# cd /usr/ports/ports-mgmt/portupgrade
# make install clean

Scan the list of installed ports with the pkgdb -F command and fix all the inconsistencies it reports. It is a good idea to do this regularly, before every upgrade.

When you run portupgrade -a, portupgrade will begin to upgrade all the outdated ports installed on your system. Use the -i flag if you want to be asked for confirmation of every individual upgrade.

# portupgrade -ai

If you want to upgrade only a certain application, not all available ports, use portupgrade pkgname. Include the -R flag if portupgrade should first upgrade all the ports required by the given application.

# portupgrade -R firefox

To use packages instead of ports for installation, provide -P flag. With this option portupgrade searches the local directories listed in PKG_PATH, or fetches packages from remote site if it is not found locally. If packages can not be found locally or fetched remotely, portupgrade will use ports. To avoid using ports, specify -PP.

# portupgrade -PP gnome2

To just fetch distfiles (or packages, if -P is specified) without building or installing anything, use -F. For further information see portupgrade(1).

== Upgrading Ports using Portmanager ==

Portmanager is another utility for easy upgrading of installed ports. It is available from the ports-mgmt/portmanager port:

# cd /usr/ports/ports-mgmt/portmanager
# make install clean

All the installed ports can be upgraded using this simple command:

# portmanager -u

You can add the -ui flag to get asked for confirmation of every step Portmanager will perform. Portmanager can also be used to install new ports on the system. Unlike the usual make install clean command, it will upgrade all the dependencies prior to building and installing the selected port.

# portmanager x11/gnome2

If there are any problems regarding the dependencies for the selected port, you can use Portmanager to rebuild all of them in the correct order. Once finished, the problematic port will be rebuilt too.

== Upgrading Ports using Portmaster ==

Portmaster is another utility for upgrading installed ports. Portmaster was designed make use of the tools found in the “base” system (it does not depend upon other ports) and uses the information in /var/db/pkg/ to determine which ports to upgrade. It is available from the ports-mgmt/portmaster port:

# cd /usr/ports/ports-mgmt/portmaster
# make install clean

Portmaster groups ports into four categories:

*

Root ports (no dependencies, not depended on)
*

Trunk ports (no dependencies, are depended on)
*

Branch ports (have dependencies, are depended on)
*

Leaf ports (have dependencies, not depended on)

You can list all the installed ports and search for updates using the -L option:

# portmaster -L
===>>> Root ports (No dependencies, not depended on)
===>>> ispell-3.2.06_18
===>>> screen-4.0.3
===>>> New version available: screen-4.0.3_1
===>>> tcpflow-0.21_1
===>>> 7 root ports
…
===>>> Branch ports (Have dependencies, are depended on)
===>>> apache-2.2.3
===>>> New version available: apache-2.2.8
…
===>>> Leaf ports (Have dependencies, not depended on)
===>>> automake-1.9.6_2
===>>> bash-3.1.17
===>>> New version available: bash-3.2.33
…
===>>> 32 leaf ports

===>>> 137 total installed ports
===>>> 83 have new versions available

All the installed ports can be upgraded using this simple command:

# portmaster -a

Note: By default, Portmaster will make a backup package before deleting the existing port. If the installation of the new version is successful, Portmaster will delete the backup. Using the -b will instruct Portmaster not to automatically delete the backup. Adding the -i option will start Portmaster in interactive mode, prompting you before upgrading each port.

If you encounter errors during the upgrade process, you can use the -f option to upgrade/rebuild all ports:

# portmaster -af

You can also use Portmaster to install new ports on the system, upgrading all dependencies before building and installing the new port:

# portmaster shells/bash

Please see portmaster(8) from more information.

== Ports and Disk Space ==

Using the Ports Collection will use up disk space over time. After building and installing software from the ports, you should always remember to clean up the temporary work directories using the make clean command. You can sweep the whole Ports Collection with the following command:

# portsclean -C

You will accumulate a lot of old source distribution files in the distfiles directory over time. You can remove them by hand, or you can use the following command to delete all the distfiles that are no longer referenced by any ports:

# portsclean -D

Or to remove all distfiles not referenced by any port currently installed on your system:

# portsclean -DD

Note: The portsclean utility is part of the portupgrade suite.

Do not forget to remove the installed ports once you no longer need them. A nice tool to help automate this task is available from the ports-mgmt/pkg_cutleaves port.

To use locate under FreeBSD you first need to run updatedb:

/usr/libexec/locate.updatedb

With a screen editor, you can scroll the page, move
the cursor, delete lines, insert characters, and more, while seeing the results of your
edits as you make them. Screen editors are very popular, since they allow you to make
changes as you read through a file, like you would edit a printed copy, only faster.

Intro

Quitting Without Saving Edits

When you are first learning vi, especially if you are an intrepid experimenter, there are
two other ex commands that are handy for getting out of any mess that you might create.
What if you want to wipe out all of the edits you have made in a session and then return
to the original file? The command:

:e!

To quit :

:q!

”The exclamation point added to the :e or :q command causes vi to override this prohibition, performing the operation
even though the buffer has been modified.”

Saving file

You can save in a new file

:w newfile or :w pathname/file

Delete a file :

:!rm file

Free space:

:!df

Shell commands :

:!ls /tmp
:!sh :!shell (For shell) – :exit to exit or CTRL+D CTRL+Z for background (fg + bg)

You try to write your file, but you get a message telling you that your disk quota has
been reached.
Try to force the system to save your buffer with the ex command :pre (short
for :preserve). If that doesn’t work, look for some files to remove. Use :sh (or
CTRL-Z if you are using a job-control system) to move out of vi and remove files.
Use CTRL-D (or fg) to return to vi when you’re done. Then write your file
with :w!.

vi Commands

vi has two modes: command mode and insert mode. As soon as you enter a file, you
are in command mode, and the editor is waiting for you to enter a command. Commands
enable you to move anywhere in the file, to perform edits, or to enter insert
mode to add new text. Commands can also be given to exit the file (saving or ignoring
your edits) in order to return to the Unix prompt.

Moving the Cursor

In command mode you can position the cursor anywhere in the file. Since you begin
all basic edits (changing, deleting, and copying text) by placing the cursor at the text
that you want to change, you want to be able to move the cursor to that place as quickly
as possible.

Single Movements

The keys h, j, k, and l, right under your fingertips, will move the cursor:

h
Left, one space
j
Down, one line
k
Up, one line
l
Right, one space

You can also use the cursor arrow keys ( ? , ? , ? , ? ), + and – to go up and down, or
the ENTER and BACKSPACE keys, but they are out of the way. At first, it may seem
awkward to use letter keys instead of arrows for cursor movement. After a short while,
though, you’ll find it is one of the things you’ll like best about vi—you can move around
without ever taking your fingers off the center of the keyboard.

Numeric Arguments

You can precede movement commands with numbers. For Ex command 4l moves the cursor four spaces to the right, just as if you had typed l four times
(llll).

e.g 4l – 4 spaces to the right
4h – 4 spaces to the left
4k – 4 lines up
4j – 4 lines down

vi has an option that allows you to set a distance from
the right margin at which vi will automatically insert a newline character. This option
is wrapmargin (its abbreviation is wm). You can set a wrapmargin at 10 characters:

:set wm=10

Movement Within a Line

Two useful commands that involve movement within a line are:

0 (digit zero)
Move to beginning of line.
$
Move to end of line.

Line numbers can be displayed
in vi by using the number option, which is enabled by typing

:set nu in command mode

Tricks:
1). edit $HOME/.vimrc and add : set ts=4 (tab space, default is 8 )

Check ”user” syntax.

# kldload if_gre.ko
# sysctl -w net.inet.ip.gre_default_mtu=1450
# ifconfig gre1 create
# ifconfig gre1 tunnel 217.154.12.2 212.25.240.34
# ifconfig gre1 mtu 1450
# ifconfig gre1 inet 10.1.12.38 10.1.12.37 netmask 255.255.255.252
# ifconfig gre1 up

And that was that!

or Lan :

# ifconfig gre1 inet 10.1.12.37 10.1.12.38 netmask 255.255.255.252 up
# /usr/sbin/greconfig -i gre1 -v -s 212.25.240.34 -d 217.154.12.2

dd if=/dev/zero of=scratch.img bs=3072 count=1000000

and then boot NetBSD using the iso :

qemu scratch.img -cdrom /home/giany/Desktop/i386cd-4.0.iso -boot d

After booting follow these steps:

Follow the instruction screens when the NetBSD installer appears. If a particular step or
choice is not mentioned here then you sould use the default choices.

- choose a custom installation

- select only one of either the GENERIC or GENERIC.MP kernels, depending on the server

- select all sets except Games and x11

- choose to use the entire disk for the NetBSD installation

- Choose to set the sizes of the NetBSD partitions

Partition sizes should be as follows:

Mountpoint Size
/ 2G
swap 2G
/tmp 512G
/var 20G
/usr 20G
/home rest

- choose to use serial port com0 for the bootblock selection

- choose US/Pacific-New as the timezone

- choose MD5 for password encryption

- set the root password

Configure hostname, IP address, default gateway as needed

After the install process close the Qemu window and run qemu using the image that slice.

qemu -m 256 -hda scratch.img -localtime -net nic,vlan=0,macaddr=00:aa:00:00:01:02,model=i82559er -net tap,vlan=0,script=no

and from the linux box:

ifconfig tap1 2.2.2.1 netmask 255.255.255.0 up

Configure the nameserver in /etc/resolv.conf set in /etc/ifconfig.fxp0 the ip address smth like :

inet 2.2.2.2 netmask 255.255.255.0 media autoselect
inet 3.3.3.3 netmask 255.255.255.0 alias // for multiple interfaces
inet 4.4.4.4 netmask 255.255.255.0 alias

My rc.conf file looks like:

hostname="kwala.x83.net"
domainname="x83.net"
auto_ifconfig=YES
defaultroute="2.2.2.1"
wscons=YES
sshd=YES

To add extra packages check this link ftp://ftp.netbsd.org/pub/NetBSD/packages/4.0/i386/All/ and choose what packages you want. I installed bash/net-snmp/perl/tcsh/mtr.
Now you should see the internet from the NetBSD box.

Setup Tripwire (ref: http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/ref-guide/ch-tripwire.html)
Edit the /etc/tripwire/twcfg.txt file to reflect the following:

EDITOR =/usr/bin/pico

Edit the /etc/tripwire/twpol.txt file to reflect the following:

(emailto = "me@me.com")
{
! /proc;
/ -> $(ReadOnly);
! /dev;
/boot -> $(ReadOnly);
/tmp -> $(ReadOnly);
/var/log -> $(ReadOnly);
/var/log/httpd/access_log -> l;
/var/log/httpd/error_log -> l;
}

Install/Setup (only once):

/etc/tripwire/twinstall.sh
site key: web site key
local key: web local key

Initialize:

/usr/sbin/tripwire --init

Check:
/usr/sbin/tripwire --check

View logs:
/usr/sbin/twprint -m r --twrfile /var/lib/tripwire/report/.twr | less

Remove files unneeded by default setup
pico /etc/tripwire/twpol.txt

Generate new policy file:
/usr/sbin/twadmin --create-polfile -S site.key /etc/tripwire/twpol.txt

Initialize again:
/usr/sbin/tripwire --init

Cron will check daily
View logs:
/usr/sbin/twprint -m r --twrfile /var/lib/tripwire/report/.twr | less
Update the database:
/usr/sbin/tripwire --update --twrfile /var/lib/tripwire/report/.twr
Customize.