I consider it debate practice, like verbal shadowboxing. He’s throwing the punches, and I need to parry them. It’s fun!
Then you get to compare notes with the debunking vireos and yell at those viewings about what they missed.
I’m just this guy, you know?
I consider it debate practice, like verbal shadowboxing. He’s throwing the punches, and I need to parry them. It’s fun!
Then you get to compare notes with the debunking vireos and yell at those viewings about what they missed.
As you like. Cheers, mate!
It’s good entertainment. Don’t short yourself, and just watch it (edit: critically) as a travel vlog.
The debunking videos are going to be so educational though! I, for one, cant wait!
I say “oh, good!” only because I enjoyed falling asleep listening both to the show and to the many debunking videos that came out on YouTube afterwards. My current favorite is the Miniminuteman analysis, which is hilarious.
I’ve been looking for some new long-form content to sleep to. Now I have something to look forward to!
This is peak 2rd quarter hot/crazy scale
| /
^ | +
hot |/
+--------
crazy>
```
Also, I’m very tired right now. I’ll explain stuff better later when I wake up.
If you’d bought a 2TB you could just dd
image the windows disk to the new drive. If you can convince Windows to downsize its partition and then use a partition editor on a USB liveboot to identify the drive sectors you could maybe still image the windows disk. Big “if.”
As to the second question, use block IDs-- the filesystem’s UUID. Grub is lazy and assumes a single root (the first found) partition so if you want a particular boot entry to use a specific root slice, you’ll need to ensure each OS entry in grub uses the right UUID for its kernel root
parameter. Loading the right root gets you the rigjt /etc/fstab to mount that root’s expected partitions
Honestly you’d be better off running your stuff in VMs. Dual-boot is a nightmare.
I am really not sure how I feel about this. It feels like when Cisco Systems bought Kalpana back in '94 and brought us the Catalyst 3000. So sexy, much disaster. Very bugs.
I really wanted to like that switch. It got better, but so did I.
Where was I?
Oh right: Qualcomm buying Intel. That’s not gonna help anything or anyone. Bad idea.
Since everything Trump says is a lie does that mean he’s considering it?
deleted by creator
They’re… silly. Lots of counterculture references.
Time will tell whether this was the cat that killed MAGA, or just the cat that killed America.
Either way, we need a pic of the cat! The memes will be epic.
Edit: before the Schrödinger’s cat jokes start, this timeline is looking more and more uncannily like the one in The Schrödinger’s Cat trilogy by Robert A Wilson.
Starship Enterprise launcher!
Ironic, isn’t it?
I just checked and he still says ‘we’ didn’t start the fire. Emphatically, in fact. Several times, even.
Seems that yep, this is all that Trump fella’s fault.
When you’re angling to be a minion of Cruz, its the epitome of aspiring to sub-mediocrity.
Who’s fully mediocre? I dunno… At random, Jack Reed maybe?
Trump is the Crystal Pepsi of politics. Basically poison, crushed-up bugs and baby oil flavored sugar water. Totally transparent, and dragging down the brand.
Hell, even Tab Clear was better. Source: the cafeteria at my high school stocked both back in the day. They were both bad
edit: Tab Clear was a thing!
No worries, the other poster was just wasn’t being helpful. And/or doesn’t understand statistics & databases, but I don’t care to speculate on that or to waste more of my time on them.
The setting above maxes out at 24h in stock builds, but can be extended beyond that if you are willing to recompile the FTL database with different parameters to allow for a deeper look back window for your query log. Even at that point, a second database setting farther down that page sets the max age of all query logs to 1y, so at best you’d get a running tally of up to a year. This would probably at the expense of performance for dashboard page loads since the number is probably computed at page load. The live DB call is intended for relatively short windows vs database lifetime.
If you want an all-time count, you’ll have to track it off box because FTL doesn’t provide an all-time metric, or deep enough data persistence. I was just offering up a methodology that could be an interesting and beneficial project for others with similar needs.
Hey, this was fun. See you around.
You must not be familiar with Shepherd breeds.