-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optimize Shutdown, Disable MOTD, Disable Cursor Blink #26
Open
dezren39
wants to merge
53
commits into
beeper:main
Choose a base branch
from
dezren39-dev:optimize
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dezren39
commented
Aug 27, 2023
i'd recc squashing, but i can cleanup my commits if needed |
dezren39
changed the title
Optimize Shutdown, MOTD, Remove Blinking Cursor
Optimize Shutdown, Disable MOTD, Disable Blinking Cursor
Aug 28, 2023
i am investigating alternative 3 here to enable the hardware cursor, but disable the blinking. https://unix.stackexchange.com/a/341753/402382 |
* disable cursor blink * Update enable_disabled_cursor_blink.sh * improve shushing
dezren39
changed the title
Optimize Shutdown, Disable MOTD, Disable Blinking Cursor
Optimize Shutdown, Disable MOTD, Disable Cursor Blink
Aug 30, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
i made some scripts which remove shutdown messages, the motd messages and the cursor blink.
this is useful on a small screen and aesthetically i think it's pretty nice.
there is no longer a blinking cursor which i believe was a minor power efficiency issue with these screens.
when shutting down, there is no longer a giant list of systemd logs the advantage of this is that when you power down with end call, a newline is drawn and then it shuts down. you can read all the text like had been mentioned in hacker news. (so long as you make sure the top line isn't important to you.)
i couldn't figure out getting rid of the remaining newline during shutdown. kind of grown to like it. (edit: i have seen this appear sometimes and no newline other times. still working to understand how it occurs, if possible to have screen stays literally 1:1 exactly the same aiming for that.)
i couldn't figure out getting rid of (automatic login) line and the 2 newlines surrounding it. giving up on that. i believe the trick with using tty3 may be a possibility here? but unexplored. (edit: got rid of this in a later patch, the trick is in the getty autologin conf.)the 'my ip address is' line is probably required to make sure users with bad dns are able to figure out their issues so i didn't even look into that line. (EDIT: on another clean install and run, now i don't see 'my ip address is' anymore, but i don't know why i did before or why it's different now. not important exactly, and i still have wifi, i used literally the same launcher as before, though i guess my debian bullseye image is today's image instead of 2 days ago?)