1 Topic by Ribby (edited by Ribby 2025-02-12 00:07:55)

  • Ribby
  • Beginner
  • Offline
  • Registered: 2025-01-26
  • Posts: 15

Topic: slock (and custom patches)

slock is a lockscreen function that allows a command upon activation. This is a unique parameter, which is slock and a command, compared to the .desktop file, which provides a command query. Limitation is that slock is a DE only application, while .desktop could be either console/DE application. There are the shell/bash script, but it works consistently with current session in DE and utilizes another session in console.

That said, I want to talk about the possibilities of slock in its default settings.
For instance, my time update lacks automation due to the authentication requirement for superuser commands. What I need is a program that that help login for syncing the clock. slock is the perfect example.

A autostarted .desktop file with command:

slock ntpd -s

And then logout of DE or reboot.
Once you once into DE, the autostarted .desktop file with initiate slock as lockscreen and ready ntpd -s. Once you login slock, you should also login ntpd -s.
However, if you do make a mistake, there is the chance that ntpd -s will drop out of terminal session.
The workaround is to logout of DE or reboot again for another attempt.

---

According to online research, the slock config file is only found in the source code package. I have to edit the config file in order to customize the slock setup. That means I have to compile the edited source afterwards. Thing is I am not sure if the change would be libre. Then there are these patches, modules that may help change the slock source code package. Not sure if they are libre. I would need a libre inspector to check out these packages. I am sure that there is a way to build one's own package, but I have yet test the compilation. Will get around to it later.

Here is the slock source code, along with its config file.
https://tools.suckless.org/slock/

Here are the unverified patches, includes hacking guide link and a set of patch subdirectories.
https://tools.suckless.org/slock/patches/
https://suckless.org/hacking/
I am interested in colors, image, message, time.
PAM too, but I am not sure if there is a libre PAM fork, considering the small application size.

slock_color-message_backspace_PKGBUILD

2 Reply by throgh

  • throgh
  • throgh
  • Package Development and Community Coordinator
  • Offline
  • From: Planet Earth
  • Registered: 2017-12-28
  • Posts: 3,012

Re: slock (and custom patches)

There is no real config-file, Ribby. As said earlier in IRC already: All is within the source-code, so this is per definition no real configuration-file and all parameters are just hardcoded by the user compiling. So it is not possible to call this a "configuration" but a modification for the complete source-base.

And also to mention: There is no libre PAM implementation. It is free and permissive licensed, but not in the hands of the community and there is no real simplified alternative in that point.

There is LinuxPAM: https://github.com/linux-pam/linux-pam
(which we are not going to adapt and implement)

There is OpenPAM: https://en.wikipedia.org/wiki/OpenPAM
(which we are also not going to adapt and implement)

Both implementations have different perspectives: LinuxPAM is not compliant with other implementations and Linux-only. Hyperbola rejects Linux-only frameworks out of clear reasonings for HyperbolaBSD as our full own operating-system and Hyperbola GNU/Linux-libre is the step in this direction. OpenPAM states to focus on simplicity, but has different problems and issues. As also said earlier in IRC: More complexity, more issues.

So if you encourage people to patch slock you should encourage them also to learn: Building, adding patchsets, installations and managing software aside the package-manager ... or as said: Packaging. To guide here: https://wiki.hyperbola.info/doku.php?id … e_creation
And all the patches you have mentioned and included in the link are free and libre licensed. Again as already mentioned in IRC also: When a software-package is added here, we have checked its surroundings. If you want to look over and find possible licensing-issues, that's fine to report. But a patch as modification for a free, libre software-project is same way licensed and cannot be just released different without creating a complete new fork.

To be clear:

1. A software-project has a license, enumerated projects here are free and libre licensed. If there are freedom-issues, please leave a note and we find either together a solution or the package has to go.

2. Patches for a software-project under a free and libre license are the same way to be included under that license. Software and patch for the software do not have different licensing.

3. Everybody has a right to fork the software, adapt own patches direct in the fork and release a new project from it. To change the license is not possible when the previous licensing does not allow this. Either way every author of every part needs to be contacted then and asked if a change to comparable but different license is possible (example: Original-BSD towards Simplified-BSD). It is as said NOT possible to just fork a project and add another license without acknowledge all authors and find a solution with them together.

4. A fork is not just a "fork" generic: There is a "soft fork" depending nevertheless upstream and on upstream development. The "hard fork" is a fork done without relation to the project before. So the "hard fork" means that every connection is cut after doing and the further development is done without any relation upstream. Surely patches can be taken nevertheless from upstream, but the generic development is even possible to go in a complete different direction with a "hard fork".

I hope the explanations make it a bit more clear.

Human being in favor with clear principles and so also for freedom in soft- and hardware!

Certainly anyone who has the power to make you believe absurdities has the power to make you commit injustices: For a life of every being full with peace and kindness, including diversity and freedom. Capitalism is destroying our minds, the planet itself and the universe in the end!

3 Reply by Ribby

  • Ribby
  • Beginner
  • Offline
  • Registered: 2025-01-26
  • Posts: 15

Re: slock (and custom patches)

If libre PAM and its variants are not yet possible, I will send a request and look for alternative MFA methods.

Since you mentioned that slock and its patches are deemed libre, I will send a request for custom slock source code variants (I prefer one with as much patch configurations as possible). Then, I will send a request to build a custom slock package variant. This package could be a alternative slock installation option. Its name could be slock-customs or slock-patches.

slock_color-message_backspace_PKGBUILD

4 Reply by throgh

  • throgh
  • throgh
  • Package Development and Community Coordinator
  • Offline
  • From: Planet Earth
  • Registered: 2017-12-28
  • Posts: 3,012

Re: slock (and custom patches)

I have already done work on our slock-package including further options. And towards MFA-options: Again to underline that this is not really a good option forward. Please read again through the several points given.

Human being in favor with clear principles and so also for freedom in soft- and hardware!

Certainly anyone who has the power to make you believe absurdities has the power to make you commit injustices: For a life of every being full with peace and kindness, including diversity and freedom. Capitalism is destroying our minds, the planet itself and the universe in the end!

5 Reply by Ribby

  • Ribby
  • Beginner
  • Offline
  • Registered: 2025-01-26
  • Posts: 15

Re: slock (and custom patches)

If further options are included in the OS repository's slock package, I would like to know how to edit the slock installation config before the actually installation takes place. But if I can run slock with custom config, that would probably be better. slock documentation does not provide enough detail in terms of its capability.

e.g.
Pre-installation steps for slock patch configuration
# doas pacman --sync --verbose slock (some other options)
# slock --commands --args

slock_color-message_backspace_PKGBUILD

6 Reply by throgh

  • throgh
  • throgh
  • Package Development and Community Coordinator
  • Offline
  • From: Planet Earth
  • Registered: 2017-12-28
  • Posts: 3,012

Re: slock (and custom patches)

You cannot "edit" the slock-configuration as - to repeat: There is NO configuration!
The package slock is as it is compiled, including the patches. The configured parameters are compiled at build-time and can't be changed at run-time.

Please also make a difference: You are talking about several different points.

1. Commandline-parameters are optional added.
2. Configuration-parameters are defined and loaded, so there is no need for any commandline-addition.

Both parts are nevertheless not part of the program slock. I have added the following patches:

https://tools.suckless.org/slock/patches/dpms/
https://tools.suckless.org/slock/patche … ed-screen/

If you want different settings, you have two options:

1. Compiling the program on you own local. This has one important disadvantage: You have no further influence on later updates throughout the package-manager.
2. Rebuilding the package itself on your own: You can refer to the packaging-guide (https://wiki.hyperbola.info/doku.php?id … e_creation).

Both options demonstrate clearly that free, libre software is and stays a community-point. I write this as it seems many people think we are just providing them their wishes and demands, but this is far away from the reality. We do what we can providing our system-project following the principles and values we have defined. But we also rely on the community itself: You compile and test, you configure ... we can only work together. But we also need to stay clearly on the given facts and options a software is offering. And slock is neither offering commandline-options to activate or deactivate options in that matter nor it offers a configuration-file doing this. Yes, in theory it would be possible to rework the software and add all of this. But in reality we would then have a complete hard-fork of slock and as we do already as much as possible, we cannot do forks for every software-project at wish.

Thread now closed!

Human being in favor with clear principles and so also for freedom in soft- and hardware!

Certainly anyone who has the power to make you believe absurdities has the power to make you commit injustices: For a life of every being full with peace and kindness, including diversity and freedom. Capitalism is destroying our minds, the planet itself and the universe in the end!