Re: change of names of configuration files
- 元のメッセージ -
| Hi devels,
| I'd like to ask for your opinion, especially those from anaconda,
| system-config-* and localization. The last commit in systemd [1]
| changed
| names of configuration files. Does someone else than systemd tools
| using
| them? Fedora 18 is (or will be soon) in freeze, so it would be better
| solve it now.
I can see some files is referring /etc/sysconfig/i18n directly instead of
obtaining from /etc/profile.d/lang.{sh,csh}, at least in my box:
/etc/X11/prefdm:[ -f /etc/sysconfig/i18n ] . /etc/sysconfig/i18n
/etc/dracut.conf.d/01-dist.conf:i18n_vars=/etc/sysconfig/keyboard:KEYTABLE-KEYMAP
/etc/sysconfig/i18n:SYSFONT-FONT,FONTACM-FONT_MAP,FONT_UNIMAP
--
Akira TAGOH
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: change of names of configuration files
On Thu, 2012-10-25 at 23:50 -0400, Bill Nottingham wrote: Of course, in checking the code, anaconda for the moment is writing *both* files with identical data. Exactly. And the reason is that there are still tools working with the /etc/sysconfig/* files. Or aren't there? Believe me I'd be more than happy to remove the lines of code writing the old configuration files once they are really deprecated and not used by any tool. -- Vratislav Podzimek Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: change of names of configuration files
On Thu, 2012-10-25 at 15:39 +0200, Marcela Mašláňová wrote: Hi devels, I'd like to ask for your opinion, especially those from anaconda, system-config-* and localization. The last commit in systemd [1] changed names of configuration files. Does someone else than systemd tools using them? Fedora 18 is (or will be soon) in freeze, so it would be better solve it now. Situation with anaconda is simple here -- we just need to *be told* what files we should write the configuration to. I'm sorry, but I cannot (and won't) follow all systemd changes. The similar case is that systemd now don't default VConsole font to latarcyrheb-sun16 (see rhbz#869233). -- Vratislav Podzimek Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: change of names of configuration files
On 10/25/2012 03:39 PM, Marcela Mašláňová wrote: Hi devels, I'd like to ask for your opinion, especially those from anaconda, system-config-* and localization. The last commit in systemd [1] changed names of configuration files. Does someone else than systemd tools using them? Fedora 18 is (or will be soon) in freeze, so it would be better solve it now. snip +# Migrate /etc/sysconfig/i18n +if [ -e /etc/sysconfig/i18n -a ! -e /etc/locale.conf ]; then + unset LANG + . /etc/sysconfig/i18n 21 || : + [ -n $LANG ] echo LANG=$LANG /etc/locale.conf 21 || : +fi + +# Migrate /etc/sysconfig/keyboard +if [ -e /etc/sysconfig/keyboard -a ! -e /etc/vconsole.conf ]; then + unset SYSFONT + unset SYSFONTACM + unset UNIMAP + unset KEYMAP + [ -e /etc/sysconfig/i18n ] . /etc/sysconfig/i18n 21 || : + . /etc/sysconfig/keyboard 21 || : + [ -n $SYSFONT ] echo FONT=$SYSFONT /etc/vconsole.conf 21 || : + [ -n $SYSFONTACM ] echo FONT_MAP=$SYSFONTACM /etc/vconsole.conf 21 || : + [ -n $UNIMAP ] echo FONT_UNIMAP=$UNIMAP /etc/vconsole.conf 21 || : + [ -n $KEYTABLE ] echo KEYMAP=$KEYTABLE /etc/vconsole.conf 21 || : +fi +/usr/bin/rm -f /etc/sysconfig/i18n /dev/null 21 || : +/usr/bin/rm -f /etc/sysconfig/keyboard /dev/null 21 || : + +# Migrate HOSTNAME= from /etc/sysconfig/network +if [ -e /etc/sysconfig/network -a ! -e /etc/hostname ]; then + unset HOSTNAME + . /etc/sysconfig/network 21 || : + [ -n $HOSTNAME ] echo $HOSTNAME /etc/hostname 21 || : +fi +/usr/bin/sed -i '/HOSTNAME/d' /etc/sysconfig/network 21 || : + /snip [1] http://lists.fedoraproject.org/pipermail/scm-commits/2012-October/889150.html Thanks, Marcela I'm proposing revert for F-18. Let's do the change in rawhide. https://fedorahosted.org/fesco/ticket/963 If someone has metric how to find out, which packages are using the old configuration files, then please do a list. Thanks, Marcela -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: change of names of configuration files
On 10/26/2012 10:24 AM, Marcela Mašláňová wrote: I'm proposing revert for F-18. Let's do the change in rawhide. https://fedorahosted.org/fesco/ticket/963 Freeze has happened... .. Meeting summary --- .. * AGREED: Freeze now for Beta, stick to current schedule. -- JBG -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: change of names of configuration files
On Thu, Oct 25, 2012 at 03:39:27PM +0200, Marcela Mašláňová wrote: Hi devels, I'd like to ask for your opinion, especially those from anaconda, system-config-* and localization. The last commit in systemd [1] changed names of configuration files. Does someone else than systemd tools using them? Fedora 18 is (or will be soon) in freeze, so it would be better solve it now. libguestfs will both use and modify at least the HOSTNAME= field in /etc/sysconfig/network (although mitigating this, it also knows about /etc/hostname, but this path is not well tested and there may be bugs). I think it's extremely dumb to be changing configuration files at this point in the Fedora 18 development cycle. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones New in Fedora 11: Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 70 libraries supprt'd http://fedoraproject.org/wiki/MinGW http://www.annexia.org/fedora_mingw -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: change of names of configuration files
- Original Message - Hi devels, I'd like to ask for your opinion, especially those from anaconda, system-config-* and localization. The last commit in systemd [1] changed names of configuration files. Does someone else than systemd tools using them? Fedora 18 is (or will be soon) in freeze, so it would be better solve it now. It's definitely not a good time for such change, especially if someone depends on this change and hits freeze... Please, take a look how it affects your projects... Jaroslav -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: change of names of configuration files
Once upon a time, Jaroslav Reznik jrez...@redhat.com said: - Original Message - Hi devels, I'd like to ask for your opinion, especially those from anaconda, system-config-* and localization. The last commit in systemd [1] changed names of configuration files. Does someone else than systemd tools using them? Fedora 18 is (or will be soon) in freeze, so it would be better solve it now. It's definitely not a good time for such change, especially if someone depends on this change and hits freeze... Also, what is the justification for the changes? Arbitrarily moving things around is just useless churn. These settings have been in these files for a long time (I know I have scripts that pull the HOSTNAME variable from /etc/sysconfig/network). -- Chris Adams cmad...@hiwaay.net Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: change of names of configuration files
On Thu, Oct 25, 2012 at 03:39:27PM +0200, Marcela Mašláňová wrote: +# Migrate /etc/sysconfig/keyboard +if [ -e /etc/sysconfig/keyboard -a ! -e /etc/vconsole.conf ]; then Come to think of it, I suspect this one might explain why both Fedora 18 Fedora 19 recently have started to forget the local keyboard map, when entering the password in both gdm and the text console. [Sorry, no BZ for this. No idea what component it should be filed under.] You'll only notice this if your password contains characters like £/# which are sensitive to the locale. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://et.redhat.com/~rjones/virt-df/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: change of names of configuration files
On Thu, 2012-10-25 at 18:53 +0100, Richard W.M. Jones wrote: On Thu, Oct 25, 2012 at 03:39:27PM +0200, Marcela Mašláňová wrote: +# Migrate /etc/sysconfig/keyboard +if [ -e /etc/sysconfig/keyboard -a ! -e /etc/vconsole.conf ]; then Come to think of it, I suspect this one might explain why both Fedora 18 Fedora 19 recently have started to forget the local keyboard map, when entering the password in both gdm and the text console. [Sorry, no BZ for this. No idea what component it should be filed under.] You'll only notice this if your password contains characters like £/# which are sensitive to the locale. anaconda has been writing to vconsole.conf for some time now - at least Oct 4th: commit 4b98eab34f310c2704ec24b417bdf919c413fa1d Author: Vratislav Podzimek vpodz...@redhat.com Date: Thu Oct 4 12:37:24 2012 +0200 Work with VConsole keymap and X layouts separately ... Resolves: rhbz#853877 Resolves: rhbz#856362 Resolves: rhbz#859867 In fact we've always had problems with X and console keymaps; there's a longstanding bug about the encrypted partition case: https://bugzilla.redhat.com/show_bug.cgi?id=743281 It's a rather complex area. I don't have a 100% grasp on it, but I _think_ F18 actually behaves rather _better_ than previous releases at this point. I think Marcela's mail is slightly misleading. The 'new' locations for these files have existed and systemd has been using them for some time. The commit Marcela linked provided RPM scripts that automatically migrate to the new locations; it doesn't actually introduce the new locations. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: change of names of configuration files
Adam Williamson (awill...@redhat.com) said: anaconda has been writing to vconsole.conf for some time now - at least Oct 4th: commit 4b98eab34f310c2704ec24b417bdf919c413fa1d Author: Vratislav Podzimek vpodz...@redhat.com Date: Thu Oct 4 12:37:24 2012 +0200 Work with VConsole keymap and X layouts separately ... Resolves: rhbz#853877 Resolves: rhbz#856362 Resolves: rhbz#859867 In fact we've always had problems with X and console keymaps; there's a longstanding bug about the encrypted partition case: https://bugzilla.redhat.com/show_bug.cgi?id=743281 It's a rather complex area. I don't have a 100% grasp on it, but I _think_ F18 actually behaves rather _better_ than previous releases at this point. I think Marcela's mail is slightly misleading. The 'new' locations for these files have existed and systemd has been using them for some time. The commit Marcela linked provided RPM scripts that automatically migrate to the new locations; it doesn't actually introduce the new locations. Right. Since F16 when systemd took over the basic startup of the system, it's had to set things like: - keymap - font - locale - hostname etc. It's always had the policy where it reads a heirarchy of locations for these settings: 1. the kernel commandline 2. a cross-distro default location 3. a distro specific location (for example, /etc/sysconfig/i18n on Fedora-alike, /etc/sysconfig/language on SuSe, /etc/rc.conf on Arch... it's a large pile of #ifdefs, and it's why there is a cross-distro default location suggested) In each case, the later location overrides the former. (Except for hostname ... I'll go file that one.) Options would be: 1. ignore the cross-distro locations, never use them, patch them out where they occur 2. ignore the distro-specific locations, never use them, patch them out where they occur (hooray, flag day!) 3. Accept both. Deal with confusion if people have both files present. 4. Attempt to patch everything to only support one variant, but allow for the other where available. Fedora's done #3, and has done so since F-16. We get the occasional bug from this, usually when someone's used one tool that writes a config to one file location, and another that assumes another. That's not a good long term solution, so discussion was to take what format anaconda is writing for new installs, and convert old installs to that format, so that upgraded systems match (all the while while the old location still works for those that modify their configs by hand, or with old tools.) Of course, in checking the code, anaconda for the moment is writing *both* files with identical data. Bill -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
