On 25 June 2014 16:09, Liam Proven wrote:
> On 24 June 2014 12:03, Ian Malone wrote:
>> PS, you've misspelt Microsoft. If you want to be consistent you need
>> to make up humorous[1] misspellings of NetworkManager and Evolution
>> too.
>> [1] For low values of humorous.
>
>
> I suggest MICROS~1.
On 24 June 2014 12:03, Ian Malone wrote:
> PS, you've misspelt Microsoft. If you want to be consistent you need
> to make up humorous[1] misspellings of NetworkManager and Evolution
> too.
> [1] For low values of humorous.
I suggest MICROS~1. It's what Win9x turned the name of the "Microsoft
Off
On 23 June 2014 21:16, Joe Zeff wrote:
> On 06/23/2014 11:43 AM, Liam Proven wrote:
>>
>> Now let's assume we were both Japanese. Could we record and search
>> accurately for a written sentence in English?
>
>
> Considering that most Japanese students study English in school? Probably.
:¬) All
Allegedly, on or about 24 June 2014, Ian Malone sent:
> PS, you've misspelt Microsoft. If you want to be consistent you need
> to make up humorous[1] misspellings of NetworkManager and Evolution
> too.
They've worked very hard to earn their denigrations...
--
[tim@localhost ~]$ uname -rsvp
Linux
On 24 June 2014 09:13, Tim wrote:
> Allegedly, on or about 23 June 2014, Ian Malone sent:
>> Though I'll bet the error doesn't actually mean that the clock is not
>> set correctly. The usual experience is it'll be something else going
>> wrong for which the underlying cause is the clock set incorr
Allegedly, on or about 23 June 2014, Ian Malone sent:
> Though I'll bet the error doesn't actually mean that the clock is not
> set correctly. The usual experience is it'll be something else going
> wrong for which the underlying cause is the clock set incorrectly and
> anonymous error is being rep
On 23 June 2014 19:43, Liam Proven wrote:
> On 23 June 2014 20:33, Tim wrote:
>> Tim:
Why the hell couldn't the computer just have said to set the clock
manually, since it couldn't manage to do it itself, instead of some
moronic number code?
>>
>>
>> Liam Proven:
>>> I know this wa
On 06/23/2014 11:43 AM, Liam Proven wrote:
Now let's assume we were both Japanese. Could we record and search
accurately for a written sentence in English?
Considering that most Japanese students study English in school? Probably.
--
users mailing list
users@lists.fedoraproject.org
To unsubscr
On 23 June 2014 20:33, Tim wrote:
> Tim:
>>> Why the hell couldn't the computer just have said to set the clock
>>> manually, since it couldn't manage to do it itself, instead of some
>>> moronic number code?
>
>
> Liam Proven:
>> I know this was a rhetorical question, but:
>>
>> These days softwa
Tim:
>> Why the hell couldn't the computer just have said to set the clock
>> manually, since it couldn't manage to do it itself, instead of some
>> moronic number code?
Liam Proven:
> I know this was a rhetorical question, but:
>
> These days software is expected to be localised into hundreds o
On 22 June 2014 17:04, Tim wrote:
> Why the hell couldn't the
> computer just have said to set the clock manually, since it couldn't
> manage to do it itself, instead of some moronic number code?
I know this was a rhetorical question, but:
These days software is expected to be localised into h
On Sun, 2014-06-22 at 15:24 +0100, Timothy Murphy wrote:
> Do you mean that rsync actually sent the message,
> or that it was an error in rsync that motivated BackupPC to send it?
IIRC when I saw it it was something in /var/log/rsnapshot
or /var/log/cron, but it was a while back.
poc
--
users m
Allegedly, on or about 22 June 2014, Timothy Murphy sent:
> Incidentally, in defence of my rant, I've found that
> when I actually try to trace an error message in the source -
> I used to do this quite a lot with NetworkManager
> when it used to send out error messages which just said
> "Failure 2
Patrick O'Callaghan wrote:
>> What 4 bytes did it want to read, incidentally?
> AFAIK it's actually an error from rsync (I've seen it in rsnapshot as
> well, which is also rsync-based). Google for more.
Do you mean that rsync actually sent the message,
or that it was an error in rsync that motiv
On Fri, 20 Jun 2014 14:21:52 -0400
George Avrunin wrote:
> It can also occur with BackupPC when keyless ssh isn't set up right
> and ssh is giving a prompt (e.g., on the first ssh login to a host). Has
> happened to me more than once...
Yea, that's the reason you find everywhere when googling, w
On Fri, 20 Jun 2014 19:16:29 +0100, "Patrick O'Callaghan"
wrote:
> On Fri, 2014-06-20 at 12:13 -0400, Tom Horsley wrote:
> > On Fri, 20 Jun 2014 16:48:38 +0100
> > Patrick O'Callaghan wrote:
> >
> > > AFAIK it's actually an error from rsync (I've seen it in rsnapshot as
> > > well, which is also
On Fri, 2014-06-20 at 12:13 -0400, Tom Horsley wrote:
> On Fri, 20 Jun 2014 16:48:38 +0100
> Patrick O'Callaghan wrote:
>
> > AFAIK it's actually an error from rsync (I've seen it in rsnapshot as
> > well, which is also rsync-based). Google for more.
>
> And apparently, what it actually means is:
On Fri, 20 Jun 2014 16:48:38 +0100
Patrick O'Callaghan wrote:
> AFAIK it's actually an error from rsync (I've seen it in rsnapshot as
> well, which is also rsync-based). Google for more.
And apparently, what it actually means is: "Hey! I'm trying to
talk to an incompatible version of rsync on the
On Fri, 2014-06-20 at 15:50 +0100, Timothy Murphy wrote:
> Many applications give unhelpful error messages,
> but I've never met any quite as useless
> as the invariable message from BackupPC:
> "Unable to read 4 bytes"
> If only it could sometimes say
> "Unable to read 3 bytes"
> or even "Hooray,
Is BackupPC packaged for Fedora now?
While this particular error message is, I agree, pretty useless, I'll make a general comment.
Software is, necessarily, notorious for generally only being able to "present the evidence immediately before it". Most applications, for example,
cannot know
Many applications give unhelpful error messages,
but I've never met any quite as useless
as the invariable message from BackupPC:
"Unable to read 4 bytes"
If only it could sometimes say
"Unable to read 3 bytes"
or even "Hooray, was able to read 1 byte".
What 4 bytes did it want to read, incidental
21 matches
Mail list logo
