When I was 18 and in my first job, my boss and I installed the very first windows NT file servers for a major uk public sector organisation. They were all named after beers that we’d drunk on team nights out. We had Blacksheep, Tanglefoot, Snecklifter, and so on. They were in a test environment so it didn’t matter. Until they went into production…
That was over 30 years ago now, but I still usually resort to beers.
But you get the joke faster now.
Btrfs with pre and post pacman-triggered snapshots. Only had to use it once, but it was very smooth.
This is the way.
Yes, that’s the point. The limit c denies the possibility of a perfectly rigid body existing physically. It can only exist as a thought experiment.
cannsbilism
I’m guessing cannibalism. But where are you shopping?
Yeah, I have a script that toggles my Dell XPS between full charge and 80%, as I’m usually on mains and only need full charge occasionally.
A kind of ‘super’ print screen, in fact.
That mb appears to have 8 channel audio on the backplane (7.1) and maybe another stereo header for the front panel headphones? That would make 10 channels in total which fits…
Interesting. Is the orange line on the board separating the audio section from the rest?
You’re probably right—I searched for ‘20 mosfets in parallel’ or something like that and it came up near the top. But I didn’t read the whole thing.
I guess there’s got to be some reason for using so many though?
My gut feeling is they didn’t put 20 there in case you scraped one off. But likely the others will have enough leeway to cover for it. If the power rail gets stressed enough, it might well fail sooner than it would have.
From the TI briefing note:
Paralleling power metal-oxide semiconductor field-effect transistors (MOSFETs) is a common wayto reduce conduction losses and spread power dissipation over multiple devices to limit the maximum junction temperature.
It would also provide redundancy in case of a failure—if you had only one, and it failed (or was scraped off by an over-enthusiastic GPU installation), you would probably not be going to space today.
I think I covered this the last time you posted, but swearing isn’t a sign of maturity. It’s generally a sign of limited vocabulary.
You may need to reconsider this view. One example (there are others):
https://www.sciencedirect.com/science/article/abs/pii/S038800011400151X
Yeah, I was being trite but still there is a reason. Idle doesn’t mean doing nothing. Perhaps it’s obscure, perhaps as impenetrable as some combination of machine state and number of milliseconds since 1970 being an even number. But you could try to track it down.
And sometimes the easiest thing is to reinstall from scratch.
Nothing crashes for no reason. Until you identify the reason, you’re employing stochastic problem solving.
That has a little too much rhythm for me. I’d recommend some Fushitsusha
So I’m normally a command line fan and have used git there. But I’m also using sublimerge and honestly I find it fantastic for untangling a bunch of changes that need to be in several commits; being able to quickly scroll through all the changed files, expand & collapse the diffs, select files, hunks, and lines directly in the gui for staging, etc. I can’t see that being any faster / easier on the command line.
I wandered in here from computer science, and I’m going back to solving parallel cache coherency for a bit of light relief.
Lots of percussive maintenance going on around here, but one that sticks in my mind was testing some of the first 486DX PCs in 1990. One particular specimen from Compaq would only boot after hard power off by taking the lid off and tapping the CPU with a screwdriver. Worked fine after that.