Сколько весит fedora linux

Hardware Overview

Fedora 38 provides software to suit a wide variety of applications. The storage, memory and processing requirements vary depending on usage. For example, a high traffic database server requires much more memory and storage than a business desktop, which in turn has higher requirements than a single-purpose virtual machine.

Minimum System Configuration

The figures below are a recommended minimum for the default installation. Your requirements may differ, and most applications will benefit from more than the minimum resources.

• 2GHz dual core processor or faster
• 2GB System Memory
• 15GB unallocated drive space

Users of system equipped with the minimum memory of 2GB may want to consider Fedora Spins with less resource intense Desktop Environments

Fedora 38 can be installed and used on systems with limited resources for some applications. Text, VNC, or kickstart installations are advised over graphical installation for systems with very low memory. Larger package sets require more memory during installation, so users with less than 768MB of system memory may have better results performing a minimal install and adding to it afterward.

For best results on systems with less than 1GB of memory, use the DVD installation image.

Recommended System Configuration

The figures below are recommended for the default x86_64 Workstation installation featuring the Gnome desktop . Your requirements may differ, depending on Desktop Environment and use case.

Fedora 38 can be installed and used on systems with limited resources for some applications. Text, VNC, or kickstart installations are advised over graphical installation for systems with very low memory. Larger package sets require more memory during installation, so users with less than 768MB of system memory may have better results preforming a minimal install and adding to it afterward.

For best results on systems with less than 1GB of memory, use the DVD installation image.

Источник

Fedora Server Technical Specification

This document aims to describe the technical characteristics and properties of the Fedora Server Edition in detail. This includes provided services, installed software, and the like. It also defines characteristics and features that are not yet or not fully implemented in the current Fedora Server Edition release.

Preamble

Fedora Server provides a stable, flexible, and universally-adaptable base for the everyday provisioning of services and applications by organizations and individuals, based on the latest technology and available quickly after the upstream releases. It aims to empower users to deploy the services they need, whether using proven mature techniques or current technical developments, under their own control and adapted to their own needs. For this purpose, it provides a broad spectrum of available techniques from which users can choose completely independently and without predetermined valuations.

Overview

The specification defines implementation details, implementation variants, and especially extensions. They constitute a detailing and technical elaboration of the goals and principles as stated in the Fedora Server Product Requirements Document.

Specifically, it covers the following topics

describes the basic features and properities. They constitute the base system, which is installed by the (graphical) installer by default.

describes additional features that are not part of the default (graphical) installation but require subsequent administrative action

describe various services which Fedora Server can validly and concurrently offer to users. Additionally, these are specifically supported by Ansible provided administratve assistance.

The features and properties specified here are the basis for the specification of Fedora Server release criteria and release blockers.

1. Core Features

This section describes the basic properties and features of the platform and their intended use.

1.1 Supported Architectures and Install Media

Fedora Server will definitely run on and provide install media for x86_64 and aarch64 servers. The project may provide install media for additional architectures. But these are not part of standard quality management and may be available ephemerally.

• A network installation media providing a minimal package set allowing to boot the system, connect to Internet and contact the Fedora media server to download packages to be installed.
• A local installation media providing the default package set as well as any featured services that are meaningfully installed without a network connection.

• It can additionally point at network resources to make available an ever larger package set.
• Nevertheless, this media should be friendly to regions with limited Internet connection stability and performance. Thus, it is a trade-off between completeness and practical download size..

1.2 File System and Storage Organization

Fedora Server gives the highest priority to maximum reliability and security of data with a maximum of possible performance.

To achieve this goal, Fedora Server encourages strict separation of system and user data and encourages to further isolate user data, e.g. by services. Any system maintenance must be possible with the least risk of endangering or compromising user data (e.g. by temporarly unmounting) and an error somewhere on the local disk storage should remain as isolated as possible and without system-wide impact.

Thus, Fedora Server Edition’s default installation

• creates the necessary standard partitions to boot the server (BiosBoot, EFI, /boot)
• creates a Volume Group with one Logical Volume of a reasonable minimal size to accomodate the root file system and system files using XFS
• leaves the remaining space untouched for customization by the system administrator for user data, services or other uses. The installer must also support the following common options

• enlarge the one logical volume to accomodate custom data as well without any separation (not recommended)
• create one or more logical volumes to accomodate custom data
• or even create an additional Volume Group dedicated to custom data

The installer also provides a custom partitioning interface to accommodate use cases beyond the scope of default partitioning.

Additionally, the installer shall provide an option to enable disk encryption.

1.3 Basic service and daemon management

Systemd provides ways to control and monitor the activity and status of system services, resources they require, and the like. All system services must provide systemd units to be included in the Fedora Server standard installation.

1.4 SELinux

SELinux will be enabled in enforcing mode, using the targeted policy. It must fully protect any installable system component and functional application.

Fedora Server Edition must include a user-friendly mechanism for identifying SELinux denials and find workarounds. Currently, Cockpit’s SELinux module provides this functionality.

Additionally, any Server Role we provide MUST also provide options to appropriately modify the system’s SELinux configuration (adjusting booleans, for example).

1.5 Networking

By default, NetworkManager controls and manages all network devices and connections. Any modifications or adjustments to the network configuration must use the NetworkManager configuration tools or the public NetworkManager D-BUS API.

Installation or First Boot must create a permanent configuration file for each physical network device found, or at least a stub configuratin file. Primarily, DHCP is to be used and enabled if available. Both must allow the system administrator to customize the default configuration without restriction.

1.6 Firewall

The default method in Fedora Server is firewalld. It is part of the basic initial installation and not deselectable.

The default initial configuration must provide the highest security possible with the ability of remote administration. But it may not interfere with the normal operation of programs installed by default.

Therefore, on a pristine default system, the only open incoming ports are SSH and Cockpit.

Configuration of ssh allows root access only with key-based login, if at all.

Additionally, any Server Role we provide MUST also provide options to appropriately display and modify firewalld’s configuration options.

1.7 Account handling

SSSD will provide the backing storage for identity management. The Fedora Server is expected to nearly always be configured for ‘centrally-managed’ user information; it must be possible to configure it to rely on a directory service for this information. Fedora Server will provide and support the realmd project for joining FreeIPA and Active Directory domains automatically. Interacting with other identity sources will remain a manual configuration effort.

1.8 Logging

Fedora Server uses systemd-journald and rsyslog for system logging. It’s recommended all applications submit logs to systemd-journald.

It stores log files locally by default and also supports sending full log data to an external server to the maximum extent possible. It uses rsyslog for forwarding data to a central server.

1.9 Miscellaneous System Information

System locale, timezone, hostname, etc. will be managed through the services provided by systemd for this purpose, specifically

1.10 System Installer

The desired installation experience for the Fedora Server product is to limit the pre-installation user interaction to the minimum. The storage configuration UI does provide a single sensible default and an alternative, fully customizable configuration UI.

Package selection will be supplementary.

Fedora Server expects to be the sole citizen on the system. Support for coexisting with other operating systems is not a goal.

Fedora Server supports kickstart as implemented by pyKickstart and Anaconda as the unattended installation mechanism.

2. System Administration

2.1 Appearance

The primary system management tool is CLI using bash on a system console. Locally, the default Fedora Server boots to a text terminal login screen. It expects the system administrator to type the required commands or using bash scripts or to use Ansible roles and plays.

The local login prompt must also display any appropriate information needed to establish remote administration of the system, in particular, Cockpit’s access URL (see next paragraph).

For remote installation, ssh and sftp are installed and activated by default. Additionally, Cockpit is installed and activated by default and provides a Web based graphical Interface to assist remote system administration.

The Fedora Server does not provide a local graphical environment. If the administrator elects to install a desktop, they should choose and install a display manager themselves.

2.2 Input Methods

The input method support for the Fedora Server console access is the LOCALE support in the command shell.

2.3 Accessibility

Accessibility support on the Fedora Server will be limited to devices supporting the vision-impaired on the console.

2.4 Software updates

Software updates on the Fedora Server must be possible to perform either locally using command-line tools (dnf), remote using ssh or Cockpit, or centrally by common management systems (e.g. Satellite, Ansible).

2.5 Problem reporting

Problems and error conditions (e.g. kernel oopses, Selinux AVCs, application crashes, OOM, disk errors) should all be reported in the systemd journal. Support for sending this information to a central place (like abrt does for crashes today) is mandatory.

Источник