intorio

This is just wrong though, they were a root CA. There was cross-signing which is typical, but their `emSign ECC Root CA - G3` root certificate was in most CA bundles.

You've been quite rude in this thread, so I'll just say that I'm glad you were able to get paid for years for your hobby of coding. For the organization paying you, that was only ever a means to an end of solving larger organization problems that you probably never bothered to understand because you just loved the thrills you experienced writing code.

Why did you expand it from what he said? I love technology, I enjoy being able to solve problems with technology and coding. I've always felt neutral about the actual act of coding, it was always just a means to the end and now I love that I can do more problem solving in less time and with less toil (from my view). But I guess I was just in it for the money.

Not only is inference currently much cheaper than people seem to think, it is going to get much cheaper. NVIDIA’s Vera Rubin is going to drive costs down for current models considerably.

How do you tell the difference between inference and training workloads from outside? The same GPUs can be used for both and the pacing suggested here relates to training and not inference as far as I can tell.

The problem is how do you enforce coordination? This isn't like nuclear testing that can be detected around the world on seismographs or from satellites in space.

AI research happens in benign looking buildings that could be doing a hundred different non-AI workloads, much of it things that industry or governments would not want 3rd parties prying into. There is too much to potentially gain to trust coordination.

> by what mechanism is an LLM going to help you design and manufacture a novel bioweapon? We know they cannot do spatial reasoning, and if they were this good at bio stuff then drug research would be absolutely out of control.

I guess my question would be how good the LLM is at writing a program that is good at spatial reasoning? If it can create a valid test suite from existing art on the subject it might be able to bumble its way to something specialized that it can then direct at a higher level.

Isn't it that kind of 'rapid self-improvement' that is the concern expressed in the linked statement?

You do need PTRACE access to pid 123456 in order to access that file. It is transparent to you, but the kernel will use the current task's PTRACE_ATTACH access when attempting to get that information.

By default, on most distributions, a user has PTRACE_ATTACH to all processes owned by it. This can be configured with ptrace_scope:

https://www.kernel.org/doc/Documentation/security/Yama.txt

RHEL 8 is impacted, the fix that introduced the issue was back ported:

https://access.redhat.com/security/cve/cve-2023-4911

Fair use only applies in certain contexts, of which writing commercial software is not one of. 'Snippets' are not fair use and it is shocking how many people here think they are.

Are any of those easily helped by a vaccine?

Transfer spots can be more competitive than Freshmen spots. This would especially be true if more people were doing it.

Your evidence of this is an opinion article by a republican political adviser. Please forgive me if I wait for the congressional investigation to look at it.

At least for a commodity chip like Broadcom Tomahawk (100G), the latency is 500ns with L3 enabled, and 300ns if only L2 is enabled. Compared to the Mellanox SB7700 at 90ns ethernet has some catching up to do if latency is the end goal.

Ethernet tooling for HPC has a ways to go, but I suspect in the future it will be more competitive. Especially if specialty fabric vendors cut down on R&D.

CLOS fabric designs seem to be winning the war these days which I think favors Ethernet in the long run. Better flow distribution on aggregate links and now widespread support for MC-LAG means you can build a really wide CLOS network with L2-only.

That 'little' magic being specialized hardware packet processors that are programmed from proprietary programs running in Linux.

Arista uses commodity ASICs which are programmed from specialized binary blobs running in a linux based userspace. This is the same thing linux whitebox switches do.

Maybe I'm just bad at negotiating, but I haven't been able to get vendors to quote me less than double the cost of the Cumulus hardware quotes I've seen (primarily Quanta). Also, looking at support costs, the quotes I have for Cumulus are about 20% cheaper than the cheapest quotes I've seen from Juniper/Dell, just for software support.

That said, NBD or sooner hardware replacement plans are a bit weird with Cumulus. I think they expect you to keep onsite spares, which still ends up being cheaper.

I think if Cumulus becomes more popular, we might see some community code that implements validation and confirmed commits and more features. If we decide to go with Cumulus, and we are thinking about it, we might write something like that.

For licensing issues, actually.

Are you running the newest firmware on the PERC? The firmware used to limit you to only Dell certified drives but they removed that after about a year, probably due to backlash. I know we told our rep we wouldn't buy the new cards until they got rid of that.