kernel
util-linux
kernel | util-linux | |
---|---|---|
5 | 35 | |
725 | 2,492 | |
1.9% | 1.9% | |
8.6 | 9.9 | |
14 days ago | 1 day ago | |
C | C | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
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.
kernel
-
Even the simplest possible assembly program will/can have a console window. How exactly?
You might find the source code for FreeDOS of interest for learning more about how the low-level access to the interrupt services worked. Specifically, console.asm installs a character write routine (which calls BIOS INT 10h under the hood).
-
Trying to run FreeDOS off CF Card on 286 homebrew system --- Question about bootloader and drive geometry information
Looking at https://github.com/FDOS/kernel/blob/master/boot/boot.asm, I see %define statements for this type of information, but I'm not sure how these memory locations are normally populated with proper values. Is this something that Sys does when preparing the CF card? Or should the BIOS populate this information when loading the boot loader?
-
"My Reaction to Dr. Stroustrup’s Recent Memory Safety Comments"
That's where I'm coming from. FreeDOS still gets occasional commits once per few months but is not really developed anymore. Watcom C still seems like it's actively developed, but it's not clear what they are trying to achieve if they are not even interested in what's happening in C/C++ world!
-
How to Port to ARM (Just Curious, not ready to do it yet)
Here's the code for the kernel https://github.com/FDOS/kernel/ You will have to entirely rewrite the Assembly code since it is x86 assembly (Netwide Assembler is great, but not for ARM). Namely boot code is assembly. The kernel does compile under multiple compilers. I'm not too sure if ARM platforms handle this, but I would look at the Linux kernel for boot code on ARM.
-
Are DOS utilities open source.
"DOS" is a little bit of a general term. Microsoft's product, MS-DOS, is not Free Software. But there are other implementations, including FreeDOS, which is compatible with MS-DOS.
util-linux
-
The First Stable Release of a Rust-Rewrite Sudo Implementation
There are su and runuser in util-linux (GPL-2.0) [1].
[1]: https://github.com/util-linux/util-linux/tree/master/login-u...
-
Simula the Forgotten Programming Language
>It remained in the "getty" process for some time, well into the {Free,Net,Open}BSD era.
Still there in agetty: https://github.com/util-linux/util-linux/blob/master/term-ut... And, I imagine in other getty implementations.
-
Don't abuse su for dropping user privileges (2015)
TIOCSTI is irrelevant. When one is dropping privileges, in a system cron job or in a process supervised by one's favourite service management system, there is no terminal involved. TIOCSTI simply doesn't enter into the picture at all.
Only when one is in a terminal login session and using su to elevate / add privileges, does TIOCSTI become relevant. But no-one here is saying not to use su to add privileges.
People blame su, sudo, and (as the person at https://github.com/slicer69/doas/issues/110 did) doas for this feature of operating system kernels. The right thing to do with TIOCSTI it to just eliminate it from the kernel. OpenBSD did back in version 6.
Sadly, the argument from Alan Cox, Linux developer, when this was proposed years ago was that it should stay in Linux, and all of the programs like su, sudo, and doas should have even more things to do in the parent process that sticks around, namely pump I/O to and from a controlling pseudo-terminal that su/sudo/doas sets up for the shell subprocess, breaking (as the maintainer of OpenDoas pointed out) the long-standing notion that the child processes belong to the same terminal session and share things like a single getlogname() with the login shell.
6 years after https://www.openwall.com/lists/kernel-hardening/2017/05/10/3... and https://www.openwall.com/lists/oss-security/2017/06/03/9, there is no sign of anyone doing anything of the sort in any su or doas implementation. (It was briefly in one su implementation, but taken out in 2017 for being a "stupid hack": https://github.com/util-linux/util-linux/commit/23f75093264a...)
Fortunately, some six months ago Linux developers finally made TIOCSTI removable and the right course of action is available to those that want it: https://lore.kernel.org/lkml/20221228205726.rfevry7ud6gmttg5...
-
Desktop Suddenly Failing to Boot - what are these error messages?
Huh, I will try this later. Bit confused by the instructions on the Archwiki but I think I can figure it out. Thanks so much for the help. Btw, it seems you were right on what was wrong. Good eyes.
-
Capture your users attention with style
So, this script serves as a pretty good wall replacement (wall will strip all escape/control sequences other than \007, by the way).
-
How do you find the developers for obscure stuff
The login program (used for terminal logins) is part of the util-linux project: https://en.wikipedia.org/wiki/Util-linux
- hexdump nonsense error messages
-
Would you use/try snaps if it has open source backend?
if anbody actually at Canonical is reading this and wants me (and others) to take snaps seriously, please consider submitting pull requests to some of the core cli tool projects impacted by the way you guys abuse the loop device mechanism. Something simple like the ability to export HIDE_SNAP_MOUNTS=1 that gets picked up by the impacted tools in util-linux (lsblk, mount, blkid, fdisk, etc) and gnu coreutils (du, df) and simply hides the lines related to loop device mounts would go a long way - preferably only the ones added by snap but even an option to hide all of them would be better than nothing.
-
Best Way For Copying Between 2 PC's With Different UIDs via USB
Pick a different filesystem, or wait for this feature to land in util-linux.
-
Are DOS utilities open source.
Also a data format. Reasonably easy to find a spec (the wikipedia article should be sufficient to implement it). Also reasonably easy to find Free Software implementations, such as fdisk.
What are some alternatives?
fdpp - FreeDOS plus-plus, 64bit DOS
coreutils - upstream mirror
surface-aggregator-module - Linux ACPI and Platform Drivers for Surface Devices using the Surface Aggregator Module over Surface Serial Hub (Surface Book 2, Surface Pro 2017, Surface Laptop, and Newer)
bindfs - Mount a directory elsewhere with changed permissions.
cacule-cpu-scheduler - The CacULE CPU scheduler is based on interactivity score mechanism. The interactivity score is inspired by the ULE scheduler (FreeBSD scheduler).
gimp - Read-only mirror of https://gitlab.gnome.org/GNOME/gimp
rust - Empowering everyone to build reliable and efficient software.
sanitizers - AddressSanitizer, ThreadSanitizer, MemorySanitizer
static-assertions - Ensure correct assumptions about constants, types, and more in Rust
linuxgems - A succinct cheat sheet for newbie linux coders and system administrators, documenting some of the more obscure and useful gems of linux lore. Intended to be viewed in emacs org-mode, or VimOrganizer, though any text editor will suffice.
changie - Automated changelog tool for preparing releases with lots of customization options
subsync - Subtitle Speech Synchronizer