illumos-gate
time
illumos-gate | time | |
---|---|---|
30 | 12 | |
1,533 | 1,015 | |
0.7% | 2.4% | |
9.6 | 8.7 | |
2 days ago | 14 days ago | |
C | Rust | |
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
illumos-gate
-
eBPF Documentary
It may become a footnote on Linux, but Linux isn't the only system out there -- and DTrace remains alive and well in many systems (not least in its reference implementation in illumos[0]).
[0] https://github.com/illumos/illumos-gate
-
Oxide Computer releases distribution of illumos intended to power the Oxide Rack
Nobody's paid to have it pass Open Group Unix Branding certification tests
https://www.opengroup.org/openbrand/register/
so it can't use the UNIX™ trade mark.
But it's got the AT&T Unix kernel & userland sources contained in it.
PDP-11 Unix System III: https://www.tuhs.org/cgi-bin/utree.pl?file=SysIII/usr/src/ut...
IllumOS: https://github.com/illumos/illumos-gate/blob/b8169dedfa435c0...
-
In OpenZFS and Btrfs, everyone was just guessing
> it seems like this bug might actually date back to the very beginning of ZFS with Sun
Looks like you might be right about that. The oldest commit referenced in the fix [0] was from 2006[1], which was just months after Sun released ZFS.
[0] https://github.com/openzfs/zfs/pull/15571
[1] https://github.com/illumos/illumos-gate/commit/c543ec060d
- Getaddrinfo() on glibc calls getenv(), oh boy
-
Grokking AVL and RAVL Trees
It could be good for in memory stores / log-structured merged trees / other data store applications although it isn't used much now-days. I find them simpler to implement and understand than red-black trees -- although that's a matter of taste I suppose. They beat red-black trees in read-heavy loads (i.e. writes / updates are more costly for AVL trees than for Red-Black trees although they beat R-B trees for read-heavy loads). You can find another implementation in Illumos (an open source Unix operating system) available here: https://github.com/illumos/illumos-gate/blob/master/usr/src/...
- Classic Unix Code Available as FLOSS (Free/Libre/Open Source Software)
-
OpenIndiana
It's high time that the Illumos developers patched https://github.com/illumos/illumos-gate/blob/master/usr/src/... and https://github.com/illumos/illumos-gate/blob/master/usr/src/... to just set the error flag and return, and made the #ifndef TIOCSTI path in https://github.com/illumos/illumos-gate/blob/master/usr/src/... the only path.
Because by the looks of https://github.com/illumos/illumos-gate/blob/7c478bd95313f5f... the C shell was fixed years ago.
-
Can SGI’s Enthusiast Community Bring IRIX Back to Life?
People are still actively working on Illumos. The last change was yesterday morning.
* https://illumos.org
People are still actively working on MirBSD. There's a CVS commit account that can be followed on the FediVerse.
* http://www.mirbsd.org
It's DragonFly BSD, not Dragon BSD, and the irony of that is that you missed FreeBSD, which is of course still going.
* https://dragonflybsd.org
* https://freebsd.org
As is GhostBSD, which tracks FreeBSD.
* https://ghostbsd.org
HardenedBSD is still going. Shawn Webb regularly talks about it on the FediVerse.
* https://hardenedbsd.org
-
Linux distributions' relative popularity over time (by Distrowatch hits)
Its successor is still out there: Illumos. Though it seems to be mainly focused on backwards compatibility for existing custom applications as it still enforces things like an 8 character username limit.
-
Use a BSD style license for your Open Source Project (2021)
> Since then, illumos has rewritten all those components
But apparently kept the same license?
>> Most of the existing code is licensed under the CDDL and we expect new code will generally be under this license as well.[0]
[0] https://github.com/illumos/illumos-gate
time
-
Rust: Actix-web and Daily Logging
// To load RUST_LOG from .env file. dotenv().ok(); /* On Ubuntu 22.10, calling UtcOffset's offset methods causes IndeterminateOffset error!! See also https://github.com/time-rs/time/pull/297 ... */ // TO_DO: 11 is the current number of hours the Australian Eastern Standard Time (AEST) // is ahead of UTC. This value need to be worked out dynamically -- if it is at all // possible on Linux!! // let guard = init_app_logger(UtcOffset::from_hms(11, 0, 0).unwrap());
-
Getaddrinfo() on glibc calls getenv(), oh boy
The problem is that this effects higher languages too, because they often build on libc. And on some OSes, they don't have a choice, because the system call interface is unstable and/or undocumented).
For example in rust, multiple time libraries were found to be unsound if `std::env::set_env` was ever called from a multi-threaded program. See:
https://github.com/time-rs/time/issues/293 and https://github.com/chronotope/chrono/issues/499
https://github.com/rust-lang/rust/issues/27970
https://github.com/rust-lang/rust/issues/90308
- The time crate has officially adopted an N-2 MSRV policy for end-user improvements and an N-4 MSRV policy for internal improvements.
-
Simple, fast and safety alternative for unzip
On that note, it would also be good to configure cargo-deny so that a CI pipeline and any maintainer can easily audit the current dependency versions. Sometimes CVEs require a new major semver (looking at you, time 0.1.x and thus chrono 0.4.x), so it's not enough to rely on people installing the tool with semver-compatible updates. Automatically auditing dependencies is really important, and given how easy cargo-deny makes it, I don't think many projects have any excuse not to configure it.
- time: MSRV policy is changing beginning 2023-07-01 to N-2 rustc versions
-
Hifitime 3.5.0: time.rs and chrono alternative, only more precise, formally verified, and used in scientific and engineering programs
I've come to understand that correct support for leap seconds for time computations cannot be implemented in a reliable and globally consistent manner. Here is a GitHub discussion that touches on this.
-
What's new in SeaORM 0.9.0
Upgrade time to 0.3
-
What lightweight date/time library to use? [2022 edition]
I'm not fully aware of all the history but here's what I think happened: time 0.1 was originally a minimal wrapper around libc time functions, maintained by Alex Crichton. (I seem to remember it may have been part of the std library before 1.0, but I'm not sure about that part.) In August of 2016 it was declared to no longer be actively maintained, with the README stating bugs would still get fixed.
- What should we do about CVE-2020-26235 (localtime_r may be unsound)?
-
no_std with Error trait?
link to source code
What are some alternatives?
linux - Linux kernel source tree
chrono - Date and time library for Rust
linux - Kernel source tree for Raspberry Pi-provided kernel builds. Issues unrelated to the linux kernel should be posted on the community forum at https://forums.raspberrypi.com/
bitvec - A crate for managing memory bit by bit
orbiter - Open-source repository of Orbiter Space Flight Simulator
uuid - Generate and parse UUIDs.
awesome-space - 🛰️🚀A list of awesome space-related packages and resources maintained by The Orbital Index
bitsvec - A bit vector with the Rust standard library's portable SIMD API.
unix-v6 - UNIX 6th Edition Kernel Source Code
wyhash-rs - wyhash fast portable non-cryptographic hashing algorithm and random number generator in Rust
NeptuneOS - Neptune OS: A Windows NT personality for the seL4 microkernel
binfarce - Extremely minimal parser for ELF/PE/Mach-o/ar