I ran into an issue where my pinentry was unable to connect, blocking me from
doing commits. You can use this to continue signing commits.
export GPG_TTY=$(tty)
gpg-connect-agent updatestartuptty /bye
printf test | gpg \
--local-user 9A47900E81415D65C32C630066E2BF2B4190EFE4 \
--pinentry-mode loopback \
--sign >/dev/nul
I’ve been running fedora coreos on my home servers for awhile. I really liked
the stability I got from bazzite, and have since enjoyed the stability of
fedora coreos. Since it’s an immutable system I’ve never quite known if I need
to reboot or not, and was unsure how to check for updates. Today I learned you
can use rpm-ostree status to see if your
fedora coreos system is up to date.
rpm-ostree status
For me it listed security advisories with a count of each severity unknown, low, moderate, and important.
This morning I had a machine crash on me and came back to an error.
Error
zsh: corrupt history file /home/u_walkews/.zsh_history
Dammit I don’t want to redo my shell history, I checked with a clanker and they
came up with this solution using strings that only prints printable
characters.
cp ~/.zsh_history ~/.zsh_history.bak
mv ~/.zsh_history ~/.zsh_history.corrupt
touch ~/.zsh_history
chmod 600 ~/.zsh_history
strings ~/.zsh_history.corrupt > ~/.zsh_history
chmod 600 ~/.zsh_history
hmmm.
Does codex change throughout the token usage window?
T Handle Wire Puller
Keys.waylonwalker.com