AshOS/README.md — readme_FA (generated) (readme_FA) @ Hosted Weblate: AshOS is installed from the official live iso for target …

The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not push the repository.

Zen

Translation

English

readme_FA (generated) (readme_FA)

Needs editing

This translation is currently locked.

Skip

	English	readme_FA (generated) (readme_FA)	Actions
	NixOS / GNU Guix - compared to nixOS, AshOS is a more traditional system with how it's setup and maintained. While nixOS is entirely configured using the Nix programming language, AshOS uses the native package manager of target distribution, for instance pacman for Arch, apt-get for Debian, etc. AshOS consumes less storage, and configuring your system is faster and easier (less reproducible however), it also gives you more customization options. AshOS is FHS compliant, ensuring proper software compatability. Unlike NixOS, you don't need to have a Ph.D. in computer science to just run an immutable os	--- Installation
	* AshOS allows declarative configuration using Ansible, for somewhat similar functionality to NixOS Fedora Silverblue/Kinoite - AshOS is more customizable, but does require more manual setup. AshOS supports dual boot, unlike Silverblue.	Arch iso can be generally used to bootstrap other distros except: Use Debian iso to bootstrap Debian, Ubuntu iso to bootstrap Ubuntu
	OpenSUSE MicroOS - AshOS is a more customizable system, but once again requires a bit more manual setup. MicroOS works similarly in the way it utilizes btrfs snapshots. AshOS has an official KDE install, but also supports other desktop environments, while MicroOS only properly supports Gnome. AshOS supports dual boot, as well as live-patching the system and installing packages without reboot	Depending on the live iso, it is very important that scripts in `./src/prep/` be executed (preparing live environment as well as partition/formatting) otherwise there would be error because time is not in sync etc. By default the installer will call these scripts, but if you want to do them manually, just comment the respective lines
	--- Installation	If running from an old arch iso, run the commands in section `# Fix signature invalid error` in `./src/prep/arch-live.sh`
	(Note: All scripts during install should be run with super user privileges)	You need an internet connection to install AshOS
	AshOS is installed from the official live iso for target distribution. For example [Arch Linux](https://archlinux.org/download/), [Debian](https://www.debian.org/CD/http-ftp/)/[Debian netinstaller](https://www.debian.org/distrib/netinst) etc.	AshOS used to ship with 3 installation profiles, one for minimal installs and two for desktop (Gnome, KDE Plasma). To make it more modular, we redesigned it and by default it only installs a bare minimum base snapshot. Once that is done, you can install any desktop environment you would like. For instance for GNOME, once booted in base snapshot, run:
	Arch iso can be generally used to bootstrap other distros except: Use Debian live iso-hybrid to bootstrap Debian, Ubuntu iso to bootstrap Ubuntu
	Depending on the live iso, it is very important that scripts in `./src/prep/` be executed (preparing live environment as well as partition/formatting) otherwise there would be error because time is not in sync etc. By default the installer will call these scripts, but if you want to do them manually, just comment the respective lines
	The commands to fix package db issues in live iso (i.e. arch_live.iso) take a long time to run. One can comment these to have installer run significantly faster. They are included mostly for virtual machine installation where time syncing issues are abundant.
	If you run into issues installing packages during installation, make sure you're using the newest iso, and update the package manager's keyring if needed
	If running from an old arch iso, run the commands in section `# Fix signature invalid error` in `./src/prep/arch-live.sh`

	English	readme_FA (generated) (readme_FA)	Actions
	Thanks to its reliabilty and automatic upgrades, AshOS is well suitable for single use or embedded devices
	As AshOS strives to be minimal solid and follow a LEGO like structure (start small, customize as you go), we primarily focus development on the base, meaning by default no Desktop Environment (not even Window Manager) is installed. This is by design as otherwise team has to support many DEs on many distros. What is provided is `profiles`. As DEs/WMs are just packages, with power of snapshotting, one can use ash to install the desired DE/WM. For instance to install GNOME in snapshot 1: ``` `ash clone 0` : create snapshot #1 `ash install 1 -P gnome` : install gnome in snapshot #1 `ash deploy 1` `reboot` ```	OpenSUSE MicroOS - AshOS is a more customizable system, but once again requires a bit more manual setup. MicroOS works similarly in the way it utilizes btrfs snapshots. AshOS has an official KDE install, but also supports other desktop environments, while MicroOS only properly supports Gnome. AshOS supports dual boot, as well as live-patching the system and installing packages without reboot
	AshOS is installed from the official live iso for target distribution. For example [Arch Linux](https://archlinux.org/download/), [Debian](https://www.debian.org/CD/http-ftp/)/[Debian netinstaller](https://www.debian.org/distrib/netinst) etc.	AshOS used to ship with 3 installation profiles, one for minimal installs and two for desktop (Gnome, KDE Plasma). To make it more modular, we redesigned it and by default it only installs a bare minimum base snapshot. Once that is done, you can install any desktop environment you would like. For instance for GNOME, once booted in base snapshot, run:
	Other chroot options	Runs a specified command inside snapshot and all it's branches
	This clones an entire tree recursively	Adds a new branch to specified snapshot
	``` ash tree-rmpkg <tree> <pacakge or packages> ```	To update a single snapshot
	This allows you to configure your system by modifying ``/etc`` as usual, and then saving these changes.	``` ash chroot <snapshot> echo 'GRUB_DISABLE_OS_PROBER=false' >> /etc/default/grub exit ```
	For Gnome and KDE profiles, we are assuming user just want things to work as default and as such we install default login manager. For any other profile, we focus on minimalism, and just install tbsm. One can obviously easily modify this if they choose to.
	Star this repo!
	``` aur::True ```	``` ash fixdb <snapshots> ```

Loading…

None

String updated in the repository

English

readme_FA (generated) (readme_FA) 352 characters edited Current translation Translated

11 months ago

Browse all string changes

Things to check

Mismatched colon

Source and translation do not both end with a colon

Reset

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Glossary

English	readme_FA (generated) (readme_FA)
No related strings found in the glossary.

String information

Source string location

:120

String age

11 months ago

Last updated

11 months ago

Source string age

11 months ago

Translation file

res/docs/README_FA.md, string 47