I recently realized that my web server was still on Debian Buster, 2 whole major versions behind the latest Debian version. Normally this kind of thing wouldn’t matter to me except that my matrix-synapse server was unable to federate with matrix synapse servers running newer versions. I normally run rolling release distributions on my local machines (I use Void btw) and it had been a long time since I tried this kind of upgrade. I went in hopeful that it would be straightforward.
_ _ ____ _ _ / \ | | _____ __ / ___| ___| (_)_ __ ___ _____ __ / _ \ | |/ _ \ \/ / \___ \ / _ \ | | '_ ` _ \ / _ \ \ / / / ___ \| | __/> < ___) | __/ | | | | | | | (_) \ V / /_/ \_\_|\___/_/\_\ |____/ \___|_|_|_| |_| |_|\___/ \_/
I am a materials scientist and software developer proficient in Rust, Fortran, C++, Java, and Python. I have extensive experience with Unix operating systems on both high performance computing resources and on my personal computer (check out Void Linux). I currently work at UKG as a Java Backend Engineer.
Checkout recent posts below or posts organized by topic here
Thanks for stopping by!
Getting CUDA toolkit installed on Void Linux
This is a short post (mainly for myself) to remember how I got CUDA installed on Void Linux. These steps are as follows:
- Download the installation files: Go to the CUDA toolkit installation website. Select Linux->x86_64->Debian->11->runfile (local)
- Set executable permission:
chmod +x ./cuda_version.run
- Install using the correct flags:
sudo ./cuda_11.8.0_520.61.05_linux.run --silent --override --toolkit --no-opengl-libs --tmpdir=/home/aselimov/down/tmp
- Add to path: Build should now be installed at /usr/local/cuda-version. Add the following to your bashrc or zshrc:
export PATH="$PATH:/usr/local/cuda-version/bin" export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/local/cuda-version/lib64"
The reason I had to add the --tmpdir
command was because I was getting an error message about the default tmp
directory not having enough space.
Hopefully this helps someone else out!
Solutions to problems with Java Development
I recently ran into some problems with java development. One problem was neovim specific but the other was an issue with gradle. I wanted to document these in case any one else has similar problems as it took me a little bit of time to figure out.
Problem 1: jdtls exiting with status code 13
I use jdtls through Mason with the built in nvim LSP and was recently having an issue where jdtls would immediately crash when opening a file. The solution to this problem was just deleting the cache for jdtls: