1. I can’t change timezone! It starts as US/Pacific. I choose Europe/Stockholm and choose Yes to "do you want to SET…". I get two error lines (which I can’t see since they flashes by too fast), and the timezone is still set to US/Pacific.

It _did_ work when I tried yesterday, but it does not today. (Both times doing auto installation)


2. In the "Do you wish to SET…" screen, it says Universal: 3.30, Local: 4.30. That’s wrong, it should say Local: 9.30. (I’m not sure which timezone UTC is though)

Is this read from NTP, of from the local clock?

Its reading the local clock. You say it won't set the tz during an auto install ?

That's right, I choose <Y>es but it's still set to US/Pacific. I'm getting some error, but it goes away to fast for me to read it.

I've managed to read the error now, it's
/usr/local/bin/KnoppMyth-tz: line 122: /etc/timezone: read-only filesystem.

Since this step is done before partitioning/formating etc, /etc is on the CD, right? So of course it's read-only. Is the timezone thing suppose to be done after the formating, or should /etc be a ram drive, or what...?

I had the same problem during the installation, and yes since it is on the CD, it doesn't change the timezone. But after rebooting and removing the KnoppMyth CD, it asks you again and then it takes.

also if you are completely through the install you can always run Knoppmyth-tz from a root prompt and it will run that script agian.

Why does it ask for timezone when it needs to ask again after a reboot? Sounds odd to me...

root@stevo:/# Knoppmyth-tz
bash: Knoppmyth-tz: command not found

Steve

_________________
-Howski
-------------------
Knoppmyth R5A16
Soyo Dragon KT400 Black Edition
Athlon XP 2400+ (2001MHz)
512MB SDRAM
nVidia GeForce4 5200 64MB
Hauppauge WinTV-PVR350
Hauppauge WinTV-PVR250

Just for practice

_________________
R5F1 - Dell P4 2.4Ghz 500MB - PVR250 x 2 - GeForce FX 5200 - Onboard sound/NIC 80GB ATA/250GB ATA/400GB SATA

KnoppMyth-tz, not Knoppmyth-tz or knoppmyth-tz

This really is a nusciance and a cause of confusion. There is about 1 new post per day from someone with a problem caused by this.

well as soon as you can figure out how to fix the script I'm sure the developers would be happy to include your improvements.

I can think of a number of approaches...

The one that's the most obvious is for the init scripts on the cd to make a ramdisk, copy /etc into it, and mount that over the existing /etc. The only problem is that it'll take a fair chunk of RAM. On my Mandrake box here at work du -k /etc shows about 32Mb of stuff. Obviously various types of cleverness are possible to reduce the memory footprint (have /etc which is a symlink farm and /real_etc which contains most of the files, ...)

You could wait on setting the time until (or rerun it) after the copy to disk has been done and mount /etc from the HD before doing it... Running it when it's not going to work isn't very useful anyway...

Another aproach is to make setting the time/TZ an early interaction in the init scripts, after the root FS is mounted but before any of the servers are brought up. To avoid being annoying make it conditional on the existance of a file (e.g. - /etc/never_been_kissed) which you can't delete from the CD ('cause it's RO) but you can delete from /etc. That way the servers don't come up with a bad time/TZ on the first HD boot.

One of the few advantages to being old and having an nasty twisty mind is being on a first name basis with most of the dirty tricks, evil hacks, and weird work-arounds out there.

yes these are all great ideas, but the fact still remains someone has to write the code, which seems to be the problem here. Not that the code or process is too difficult to figure out, just that noone has or has made the time to do it.

First on my list is to get together a complete step by step write up of how to do an install or upgrade with TV-Out getting this right in the process and get that posted. Then I can start thinking about putting the research time in to learn enough about the mechanisms used in vanilla Knoppix and how KnoppMyth differs, and a variety of debian issues (KnoppMyth is my first debian based distro), and ...

OBTW - No fair shifting the ground, all you said the first time was "figure out how" not "do it" or "write the code".