#6 create a minimal build profile
Merged a year ago by ngompa. Opened a year ago by leifliddy.
Unknown source minimal  into  rawhide

file modified
+1
@@ -21,6 +21,7 @@

  	<include from="this://./components/base.xml"/>

  	<include from="this://./components/desktop-environments.xml"/>

  	<include from="this://./components/users.xml"/>

+ 	<include from="this://./platforms/minimal.xml"/>

  	<include from="this://./platforms/server.xml"/>

  	<include from="this://./platforms/workstation.xml"/>

  	<packages type="bootstrap">

@@ -0,0 +1,20 @@

+ <image>

+ 	<profiles>

+ 		<profile name="minimal" description="Minimal Environment">

+ 			<requires profile="BootCore"/>

+ 			<requires profile="Common"/>

+ 		</profile>

+ 	</profiles>

+ 	<preferences profiles="minimal">

+ 		<type image="oem" filesystem="btrfs" kernelcmdline="scsi_mod.use_blk_mq=1 multipath=off" target_blocksize="4096" bootpartition="true" bootpartsize="1000" bootfilesystem="ext4" efipartsize="500" firmware="uefi" fsmountoptions="x-systemd.growfs,compress=zstd:1">

+ 			<bootloader name="grub2" console="console" timeout="5" timeout_style="hidden"/>

+ 			<systemdisk name="fedora">

+ 				<volume name="home"/>

+ 				<volume name="root"/>

+ 			</systemdisk>

+ 			<oemconfig>

+ 				<oem-resize>false</oem-resize>

+ 			</oemconfig>

+ 		</type>

+ 	</preferences>

+ </image>

This will:

  1. allow developers to quickly test the build process
  2. give users the option of installing a minimalistic environment

Some packages have been included in this profile for convenience purposes.

While others I should probably explain:
light - to allow users to control the screen and keyboard backlight from the command line.

net-tools - I'll probably get my hand slapped for this, but there's a fair amount of people who
like using ifconfig to view (not set) the interface config info

alsa-ucm-asahi - although not really needed for a minimal env, we include this so
that users won't have to remember to install it later on.

Preferences:
* use that standard Fedora behavior of creating an /xfs boot partition

Bootloader:
* use the standard Fedora grub behavior of timeout=5 and timeout_style="hidden"

I'd rather not have net-tools on here. As for the rest of the packages, why not just put them in the Common profile?

Your minimal profile can just source BootCore and Common profiles and be done with it.

As for the boot partition, the actual default for /boot should remain ext4. It's only xfs for Fedora Server simply to validate that combination for Fedora Server.

As for the bootloader settings, those probably make sense for all platforms.

rebased onto 6e7f935d31047af112925ad9fd233b4973f3b96d

a year ago

> Your minimal profile can just source BootCore and Common profiles and be done with it.
The goal was to find a balance between minimal and functional and I didn't think I needed every package from Standard.

> As for the boot partition, the actual default for /boot should remain ext4.
So only way (that I've found) to install a minimal environment via Fedora-provided media is with the (Fedora server) netinstall iso. And when you install the minimal environment, it creates an xfs /boot partition by default.
So I've always linked the two together.

> As for the bootloader settings, those probably make sense for all platforms.
Sure, I'll do another PR for that.

I'll make the above changes.

As for the boot partition, the actual default for /boot should remain ext4.

So only way (that I've found) to install a minimal environment via Fedora-provided media is with the (Fedora server) netinstall iso. And when you install the minimal environment, it creates an xfs /boot partition by default.
So I've always linked the two together.

The "Everything" ISO on alt.fedoraproject.org is the actual netinstall ISO. Fedora Server wanted a branded netinstall ISO, so they have one. Workstation used to have one too, but they chose to stop supporting one.

1 new commit added

  • rework minimal profile
a year ago

reworked minimal.xml to install Common profille (from base.xml)

base.xml is installing two groups: core + standard
The minimal profile is only profile really using that as all the other profiles will install those two groups via their (higher-level) groups.
I removed hardware-support as I would like for the minimal group to remain...well minimal (the other profiles will install hardware-support via their groups)
I not a fan of installing the Standard group in it's entirety as it makes the image a bit too big for my taste. But these are just minor gripes. It does achieve the purpose of creating a relatively small-footprint build, and that was the whole point of this. Should be good to go!

Please don't remove this.

I removed hardware-support as I would like for the minimal group to remain...well minimal (the other profiles will install hardware-support via their groups)

This only makes sense if we weren't installing on bare metal. As these are bare metal images, I'd rather keep it.

The default packages in the hardware-support group are all firmware packages that don't pertain to this hardware though. But no worries, I'll re-add it.

1 new commit added

  • re-added hardware-support group
a year ago

Can you squash your commits?

This is using spaces instead of tabs here...

1 new commit added

  • corrected minor formatting issue
a year ago

rebased onto f611badfbed62003cf2eb91e3b6442b200883f40

a year ago

The requested changes have been made. Can I merge this?

rebased onto d569746

a year ago

Pull-Request has been merged by ngompa

a year ago
Metadata