136 private links
The new "Simple standalone #SSH Agent for #OpenPGP cards" (https://crates.io/crates/openpgp-card-ssh-agent) is now available as a package for #Arch Linux, by the way :arch: 😏
This agent offers a frictionless UX when using ssh with keys that are stored on OpenPGP card devices: No more ongoing PIN entry required! 🚀
@dvzrv has once again done amazing packaging and documentation work! 🥳 Thank you 😃
See https://wiki.archlinux.org/title/SSH_keys#OpenPGP_card_ssh-agent for details.
Das Problem lag in den Weiterleitungsregeln des HTTP-Servers. Hier war "/Verse" als Startseite mit einem großgeschriebenen Anfangsbuchstaben definiert, was dazu führte, dass die HTTP-Weiterleitung nicht ordnungsgemäß funktionierte. Nachdem dies korrigiert wurde und "/verse" als Startseite festgelegt wurde, funktionierte die HTTP-Weiterleitung einwandfrei, und somit war das ACME-Protokoll auf den jeweiligen Domino-Servern einsatzbereit.
Right now, I want to talk about the heritage of these input/output mechanisms. Why is it that punched paper tape and the teleprinter were the most obvious way to interact with the first electronic computers? As you might suspect, the arrangement was one of convenience. Paper tape punches and readers were already being manufactured, as were teleprinters. They were both used for communications.
It is time for me to re-do my old thread about the origins of "80 columns" and how it can very well be related to pretty ancient stuff, not dissimilar to "space shuttle and horse's rear end".
As you know, the default mode on IBM PCs is text 80x25. The limitation of 80 columns per line, also known as "80 column rule" is still widespread; for example, that's the rule for Linux kernel. But why 80? Why not 70 or 90?
The answer to that is usually "IBM punch cards are 80 characters wide", but things are more interesting than that!
First, the commonly accepted column width was supposed to be 72. American typewriters used to have just 72 columns, earlier DEC terminals supported only 72 columns, and even IBM punch cards had only 72 columns for text.
Second, yes, IBM punch cards were 80 characters wide, but why?
Fasd (pronounced similar to "fast") is a command-line productivity booster. Fasd offers quick access to files and directories for POSIX shells. It is inspired by tools like autojump, z and v. Fasd keeps track of files and directories you have accessed, so that you can quickly reference them in the command line.
The name fasd comes from the default suggested aliases f(files), a(files/directories), s(show/search/select), d(directories).
Fasd ranks files and directories by "frecency," that is, by both "frequency" and "recency." The term "frecency" was first coined by Mozilla and used in Firefox (link).
GNU Stow is a symlink farm manager which takes distinct packages of software and/or data located in separate directories on the filesystem, and makes them appear to be installed in the same place. For example, /usr/local/bin could contain symlinks to files within /usr/local/stow/emacs/bin, /usr/local/stow/perl/bin etc., and likewise recursively for any other subdirectories such as .../share, .../man, and so on.
This is particularly useful for keeping track of system-wide and per-user installations of software built from source, but can also facilitate a more controlled approach to management of configuration files in the user's home directory, especially when coupled with version control systems.
Stow is implemented as a combination of a Perl script providing a CLI interface, and a backend Perl module which does most of the work. Stow is Free Software, licensed under the GNU General Public License.
zoxide is a smarter cd command, inspired by z and autojump.
It remembers which directories you use most frequently, so you can "jump" to them in just a few keystrokes.
zoxide works on all major shells.
Sticker. Hm. "Sticker"
$ Ohne Graphik, trotzdem da
$ Commandline only Antifa
I embraced OS X as soon as it was available and have never looked back. So a lot of In the Beginning...was the Command Line is now obsolete. I keep meaning to update it, but if I'm honest with myself, I have to say this is unlikely.[1]
In July 2004 I found myself sitting alone in the dark, on the enclosed deck of a ferry boat oozing between fog-shrouded islands of the Alaskan coast. The scenery was haunting, but after the first three hours, I decided to occupy myself by finally reading Neal Stephenson's essay about the command-line. Halfway through it I began crossing things out, and scribbling comments in the margin. The essay was five years old, and in dire need of a fresh perspective.
Months later, I learned that Stephenson himself was dissatisfied with the essay. He wrote that it, "is now badly obsolete and probably needs a thorough revision." An "Ask Slashdot" poll quoted him as saying, "I keep meaning to update it, but if I'm honest with myself, I have to say this is unlikely."
Though I have fleshed out my original comments into longer, more structured pieces, it is not my intention to replace or revise Neal Stephenson's original writing. His original essay is a much more cohesive and entertaining read than my notes are. (He is a Writer, after all. I consider myself a code-monkey by comparison.) In fact, my notes do not hold together unless they use the original essay as a framework, and that's why his entire essay is reproduced here, with my comments color-coded. And yes, I have sought and obtained permission from Neal to do this.
Difftastic is a structural diff tool that compares files based on their syntax.
Like many things in git, zdiff3 is one of those hidden features that I wish was set as the default option. It has made my day to day development much easier when it comes to resolving conflicts and it's a nice little improvement over diff3. If you want to enable zdiff3 by default on versions of git >= 2.35, you can run git config --global merge.conflictStyle zdiff3. If you just want to give it a test run next time without setting that option to see if you like it you can also run git checkout --conflict zdiff3 ./conflicted/file/path to checkout just the one conflicted file again with the zdiff3 algorithm.
Here's the truth. Ted Kowalski, username frodo, may he rest in peace, was the original author, just down the hall from my office in Murray Hill, and his name for the program had a 'u' where there is now an 's'. Management made him change it for distribution, but they couldn't make him change his pronunciation.
The binary size difference is presumably because the 'test' binary omits the version and help text, along with the code to display it. But if you look at the relevant Coreutils test.c code, the relevant code isn't disabled with an #ifdef. Instead, LBRACKET is #defined to 0 when compiling the 'test' binary. So it seems that modern C compilers are doing dead code elimination on the 'if (LBRACKET) { ...}' section, which is a well established optimization, and then going on to notice that the called functions like 'usage()' are never invoked and dropping them from the binary.
If you are like me and have some systems with fully encrypted disks, where you can’t or don’t want to be physically present for a system (re)boot, or which don’t have OOBM/KVM/CIMC access, this might be for you!
A Simple and static blog generator in manpage design - written in Python.
some day you try to connect to some new system and get rudely disconnected before you get prompted for a password. The direct answer to what's happening is that you've run into the server's limit on how many different authentication options it will let you try
Okay, wow, my post about an empty file has generated a lot of feedback, mostly for the throwaway line at the bottom about an empty file being the smallest version of /bin/true possible.
age calls itself a “simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composeability”. I’m quite fond of the concept and the utility and use a pair of Yubikeys on which I keep some of its identities (secret keys).
A is for awk, which runs like a snail, and
B is for biff, which reads all your mail.
C is for cc, as hackers recall, while
D is for dd, the command that does all.
E is for emacs, which rebinds your keys, and
F is for fsck, which rebuilds your trees.
G is for grep, a clever detective, while
H is for halt, which may seem defective.
I is for indent, which rarely amuses, and
J is for join, which nobody uses.
K is for kill, which makes you the boss, while
L is for lex, which is missing from DOS.
M is for more, from which less was begot, and
N is for nice, which it really is not.
O is for od, which prints out things nice, while
P is for passwd, which reads in strings twice.
Q is for quota, a Berkeley-type fable, and
R is for ranlib, for sorting a table.
S is for spell, which attempts to belittle, while
T is for true, which does very little.
U is for uniq, which is used after sort, and
V is for vi, which is hard to abort.
W is for whoami, which tells you your name, while
X is, well, X, of dubious fame.
Y is for yes, which makes an impression, and
Z is for zcat, which handles compression.