bewaretheirs

That's an oddly narrow focus!

Nintendo appears to make the musical elements of its work a priority and it's good to see it escaping the game console into live performance -- following in the footsteps of both show tunes and movie music..

Most of the big TLDs have already converted to algo 13 -- .org is still lingering on algo 8, but .com, .net, .edu, .gov have all converted, so a lot of the DNS traffic is using smaller signatures already.

Changing the algorithm for the root is being studied - see for instance https://lists.icann.org/hyperkitty/list/ksk-rollover@icann.o... ; I wouldn't be surprised to see an algo change as part of the next root key rollover.

Well, my reading is that the corrective action was less "add redundant safeties" and more "have sufficient process controls in place to ensure you don't break the feedback loop during pipeline work".

One potential problem with a pressure relief valve as a safety is that it could turn into a flare/blowtorch if there is an ignition source nearby, which constrains where it can be located (and requires ongoing maintenance to ensure vegetation/etc., doesn't build up where it could get torched).

As performed on the David Letterman show: https://www.youtube.com/watch?v=CLQ7xYnyIBQ You can see a few shots of the Cuica -- the drum(!) that makes the high-pitched squeaky monkey noises.

And for fans of video game music: that song inspired this little bit from the 8-bit big band: https://www.youtube.com/watch?v=v6hJvSkVLXs

Huh. I've owned a few manual-transmission cars over the years and they all disallowed this trick -- pressing the clutch would disengage cruise control just like a tap on the brakes.

The NTSB final report on this accident is here:

https://www.ntsb.gov/news/events/Pages/2019-PLD18MR003-BMG.a...

Unfortunately the shutdown of go.usa.gov broke a bunch of links from that page, but the NTSB recommendations are summarized starting on page 33 (PDF page 44) of https://www.ntsb.gov/investigations/AccidentReports/Reports/...

But the recommendations to the gas company included:

> Review and ensure that all records and documentation of your natural gas systems are traceable, reliable, and complete. (P-18-7) (Urgent)

> Apply management of change process to all changes to adequately identify system threats that could result in a common mode failure. (P-18-8) (Urgent)

> Develop and implement control procedures during modifications to gas mains to mitigate the risks identified during management of change operations. Gas main pressures should be continually monitored during these modifications and assets should be placed at critical locations to immediately shut down the system if abnormal operations are detected. (P-18-9) (Urgent)

Edit to add:

This page has currently working links to the specific recommendations:

https://www.ntsb.gov/investigations/Pages/pld18mr003.aspx

Something similar was at work in the 2018 natural gas explosions in and around Andover, MA: https://en.wikipedia.org/wiki/Merrimack_Valley_gas_explosion...

"According to the NTSB's preliminary report, customers in the accident area received gas from a low-pressure (0.5 psi) distribution network which, in turn, was fed from a high-pressure (75 psi) main pipeline via regulators controlled by sensors measuring pressure in the low-pressure pipes. At the time of the accident, workers were replacing some of the low-pressure piping, but the procedure set out by Columbia Gas for doing this failed to include transfer of a regulator's pressure sensor from the old, disused piping to the new. As a result, when the old pipe was depressurized, the regulator sensed zero pressure on the low-pressure side and opened completely, feeding the main pipeline's full pressure into the local distribution network."

It's more likely that something energetic happened with an onboard system (propulsion or batteries). Could just be leaky valves causing propellant and oxidizer to meet somewhere they shouldn't..

It's had a few propulsion system issues:

> On 9 September 2016, Intelsat announced that due to a malfunction in the LEROS-1c primary thruster, it would require more time for orbit rising ...

> In August 2017, another propulsion issue appeared, leading to larger-than-expected propellant usage to control the satellite attitude during the north/south station keeping maneuvers. This issue reduced the orbital life-time by about 3.5 years.

https://en.wikipedia.org/wiki/Intelsat_33e

Odd that the article makes no mention of intel's APX extensions (which add more integer registers, 3-operand variants of most 2-operand instructions, and assorted other tweaks).

According to their web site at https://kairospower.com/technology/ it uses a molten fluoride salt based coolant but unlike the MSR/LFTR designs the fissionable fuel is not dissolved into the coolant; instead, the Kairos reactor design puts the fissionables in pellets that are intended to remain solid while in operation; it looks more like a pebble-bed reactor than a MSR/LFTR.

Main difference (besides scale) is that the booster is cooperating with the chopsticks, navigating to hover at a point between the arms.

In August, they said the rocket was ready to fly .. but they were quite visibly still doing significant work to the catch mechanism on the launch tower.

The water deluge system has been in operation for all launches save the first and has been functioning well, protecting the pad from damage. It uses drinking-quality water and outflow has been sampled after each launch, with negligible traces of contaminants detected.

There was a disagreement between the Texas Commission on Environmental Quality and the US EPA about the specific type of permit that SpaceX needed from TCEQ for the deluge system but that was a paperwork/documentation issue only.

see:

https://www.spacex.com/updates/#starships-fly

First attempt to catch the booster back at the launch site.

The "mechazilla" launch tower has two "chopstick" arms which are used to pick up and stack both stages and which are intended to be able to catch the returning booster and maybe also the returning Starship upper stage.

Not much different from the prior flights.

Flight 4 was licensed on June 4th, was originally scheduled to launch on June 5th, and actually launched on the 6th.

Flight 3 received its license on March 13th and launched on March 14th.

Flight 2 received its license on November 15th 2023, and launched on November 18th.

Flight 1 received its license on April 14th; it launched on April 20th.

I've seen multiple reports that the equipment was in stock and for sale in Home Depot stores in the surrounding area.

Wasn't always this way -- see this historic reconstruction of a Baroque orchestra https://www.youtube.com/watch?v=fNqJ8mED1VE (Handel, Music for the Royal Fireworks on period instruments)

Down on the lowest level of the stage we find a small string orchestra, but then behind it on risers there are something like 18 oboes(!!), 10 bassoons, 9 horns, 9 trumpets.

If you transmit, you can be tracked. If you could modify a device to include an explosive, you could also modify it to include an undisclosed transmitter.

> B&H Photo

Okay, that pretty much guarantees that somebody at the Goa Chronicle fell hook, line, and sinker for a bit of internet satire.

EDIT:

It would also appear that the good folks at the Goa Chronicle failed to check a Yiddish-English dictionary.

Pagers are immune to a number of threats that two-way communications devices enable.

Hezbollah reportedly bans its members from carrying cell phones and has them carry pagers instead:

https://www.reuters.com/world/middle-east/pagers-drones-how-...

I've not seen it used this way before but it is similar enough to the dagger and double-dagger symbols that the intent to use it as a footnote marker is clear.

PG wrote:

"Whatever founder mode consists of, it's pretty clear that it's going to break the principle that the CEO should engage with the company only via his or her direct reports."

Whatever happened to "Management by Wandering Around"? Usually credited to HP but Shakespeare had Henry V do it (see act 4 scene 1) and there are probably even earlier examples.

No need for a new one; the two they built for the Apollo program still work just fine.

Note that the crawler-transporter doesn't hang around at the pad during the launch - after setting the mobile launcher down at the pad, it drives away back towards the VAB until it's needed next.

During the Apollo era, it also transported the Mobile Service Structure - a tower with work platforms that allowed access to much of the spacecraft on top of the rocket.

It's tower on a large steel platform but it also includes significant GSE (ground support equipment) - cabling and cryogenic plumbing to connect to the rocket to let it be fueled and readied for launch, all connected via mechanical arms to pull the quick disconnects away from the rocket, in some cases into armored boxes to protect against the rocket exhaust. Plus a crew access arm to let astronauts board, elevators so they don't have to climb stairs in their space suits, etc., etc.,

It is carried around by one of the two existing crawler-transporters, which moves it between the VAB where the rocket is built and the launch pad.

The smallest page size tends to get entrenched in the rest of the system (for things like linker page sizes, IOMMU interfaces, etc.,); growing the smallest page size might not be a viable option in existing systems and it might be easier to introduce intermediate-size TLB entries, perhaps formed by consolidating adjacent contiguous PTE's..

I believe that's still the contingency plan in the unlikely event that they have to evacuate the ISS in the period between Starliner undocking and Crew-9 docking.

Easy to imagine but there are so many details to nail down that it's hard to do in practice.

In the words of someone in the industry who tends to be on the laconic side:

"It is not as simple as a 'common connector'. There are different pressures, mixture ratios, comm gear, seat interfaces, etc. A requirement for commonality flows requirements upstream to the suit, seat and spacecraft. "

https://forum.nasaspaceflight.com/index.php?topic=60593.msg2...

Intel's menu of page sizes is an artifact of its page table structure.

On x86 in 64-bit mode, page table entries are 64 bits each; the lowest level in the hierarchy (L1) is a 4K page containing 512 64-bit of PTEs which in total map 2M of memory, which is not coincidentally the large page size.

The L1 page table pages are themselves found via a PTE in a L2 page table; one L2 page table page maps 512*2M = 1G of virtual address space, which is again, not coincidentally, the huge page size.

Large pages are mapped by a L2 PTE (sometimes called a PDE, "page directory entry") with a particular bit set indicating that the PTE points at the large page rather than a PTE page. The hardware page table walker just stops at that point.

And huge pages are similarly mapped by an L3 PTE with a bit set indicating that the L3 PTE is a huge page.

Shoehorning an intermediate size would complicate page table updates or walks or probably both.

Note that an OS can, of its own accord independent of hardware maintain allocations as a coarser granularity and sometimes get some savings out of this. For one historic example, the VAX had a tiny 512-byte page size; IIRC, BSD unix pretended it had a 1K page size and always updated PTEs in pairs.

It was deleted from the default build of the timezone files but remains in the source tree; patches are accepted.

Choices have to be made for usefulness vs completeness vs size as it's quite likely that at least one and perhaps multiple copies of the database are present on any system out there running code in C that needs to know what time it is in human terms.

But if you're a packrat, you can include the extras in your build of the timezone data by setting PACKRATDATA=backzone during the build.