Your whole rant is ridiculous because the problems you encountered were due to the driver not being open source, which apparently is now going to change
but each blockchain transaction can be expensive, especially if you want to see it posted anytime in the next few days.
Slightly less wrong, but still wrong. Last time I made a BTC transaction, I set the transaction fee to zero. It took a few hours but eventually the miners picked it up.
I've had numerous instance of "service xyz restart" not restarting the service yet not producing an error message AND giving exit code 0. It might be due to debian's unit files being a mess, but that doesn't really change anything.
Disclaimer before someone calls me out on the BSD message above: I have to fiddle with Linux at work.
Sorry, gmail keeps locking me out so I miss/get delayed a lot of reply notifications these days.
Anyway, at speeds we can reach with our technology, it would take around 5 million years to cross the galaxy.
I guess this is true when only considering speed. I think there's a lot more to crossing the galaxy in 5M years than velocity alone.
Only ONE of those 10 billion worlds has to have intelligent life begin to colonize the galaxy a mere 5 million years before we started talking about it to arrive by tea time tomorrow.
Dunno. This is based on the assumption that galactic colonization is a) desirable and b) happens in a von Neumann probe sort of way, which would be a different matter altogether.
If you want you can write a ~130 line perl program
I'm shocked it takes 130 lines of perl to decode the logs. Seriously how complex can the format be?
It's a fucking computer. Everything on computers is binary!
Sure, and there' sone particular set of binaries that are immediately accessible to humans; it's called text files.
IOW you're missing the point. I don't want to have to depend on whatever tiny ass rescue system I boot for disaster recovery to ship a perl interpreter (not to mention the native infrastructure to decode the logs)!
I wonder how the universality and thus the usefulness of text files is such a difficult concept to grasp.
To me, the fact that the major distros have adopted systemd is strong evidence that it is probably better.
Raises the question, better for whom? Systemd seems to make some things easier for distro maintainers, at the cost of fucking shit up for users and admins.
That said, Debian's vote on the matter was essentially 50:50, and they're going to keep supporting SysV init. Most distros are descendants of Debian, so there's that. Redhat switched for obvious reasons (having the main systemd developer on their payroll and massively profiting from increased support demands).
Can I ask, why don't you and other admins/devs like you start to contribute to systemd?
Adding more code to something already hugely overweight isn't going to make things better. I can only think of one kind of contribution that'd be worthwhile: rip out a lot of code. I'm not convinced this sort of contribution would be accepted.
And generally I've much better plans to do with my time instead of joining a project I hate. For instance, my ceiling has this funny dot pattern and I still haven't gotten around to counting all the dots.
I also think the fact that we've never found any evidence of such is probably a pretty good indication that the difficulty of traversing the void between stars is likely insurmountable even if you're an AI in radiation-hardened hardware.
I'm not sure that's right -- on a cosmic scale we really haven't been looking for all too long yet, and we're such a small target to hit - or put differently, the universe is so huge - that even with a viable means of bridging those distances, it wouldn't seem all too likely to be run into just by chance (especially not in the short timespan in which we could actually tell what's going on). For all I know, the various stories about gods and angels and whatever might as well be based on such encounters;)
$100k is like nothing compared to $90m. Since it's a test flight, they sure wouldn't want to carry a $90m payload as well. In these dimensions it really doesn't change anything whether your payload is a $100k car or a $100 block of steel. Except for the PR
HTTPS doesn't hide anything from the endpoint. That should be obvious?
If you mean the destination web server can decrypt the https traffic, then yes, it's obvious. The only difference between HTTP and HTTPS in this case is that when HTTPS is used only the destination web server can see the plaintext as opposed to every router and every three latter tap on the its path.
However, it does largely defeat the multipathing, proxy caching and rewriting possible with HTTP, all of which helps hide who accesses an endpoint
All of which also helps mess with the traffic and watch and filter the traffic on its way. That said, caching and rewriting are things that could be done locally.
as well as automatically adding an immutable identifier; the session key.
The session key is not immutable, it isn't called session key for nothing. It's about as immutable as the address+port 4-tuple that identifies a particular TCP connection.
When I access http://www.fbi.gov/ and the proxy I use serve it from cache, the site won't even know that I accessed it. And when I ask for http://ww.cia.gov/page1 and http://www.cia.gov/page2 and the request comes from two different IPs, the site doesn't know that it's the same client accessing both pages. And when I access http://www.inflatableunicorns.... and my proxy deletes tracking information from the header (including IP address and browser fingerprints), they don't know that I'm the same person who visited last week. And they won't know that I looked at adcampaign.jpg either, because it can be served from a cache.
I get it, you like proxies and the ability to mess with and inspect your traffic on the way. It's ridiculous that you're oh-so-concerned about preventing three letter agencies from tracking you that you're opening them every door to get much better information - your payloads as opposed only your metadata. And obviously they're free to add their malware to your every download.
Now enter HTTPS, and how it changes this by trying to ensure a 1:1 connection.
Changes it mostly in a positive way, as pointed out.
the three letter agencies [] sit at the endpoints
For every endpoint where such an agency is actually sitting, there are 10 regular midway taps such an agency is operating.
I am, however, glad that you at least dropped the notion that https used client certificates. One step at a time.
Slashdot Mirror
Cool story. Now be a good consumer and purchase more products. Only way to get that feeling of pride and accomplishment.
Your whole rant is ridiculous because the problems you encountered were due to the driver not being open source, which apparently is now going to change
If "service xyzzy restart" doesn't work then "systemctl restart xyzzy" wouldn't work either
Yes. So?
It is infinitely divisible
Wrong.
but each blockchain transaction can be expensive, especially if you want to see it posted anytime in the next few days.
Slightly less wrong, but still wrong. Last time I made a BTC transaction, I set the transaction fee to zero. It took a few hours but eventually the miners picked it up.
I kind of agree that AD is a "must out of the box". At least it has no place in my box.
Now if this isn't a textbook win-win situation I'm not sure what is. :)
I've had numerous instance of "service xyz restart" not restarting the service yet not producing an error message AND giving exit code 0. It might be due to debian's unit files being a mess, but that doesn't really change anything.
Disclaimer before someone calls me out on the BSD message above: I have to fiddle with Linux at work.
for example he refuses to merge any patch that improves cross-platform compatibility.
As a BSD user, I'm incredibly happy about this decision.
Sorry, gmail keeps locking me out so I miss/get delayed a lot of reply notifications these days.
Anyway, at speeds we can reach with our technology, it would take around 5 million years to cross the galaxy.
I guess this is true when only considering speed. I think there's a lot more to crossing the galaxy in 5M years than velocity alone.
Only ONE of those 10 billion worlds has to have intelligent life begin to colonize the galaxy a mere 5 million years before we started talking about it to arrive by tea time tomorrow.
Dunno. This is based on the assumption that galactic colonization is a) desirable and b) happens in a von Neumann probe sort of way, which would be a different matter altogether.
systemd-resolved is an optional package that only a clown would think of installing in a datacenter.
Yeah, much like the rest of systemd.
I agree. TFA reads like "We are having development issues, therefore systemd sucks."
Welcome to development.
Except they're trying to host VMs, not develop software.
Nice job pretending to read TFA.
If you want you can write a ~130 line perl program
I'm shocked it takes 130 lines of perl to decode the logs. Seriously how complex can the format be?
It's a fucking computer. Everything on computers is binary!
Sure, and there' sone particular set of binaries that are immediately accessible to humans; it's called text files.
IOW you're missing the point. I don't want to have to depend on whatever tiny ass rescue system I boot for disaster recovery to ship a perl interpreter (not to mention the native infrastructure to decode the logs)!
I wonder how the universality and thus the usefulness of text files is such a difficult concept to grasp.
you do realize that they have to support it, right?
You realize that this is their business model, right?
if systemd caused an increase in support instances, they'd do something about it.
Yeah. They'd sure hate an increased demand in their product (support!) and do what they can to avoid that. /s
Uh, Redhat? You know, the company whose business model is commercial support for their Linux distribution.
Because it's totally their own address and not one of someone they hate and want to see subscribed to penis enlargement mailing lists.
Oh come on, just hexdump(1) your logs. How hard can it be.
Kids these days.
To me, the fact that the major distros have adopted systemd is strong evidence that it is probably better.
Raises the question, better for whom? Systemd seems to make some things easier for distro maintainers, at the cost of fucking shit up for users and admins.
That said, Debian's vote on the matter was essentially 50:50, and they're going to keep supporting SysV init. Most distros are descendants of Debian, so there's that. Redhat switched for obvious reasons (having the main systemd developer on their payroll and massively profiting from increased support demands).
With Debian and Redhat removed, what remains on the list of major distros?
Yeah.. strong evidence...
Can I ask, why don't you and other admins/devs like you start to contribute to systemd?
Adding more code to something already hugely overweight isn't going to make things better.
I can only think of one kind of contribution that'd be worthwhile: rip out a lot of code. I'm not convinced this sort of contribution would be accepted.
And generally I've much better plans to do with my time instead of joining a project I hate. For instance, my ceiling has this funny dot pattern and I still haven't gotten around to counting all the dots.
Technology doesn't hold still.
Doesn't mean that just because a technology is new it's automatically a good idea, great-grandpa.
Love, a NetBSD-on-everything millenial who'd pick Slackware if forced to use Linux
I also think the fact that we've never found any evidence of such is probably a pretty good indication that the difficulty of traversing the void between stars is likely insurmountable even if you're an AI in radiation-hardened hardware.
I'm not sure that's right -- on a cosmic scale we really haven't been looking for all too long yet, and we're such a small target to hit - or put differently, the universe is so huge - that even with a viable means of bridging those distances, it wouldn't seem all too likely to be run into just by chance (especially not in the short timespan in which we could actually tell what's going on). For all I know, the various stories about gods and angels and whatever might as well be based on such encounters ;)
What about machines driven by strong AI built by some advanced life-as-we-know-it kind of civilisation, though?
You're so smart.
Joke aside, "as we know it" is implied because at this point we only know one way.
$100k is like nothing compared to $90m. Since it's a test flight, they sure wouldn't want to carry a $90m payload as well. In these dimensions it really doesn't change anything whether your payload is a $100k car or a $100 block of steel. Except for the PR
If you try to be a Grammatiknationalsozialist on the Internet then at least spell the words right.
Love from Germany!
HTTPS doesn't hide anything from the endpoint. That should be obvious?
If you mean the destination web server can decrypt the https traffic, then yes, it's obvious. The only difference between HTTP and HTTPS in this case is that when HTTPS is used only the destination web server can see the plaintext as opposed to every router and every three latter tap on the its path.
However, it does largely defeat the multipathing, proxy caching and rewriting possible with HTTP, all of which helps hide who accesses an endpoint
All of which also helps mess with the traffic and watch and filter the traffic on its way. That said, caching and rewriting are things that could be done locally.
as well as automatically adding an immutable identifier; the session key.
The session key is not immutable, it isn't called session key for nothing. It's about as immutable as the address+port 4-tuple that identifies a particular TCP connection.
When I access http://www.fbi.gov/ and the proxy I use serve it from cache, the site won't even know that I accessed it. And when I ask for http://ww.cia.gov/page1 and http://www.cia.gov/page2 and the request comes from two different IPs, the site doesn't know that it's the same client accessing both pages. And when I access http://www.inflatableunicorns.... and my proxy deletes tracking information from the header (including IP address and browser fingerprints), they don't know that I'm the same person who visited last week. And they won't know that I looked at adcampaign.jpg either, because it can be served from a cache.
I get it, you like proxies and the ability to mess with and inspect your traffic on the way. It's ridiculous that you're oh-so-concerned about preventing three letter agencies from tracking you that you're opening them every door to get much better information - your payloads as opposed only your metadata. And obviously they're free to add their malware to your every download.
Now enter HTTPS, and how it changes this by trying to ensure a 1:1 connection.
Changes it mostly in a positive way, as pointed out.
the three letter agencies [] sit at the endpoints
For every endpoint where such an agency is actually sitting, there are 10 regular midway taps such an agency is operating.
I am, however, glad that you at least dropped the notion that https used client certificates. One step at a time.