You sound like a democrite rather than a liberal. Hitlary's gang is about as liberal as repugnicants, both pro- and anti-Drumpf, are conserving anything.
She's also actually more racist than Trump, and that's quite an accomplishment. And far more a bigot -- on the other hand, Trump is far, far more an idiot.
We really don't want systemd to do its "dependency logic" for mounts. Case in point: have a btrfs RAID, physically remove one of its disks and mount with -o degraded. A basic operation that doesn't involve an init daemon and is impossible to get wrong, right? Not on systemd. If your RAID happens to be in fstab (ie, any real case other than when running from rescue media), systemd will helpfully instantly unmount it again. There's no known workaround for this bug other than commenting out the mount in fstab (or upgrading to sysvinit...).
I don't get how one could possibly screw this up. So systemd runs a daemon statting all your mountpoints just so it can unmount them if it believes some dependency isn't met?!?
Other cases where it messes with filesystems are not better. Where rsyslog goes to great lengths to ensure logs survive a system crash, sometimes even in annoying ways (like disk spinup on laptops) and uses append-only plain text logs that are readable even when heavily corrupted, systemd not only makes corruption and total data loss nearly guaranteed, but even goes out of its way to disable data consistency features (checksums, protection from torn writes, transactions) because "performance" and spams you with warnings if you manually turn them back.
HELL YEAH! Bring in a new N900 and I'll jump at it even if the specs would suck. In fact, I still use a N900 as iToys and Android are fit for a fart app and maybe a Fecesbook status update or two, but nothing more.
N900's keymap was brain-dead (most symbols required a pull-up menu) but, as Maemo used regular sane X, it's nothing you can't fix. Once you have full ASCII available, you are set for long hacking sessions without even bothering to fire up the big computer. Yes, I do use my phone nearly exclusively for its text terminal, like a proper Unix greybeard should. And there's no need to ssh out, it can run gcc, postgres, perl or whatever you want just fine (although with 256RAM it sucks so you want ssh unless you're stuck on a family gathering in a bumfuck village with no network access).
Do you type "const int one=1, two=2;" before every line, too? Sorry, with your scheme that'd be "const int one = 1; const int two = 2;". I fail to see a benefit other than getting Cobol fingers...
That 512MB RAM costs peanuts for a single virtual machine, yeah. But what if you run hundreds or more? Wasting 10% memory suddenly means you need 10% more hardware for the same number of customers if their VMs tend to have small CPU and I/O needs outside load spikes and thus need mostly RAM for adequate performance.
My uneducated guess would be a similar complaint rate as email spam (as ads are a form of spam). That is, a sane person takes steps to block the spam/ad and quickly learns that complaining to the spammer is futile, and worse, lets them know the ad/spam was read.
Sorry to let you such disturbing news, but there is a world outside the USA. Here, automatic transmission is derided akin to training wheels on a bicycle, and every armchair engineer will tell you how much worse acceleration you get with auto.
While this was not my original reason, this article makes me smug for using a pair of old 1280x1024 monitors. I run one over DVI, one over VGA. Especially VGA ones are a dime a dozen, if you shop around you can get a high quality used one under $20. With old monitors it's random whether you get one that flickers, has a high blue/etc loss or similar flaws -- but even if you can't return, it's $20 for another try. VGA ones also require adjustment, but if you press auto-adjust over a proper test screen rather than your desktop, analog-to-digital artifacts can be almost completely eliminated.
VGA provides no way for smuggling malware, and DVI ones are way too old to be vulnerable for such tricks. As an extra bonus, you get a sane aspect ratio rather than a modern narrow strip.
So here's a compromise: block only third-party domains -- not just javascript, everything (advertising, tracking, etc). With an extension like RequestPolicy, a site that is stored on multiple servers might require an action to be usable, but it's pretty obvious what to allow. And you need to whitelist requests only on the first visit.
The ioccc is merely unreadable, it makes code really stand out. Instead, you want Underhanded C where code must be clear, appear good and pass code review.
Slashdot Mirror
You sound like a democrite rather than a liberal. Hitlary's gang is about as liberal as repugnicants, both pro- and anti-Drumpf, are conserving anything.
She's also actually more racist than Trump, and that's quite an accomplishment. And far more a bigot -- on the other hand, Trump is far, far more an idiot.
By state count or by area, that's little. But by population count, 60% of USians live in the constitution-free zone.
We really don't want systemd to do its "dependency logic" for mounts. Case in point: have a btrfs RAID, physically remove one of its disks and mount with -o degraded. A basic operation that doesn't involve an init daemon and is impossible to get wrong, right? Not on systemd. If your RAID happens to be in fstab (ie, any real case other than when running from rescue media), systemd will helpfully instantly unmount it again. There's no known workaround for this bug other than commenting out the mount in fstab (or upgrading to sysvinit...).
I don't get how one could possibly screw this up. So systemd runs a daemon statting all your mountpoints just so it can unmount them if it believes some dependency isn't met?!?
Other cases where it messes with filesystems are not better. Where rsyslog goes to great lengths to ensure logs survive a system crash, sometimes even in annoying ways (like disk spinup on laptops) and uses append-only plain text logs that are readable even when heavily corrupted, systemd not only makes corruption and total data loss nearly guaranteed, but even goes out of its way to disable data consistency features (checksums, protection from torn writes, transactions) because "performance" and spams you with warnings if you manually turn them back.
ip6tables -t nat -- this NAT? There are good uses of NAT, although not what most people are thinking of.
HELL YEAH! Bring in a new N900 and I'll jump at it even if the specs would suck. In fact, I still use a N900 as iToys and Android are fit for a fart app and maybe a Fecesbook status update or two, but nothing more.
N900's keymap was brain-dead (most symbols required a pull-up menu) but, as Maemo used regular sane X, it's nothing you can't fix. Once you have full ASCII available, you are set for long hacking sessions without even bothering to fire up the big computer. Yes, I do use my phone nearly exclusively for its text terminal, like a proper Unix greybeard should. And there's no need to ssh out, it can run gcc, postgres, perl or whatever you want just fine (although with 256RAM it sucks so you want ssh unless you're stuck on a family gathering in a bumfuck village with no network access).
Do you type "const int one=1, two=2;" before every line, too? Sorry, with your scheme that'd be "const int one = 1; const int two = 2;". I fail to see a benefit other than getting Cobol fingers...
More terse code tends to be more readable.
Eh? That's one of nicer features of C. Think of if ((x=somefunction())), or related switch(x=somefunction()).
That 512MB RAM costs peanuts for a single virtual machine, yeah. But what if you run hundreds or more? Wasting 10% memory suddenly means you need 10% more hardware for the same number of customers if their VMs tend to have small CPU and I/O needs outside load spikes and thus need mostly RAM for adequate performance.
So they put their program on pid 1, on bare BIOS^Wkernel? Ah booters of the old times...
And this line made me smile:
System Docker replaces traditional init systems like systemd
So CADTs are moving away from systemd as fast as they flocked to it, while the rest of us are smirking.
"Every nonfree program has a lord, a master -- and if you use the program, he is your master."
Or better, consider every network to be untrusted. No nasty surprises this way.
RequestPolicy. A blacklist leaks junk constantly, being a game of whack-a-mole. A whitelist, on the other hand, kills all non-first-party ads dead.
This has been tried three decades ago by viruses, and has been kind of solved. And the resemblance is telling: Facebook is malware.
My uneducated guess would be a similar complaint rate as email spam (as ads are a form of spam). That is, a sane person takes steps to block the spam/ad and quickly learns that complaining to the spammer is futile, and worse, lets them know the ad/spam was read.
I haven't seen SGI products in years.
Well, their IRIX workstations were just pure awesomesity!
"Being lazy is a sign of high intelligence" -- I knew it, this means I must be an underappreciated super-genius!
Sorry to let you such disturbing news, but there is a world outside the USA. Here, automatic transmission is derided akin to training wheels on a bicycle, and every armchair engineer will tell you how much worse acceleration you get with auto.
It's not about the analog port, it's about the monitor being old and thus "dumb".
Eh, why would anyone use CRT? There's been a decade of fine LCD ones before the aspect ratio went apeshit.
While this was not my original reason, this article makes me smug for using a pair of old 1280x1024 monitors. I run one over DVI, one over VGA. Especially VGA ones are a dime a dozen, if you shop around you can get a high quality used one under $20. With old monitors it's random whether you get one that flickers, has a high blue/etc loss or similar flaws -- but even if you can't return, it's $20 for another try. VGA ones also require adjustment, but if you press auto-adjust over a proper test screen rather than your desktop, analog-to-digital artifacts can be almost completely eliminated.
VGA provides no way for smuggling malware, and DVI ones are way too old to be vulnerable for such tricks. As an extra bonus, you get a sane aspect ratio rather than a modern narrow strip.
The best solution is a manual transmission. So few people know how to drive them now they're practically magic.
I haven't been in an automatic one in my life, so your estimate is off. Poland.
Unauthorized access sees you paid 95%.
Make that 5000% and we can start talking about there being some downsides to tracking (for the tracker).
Google still returns massively better results than DuckDuckGo. And for spying/tracking, there's Tor.
So here's a compromise: block only third-party domains -- not just javascript, everything (advertising, tracking, etc). With an extension like RequestPolicy, a site that is stored on multiple servers might require an action to be usable, but it's pretty obvious what to allow. And you need to whitelist requests only on the first visit.
The ioccc is merely unreadable, it makes code really stand out. Instead, you want Underhanded C where code must be clear, appear good and pass code review.