On Wed, 17 Mar 2010 00:50:42 +, Peter Humphrey wrote:
It is? In that case I don't know how I've managed with Linux since 1993
without it.
That's what everyone who hasn't used screen says, I said the same.
There are those that use screen and those that haven't tried it, I've yet
to meet
Neil Bothwick wrote:
On Wed, 17 Mar 2010 00:50:42 +, Peter Humphrey wrote:
It is? In that case I don't know how I've managed with Linux since 1993
without it.
That's what everyone who hasn't used screen says, I said the same.
There are those that use screen and those that
On Wednesday 17 March 2010 08:46:36 Dale wrote:
You really need to check out screen Peter. I'd be glad to help with
the basics of it.
That's a generous offer, Dale. I may take you up on it...
--
Rgds
Peter.
On Tue, 16 Mar 2010 01:00:21 +, David W Noon wrote:
As do the log files in $PORT_LOGDIR, they contain exactly the same
output you would see in the terminal.
Not quite. The sequence in which the ebuilds were run is lost when the
discrete logs are your only source of tracing through,
On 15 Mar 2010, at 20:46, David W Noon wrote:
...
Because emerge jobs produce copious amounts of output that is
difficult
to read as it scrolls past. I much prefer the cron daemon or at
daemon
to send me the output as email, so I can scroll backwards and
forwards through it at my leisure.
Stroller writes:
I'm going to assume that you're not being facetious, however I'm
amazed you don't know `screen`. Everyone should know `screen`! It's
amazing, and I can't believe that if you had tried it then you
wouldn't have it installed. I sure you'll wonder how you lived without
it.
Yes
On 16 Mar 2010, at 22:26, Alex Schuster wrote:
...
I want to add one thing: I suggest changing the defscrollback value in
/etc/screenrc from 100 to something much larger, I have 10. If
not,
you can only scroll back 100 lines, which is not that much.
I don't *think* the default is as
Stroller writes:
On 16 Mar 2010, at 22:26, Alex Schuster wrote:
...
I want to add one thing: I suggest changing the defscrollback value
in /etc/screenrc from 100 to something much larger, I have 10.
If not, you can only scroll back 100 lines, which is not that much.
I don't
On Tuesday 16 March 2010 22:26:28 Alex Schuster wrote:
Yes screen is quite essential.
It is? In that case I don't know how I've managed with Linux since 1993
without it.
--
Rgds
Peter.
On 17 Mar 2010, at 00:50, Peter Humphrey wrote:
On Tuesday 16 March 2010 22:26:28 Alex Schuster wrote:
Yes screen is quite essential.
It is? In that case I don't know how I've managed with Linux since
1993
without it.
I don't know how I managed in my youth without a washing machine,
On Monday 15 March 2010 02:44:56 fire-eyes wrote:
Are you using the EU pool? I am, and I have that problem frequently.
I don't have /that/ problem at all. The only problem I have with it is
the Irish server in the pool - it wouldn't be enough to go for a cuppa
while it's running; I'd have to
On Mon, 15 Mar 2010 10:10:52 +, Peter Humphrey wrote:
I don't have /that/ problem at all. The only problem I have with it is
the Irish server in the pool - it wouldn't be enough to go for a cuppa
while it's running; I'd have to come back tomorrow if I let it continue
at its own pace*.
On Mon, 15 Mar 2010 12:10:02 +0100, Peter Humphrey wrote about Re:
[gentoo-user] what's wrong with rsync 3.0.6?:
On Monday 15 March 2010 02:44:56 fire-eyes wrote:
Are you using the EU pool? I am, and I have that problem frequently.
I don't have /that/ problem at all. The only problem I have
On Monday 15 March 2010 14:15:08 David W Noon wrote:
You run your emerge --sync jobs by hand?!!!
I run mine from the root crontab.
My boxes aren't allowed to run all night, so I call a script that runs
the updating process when I fire them up in the morning. No sweat.
I also have it
On Monday 15 March 2010 12:28:49 Neil Bothwick wrote:
Is that heanet.ie?
Yes.
I always get decent speeds from there.
Just shows what oddities show up from time to time in complex networks.
My speed is far better from eastern Europe (Ukraine, Latvia, ...) than
from just across the Irish
On Mon, Mar 15, 2010 at 02:15:08PM +, David W Noon wrote:
You run your emerge --sync jobs by hand?!!!
Why is that surprising? My laptop does not have an always-on internet
connection, nevermind it sits silently and off for most of the day. I
sync by hand when I have time, roughly twice each
On Mon, Mar 15, 2010 at 5:10 AM, Peter Humphrey
pe...@humphrey.ukfsn.org wrote:
On Monday 15 March 2010 02:44:56 fire-eyes wrote:
Are you using the EU pool? I am, and I have that problem frequently.
I don't have /that/ problem at all. The only problem I have with it is
the Irish server in
On Mon, 15 Mar 2010 17:00:02 +0100, Willie Wong wrote about Re:
[gentoo-user] what's wrong with rsync 3.0.6?:
On Mon, Mar 15, 2010 at 02:15:08PM +, David W Noon wrote:
You run your emerge --sync jobs by hand?!!!
Why is that surprising?
Because emerge jobs produce copious amounts of output
On 15 Mar 2010, at 17:08, David W Noon wrote:
On Mon, 15 Mar 2010 17:00:02 +0100, Willie Wong wrote about Re:
[gentoo-user] what's wrong with rsync 3.0.6?:
On Mon, Mar 15, 2010 at 02:15:08PM +, David W Noon wrote:
You run your emerge --sync jobs by hand?!!!
Why is that surprising
On Mon, 15 Mar 2010 19:20:02 +0100, Stroller wrote about Re:
[gentoo-user] what's wrong with rsync 3.0.6?:
On 15 Mar 2010, at 17:08, David W Noon wrote:
On Mon, 15 Mar 2010 17:00:02 +0100, Willie Wong wrote about Re:
[gentoo-user] what's wrong with rsync 3.0.6?:
On Mon, Mar 15, 2010 at 02:15
On Mon, Mar 15, 2010 at 05:08:06PM +, David W Noon wrote:
On Mon, 15 Mar 2010 17:00:02 +0100, Willie Wong wrote about Re:
[gentoo-user] what's wrong with rsync 3.0.6?:
On Mon, Mar 15, 2010 at 02:15:08PM +, David W Noon wrote:
You run your emerge --sync jobs by hand?!!!
Why
On Mon, 15 Mar 2010 23:20:03 +0100, Willie Wong wrote about Re:
[gentoo-user] what's wrong with rsync 3.0.6?:
On Mon, Mar 15, 2010 at 05:08:06PM +, David W Noon wrote:
[snip]
Because emerge jobs produce copious amounts of output that is
difficult to read as it scrolls past. I much prefer
On Mon, 15 Mar 2010 20:46:11 +, David W Noon wrote:
I do know `man less`, `man more`, etc., and output redirection to file.
Heck, I'm even old enough to know Ctl+S and Ctl+Q, as I used to
program PDP-11s back in the 1970s. But none of those addresses the
fundamental issue of sitting there
On Mon, 15 Mar 2010 23:10:41 +, David W Noon wrote:
Also, for builds, there is such a
thing as elogs (which allows you to save all messages to
/var/log/portage for ease of reading at your leisure.
I have mine go to /var/log/portage/log. But these only log the
activities within a
On Tue, 16 Mar 2010 00:20:02 +0100, Neil Bothwick wrote about Re:
[gentoo-user] what's wrong with rsync 3.0.6?:
On Mon, 15 Mar 2010 23:10:41 +, David W Noon wrote:
Also, for builds, there is such a
thing as elogs (which allows you to save all messages to
/var/log/portage for ease
On Tue, Mar 16, 2010 at 01:00:21AM +, David W Noon wrote
On Tue, 16 Mar 2010 00:20:02 +0100, Neil Bothwick wrote
As do the log files in $PORT_LOGDIR, they contain exactly the same
output you would see in the terminal.
Not quite. The sequence in which the ebuilds were run is lost when
Am 14.03.2010 00:42, schrieb pk:
On 2010-03-13 20:15, Jarry wrote:
obelix ~ # emerge --sync
Starting rsync with rsync://134.68.220.73/gentoo-portage...
Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
rsync.c(544) [receiver=3.0.6]
Jarry wrote:
Hi, I noticed this error when I try to sync my portage tree:
---
obelix ~ # emerge --sync
Starting rsync with rsync://134.68.220.73/gentoo-portage...
Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
rsync.c(544)
Hi, I noticed this error when I try to sync my portage tree:
---
obelix ~ # emerge --sync
Starting rsync with rsync://134.68.220.73/gentoo-portage...
Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
rsync.c(544) [receiver=3.0.6]
On 2010-03-13 20:15, Jarry wrote:
obelix ~ # emerge --sync
Starting rsync with rsync://134.68.220.73/gentoo-portage...
Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at
rsync.c(544) [receiver=3.0.6]
Retrying...
It's the server, not rsync
30 matches
Mail list logo