Other Help Topics :: log-file of bootproces

Quote (mikshaw @ Sep. 20 2005,11:25)

Since screen is a whole other system of shells, it's possible that the output is being controlled by screen rather than being sent to stdout/stderr. Just guessing as usual =o)

Just out of curiosity...if it's just a headless jukebox, why use screen?

I control the box from a windows pc with putty over ssh and with screen I don't have to keep putty open all the time. I thought it was working now but the commands in bootlocal are being executed bij root so to return to the screen I also have to be root. This is not a big problem, but not the way I want it so I'll keep trying

I think you can execute it from bootlocal with "su dsl -c screen ...".

Another option might be to return /.bash_profile to it's original state of automatically logging in as dsl (if you are running in runlevel 5), and start screen from /home/dsl/.bash_profile (in place of startx). From my experience with screen in DSL, you'll need to make sure that /dev/tty1 has write permission by either user 'dsl' or group 'staff', if you haven't already done this.

Quote (mikshaw @ Sep. 20 2005,14:12)

I think you can execute it from bootlocal with "su dsl -c screen ...".

I tried that but get this error:
Cannot open your terminal '/dev/console' - please check.^M

Quote (mikshaw @ Sep. 20 2005,14:12)

Another option might be to return /.bash_profile to it's original state of automatically logging in as dsl (if you are running in runlevel 5), and start screen from /home/dsl/.bash_profile (in place of startx).

I'm to much linux-newbie to understand what you are saying here. But I'll find out

Quote (mikshaw @ Sep. 20 2005,14:12)

From my experience with screen in DSL, you'll need to make sure that /dev/tty1 has write permission by either user 'dsl' or group 'staff', if you haven't already done this.

I have read this earlier but never had problems with that, but maybe I'm having them now.

I think the /.bash_profile thing would be a non-issue for you if you didn't change it yourself (or are you running a multi-user setup?). I'm guessing you have been running screen as root?

The permission problem is likely due to root being automatically logged in on tty1, so root takes ownership of it. The only ways i know how to deal with it is to force the ownership of the tty to dsl or staff, or use screen as root, or set up your system with a login prompt instead of auto-login.

original here.