On Mon, Feb 25, 2002 at 02:38:03AM -0800, Randal L. Schwartz wrote:
You're either going to update the atime, or you have to update the
ctime to reset the atime, or you have to read the raw disk somehow.
Or use something other than mutt to tell you which mailboxes have new
messages in them.
On Mon, Feb 25, 2002 at 10:51:44AM +, Roger Burton West said:
Or use something other than mutt to tell you which mailboxes have new
messages in them. xbuffy/gbuffy, if you're using an X desktop, for
example.
I'm, err, not.
Unless I decide to run an X connection over ssh aswell. Which I
On Mon, Feb 25, 2002 at 10:51:44AM +, Roger Burton West wrote:
On Mon, Feb 25, 2002 at 02:38:03AM -0800, Randal L. Schwartz wrote:
You're either going to update the atime, or you have to update the
ctime to reset the atime, or you have to read the raw disk somehow.
On a system where I am
On Mon, Feb 25, 2002 at 11:29:25AM +, Simon Wistow wrote:
Unless I decide to run an X connection over ssh aswell. Which I don't
want to.
You can run x over ssh? Kewl! How?
--
Natalie Ford .. [EMAIL PROTECTED]
On Mon, 25 Feb 2002, Natalie Ford wrote:
On Mon, Feb 25, 2002 at 11:29:25AM +, Simon Wistow wrote:
Unless I decide to run an X connection over ssh aswell. Which I don't
want to.
You can run x over ssh? Kewl! How?
Just make sure your ssh server and client both have it enabled
On Mon, Feb 25, 2002 at 11:29:25AM +, Simon Wistow wrote:
On Mon, Feb 25, 2002 at 10:51:44AM +, Roger Burton West said:
Or use something other than mutt to tell you which mailboxes have new
messages in them. xbuffy/gbuffy, if you're using an X desktop, for
example.
I'm, err,
the == the hatter [EMAIL PROTECTED] writes:
the Just make sure your ssh server and client both have it enabled
the (ForwardX11 yes and X11Forwarding yes) and then run programs as normal
the on the remote server. Then up they pop, encrypted in transit, on your
the local display.
And
On Mon, Feb 25, 2002 at 12:30:38PM +, the hatter wrote:
Just make sure your ssh server and client both have it enabled
(ForwardX11 yes and X11Forwarding yes) and then run programs as normal
on the remote server. Then up they pop, encrypted in transit, on your
local display. No need to
On Mon, 25 Feb 2002, Natalie Ford wrote:
On Mon, Feb 25, 2002 at 12:30:38PM +, the hatter wrote:
Just make sure your ssh server and client both have it enabled
(ForwardX11 yes and X11Forwarding yes) and then run programs as normal
on the remote server. Then up they pop, encrypted in
On Mon, 2002-02-25 at 17:05, Chris Devers wrote:
On Mon, 25 Feb 2002, Natalie Ford wrote:
So, I need to be running X on my client end? I run ssh from windoze...
Last time I checked, there weren't any good freeware ports of Win32/X, but
maybe someone has managed to compile Xfree86 under
On Mon, 25 Feb 2002, Natalie Ford wrote:
So, I need to be running X on my client end? I run ssh from windoze...
No you need to be running an XServer on your server end[1].
There are many X servers that work with Windows, and many ssh clients that
will do the forwarding to these clients.
On Mon, 25 Feb 2002, Chris Devers wrote:
but it's super easy to set up and the main performance constraint seems to
be plain old bandwidth, as opposed to whatever ram disc space you'd need
to get X going reasonably well on top of Windows...
The real killer is latency. I've had problems
12 matches
Mail list logo
