I like pam_mount‘s idea of providing per-user, on-demand, block device level encryption. Sadly, it turns out it doesn’t really play nicely with systemd user sessions, which are enabled by default in Arch Linux (you can disable them, but it screws up stuff like PulseAudio socket activation). The Arch wiki warns upfront that pam_mount can also unmount your partitions when you close your last session but this is currently not working due to the use of pam_systemd.so in the PAM stack. While pam_mount and systemd indeed have some disagreements, they can be persuaded to play together quite nicely with some fiddling.
While experimenting with Arch Linux, it turned out I couldn’t run the iDRAC Virtual Console (firmware version: 1.66.65), no matter which Java version I used. For those unaware, iDRAC Virtual Console is a Java application for out-of-band management of Dell servers. Whenever I tried to run it, all I got was a pop-up window saying “Connecting to Virtual Console server” and then a nasty message on the console:
Recently I had to migrate some raw disk images to LVM volumes. These disk images belonged to KVM virtual machines, which didn’t really need the whole disk space they were assigned upon creation. The images were sparse files, which allowed me to keep the actual disk space used to the bare minimum. I had to use LVM in the target infrastructure, but didn’t want to statically assign disk space to each VM as a lot of disk space would be wasted. LVM thin volumes were a perfect solution for my problem.
I have recently acquired a 32 GB ADATA Premier SP800 SSD drive and failed to find its hardware design details on the Internet, so I thought I’d ask ADATA technical support. Here is their answer:
Thank you for contacting ADATA Technology.
Please below the hardware parameters of the 32GB ADATA Premier SP800 SSD drive you requested:
- Page size: 8192 bytes.
- Block size: 256 pages (2048K bytes).
I have to warn you, though, that if you require solid technical support from your vendor, don’t choose ADATA. It took me an hour to register my drive and actually send my inquiry due to terrible lags and connection resets. I had to wait two working days for an answer.
To be fair, though, the disk itself is great value for money. For ca. $50 you get a device capable of achieving 250+ MB/s sequential read/write.
I’ve played around with PXE booting recently and came across an irritating problem. The PXELINUX documentation states that it should reboot the machine after an unsuccessful PXE boot. However, that wasn’t true for both mainboards I’ve tested it with (MSI B75IA-E33 and Dell 0X3GJK, found inside a Dell Vostro V131 laptop) – instead of rebooting, the BIOS continued to boot the next available medium (HDD in my case).
When performing ISSU on Cisco 4500 switches running IOS XE, the first step to do is to issue the
issu loadversion command. If the switch refuses to perform this command with the following error:
#issu loadversion 3 bootflash:cat4500e-universalk9.SPA.03.04.00.SG.151-2.SG.bin 4 slavebootflash:cat4500e-universalk9.SPA.03.04.00.SG.151-2.SG.bin % Active Boot variable is invalid
make sure the configuration register is set to 0x2102:
#configure terminal Enter configuration commands, one per line. End with CNTL/Z. (config)# config-register 0x2102
Make sure you reload both supervisors before proceeding. You can check the current value of each supervisor’s configuration register using the
show redundancy command.
On New Year’s Eve I had to troubleshoot a nasty issue with a mail server which apparently stopped accepting mail for delivery. Looking into the matter I have determined it was due to a named process (running on the same box) failing to resolve hostnames. Upon attempting to restart the process it turned out I wasn’t able to shut it down properly and restarting it took ages for no apparent reason.