You are not logged in.
Pages: 1
Hi all,
some time ago I added "read KEY" at the end of my rc.local file, just to avoid clearing the messages at boot until a key is pressed. It has been working for a long while, but recently (I don't know exactly when, but it was after some update) it stopped working.
Has anybody experienced this issue? maybe any idea about it? The message I get, before the screen clearing, is the following:
rc.local: read "Resource temporarily unavailable"
Thanks in advance.
Offline
I can't answer your specific question, but you can use the scroll lock key to freeze the screen if you want.
Offline
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline
Mr.Elendig: I have took a look at the wiki, but it says it's possible to use the "read" command at rc.local. For me it doesn't work properly so I have use the method related to inittab. Anyway I would like to find out why "read KEY" stopped working...
foutrelis: I didn't know about the scroll lock key, I'll try it, although I would like a "persistent" solution...
thanks both for your replies.
Offline
I use one of the methods described in the wiki.
Comment out "c1:2345:respawn:/sbin/agetty -8 38400 tty1 linux" in /etc/inittab. This way you can switch back to tty1 to see the boot messages.
Regarding read, it's a shell built-in. So i guess I'd check recent changelogs of your shell. Maybe you just recently upgraded from bash3 to bash4?
no place like /home
github
Offline
thanks for your suggestion. Finally I used the inittab method explained in the wiki, with "agetty -i" option.
it's a little bit rare as I have another computer with arch, completly updated, and the same trick (read KEY) working without problem...
Offline
Pages: 1