No description
Find a file
2022-12-05 20:38:37 +01:00
.github/workflows Next version (#42) 2022-07-30 19:41:41 +02:00
extra Next version (#76) 2022-11-22 16:30:26 +01:00
src Add already running and root checks 2022-12-05 20:38:37 +01:00
.gitignore Initial commit 2021-12-28 19:43:20 +01:00
Cargo.lock Remove the dependency on the hex crate (#100) 2022-11-22 22:35:51 +01:00
Cargo.toml Remove the dependency on the hex crate (#100) 2022-11-22 22:35:51 +01:00
cover.png Next version (#76) 2022-11-22 16:30:26 +01:00
install.sh Next version (#76) 2022-11-22 16:30:26 +01:00
LICENSE-APACHE Create LICENSE-APACHE 2021-12-31 16:07:03 +01:00
LICENSE-MIT Rename LICENSE-MIT.md to LICENSE-MIT 2021-12-31 16:07:16 +01:00
README.md Add platforms section in README 2022-12-02 19:26:14 +01:00

Lemurs 🐒

A TUI Display/Login Manager written in Rust

Cover image

Note: the project is installable and working, but there might still be some limitations.

A minimal TUI Display Manager/Login Manager written in Rust similar to Ly.

Goal

The goal of this project is to create a small, robust and yet customizable Login Manager which can serve as the front-end to your graphical GNU/Linux. Lemurs uses Linux PAM as its method of authentication.

Installation

There are two different ways to install Lemurs. Both require the rust toolchain to be installed. I.e. there is currently no precompiled option.

Arch Linux --- AUR

Lemurs can be installed from the AUR. This will build the package on your local machine. It will automatically pull in rustup, but you might have to set the default toolchain with rustup default stable.

paru -S lemurs-git # paru can be replaced by any other AUR helper

or

git clone https://aur.archlinux.org/lemurs-git.git
cd lemurs-git
makepkg -si

Compiling from source

The install.sh script can be used to compile and setup the display manager on your Unix machine. This will perform multiple steps:

  1. Build the project in release mode (requires Rust's cargo)
  2. Setup the /etc/lemurs folder which contains some of the configuration and necessary files such as your selection of window managers.
  3. Disables the previous Display Manager
  4. Copies over the systemd service and enables it.

Although you might first want to set up some window managers (see Usage), upon rebooting you should now see Lemurs.

Usage

After installation you can add your environments by creating runnable scripts.

For your Xorg put your xinitrc scripts in the /etc/lemurs/wms directory. For Wayland, put a script that starts your compositor in the /etc/lemurs/wayland directory. For both cases, the name of the runnable script file is the name that is shown in the environment switcher within lemurs. Multiple Xorg and Wayland environments can exist at the same time.

Example 1: BSPWM

For the bspwm window manager, you might add the script /etc/lemurs/wms/bspwm.

#! /bin/sh
sxhkd &
exec bspwm

Remember to make this script runnable. This is done with the chmod +x /etc/lemurs/wms/bspwm command.

Upon rebooting your new bspwm should show up within Lemurs.

Example 2: Sway

For the sway compositor and window manager, you might add the script /etc/lemurs/wayland/sway. Ensure that you have sway installed and added yourself to the seat group.

#! /bin/sh
exec sway

Remember to make this script runnable. This is done with the chmod +x /etc/lemurs/wayland/sway command.

Upon rebooting your new sway should show up within Lemurs.

Configuration

Many parts for the UI can be configured with the /etc/lemurs/config.toml file. This file contains all the options and explanations of their purpose. The flag --config <CONFIG FIlE> can be used to select another configuration file instead. An example configuration can be found in the extra folder in this repository.

Preview & Debugging

Lemurs logs a lot of information of it running to a logging file. This is located by default at /var/log/lemurs.log, but can be turned of by running with the --no-log flag.

If you want to test your configuration file you can also run lemurs --preview. This will run a preview instance of your configuration. This will automatically create a lemurs.log in the working directory.

File Structure

Below is overview of the source files in this project and a short description of each of them and their use. This can be used by people who want to contribute or want to tweak details for their own installation.

|- src: Rust Source Code
|  |- main.rs: CLI argument parsing & main logic
|  |- auth: Interaction with PAM modules
|  |- config.rs: Configuration file format and options
|  |- info_caching.rs: Reading and writing cached login information
|  |- post_login: All logic after authentication
|  |  |- env_variables.rs: General environment variables settings
|  |  |- x.rs: Logic concerning Xorg
|  |- ui: TUI code
|  |  |- mod.rs: UI calling logic, separated over 2 threads
|  |  |- input_field.rs: TUI input field used for username and password
|  |  |- power_menu.rs: Shutdown and Reboot options UI
|  |  |- status_message.rs: UI for error and information messages
|  |  |- switcher.rs: UI for environment switcher
|  |  |- chunks.rs: Division of the TUI screen
|- extra: Configuration and extra files needed
|  |- config.toml: The default configuration file
|  |- xsetup.sh: Script used to setup a Xorg session
|  |- lemurs.service: The systemd service used to start at boot

Platforms

Tested on

  • ArchLinux (Vanilla, ArcoLinux)
  • VoidLinux
  • Ubuntu (make sure to install libpam-dev)

License

The project is made available under the MIT and APACHE license. See the LICENSE-MIT and LICENSE-APACHE files, respectively, for more information.

Contributions

Please report any bugs and possible improvements as an issue within this repository. Pull requests are also welcome.