Re: Applying patches .... please wait
Oh no, guess I'm out a can of coke.
That's neat, though. Thanks.
2678 publicly visible posts • joined 5 Mar 2007
The bit is getting old, mate.
Studying the "nothing but rocks" of Mars gives us an insight into processes that took place on earth but are no longer observable due to differences in atmospheric composition. There are geological structures on Mars that are impossible to observe here, because here they would be chemically destroyed by the ongoing presence of liquid water, whereas there they can sit out in the open without damage. By studying that, we can gain a better understanding of the history of our own planet's history.
but we do have Brexit, a deadly pandemic, global warming, riots in Belfast, warfare and starvation in Yemen, and lots of other really important things to think about (not to mention my vacuum cleaner packing up), so hopefully the news outlets will cover other important items too, eventually.
They'll all still be around next week and likely won't have changed much in the meantime.
That's been the problem from day one. As an init, it's fine. Starts services in a neat, orderly way with a consistent configuration.
Why does it have to glom logging and device management and networking and inter-process communication and user management and home directories and container management and file system overlays... and so on and so forth.
There's never a rational explanation for it.
Except it's real. The link to the official release news was right in the article, with its last commit on the 30th, and this particular part of the release was being touted in release-candidates back in February.
I had exactly the same problem this week. New laptop with an ubuntu-based OS, which in most other regards is a very nice machine, but the networking just killed me. I couldn't resolve anything on my lan no matter what I tried. I was at least able to disable resolved and put network manager back in charge of resolv.conf, which is a step in the right direction at least. Now it gets its nameservers from the dhcp lease instead of that convoluted solution to something that was only ever a problem in poettering's mind.
Somewhat related, I had a weird problem with pulseaudio as well. It appears to have found a way to crash my docking station by sending a power down command to the idle sound hardware in it. Another obscure configuration to change. Hooray.
Similar arguments were used by the luddites.
At the individual level they were right, because they were losing their employment, but at the macro level they were wrong, because automation of their jobs removed the need for future generations to put their children under running machinery or spend their lives destroying their bodies for someone else's profit.
Automation of repetitive manual labour is always a net good for society. For just one example, look at farming. Harvesting a few fields of wheat used to require hundreds of people working for days. Now two people can do the work of those hundreds in half the time. Automation in farming increased the efficiency of land use enough to supply more food than the human race physically needs from less land that was used a century ago (though the issues over how that food is distributed leave a lot to be desired, and up to a third of that food is lost due to lack of proper storage facilities in the third world).
The only thing that ultimately justifies the retention of human labour for many repetitive jobs is that the supply of human labour is currently significantly cheaper than the machine, especially as much of the lowest paid labour comes from economic migrants who end up paid just enough to survive and nothing more.
It might suck in the short term, especially for the individuals involved, but that's not an argument against automation in and of itself, otherwise most of us would still be harvesting someone else's crops by hand.
"Main" implies a hierarchy of acceptability, inasmuch as anything that is not "main" is lesser and subservient to "main". To call a particular otherwise co-equal branch of the repository "main" is to other branches that are not mainstream, or in other words, to impose the hierarchical modes of thought inherent to the white supremacist behaviours of contemporary society, that discriminated against black and brown bodies that fall outside of the "main", where they are pushed to the fringes by white conceptualisations of structural oppression and racism.
From the look of things they're using poorly formatted JSON in their API requests, setting "true" or "false" as a string values instead of a boolean, then "fixing" that by explicitly re-casting any string with the value of "true" or "false" as a boolean value. This is bad for a lot of reasons.
I'm currently waiting for ups to get off their backsides and deliver a package from Spain. They've had it in Madrid for over a week now, blaming Brexit even though other couriers just sail right through without issue.
Every time ups is the courier, something goes wrong. The most memorable recently was when they destroyed half of an order of national heritage mead and didn't bother to warn me before they left a sodden, glass-filled box on my doorstep. They only very reluctantly responded to the seller's compensation claim after a month.
It's because we're retained the EU's VAT rules and regulations and are applying them at our border the same way the EU applies them at its border.
Within the customs union, if you were to import goods from a seller in a third country, and the seller hasn't made the appropriate registrations and arrangements to collect VAT on behalf of the EU territory into which they're selling (and very few did), VAT would be applied and collected at the common customs border.
We've retained that portion of the acquis, so now imports from outside the UK have VAT applied at our border. This includes imports from sellers inside the EU, who shouldn't be applying VAT to UK sales, and should be supplying the same paperwork they'd supply to exports (including RMAs) to any other third country.
Our exports to the EU also have VAT and other duties applied at the EU border. Sales outside of the UK's VAT regime don't have UK VAT applied, as has been the norm when selling to places outside of the EU when we were part of it, so anyone selling from the UK to the EU shouldn't be adding VAT to the price.
VAT wasn't part of the trade agreement, which is really more of a framework agreement than an actual trade deal. Some future agreement on VAT might be negotiated within that framework, but I expect it's low down on the priorities.
The point is, we're applying the rules as inherited. Now whether the government will be keen to change those rules is anyone's guess (I'm going out on a limb to predict the only changes they'll make are the ones that they think will bring in more revenue), but blaming the government for the existence of these rules is a bit parochial, given they were originated by the EU and are now being mutually applied, unchanged, by both parties to one another as they would to any other third country.
init
option in sixth birthday release
You shouldn't. One of the touted features of Pulse Audio was that it could synchronise streams across a network to multiple devices, which I thought might be lovely for a whole-home audio system. It worked great on ethernet, as far as I tested it anyway, but the moment you introduced a wireless device, the entire network would be swamped with traffic and fall apart. It was a very well documented and reported bug.
Poettering marked it WONTFIX and refused to address it for years, presumably because he couldn't understand why someone would want to stream audio over wifi to a device that wasn't in a position to be wired. I suspect it's still not fixed, even today.
It's all about specific impulse, or the efficiency of thrust to fuel expended. Our current engineering cannot match the requirements, but we have tested small-scale engines that are capable of a much higher specific impulse; they're just not capable of particularly high thrust. Not yet. There are also theoretical engine technologies that have yet to be tested, but which are more than merely hypothetical due to the fact that all of the components already exist in some form, though not yet in a form robust enough to be used for the purpose.
To say it can never be done because we're not able to do it now is a weird sort of arrogance, especially when all of the necessary components already exist.