Re: Fw: Purpose of Port 0. (About Bug 1068)

Sorry, I wasn't quite clear what you mean by "What I suggest in Bug 1068 is intended to be along those lines", I might be able to use a bit of explanation. As in: what do you suggest we do and not do to the current texts of the standard, and why? I actually thought that port 0 was reserved

Fw: Purpose of Port 0. (About Bug 1068)

;ma...@isc.org> Sent: Monday, February 20, 2017 19:07 To: Danny Niu Cc: joel jaeggli; i...@ietf.org Subject: Re: Purpose of Port 0. In message <sg2pr06mb071061291c3dc252aa62fcb2c1...@sg2pr06mb0710.apcprd06.prod. outlook.com>, Danny Niu writes: > Questions: > Is "Berkerl

Re: I/O semantics of pipe and FIFO.

From: Danny Niu <danny...@hotmail.com> Sent: Saturday, March 4, 2017 22:43 To: Shware Systems Subject: Re: I/O semantics of pipe and FIFO. LSB deferred to SUSv4 on this, but I found Linux v4.09 manpage section 2 read mentioning it might return les

I/O semantics of pipe and FIFO.

Hi all. I couldn't remember where I saw it saying, that when reading from a pipe or a FIFO, the read syscall returns the content of at most one write call. It's a bit similar to the message-nondiscard semantics of dear old STREAM. Currently, I'm reading through the text to find out a bit

Re: I/O semantics of pipe and FIFO.

. From: Danny Niu <danny...@hotmail.com> Sent: Sunday, March 5, 2017 10:05 To: Stephane Chazelas Cc: Austin Group Mailing List Subject: Re: I/O semantics of pipe and FIFO. Just so you guys can reproduce what I was talking about, here's essentially what I did: #!/bin/sh cd ~ mkfifo

Re: [1003.1(2013)/Issue7+TC1 0001041]: Encourage implementations to include better integrity checksum, compression and decompression utilities if possible.

Is the reuse of existing specification names (compress, uncompress, zcat) mostly to avoid trademark infringements? From: Austin Group Bug Tracker Sent: Friday, August 4, 2017 00:30 To: austin-group-l@opengroup.org Subject:

Quick timey question.

Why is gettimeofday() deprecated? I felt it's a simpler interface.

Re: UTF-8 locale & POSIX text model

On 26 Nov 2017, at 3:53 AM, k...@keldix.com<mailto:k...@keldix.com> wrote: On Wed, Nov 22, 2017 at 05:43:51PM +, Stephane Chazelas wrote: 2017-11-22 16:27:15 +0100, Martijn Dekker: Op 22-11-17 om 16:02 schreef Geoff Clare: Danny Niu <danny...@hotmail.com<mailto:danny...@hotmail

UTF-8 locale & POSIX text model

Hi all, I've a few questions about textual data in POSIX systems. It was said that the goal of the POSIX standards is to ensure source code level portability of application programs. However, some lunatix system may swap the upper and lower case columns of the ASCII table, to make vertical

[History digging] What were the standardization criteria for multi-threading synchronization primitives?

Given the wide variaty of synchronization primitives available in the theoretical field, what was POSIX's criteria for standardization at the time for pthread and real-time option groups' interfaces? Are there examples of and rationales for synchronization primitives being excluded from

The Purpose and Meaning of IPPROTO_ Constants.

Hi all. Currently defined in the spec: 1. the IPPROTO_ constants are used as `level' parameter in (set|get)sockopt functions, and 2. only protocol-specific options for IPPROTO_IPV6. Currently in practice. 1. IPPROTO_ constants follow "Assigned Internet Protocol Numbers", see

Re: [1003.1(2016)/Issue7+TC2 0001106]: *rand48(): Should this use uint16_t instead of unsigned short?

I was going to add a note to disagree, but it's closed before I could make a move. POSIX is a prescriptive standard, which unlike LSB who's descriptive, and we can and should make changes that're meaningful. rand48 says clearly it's rand*48*, so it doesn't make sense it generates 54 bytes

Where can I find information on "binding to system-assigned port"

There’s quite a lot of change and I couldn’t catch up. The “My View” section in the bug reporter no longer shows old bugs. I’d like to know how had we resolved the “binding to system-assigned port” bug, If we had resolved it. Thanks.

How do I contact store owner for download errors?

I know this probably shouldn’t go onto the development mailing list, but I’d want to try nonetheless. I get this error when I try to re-download SUSv4 2018ed and Base Specs Issue7 2018ed. An error occurred while getting the requested content. Please contact the store owner. How should I

CMSG_LEN missing in ?

I was just reading APUE side-by-side with my local HTML copy of SUSv4. I was reading the part about sending file descriptors, and found CMSG_LEN mentioned in the book missing from the specification. Is this intentional or accidental?

What do letters for symlink options (-P -L -H) stand for?

I posted a question to unix.stackexchange.com, but answers I got so far aren't quite satisfactory, as they are hardly backed by references. I hope expertized folks on this mailing list may have a better answer for this question << EOF I've summarized a list of commands that accepts symbolic

Re: Are BSDs evidently more fault tolerant than (say) SysV and Linux?

were more specific about which varieties of "faults" you're thinking of, software related, hardware related, operator error? On Monday, November 25, 2019 Danny Niu wrote: Actually I've also asked this on Unix.StackExchange.com, but it gets closed for being too broad, and I can't think of

What is this out-of-scope thing called Record IO?

At the beginning of the spec, there listed several things that are out of the scope of the standard. One of which mentioned is the "Record I/O considerations". I searched it on Bing since my national firewall won't allow me to Google it, but little relevant turned up. What is it exactly?

Re: What do letters for symlink options (-P -L -H) stand for?

> On Nov 21, 2019, at 11:47 PM, Danny Niu wrote: > > I posted a question to unix.stackexchange.com, > but answers I got so far aren't quite satisfactory, as > they are hardly backed by references. > > I hope expertized folks on this mailing list may

Are BSDs evidently more fault tolerant than (say) SysV and Linux?

Actually I've also asked this on Unix.StackExchange.com, but it gets closed for being too broad, and I can't think of a way to make it specific. One of those fellows mentioned it's because the way BSD UFS filesystem implemented made it more fault tolerant. But I think there must be a more

Re: "Flow OF control" in general information for system interfaces volume.

Is there a bug tracking the progress of us obsoleting STREAMS? 在 2020-02-25 16:57，“Danny Niu” 写入: Quick question. What does this "flow OF control" mean? Is it supposed to be "flow control"? In system interfaces volume, section 2.6 STREAMS: > Hig

Re: "Flow OF control" in general information for system interfaces volume.

with regard to using poll(2) with sockets: < 写入: Is there a bug tracking the progress of us obsoleting STREAMS? 在 2020-02-25 16:57，“Danny Niu” 写入: Quick question. What does this "flow OF control" mean? Is it supposed to be "flow control"?

Extra note regarding bug 1102 which marked inet_addr obsolete.

The bug 1102 obsoletes inet_addr function. There's at least one other place having a reference to this function, namely getaddrinfo() function, says: If the specified address family is AF_INET or AF_UNSPEC, address strings using Internet standard dot notation as specified in inet_addr are

Re: [Online Pubs 0001326]: Superfluous punctuations

I see. Somehow, it got line-wrapped even though the window size is large enough to show them in 1 line. 发件人: shwaresyst 日期: 2020-02-24 12:27:52 收件人: "nore...@msnkbrown.net" , Austin Group Mailing List 主题: RE: [Online Pubs 0001326]: Superfluous punctuations 重发发件人: Austin Group Mailing List

"Flow OF control" in general information for system interfaces volume.

Quick question. What does this "flow OF control" mean? Is it supposed to be "flow control"? In system interfaces volume, section 2.6 STREAMS: > High-priority and priority messages are used to send > control and data information outside the normal >flow of control< I realize as we obsolete

Re: Extra note regarding bug 1102 which marked inet_addr obsolete.

Sorry, I missed the note containing the final accepted text. Please ignore this. 在 2020-02-24 13:18:07，“Danny Niu” 写入: The bug 1102 obsoletes inet_addr function. There's at least one other place having a reference to this function, namely getaddrinfo() function, says

Is there an atomic compare-swap function/routine in the standard?

As asked, is there an CMPXGCHG-like function in the standard? I tried looking for keywords such as cmp, comp, ch, but nothing turned up in the system interfaces list. The C language introduced atomic functions in C11 though.

Re: A question on file flags after fork

sted. Anyway, this mailing list should focus on **standard development**, questions like this of yours should go to places like unix.stackexchange.com. 在 2020-01-14 14:07:23，“Ronald F. Guilmette” 写入: In message , Danny Niu wrote: >To a process, a "file descriptor" is a

Re: A question on file flags after fork

Hi there Ron. I'm not a standard developer, I'm just an outsider who happens to have Interest in the Unix standardization activities. 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

Should POSIX/SUS advise against MSG_OOB in recognition of RFC 6093?

RFC 6093 "On the Implementation of the TCP Urgent Mechanism" surveys the then existing implementations of TCP "URG" flag and use and recommends that new applications to not use it. In POSIX, it is said that "Support for an out-of-band data transmission facility is protocol-specific"; and unlike

Did we specify what "directory search" is anywhere in the standard?

Did we specify what "directory search" permission is anywhere? The closest thing I saw seems to be "File Access Permissions" in Base Definitions volume General Concepts section, but it doesn't specify anything for searching a directory. Info are scattered across the System Interfaces volumes in

Why can't a single condvar be used with multiple mutexes?

Hi, all. I realize this is busy time for the group to work on the next version of the standard, and I hope I'm not being too disruptive. In pthread_cond_wait and pthread_cond_timedwait, it is unspecified when a single condition variable is used with more than one mutex. I suppose such

答复: How do I get the buffered bytes in a FILE *?

Rob, you can use the MSG_PEEK flag on recv(2) instead of relying on stdio FILE* handles. 发件人: Rob Landley via austin-group-l at The Open Group 日期: 星期二, 2022-04-12 05:59:31 收件人: Rich Felker 抄送: austin-group-l@opengroup.org 主题: Re: How do I get the buffered bytes in a FILE *? On 4/11/22 15:41,

Re: [1003.1(2013)/Issue7+TC1 0001068]: Binding to a system-assigned port.

I'm sincerely sorry for my mailer's (Microsoft Hotmail's) URL protector. I'll take note of that in the future.

Re: Minutes of the 21st July 2022 Teleconference

That sounds very good, but I have one thing on my mind Mr. Josey. How did we decide to resolve bug 1068 by accepting it as marked? Did we do some liaison work with IETF? Surveyed existing implementations? Or both, or anything else? > 2022-07-22 21:29:10，Andrew Josey via austin-group-l at The