Twelve years I started with Perl and I still can't remember EVERY TIME which one between ^ and $ should be used to match begin and end of regex pattern 🤔
Any mnemonic or memory aid? I can use a cheat sheet, but come on…
@smonff@Perl Y’all know I’m the first to crow about unique #Perl features, but #RegularExpressions’ syntax of ^ for the start of a line or string and $ for the end dates back at least to #Unix co-author Ken Thompson’s rewrite of the qed text editor for the #CTSS operating system on the IBM 7090 #mainframe at #BellLabs around 1970. (Perl creator Larry Wall was a teenager at the time.)
This is my expression when local (and exclusive) flock() locks on a Linux NFS server don't conflict with POSIX locks obtained over NFS through lockd/NLM/etc. Because these NFS locks may be from flock() on clients.
Augh. This is robot logic and it means 'don't run anything on your NFS servers'.
The interoperability problems are significant. H. Peter Anvin's flock(1) uses flock(2), whereas you are using fcntl(2).
Ironically, this means that #Linux is your worst nightmare, because #Illumos and the BSDs guarantee that those two will (locally) interlock, whereas Linux doesn't and the world has thus got two #flock tools on Linux that don't interlock.
That's going to be a #Unix StackExchange answer somewhen.
@ovid@htothedip@eric Nice thing about #Perl is there's less syntactical distance from #bash and #Unix shells of its ilk. Pythonistas consider that a bug. 🙁
I remember #Gem, great GUI for the time although I never adopted it, but did use Ventura publisher and AmiPro intead of Aldus and Word, respectively, on Windows
Everything else though, yah, very, very similar history for myself except for the Apple 🍏 stuffs; like you, I'm quite proudly Mac stupid.
It's always good to meet a fellow Slacker, and "frinds don't let frinds run ewb00ntew!"
「 In 1994, the paper Scalability in the XFS File System saw publication. Computers got faster since 1984, and so did storages. Notably, we are now seeing boxes with multiple CPUs, and with storages reaching into the Terabytes. The improvements to the 4.3BSD fast filing system (or the modified version in SGI IRIX called EFS) were no longer sufficient 」
— Kristian Köhntopp
Oh wow, TIL: When you do input redirection from a file in #bash, e.g.
python whatever.py < foo.csv
the running command can actually stat() the stdin file descriptor and get the size of the input file! I would’ve expected that it’s more like “well, it’s your stdin, you can’t get the size for that, it’s a stream”.
And, to be fair, if you don’t directly associate the file to the command, it breaks. For example,
Two years ago on "Computer Chronicles Revisited," I covered a 1984 episode on operating systems. Herb Lechner sat in the co-host's chair as Gary Kildall appeared as a guest to discuss Digital Research's CP/M. We also get the first UNIX talk on the program, as AT&T was now in a position to commercially exploit its famous operating system.
Oh wow, TIL: When you do input redirection from a file in #bash, e.g.
python whatever.py < foo.csv
the running command can actually stat() the stdin file descriptor and get the size of the input file! I would’ve expected that it’s more like “well, it’s your stdin, you can’t get the size for that, it’s a stream”.
And, to be fair, if you don’t directly associate the file to the command, it breaks. For example,
「 I wanted something the likes of which actually no longer exists: I dreamt of a Unix Workstation.
Not just any old Unix box mind you, but a rather specific one: a Silicon Graphics Indy with a 24-bit frame buffer, 128 megabytes of memory and a 175 MHz MIPS R4400 CPU 」