-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/25/2014 03:58 PM, Bill Nottingham wrote:
Stephen Gallagher (sgallagh(a)redhat.com) said:
>> === Display manager ===
>>
>> gdm will be used as the display manager. It is responsible for
>> showing a login screen on each seat. It will be able to
>> launch both X-based sessions and Wayland sessions.
>>
>> Desktop environments are expected to make themselves known as
>> an available session option on the login screen by dropping a
>> .desktop file into /usr/share/xsessions (or its wayland
>> equivalent).
>>
>> Other facilities provided by the display manager include screen
>> unlock authentication and user switching.
>>
>
>
> Display manager is irrelevant to the Server product.
Admittedly, this is rehashing a bit of an old discussion, but we
have (RHEL) stats that somewhere around 20% of server installs
install a desktop.
If Fedora Server wants to explicitly not serve those users, it's
worth noting specifically. If it wants to serve them by offering
some sort of environment that boots into just cockpit + terminal +
web browser, it's worth specifying the requirements there.
"7. The user must be able to install and manage Fedora Server in a
headless mode where the display framework is inactive." [1]
That being said, Cockpit itself has a terminal emulator built-in as
well. So ideally there's no reason to install a graphical environment
on the system. You should be able to just connect to it from any
browser and operate from there.
Also, I want to make it relatively easy for a Fedora Server install to
also essentially just "push a button" and also have a fully-functional
Workstation. That should be a non-default case.
[1]
https://fedoraproject.org/wiki/Server/Product_Requirements_Document#Use_C...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird -
http://www.enigmail.net/
iEYEARECAAYFAlMNBnIACgkQeiVVYja6o6OQSQCfd8WxqZBKMBiyriyq0siLFd8Y
6ScAn3V+xMkcv4D67bgnsD+zYa+TrLfx
=xIIB
-----END PGP SIGNATURE-----