So. You already know what’s happening here (probably) because the title is obvious (hopefully). But for the title-skippers in the crowd I’ll lay out the introduction-with-waffle: far too often I find myself having a go at a duck, in an effort to educate myself (again) about good partitioning schemes for new Linux installations (in this case Debian).
I’m tired of doing that, so now we have this post to document my latest preferred partition scheme. Now, when (not if) I’m repeating this Linux/Debian installation exercise in the future, I’ll just have a go at myself.
Can you tell what it is? Can you tell where it’s gone?!
An Internet (maybe) to the first person to comm-… err, actually, no, there aren’t any Internets for this (not even maybe). That’d be ridiculous. Total, flagrant disregard for manufactured scarcity. Can’t have it (actually still maybe).
Let’s see just how much we can narrow the target audience for this post, shall we?
Do you use RSS feeds to keep up with the news? Do you host your own TT-RSS server to monitor those RSS feeds? Are you running a Sandstorm instance (bonus question: on the Oasis platform)? Do you run your TT-RSS server as a grain on your Sandstorm instance? Do you use the night.css TT-RSS theme? Finally, do the greyscaled images of the theme annoy you?
If you answered yes to /all/ of those questions, you are probably one of these: a) you are me (hello), b) you follow, and use, the news-upkeep methods I describe alarmingly closely, c) the internet brought you here when you searched for a solution to your annoyance and somehow we do the same things and this is exactly what you were looking, and we’re clearly cosmically connected or whatever (make of that what you will).
All that is a very long way of saying that I have made startlingly basic CSS modifications to my TT-RSS theme to stop it greyscaling the images in my feeds, and I’m about to describe just how I did it.
Research finished! It took ’em years, but Blizzard has finally made good on delivering a long-anticipated full-feature movie with Warcraft. Does it sail on gryphon wings or plummet to the depths of the naga?
Want a tip? Have a tip. Sometimes tech, sometimes life, sometimes not a tip at all. Now faced with the prospect of not posting this month (shock and horror!), I throw ’em out there with wild abandon.
Satisfy* your hunger after the jump.
Have you ever set a GRUB boot password, unwittingly buggering it up with a typo, and then panicked when your rebooting host claimed you were giving it the wrong password so it wouldn’t boot? On an LVM disk system? I have. Just last week, in fact. Wanna know how I fixed it?
Hit the jump, then.
I’m totally not compensating for failing to post in March.
Just thought I’d get that out of the way. Y’know, to ward off questions.
Many moons ago (like two damn years’; wowzor ‘n stuff), I pumped out text detailing how I keep up with the news-ey things that interest me. Well, the inexorable passage of time has seen that old post turn to a falsehood. Now I, in a narcissistic revisitation of old material, decided it was high time I let my valuable readers know that things just don’t work like that any more.
So here’s something that took me an embarrassingly long to time figure out: (Arch) Linux doesn’t like it when you have multiple network configuration utilities set to connect you to a network. In my case, a wireless network. In fact, the same wireless network for both utilities.