On Tue, Aug 12, 2008 at 1:11 PM, Martin Langhoff <[EMAIL PROTECTED]> wrote: > #7708 - If you just install an XS, do the basic config (domain_config, > etc) and then install a new xs-config, the install mechanism makes a > mess. One tell-tale sign is that the files edited by domain_config are > overwritten. Diagnosing more later...
Done a clean XS install off 165, and about to update it. But I reviewed /etc and /var/named (which I know breaks) and I already have a diagnosis. First xs-config gets installed, and replaces files in /etc and /var/named with symlinks. Second, the sysadmin runs domain_config, and some of the scripts in domain_config run sed over symlinks in /etc instead of doing it dorectly against the _target_ in /fsroot.olpc.bla/. It's well known that sed -i (and perl -i, and anything that does the same job) breaks symlinks. Hmmm Hmm. So the damage is done not at upgrade time, but at domain_config time. So there's no easy/sane way I can fix it for already installed machines. Anyone who installed an XS will need to apply some manual steps to get the machine in a sane state after the next update. Working with a solution now - but I had hoped for a "quick fix" I could apply to ease the pain. No such. So I'm prob going to use the sysconfig trick to divert to a different config file, and update the domain_config machinery a bit to use templates. No easy path unfortunately :-/ cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff _______________________________________________ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
