This is a collection of random notes about FreeBSD's in kernel TLS implementation based on reading the source code (so far). The focus is TLS for NFS/RPC.
Lucene has Luke built in however I cannot start it directly via lucene/luke/bin/luke.sh on Ubuntu 20.04 with OpenJDK 11.
git clone https://github.com/apache/lucene.git Lucene
cd Lucene
./gradlew assemble
java -cp './lucene/luke/build/lucene-luke-9.0.0-SNAPSHOT/*' \
-Xmx1024m -Xms512m -XX:MaxMetaspaceSize=256m org.apache.lucene.luke.app.desktop.LukeMain
This is a story about an operating system problem that occupied me at work in 2015 for couple of days. The goal is to give you an overview of debugging techniques and associated tools. I'd like to use this opportunity (writing this article for my students of the Unix programming class at the Mathematical-physical faculty of the Charles university in Prague in 2021) to provide some historical points, some background and some details about operating system work (I feel old writing this). As a bit of a spoiler, the cause of the problem turned out to be completely different than what it seemed initially and involved traversing multiple layers in the operating system. I love this kind of problems because it is fun and great learning experience. I vaguely remember a job advertisement in Netfix bunch of years back that demanded that the applicants posses intimate knowledge of the operating system internals down to (
nice infographics on https://www.reddit.com/r/MechanicalKeyboards/comments/jihbhi/custom_mechanical_keyboard_infographic_v30_is_now/
Cherry MX Brown - to make it similar to the Sun Type 7 keyboard I was using previously (excellent keyboard however too wide).
Fn key - the "house/home" key
The LSI card does not support disks larger than 2 GiB.
https://stackoverflow.com/questions/23111631/cannot-download-docker-images-behind-a-proxy
mkdir /etc/systemd/system/docker.service.d
cat << EOF > /etc/systemd/system/docker.service.d/http-proxy.conf
[Service]
Environment="HTTP_PROXY=http://proxy.example.com:80/"
mediator-version with mediator-implementation in Solaris IPS a good idea ?TLDR answer: no, generally it's not
Suppose we have 2 packages that mediate usr/include/moomin (also they deliver symlinks in lib which is not really mediated since the link names differ), the foo package mediates using the mediator-version, the bar package mediates using mediator-implementation:
uls-0:/builds/vkotal/ips$ grep -v ^# foo.p5m
set name=pkg.fmri [email protected],5.11-0
xrandr --addmode DP-2 1440x900
What is OpenGrok