The following proposal comes out of the discussion at this weeks Server SIG
meeting[1]
Fedora Server will have:
* / (root) will be a minimum of 2 GiB and a maximum of 15 GiB
* SWAP will continue to be calculated automatically based on available RAM on
the system
* All unused space will be assigned to a volume group and available to be
assigned to new partitions or extend existing partitions.
* Anaconda will continue to handle the appropriate EFI and /boot settings
We also discussed during the meeting whether we should have a separate /var
partition by default, but the general sense was that we might be better served
by developing a mechanism to allow partitions to be split from existing mount
points, which would be more flexible going forward.
As we did not have quorum in the meeting by the point we got to this proposal,
I'm taking it to the list for discussion and votes.
For the record, the current behavior of the partitioning scheme is for / to be
given up to 50 GiB of space and then any remaining space after that is assigned
to a separate /home partition.
[1]
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-03-15/serversig.201…
Dear all,
Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 30
Release Readiness meeting. This meeting will be held on Thursday,
2018-04-25 at 19:00 UTC.
We will meet to make sure we are coordinated and ready for the release
of Fedora 30. Please note that this meeting will be held even if the
release is delayed at the Go/No-Go meeting on the same day two hours
earlier.
You may receive this message several times in order to open this
meeting to the teams and to raise awareness, so hopefully more team
representatives will come to this meeting. This meeting works best
when we have representatives from all of the teams.
For more information, see
https://fedoraproject.org/wiki/Release_Readiness_Meetings.
View the meeting on Fedocal:
https://apps.fedoraproject.org/calendar/meeting/9514/?from_date=2019-04-22
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
Pronouns: he/him
Hi,
I ran into this "fun" hack
https://news.ycombinator.com/item?id=19642554 and I'm wondering
whether it'd be a good idea for F31 to ship with:
#AllowAgentForwarding no
#PasswordAuthentication no
Cockpit provides an interface to add SSH public keys for a while now.
However the installer doesn't require creation of an admin user, it's
an option.
Related to that, I'd like to see the installer:
a. Require creation of a non-root user with "Make this user
administrator" checked by default
b. Root user has "Lock root account" checked by default
When I check "lock root account" and return to the installation
overview, it shows for root user that logins are disabled, so it's not
like the person doing the install has to go dig around for the fact
root user will be disabled. And they can easily uncheck it and set a
password.
Any thoughts?
--
Chris Murphy