Only the mentally ill would fault you for that, no worries.milyges wrote://EDIT: Yes! It's another UNIX clone

Only the mentally ill would fault you for that, no worries.milyges wrote://EDIT: Yes! It's another UNIX clone
Stop being a UNIX hugger.Brynet-Inc wrote:Only the mentally ill would fault you for that, no worries.milyges wrote://EDIT: Yes! It's another UNIX clone
If Brynet-Inc and David Cutler came into contact, they would annihilate.Love4Boobies wrote:Stop being a UNIX hugger.Brynet-Inc wrote:Only the mentally ill would fault you for that, no worries.milyges wrote://EDIT: Yes! It's another UNIX cloneThere are plenty of reasons (some mentioned on the forum) why the UNIX world is so very far from being perfect. It was designed like 40 years ago, software and hardware evolved.
None of said reasons are valid enough to warrant further discussion, now leave me alone, another non-perfect UNIX clone is being created somewhere on Earth and I AM going to hug it.Love4Boobies wrote:Stop being a UNIX hugger.There are plenty of reasons (some mentioned on the forum) why the UNIX world is so very far from being perfect. It was designed like 40 years ago, software and hardware evolved.
Yeah well he's just fussy, there is no scheduler that everyone will be content with.. so we should make due with what time we have.Love4Boobies wrote:Well, Brendan made a good point against UNIX schedulers in this post. Priorities are very important in scheduling.
Best hate everything.. except those things that you like.. I find that less confusing.Love4Boobies wrote:But I'm not a UNIX hater, nor a Microsoft hugger; I'm agnostic. My OS will probably take over the world someday but untill then...
The idea of the nice command is to be "nice" to other users by giving their processes priority over yours. Nobody ever uses it.
Actually, Xinu's Not Unixpiranha wrote:Unix is just xinu spelled backwards. So if you don't like unix or systems designed like it, whats a better alternative?
For POSIX pthreads there's "scheduling policies" and "scheduling priorities". For Linux, the pthreads library has scheduling policies SCHED_FIFO, SCHED_RR and SCHED_OTHER. SCHED_FIFO and SCHED_RR are intended for real-time tasks and do have priorities, but the program must be running as "root" to use these scheduling policies. That only leaves SCHED_OTHER (which is the default, and the most appropriate for normal tasks including my utility). SCHED_OTHER doesn't have any priorities (the minimum priority is zero and the maximum priority is zero).Synon wrote:Brendan's problem may have arised from him trying to increase the priority of his threads. Everything starts at it's maximum priority (I don't know why, but -20 is highest and +19 is lowest). If you want a thread to have a higher priority than another, you have to decrease the priority of the thread that should have a lower priority.
+1Brynet-Inc wrote: another non-perfect UNIX clone is being created somewhere on Earth and I AM going to hug it.
The first cars were actually battery-powered... there's a lesson in there somewhere.JackScott wrote:The petrol (gasoline) powered car has lasted 100 years. Doesn't mean it's still a good idea.
And we're probably getting back to (hydrogen) batteries in a few years...Solar wrote:The first cars were actually battery-powered... there's a lesson in there somewhere.JackScott wrote:The petrol (gasoline) powered car has lasted 100 years. Doesn't mean it's still a good idea.
JackScott wrote:You may have meant that the UNIX OS because it's had more bugfixes than others. This is also false, since the code gets completely rewritten by some bored programmer every decade or so.
And? as long as that egine still revs up past 6000 RPM and my radio still plays "Don't stop me now" I could care lessJackScott wrote:The petrol (gasoline) powered car has lasted 100 years. Doesn't mean it's still a good idea.