terminal-code has been replaced by a shell script which 1) Generates a syslog message at level LOG_EMERG; 2) reduces the user's disk quota by 100K; and 3) RUNS ED!!!!!!
When I was in graduate school, I was doing a lot of molecular dynamics simulations, but I did not have access to a lot of high-performance hardware. The math department had a 4-node Cray that was impossible to reserve time on, and the CS department had a 16-node Dell cluster that ran SGE and was decently reliable. When those resources ended up not being enough for my crazy array of tasks, I got resourceful and started gathering every single outdated CPU anyone anywhere on campus was getting rid of or had no use for, and built my own cluster in our lab. Before finishing my Ph.D. I had 12 SGI Indys, 8 PowerMac G3 6300s, 10 PowerMac G3 7600s, and 20+ Dell P3 towers in my "cluster".
Very nice, I know how things like this go. You are in a hurry and documentation is something never gotten to. Plus it is a "one-time" setup, to be thrown away when complete. That is fully 100% full understandable :)
I am sure there are other impressive stories about what people did with NetBSD, too bad these really never get published. Things like this would have been nice to show up here:
I dont understand the purpose of using 40,000 lbs of TNT (0.2 kilotons) that registers as M3.9 quake - what kind of explosive payload is it simulating?
the only thing that comes to mind, is the smallest yield settings of a modern tactical nuke B61-12
I would guess that they want to simulate a percentage of the shock force of a near miss or hit from a (russian, chinese, other equivalent-tech) torpedo or naval mine without actually risking rupturing the hull. So they need a much greater weight of explosives positioned a much further distance away than if they were to actually fire a torpedo at the ship.
Or for general shake and vibration and shock force testing of the entire ship, simulating a combat environment. Unlike the shake/rattle/hydraulic ram rigs which are used to qualify a new airliner design on a structural test article, there's no other way than lots of explosives to shake/vibrate an entire Nimitz, Ford class size aircraft carrier.
I would guess they want a large enough explosion to generate peak acceleration of the entire ship without a local enough explosion to actually damage it. Getting enough separation to make it non-local requires a lot of explosive thanks to the inverse cube law.
If you look at e.g. seismic damage models, peak acceleration is correlated with most of the worst outcomes.
The structure is engineered to survive a multitude of conventional threats intact. It is testing properties of the design rather than specific weapons per se. Also, these tests are intended to be non-destructive which impacts their design.
Exercises where the US military uses decommissioned aircraft carriers and other large ships as targets are illustrative. They are basically unsinkable. You can hit them with torpedoes, bombs, missiles, etc all day. At the end of the exercise they usually have to send over a specialized demolition crew to actually scuttle the ship. Astonishingly damage resistant.
A nuke would of course do the trick but now you are playing a different game.
People chronically underestimate how difficult it is to get enough conventional explosive on target to sink a major naval vessel, even ignoring the extensive active defenses.
> People chronically underestimate how difficult it is to get enough conventional explosive on target to sink a major naval vessel, even ignoring the extensive active defenses.
American ships, certainly. Russian ships? Oh boy. The Ukrainians, a country with no navy to speak of, sunk the Russian flagship Moskva to widespread memefied acclaim, a bunch of other Black Sea assets and are now taking potshots at the shadow fleet.
I'm guessing with a few more tries to get the right positioning and amount of explosives, those terrorists could blow up US ships as well as the Ukrainians do Russian ones.
Well, actually, the Argentinians had no trouble delivering high explosives to UK vessels, but they did have a great deal of trouble getting those explosives to sink those vessels ... mostly because their bomb fuzes were incorrectly set or inappropriate for the delivery profile.
But on a more serious note, none of the ships sunk by air attack in the Falklands were large military vessels. The largest vessel sunk was the Atlantic Conveyor, and that was (1) a civilian cargo ship built to civilian levels of durability, and (2) it was carrying a large quantity of ammunition essentially unprotected (unlike how a large warship would carry it). Even then, the missile strike and fire did not sink the ship immediately. For the largest military vessels sunk by air attack, the two Type 42s Sheffield and Coventry were relatively small destroyers (less than half the displacement of either their USN contemporaries the Spruance/Kidd or a modern Arleigh Burke) and again there the Exocet strike and resulting fire did not sink Sheffield immediately either. The smaller Type 21 frigates lost, Antelope and Ardent, were never really meant to survive meaningful damage and yet both remained afloat overnight before sinking. For comparison, the roughly contemporary USN frigates, the Perry-class (larger in displacement than the Type 42s), survived both Exocet (Stark) and mine (Samuel B. Roberts) strikes.
(The General Belgrano was a larger military vessel lost to submarine attack with, but considering that it was a treaty-limited 44-year-old light cruiser operating unprepared for submarine attack, it is hard to draw too many conclusions about modern ship durability from its loss - and her sisters in the Brooklyn class generally survived quite a punishment in WWII.)
The ships sunk in the Falklands War were all less than half the displacement of a typical US Navy destroyer. The sole exception is the Belgrano, which was built in the 1930s!
The ship being tested here is ~25x the size of the largest British ship that was sunk. Generally speaking, there is a super-linear relationship between ship size and the amount of explosive required to sink it. There is mountains of empirical data on this that you are choosing to ignore.
Every military knows this. They are making a tradeoff between size, which makes the target more difficult to destroy and easier to defend, and the number of ships they can build which allows them more flexibility in force projection.
I've been working on RVW, my adaptation of the standard transformer model that is capable of online continual learning without catastrophic forgetting. I finally published the first pre-print of my early experiments: https://doi.org/10.5281/zenodo.20064617
Now I'm working on expanding the work into more parameters and improving performance. I just finished an extremely harsh test of a Nemotron-flavored RVW that consisted of stretches of a random assortment of domains interspersed with long runs of single domains. Across all of it the model didn't forget (and actually improved on some of the more challenging domains). PPL on SmolTalk is still in the ~18 range, which I'd like to get lower, but this is all with only 4B params.
Currently, I'm training a Llama 3.2-flavored RVW with only about 2B params to see how that turns out. Depending on results of that, I may take it to Gemma 4 next.
IIRC, there was always a way to filter out certain messages (or that may be an alt.org customization, but it's been a part of my config file for a while now).
For real! Valkyrie is the perfect "just bash things while only half paying attention" class. Great for when I'm playing to unwind (as opposed to playing as a challenge to myself).
I think Douglas Adams had one of the best quotes regarding observing infinity:
"Infinity itself looks flat and uninteresting. Looking up into the night sky is looking into infinity – distance is incomprehensible and therefore meaningless."
It's been a while since I worked at Apple, but back in the day the entire OS X Server team made extensive use of kerberized NFS shares for moving around large files...
...the last version of Server shipped in 2021 (and the last real version shipped almost a decade before that).
Hmm, the more I think about I think you’re right, they likely still do use kerberized nfs, but I think the auth layer they use is… different. Without giving too much away, the internal SSO software ends up either wrapping or providing Kerberos tickets in some way, so I’m imagining that code path doesn’t panic.
In fact that’s probably the clue… everyone internally at Apple using krb5 auth with nfs is probably using the internal SSO software and the code path for “vanilla” Kerberos (ie. Ticket Viewer.app and so on) has zero testing. Maybe I’ll write that into the next crash tracer report I type up :-D
My first job after finishing my undergrad degree was performing quality analysis on corn starch. As a condition of employment, I had to sign a paper saying anything I invented related to corn was property of my employer.
It's been more than a few years since I worked at Apple, but they were always unique in the tech space in that their retail division dwarfed headcount. If I recall correctly all of OS X Lion was produced by around 3,000 engineers (and probably less, since I think that count included iLife and iWork).
(adapted from the venerable "Ed, man! !man ed": https://www.gnu.org/fun/jokes/ed-msg.html)