Hi im making ICS machine using my old laptop and boot it on runlevel 3 by default.
However the screen doesn’t automatically turn off and keep displaying the login prompt; unless i set it on
xterm -blank 1
But again, this command doesn’t carry to next power on. means I have to re enter it after every shutdown/reboot.
how to make it remember my setting (or at least automatically input the line after each boot)?
On 2014-09-24 22:56, razirazo 90 wrote:
>
> Hi im making ICS machine using my old laptop and boot it on runlevel 3
> by default.
>
> However the screen doesn’t automatically turn off and keep displaying
> the login prompt; unless i set it on
>
> Code:
> --------------------
> xterm -blank 1
> --------------------
What you say does not match.
If you are using runlevel 3, you can not use xterm.
Maybe you skipped part of the description of your system?
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
OMG LOL wrong name!
Actually I mean setterm
(playing too much with xterm lately… sigh)
How do I edit the first post?
LOL!
You can put a “setterm” command in your “.profile” or other shell startup file. That way, it is automatically run.
How do I edit the first post?
You don’t (except in the first few minutes after posting)
On 2014-09-25 21:06, razirazo 90 wrote:
> OMG LOL wrong name!
>
> Actually I mean setterm
Ahhh! 
> (playing too much with xterm lately… sigh)
I needed a similar on an laptop. In text mode, the display eventually
sleeps, and is incapable of waking up. In the end, I wrote a script in
/root/bin/:
#!/bin/bash
setterm -blank 0 -store
setterm -powerdown 0
setterm -powersave off
echo “Terminal setterm done.”
klogconsole -r 10
I think I got it called from .bashrc, which of course means that I had
to log-in at least once, as root. And redo on each hibernation cycle.
Finally, I decided not to use it, and instead boot to runlevel 5, even
if I then go to a terminal. I graphical mode, the screen is handled
correctly: it goes to sleep and awakes when wanted, thus using less
electricity and probably lasting longer. It is already an old machine,
so the duration of the backlight is a consideration.
> How do I edit the first post?
You can not, and that’s intentional. Reasons explained in the FAQ, I
believe.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
thanks for the answer.
now I solved it by putting init script in init.d and symlink in runlevel 3 init folder.
On 2014-09-28 13:06, razirazo 90 wrote:
>
> thanks for the answer.
>
> now I solved it by putting init script in init.d and symlink in runlevel
> 3 init folder.
Curious. I thought that would not work…
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Lol actually im not really sure. I blindly tried like 4-5 other random solutions suggested around internet as well, reboot, and it just magically (and curiously) work now.
I thought it was the init script.
But then you said it wouldn’t work, means there is any one the other that actually do the trick.
On 2014-09-28 18:36, razirazo 90 wrote:
> Lol actually im not really sure. I blindly tried like 4-5 other random
> solutions suggested around internet as well, reboot, and it just
> magically (and curiously) work now.
>
> I thought it was the init script.
> But then you said it wouldn’t work, means there is any one the other
> that actually do the trick.
I think that the init script does not work because it is not attached to
a terminal, so setterm fails. I think I tried to do it that way
previously and failed, so I’m surprised if it works for you.
If you have another method “running and trying”, it could be that one
which is doing the trick and not the init script
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)