| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
As flagged by Lintian
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Like much English text, the systemd documentation uses "may not" in the
sense of both "will possibly not" and "is forbidden to". In many cases
this is OK because the context makes it clear, but in others I felt it
was possible to read the "is forbidden to" sense by mistake: in
particular, I tripped over "the target file may not exist" in
systemd.unit(5) before realizing the correct interpretation.
Use "might not" or "may choose not to" in these cases to make it clear
which sense we mean.
|
| |
|
|
|
|
|
|
|
|
|
| |
Tool to parse it and to use it for Debian packaging available at
https://github.com/systemd/package-notes
Add 3 levels of priority like Debian does, but using terminology
from RPM as it seems more apt.
We will very likely never use 'required', as we use this functionality
for optional features, but it is worth having it in the spec nonetheless
as we want it to be generalized.
|
| |
|
|
|
| |
This commit fixes two instances of a miscount. As the number is not important in either case, and seemingly subject to changes, it was removed entirely.
Another sentence was reworded to improve readability.
|
| | |
|
| |
|
|
|
|
|
| |
Some people are just sad, sad lost souls who don't like even the tiniest
ray of color in their life. Let's add an env var knob for allowing them
to turn the background tinting off, to drive the last bit of color from
their life so that they can stay in their grey grey life.
|
| |
|
|
|
|
|
| |
delete it
This is not information that needs to be published on systemd.io as it's
purely internal, so the README is enough
|
| |
|
|
| |
cgroupv1 is deprecated, and os-release has a fully fledged manpage
|
| |
|
|
| |
@iainlane doesn't work on Ubuntu infrastructure anymore, and `bionic` is still ESM, but not really supported anymore either.
`noble`, which is the latest Ubuntu, probably is better for testing `systemd` in 2024, and pinging `qa-help` on IRC is the current official way to contact the team behind Ubuntu's infrastructure.
|
| |
|
|
|
|
|
| |
systemd-debug-generator(8) lists it as `systemd.debug_shell`.
According to 1d84ad944520fc3e062ef518c4db4e1d3a1866af, kernel command
line options should use an underscore instead of a dash.
|
| |
|
|
| |
Signed-off-by: spdfnet <32593931+spdfnet@users.noreply.github.com>
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This is a bit hackish, but really useful sometimes to play around with
some qemu switches.
|
| |\
| |
| | |
docs: use absolute links for our pages
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since 56b2970 has proven to be a no-go for us, as it breaks existing
links, let's embrace the trailing slash and use absolute links
everywhere for our pages. This way we'll get around browser cleverly
appending the relative link to the current location (since it ends with
a slash), and given our docs/ layout is flat it's not much of a hassle
either.
Converted using this beauty:
$ sed -ri 's/(\[.+\]\()([A-Z_]+\))/\1\/\2/g' *.md
Resolves: #32088 (again) and #32310
|
| | |
| |
| |
| |
| |
| | |
This breaks existing links with a trailing slash, so it's a no-go.
This reverts commit d1a7e030c5daa4a09ee93b8af6b28ecaac5d34d0.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Let's create the .ssh dir with the right perms first.
Suggested by @gcb.
Fixes: #28172
|
| | | |
|
| |\ \
| |/
|/| |
vmspawn: generate predicatable TAP device names and MAC addresses
|
| | | |
|
| |\ \
| | |
| | |
| | | |
I did the merge manually to resolve a trivial conflict.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Some of the internal links didn't work.
To make them work we had two options:
1. Keep the trailing slash at the jecyll config:
The built structure of the html files is one directory for each file, including a html file.
This is why a relative link including the `../` is required to get out of the built folder and make it work.
e.g.
config: permalink: /:title/
HACKING.md: [Coding Style](../CODING_STYLE)
2. Remove the trailing slash, the built structure is like the structure in dev: one html file for each markdown file.
In this case, the links as they are implemented just work.
e.g.
config: permalink: /:title
HACKING.md: [Coding Style](CODING_STYLE)
We use option 2 :)
|
| | | | |
|
| | | |
| | |
| | |
| | | |
for ELF_PACKAGE_METADATA
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
