gbrown_

This brought back fond memories of spending much of my teens on what.cd, good times.

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

Previous discussion of Anandtech article on this https://news.ycombinator.com/item?id=27350632

Looks like imgur is also effected, EC2 issue?

I had the same, seems to be a result of having HTTPS-Only Mode enabled. Looks like usu.edu is available over HTTPS but not this page.

Are you able to say anything about the distribution across hardware? E.G. Is there any correlation across such faulty parts with serials/production dates or is it very random/insufficient frequency to say?

For those intertested OP's blog and prior submission [1][2].

> I am thinking that other people may want to have something like that, both for nostalgic reasons and for learning programming, so I thought of asking around and, if enough people like the idea, turn this into a product.

Is a HN post the place for this?

[1] https://raspberrypi4gameconsole.blogspot.com/

[2] https://news.ycombinator.com/item?id=26544635

Video presentation giving an overview https://www.youtube.com/watch?v=QMF3rqhjYuM

You may want to check out these tickets [1][2]. The latest comment in the second link nails it for me.

> I don't understand this decision. First the removal of compact mode was motivated because is has bad discoverability. Then community raise its voice to say that not what it wants. And the answer is to make the setting even less discoverable…

> Of course is won't be used if it is less and less discoverable. And this decision break the meaning of doing telemetry on compact mode altogether, how are we going to mesure if people prefer Proton normal vs Proton compact if they don't even have the option showed at all???

> Please keep support on compact mode, don't let it rot and broke

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1693028

[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1703254#

When was the last time a UI update didn't add padding?

> it's basically an ad for Intel® Xeon® and Optane®.

Bingo.

That'll be the "fiction" part of the science fiction.

Minor quibble the -i option mnemonic is "in-place" rather than "interactive".

At a previous job I was receiving training from a Cray engineer and things were winding down as we approached lunch. We were talking about various hardware replacement activities and the instructor recalled such work he had done on older Cray machines, I think it was a Cray-2. My memory is fuzzy around how exactly this came up because upon hearing "So I was replacing a register" my mind detonated. I was aware processors had spanned multiple chips and boards but hadn't really internalised how not long ago that was until that moment.

The classic example is the shell, if it's in a chroot say there's not a lot for you to execute. However the shell itself remains pledged.

Pledges must reflect the capabilities of a program. Yes the "proc" and "exec" pledge promises are powerful but they can be constrained by their environment such as chroots or calls to unveil.

As an aside if you have very good knowledge of what a pledged program executes you can opt into setting up pledge for it ahead of time in the form of execpromises.

There may be OpenBSD devs working on and using Got, but the OpenBSD project has never declared that it intends to move to it.

I'm not against nested abbreviations per se but "BPF Memcached Cache" could have just been abbreviated to BPFMC. Avoiding collision with what I would have assumed to be reasonably well known BMC of "Baseboard Management Controller".

This is exactly what I do too. No messing with magic aliases to tweak --git-dir and --work-tree, just vanilla git.

I just wanted to point out typo. I'm aware of the env idiom, though that wouldn't work in the chroot environment described in the article. Short of also copying it to the chroot which would be a bit redundant.

I replied to someone on Twitter about this as I mistakenly thought they were the author, but the interpreter line in the example script should be #!/usr/bin/awk rather than #!/bin/awk.

Sending typescript to a FIFO seems odd. Sure you can see live input rather than following a line at a time with tail -f but you also lose persistence. To share something live I'd just use tmux or screen, granted if you want to ensure the observer has read only access there may be a couple more steps than using a FIFO.

The use of grep the author proposes will have each line of output prefixed with the name of the file it came from followed by a colon. That is if the glob expands to more than one file though, if it only expands to a single file then it is equivalent to cat. Use of the -h option should be passed to grep if the difference in format is something the author wishes to guarantee.

Discussion from earlier today https://news.ycombinator.com/item?id=27000570

I would not conflate the tag line about remote holes in the default install with the security features OpenBSD provides [1]. Of which both base and ports benefit from, not to mention the patches for things like Chrome and Firefox to make use of pledge(2) and unveil(2).

[1] https://www.openbsd.org/innovations.html

Ah interesting to know about Gen11, thanks for the links.

Lack of TouchID on newer models is one of the main reasons I've yet to upgrade from my iPhone 8.

> There are many GPUs with no double precision floating point support in hardware.

Which ones? I'm genuinely curious about this.

> yet GPUs don't support double precision well.

Are there GPUs without FP64 functionality at all? Or are you just referring to most consumer GPUs being built for FP32 performance over FP64?

Ah cool, seems I missed that when it appeared on HN a few weeks back. Thanks for the pointer.

How about undocumented instructions? Sandsifter[1] is an interesting project and the video from BlackHat[2] is a good watch. There's also a previous discussion of it on HN[3].

[1] https://github.com/Battelle/sandsifter

[2] https://www.youtube.com/watch?v=KrksBdWcZgQ

[3] https://news.ycombinator.com/item?id=18179212