I’m just this guy, you know?
Not here. I don’t use Windows and so I rebind the Win key (or, Super) for some quick functions.
Win + L to lock the screen
Win + K to blank it
Win + C for my calculator app
Win + T (and Ctrl+Shift+T) for a Terminal
Win + Left/Right arrow to cycle to the previous/next desktop
Bonus fun, I rebind the Right Alt key to a Compose key for typing Latin-1 diacritics in non UTF-8 applications. (Plus, I can’t remember the U-codes)
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.
Two’s too many to count
And two other to’s
King Biden yeeting the skibidi toiletries.
Or… something. I don’t even known what I just said.
Its ambiguous, but it seems to expresses the speaker regrets not feeling regretful about the topic, as if to acknowledge that one might (and maybe should) sympathize with the other party, but in fact does not.
Depending on the context, it might also merely express that speaker is an asshole.
Starship Enterprise launcher!
My next mower will probably be a lawn service
San Jacincto was a different battle wherein Mexico got their collective ass kicked in there. The Alamo was a rallying cry.
Alamo itself was a rout for the Texians [sic]. There’s no side-stepping that. It goes as it goes.
I didn’t so much forget it as I did assume Texans were just playing the martyr for getting their collective asses kicked in. Again.
You know… Like Dallas Cowboys fans?
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.
If you’re wrong then I don’t wanna be right.
Removed by mod
#### MAXLOGAGE=24.0
Up to how many hours of queries should be imported from the database and logs? Values greater than the hard-coded maximum of 24h need a locally compiled `FTL` with a changed compile-time value.
I assume this is the setting you are suggesting can extend the query count period. It still will only give you the last N hours’ worth of queries, which is not what OP asked. I gather OP wants to see the cumulative total of blocked queries over all time, and I doubt the FTL database tracks the data in a usable way to arrive at that number.
Ah, well if you know differently then please do share with the rest of us? I think the phrasing in my post makes it pretty clear I was open to being corrected.
So, like a running sum? No, I don’t think so, not in Pi-hole at least.
Pi-hole does have an API you could scrape, though. A Prometheus stack could track it and present a dashboard that shows the summation you want. There are other stats you could pull as well. This is a quick sample of what my home assistant integration sees
Oh, jeez. I remember reading that book in elementary school!
Thanks for the horrific trip down memory lane, ya bastid. Happy Halloween, too.