greenstalk, that was a very thorough analysis, and you did raise valid points. I don't agree with your categorization of them, and it seems that people on the mythtv-users list were more interested in arguing than addressing the underlying problems. Not a lot we can do about that situation.
Xsecrets already explained which bugs are MythTV and which ones are KnoppMyth. I'll elaborate a little on ones I'm familiar with.
But first, let me suggest that in the future, you check to see if the place where you give your analysis is the right one before you post. Most of us on this forum could have told you what piece of software was responsible for what behavior. It really wasn't appropriate to send it all to the mythtv-users list. Ok, enough of that. Now here's my $0.02. If I don't comment on something, assume Xsecrets already said it for me
S-1) You're right - these values should be kept in sync. It is possible to address this in the KnoppMyth installer (which is not as broadly-defined as what you initially thought) by having it look at the actual partition size of /cache and set the MythTV's default ringbuffer size appropriately. It's actually really easy.
S-3) I think it uses default VESA settings to attempt broad coverage on a wide range of hardware. I recommend starting the install with the
Code:
screen 800x600
parameter. The default is 1024x768, but if you tell it 800x600, it'll set up X to run at that resolution instead. You can also try ctrl-alt-minus when X is going insane on your hardware, to reduce it to a usable resolution.
You're correct that the knoppix (or kanotix? cesman?) code that does this detection is not very specific to your monitor, even if it is plug&play. I often use a 1280x1024 LCD, and by default, it is set up as 1024x768, just like every other monitor - unless you specify the resolution. I looked at the code once, and it was not nearly as sophisticated as I thought.
CR-1) I agree with your sentiment (never surprise or confuse the user), but not the severity level.
CR-2) This could be addressed in KnoppMyth. It's straightforward to do, and it benefits debugging. But it's really not critical
A-3) Not an unreasonable request. It's easy to do, doesn't hurt people who don't need it, and helps people who do. (FYI, you can also launch an xterm with alt-X and run
Code:
KnoppMyth-run
in the shell.)
R-1) This is my bug. Basically, I
assumed that zap2it account information would always contain a usable zipcode, so I wrote scripting around that. Late in the release process, users reported errors downstream of my zipcode extraction code, and it turns out that for cable and satellite users, the 5-digit code in their account info isn't a zipcode at all. So I quickly put together an addition that would ask the user to enter a zipcode when a script asked for it and couldn't poll the zap2it account data for it. There was not enough time to make it only ask once, but it should cache it as you say and only ask once.
It's used for two things: download of channel icons, and mythweather locale. If you don't have a zipcode, you can just press enter. I don't think you can get non-US channel icons via mkiconmap.pl anyway, and you can set your mythweather locale manually as before. It would probably make sense to indicate this information in the prompt the user is given, of course
R-2) This type of thing is largely due to the fact that MythTV has its own messages that it gives you, and the KnoppMyth installer has its own. So if you see a GUI say "Now run mythfilldatabase" and then you happen to notice in a shell that it's running for you, you've witnessed a manual step in MythTV that was automated in KnoppMyth. There's no straightforward fix for it, unless the MythTV devs added a command-line parameter for mythtv-setup that would make it not say to run mythfilldatabase. It's unfortunate, since both MythTV and KnoppMyth are trying to be helpful here, and it causes a little confusion in the process.
R-6) If you need emacs before you have a network connection, download the source or binaries ahead of time, put them on a CD, and install them from CD. I'm a career-long emacs user, too, but I wouldn't advocate adding a 13MB package just in the event that someone who can't use vi or nano between the first post-install boot and first network connection needs to edit a file. You only need to learn a few keystrokes to use vi for trivial file editing, and you can print out a reference guide. ESC, x, i, a, o, dd, and :wq are your friends.
C-1) I agree - I don't like this theme either. It uses nice icons, but otherwise it's hard to use for reasons you described. But it is the default. (For Dragons, we use Iulius.) In any case, it's easy to change once you're running the frontend.
C-4) I'm maintaining this script now. Since it is text-based, how can we describe the differences between the gray remote and silver remote? I agree that either remote could look like either color to you if you don't have the other one handy for comparison.
When the script says it doesn't know how to handle a remote that's in the menu, this is our way of saying that we know people have the remote, but we don't have their config files and/or lspci data. You have to understand that the KnoppMyth developers do not have all possible hardware sitting around
We need people to contribute things like config files for their remotes.
C-5) If you do a channel scan, all your tunable channels should show up and be valid selections for starting channel. If you have a setup in which it makes sense to tune to channel 3, why didn't you feed the tuner card channel 3 during a channel scan?
I think the dialog here is correct, but I also think that a default channel should be selected for you, based on the channel scan. But that's for the MythTV developers, not us.
View unanswered posts
View active topics
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register
Dude, you've describe nothing about "MyhtTV Installer" in that thread. Issues w/ KnoppMyth should be posted here and NOT on the MythTV mailing list.