Difference between revisions of "Talk:Activating Numlock on Bootup"

From ArchWiki
Jump to: navigation, search
(systemd service -> AUR Package: Remove cllosed discussion.)
Line 6: Line 6:
 
Maybe we should put a warning at least?
 
Maybe we should put a warning at least?
  
 
== <s> systemd service -> AUR Package </s> ==
 
 
In reference to to the 12/22 modification by Hgabreu I've created a little service who launch the script described here : [https://wiki.archlinux.org/index.php/Activating_Numlock_on_Bootup#Console]
 
 
It works fine on my computer so I created a package on AUR, for sharing this little thing with the community.
 
It doesn't depend on a deprecated file from initscript, (/etc/rc.local), it's full systemd :D
 
 
You can try to install it :
 
numlockontty package
 
[https://aur.archlinux.org/packages/numlockontty/]
 
 
the service name is numLockOnTty, so you just have to enable it.
 
 
If you think it's useful, we can edit the page to add theses instruction (in proper snglish because mine is a little poor and pretty awful... sorry I'm french ^^")
 
--[[User:Ybalrid|Ybalrid]] ([[User talk:Ybalrid|talk]]) 19:37, 2 January 2013 (UTC)
 
 
It's me again, peoples ask me to change the name of the packet, so now it will be systemd-numlockontty
 
--[[User:Ybalrid|Ybalrid]] ([[User talk:Ybalrid|talk]]) 23:54, 2 January 2013 (UTC)
 
  
 
== .sh extension ==
 
== .sh extension ==

Revision as of 12:53, 11 November 2013

Extending getty@.service

For many months I used this method, and it caused huge instability problems that I couldn't track down... Putting that service in exactly as described causes VTs to flicker and go black and unresponsive about half of the time.

Maybe we should put a warning at least?


.sh extension

as of KDE. script workaround as described didn't work for me. adding .sh extension and pre-kde startup did the trick --Josephk (talk) 16:58, 23 February 2013 (UTC)