On Fri, Nov 08, 2002 at 05:28:52PM +0100, Ivan Brezina wrote:
On Fri, 8 Nov 2002, Joseph Pingenot wrote:
From Norbert Preining on Friday, 08 November, 2002:
I think that vim-gtk tries to open a window, recognizes that this
doesn't work (authorization) and starts normal text mode vi.
On Fri, Nov 08, 2002 at 05:28:52PM +0100, Ivan Brezina wrote:
On Fri, 8 Nov 2002, Joseph Pingenot wrote:
From Norbert Preining on Friday, 08 November, 2002:
I think that vim-gtk tries to open a window, recognizes that this
doesn't work (authorization) and starts normal text mode vi.
* David Stanaway [EMAIL PROTECTED] [20021110 14:19]:
On Fri, 2002-11-08 at 11:42, Joseph Pingenot wrote:
xhost is for working with connections coming over tcp. :0.0 uses
a named socket (/tmp/Xsomething), and Debian's X servers don't listen
in on a tcp socket by default (security. No
* David Stanaway [EMAIL PROTECTED] [20021110 14:19]:
On Fri, 2002-11-08 at 11:42, Joseph Pingenot wrote:
xhost is for working with connections coming over tcp. :0.0 uses
a named socket (/tmp/Xsomething), and Debian's X servers don't listen
in on a tcp socket by default (security. No
I am using woody + testing + some unstable:
in xterm/gnome-terminal usually I do (as normal user)
xhost +
This disables access control in the X server. This is, almost always,
a very bad idea.
Indeed. Therefore I use
mfluch@seneca:~$ su
Password:
root@seneca:/home/mfluch export
Quoting Martin Fluch ([EMAIL PROTECTED]):
Indeed. Therefore I use
mfluch@seneca:~$ su
Password:
root@seneca:/home/mfluch export XAUTHORITY=/home/mfluch/.Xauthority
root@seneca:/home/mfluch
...and then every X application works just as before as the normal user.
It's a little simpler
On Sat, 9 Nov 2002, Rick Moen wrote:
mfluch@seneca:~$ su
Password:
root@seneca:/home/mfluch export XAUTHORITY=/home/mfluch/.Xauthority
root@seneca:/home/mfluch
...and then every X application works just as before as the normal user.
It's a little simpler to do:
$ ssh -X
On Sat, 9 Nov 2002, Jörg Schütter wrote:
On Sat, 9 Nov 2002 13:36:25 +0200 (EET)
Martin Fluch [EMAIL PROTECTED] wrote:
On Sat, 9 Nov 2002, Rick Moen wrote:
It's a little simpler to do:
$ ssh -X root@localhost
Even easier: the following lines in the /root/.bashrc do the
Try http://fgouget.free.fr/sux/sux-readme.shtml
chj
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Quoting Martin Fluch ([EMAIL PROTECTED]):
Indeed. Therefore I use
[EMAIL PROTECTED]:~$ su
Password:
[EMAIL PROTECTED]:/home/mfluch export XAUTHORITY=/home/mfluch/.Xauthority
[EMAIL PROTECTED]:/home/mfluch
...and then every X application works just as before as the normal user.
It's
On Sat, 9 Nov 2002, Rick Moen wrote:
[EMAIL PROTECTED]:~$ su
Password:
[EMAIL PROTECTED]:/home/mfluch export XAUTHORITY=/home/mfluch/.Xauthority
[EMAIL PROTECTED]:/home/mfluch
...and then every X application works just as before as the normal user.
It's a little simpler to
On Sat, 9 Nov 2002 13:36:25 +0200 (EET)
Martin Fluch [EMAIL PROTECTED] wrote:
On Sat, 9 Nov 2002, Rick Moen wrote:
It's a little simpler to do:
$ ssh -X [EMAIL PROTECTED]
Even easier: the following lines in the /root/.bashrc do the same trick:
if [ ! $LOGNAME = root ]; then
On Sat, 9 Nov 2002, Jörg Schütter wrote:
On Sat, 9 Nov 2002 13:36:25 +0200 (EET)
Martin Fluch [EMAIL PROTECTED] wrote:
On Sat, 9 Nov 2002, Rick Moen wrote:
It's a little simpler to do:
$ ssh -X [EMAIL PROTECTED]
Even easier: the following lines in the /root/.bashrc do the
Try http://fgouget.free.fr/sux/sux-readme.shtml
chj
No, but I have noticed when i open an xterm, su to root and run
vi(vim-gtk), whenever I quit vi, i get this.
Xlib: connection to :0.0 refused by server
Xlib: Client is not authorized to connect to Server
Xlib: connection to :0.0 refused by server
Xlib: Client is not authorized to connect to
On Fre, 08 Nov 2002, Steve Johnson wrote:
No, but I have noticed when i open an xterm, su to root and run
vi(vim-gtk), whenever I quit vi, i get this.
Xlib: connection to :0.0 refused by server
Xlib: Client is not authorized to connect to Server
Xlib: connection to :0.0 refused by server
This one time, at band camp, Steve Johnson said:
No, but I have noticed when i open an xterm, su to root and run
vi(vim-gtk), whenever I quit vi, i get this.
Xlib: connection to :0.0 refused by server
Xlib: Client is not authorized to connect to Server
Xlib: connection to :0.0 refused by
From Norbert Preining on Friday, 08 November, 2002:
I think that vim-gtk tries to open a window, recognizes that this
doesn't work (authorization) and starts normal text mode vi.
Probably the easiest way to do this is, instead of using su/sudo, run
ssh -X localhost. It'll tunnel your X apps
On Fri, 8 Nov 2002, Joseph Pingenot wrote:
From Norbert Preining on Friday, 08 November, 2002:
I think that vim-gtk tries to open a window, recognizes that this
doesn't work (authorization) and starts normal text mode vi.
Probably the easiest way to do this is, instead of using su/sudo,
From Ivan Brezina on Friday, 08 November, 2002:
Another possibility is:
su -c vim-gtk
you can also use xhost +username for allowing users to connect to our
Xserver. But this does not work for me on Debian.
xhost is for working with connections coming over tcp. :0.0 uses
a named socket
xhost is for working with connections coming over tcp. :0.0 uses
a named socket (/tmp/Xsomething), and Debian's X servers don't listen
in on a tcp socket by default (security. No chance of someone sniffing
your password if nobody can connect remotely!). Thus, xhost won't work.
I am
On Fri, 2002-11-08 at 11:42, Joseph Pingenot wrote:
xhost is for working with connections coming over tcp. :0.0 uses
a named socket (/tmp/Xsomething), and Debian's X servers don't listen
in on a tcp socket by default (security. No chance of someone sniffing
your password if nobody can
Indeed. My mistake. I just verified that X wasn't listening in to
tcp/6000, xhost +'ed, and su -'ed, setup the display variable, and it
worked.
NM. I'm wrong. Seems something on this guy's end is borken.
-Joseph
--
[EMAIL PROTECTED]
As far as Microsoft, we will never take a company
On Fri, Nov 08, 2002 at 10:53:10AM -0800, Yogesh Sharma wrote:
xhost is for working with connections coming over tcp. :0.0 uses
a named socket (/tmp/Xsomething), and Debian's X servers don't listen
in on a tcp socket by default (security. No chance of someone sniffing
your
On Fre, 08 Nov 2002, Steve Johnson wrote:
No, but I have noticed when i open an xterm, su to root and run
vi(vim-gtk), whenever I quit vi, i get this.
Xlib: connection to :0.0 refused by server
Xlib: Client is not authorized to connect to Server
Xlib: connection to :0.0 refused by server
This one time, at band camp, Steve Johnson said:
No, but I have noticed when i open an xterm, su to root and run
vi(vim-gtk), whenever I quit vi, i get this.
Xlib: connection to :0.0 refused by server
Xlib: Client is not authorized to connect to Server
Xlib: connection to :0.0 refused by
From Norbert Preining on Friday, 08 November, 2002:
I think that vim-gtk tries to open a window, recognizes that this
doesn't work (authorization) and starts normal text mode vi.
Probably the easiest way to do this is, instead of using su/sudo, run
ssh -X localhost. It'll tunnel your X apps
On Fri, 8 Nov 2002, Joseph Pingenot wrote:
From Norbert Preining on Friday, 08 November, 2002:
I think that vim-gtk tries to open a window, recognizes that this
doesn't work (authorization) and starts normal text mode vi.
Probably the easiest way to do this is, instead of using su/sudo,
xhost is for working with connections coming over tcp. :0.0 uses
a named socket (/tmp/Xsomething), and Debian's X servers don't listen
in on a tcp socket by default (security. No chance of someone sniffing
your password if nobody can connect remotely!). Thus, xhost won't work.
I am
On Fri, 2002-11-08 at 11:42, Joseph Pingenot wrote:
xhost is for working with connections coming over tcp. :0.0 uses
a named socket (/tmp/Xsomething), and Debian's X servers don't listen
in on a tcp socket by default (security. No chance of someone sniffing
your password if nobody can
Indeed. My mistake. I just verified that X wasn't listening in to
tcp/6000, xhost +'ed, and su -'ed, setup the display variable, and it
worked.
NM. I'm wrong. Seems something on this guy's end is borken.
-Joseph
--
[EMAIL PROTECTED]
As far as Microsoft, we will never take a company
On Fri, Nov 08, 2002 at 10:53:10AM -0800, Yogesh Sharma wrote:
xhost is for working with connections coming over tcp. :0.0 uses
a named socket (/tmp/Xsomething), and Debian's X servers don't listen
in on a tcp socket by default (security. No chance of someone sniffing
your
32 matches
Mail list logo
