Search Results for "source code"
Sort By:
Showing 3 open source projects for "source code"
View related business solutions-
Our Free Plans just got better! | Auth0You asked, we delivered! Auth0 is excited to expand our Free and Paid plans to include more options so you can focus on building, deploying, and scaling applications without having to worry about your security. Auth0 now, thank yourself later.
-
The Secure Workspace for Remote WorkVenn is a secure workspace for remote work that isolates and protects work from any personal use on the same computer. Work lives in a secure local enclave that is company controlled, where all data is encrypted and access is managed. Within the enclave – visually indicated by the Blue Border around these applications – business activity is walled off from anything that happens on the personal side. As a result, work and personal uses can now safely coexist on the same computer.
-
1
Kobo XCSoar Launcher
a customizable boot menu for your Kobo Mini
Mainly this project aims at easing startup and use of XCSoar (see xcsoar.org) on Kobo Mini. But the scope of use should not be limited solely to XCSoar. The Launcher should be small in code size, reuse most of the original libraries, provide flexible configuration to any application that might be ported to the Kobo Mini. It supports customizable fonts, toolbox-pages, buttons (also graphical), labels, autostart and sleep timers. -
2
Underdog -- Early and Late User Context
mkinitramfs & mkinitrd replacement and (eventually) alternate /init
Many complex storage environments running within GNL/Linux could benefit from increased disassembly and resource remediation during shutdown. Underdog an alternate /init to create a "late" user context to resume control during shutdown to park media and detach network devices. Currently there is a fully working initramfs (mkinitramfs/mkinitrd) replacement that is capable of building the early user context images both as separate files or built into the kernel image. The working proof... -
3
Tini
A tiny but valid `init` for containers
All Tini does is spawn a single child (Tini is meant to be run in a container), and wait for it to exit all the while reaping zombies and performing signal forwarding. It protects you from software that accidentally creates zombie processes, which can (over time!) starve your entire system for PIDs (and make it unusable). It ensures that the default signal handlers work for the software you run in your Docker image. For example, with Tini, SIGTERM properly terminates your process even if you...
- Previous
- You're on page 1
- Next
