summaryrefslogtreecommitdiffstats
path: root/docs (follow)
Commit message (Collapse)AuthorAgeFilesLines
* doc: fix typoYu Watanabe2021-12-091-1/+1
|
* tree-wide: fix typoYu Watanabe2021-12-011-2/+2
|
* docs: document that systemd closes console during normal runtimeArvid E. Picciani2021-12-011-1/+4
| | | | | | fixes #21451 Signed-off-by: Arvid E. Picciani <aep@exys.org>
* Merge pull request #21578 from bluca/json_specZbigniew Jędrzejewski-Szmek2021-11-301-7/+12
|\ | | | | docs: clarify JSON terms in COREDUMP_PACKAGE_METADATA
| * docs: clarify ELF note usage in COREDUMP_PACKAGE_METADATALuca Boccassi2021-11-301-4/+4
| |
| * docs: clarify JSON terms in COREDUMP_PACKAGE_METADATALuca Boccassi2021-11-301-4/+9
| |
* | tree-wide: fix typoYu Watanabe2021-11-302-2/+3
|/
* docs: fix descriptions in discoverable partitionsAlyssa Ross2021-11-271-4/+4
| | | | | | | | | | | | | | | 00db9a114e ("docs: generate table from header using a script") got the descriptions for the partition types mixed up. After that change, the spec claimed, for example, that the /usr partition should contain "dm-verity integrity hash data for the matching root partition", and that the /usr verity partition should be of type "Any native, optionally in LUKS". This made the spec an extremely confusing read before I figured out what must have happened! I've gone through the table as it existed prior to 00db9a114e, and moved the descriptions around in the script that generates the table until they matched up with what they used to be. Then I regenerated the table from the fixed script.
* user-record: add rebalanceWeight fieldLennart Poettering2021-11-251-3/+10
|
* os-release: add new PORTABLE_PREFIXES= field for declaring valid portable ↵Lennart Poettering2021-11-231-0/+14
| | | | service match prefixes
* docs: remove comment that makes githubs renderer very angryZbigniew Jędrzejewski-Szmek2021-11-231-1/+0
| | | | It is fine on github.com, but not on github.io.
* man/doc: document auto resize modesLennart Poettering2021-11-231-0/+6
|
* Merge pull request #21425 from keszybz/ppc64-fixesLennart Poettering2021-11-221-56/+118
|\ | | | | Add base-filesystem defines for arm64/ppc64el/riscv64 and make build quiet again
| * docs: document the partition UUID used by homedZbigniew Jędrzejewski-Szmek2021-11-191-0/+1
| |
| * docs: generate table from header using a scriptZbigniew Jędrzejewski-Szmek2021-11-191-30/+91
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds a helper script: $ python3 tools/list-discoverable-partitions.py <src/shared/gpt.h <!-- generated with tools/list-discoverable-partitions.py --> | Partition Type UUID | Name | Allowed File Systems | Explanation | |---------------------|------|----------------------|-------------| | _Root Partition (Alpha)_ | `6523f8ae-3eb1-4e2a-a05a-18b695ae656f` | [Root Partition] | [Root Partition more] | | _Root Partition (ARC)_ | `d27f46ed-2919-4cb8-bd25-9531f3c16534` | ditto | ditto | ... The output can be pasted into the markdown file. I think this works better than trying to match the two lists by hand.
| * docs: switch the first two columns in partition uuid listZbigniew Jędrzejewski-Szmek2021-11-191-56/+56
| | | | | | | | | | Readers are most likely to want to go from a partition id to the uuid, so puts the uuid second
* | doc: rebreak boot loader specLennart Poettering2021-11-191-66/+225
|/
* docs: clarify the assumption on numeric values of JSON parsers we makeLennart Poettering2021-11-191-0/+10
| | | | | | Prompted by: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/BOBD6KVTXPR6K5ANAX6LIJLKNSGXCR3B/
* CONTAINER_INTERFACE: clarify that /proc/sys can be writable with namespacingLuca Boccassi2021-11-171-4/+6
| | | | | | When user and network namespaces are enabled, the kernel makes the global keys read-only, and makes the namespaced ones available for the guest already.
* docs: mention RET_NERRNO() in CODING_STYLE.mdLennart Poettering2021-11-161-0/+19
|
* Merge pull request #21333 from poettering/homed-report-fs-and-access-modeLennart Poettering2021-11-131-0/+5
|\ | | | | homed: report actual home dir access mode and fs type in effect
| * doc: document the two new accessMode/fileSystemType fieldsLennart Poettering2021-11-121-0/+5
| |
* | Merge pull request #21331 from poettering/luks-extra-mount-optionsLennart Poettering2021-11-131-0/+3
|\ \ | | | | | | homed: allow per-user additional LUKS mount options
| * | doc: document the new luksExtraMountOptions conceptLennart Poettering2021-11-121-0/+3
| |/
* / docs: document new mount option env varLennart Poettering2021-11-121-0/+6
|/
* Change gendered terms to be gender-neutral (#21325)Emily Gonyer2021-11-122-2/+2
| | | Some typos are also fixed.
* doc: add some docs with a checklist of what to do for new architecturesLennart Poettering2021-11-101-0/+61
|
* docs: invite people to define GPT partition types for all archs nowLennart Poettering2021-11-101-5/+3
| | | | | | | | | | | | | The discovery partitions spec so far suggested we should define arch-specific partition type uuids only for archs that have EFI. Let's change that and invite people to define them for any arch. Why? Even if GPT is defined as part of the UEFI spec it's quite useful independently of it, too. Specifically, our image dissection logic makes use of it, i.e. systemd-nspawn, systemd-gpt-auto-generator, systemd-repart, RootImage=, portable services, and so on. None of these tools are related to UEFI in any way. Hence, let's open this up.
* Merge pull request #20813 from unusual-thoughts/exittype_v2Zbigniew Jędrzejewski-Szmek2021-11-081-0/+1
|\ | | | | Reintroduce ExitType
| * Reintroduce ExitTypeHenri Chain2021-11-081-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This introduces `ExitType=main|cgroup` for services. Similar to how `Type` specifies the launch of a service, `ExitType` is concerned with how systemd determines that a service exited. - If set to `main` (the current behavior), the service manager will consider the unit stopped when the main process exits. - The `cgroup` exit type is meant for applications whose forking model is not known ahead of time and which might not have a specific main process. The service will stay running as long as at least one process in the cgroup is running. This is intended for transient or automatically generated services, such as graphical applications inside of a desktop environment. Motivation for this is #16805. The original PR (#18782) was reverted (#20073) after realizing that the exit status of "the last process in the cgroup" can't reliably be known (#19385) This version instead uses the main process exit status if there is one and just listens to the cgroup empty event otherwise. The advantages of a service with `ExitType=cgroup` over scopes are: - Integrated logging / stdout redirection - Avoids the race / synchronisation issue between launch and scope creation - More extensive use of drop-ins and thus distro-level configuration: by moving from scopes to services we can have drop ins that will affect properties that can only be set during service creation, like `OOMPolicy` and security-related properties - It makes systemd-xdg-autostart-generator usable by fixing [1], as obviously only services can be used in the generator, not scopes. [1] https://bugs.kde.org/show_bug.cgi?id=433299
* | build: preserve correct mode when generating files via jinja2Christian Brauner2021-11-081-2/+1
| | | | | | | | | | | | | | | | | | When using "capture : true" in custom_target()s the mode of the source file is not preserved when the generated file is not installed and so needs to be tweaked manually. Switch from output capture to creating the target file and copy the permissions from the input file. Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>
* | Merge pull request #21171 from DaanDeMeyer/tty-dimensionsLennart Poettering2021-11-061-0/+2
|\ \ | | | | | | exec: Add TTYRows and TTYColumns properties to set TTY dimensions
| * | exec: Add TTYRows and TTYColumns properties to set TTY dimensionsDaan De Meyer2021-11-051-0/+2
| |/
* / docs: document systemd-homed development env varsLennart Poettering2021-11-051-0/+32
|/
* CODING_STYLE: allow joined variable declarations and function callsZbigniew Jędrzejewski-Szmek2021-11-031-9/+18
| | | | | | | | | … but only for a single variable. The guidelines already allowed declaring variables at the point of initialization. But not making a function call to do that. Let's allow that now. The existing style of declaring and initializing seperate is still allowed, and whatever makes most sense should be used.
* docs: document what integer range we expect from JSON parsersLennart Poettering2021-10-281-0/+5
|
* docs: document $PASSWORD in ENVIRONMENT.mdLennart Poettering2021-10-281-0/+15
| | | | Fixes: #20955
* homework: allow specifying explicit additional mount options when using CIFS ↵Lennart Poettering2021-10-271-9/+13
| | | | | | | | backend This is useful since certain shares can only be mounted with additional mount flags. For example the SMB share in modern AVM Fritz!Boxes requires "noserverino" to be set to work from Linux.
* homework: allow specifying a dir component in CIFS servicesLennart Poettering2021-10-271-1/+3
| | | | | | | | | | Allow specifying CIFS services in the format //host/service/subdir/… to allow multiple homedirs on the same share, and not in the main dir of the share. All other backends allow placing the data store at arbitrary places, let's allow this too for the CIFS backend. This is particularly useful for testing.
* doc: fix typo in commandYu Watanabe2021-10-271-1/+1
| | | | Follow-up for #21147.
* Merge pull request #21147 from DaanDeMeyer/hacking-docsZbigniew Jędrzejewski-Szmek2021-10-271-25/+32
|\ | | | | docs: Clean up HACKING.md
| * docs: Specify code block language for mkosi boot instructionsDaan De Meyer2021-10-271-4/+4
| |
| * docs: Make mkosi install instructions genericDaan De Meyer2021-10-271-2/+3
| |
| * docs: Extend builddep instructions to include more distrosDaan De Meyer2021-10-271-5/+12
| |
| * docs: Remove mkosi symlink instruction from HACKINGDaan De Meyer2021-10-271-1/+0
| | | | | | | | | | | | mkosi automatically builds for the host distro which seems a much better default to encourage since dnf won't be installed on any host system that's not Fedora anyway.
| * docs: Simplify git instructions in HACKING slightlyDaan De Meyer2021-10-271-3/+2
| |
| * docs: Clean up links in HACKING.mdDaan De Meyer2021-10-271-10/+11
| |
* | docs/COREDUMP_PACKAGE_METADATA: ELF section should be allocated and 0-paddedLuca Boccassi2021-10-271-6/+6
| |
* | docs/COREDUMP_PACKAGE_METADATA: ELF section should be read-only and ↵Luca Boccassi2021-10-261-3/+3
| | | | | | | | 4-bytes-aligned
* | docs/COREDUMP_PACKAGE_METADATA: add architecture fieldLuca Boccassi2021-10-261-18/+26
|/