Re: A question on file flags after fork

2020-01-14 Thread Ronald F. Guilmette
In message <16937.1578995...@jinx.noi.kre.to>, Robert Elz wrote: >But you do need some experience reading standards... I would like to pause just longe enough to thank you all for the unambiguously patronizing and derogatory manner in which you have welcomed me into your community, all due

Re: A question on file flags after fork

2020-01-13 Thread Ronald F. Guilmette
In message , Danny Niu wrote: >Anyway, this mailing list should focus on **standard development**, >questions like this of yours should go to places like unix.stackexchange.com. I can only thank you for your kindness, grace, generosity, and understanding. I'm sure that these will all inspire

Re: A question on file flags after fork

2020-01-13 Thread Ronald F. Guilmette
In message <1676199645.11146898.1578981958...@mail.yahoo.com>, Shware Systems wrote: >Short answer, because both file descriptors reference the same file >description... OK. I see where I took a wrong turn now, however I must say that I cannot blame myself for having done so. The language

Re: A question on file flags after fork

2020-01-13 Thread Ronald F. Guilmette
In message , Danny Niu wrote: >To a process, a "file descriptor" is a pointer to the "open file description" >in >the kernel-administered memory space/range. The two are related, but have >different set of flags. Can you point to specific passages of the stadard, or draft standard, that