> As for clock, I think you didn't get my point. I don't complain about > what installed system thought of my clock (whether they were set to > UTC or local time). I just want to say that hardware clock must have > not been changed in any case without reliable response from NTP > server. Debian has to show local time according to selected timezone > and UTC setting in /etc/default/rcS, but it doesn't have to touch hw > clock at all when hw clock is the only more or less reliable time > source. Well, D-I actually doesn't use any NTP server. So, if somethign bad happened with some NTP stuff changing your hw clock, I'm afraid that the bug doesn't belgon to D-I. > Right. > > >For Russian, console-cyrillic should be installed. > > I know about this package, but shouldn't it be installed automatically > by D-I if I select Russian key-map then? Nope. It is installed if you choose Russian as language. But, as another recent thread did show, there are some glitches with this as the localechooser fnish-install script seems to overwrite console-cyrillic settings. > >> I have various USB devices connected to my PC. Logs about some of them > >> always appear after "bor login:" prompt. Looks very unprofessional > >> although I'm used to unexpected Linux kernel messages on the console. > > > >This has nothing to do with the installer, I'm afraid. BTW, I also > >don't like Linux kernel messages at the console. Probably something to > >set in syslog stuff, which I never succeeded to find. I agree this is > >pretty annoying. > > http://www.debian.org/doc/manuals/reference/ch-tips.en.html#s8.6.8 > But IMO users should not bother about such things. Thanks for pointing me to this...:-)....this shows that even more than 10 years of Debian use means that one still has things to learn..:-) If you actually do not agree with the default settings of klogd, I suggest you report the bug to the klogd package. The decision of changing that setting belongs to the klogd maintainer. Anyway, thanks, again, as I was seeking for that information for a while..:-) > >All the remaining does not really belong to the installer and should > >be reported against the relevant packages..... > > Well, D-I is D-I itself + the integration of various packages, and I > think D-I team should pay attention to the smoothness of this > integration and the final result. D-I + installed system is the first Sure, in an idealistic world. But we even don't have the needed manpower to process issues that really pertain to the installer so, except when issues are obviously identifiable (see above), we cannot really make the very hard work of analyzing all install reports to dispatch issues. Sorry for that. Just see the bugs reported to "installation-reports" to get a picture..:-) > BTW, who decides what packages are included on netinst CD? The maintainers of these package, by making them part of the base system. Of course, the Debian policy has strict requirements for a package to be part of the base system. > >> I believe average non-technical PC users had no chances to overcome this > >> major obstacle of conecting Debian to the Internet via USB ADSL modem. > > What could be done here? eciadsl (is this the only available package > for USB DSL modems?) + pppoe + dependencies should be included on > netinst CD. eciadsl documentation should be improved, and D-I should > detect DSL modems automatically. Ideally, (from the user's point of > view), all firmware and other binaries for the package should be > included as well, so that Internet connection could be set-up during > the installation without the need to manually download packages from > foreign sites. I know this is controversial topic, which is currently > discussed on some Debian mailing list. Yep. A lot...:-) About USB DSL stuff, I have no clues. My only experience is that most of these bloody USB DSL modems require bloody firmware to be loaded, which is usually non free stuff...:-(. > >> I wish I could configure console "beep" sound during installation so > >> that my wife didn't get angry about "beeping" through filesystem at 2am, > >> and I needn't look for 2 year old notes with magic escape sequnces for > >> the "beep". > > >From my point of view these basic issues should be handled during the > installation. Who else but D-I team should take care of these? When > the whole system is being installed I don't know what exact packages > provide what functionality. So for me as a user any issue not directly > associated (in my mind) with particular package looks like > distribution flaw. And if the number of such issues reaches some > critical mass, a user will choose to try different distribution > instead of spending time on filling numerous bug reports. Maybe..:-). The difference in Debian is that cllued users can help to solve out these usability issues. I have indeed no idea about the Right Way to enable/disable the console beep. This is probably done in the user's environment...so disabling it for the created user would indeed mean that the deault environment for users should have the console beep disabled. Is this likely? I'm not completely sure but I bet that many would disagree. --
Attachment:
signature.asc
Description: Digital signature