3 ms·

What a pity that lots of people seem to want to create (often small) enhancements to xv6 > https://github.com/mit-pdos/xv6-public/pulls https://github.com/mit-

What a pity that lots of people seem to want to create (often small) enhancements to xv6 > https://github.com/mit-pdos/xv6-public/pulls https://github.com/mit-pdos/xv6-public/pulls but the authors (probably because of lack of time and/or academic obligations) seem to ignore them.

beefhash 8y ago
I mean, it's basically licensed under MIT. If somebody really wants to do something with the OS, they can just go and fork it, then get everybody else to hack on that instead. Given upstream is dead, it shouldn't be too hard to gain traction. Some "basic" (actually very involved, but the modern-day PC is hell) requirement to get it to run on physical hardware past 2020[1] is UEFI support. USB keyboard support is probably also a hard requirement nowadays and would basically require a full USB stack. [1] https://arstechnica.com/gadgets/2017/11/intel-to-kill-off-the-last-vestiges-of-the-ancient-pc-bios-by-2020/ https://arstechnica.com/gadgets/2017/11/intel-to-kill-off-th...
justin66 8y ago
Rather than incorporate them into the software, small enhancements are the sort of thing the authors of the project would prefer to leave as exercises for students, I'm sure.
sigjuice 8y ago
If you read through the comments of the closed pull requests you will get some idea of the type of enhancements that the maintainers expect.
- wolfgke 8y ago
  Look at the open pull requests.
  - sigjuice 8y ago
    If I have read through the closed PRs, then obviously I have looked at the open PRs too: Makefile trivialities, homework solutions, and duplicates. Not a whole lot there.
    - wolfgke 8y ago
      Counterexamples: Optimization: https://github.com/mit-pdos/xv6-public/pull/24/files https://github.com/mit-pdos/xv6-public/pull/24/files Improvement in build system: https://github.com/mit-pdos/xv6-public/pull/33 https://github.com/mit-pdos/xv6-public/pull/33 Bugfix in build system: https://github.com/mit-pdos/xv6-public/pull/34/files https://github.com/mit-pdos/xv6-public/pull/34/files Making code more standard compliant (assigning a function pointer to a void pointer is undefined behavior): https://github.com/mit-pdos/xv6-public/pull/43 https://github.com/mit-pdos/xv6-public/pull/43 Enable building on FreeBSD: https://github.com/mit-pdos/xv6-public/pull/50 https://github.com/mit-pdos/xv6-public/pull/50 Bugfix: https://github.com/mit-pdos/xv6-public/pull/51/files https://github.com/mit-pdos/xv6-public/pull/51/files Improvement in console system: https://github.com/mit-pdos/xv6-public/pull/62/files https://github.com/mit-pdos/xv6-public/pull/62/files --- Also concerning your "homework solutions" argument: The fact that these PRs are not closed is also a strong point for my argument.

beefhash 8y ago

I mean, it's basically licensed under MIT. If somebody really wants to do something with the OS, they can just go and fork it, then get everybody else to hack on that instead. Given upstream is dead, it shouldn't be too hard to gain traction. Some "basic" (actually very involved, but the modern-day PC is hell) requirement to get it to run on physical hardware past 2020[1] is UEFI support. USB keyboard support is probably also a hard requirement nowadays and would basically require a full USB stack. [1] https://arstechnica.com/gadgets/2017/11/intel-to-kill-off-the-last-vestiges-of-the-ancient-pc-bios-by-2020/ https://arstechnica.com/gadgets/2017/11/intel-to-kill-off-th...

justin66 8y ago

Rather than incorporate them into the software, small enhancements are the sort of thing the authors of the project would prefer to leave as exercises for students, I'm sure.

sigjuice 8y ago

If you read through the comments of the closed pull requests you will get some idea of the type of enhancements that the maintainers expect.

wolfgke 8y ago
Look at the open pull requests.
- sigjuice 8y ago
  If I have read through the closed PRs, then obviously I have looked at the open PRs too: Makefile trivialities, homework solutions, and duplicates. Not a whole lot there.
  - wolfgke 8y ago
    Counterexamples: Optimization: https://github.com/mit-pdos/xv6-public/pull/24/files https://github.com/mit-pdos/xv6-public/pull/24/files Improvement in build system: https://github.com/mit-pdos/xv6-public/pull/33 https://github.com/mit-pdos/xv6-public/pull/33 Bugfix in build system: https://github.com/mit-pdos/xv6-public/pull/34/files https://github.com/mit-pdos/xv6-public/pull/34/files Making code more standard compliant (assigning a function pointer to a void pointer is undefined behavior): https://github.com/mit-pdos/xv6-public/pull/43 https://github.com/mit-pdos/xv6-public/pull/43 Enable building on FreeBSD: https://github.com/mit-pdos/xv6-public/pull/50 https://github.com/mit-pdos/xv6-public/pull/50 Bugfix: https://github.com/mit-pdos/xv6-public/pull/51/files https://github.com/mit-pdos/xv6-public/pull/51/files Improvement in console system: https://github.com/mit-pdos/xv6-public/pull/62/files https://github.com/mit-pdos/xv6-public/pull/62/files --- Also concerning your "homework solutions" argument: The fact that these PRs are not closed is also a strong point for my argument.