Re: rsync and mutt woes
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. xbuffy/gbuffy, if you're using an X desktop, for example. Roger -- He's an old-fashioned dishevelled cyborg with a secret. She's a tortured junkie nun with only herself to blame. They fight crime!
Re: rsync and mutt woes
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 don't want to. -- : it's pretty hard to look miserable when you're spinning on your head
Re: rsync and mutt woes
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 the only user I might be tempted to do this: mount -o noatime,remount /home rsync ... mount -o atime,remount /home
Re: rsync and mutt woes
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]
Re: rsync and mutt woes
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 (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 set environment variables (or xhost allow, iirc) as ssh takes care of most of that stuff. the hatter
Re: rsync and mutt woes
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, not.
Unless I decide to run an X connection over ssh aswell. Which I don't
want to.
So gut the X app and turn it into a console-based one. The trick for
identifying which messages are new won't be X-specific after all.
Alternatively I've found I like maildirs. They're a little more work,
but identifying new messages is just a case of
(ls Maildir/new ; ls Maildir/cur | grep -v ':2,[A-R]?*S[T-Z]?$' ) | wc -l
And identifying which folders have new stuff is just when
Maildir/{cur,new}/ was modified later than Maildir/
--
Richard Clamp [EMAIL PROTECTED]
Re: rsync and mutt woes
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 compressed, if you did ssh -z. Makes X on a dialup barely useable instead of completely unusable. the No need to set environment variables (or xhost allow, the iirc) as ssh takes care of most of that stuff. Yes. ssh rocks. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 [EMAIL PROTECTED] URL:http://www.stonehenge.com/merlyn/ Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
Re: rsync and mutt woes
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 set environment variables (or xhost allow, iirc) as ssh takes care of most of that stuff. So, I need to be running X on my client end? I run ssh from windoze... -- Natalie Ford .. [EMAIL PROTECTED]
Re: rsync and mutt woes
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 transit, on your local display. No need to set environment variables (or xhost allow, iirc) as ssh takes care of most of that stuff. So, I need to be running X on my client end? I run ssh from windoze... Um, yeah I think so. Ssh can get the bits across the wire in a safe way, but you need an application on either end that can interpret those bits in a useful way -- which means a local X server on the Windows box. Last time I checked, there weren't any good freeware ports of Win32/X, but maybe someone has managed to compile Xfree86 under Cygwin or something. Alternatively, you can run VNC on both ends, pipe *that* through SSH, and you end up not needing anything on the Windows side except for the VNC client software (and SSH I suppose, but that seems implicit here). I'm not sure how it compares performance wise to pure X -- worse, I'm guessing -- 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... -- Chris Devers Okay, Gene... so, -1 x -1 should equal what? A South American! [] no human can understand the Timecube and Gene responded without missing a beat Yeah. I'm not human.
Re: rsync and mutt woes
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 Cygwin or something. Yep, Xfree86 does run under cygwin. Binaries are available. http://www.cygwin.com/xfree/ KDE runs pretty well too. Has anybody tried gnome? As for the performance issues Chris brings up, it depends on what you're doing. If you have a reasonably modern computer, you should be able to get it to run. Gimp over the network is pokey, but you would expect that. Xemacs is fine, and even web browsing is ok (I'd rather use galeon than IE, and my network is faster than my phone line, so it works ok.) -- mike '''Roger Waters had issues'. -- Robert Jones' -- Todd Larason' -- Barry Yarbrough
ssh (was Re: rsync and mutt woes)
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. Most of these you need to pay
for. IIRC the latest (free as in beer) versions of putty[2] does X
forwarding, but you'll still need a seperate X Server running on
the windows box otherwise it won't have anything capible of drawing the
actual application ;-)
Personally on my Windows box I use cygwin[3] (free - beer and speech -
windows port of gnu stuff that has a nice installer) with a port of
gnu-ssh and XFree86[4]. It's not the most elegant solution, but it works
well enough for me for my occasional windows use and I don't have to pay
for anything. Most importantly, it's not rootless, meaning all your
Xserver windows run inside a big window.
Win-R
cmd
bash
startx
ssh 2shortplanks.com
xterm
[1] Oddness of X. The server is the computer with the monitor
attached to it. The programs you run on your Linux/FreeBSD/Computer are
the clients that need a server to display upon. It's the programs that
initilise the conversation because they want to display something.
[2] http://www.chiark.greenend.org.uk/~sgtatham/putty/
[3] http://www.cygwin.com/
[4] http://cygwin.com/xfree/
--
s'' Mark Fowler London.pm Bath.pm
http://www.twoshortplanks.com/ [EMAIL PROTECTED]
';use Term'Cap;$t=Tgetent Term'Cap{};print$t-Tputs(cl);for$w(split/ +/
){for(0..30){$|=print$t-Tgoto(cm,$_,$y). $w;select$k,$k,$k,.03}$y+=2}
Re: rsync and mutt woes
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 running X applications
between places with huge huge pipes that have a couple of slow hops
between them. If it takes 800ms for a packet to get there and back it's
really noticable.
Later.
Mark.
--
s'' Mark Fowler London.pm Bath.pm
http://www.twoshortplanks.com/ [EMAIL PROTECTED]
';use Term'Cap;$t=Tgetent Term'Cap{};print$t-Tputs(cl);for$w(split/ +/
){for(0..30){$|=print$t-Tgoto(cm,$_,$y). $w;select$k,$k,$k,.03}$y+=2}
