Only example by Fedora is in French. Unfortunately I do not read French:
(Is there a way to translate the whole French Topic to English ?)
I haven’t search the entire internet but it is always better for gaining the exact knowledge when reaching after a hand in herehttps://discussion.fedoraproject.org/ before doing properly mistakes by non Fedora forums which are good for other tasks.
I do not find it searching the help guide or the forum.
On this machine Asus G75 I have 1 TB SSD and have used 20 % of the storage. As I experimenting and learning by installing and trying out a lot of apps I’m not know or do not need but not are able to clean up by uninstallation. It not a proper measurement as I gained a lesser experience than when this Fedora OS was installed.
The link you posted explains a lot but I’m not sure how much space I need yet. I do not going to build Virtual machine or VNC which uses a lot of capasity as I understood reading the link you posted.
I will mostly use it for having few necessary apps. As a former guy helped me downgrade the Mac OS version. I’m not shure the trust level of this guy and which software he installed. I use the mac os for Ableton and Rekordbox mostly to DJ and create music as Mac is very stable according to plugins and sound drivers. (I’m not there yet with Linux and Big Wig ). That needs a lot space and as it is an old processer it take a lot of processor force. But as imagine would I like to switch to Fedora in the bootmode and running apps like Wireshark or do some serious mods with CLI. The security levet is very low because I can not update this Mac OS as the Macbook pro late 2013 model can follow the new OS versions. I’m living in the past some how but need to be up to date with security level by using Fedora linux apps.
In general, a minimal installation of fedora requires ~250 MB in /boot/efi, ~700 MB in /boot, and at least 25 GB in /. /home should have as much space as you feel is needed.
If installing on a 1 TB SSD I could recommend that you allocate at least 75 GB for /.
On my daily driver system I have this in a 240 GB SSD
# fdisk -l
Disk /dev/sda: 223.58 GiB, 240065183744 bytes, 468877312 sectors
Disk model: SanDisk SSD PLUS
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: E40A3810-D22D-49F4-99A1-660AC05AA530
Device Start End Sectors Size Type
/dev/sda1 2048 514047 512000 250M EFI System
/dev/sda2 514048 6658047 6144000 2.9G Linux filesystem
/dev/sda3 20994048 335575039 314580992 150G Linux LVM
Partitions sda1 & 2 are /boot/efi and /boot while sda3 is /. /home is on a separate drive (5 TB raid array). I allocated a lot more space than needed for /boot, so ~750 to 1000 MB is quite adequate even though it will function with as little as 500 MB.
Wouw! Does that also mean that Fedora can be installed on a Raspberry pi 4 with that low level of data usage.
I made the partion on 50 GB of a 500 GB SSD. but now I’m in doubt if it should be repartitions to 25 GB. Anyway I have to learn by testing things out. I mean it is only a computer. In can positively be redone.
Sda means harddisks and EFI is where the system boots from. but the sda2 says filesystem in your case. The sda3 is RAID a server like hosting network.
Is it all on the same disk or 3 different ?
So would I have the option to do similar as the CLI in the Terminal crossed with the Xcode in Macbook. there are some similarities.
Those are the arm images. You select either server or workstation then the DE you wish, then when you get to the actual images you would need to select the raw image. I am guessing you would need to already have a fedora OS installed on the PC since you are trying to use the media writer which is used to write an iso to a usb device. But to put the raw arm image on the sd card you need the arm-image-writer instead.
If you have adequate RAM you could do it all while booting and running the live image. The raw arm image is only ~1.3 GB.
On fedora (even the live image) install the arm-image-installer package.
Then the command arm-image-installer with nothing else will give you the options and commands needed to make it work. It is so simple to use that they did not even provide a man page for it.