liblinux
trackball
liblinux | trackball | |
---|---|---|
16 | 104 | |
195 | 715 | |
- | - | |
0.0 | 1.8 | |
over 4 years ago | almost 2 years ago | |
Makefile | C++ | |
MIT License | - |
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.
liblinux
- Liblinux – architecture-independent access to Linux system calls
-
A standalone zero-dependency Lisp for Linux
> libc isn't really getting in the way here.
For the standard set of system calls, the libc is pretty great. For Linux-specific features, it could take years for glibc to gain support. Perhaps it's gotten better since then, perhaps it still takes years. I don't know.
Years ago I read about the tale of the getrandom system call and the quest to get glibc to support it:
https://lwn.net/Articles/711013/
A kernel hacker wrote in an email:
> maybe the kernel developers should support a libinux.a library that would allow us to bypass glibc when they are being non-helpful
That made a lot of sense to me. I took that concept and kind of ran with it. Started a liblinux project, essentially a libc with nothing but the thinnest possible system call wrappers. Researched quite a bit about glibc's attitude towards Linux to justify it:
https://github.com/matheusmoreira/liblinux#why
Eventually I discovered Linux was already doing the same thing with their own nolibc.h file which they were already using in their own tools. It was a single file back then, by now it's become a sprawling directory full of code:
https://github.com/torvalds/linux/tree/master/tools/include/...
Even asked Greg Kroah-Hartman on reddit about it once:
https://old.reddit.com/r/linux/comments/fx5e4v/im_greg_kroah...
Since the kernel was developing their own awesome headers, I decided to drop liblinux and start lone instead. :)
-
Nolibc: A minimal C-library replacement shipped with the kernel
It gives you access to 100% of Linux's system calls. It eliminates a lot of global state. It gets rid of a lot of legacy libc crap.
Years ago I wrote a fairly referenced rationale in my liblinux project:
https://github.com/matheusmoreira/liblinux/blob/master/READM...
-
Win32 Is the Only Stable ABI on Linux
> Now, do I think it would make total sense for syscall wrappers and NSS to be split into their own libs (or dbus interfaces maybe) with stable ABIs to enable other libc's, absolutely!
I worked on this a few years ago: liblinux.
https://github.com/matheusmoreira/liblinux
I'm not developing it anymore though because I found out the Linux kernel itself has a superior nolibc library:
https://github.com/torvalds/linux/tree/master/tools/include/...
It used to be a single header but it looks like they've recently organized it into a proper project!
I wonder if it will become some kind of official kernel library at some point. I asked Greg Kroah-Hartman about this and he mentioned there was once a klibc:
https://old.reddit.com/r/linux/comments/fx5e4v/im_greg_kroah...
> This is something the BSD's got absolutely right.
BSDs, every other operating system really, force us to use the bundled C libraries and the C ABI. I think Linux's approach is better. It has a language-agnostic system call binary interface: it's just a simple calling convention and the system call instruction.
The right place for system call support is the compiler. We should have system_call keywords that cause it to emit code in the aforementioned calling convention. With this single keyword, it's possible to do program literally anything on Linux. Wrappers for every specific system call should be part of every language's standard library with language-specific types and semantics.
-
Oasis: Small statically-linked Linux system
I'm not using this stuff professionally, it's just my own home lab's virtual machines with little services implemented as freestanding C programs. Not doing anything fancy right now, much of it was just to see if I could do it.
I've seen other people commenting here on HN saying they're using the same approach so it's defenitely not my invention.
I published some of my work in the form of a liblinux that I use to make system calls:
https://github.com/matheusmoreira/liblinux
I'm not developing it anymore though because I found out the kernel itself has a nolibc library:
https://github.com/torvalds/linux/tree/master/tools/include/...
It used to be a single header but it looks like they've organized it into a proper project.
-
A Tutorial on Portable Makefiles
That's awesome. I didn't know about rwildcard until now. Is it part of GMSL? I searched for rwildcard on gmsl.sourceforge.io but didn't find it.
I think my function is needlessly complicated compared to rwildcard. Here's my code:
https://github.com/matheusmoreira/liblinux/blob/modular-buil...
https://github.com/matheusmoreira/liblinux/blob/modular-buil...
The file? and directory? functions were inspired by GMSL.
I wrote a general recursion function. It takes a function to apply to lists and a function to compute whether an element is a base case.
The recursive file system traversal function applies a directory globbing function to the list of paths and has file? as base case.
The find function filters out any items not matching a given predicate function. It was my intention to provide predicates like C_file? and header_file? but I stopped developing that project before that happened.
I think rwildcard is probably simpler and more efficient!
- GitHub - matheusmoreira/liblinux: Linux system calls.
- liblinux: Architecture-independent access to Linux system calls
- Liblinux is a C library that provides architecture-independent access to Linux system calls.
trackball
-
Different Strokes for Different Folks
For an even more configurable mouse, check out the Ploopy mouse and trackballs: https://ploopy.co/
Fully open source, the mouse (that I own) uses QMK for its firmware. Which means I can use key binding layers rather than single buttons. In other words, one button acts like a shift button that modifies the action of the other buttons. So I have easy access to page up/down, mission control (what was exposé in macOS), paste plain (shift+option+cmd+v), etc etc. I don't have anything Emacs specific on the mouse, but my keyboard (Keychron Q10) has several macro keys that I have meta-x and ctrl-g bound to.
-
My G502 mouse lasted 2 years before dying sometime in 2022. Found a G602 from 2013 that’s nearing 10 years and still kicking ass. They TRULY don’t make them like they used to.
If you truly want a mouse built to last, look into a Ploopy (https://ploopy.co/). You can get trackball ones, or a classic style mouse. It's fully open source and uses 3D printed parts, so not only can you easily get it repaired, you can also modify it to your hearts content. Also possible to remap the buttons or even program the microcontroller with custom code to do specific tasks if you wish.
-
Wait what?... THEY MAKE MK MICE NOW?!?
I have no affiliation with https://ploopy.co, but as an enjoyer of their products, I'd urge you to take a look at their mouse & trackball if you want a proper custom mouse/trackball made for keyboard enthusiasts. 10/10 stuff.
- Fairphone announce modular headphones: Fairbuds XL
-
Recommendations for Trackball I haven't considered?
Check out the Ploopy options. https://ploopy.co/
-
Steam Deck + Framework modular handheld console idea
You might be interested in the very unfortunately named ploopy.
- We are dubbing it the "Macroball". Dank or jank?
-
How loud does a Ploopy trackball get?
Print this to be as loud as possible.
- Any alternative to the HUGE? (no thumb balls)
-
What are my alternatives to Atreus62
I haven’t gotten around to trying anything from fingerpunch yet (I think their faux fox series is probably their most popular) but I don’t imagine any of their cases meant for trackballs is all that hard to work with (and if you just want a trackball, Ploopy seems to be the go to)
What are some alternatives?
cosmopolitan - build-once run-anywhere c library
ploopy-classic - A trackball mouse. Mechanical files, PCBs, and firmware all included.
vscode-gitlens - Supercharge Git inside VS Code and unlock untapped knowledge within each repository — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via rich visualizations and powerful comparison commands, and so much more
mini-trackball - A small, open-source trackball, powered by QMK.
rustix - Safe Rust bindings to POSIX-ish APIs
trackpoint - How to integrate a trackpoint in a mechanical keyboard
libratbag - A DBus daemon to configure input devices, mainly high-end and gaming mice
dm_r_track
minibase - small static userspace tools for Linux
nano-trackball - A very small trackball-only mouse. Mechanical files, PCBs, and firmware all included.
linux - Linux kernel source tree