I recently ordered a Chelsio T6225-CR network interface card and a couple of SM25G-SR SFP28 optical modules.
The aim is to get a 10 Gbit/s connection to the LAN, utilise the off-load capabilities of the NIC, and of course utilise the on-board crypto accelerator. The latter will not be useable until the system moves to the upcoming
stable/12, I look forward to encrypted crash dumps and linear ZFS scrubbing.
I hope both OpenSSH and OpenSSL will be able to use the crypto accelerator by ways of
crypto(4). Imagine a crypto speed in excess of 30 Gbit/s. That’s pretty neat. If all goes well, another T6225-CR may find its way to a VPN router.
synth 2.05 was released not long ago. None of the below applies. Continue reading Unable to build ports depending on
I needed to migrate an UFS filesystem from one disk to another. I had several options including using two
tar processes in a pipeline or using
restore in a pipeline. I opted for the latter to make sure everything got preserved during the transfer.
Here’s the sequence of commands where
/dev/gpt/nroot0 is the GPT label of the new filesystem and
/ is the donor filesystem:
mount /dev/gpt/nroot0 /mnt
dump -0LaP 'restore -rf -' /
I need to remind myself of running the IPP webpage in compatiblity mode in IE11 when installing printers.
Even if you specify
ipp.FQDN, IE11 will kindly enter your
FQDN into the list of domain names to show in compatibility mode. Remember to remove
FQDN from that list when you’re done.
iPrint client 5.99 seems to be the last of its kind. From now on, iPrint is an appliance. Maybe it’s time to leave Novell and their products for good.
Sometimes security is on the border of being ridiculous. Modern Windows 10 is very anxious when connecting to guest-access allowed, readonly Samba shares, Here’s how to allow “insecure” guest logons for stand-alone computers. The same is true when configuring a GPO.
Windows Registry Editor Version 5.00
If technologists do not speak up to educate policymakers, bad policy will result, and we will have to live with it.
—Margaret Martonosi, Comm. ACM, 2018-05, vol. 61, no. 5.
efi_max_resolution. If you run
base/head on monitors without Full HD (FHD), then you might need to specify your desired resolution in
This should suffice for a resolution of 1280×1024 on 19 inches displays.
This is what a kernel panic may look like when facing memory corruption.
kernel: panic: solaris assert: arc_buf_alloc_impl(hdr, private, compressed_read, 1, &buf) == 0 (0x5 == 0x0), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c, line: 5318
kernel: cpuid = 1
kernel: KDB: stack backtrace:
kernel: db_trace_self_wrapper() at 0xffffffff8046b52b = db_trace_self_wrapper+0x2b/frame 0xfffffe0122681380
kernel: vpanic() at 0xffffffff806c5ba6 = vpanic+0x186/frame 0xfffffe0122681400
kernel: panic() at 0xffffffff806c5a13 = panic+0x43/frame 0xfffffe0122681460
kernel: assfail3() at 0xffffffff8030987c = assfail3+0x2c/frame 0xfffffe0122681480
kernel: arc_read() at 0xffffffff80322ddc = arc_read+0x83c/frame 0xfffffe0122681510
kernel: dbuf_read() at 0xffffffff8032e918 = dbuf_read+0x678/frame 0xfffffe01226815c0
kernel: dmu_buf_hold_array_by_dnode() at 0xffffffff80338bf3 = dmu_buf_hold_array_by_dnode+0x203/frame 0xfffffe0122681630
kernel: dmu_read_uio_dnode() at 0xffffffff8033a167 = dmu_read_uio_dnode+0x37/frame 0xfffffe01226816a0
kernel: dmu_read_uio_dbuf() at 0xffffffff8033a10b = dmu_read_uio_dbuf+0x3b/frame 0xfffffe01226816d0
kernel: zfs_freebsd_read() at 0xffffffff803d7e80 = zfs_freebsd_read+0x660/frame 0xfffffe0122681780
kernel: VOP_READ_APV() at 0xffffffff80a7b77c = VOP_READ_APV+0x7c/frame 0xfffffe01226817b0
kernel: vn_read() at 0xffffffff807a0815 = vn_read+0x195/frame 0xfffffe0122681830
kernel: vn_io_fault1() at 0xffffffff8079e4e9 = vn_io_fault1+0x169/frame 0xfffffe0122681970
kernel: vn_io_fault() at 0xffffffff8079c6ac = vn_io_fault+0x18c/frame 0xfffffe01226819e0
kernel: dofileread() at 0xffffffff807291aa = dofileread+0xba/frame 0xfffffe0122681a20
kernel: kern_readv() at 0xffffffff80728db8 = kern_readv+0x68/frame 0xfffffe0122681a70
kernel: sys_read() at 0xffffffff80728d46 = sys_read+0x86/frame 0xfffffe0122681ac0
kernel: amd64_syscall() at 0xffffffff809d5f18 = amd64_syscall+0xa38/frame 0xfffffe0122681bf0
kernel: fast_syscall_common() at
It’s winter break, giving me time to bring systems down for their much needed maintenance. One of my tasks was to upgrade our XenServers. They’re not joined to the same pool for historical reasons. One of them is close to 8 years old, the other one is fairly new. For the first server I chose to reboot into the hypervisor after upgrading to 7.2, before upgrading to 7.3. A wise choice. Just for the fun of it, I chose not to reboot into the hypervisor on the second server between 7.2 and 7.3. This left me with the choice of restoring the old 7.1 version or performing a clean reinstall of 7.3. Neither option was inviting, so I had to reboot into the hypervisor prior to upgrading to 7.3. Lesson learned.
The irony of this story is that XenServer 7.4 was released two days ago. Luckily, I can use the new update feature and save me a trip to the server room.
While trying to log in on our Novell servers using Client for OES 2 SP4 IR7a on Windows 10 1709, I was greeted with:
A required network service has not started.
Please check your error log for details.
The third reply of this post gave me a clue, simply run
setup.exe one more time and reboot.
Uninstallation of IR7a still gives me error
0x80070005. The Registry settings in
HKEY_LOCAL_MACHINE\SOFTWARE\Novell was accessible to me as a regular user. Maybe the client’s uninstaller is complaining about rights in the filesystem.
iobit‘s uninstaller free saved the day.
I really wish for more specific error messages.
yourscript.cmd from an elevated Command Prompt window eliminated all my problems. Search for “Command Prompt” on the start menu and hold down Ctrl+Shift when you click on the menu item. Simply right-clicking on
yourscript.cmd and selecting “Run as administrator” proved to be insufficient. Creating
HKEY_LOCAL_MACHINE\SOFTWARE\Novell manually might also set things straight.