|
Well, we're certainly not disagreeing.
I just felt you were making a very broad, blanket statement.
Amongst those you've mentioned, I've tinkered with RHEL and CentOS, but always with a GUI. I'm not so hardcore yet as to live off of the terminal window by itself. 
|
|
|
|
|
I don't know where you got that subject line from, but...
Linux is a Unix clone; its architecture is a carbon copy of Unix. And Unix was never planned, designed.
The *nix process concept was a created as a mechanism to let the space ships of the Space Invasion game to come increasingly closer while you were scratching your head. The shell is the Space Invasion command interpreter loop. They needed a language for programming the whole thing, and threw up a number of language constructs in a messy pile - C is the most explisitly non-designed language that I have ever come across. And it shows!
I would be curious to know where this "though-out" is found. Most of the thinking has been spent on "How shall we clean up this terrible mess?" To some degree, the question has been evaded by stating "That is not our problem" (e.g. higher level protocols, file system structures, synchronization, shared data, user identification) - keep it simple; if it simpler than necessary, claim that it improves clarity! Slowly, a few mechanisms crept in: Existence of a file was replaced by a binary semaphore (so that we didn't have to worry about concepts such as critical regions and monitors...), we got .so libraries, and if you were an expert, you could set up segments of the data segment as shared.
X.11 could be patched on top to give the illusion of event-driven system design - but worked only for the mouse and keyboard. Exception handling was kludged onto the C language, and so was OO. For threads we had several years with competing kludges.
I never saw a speck of "design" work behind the *nix operating system, and very little in the activities closely related to it (such as the C language and communication protocols). For some protocols, the IETF simply had to make major cleanups, e.g. in the SMTP protocol and a number of others, and it is clear for everybody to see that all the old critisisms of "non-*nix-style" starndardization work becomes increasingly appliccable to *nix and TCP/IP protocols standardization.
|
|
|
|
|
I don't know where you're coming from (especially when you're only known here as "member 7989122"), but I think a conversation between yourself and Linus Torvalds would be fascinating.
I'm not being facetious.
|
|
|
|
|
If he pays a visit to Kargasniemi or Karesuvanto, I'll probably be passing both towns during my vacation this summer. But I guess that if he is back in his homeland then, he will probably stay much further south in the country. I have never visited the south of Finland - I would like to spend a vacation there, but I guess I'd prefer it to be a vacation. Not for discussing OS design (and lack thereof).
I guess my need for fierce turf wars is fully satisified during my working day. If I should happen to meet one of the big gurus by accident, I would probably do as I use to when meeting people with strong opinions and egos: Act a lot less experienced than I am, but rather poke him with some far more thought out questions that they initially appear, to have him reveal more of his real thoughts and approaches to things, when he doesn't feel that he has to "defend" things, but rather "explain". You reveal a lot more when you explain. And the listener, me, can place "naive" questions at the right time to dig far deeper than what comes out of a turf war.
Sidetracking: One of my friends, on his way to becoming a top rate DBMS expert in the 1980s, had the database guru Jim Gray as his idol. At VLDB conferences, he was chasing Grey, hoping to one day get so close that he could say that he had been touching Jim Gray's coat 
Then, one day at a VLDB conference, he saw Jim Gray coming right at him, cheering: "Hi, I hear that you guys are from Norway, is that right? Getting drunk with Norwegains is always great fun! Would you like to come along for a drinking night?" ... My friend went along, and the two became friends for live: When my friend married, Gray crossed the Atlantic to be his best man. I don't know if they ever were discussing database systems. Most likely they did, but that is not what formed a close friendship.
|
|
|
|
|
I'm not even sure your base premise is correct, since Windows was developed as a single user system and Linux a multi user system.
As for your observation about Linux shutdown, running sudo is the correct thing to do. Linux was derived from a multi-user environment and allowing any random user to shutdown the OS is not a good thing to do. The reason the console GUI shutdown works without sudo is because there is an underlying assumption that if you're using the console GUI then you're running in single user mode. I suspect the remote X-Windows GUI will require sudo to operate, just like Windows "hiding" the shutdown option when using RDP to connect to a remote system.
|
|
|
|
|
obermd wrote: running sudo is the correct thing to do. Linux was derived from a multi-user environment and allowing any random user to shutdown the OS is not a good thing to do
I agree entirely. I was just pointing out the inconsistency.
obermd wrote: The reason the console GUI shutdown works without sudo is because there is an underlying assumption that if you're using the console GUI then you're running in single user mode
That's probably the best response I've seen yet this thread. I wouldn't suggest however this is a great assumption to make.
obermd wrote: I suspect the remote X-Windows GUI will require sudo to operate,
Maybe it does, I haven't tried. I suspect you're right.
obermd wrote: just like Windows "hiding" the shutdown option when using RDP to connect to a remote system.
It's inconsistent for sure (across the multiple versions of Windows, and workstation- vs server versions), and I know I've seen policies to display/remove the option. But now that you bring this up, when you do have the option, Windows does warn you if you're about to do a shutdown and it knows other users are currently logged in. Given that's the case, I have to wonder why a UI-initiated shutdown request wouldn't do the same on Linux. It could be based on the assumption you put forth, but then, doing the check and putting up a warning as Windows does seems like a no-brainer to me.
All this to say...none of this is a "flaw" and I'm sure it's a deliberate design decision. And it'd be interesting to read the arguments that have been made on either side.
|
|
|
|
|
dandy72 wrote: I was just pointing out the inconsistency.
I think it's more accurate to call it a "security comprimise", because it's specifically intended to work that way. I don't see it as inconsistent.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Weird discussion in case of Win10. I use linux subsystem for linux within it. You can choose some linux distributions from windows store. I use, for example, firefox in linux on Win10 with success..
|
|
|
|
|
I'm glad you acknowledged that, I was about to, when to my surprise the last comment finally did.
I was also going to point out that there was an awful lot of discussion about other OSes when clearly the OP just wanted to complain about Windows. But then again, there's plenty of discussion here when someone just asks a question that can be answered "yes" or "no."
|
|
|
|
|
I'm not prejudiced -- they both suck!
Over the past few weeks I have been trying to sort out a Linux X-Windows problem. Too many versions, too many updates, too little adequate documentation, too many kids putting out messages on forums, too little design thoughtfulness, too many cryptic names ... I could go on for days.
Prior to that, I was trying to sort out a Window's UEFI dual boot problem. Same for Windows...and add too many internal functions that I don't need...or want, too many hidden telemetry functions that I don't trust, too many legacy functions that really should have been updated, too much being forced to do things MS's way....and on, and on, and on.
I want a clean, simple, understandable, capable, stable system that, in Apple's words, "just works". (I am not a fan of Apple either, but that's another story.)
I find too much of my time is spent nowadays sorting out interaction problems and managing updates. And I'm not getting done what I want to get done.
Not, back to figuring out why my abacus gave me a different answer than my slide rule.
|
|
|
|
|
I understand exactly what you're saying.
The problem is, we need someone to hit the Reset button and start with a whole new OS.
The problem with that is that it'd be expected to be compatible with everything else that already exists, else it's a non-starter. There's just so much baggage to worry about, such a project IMO would never get off the ground. So what do we do?
|
|
|
|
|
I've been doing some sideline research on what it would take to hit the Reset button (I like the way you phrased that!).
I wonder if that's what Google, Apple, etc., did when they came out with things like Android. OS'es don't have to be as complex as Windows or as convoluted as Linux.
Both have good features but carry so much legacy garbage that they become virtually unusable. Both are based on 1970's technology and little has been done to start from scratch, probably because nobody has the deep pockets or the will power to do it.
Things that might be done differently, IMO, include a programming language that is less error prone and more readable than current languages like C++ and javascript; consistent, clear naming conventions for utilities like using "copy" instead of "cp", less emphasis on "themes", better version and dependency usage, less hardware variation thus avoiding driver issues...just to name a few.
Scrapping compatibility goes a long way towards solving a lot of the legacy issues. Scrapping the idea of "being all things to all people" takes it even further.
Then, getting management out the picture would help as well. (I can't tell you how many times I've heard a manager say something like "We need to do....because _____ (fill in his favorite competitor) is doing it."
Or, maybe Artificial Intelligence will bring some real intelligence to the issue.
Just my thoughts.
|
|
|
|
|
rjmoses wrote: Scrapping compatibility goes a long way towards solving a lot of the legacy issues. Scrapping the idea of "being all things to all people" takes it even further.
When I read this I immediately thought "tablets".
They had a good run, companies made billions from them, but every market analyst is now saying sales have flatlined, if not declined altogether, for the past few years and there's no sign of that ever reversing course. Already.
They do a good job of "not being all things to all people", and for a lot of them this is all they need. But it's clear right now they're never going to be a complete replacement for what came before (and I'm not sure honestly if that was ever anyone's stated goal), and because of that, instead of simplifying things, they now add to the ecosystem complexity. I don't see how we can achieve a "full reset". Maybe a giant, planet-wide EM pulse like they like to do in the movies.
|
|
|
|
|
The general thinking is that if you have access to the console running the UI, then you also have access the the power button.
If your machine is genuinely multiuser, then there should be some system configuration to prevent a user from shutting down the system remotely.
|
|
|
|
|
couple of weekends job replacing magnetic ballasts with electronic ones (some were in really bad shape).
anyway electrician had drawn the neutral and ground through each light (per breaker circuit) which is fine, well would have been fine as in some cases with nothing to tie the earth onto he just left the ground wires (loop-in, loop-out) dangling and not even connected to each other.
OK, in lights, it's sort-of ok to run them on 2 wires (L & N) - but if you're going to have the ground wire there it should be a valid - what's the point of providing that green/yellow wire connected to thin air? Why, well...
perhaps the same idiot, or an underling had LAZILY drawn the end of one of those light circuits down to a remote wall plug - already DEAD WRONG but without that ground connected literally deadly.
But of course it was wired a decade ago, too late to call that sparky out (sure blame long departed apprentices anyway even though he is responsible for ensuring wiring it to code).
People talk about programmers being reckless, well for mine a sparky's only got 3 wires - one of which can kill you, and yet they can be lazy/careless and stupid too.
Note: I'm no [trained] sparky but really this sh*t is so basic and yet the fully trained tradies still screw it up - once perhaps can claim as 'accidental', but repeated is pure stupidity and laziness.
not my first time, older warehouse I also re-wired some lighting (added some internal offices) back in Aus... half of the lighting circuits had L and N swapped sometimes more than once. (previous tennants wondered why the flouro's dimly glowed at night when switched off - I can forgive them for not knowing why as they were not electricians, but for sure not the idiot that did that wiring.)
Message Signature
(Click to edit ->)
|
|
|
|
|
Lopatir wrote: perhaps the same idiot, or an underling had LAZILY drawn the end of one of those light circuits down to a remote wall plug - already DEAD WRONG but without that ground connected literally deadly.
Q. What's carbonized, and hangs from the ceiling?
…
Seriously,  ?!
That sort of thing would never pass here in Israel. The electricity company inspects any new building before they will connect the power, and yes, I have known them to fail buildings.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Here in the US... Well, that about sums up all I needed to say about wiring "standards" over here. I just had to replace a light fitting after a water leak destroyed the old one and found the three wires ready for me; a black one, a white one and another black one. One of them was ground/earth, statistically a higher chance of it being a black wire... or that might be the death wire! I got a sparky friend of mine to come in with his magical instruments - he swore at it for a few minutes and then figured out which was which and bound the appropriate wires with appropriately coloured tape for future reference. I worry a lot about the rest of the house.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Forogar wrote: I worry a lot about the rest of the house.
My advice: As much as can be avoided best not look, ignorance is bliss.
(And have to wonder if those extremists that shut off the mains at night when they sleep are not so crazy after all?)
Message Signature
(Click to edit ->)
|
|
|
|
|
57. Me, I'm a little leprechaun (4)
|
|
|
|
|
Self?
Socialism is the Axe Body Spray of political ideologies: It never does what it claims to do, but people too young to know better keep buying it anyway. (Glenn Reynolds)
|
|
|
|
|
yup 
|
|
|
|
|
S-ELF
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
ya
|
|
|
|
|
So close!
Socialism is the Axe Body Spray of political ideologies: It never does what it claims to do, but people too young to know better keep buying it anyway. (Glenn Reynolds)
|
|
|
|
|
I got a M.2 SSD enclosure, then bought a crucial SSD(240G).
try to use it to do some projects in travel.
anyone has other use for this type portable memory?
diligent hands rule....
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
