FreeBSD - Revision history

Ktk: /* SMTP configuration */

2011-05-03T19:42:22Z

SMTP configuration

← Older revision		Revision as of 21:42, 3 May 2011
Line 134:		Line 134:

	===SMTP configuration===		===SMTP configuration===
	If you want your FreeBSD box to be able to send mail the easiest way to go is to configure [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/outgoing-only.html ssmtp]. Note, if you want that the <tt>From:</tt> does '''not''' get overwritten, you have to set this line:		If you want your FreeBSD box to be able to send mail the easiest way to go is to configure [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/outgoing-only.html ssmtp] and [http://wiki.freebsd.org/SecureSSMTP]. Note, if you want that the <tt>From:</tt> does '''not''' get overwritten, you have to set this line:

	FromLineOverride=YES		FromLineOverride=YES

Ktk: /* iSCSI on FreeBSD */

2011-02-21T19:50:36Z

iSCSI on FreeBSD

← Older revision		Revision as of 21:50, 21 February 2011
Line 216:		Line 216:
	* stop jail services		* stop jail services
	* stop jails		* stop jails
	* unmount zfs: <tt>zfs unmount …<tt>		* unmount zfs: <tt>zfs unmount …</tt>
	* <tt>zpool export zpool</tt>		* <tt>zpool export zpool</tt>
	* <tt>/usr/local/etc/rc.d/iscsi stop</tt>		* <tt>/usr/local/etc/rc.d/iscsi stop</tt>

Ktk: /* iSCSI on FreeBSD 7.0 */

2011-02-21T19:50:17Z

iSCSI on FreeBSD 7.0

← Older revision		Revision as of 21:50, 21 February 2011
Line 206:		Line 206:
	login auth sufficient /usr/local/lib/pam_ldap.so		login auth sufficient /usr/local/lib/pam_ldap.so

	==iSCSI on FreeBSD ~~7.0~~==		==iSCSI on FreeBSD==
	Load the iSCSI kernel module or add iSCSI support to your kernel according to http://www.cyberciti.biz/faq/freebsd-iscsi-initiator-howto/. Do not run the <tt>iscontrol</tt> command like stated, that does not work with this syntax.		Load the iSCSI kernel module or add iSCSI support to your kernel according to http://www.cyberciti.biz/faq/freebsd-iscsi-initiator-howto/. Do not run the <tt>iscontrol</tt> command like stated, that does not work with this syntax.

Line 212:		Line 212:

	Note that this is an internal network for freezer in that example, just works if you configured that subnet too for sure.		Note that this is an internal network for freezer in that example, just works if you configured that subnet too for sure.

			For stopping the jails on ZFS/iSCSI properly the following steps are required:
			* stop jail services
			* stop jails
			* unmount zfs: <tt>zfs unmount …<tt>
			* <tt>zpool export zpool</tt>
			* <tt>/usr/local/etc/rc.d/iscsi stop</tt>

	==Configuring mail for the box==		==Configuring mail for the box==

Ktk: /* Basic ports setup */

2010-02-01T14:08:04Z

Basic ports setup

← Older revision		Revision as of 16:08, 1 February 2010
Line 25:		Line 25:
	* Description: csup is used to update our port collection. So far this was done using cvsup but that's depricated and should no longer be used. You do not have to install csup separately as this is shipped with the base system it seems.		* Description: csup is used to update our port collection. So far this was done using cvsup but that's depricated and should no longer be used. You do not have to install csup separately as this is shipped with the base system it seems.
	* Config file: Copy a file from <tt>/usr/share/examples/cvsup</tt> to <tt>/etc</tt>, I recommend to use <tt>ports-supfile</tt> unless you want to update more than just ports.		* Config file: Copy a file from <tt>/usr/share/examples/cvsup</tt> to <tt>/etc</tt>, I recommend to use <tt>ports-supfile</tt> unless you want to update more than just ports.
	* Changes: Adjust the <tt>~~hosts~~=</tt> entry to <tt>~~hosts~~=cvsup.ch.freebsd.org</tt>		* Changes: Adjust the <tt>host=</tt> entry to <tt>host=cvsup.ch.freebsd.org</tt>
	* Documentation: [http://www.freebsd.org/doc/en/books/handbook/cvsup.html Using CVSUp]		* Documentation: [http://www.freebsd.org/doc/en/books/handbook/cvsup.html Using CVSUp]

Ktk: /* Configuring mail for the box */

2010-01-01T18:51:14Z

Configuring mail for the box

← Older revision		Revision as of 20:51, 1 January 2010
Line 216:		Line 216:
	We either have to read the mail for the root user on a regular base (using <tt>mail</tt> for example) or we forward the mails to an external mailbox (recommended we forget it anyway otherwise ;).		We either have to read the mail for the root user on a regular base (using <tt>mail</tt> for example) or we forward the mails to an external mailbox (recommended we forget it anyway otherwise ;).

	Do do that we have to edit the file </etc/aliases</tt>. It should contain:		Do do that we have to edit the file <tt>/etc/aliases</tt>. It should contain:

	root: myself@somedomain.org		root: myself@somedomain.org

	When you edited that run the command <tt>newaliases</tt> to activate the changes.		When you edited that run the command <tt>newaliases</tt> to activate the changes.

Ktk at 16:08, 30 April 2009

2009-04-30T16:08:31Z

← Older revision		Revision as of 18:08, 30 April 2009
Line 212:		Line 212:

	Note that this is an internal network for freezer in that example, just works if you configured that subnet too for sure.		Note that this is an internal network for freezer in that example, just works if you configured that subnet too for sure.

			==Configuring mail for the box==
			We either have to read the mail for the root user on a regular base (using <tt>mail</tt> for example) or we forward the mails to an external mailbox (recommended we forget it anyway otherwise ;).

			Do do that we have to edit the file </etc/aliases</tt>. It should contain:

			root: myself@somedomain.org

			When you edited that run the command <tt>newaliases</tt> to activate the changes.

Ktk: /* Upgrading Ports */

2009-03-02T11:47:34Z

Upgrading Ports

← Older revision		Revision as of 13:47, 2 March 2009
Line 82:		Line 82:
	portupgrade -rR pkgname: This will update the package itself, but will first compile all things on which that package depends including all other ports that depend on our upgraded package. Like this a package and its dependencies are really up to date.		portupgrade -rR pkgname: This will update the package itself, but will first compile all things on which that package depends including all other ports that depend on our upgraded package. Like this a package and its dependencies are really up to date.

	~~(see also~~: [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html FreeBSD handbook, using ports])		References:
			* [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html FreeBSD handbook, using ports])
			* [http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html?page=2 OnLAMP.com article]

	===Flags for Ports===		===Flags for Ports===

Ktk at 11:45, 2 March 2009

2009-03-02T11:45:55Z

← Older revision		Revision as of 13:45, 2 March 2009
Line 78:		Line 78:
	pkgdb -F		pkgdb -F
	* run portupgrade:		* run portupgrade:
	portupgrade -a		portupgrade -arR: will update all packages, including all dependencies. I usually don't do that as this is a lot of work for making sure all services still work fine aftewards, at least on a bit more complex server setups. I prefer the second way of upgrading a single packet at a time only:
	* to update a single package:		* to update a single package:
	portupgrade pkgname		portupgrade -rR pkgname: This will update the package itself, but will first compile all things on which that package depends including all other ports that depend on our upgraded package. Like this a package and its dependencies are really up to date.

	(see also: [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html FreeBSD handbook, using ports])		(see also: [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html FreeBSD handbook, using ports])

Ktk: /* net/cvsup-without-gui */

2009-02-20T15:05:48Z

net/cvsup-without-gui

← Older revision		Revision as of 17:05, 20 February 2009
Line 22:		Line 22:
	==Basic ports setup==		==Basic ports setup==
	I usually just install source packages from ports for my servers. This makes it possible to adjust it to my needs and stay up to date when required. We start with some basic ports.		I usually just install source packages from ports for my servers. This makes it possible to adjust it to my needs and stay up to date when required. We start with some basic ports.
	====net/~~cvsup-without-gui~~====		====net/csup====
	* Description: ~~cvsup~~ is used to update our port collection~~, we~~ install the ~~version without GUI so no X11 dependencies will be installed~~		* Description: csup is used to update our port collection. So far this was done using cvsup but that's depricated and should no longer be used. You do not have to install csup separately as this is shipped with the base system it seems.
	* Config file: Copy a file from <tt>/usr/share/examples/cvsup</tt> to <tt>/etc</tt>, I recommend to use <tt>ports-supfile</tt> unless you want to update more than just ports.		* Config file: Copy a file from <tt>/usr/share/examples/cvsup</tt> to <tt>/etc</tt>, I recommend to use <tt>ports-supfile</tt> unless you want to update more than just ports.
	* Changes: Adjust the <tt>hosts=</tt> entry to <tt>hosts=cvsup.ch.freebsd.org</tt>		* Changes: Adjust the <tt>hosts=</tt> entry to <tt>hosts=cvsup.ch.freebsd.org</tt>
			* Documentation: [http://www.freebsd.org/doc/en/books/handbook/cvsup.html Using CVSUp]

	====net/openntpd====		====net/openntpd====

Ktk: /* Basic ports setup */

2009-02-19T10:03:43Z

Basic ports setup

← Older revision		Revision as of 12:03, 19 February 2009
Line 21:		Line 21:

	==Basic ports setup==		==Basic ports setup==
			I usually just install source packages from ports for my servers. This makes it possible to adjust it to my needs and stay up to date when required. We start with some basic ports.
	====net/cvsup-without-gui====		====net/cvsup-without-gui====
	* Description: cvsup is used to update our port collection, we install the version without GUI so no X11 dependencies will be installed		* Description: cvsup is used to update our port collection, we install the version without GUI so no X11 dependencies will be installed