4lDO2

5 ms·

1. 1.▲
   by 4lDO2 2y ago

   Generally this aligns with what the Redox kernel is currently transitioning into, with a few limitations in order to retain compatibility for the (quite larger number) of applications we "need" to support. > My idea of operatin
2. 2.▲
   by 4lDO2 2y ago

   Yes, and yes.
3. 3.▲
   by 4lDO2 2y ago

   File descriptors and file descriptions are not the same thing. Descriptors are references to descriptions, along with some metadata, and multiple descriptors can point to the same description.
4. 4.▲
   by 4lDO2 2y ago

   Rust does however implement the IO traits for `&File` as well (shared), and IIRC also implements `try_clone` which is the dup equivalent.
5. 5.▲
   by 4lDO2 2y ago

   The rationale was discussed in-depth earlier on LWN ( https://lwn.net/Articles/982186/ ). Signals are useful as a software analogue to hardware interrupts, even though they are probably too low-level for most applic
6. 6.▲
   by 4lDO2 2y ago

   I'm aware of this example, this was discussed earlier on HN [1]. I think it would be reasonable to (try to) enforce O_APPEND in such scenarios, in which case libc might internally open a pipe (configured to passively or actively be flu
7. 7.▲
   by 4lDO2 2y ago

   Pipes lack a file cursor, but they still need to store the fcntl file description flags, so yes. This is emulated by the Redox kernel for old schemes, by inserting fcntl calls between the legacy read/write calls that don't allow p