Explore projects

Scripts used when converting the source code from CVS to Git.

Scripts used during conversion from Subversion to Git.

Contributions made by Opera to the Xenofarm project. This repository is used for review of contributions by Opera before they are committed to the main Xenofarm repository.

An attempt to solve bug 1616 of the lyskom-server, storing the code using TopGit.

The main repo.

The scripts and data files used when converting Xenofarm from CVS to Git.

The main repository of the LysKOM client written in Emacs Lisp.

My fork of mcwm, containing bugfixes and personal configuration changes. See http://hack.org/mc/projects/mcwm/ for the original project.

My photo management system.

Compressing SOCKS5 proxy written in Pony

Nettle is a low-level cryptographic library that is designed to fit easily in more or less any context: In crypto toolkits for object-oriented languages (C++, Python, Pike, ...), in applications like LSH or GNUPG, or even in kernel space.

Repository for dynamic DNS for Lysator members to use for home servers.

Liboop is a low-level event loop management library for POSIX-based operating systems. It supports the development of modular, multiplexed applications which may respond to events from several sources. It replaces the “select() loop” and allows the registration of event handlers for file and network I/O, timers and signals. Since processes use these mechanisms for almost all external communication, liboop can be used as the basis for almost any application.

Initially developed by Dan Egnor, liboop is now maintained by Niels Möller and Per Cederqvist.

Hacked version of readosm library, from https://www.gaia-gis.it/fossil/readosm/index

Liboop is a low-level event loop management library for POSIX-based operating systems. It supports the development of modular, multiplexed applications which may respond to events from several sources. It replaces the “select() loop” and allows the registration of event handlers for file and network I/O, timers and signals. Since processes use these mechanisms for almost all external communication, liboop can be used as the basis for almost any application.

Initially developed by Dan Egnor, liboop is now maintained by Niels Möller and Per Cederqvist.

A historic program that was used to set up the proper permissions of the accesslog files at Lysator.

Private modifications, not yet merged into the main repo.