cc: anaconda-devel@
From today's Fedora QA minutes https://meetbot.fedoraproject.org/fedora-meeting/2022-01-24/fedora-qa.2022-0...
16:20:54 <pboy> I'll test that again, but I'm sure, if you use everything DVD you get the wrong preconfiguration. We had a thread about that on server list.
I'm not finding this thread. But Adamw surely knows the history of Everything ISO better than I do. My fuzzy memory is that it's sort of a side effect of how images are made and it's kept around as a catch all. It's the only way to do a netinstall for any of the desktops. The default package set is for a minimal install, a.k.a. Fedora Custom. The idea is to make it straightforward to get a minimum bootable system and then use dnf to build it up from there.
Just for context, "Everything ISO" e.g. https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220124.n...
This image defines "automatic" partitioning as btrfs. It's intrinsic to the image itself what the partitioning defaults to. It's not a function of the package set, i.e. choosing the Server package set doesn't get you Server's default partitioning. It's a little confusing, but it's working as designed, insofar as it has one.
I cc'd Anaconda folks, because I'm not sure exactly where the "autopart" kickstart command gets defined these days. And also whether it's worth the effort to make autopart variable based on what edition or spin is selected in the Everything netinstaller? I'm not sure that it is.
Am 24.01.2022 um 18:42 schrieb Chris Murphy lists@colorremedies.com:
cc: anaconda-devel@
From today's Fedora QA minutes https://meetbot.fedoraproject.org/fedora-meeting/2022-01-24/fedora-qa.2022-0...
16:20:54 <pboy> I'll test that again, but I'm sure, if you use everything DVD you get the wrong preconfiguration. We had a thread about that on server list.
I'm not finding this thread. But Adamw surely knows the history of Everything ISO better than I do. My fuzzy memory is that it's sort of a side effect of how images are made and it's kept around as a catch all. It's the only way to do a netinstall for any of the desktops. The default package set is for a minimal install, a.k.a. Fedora Custom. The idea is to make it straightforward to get a minimum bootable system and then use dnf to build it up from there.
Just for context, "Everything ISO" e.g. https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220124.n...
This image defines "automatic" partitioning as btrfs. It's intrinsic to the image itself what the partitioning defaults to. It's not a function of the package set, i.e. choosing the Server package set doesn't get you Server's default partitioning. It's a little confusing, but it's working as designed, insofar as it has one.
I cc'd Anaconda folks, because I'm not sure exactly where the "autopart" kickstart command gets defined these days. And also whether it's worth the effort to make autopart variable based on what edition or spin is selected in the Everything netinstaller? I'm not sure that it is.
Chris,
if I remember correctly, wasn’t it you who informed me (about a year ago in the context of F32/33) that booting from everything DVD and select „Fedora Server“ does not result in an identical installation as booting from Server DVD and selecting „Fedora Server“? (when I wondered about the installation on a rented remote hardware where only „Everything“ was available).
Anyway, no case to worry at the current status, I think. I will test this more closely. At the moment I am still completing and refining my dedicated server test environment.
Besides the question about the boot medium and group selection, the January 18 build has still the issue with /etc/resolv.conf being a file instead of a link (and thus breaking split DNS). The bug is marked as resolved (in December/January according to Adam), maybe the build was made just before that became effective. We have to keep this in mind.
Best Peter
On Mon, Jan 24, 2022 at 1:46 PM Peter Boy pboy@uni-bremen.de wrote:
Am 24.01.2022 um 18:42 schrieb Chris Murphy lists@colorremedies.com:
cc: anaconda-devel@
From today's Fedora QA minutes https://meetbot.fedoraproject.org/fedora-meeting/2022-01-24/fedora-qa.2022-0...
16:20:54 <pboy> I'll test that again, but I'm sure, if you use everything DVD you get the wrong preconfiguration. We had a thread about that on server list.
I'm not finding this thread. But Adamw surely knows the history of Everything ISO better than I do. My fuzzy memory is that it's sort of a side effect of how images are made and it's kept around as a catch all. It's the only way to do a netinstall for any of the desktops. The default package set is for a minimal install, a.k.a. Fedora Custom. The idea is to make it straightforward to get a minimum bootable system and then use dnf to build it up from there.
Just for context, "Everything ISO" e.g. https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220124.n...
This image defines "automatic" partitioning as btrfs. It's intrinsic to the image itself what the partitioning defaults to. It's not a function of the package set, i.e. choosing the Server package set doesn't get you Server's default partitioning. It's a little confusing, but it's working as designed, insofar as it has one.
I cc'd Anaconda folks, because I'm not sure exactly where the "autopart" kickstart command gets defined these days. And also whether it's worth the effort to make autopart variable based on what edition or spin is selected in the Everything netinstaller? I'm not sure that it is.
Chris,
if I remember correctly, wasn’t it you who informed me (about a year ago in the context of F32/33) that booting from everything DVD and select „Fedora Server“ does not result in an identical installation as booting from Server DVD and selecting „Fedora Server“? (when I wondered about the installation on a rented remote hardware where only „Everything“ was available).
That's a different case. That's referring to the package collection. The Everything ISO has the base Fedora "profile" that most variants use (which uses Btrfs). But it also doesn't select Fedora Server by default and is explicitly designed "for experts", The Fedora Server netinstall ISO uses the Fedora Server "profile" and will use the Fedora Server settings by default, including using LVM+XFS.
Think of the Everything ISO as something that an Arch convert would use, while the Fedora Server netinstall ISO would be something that a sysadmin doing server deployments from a central repo mirror would use.
Dne 24. 01. 22 v 20:20 Neal Gompa napsal(a):
On Mon, Jan 24, 2022 at 1:46 PM Peter Boy pboy@uni-bremen.de wrote:
Am 24.01.2022 um 18:42 schrieb Chris Murphy lists@colorremedies.com:
cc: anaconda-devel@
From today's Fedora QA minutes https://meetbot.fedoraproject.org/fedora-meeting/2022-01-24/fedora-qa.2022-0...
16:20:54 <pboy> I'll test that again, but I'm sure, if you use everything DVD you get the wrong preconfiguration. We had a thread about that on server list.
I'm not finding this thread. But Adamw surely knows the history of Everything ISO better than I do. My fuzzy memory is that it's sort of a side effect of how images are made and it's kept around as a catch all. It's the only way to do a netinstall for any of the desktops. The default package set is for a minimal install, a.k.a. Fedora Custom. The idea is to make it straightforward to get a minimum bootable system and then use dnf to build it up from there.
Just for context, "Everything ISO" e.g. https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220124.n...
This image defines "automatic" partitioning as btrfs. It's intrinsic to the image itself what the partitioning defaults to. It's not a function of the package set, i.e. choosing the Server package set doesn't get you Server's default partitioning. It's a little confusing, but it's working as designed, insofar as it has one.
I cc'd Anaconda folks, because I'm not sure exactly where the "autopart" kickstart command gets defined these days. And also whether it's worth the effort to make autopart variable based on what edition or spin is selected in the Everything netinstaller? I'm not sure that it is.
Chris,
if I remember correctly, wasn’t it you who informed me (about a year ago in the context of F32/33) that booting from everything DVD and select „Fedora Server“ does not result in an identical installation as booting from Server DVD and selecting „Fedora Server“? (when I wondered about the installation on a rented remote hardware where only „Everything“ was available).
That's a different case. That's referring to the package collection. The Everything ISO has the base Fedora "profile" that most variants use (which uses Btrfs). But it also doesn't select Fedora Server by default and is explicitly designed "for experts", The Fedora Server netinstall ISO uses the Fedora Server "profile" and will use the Fedora Server settings by default, including using LVM+XFS.
Think of the Everything ISO as something that an Arch convert would use, while the Fedora Server netinstall ISO would be something that a sysadmin doing server deployments from a central repo mirror would use.
Hi,
Yes, it's as Neal said. Basically Anaconda is now using configuration profiles which are matching the /etc/os-release values.
https://github.com/rhinstaller/anaconda/blob/master/data/profile.d/fedora-se...
If there is a match we will choose that configuration file. Not sure what the Everything ISO has there. However, it's possible that it is matching the base Fedora configuration file:
https://github.com/rhinstaller/anaconda/blob/master/data/profile.d/fedora.co... where you can find the default_scheme: https://github.com/rhinstaller/anaconda/blob/master/data/profile.d/fedora.co...
Best Regards, Jirka
On Tue, Jan 25, 2022 at 10:34 AM Jiri Konecny jkonecny@redhat.com wrote:
Dne 24. 01. 22 v 20:20 Neal Gompa napsal(a):
On Mon, Jan 24, 2022 at 1:46 PM Peter Boy pboy@uni-bremen.de wrote:
Am 24.01.2022 um 18:42 schrieb Chris Murphy lists@colorremedies.com:
cc: anaconda-devel@
From today's Fedora QA minutes
https://meetbot.fedoraproject.org/fedora-meeting/2022-01-24/fedora-qa.2022-0...
16:20:54 <pboy> I'll test that again, but I'm sure, if you use everything DVD you get the wrong preconfiguration. We had a thread about that on server list.
I'm not finding this thread. But Adamw surely knows the history of Everything ISO better than I do. My fuzzy memory is that it's sort of a side effect of how images are made and it's kept around as a catch all. It's the only way to do a netinstall for any of the desktops. The default package set is for a minimal install, a.k.a. Fedora Custom. The idea is to make it straightforward to get a minimum bootable system and then use dnf to build it up from there.
Just for context, "Everything ISO" e.g.
https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220124.n...
This image defines "automatic" partitioning as btrfs. It's intrinsic to the image itself what the partitioning defaults to. It's not a function of the package set, i.e. choosing the Server package set doesn't get you Server's default partitioning. It's a little confusing, but it's working as designed, insofar as it has one.
I cc'd Anaconda folks, because I'm not sure exactly where the "autopart" kickstart command gets defined these days. And also whether it's worth the effort to make autopart variable based on what edition or spin is selected in the Everything netinstaller? I'm not sure that it is.
Chris,
if I remember correctly, wasn’t it you who informed me (about a year
ago in the context of F32/33) that booting from everything DVD and select „Fedora Server“ does not result in an identical installation as booting from Server DVD and selecting „Fedora Server“? (when I wondered about the installation on a rented remote hardware where only „Everything“ was available).
That's a different case. That's referring to the package collection. The Everything ISO has the base Fedora "profile" that most variants use (which uses Btrfs). But it also doesn't select Fedora Server by default and is explicitly designed "for experts", The Fedora Server netinstall ISO uses the Fedora Server "profile" and will use the Fedora Server settings by default, including using LVM+XFS.
Think of the Everything ISO as something that an Arch convert would use, while the Fedora Server netinstall ISO would be something that a sysadmin doing server deployments from a central repo mirror would use.
Hi,
Yes, it's as Neal said. Basically Anaconda is now using configuration profiles which are matching the /etc/os-release values.
https://github.com/rhinstaller/anaconda/blob/master/data/profile.d/fedora-se...
If there is a match we will choose that configuration file. Not sure what the Everything ISO has there. However, it's possible that it is matching the base Fedora configuration file:
https://github.com/rhinstaller/anaconda/blob/master/data/profile.d/fedora.co... where you can find the default_scheme:
https://github.com/rhinstaller/anaconda/blob/master/data/profile.d/fedora.co...
Btw. the issue with changing profiles based on the packages selection was already discussed here: https://bugzilla.redhat.com/show_bug.cgi?id=2002668
I still think that the best approach would be to extend the boot menu of the Everything ISO as mentioned at: https://bugzilla.redhat.com/show_bug.cgi?id=2002668#c1
The Anaconda profiles are documented here: https://anaconda-installer.readthedocs.io/en/latest/configuration-files.html...
Best Regards, Jirka _______________________________________________ Anaconda-devel mailing list -- anaconda-devel@lists.fedoraproject.org To unsubscribe send an email to anaconda-devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/anaconda-devel@lists.fedorapro... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On Tue, Jan 25, 2022 at 6:47 AM Vendula Poncova vponcova@redhat.com wrote:
On Tue, Jan 25, 2022 at 10:34 AM Jiri Konecny jkonecny@redhat.com wrote:
Dne 24. 01. 22 v 20:20 Neal Gompa napsal(a):
On Mon, Jan 24, 2022 at 1:46 PM Peter Boy pboy@uni-bremen.de wrote:
Am 24.01.2022 um 18:42 schrieb Chris Murphy lists@colorremedies.com:
cc: anaconda-devel@
From today's Fedora QA minutes https://meetbot.fedoraproject.org/fedora-meeting/2022-01-24/fedora-qa.2022-0...
16:20:54 <pboy> I'll test that again, but I'm sure, if you use everything DVD you get the wrong preconfiguration. We had a thread about that on server list.
I'm not finding this thread. But Adamw surely knows the history of Everything ISO better than I do. My fuzzy memory is that it's sort of a side effect of how images are made and it's kept around as a catch all. It's the only way to do a netinstall for any of the desktops. The default package set is for a minimal install, a.k.a. Fedora Custom. The idea is to make it straightforward to get a minimum bootable system and then use dnf to build it up from there.
Just for context, "Everything ISO" e.g. https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220124.n...
This image defines "automatic" partitioning as btrfs. It's intrinsic to the image itself what the partitioning defaults to. It's not a function of the package set, i.e. choosing the Server package set doesn't get you Server's default partitioning. It's a little confusing, but it's working as designed, insofar as it has one.
I cc'd Anaconda folks, because I'm not sure exactly where the "autopart" kickstart command gets defined these days. And also whether it's worth the effort to make autopart variable based on what edition or spin is selected in the Everything netinstaller? I'm not sure that it is.
Chris,
if I remember correctly, wasn’t it you who informed me (about a year ago in the context of F32/33) that booting from everything DVD and select „Fedora Server“ does not result in an identical installation as booting from Server DVD and selecting „Fedora Server“? (when I wondered about the installation on a rented remote hardware where only „Everything“ was available).
That's a different case. That's referring to the package collection. The Everything ISO has the base Fedora "profile" that most variants use (which uses Btrfs). But it also doesn't select Fedora Server by default and is explicitly designed "for experts", The Fedora Server netinstall ISO uses the Fedora Server "profile" and will use the Fedora Server settings by default, including using LVM+XFS.
Think of the Everything ISO as something that an Arch convert would use, while the Fedora Server netinstall ISO would be something that a sysadmin doing server deployments from a central repo mirror would use.
Hi,
Yes, it's as Neal said. Basically Anaconda is now using configuration profiles which are matching the /etc/os-release values.
https://github.com/rhinstaller/anaconda/blob/master/data/profile.d/fedora-se...
If there is a match we will choose that configuration file. Not sure what the Everything ISO has there. However, it's possible that it is matching the base Fedora configuration file:
https://github.com/rhinstaller/anaconda/blob/master/data/profile.d/fedora.co... where you can find the default_scheme: https://github.com/rhinstaller/anaconda/blob/master/data/profile.d/fedora.co...
Btw. the issue with changing profiles based on the packages selection was already discussed here: https://bugzilla.redhat.com/show_bug.cgi?id=2002668
I still think that the best approach would be to extend the boot menu of the Everything ISO as mentioned at: https://bugzilla.redhat.com/show_bug.cgi?id=2002668#c1
The Anaconda profiles are documented here: https://anaconda-installer.readthedocs.io/en/latest/configuration-files.html...
Would it be possible to add the ability to define partitioning schemes per scheme? For example, with Btrfs on Fedora Server, having a subvolume for /home is sensible, but with the other arrangements that divide up space, probably not. For RPM-OSTree systems (Kinoite/Silverblue), we'd like to have a /var subvolume in addition to /home, but not when plain partitions or LVM is used.
anaconda-devel@lists.stg.fedoraproject.org
-
Chris Murphy -
Jiri Konecny -
Neal Gompa -
Peter Boy -
Vendula Poncova