Re: Standards
Thanks, bazza. That raises the possibility of a Mil-Std for distros to meet, including SysV Init and X-Open with RedHat/IBM locking themselves out of it. Lovely!
33139 publicly visible posts • joined 16 Jun 2014
"A large part of low end mini sales of Unix systems was just as dominated by VAR software considerations as in the workstation market."
Yes. My experience was there's be a package of H/W, O/S, (Informix) RDBMS and application. That included the company's product when I worked for a VAR or some industry-specific package which was the main reason for the purchase when I worked in admin. Even where the main application was home-grown and the original purchase stopped at the RDBMS we also bought in an accounts package to work with it.
But actually building the application for distribution would be a problem for vendors, given the number of H/W architectures they had to deal with. I certainly hosted at least one local VAR to build a version of their product on our HP-UX box (always keep on good terms with your local S/W house, you never know when you might want a job with them).
"No-one likes doing free work for other companies to take."
So no-one developed BSD? Or did somebody develop it and then have an "Oh shit!" moment when they got round to reading the licence? Or is it possible that those developing BSD knew exactly what the licence implied and were not only OK with the implications but welcomed them? Should they have gone to some random A/C on the internet for instruction on what licence they should have used?
There's Linus's kernel, then there are the various LTS kernels which are managed by Greg K-H. Then there are the kernels which might or night not have additional tweaks. And, as I pointed out, your own kernel if you want one. But where is the non-MS Windows kernel?
I've pointed out elsewhere that the maintainer system which FOSS projects have adapted is a good solution to the problem posed in TMMM of how to coordinate multiple developers while maintaining clarity of vision. It doesn't put the maintainer in the position of a proprietor because anyone can fork it and become a maintainer without reference to the original maintainer or anyone else. It's an important aspect. Let's not obscure that, even tongue in cheek.
You can download the entire source code of the Linux kernel. You can tweak any bit of it you think needs tweaking to make your very own version, not Linus's, not anyone else's. Yours. You can compile your tweaked version (assuming it's still syntactically correct after your tweaks). When/if you've compiled it you can run in (assuming your tweaks didn't make it crash).
Try to repeat that for the Windows kernel.
Now do you understand what proprietary means?
SCO on the laptop was my choice partly because I could run development versions of Informix products on it I could support clients running Informix on SCO servers. I never met Interactive as a desktop product but as Onix it provided my first Unix server; I believe they also ported the original Aix.
But let's look at "Does that [the Unix wars and need to compile multiple versions of applications*] sound familiar? That kind of thing is still a problem for the Linux desktop, and it's why I'm a big fan of Linux containerized desktop applications, such as Red Hat's Flatpak and Canonical's Snap."
Go and look at the download page for LibreOffice. At any time LO offers two versions for any platform, the leading edge and trailing edge versions. Check either of them. What options are offered for each version? For Linux there's 64-bit RPM and Deb. For Windows there's 64 and 32 bit. For Mac there's Intel and Apple silicon. That's right, there are no more versions offered for Linux than for Windows or Mac. Why is Linux considered to present more of a problem?
Now let's look at another staple on my desktop, Seamonkey. We have a choice of 64 and 32 bit Linux, 64 & 32 bit Windows and just x64 Mac with a choice of languages (it looks like macOS is the difficult one here, not Linux). They've even removed the RPM vs Deb choice because all that has to be done (and it's all the LO options automate for you) is copy the download over to /opt and extract it. The same method has been used for years for installing non-distro applications. What Flatpak and Snap are ostensibly solving is a non-problem, something that's never been a problem, a straw man. What they are very clearly doing is creating their own little walled gardens. What sounds familiar about them is that they're reviving the Unix wars for exactly the same reason the original wars were conducted - to conquer territory.
* In part the need to recompile was driven by multiple H/W architectures: DEC, HP, IBM, Intel, MIPS, SPARC, Zilog and various others. The only H/W choice at present is between 64 and, where it survives, 32 bit Intel** and Apple.
** And that itself is really an OS rather than a H/W choice.
I think I can spot two problems in your experimental method at step 3. First you're adding milk. This ruins it. Secondly you mention weird floaty brown stuff. This indicates you're using hard water. If you have the misfortune to be in a hard water area you should try a water softener although this may wll put sodium ions into the tea anyway.
As to Franci's argument for salt, it rests on the assumption that the bitter receptors need to be blocked. Why?
While the article mostly mentions the EU or European Union ot also, at one point, just says Europe as does the earlier linked article. So just what is the scope of these changes Apple is making? Do they just apply within the EU or also to other parts of Europe? Has Brexit once again protected UK iFans from the dangers unleashed across the Channel by those dastardly EU bureaucrats?
"if you then take all of this and you train a model on top of ... all of this distribution of data that exists out there that humans have produced ... including facts as themselves – and then you ask a model to model the whole thing and start generating data – which is statistically indistinguishable from this distribution of data – the model inherently is going to make mistakes.
And it always will make mistakes. It's infeasible to assume that in some hypothetical future, we'll build perfect models. It's impossible. "
But let's carry on anyway because we can make money out of it.
(Somewhat abridged and my emphasis.)
It's the old trade-off between convenience and security. In reality, of course, it's more a matter of trading short-term inconvenience for considerably worse long-term inconvenience.
The best simple solution for the individual is to at least use a password manager to generate per-site complex passwords. Even better is to double it up with having generating individual email addresses for each site as well. If the site's won't protect you against password-stuffing you just have to protect yourself.
"Most of that data isn't online, much of it isn't even centrally filed anywhere"
The world's rather a big place to file everything in one place but central filing of census,and BMD (births, marriages and deaths) has been instituted in many countries since the C19th.
In England and Wales, for instance, that has been done since the middle of 1837. There are crowd-sourced indexes at freebmd..org.uk. To make real progress may require purchase of birth & marriage certificates (you can click through from freebmd to the registry's online ordering site) although it's surprising what progress can be made just with such indexes and images of the census returns (useful reords startin 1841 for E&W). These would require one of the subscription services, Ancestry or FindMyPast but again quite a lot can be achieved with the free service of familysearch.org (apart from freebmd these sites cover world-wide sources).
Prior to civil registration in any given jurisdiction you would usually need to rely on religious records such as baptisms and burial regiters in place of birth and death records. These are not necessarily centrally filed although bishops' transcripts supposedly exist for the Church of England but not as complete as one would like. However local societies and individual genealogists have been transcribing and publishing these since the late C19th and a great deal of these publications can be found on archive.org and, of course, have also been transcribed by the sites I mentioned in the previous paragraph.
I have no experience with other jurisdictions except Ireland and the experience there is frustration due to the destruction of the registries in a fire in 1922. I've found it difficult to get any of my wife's lines back beyond the early C19th and one individual has proved extremely difficult.
And, of course, the occasional bastard will prove as difficult in genealogy as they do in management.
Let me guess: they use the email address as userID. This would almost invariably be the same email address their customers use on many other sites so as soon as one of those sites is compromised the full login credentials become available. While 23andme - and any other company - can't stop their customers reusing passwords* they can stop them reusing login IDs by the simple expedient of issuing their own, non-email, IDs. There's no need to go to 2FA. The only reason that that's industry standard is because email as userID is also industry standard.
* Actually there is something they can do. They can check any ID/password combination they find against haveibeenpwned, reject them and advise their customers to reeset all their other passwords. They could also monitor haveibeenpwned for additions which match their own customers' credentials and force a password reset on any that match.
"In VM's case the front line staff often seem to be the last people to hear about a wider problem, offering to send out an engineer to your home to solve a problem that is keeping half the bloody town off-line."
In BT's case the front-line staff weren't even informed that there was (presumably) planned work going on on all the connections from the local footway box but offered to send out an engineer at a cost of £80 if there was no fault. I walked down to the village first to check. I suppose we have the OpenReach split to thank for that lack of communication
On complaining that the front desk should have been informed BT marked their own homework by saying it was quite OK. I suppose I should have escalated it Ofcom but doubt the outcome would have been different - they're hardly going to say an issue ultimately of their own making is actually a problem.
"The only people who call landlines these days are scammers in Bangalore."
SWMBO is called regularly by her sister who iives a few hundred yards away and neither of us is in Bangalore. My daughter, who lives a mile or so away. My cousin-in-law. Friends to whom I regularly give a lift as they're no longer driving because of age. SWMBO calling her sister-in-law in N Ireland. Other family members. Doctors. Pharmacists. Northern Powergrid to report power failures. We receive and make a lot of landline calls. Until the great switch-off the landline is more reliable than the mobile signal and certainly better quality. After the switch off we'll be in trouble every time the power fails. Yes, I know about battery backup but the last failure took out the DSLAM and that didn't get fixed until the next day.
"we have taken immediate steps to secure and screen all systems in order to contain the incident and limit the impact on our operations,"
Translation: we've sent comeone to the ironmongers for stable door bolts.
"We take cybersecurity exceptionally seriously"
Translation: we/ve just discovered cybersecurity has to be taken exceptionally seriously"
Alternative translation: Cybersecurity is to be taken seriously but we made an exception.
You have to wonder just when it will dawn on HR types that personal data held for a moment longer than needed becomes toxic waste. Perhaps a mandatory fine of 1,000 GBEurollars per retained passport scan discovered on audit* and 10x that for each taken in a heist would have some effect. But probably not.
* It's time for compulsory unannounced audits of organisations licensed** to hold personal data of more than, say 100 people.
** Yes, it's time for such licensing.
Yes, you'd have thought someone who had "bought into ISO standards, big time" would have had a tick box labelled "Conduct Risk Assessment". Of course everyone knows the words printed against tick boxes have no meaning, they're just to decorate the page before you add the ticks (and why don't they print the pages pre-ticked?).
Even so, it sounds more like a case of OCD than real adherence to standards.
I'm old enough to remember when Japanese products were cheap junk, were continually derided as cheep junk when in fact they no longer were and eventually their producers walked all over local businesses because they improved design and quality.
I think this mistake is being repeated with China. There's certainly a lot of junk but a couple of gadgets I've bought recently seem to show good build quality and attention to detail in the BoM such as a lens cloth included with a document camera and a dual charging cable with a radio mic. Those things don't happen without somebody thinking of them and while a few years ago nobody might have given that level of thought it is starting to happen now.
"A couple of takeovers ago the company at the time openly stated the reason they did not offer market leading salaries was because people should stay employed for a couple of years, gain experience, and then move on."
Which is an open admission, of which their customers should take note, that they only employ inexperienced people and those too incompetent to move on.
"Linux doesn't really have any standard interface, and while the various Distro makers may have their own UIs and guidelines, the fact the user can just replace the UI negates the whole idea of UI guidliness.."
It's true that Linux offers the opportunity to experiment and one way to do that with UIs is to produce a distro to feature it. It's also true that Ubuntu had a similar rush of blood to the head as did Microsoft, producing Ubity and W8 respectively. Ubuntu users were lucky - they just had to switch to whatever they'd used previously.
If you look more closely at the Linux GUI desktop world the most popular have followed CUA principles. Special mention goes to the founders of Mate and Cinnamon, both of whom took on the task of perpetuating the Gnome 2 look and feel when the Gnome developers started going rogue. The ability to switch desktops means that it becomes possible for users to main consistency through time where as Windows, with its imposed this-year's-standard approach, drags users along with it however unwilling.
"There was FVWM which was vaguely like Windows 3.x, FVWM95 which was a shameless Windows95 ripoff, IceWM"
A quick check on Devuan. "Was" is only the correct tense for FVWM95.
"On the other hand, this tends to stifle innovation and is why we're still using the same basic desktop metaphor almost a half-century later."
If it ain't broke... In fact there has been innovation that doesn't break and innovation which does. The former just fits in more or less unnoticed* because it seems natural, the latter gets complains.
* Unnoticed because people don't notice it wasn't there before.
Also a > will indicate another level of menu.
Kate (KDE Atdvanced Text Editor) manages both an ellipsis and an arrow for Save with encoding - the arrow indicates a further menu for the choice of encodings and the ellipsis the save dialog which will follow once you've chosen the encoding. Not that I've ever had a need to use that option.
"Most programs that deal with multi-line text have some way of inserting a line break which is not an end of paragraph. Usually it's either Ctrl+Enter or Shift+Enter. In Outlook, one of those two will just send the message, ready or not."
My first reaction to that is that in plain text the notion of a non-breaking new line is nonsense so why would you need a key combination for it?
But wait, this is Outlook, the home of top-posting HTML, get as far as way from standards as possible without actually breaking email so - yes, you're right. It is odd.
"That is how Locoscript on the Amstrad PCW handled insertion as well. It's a lot lighter on CPU than trying to move all the existing text after the insertion point up, and rewrapping, character by character."
Ah, we agree on something - on the rest we agree to differ. I never used Locoscript but it sounds as if they had the right idea.
My own trajectory was punched cards to Z-80 basically as an instrument controller to IBM-compatible as a Z-80 replacement. Overlapping that was VT100/220 talking to Unix boxes or PCs running Kermit as terminal emulation. Windows initially came along as a vehicle for running multiple terminal emulations to Unix boxes. IBM only entered that world through its Unix offerings - and without CUA.
I think that oversimplifies the history. OTOH W95 took a lot from HP's overlay for Windows 3 (memory says it was called New Era but I may be confusing it with something else). The early W95 and beyond included a copyright declaration for HP. New Era (or whatever) had a huge number of tiny files with character salad names defining odd bits and pieces which, I think, became the foundation of the registry when gathered into one place. It also have a better text editor than W3.