Why’re you wording this as if the act of using Linux is what’s addictive? Lol
Not necessary the operating system it self, but the things I do with Linux, like researching stuff, enganging in discussion's and playing games, are addictive for me
Researching what? Engaging what? What aspect of this has to do with Linux?
I do them with Linux, why is this so hard to understand?
how is it not addicting? lol
I've done three lines of AUR and injected some systemd today but I can quit anytime I want, I promise
Not a direct answer for you, but a different approach.
Psychologically the carrot is better than the stick, meaning you'll keep fighting the lock-out mechanism, eventually resenting it and removing it.
Having an alert to remind you that you wanted to stop will be more pursuasive. (I have a "go to bed" alarm with a gentle, gradually increasing volume on my phone)
What's even better is tying a habit you want (eating, going to bed, etc) into another habit which already exists, but obviously, I don't know you well enough to suggest anything specific, but perhaps something else happens near those times you want to stop and that'll help?
Psychologically the carrot is better than the stick, meaning you’ll keep fighting the lock-out mechanism, eventually resenting it and removing it.
The logout mechanism just needs to though me out of my way and take at least 5 minutes (better more) to circumvent, this will probably be enough for me to do the right thing.
Having an alert to remind you that you wanted to stop will be more pursuasive. (I have a “go to bed” alarm with a gentle, gradually increasing volume on my phone)
I tried this for many times, but ended up just dismising the alarms because my will is weak
Starting from version 50, Gnome (the desktop stack) has screen time block configurable in the settings.
Will it be possible to set multiply block times?
cron job that launches the lock screen at the specified time and unlocks it later?
My idea for this has always been a battery powered computer, where the battery gets charged by a pedal powered generator. So I can use the computer as much as I want, but I have to at least get some exercise to keep it running.
but I have to at least get some exercise to keep it running.
Fuck that's brilliant
cron job that launches the lock screen at the specified time and unlocks it later?
Is there a way to only allow changing it when entering a password (that is different from the user password)
Yes the cron job would run as root.
So I can't stop it or change it because it has a higher rank and a different password then my main user?
Usually the password is different, yes. If you're unfamiliar with Linux system administration you might ask for more specific help. Root is the administrative account that lets you add and delete user accounts, access all the system's files, and that sort of thing. Ultimately though, it's like the joke about how many psychiatrists it takes to change a light bulb (just one, but the light bulb has to want to change). If you want to break through your time limiting software, you will find a way to do so. So you have to be willing to go along with it.
I think if it will take longer then 5 minutes to circumvent it, then I will do the right thing
Pipe /dev/random to passwd for your user and put it in a chron job, then have another chron job that echos your original password back
This is the way i'd do it, no warning or i'd be tempted to go and change the job. Also test on a new temp user unless OP is chad level script writer.
That sounds like a great way to permanently lock yourself out.
It wouldn't permanently lock you out if it failed because you can boot into a live ISO to change your password back if it fails to change it back to your original password.
I haven't personally used it but I think that is what pam_time is for.
Is this the Github of it: https://github.com/linux-pam/linux-pam ?
Could I pam_time root or something that has a higher rank and a different password then my main user?
You can prevent root login entirely using sudo and no root password.
Of course you could then override your init to give you a root shell, which you could avoid by having a grub and bios password.
But you'd be able to reset the bios password if you have physical access anyway.
As I only use sudo to update my system, I could use a user that doesn't has sudo access and set up some a cron job to do updates once a day. And flatpak instalation and updating doesn't require sudo at all
looks right
Write a script that installs one random AUR package a day.
Then you’ll either never be able to leave, or distrust your system forever and want to spend less time on it.
It all depends on how "forced" you want to be.
Generally, in Linux, if you've installed it, you have the power to uninstall it. Once your lockout gets put in effect, you can boot from USB, mount the hard drive, modify the files necessary to bypass your lockout, then reboot and proceed as if your lockout didn't exist.
Given that perspective: wouldn't a nag reminder popping over your screen that you actually pay attention to be better than "locking your account" with locks so easily picked?
It all depends on how “forced” you want to be.
I would say: It should take at least 3 minutes (better more) to circumvent it.
Generally, in Linux, if you’ve installed it, you have the power to uninstall it. Once your lockout gets put in effect, you can boot from USB, mount the hard drive, modify the files necessary to bypass your lockout, then reboot and proceed as if your lockout didn’t exist.
This sounds like it would take me around 10 minutes, so its enough for me to stop and do what I should be doing instead.
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0