[mythtv-users] Can mythtv handle two dumb capture cards?

[Isaac Richards]

On Thursday 22 July 2004 03:44 pm, Maarten wrote:
> On Thursday 22 July 2004 21:05, Isaac Richards wrote:
> > On Thursday 22 July 2004 02:38 pm, Maarten wrote:
> > > On Thursday 22 July 2004 20:03, Isaac Richards wrote:
> > >
> > > Djeeez louise...  I just pointed out some little thing, no need to spin
> > > it into a whole tediously long thread...!
> >
> > I took offense to your shitty attitude, else I wouldn't have bothered
> > responding at all.  But since you insist...
>
> ...MY shitty attitude...?  Oh yeah, you're always backing J. D. Stanley, so
> it figures you stepped in.  But never mind that.  He, IMHO, was wrong and
> still is and yes, I react bad to people who are stubborn like that.

I back up people who contribute to my project, yes, especially when they're 
right.  He was wrong when he said it doesn't log, of course, but you were 
also wrong when you said that the default behavior is to log.

> > > But, since we're here now, and since we obviously are both too stubborn
> > > to admit to anything, let me quote you directly from your own official
> > > docs, although I fear this is gonna get real repetitive over time:
> >
> > Section 21 is additional optional configuration.  You've cut out the
> > 'contributed by' attributions who, coincidentally, aren't developers. 
> > The docs on how to run mythbackend are in section 9.2.
>
> Yeah ?  And can you then please quote me what the exact last sentence is of
> chapter 9.2 which you are referring to now ?   Precisely...

Do you have reading comprehension difficulties?  What does 'For example, you 
may add this' mean to you?  Does it say 'go out and do this right now'?  Does 
it say 'you must do this now or you will not have a working system'?

Instead, it says:
 
Once mythfilldatabase has finished, start the master server before continuing. 
$ mythbackend

If the user does something beyond that, they're changing the defaults.

> You know, I do understand where this is coming from but you must understand
> that joe average user will not -after the first trials- keep starting
> mythbackend manually.  

Then they're changing the defaults.

> So they will follow your instructions, hence click 
> the link to chapter 21 from chapter 9. They then will install the contrib
> file -per the docs- and off they go.  

Again, changing the defaults.

> I have 8 years professional linux 
> experience; you don't need to tell ME how to en- or disable logging.  But
> the fact of the matter is, you always hammer on readling the docs, and
> rightly so.  But please be good enough to admit it when there is a slight
> misalignment between what you say and what the docs say. It won't kill ya.
> We didn't have to get into a flamewar over this, quite trivial, little
> point.

It's always funny when people get defensive enough to bring up how many years 
of experience they have with something, especially when it doesn't have 
anything to do with anything.

> From my viewpoint it's very simple: following your docs most people will
> end up with a _logging_ mythbackend, never mind your good intentions and
> how the app may have been compiled.   But I reckon, we cannot agree on this
> ? Okay.

And so will people who install binary rpms/debs and use their init scripts -- 
but it still doesn't change the fact that the default in the source is not to 
log to a file.

> Shall we just stop this now ?  I do like flames, but this is neither the
> place nor the person, cause I admire your work and flames like this can
> only end up badly.  And I have better threads to contribute to. So do you,
> undoubtedly.

You have better things to contribute?  Can't wait to see what.

> > Why would necessary instructions (how to run mythbackend) be way at the
> > end of the docs in section 21, 'Miscellaneous'?  That just doesn't make
> > sense at all.
>
> Hey, good question but don't look at me. I didn't write them.

Funnily enough, neither did I.

Isaac