Comments for The Ignorant Hack

Comment on The short list #5: coredumping with sudo on #FreeBSD by Sean

Sean — Wed, 26 Mar 2014 16:48:48 +0000

I wish I was that sneaky. You are correct. It should be set to false if you want it to work.

Comment on The short list #5: coredumping with sudo on #FreeBSD by Peter Pentchev

Peter Pentchev — Wed, 26 Mar 2014 10:22:05 +0000

Errr… are you sure that you don’t mean “Set disable_coredump false”? 🙂 Or was that meant as an additional hurdle to people who blindly copy stuff from random websites and run it without really thinking about what it means? 🙂

Comment on How I learned to stop worrying and love the powderkeg. #FreeBSD by Peter Wemm

Peter Wemm — Tue, 04 Mar 2014 07:24:14 +0000

BTW; with regards to finding your initial list of ports to build based on a working system, one (relatively) easy way is with portmaster itself.

# portmaster –list-origins | sort

Fair warning: you probably want to do a
# pkg autoremove
.. first to get rid of the build time dependencies that may be laying around. If you don’t do this, your –list-origins output will be huge as each not-needed build tool will be a “leaf”.

Comment on How I learned to stop worrying and love the powderkeg. #FreeBSD by Tom Lazar

Tom Lazar — Wed, 08 Jan 2014 15:35:21 +0000

two corrections to my previous post: 1. don't edit /usr/local/poudriere/jails/92amd64/etc/make.conf directly, instead edit /usr/local/etc/poudriere.d/92amd64-make.conf 2. the syntax for the options is editors_libreoffice_UNSET+=CUPS not editors_libreoffice_OPTIONS_FILE_UNSET+=CUPS

Comment on How I learned to stop worrying and love the powderkeg. #FreeBSD by Tom Lazar

Tom Lazar — Wed, 08 Jan 2014 13:38:40 +0000

to clarify what feld said: you set the options in the make.conf of each poudriere jail (i.e. /usr/local/poudriere/jails/92amd64/etc/make.conf) using the 'new style' options syntax as described in https://wiki.freebsd.org/Ports/Options/OptionsNG) i.e. editors_libreoffice_OPTIONS_FILE_UNSET+=CUPS

Comment on How I learned to stop worrying and love the powderkeg. #FreeBSD by feld

feld — Tue, 19 Nov 2013 01:38:31 +0000

In reply to Vince Hoffman. Please keep in mind that populating the options as Vince detailed above is dangerous. Poudriere will never attempt to tell you if the default options have changed or if options you have set have been renamed or removed. The right thing to do is carefully extract which options you have changed and put them in your poudriere make.conf for easy review and adjustment later.

Comment on How I learned to stop worrying and love the powderkeg. #FreeBSD by Vince Hoffman

Vince Hoffman — Sun, 03 Nov 2013 21:33:27 +0000

One thing you have either missed off for brevity or else might like to know about is options.
For me one of the reasons for building my own packages is using non default options to ports, this is handled by
poudriere options -j 11-amd64 www/firefox
which effectively run a “make config-recursive” and will store the options under /usr/local/etc/poudriere.d/11-amd64-options (different jailscan have different option directories or I symlink them so i have consistent options)
If you already have port options saved you can pre-populate this directory from /var/db/ports

Comment on Cadillac ZFS #FreeBSD by Sean

Sean — Sat, 21 Sep 2013 15:53:30 +0000

In reply to Allan Jude. Yes, but did you *pay* as much for your machines. :-)

Comment on Cadillac ZFS #FreeBSD by Allan Jude

Allan Jude — Sat, 21 Sep 2013 15:23:23 +0000

Technically, the ‘optimal’ setup (other than 6x mirrors) for 12 drives would be 2x RAID-Z2. In RAID-Z you generally want to have the number of non-parity drives be a power of 2 (so that the 128kb record is split evenly across the non-parity drives).

Of course this would have left you with only 24 TB usable, compared to the 30 TB you got with the 2x Z1 or 1x Z2 you were considering.

Most of my ZFS boxes have 96 or 144gb of ram, but are otherwise very similar.

Comment on Cadillac ZFS #FreeBSD by Freddie

Freddie — Fri, 20 Sep 2013 22:21:24 +0000

If you really want to crank up the throughput, consider running a test using 6x mirror vdevs. 🙂 Then you’ll really see what the hardware is capable of. 😀

Just be warned … once you do mirror, you’ll never do raidz again. At least not where performance is concerned. For bulk storage, raidz2 works “good enough”, especially if you can get it to use 4 or more vdevs (we use 24- and 45-bay chassis for bulk storage).