After a recent spat with NAStie (my home NAS built in building
NAStie) and its grub infestation, I decided to
go back to FreeBSD for my home server needs. I like Linux, but mostly for
desktop/remote server stuff. For home server on old hardware, I likes me some
So, I started my research at my post about RAID1 on FreeBSD (FreeBSD 5.2.1 and
cheap RAID1), learned about the
RAID-1 options in FreeBSD, and needed to decide whether there was any use in
trying for a volume management option.
As to why: In my home network server upgrades are driven not by space
requirements, but by old …continue.
Unlike my previous experiment with building NAStie
installing this variant of linux onto LVM-only partitions proved
difficult. My attempts left my sleep schedule a bit tweaked, and my
disgust for "automated" configuration-file-building-scripts found new
purpose. That aside, what worked when I installed Arch linux on LVM
partitions is below.
Install Arch using the standard install tool.
While doing this, refer to the Arch Wiki page on LVM
and follow its instructions until it talks about changing the grub
Assigning (VolumeGroupLabel-LogicalVolumeLabel) to GRUB_DEVICE in
/etc/default/grub will cause the /boot/grub/grub.cfg-building
script to insert the parameter
'root=(VolumeGroupLabel-LogicalVolumeLabel)' when building the
In High resolution console on FreeBSD I mentioned a
particular way of setting the VESA mode for syscons, but a post on the
freebsd-questions mailing list mentioned a different method. Instead
of setting the allscreens_flags="MODE_325" in /etc/rc.conf, you use the
Putting the following items into /boot/device.hints puts syscons into
MODE_325 (1280x1024x32 on my VirtualBox installation).
This does not put FreeBSD into this mode as soon as the kernel starts
booting, but it does as soon as the sc driver is loaded (which is much
sooner than rc.conf is processed). As a result, a significant portion
of your dmesg is available in your larger console.
Ever since installing Symantec Endpoint Protection in unmanaged mode
LiveUpdate has been annoying me by updating itself once per day...
that is not the annoyance, though. The annoyance is it
creates a window on screen showing progress, and then requires user
intervention to make it go away!
I was just starting on my quest to find a way to change that behavior
when I found someone had already done the homework. Far be it from me
to be ungrateful and not use the results of his efforts (command-line
used below). ;)
$sudosymsched-dall$sudosymschedLiveUpdate"Update All Daily"10-daily03:13
A small irritation about FreeBSD is man does not automatically adjust
its line-length to account for the number of columns currently displayed
in a particular xterm. So, after weeks of intermittent frustration and
small, aborted attempts to determine why I could not get the man to do
what I wanted, I decided a concerted effort was worth my time (that, and
I asked for help ;)).
When using FreeBSD, I always run into the problem of maintaining local
ports. Usually I find a way around the problem using some good-natured
shell hijinks, or end up simply installing linux as a stop-gap (due to
time pressure), but this time I think I have found a more permanent
solution: Local ports which coexist with portsnap! In that
thread there was actually another, similar solution, but I have
stuck with the first for now. The only significant difference between
the two was the use of categories.
I followed the instructions in the first link, leaving out any ports
categories I did not need. Then …continue.
During my brief brush with Arch a few years back I found their
documentation to be extremely well-done. Given that, I find it odd I have
never stuck with that distribution for long... Especially since I end
up back at the Arch wiki for configuration advice over and over
again. This time I could not remember the different options I used for
NTPd configuration, and ended up back at the Arch Linux NTP
article and the NTP pool web site.
Now it is saved here for safe-keeping, and I (hopefully) will not forget