3 ms·

Just to prevent inevitable confusion, SystemV filesystem is different than SystemV init which you may be thinking of. SysV init isn't part of the kernel and whi

Just to prevent inevitable confusion, SystemV filesystem is different than SystemV init which you may be thinking of. SysV init isn't part of the kernel and while it's been replaced with systemd in many distributions, it's not impacted by this change.

twic 4y ago
The SysV name is also attached to a set of old and strange interprocess communication primitives: https://man7.org/linux/man-pages/man7/sysvipc.7.html https://man7.org/linux/man-pages/man7/sysvipc.7.html Unix has a bigger range of IPC mechanisms than i think most people realise. Everyone knows about internet sockets and pipes. Most people know about shared memory, named pipes, and unix domain stream sockets. But how many people know about unix domain datagram sockets, or POSIX message queues?
- xyzzyz 4y ago
  In a university class, we had an assignment that asked us to write a program that would communicate with its copies over POSIX message queues. I remember grepping through the source of all the software I had on my Gentoo installation, and couldn’t find a single one that had any sort of usage or support for POSIX message queues. Does anyone know of even a single app that uses them?
  - mmcgaha 4y ago
    I don't know of anything other than one I wrote back in the late 2000s that let me coordinate a web service with process pool of ERP instances. When I wrote it I remember thinking that ftok could have real issues on a large filesystem. I never ran into any problems so I sort of put the issue out of my mind.
  - RobotToaster 4y ago
    They tend to be used more in real time systems I think.
  - dfox 4y ago
    There are two things: SysV IPC and POSIX IPC, both of which have message queues. In the SysV case this feature probably made sense because it was designed at a time when BSD sockets were not yet the universaly accepted API. POSIX equivalent probably exists mostly for completeness. One might say that the whole of POSIX IPC is simply SysV IPC with sane and "unix-like" API (ie. names instead of "IPC keys"). One of the problems with POSIX IPC is that you cannot really use it if you want to be portable, because on BSD and derived systems the implementation is best described as also existing only for completeness.

twic 4y ago

The SysV name is also attached to a set of old and strange interprocess communication primitives: https://man7.org/linux/man-pages/man7/sysvipc.7.html https://man7.org/linux/man-pages/man7/sysvipc.7.html Unix has a bigger range of IPC mechanisms than i think most people realise. Everyone knows about internet sockets and pipes. Most people know about shared memory, named pipes, and unix domain stream sockets. But how many people know about unix domain datagram sockets, or POSIX message queues?

xyzzyz 4y ago
In a university class, we had an assignment that asked us to write a program that would communicate with its copies over POSIX message queues. I remember grepping through the source of all the software I had on my Gentoo installation, and couldn’t find a single one that had any sort of usage or support for POSIX message queues. Does anyone know of even a single app that uses them?
- mmcgaha 4y ago
  I don't know of anything other than one I wrote back in the late 2000s that let me coordinate a web service with process pool of ERP instances. When I wrote it I remember thinking that ftok could have real issues on a large filesystem. I never ran into any problems so I sort of put the issue out of my mind.
- RobotToaster 4y ago
  They tend to be used more in real time systems I think.
- dfox 4y ago
  There are two things: SysV IPC and POSIX IPC, both of which have message queues. In the SysV case this feature probably made sense because it was designed at a time when BSD sockets were not yet the universaly accepted API. POSIX equivalent probably exists mostly for completeness. One might say that the whole of POSIX IPC is simply SysV IPC with sane and "unix-like" API (ie. names instead of "IPC keys"). One of the problems with POSIX IPC is that you cannot really use it if you want to be portable, because on BSD and derived systems the implementation is best described as also existing only for completeness.