Search
13 results for “antoniusmisfit”
-
So, I officially put up the initial sources for my "PDOS-goodies" project, which aims to be a collection of utilities aimed at addressing features gaps in #PDOS, the Public Domain Operating System. Here it is: https://github.com/antoniusmisfit/pdos-goodies
-
@antoniusmisfit @davidallengreen
I concur, a #federated platform in the long run should be more stable, better moderated, and not subject to the whims of owners who, like the press, may use their platform including powerful algorithms to push their own agenda.
Are there any weaknesses of #Mastodon , apart from resource limitations for some #instanceadmins ?
I've long advocated for #opensourcetechnology & put my money where my mouth is on these.
-
And don't think it'll be a cakewalk to get out of that lock-in. It took Devuan almost 3 years to release their first stable version. It's not simply a matter of init switching anymore. Logging, networking, time syncing, task scheduling, user management, multiseat management, desktop environment communications are being absorbed into systemd components that refuse to run unless systemd is PID 1.
-
NetHack 5.0.0 released a couple days ago, and I'm happy to report that it *still* supports MS-DOS(and #FreeDOS) quite nicely. https://www.nethack.org/v500/ports/download-msdos.html
-
Finally figured out how to enable basic job control(via Ctrl+D, Ctrl+C and Ctrl+Z) and reading /etc/profile in #Floppinux : run "sh -l -m".
This now enables me to try writing a crude but functional service manager for Floppinux in shell script.
-
I've got another #Floppinux #Linux puzzle to solve.
I'm thinking of writing a crude service manager in shell script, but Floppinux doesn't have the fg, bg, or kill commands. But you can run a command in the background by adding the "&" at the end, and you can set traps to run on receiving specific signals. Is there a way to kill a command without the kill command? Is there something within /proc/$pid/ I can poke at to very manually trigger process termination?
-
The SAVE command in #PDOS is the #DOS equivalent of *nix here-documents, but with two drawbacks:
1. It cannot "save" to stdout. A file MUST be specified.
2. While it can overwrite a file, there's no option to append to a file(yet).
Despite these drawbacks, SAVE enables batch files to create files. And outside of a batch file(or in a batch file with the /I switch), SAVE acts like the "COPY CON" command found in other DOS-based operating systems.
You can grab PDOS here: pdos.org
-
@doctorwhom @elfin I too did not know about #Springdale until the current ruckus with Red Hat. Going the LFS route does grant you 100% control of what goes into your distro, but then you gotta maintain it yourself. If you think you(or the university) can do that, then definitely go for it!
-
@doctorwhom @elfin I too did not know about #Springdale until the current ruckus with Red Hat. Going the LFS route does grant you 100% control of what goes into your distro, but then you gotta maintain it yourself. If you think you(or the university) can do that, then definitely go for it!
-
@doctorwhom @elfin I too did not know about #Springdale until the current ruckus with Red Hat. Going the LFS route does grant you 100% control of what goes into your distro, but then you gotta maintain it yourself. If you think you(or the university) can do that, then definitely go for it!
-
@doctorwhom @elfin I too did not know about #Springdale until the current ruckus with Red Hat. Going the LFS route does grant you 100% control of what goes into your distro, but then you gotta maintain it yourself. If you think you(or the university) can do that, then definitely go for it!
-
@doctorwhom @elfin I too did not know about #Springdale until the current ruckus with Red Hat. Going the LFS route does grant you 100% control of what goes into your distro, but then you gotta maintain it yourself. If you think you(or the university) can do that, then definitely go for it!