Da Kiwi

deinstall_removed_port

anonymous@undisclosed.example.com (Anonymous) — Thu, 30 Jan 2020 10:00:07 +0000

2026/06/27 16:09	current
Line 1:	Line 1:
	+	====== Deinstall an already removed port on FreeBSD ======

	+	Sometimes we use alternate ports (in my case, openssl111, to get TLS 1.3 under nginx), and the port get replaced by another version (openssl111 got deleted and openssl was upgraded to 1.1.1)
	+
	+	pkg will process dependencies and uninstall all software built against openssl111. And we cannot "make deinstall" openssl111 as the port has been removed.
	+
	+	So assuming we are replacing a port with another one with the same version, we can create a temporary port. I use jails so I have to do this in basejail:
	+
	+	<code>
	+	cd /path/to/basejail/usr/ports
	+	cp -vrp openssl openssl111
	+	sed -i bak s/openssl/openssl111/ openssl111/Makefile
	+	cd openssl111
	+	make deinstall
	+	</code>
	+
	+	Voila! You just have to install openssl now.

nagios_toaster

anonymous@undisclosed.example.com (Anonymous) — Wed, 21 Jun 2023 20:27:24 +0000

2013/08/18 22:27		current
Line 42:		Line 42:
	==== NConf integration ====		==== NConf integration ====
	* Add a link in the Nuvola menu. Edit /www/monitor/nagios/side/dtree_data.js, and add the following line at the end, just before the //document.write(configuration);// statemement:		* Add a link in the Nuvola menu. Edit /www/monitor/nagios/side/dtree_data.js, and add the following line at the end, just before the //document.write(configuration);// statemement:
		+
	<code js>		<code js>
	configuration.add(5,0,'Administration','/nconf/','','','side/icons/configuration.gif');		configuration.add(5,0,'Administration','/nconf/','','','side/icons/configuration.gif');

ipsec

anonymous@undisclosed.example.com (Anonymous) — Fri, 09 Mar 2012 21:43:38 +0000

2011/01/30 14:26		current
Line 1:		Line 1:
	====== IPSec for FreeBSD's jails communication ======		====== IPSec for FreeBSD's jails communication ======

-	Abstract: Here we assume we have two FreeBSD hosts, A using public IP 1.1.1.1 and internal virtual net 192.168.3.0 for jails, and B using public IP 2.2.2.2 and internal net 192.168.6.0 for jails. We need hosts and jails to communicate together, preferably in a encrypted way.	+	Abstract: Here we assume we have two FreeBSD hosts, A using public IP 1.1.1.1 and internal virtual net 192.168.3.0 for jails, and B using public IP 2.2.2.2 and internal net 192.168.6.0 for jails. We need hosts and jails to communicate together, preferably in a crypted way.

	===== Preparation on both hosts =====		===== Preparation on both hosts =====

openvpn

anonymous@undisclosed.example.com (Anonymous) — Sat, 06 Mar 2010 00:00:03 +0000

2010/03/06 00:56		current
Line 312:		Line 312:
	</code>		</code>

-	A zip file name <user>_vpn.zip will the be created in /tmp/ with all necessary files, send it to the user via encrypted channel; if you really do want to send it over e-mail, you can use [[http://caspian.dotconf.net/menu/Software/SendEmail/\|SendEmail]]:	+	A zip file name j.doe_vpn.zip will the be created in /tmp/ with all necessary files, send it to the user via encrypted channel; if you really do want to send it over e-mail, you can use [[http://caspian.dotconf.net/menu/Software/SendEmail/\|SendEmail]]:

	<code>		<code>
-	# sendEmail -f <sender> -t <recipient> -u "VPN certificate" -m "here it is." -a /tmp/<user>_vpn.zip	+	# sendEmail -f vpn@example.com -t j.doe@example.com -u "VPN certificate" -m "here it is." -a /tmp/j.doe_vpn.zip
	</code>		</code>

gemini_toaster

anonymous@undisclosed.example.com (Anonymous) — Wed, 21 Jun 2023 20:38:51 +0000

2022/06/18 16:08		current
Line 52:		Line 52:

	* Add the following lines to /etc/inetd.conf. Adjust -d parameter to previously created user's home directory, don't forget the last slash:		* Add the following lines to /etc/inetd.conf. Adjust -d parameter to previously created user's home directory, don't forget the last slash:
		+
	<code>		<code>
	gemini stream tcp nowait gemini /usr/local/bin/vger vger -v -i -d /home/gemini/		gemini stream tcp nowait gemini /usr/local/bin/vger vger -v -i -d /home/gemini/
Line 58:		Line 59:

	* Activate inetd either by issuing		* Activate inetd either by issuing
		+
	<code bash>		<code bash>
	# sysrc inetd_enable="YES"		# sysrc inetd_enable="YES"
Line 63:		Line 65:

	or, if you use separate files:		or, if you use separate files:
		+
	<code bash>		<code bash>
	# echo "inetd_enable=\"YES\"">/usr/local/etc/rc.conf.d/inetd		# echo "inetd_enable=\"YES\"">/usr/local/etc/rc.conf.d/inetd

groupware_toaster

anonymous@undisclosed.example.com (Anonymous) — Wed, 21 Jun 2023 20:35:39 +0000

2023/06/11 01:27		current
Line 147:		Line 147:

	* If using classic skin, replace the strange "interrogation mark" button by a prettier one:		* If using classic skin, replace the strange "interrogation mark" button by a prettier one:
		+
	<code bash>		<code bash>
	mv plugins/agendav/skins/classic/agendav.gif plugins/agendav/skins/classic/agendav.old.gif		mv plugins/agendav/skins/classic/agendav.gif plugins/agendav/skins/classic/agendav.old.gif

postgresql_upgrade_on_freebsd

anonymous@undisclosed.example.com (Anonymous) — Mon, 29 Sep 2025 11:54:15 +0000

2023/09/25 16:51		current
Line 2:		Line 2:

	For minimal downtime during migration, we will use `pg_upgrade` tool, which needs both old and new PostgreSQL binaries available. To do so, we will use FreeBSD's ports system, without `make clean` at first to keep compiled binaries.		For minimal downtime during migration, we will use `pg_upgrade` tool, which needs both old and new PostgreSQL binaries available. To do so, we will use FreeBSD's ports system, without `make clean` at first to keep compiled binaries.
-
	## A note about locales		## A note about locales

-	You might encounter weird locales issue while ensuing `initdb` command, like this:	+	You might encounter weird locale issue while ensuing `initdb` command, like this:

	```bash		```bash
Line 11:		Line 10:
	```		```

-	The only workaround I found was to disable locale detection in the source code:	+	This seems to be caused by a [remaining deprecated locale](https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274718#c12). You can delete it by using the following command, depending on if you're running PostgreSQL in a jail (I didn't find a cleaner way, sorry):

-	```diff	+	```bash
-	--- /var/ports/basejail/usr/ports/databases/postgresql15-server/work/postgresql-15.2/src/backend/utils/adt/pg_locale.c 2023-08-22 18:55:52.003715000 +0200	+	sudo rm -rf /usr/share/locale/sr_YU.ISO8859-5
-	+++ /tmp/pg_locale.c 2023-08-22 18:54:40.437733000 +0200	+	sudo rm -rf /basejail/usr/share/locale/sr_YU.ISO8859-5
-	@@ -1727,8 +1727,8 @@	+
-	freelocale(loc);	+
-	}	+
-	else	+
-	- // ereport(ERROR,	+
-	- // (errmsg("could not load locale \"%s\"", collcollate)));	+
-	+ ereport(ERROR,	+
-	+ (errmsg("could not load locale \"%s\"", collcollate)));	+
-	#elif defined(WIN32) && _WIN32_WINNT >= 0x0600	+
-	/*	+
-	* If we are targeting Windows Vista and above, we can ask for a name	+
	```		```
-
-	You can apply this patch while compiling new version's port (issue `make`, stop it with ctrl+c after download and extract, patch, then issue `make` again)

	## Compile old and new version from ports		## Compile old and new version from ports

ssh

anonymous@undisclosed.example.com (Anonymous) — Wed, 21 Jun 2023 20:30:04 +0000

2013/12/09 02:12		current
Line 46:		Line 46:
	* install some proxy software (i.e., Squid)		* install some proxy software (i.e., Squid)
	* connect to the server, and map a port to the proxy's one:		* connect to the server, and map a port to the proxy's one:
		+
		+
	<code>		<code>
	ssh -R8181:localhost:3128 server_to_connect_to		ssh -R8181:localhost:3128 server_to_connect_to
	</code>		</code>
	* once connected, enter:		* once connected, enter:
		+
	<code>		<code>
	export http_proxy=http://127.0.0.1:8181		export http_proxy=http://127.0.0.1:8181

vpn_vs_proxies

anonymous@undisclosed.example.com (Anonymous) — Tue, 21 Feb 2012 17:42:57 +0000

2012/02/21 18:41		current
Line 23:		Line 23:

	<code>		<code>
-	port-share //remoteserver// 443	+	port-share remoteserver 443
	</code>		</code>

dokuwiki_goes_mobile

anonymous@undisclosed.example.com (Anonymous) — Thu, 12 Mar 2015 20:24:12 +0000

2012/03/24 12:03		current
Line 1:		Line 1:
		+	WARNING: This hack does not work anymore, but you can now handle mobile skins in a much proper way through the [[https://www.dokuwiki.org/plugin:loadskin\|loadskin]] plugin.
		+
	====== Making dokuwiki handle mobile devices ======		====== Making dokuwiki handle mobile devices ======
	===== Install some mobile template =====		===== Install some mobile template =====