g0xA52A2A

Slides from this year's CoNGA (Conference on Next Generation Arithmetic) are available here [1]. Not sure if there are video recordings to come.

[1] https://posithub.org/conga/2023/#schedules

Another nicety OpenBSD's cron gained not long ago was the "-s" flag to ensure only a single instance of command will be run concurrently.

https://man.openbsd.org/man5/crontab.5#s

I share the same annoyance with quoting but avoid it differently by setting

    export QUOTING_STYLE=literal

This means I don't have to be clever about thinking if I need to pass -N to ls depending which OS I'm on.

There's also a part 2 available https://dayzerosec.com/blog/2023/04/22/reversing-the-amd-sec...

Part 2 is also now available https://johnnysswlab.com/decreasing-the-number-of-memory-acc...

Discussion on https://news.ycombinator.com/item?id=35302767

Immutable mappings make this cheap.

It's rather surprising how nuanced tmux can be considering its OpenBSD roots.

Just replying to provide some context [1] for those who come across this comment as I think it's pretty interesting. Also OpenBSD are working on something for this [2].

[1] https://seclists.org/oss-sec/2023/q1/92

[2] https://marc.info/?l=openbsd-tech&m=167673316325935&w=2

LOL I thought it was my submission, totally missed the redirect.

Changed "privilege separation" -> "separation" to fit within character limits.

I'll offer a random anecdote. I lived in Switzerland for a couple of years in the early 2010's, so before contactless payment had become so prevalent as it is now. Most of the transactions I made and saw others made was via cash rather than chip and PIN (the norm in most Europe at the time). One of the memories that stands out from my time there is whilst in the queue getting some groceries in Denner (a lower end supermarket), the person in front of me paid with a 1,000 CHF note and no-one batted an eye! I didn't even know the denominations went that high, which is more a reflection of my ignorance of the place I was living really. I mentioned this to my work colleges the next day and was told it wasn't that unusual, especially with older generations.

To be clear chip and PIN was widely available at this time but most people used cash. Even with a decade gone and a pandemic I still wouldn't be surprised if I were to go back to Switzerland tomorrow and see people paying for groceries with huge documentations

TLDR: The Swiss like cash.

This is from a lecture given earlier this week [1], I hopefully there's a recording that can be made available.

[1] https://www.ucalgary.ca/programs/mathphil/2022-23

This exemplifies one of the key reasons OpenBSD forked OpenSSL. For those who haven't seen it I'd recommend this presentation from Bob Beck[1], around the 10 minute mark he recounts fixing issues in the memory allocator which had been reported 4 years prior. Seems there's still a similar backlog sitting behind embargoes?

[1] https://www.youtube.com/watch?v=GnBbhXBDmwU

Dupe of https://news.ycombinator.com/item?id=34349558

I'm a fan of just having my $HOME as a plain git repo with "*" in ~/.gitignore. Having to force add new files is a minor chore but one I'm more than happy to live with.

Some context https://twitter.com/penberg/status/1611691744327831552

Annoyingly you can’t set “very magic” only “magic”. So I have written some vimscript to try and ensure when I start a pattern it starts with “\v” though I’d hesitate to call it robust.

What a beautifully formatted reply.

Title edited to fit within t character limits.

Previous discussion https://news.ycombinator.com/item?id=33691048

On mobile at the moment but it will be interesting to see how this compares to Glidesort [1]. Though I don’t think it’s been released yet.

[1] https://m.youtube.com/watch?v=2y3IK1l6PI4

It’s the 31st century, I’m exiting the TTS and once again I’m accosted by owls.

The best guide is built in to Vim but sadly often overlooked.

https://vimhelp.org/usr_01.txt.html#usr_01.txt

Title should be "FreeBSD" rather than the all encompassing "BSD".

In a similar vein there's also Linenoise form the creator of Redis.

https://github.com/antirez/linenoise

I hate this headline and wince every time I see it, even the article quotes

> There's nothing special about ZFS that requires/encourages the use of ECC RAM more so than any other filesystem. If you use UFS, EXT, NTFS, btrfs, etc without ECC RAM, you are just as much at risk as if you used ZFS without ECC RAM. I would simply say: if you love your data, use ECC RAM. Additionally, use a filesystem that checksums your data, such as ZFS.

And goes on to say

> I have nothing to substantiate this, but my thinking is that since ZFS is a way more advanced and complex file system, it may be more susceptible to the adverse effects of bad memory, compared to legacy file systems.

We have machine-check exceptions, the purpose of this paper is to draw attention to erroneous behavior that is silent.

I'd love to see more details on the defective parts, particularly counts of CPU model (anonymized if needs be) and counts of which part of the architecture exhibited faults.

From working in HPC I've handled reports of things like FMA units producing incorrect results or random appearance of NaNs. Were it not for the fact that we knew these things could happen and customer's intimate knowledge of their codes I dread to think how'd "normal" operations would track these issues down. Bad parts went back to the CPU manufacturer and further testing typically confirmed the fault. But that end of the process was pretty much a black box to anyone but the CPU manufacturer. I'd be keen to know more about this too.

A good cup of coffee seems hard to come by.