What changes to do in `/etc/gdm/custom.conf` after getting a new pacnew file?

Support System Updates
1

I have the following in \etc\gdm\custom.conf :

# GDM configuration storage

[daemon]
AutomaticLoginEnable=False

[security]

[xdmcp]

[chooser]

[debug]
# Uncomment the line below to turn on debugging
#Enable=true

And I the following in \etc\gdm\custom.conf.pacnew :

# GDM configuration storage

[daemon]

[security]

[debug]
# Uncomment the line below to turn on debugging
#Enable=true

What changes should I make to the non-pacnew file before removing the pacnew file?

2

Hi @michael-novak,

Note that I don’t like, don’t use and don’t care about Gnome. So there is a chance that I’m wrong, however small it might be.

If you’re certain that you haven’t changed anything in the .conf file, it should theoretically be safe to just replace it with the .pacnew file.

Otherwise, ensure that all the changes you’ve made are present in the .pacnew file, it’s saved and then replace the .conf file with it.

However, I think working through these, and understanding them is crucial:

3

I ask!
Isn’t this \etc\gdm\custom.conf.pacnew file created because you enabled automatic login?

4

None. In this case, you can delete the .pacnew. It’s only a template.

UNIX uses forward slashes as directory delimiters in paths, not backslashes. That’s an MS-DOS thing, because MS-DOS — which was actually an illegal 16-bit rewrite of CP/M — was already using forward slashes for command options before the FAT filesystem even supported directories.

In UNIX, a backslash is an escape character, for indicating that the special character following next — e.g. a space, a tab, a colon, a single or double quote, a newline, et al — must be interpreted as a literal character.

3 Likes
5

Thank you very much!

1 Like