No. The only difference between clear and clear_console ist that
clear_console gets rid of the scrollback buffer of Linux VTs. For
Xterms, serial consoles etc. there is no difference as far as I know.
--
clear_console should be moved to ncurses-bin
https://bugs.launchpad.net/bugs/39068
You
This probably relates to the group that owns /dev/tty0 and /dev/console
- I noticed that some of the servers I administer would exhibit this
behaviour and others wouldn't. On my 9.04 desktop they're owned by root,
but on an 8.04 server they're owned by dialout, and I was a member of
the dialout
** Changed in: bash (Ubuntu)
Status: Incomplete = Triaged
--
clear_console should be moved to ncurses-bin
https://bugs.launchpad.net/bugs/39068
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
I've taken the time to recreate the bug as described in the test case in
Karmic Koala, what will be the 9.10 release of Ubuntu, and one does
still need to be root to use clear_console on a pty. Subsequently, I am
changing the bug's state back to it's original one of Triaged.
Sebastian - it might
BTW, I'm still convinced that this inconistency should be fixed, one way
or the other. The best probably is to make clear do everything
clear_console does.
--
clear_console should be moved to ncurses-bin
https://bugs.launchpad.net/bugs/39068
You received this bug notification because you are a
Well, the inconsistency is _trivial_ to reproduce, it doesn't make any
sense to set it to incomplete. Just compare clear_console vs. sudo
clear_console in a pty.
--
clear_console should be moved to ncurses-bin
https://bugs.launchpad.net/bugs/39068
You received this bug notification because you
** Changed in: bash (Ubuntu)
Status: Confirmed = Triaged
--
clear_console should be moved to ncurses-bin
https://bugs.launchpad.net/bugs/39068
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
