; partitions' Type-UUIDs will have to be bent to match
the expected value for an ESP. What do you think, does that sound sane?
> PS: Any opinion about my latest comment ("nitpick") in the MR ?
Yeah, that is perfectly reasonable - I will update the MR as soon as I can :)
--
with best regards:
- Johannes Truschnigg ( johan...@truschnigg.info )
www: https://johannes.truschnigg.info/
signature.asc
Description: PGP signature
s result working and booting
fine across a variety of x86 EFI platforms and vendors, with the system
retaining its ability to boot from a single remaining leg of the ESP RAID1
during testing.
--
with best regards:
- Johannes Truschnigg ( johan...@truschnigg.info )
www: https://johannes.truschnigg.info/
signature.asc
Description: PGP signature
heers!
--
with best regards:
- Johannes Truschnigg ( johan...@truschnigg.info )
www: https://johannes.truschnigg.info/
signature.asc
Description: PGP signature
Package: fping
Version: 5.1-1
Severity: wishlist
Dear Maintainer,
I recently tried to use fping's relatively new `--fast-reachable` feature
(introduced in fping 5.2) on Debian and noticed that the package is at its
upstream release 5.1 still on sid.
Upstream is at 5.3 and has implemented a numbe
Package: partman-auto-raid
Version: 51
Severity: normal
Tags: d-i patch
Dear Maintainer,
I was trying to get a preseeded Debian installation to create a md software
RAID array with superblock version 1.0. To do that, one has to issue `mdadm
--create ... --metadata=1.0 ...` at array creation time.
Dear maintainer,
tc-play 3.3 seems to build fairly cleanly on bullseye from its tag/release
tarball [0]. It'd be *really* nice to have in Debian to be able to handle
VeraCrypt volumes.
[0]: https://github.com/bwalex/tc-play/archive/v3.3.tar.gz
--
with best regards:
- Johannes Trusc
Package: sssd-ad
Version: 2.4.1-2
Severity: normal
Dear Maintainer,
sssd-ad supports dynamically updating DNS recource records on Active
Directory-based authoritative DNS servers after the system has joined their AD
domain. To use this feature, a number of dyndns-specific sssd options have to
be
ould take to stop a user's cluster (esp. in the default
"smart" mode, 5s seems VERY unlikely for busy servers).
Thanks very much for taking note of this problem, and trying to help fix it!
--
Mit freundlichen Grüßen
Johannes Truschnigg
Senior System Administrator
--
mailto:johannes
ckage).
Thanks for taking note of this issue, and its easy fix.
--
Mit freundlichen Grüßen
Johannes Truschnigg
Senior System Administrator
--
mailto:johannes.truschn...@geizhals.at (in dringenden Fällen bitte an
i...@geizhals.at)
Geizhals(R) - Preisvergleich Internet Services AG
Obere Donaustrasse
to have absurdly long lines in inittab.
If you need to do something that doesn't fit in 127 bytes on its command line,
you might just as well write a wrapper, and call that fron inittab. Helps
keeping things tidy - but that's personal preference of course.
--
with best regards:
- J
Of course I managed to get a typo not only into my report, but also into the
attached patch: "fiels" is supposed to read "field". I've attached a corrected
version for your convenience - sorry for the noise.
diff -u -r a/sysvinit-2.88dsf/man/inittab.5 b/sysvinit-2.88dsf/man/inittab.5
--- a/sysvinit
Package: sysvinit
Version: 2.88dsf-13.1+squeeze1
Severity: minor
Tags: patch
I added a new entry to inittab on a busy host which did not seem to start upon
invoking `telinit q`. Syslog received the following message:
Nov 22 10:16:29 r7 init: /etc/inittab[93]: process field too long
This limit (
12 matches
Mail list logo
