POSIX is a standard of compliance having to do with API (and yes command line functions too as a part of that). Linux, UNIX, and yes Mac OSX are all POSIX compliant. This does not mean UNIX, Linux or Mac OSX are compatible with one another as they are all different beasts.

EDIT: this *does* however mean you can write a clever neat script that uses all POSIX compliant commands, and said script should be able to run on any POSIX OS.

Fraid, not. Linux is not POSIX compliant where Ptheads is concerned, and it causes lots of problems in writing portable software. For Linux to continue to be backwards compatible it creates a PID for each thread as it's old thread model did. POSIX specifies only one PID per program. Because of this Linux NICE values are also broken in the thread model.* IIRC there may be some other differences in timers and signals.

*Since you can use NICE in a script, that breaks scripts between Linux and POSIX.

---

If I were Martin I'd now ask you what it is that you can't do with Linux, then I'd suggest softwares to fill that gap (with GUI where possible)
;-)

Taxes. And Martin didn't have an answer.

Ah, I used to have that problem too. My only solution was a VM running inside Linux. Nowadays it's not an issue cause I do my taxes through my web browser, which is supported on either family of OS in my case.

There are a lot who go the VM way, but the load required to support a lot of those VM's isn't worth the headache of running that OS (as far too many have found out here, to their fruitless endeavors).

BTW, Martin is good at pointing out what he see's as Window's problems in such threads as these, but he's awfully lite on the ground when people are having actual problems with Linux, which makes a lot of us suspect his actual experience when these happen is very small (he seems to disappear very quickly then).

Cheers.

Nice to see that I'm not the only one to notice that.

BTW, Martin is good at pointing out what he see's as Window's problems in such threads as these, but he's awfully lite on the ground when people are having actual problems with Linux, which makes a lot of us suspect his actual experience when these happen is very small (he seems to disappear very quickly then).

Martin wrote:

My professional time comes at a cost and is charged.

For someone who espouses free, shall we say his hypocrisy is on display.

---

Free as in beer, not as in money. ;-)

Free to use, modify and share. Not necessarily free of labor or cost.

---

#resist

BTW, Martin is good at pointing out what he see's as Window's problems in such threads as these, but he's awfully lite on the ground when people are having actual problems with Linux, which makes a lot of us suspect his actual experience when these happen is very small (he seems to disappear very quickly then).

Martin wrote:

My professional time comes at a cost and is charged.

For someone who espouses free, shall we say his hypocrisy is on display.

You are free to choose your support for fossware, support it yourself, or pay others to provide support for you (that's part of the revenue for Apache, RedHat and a few others). The fossware itself is free to download as source code.

---

I think you'll find it's a bit more complicated than that ...

Getting here the wrong way as usual and next reading the OP, by Bob DeWoody.

https://en.wikipedia.org/wiki/Operating_system

Read this article and perhaps a bit of misunderstanding could be noted by means of some postings around in this thread.

If it was not for the fact that NVIDIA Force Experience is the application controlling my graphics solution and also Norton Security for the prevention and detection of any computer viruses,
such a thing would be fine.

Think of a server-based network monitor software as being rather simple in its use.

Such a thing does often do not offer not too much when it comes to possible ways of such monitoring, which leaves me to the possible guess that there could be other ways around.

Trust Peter Norton in the same way as you are supposed to trust Microsoft as well. They are in fact not the same business.

Those in charge of offering me a good protection could well be ahead of the thief or culprit perhaps being of a different opinion, but here again could be about both a precise meaning as well as a given intention.

Also the fact that a thief is supposed to steal for his living, while there could also be others who still chooses to sell their products and solutions.

Peter Norton sold his business to Symantec many years ago.

Sirius.

My point is not here that what most people probably know and it is the fact that both Symantec, by Peter Norton and Microsoft probably depend on each other for a given success.

I am not the one here who is supposed to be doing this, but at least the computer I am running on could still be "my" business.

First of all, trust a given software and next its vendor.

We all know that Bill Gates started up small, almost in the garage for a starter and eventually became the CEO of Microsoft, before probably stepping down a bit, or retiring a while ago.

I am not an expert on such titles, nor the sharing of responsibilities between people, but Peter Norton is supposed to be owning Symantec, despite originally coming from the Microsoft development team.

The fact is that as being a computer user, I will not have such a thing as computer viruses or worms infect my system and there choose to be running such software as Norton Security.

Make a given person perhaps a thief when he chooses to steal information, or perhaps hack into the computers of other people.

A virus by means of being a product of nature could be harmless at times, but also sometimes lethal as well.

Should note that during the boring time of daylight, I happened to watch a video broadcast by Fox News.

It ended up being a sequence of such clips, so here it became either the second or third.

But noticing during an interview that the subject, who happened to be a Republican Senator, chose to cut of a question from the presenter in the middle, or even at the start and therefore looked a bit ugly to me.

Personally, I am having the feeling that a sense of peace and satisfaction should rather be a common norm.

There were two major wars being fought against an enemy which perhaps could be about a given ideology, but most likely ended up being something else.

Next, both these wars became won.

Now, sit down and enjoy your Sunday evening, because such a thing should be the better one to make.

Unless so, we could be back at the question of whether or not the same thing is happening all over again and also this time for a just or given cause.

Now, sit down and enjoy your Sunday evening, because such a thing should be the better one to make.

Yes troll, no troll, 3 bags full troll.

POSIX is a standard of compliance having to do with API (and yes command line functions too as a part of that). Linux, UNIX, and yes Mac OSX are all POSIX compliant. This does not mean UNIX, Linux or Mac OSX are compatible with one another as they are all different beasts.

EDIT: this *does* however mean you can write a clever neat script that uses all POSIX compliant commands, and said script should be able to run on any POSIX OS.

Fraid, not. Linux is not POSIX compliant where Ptheads is concerned, and it causes lots of problems in writing portable software. For Linux to continue to be backwards compatible it creates a PID for each thread as it's old thread model did. POSIX specifies only one PID per program. Because of this Linux NICE values are also broken in the thread model.* IIRC there may be some other differences in timers and signals.

*Since you can use NICE in a script, that breaks scripts between Linux and POSIX.

Seems Linux implements a closer approximation to posix threads now:

http://man7.org/linux/man-pages/man7/pthreads.7.html

Threaded processes appear as a single process in ps, and pstree will list the threads, e.g.

$ ps -fu bobby | grep java
bobby    6196  4815  0 Feb21 ?        00:16:36 java

$ pstree 6196
java─┬─{gdbus}
     ├─{gmain}
     ├─73*[{java}]
     └─{threaded-ml}

---

I think you'll find it's a bit more complicated than that ...

As you see here, top displays each thread with a different PID. H for thread view and V for forest view.

top - 18:33:12 up 15 days, 19:52,  3 users,  load average: 5.02, 5.22, 5.25
Threads: 252 total,   6 running, 246 sleeping,   0 stopped,   0 zombie
%Cpu(s): 24.3 us,  0.6 sy, 68.6 ni,  6.5 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem:    947732 total,   871428 used,    76304 free,    78188 buffers
KiB Swap:   102396 total,    75360 used,    27036 free.   237640 cached Mem

  PID  PPID USER      PR  NI nTH    VIRT    RES    SHR   SWAP S %CPU %MEM     TIME+ P COMMAND                                                                                                                                                                                                                                                                            
  662     1 boinc     30  10   2   53636   8044   4308    736 S  0.3  0.8  91:26.98 2  `- boinc                                                                                                                                                                                                                                                                          
  678     1 boinc     30  10   2   53636   8044   4308    736 S  0.0  0.8   0:08.55 3      `- boinc                                                                                                                                                                                                                                                                      
10596   662 boinc     39  19   2   70208  67504   1692    264 R 60.0  7.1   1166:29 3      `- setiathome_8.02                                                                                                                                                                                                                                                            
10597   662 boinc     39  19   2   70208  67504   1692    264 S  0.0  7.1   0:45.70 1          `- setiathome_8.02                                                                                                                                                                                                                                                        
11807   662 boinc     39  19   2   70724  68052   1716      0 R 74.0  7.2   1004:32 0      `- setiathome_8.02                                                                                                                                                                                                                                                            
11808   662 boinc     39  19   2   70724  68052   1716      0 S  0.0  7.2   0:40.30 0          `- setiathome_8.02                                                                                                                                                                                                                                                        
17117   662 boinc     39  19   2  137884 137048   4140      0 R 64.3 14.5 290:43.41 3      `- einsteinbinary_                                                                                                                                                                                                                                                            
17118   662 boinc     39  19   2  137884 137048   4140      0 S  0.0 14.5   0:12.65 0          `- einsteinbinary_                                                                                                                                                                                                                                                        
18857   662 boinc     39  19   2  137884 136984   4076      0 R 77.6 14.5  54:49.68 0      `- einsteinbinary_                                                                                                                                                                                                                                                            
18858   662 boinc     39  19   2  137884 136984   4076      0 S  0.3 14.5   0:02.35 3          `- einsteinbinary_  

Not everything is POSIX compliant and depending on what you are doing it can be a real PITA!

---

As you see here, top displays each thread with a different PID. H for thread view and V for forest view.

[...]

Not everything is POSIX compliant and depending on what you are doing it can be a real PITA!

?

What PITA do you trip over?


Note also:

NPTL: The New Implementation of Threads for Linux

August 01, 2005

Introduced with Version 2.6 of the Linux kernel, the Native POSIX Thread Library brings full compliance to the POSIX Standard...

... NPTL brings full compliance to the POSIX Standard for all major features, and performance boosts varying from outstanding to orders of magnitude...



Other snippets to note:

"There are two thread values that get confused. pthread_self() will return the POSIX thread id; gettid() will return the OS thread id. The latter is linux specific and not guaranteed to be portable"

"Threads have tids (threadIds), and all threads run in the same process (pid). So, your threads should all have the same pid assuming they're created in the same process, but they'll have different tids.

pthread_self() gives tid, and getpid() gets the pid."


Or are you running a pre-2005 system?

Happy crunchin' in freedom!
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)