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.
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.
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.
Also, I'm very tired right now. I'll explain stuff better later when I wake up.