Re: Oh no
Everything since W2K has been grot.
40470 publicly visible posts • joined 16 Jun 2014
"The various flavours/desktops of Linux are fine as they are trying to make them look like Windows is not doing anyone any favours."
OK, they're not necessarily doing you any favours. OTOH what would be a favour for somebody attempting to move away from Windows? The UI will necessarily look like something but what? Some SciFi fan's homage to their favourite films which seems to ba a favourite basis for theming DEs? Or something that looks reassuringly familiar?
You're not the target market for this sort of distro. Neither am I. But that doesn't mean that it isn't what the users it's aimed at won't want.
Having said that, maybe a W10 look would have been better.
"I don't understand how allowing access to all admin tools via sudo and the users password is more secure than using a root account with a different password."
The theory is that if you have a big hairy server operated by several people with differing roles you can assign each one with the rights they require and you can also log who does what. To some extent the first was solved years ago by having some subsystems owned by a specific userid such lpadmin.
However, with a personal computer with a single user this is pointless. There is no subdivision of functions. With sudo we have a situation where one userid and password pair can do anything. The additional protection of a second password has been sacrificed for a non-existent gain.
It makes sense to use root and su rather than sudo..
At the very worst, if the user can't remember more than one password then set root and user to have the same password. What's the difference between a Ubuntu user being presented with a dialog box* to enter their own password and a Debian user being presented with a dialog box to enter the root password which happens to be the same as their own?
Answer - the last offers the option of improving security by changing the root password, the first doesn't.
Obviously my preference is separate root with its own password.
* This assumes that admin tasks are being performed by GUI apps run from the menu using pkexec or the like rather than CLI.
You don't login as root, you su to it. For a non-technical user the reality is that they won't use su or sudo explicitly - they'll pick something off the menu to do some specific maintenance operation such as run updates which will ask for a password. That will be their own password for sudo based systems and the root password for su. When that operation completes if su was being used the root session also ends.
It would need:
Data centres to be owned and managed by a franchisee company in the country or bloc to which services are to be provided.
Owners and managers should be citizens of the same.
The contract between the franchisee and Google (or Microsoft etc) should be subject to the law of the same and signed there.
The contract should stipulate that the franchisor should have no access to data hosted by the franchisee or to the franchisee's customers
The contract should stipulate that the franchisee is under no obligation to provide hosted data or information about its customers or to the franchisor
The contract should stipulate that the franchisor does not have any authority to instruct the franchisee from providing services until the end of the franchise term.
The contract should stipulate that the franchisee is under no obligation to stop providing services until the end of the contract.
The contract should stipulate that the franchisor does not have any authority to instruct the franchisee to withhold services from any person or business who wishes to purchase services
The contract should stipulate that the franchisee is under no obligation to instruct the franchisee to withhold services from any person or business who wishes to purchase services
And probably more besides. It should be an operation completely hands off by anyone subject to US law. Arm's length would not be good enough.
That 4% know something you don't. It Just Works.
Your echo chamber may tell you otherwise based on somebody repeating something they read online posted by someone who'd never tried it based on something they read online posted by... eventually somebody who'd seen somebody managing a server farm from the command line or possibly running s minimal set of utilities on a pre-v1.0 kernel in the '90s. Probably a few repeats of some of your own rants are in that sequence.
But those of us using it as a daily driver know it Just Works. That's as oppose to Only Just Works - don't confuse the two.
It Just Wordk. Remember that. It's why we use it.
Some years ago a local council grant enabled our local Civic Soc to produce a folded tourist information leaflet. UK readers will know the format - it's found in every hotel and tourist information office. The text is out of date but we have a PDF version of it. Okular tells me it was produced by InDesign. A PDF can be edited with LibreOffice Draw. The other 3 pages can be edited as a mixture of images and text boxes but the front page is just a single big image, including the text on it. At least that's how it appears in the PDF and in print. But open it with Draw and there's something else. A big black rectangle, the size of the finished folded leaflet blocking the copy. How it doesn't show in the PDF viewer or in print I don't know - PDF is a strange thing.
Easily removed but is leaving this debris behind this debris something commercial professional software line InDesign does? Or something commercial, professional InDesign users do?
Here's a thought. The Health Sec is taking direct control over from NHS England. How about he undertakes a survey of his new empire to see what he's actually got that works, is created in house, is totally under UK control, not US and doesn't involve forking out huge sums of money for anything other than the H/W to run it on.
"you reach a point where you can't refine the requirements any further until there is something for the userbase to start poking at"
This is where fast prototyping comes in. Working with an RDBMS (Informix) it was easy enough to throw together a table or two based on what I thought were the data needs for what was required and have it automatically generate a default screen based on that. The users could then try it to see if it represented what they'd been thinking about. It wouldn't be pretty or have any business logic behind it but it could be done and amended very quickly. When they were happy with it it could be something more and less than a final spec - a working sketch, in effect.
That is maybe something that an LLM could produce.
"I'm still trying to convince my kids to learn to code, because I think they'll have a decent and rewarding career for many years yet."
If they go into coding because their dad persuaded them rather than something different that they'd rather do then they may have a career in coding but it won't be decent and rewarding. We all think that what comes naturally to us is equally accessible to everyone. It isn't.
"The union are looking after the collective rights of their members (or ought to be)."
Tell that to Ryanair's flight attendants: https://www.bbc.co.uk/news/articles/cpqeelw04e9o
All too often it's not clear what "the Union" is; IME it acted as if it had a feudal relationship with its members who were expected to pay their rent and do what they were told in order to be weaponised in pursuance of somebody else's pay claim.
On the whole I'm in sympathy with artists' rights but AFAICS this is just the Union miffed at being cut out of their self-appointed role as middle man by direct negotiations between company and rights-holder. My limited experience of unions was that they weren't on my side in negotiations when they were supposed to be.
Have core services such as the RDBMS that drives the rest connected to the rest of the business only through their data ports and not at all to the outside world*. No SSH or whatever. No other functionality. Maintenance only through the system console or at most a very small, dedicated network. Inconvenient? Ask M&S, the Co-op and all the rest about inconvenience.
Have a business resilience plan. Run exercises to test it. And test your backup and restores.
By now the boards of every big retail and distribution company in the country should be making this their top priority but I wonder how many are.
* Yes, I know this is makes updates tricky. It was much easier in my system minding day when updates came on CDs at intervals of some months from the vendor. It would need a process to verify the updates and the media to convey them across the air gap.
I've never been very fussed about keyboards. Maybe that goes back to my old portable typewriter, bought for a tenner as soon as I got my first grant cheque at University. It was a beast with a heavy action - shift was at least 3rd finger to operate. I trusted my handwriting even less than my typing but any keyboard since has been an improvement. Nevertheless i served me well. Eventually I even had a typebar changed from some symbol I didn't use to one I needed - a tilde probably. Last time I saw it its wooden case had woodworm.
Upper management is a risk that can't be easily designed out. It's upper management that needs to be source of concern about security. Back at the turn of the century the internet was still this new-fangled thing for the decision makers so they distrusted it and were, in any case, security-minded. A generation on and they're quite blasé about the net and probably not particularly security-minded at all.
"So some of it needed to be internet connected."
But not necessarily that much. In the system I was dealing with the application could be made online but that site wouldn't have held the data. The problem here is that there's no separation of functions so gaining access by whatever - phishing for example - seems to allow the attacker to wander through the entire network.
Over two decades I was working on something of similar sensitivity. Everything was fenced off. Private network connections, security clearance for everyone working on it..Although the premises were used to handling secure stuff it had its own private local network etc.
Now let's just expose it to the internet because it's cheap and a whole lot less fuss.
I'd like to think heads will roll over it starting with whoever decided that an internet-accessible protal was a good idea but committees are great for spreading the blame and making it impossible to work out whose idea it was in the first place.