Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@stop What do you mean?
-
@Benedikt su should just work.
-
@stop Well, not exactly. If you su from an user to another (which is not root), the second user has no permissions to write to the pseudo-terminal of the first user. So you will get an error like "Cannot open your terminal '/dev/pts/x' - please check." if you try to use screen without previously creating a new pseudo-terminal (which "script /dev/null" does).
Another dev on my team just got a new machine. Before he came in today I made two separate USB installers and ...
The little things are what makes you happy.
It was really annoying that screen doesn't work after an su. It makes sense, but typing "script /dev/null" everytime (and remember to write "exit" after it so bash history works again) is annoying.
So a little script to "/bin/scrn" with the following content made my life better:
#!/bin/sh
command="screen $@"
script /dev/null -c "$command"
Never worry about screen after su again! Tech life is great, isn't it?
rant
screen
linux
su
shell script