bootloader would be able to read it. The drawback with this is,
it needs to be UEFI Secure Boot signed, and we need some plan and policy how
that would work - per distribution btrfs drivers? Or is there a way to make it
generically supportable across distributions with a
configure GRUB2 for unlocking a
LUKS encrypted partition (so that GRUB can find the kernel and initramfs, load
them, and start the kernel). Therefore, on Fedora /boot is not encrypted, and
LUKS unlock for root is done in the initramfs.
Otherwi
4 specific mount option. Btrfs already does this by default.
--
Chris Murphy
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedorapro
won't be able to navigate to it from
/ - you can either mount the top level of the file system and delete it, or
you can delete directly by subvolume ID without mounting the top level, see man
btrfs subvolume
If you have questions find me (cmurf) on matrix
https://matrix.to/#/#fedora:fe
opment perspective. There's a similar effect with multiple
device Btrfs in KDE and GNOME, so it's not a Cockpit issue.
https://github.com/storaged-project/udisks/issues/802
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.or
x27;s no swap activated because you
once did a rollback way back when... :D
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://d
oing this if there's a problem (firmware confusion) with GPT.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraprojec
ould be blockers, not bugs that only manifest as part of a
dual boot Fedora installation.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Cond
as installation advise. It could be adapted into a Quick Doc for that
purpose though.
But my understanding of the original poster's issue is that he now has a bunch
of system level customizations. Not so much user level customizations.
Therefore the reuse home directory method wouldn't h
help with that as if there's a button you can
push to fix that. There's no button for train derailments. It's a customized
recovery every time that requires esoteric knowledge. Everything about it is
manual.
Are trains fragile? I'm not sure that's the best description bu
ld autocomplete the only directory present which is the shipping
kernel for Fedora 36.
Or hey I have that kernel in a btrfs snapshot I created after an F36 clean
install. It should be 5.17.5-300.fc36.x86_64 so the actual command ought to be
cp -r /mnt/root00/usr/lib/modules/5.17.5-300.fc36.x
and home (/home). You've toasted
the /boot volume which is functionally like Windows' system volume that it
boots from initially, if you wipe that, you'd be totally screwed on Windows
too. And also these days on Windows you don't get automatic restore points
either, y
where I can, I'm a bit frantic
> frankly.
Panic is one of the best known paths to data loss.
Before making any further changes, I advise a backup of important user data. Do
not attempt repair or reinstallation until there's at least two independent
copies of your important data.
--
hree dozen steps to repair this setup. They all have to
be exactly correct or it won't work. Much of this logic is in the installer.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...
On Fri, Sep 9, 2022, at 5:44 AM, Jack Craig wrote:
> hi all,
>
> I've been subscribed to this list for a while and I have never seen any
> traffic regarding Silverblue, is there a separate mailing list for
> Silverblue??
Pretty sure most of it happens on Discourse.
https://discussion.fedorapr
y replace grub.cfg, it's a static file these
days. The files that change are drop-in files found in /boot/loader/entries and
can be modified with grubby per examples at:
https://fedoraproject.org/wiki/GRUB_2#Changing_kernel_command-line_parameters
On Mon, Aug 15, 2022, at 2:32 PM, Bill Cunningham wrote:
> On 8/15/2022 12:17 PM, Chris Murphy wrote:
>>
>> On Sun, Aug 14, 2022, at 5:08 PM, Bill Cunningham wrote:
>>> I just thought I would ask for opinions on backups that people use.
>>> I have thought abo
hat's changed and
whether the parent snapshot is already on the destination. And then it's just
the time to transfer the data that's changed. So for a single file changed in
10 minutes, it could take just a couple seconds.
--
Chris Murphy
.org/koji/buildinfo?buildID=1977609
That's the -42 version which should work. Then you have the packages locally
and you can just put them in a directory and if you do an update that steps on
this version again, you can just cd to that dir and do "dnf downgrade *rpm" and
it'l
//fedoraproject.org/wiki/GRUB_2#Instructions_for_UEFI-based_systems
But ordinarily grub.cfg is static, you don't ever need to interact with it
anymore. All the Fedora bootloader files are in /boot/loader/entries in BLS
format. One file per kernel.
--
Chris Murphy
__
rsion, with a bls snippet containing
a rootflags entry pointing to the currently active subvolume used as root.
Anyway, it's slightly tricky but not endlessly.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe
this. Therefore it gets
confusing because you have to evaluate all the tradeoffs of each layout.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of
anism for system snapshots and rollbacks would be useful in
troubleshooting system problems?
Do you think a snapshot+rollback mechanism would be more or less useful than a
graphical rescue environment, for troubleshooting system problems?
Thanks!
--
Chris M
opted out of BootLoaderSpec conversion.
In particular the section
https://fedoraproject.org/wiki/GRUB_2#Instructions_for_UEFI-based_systems
contains more thorough instructions resulting in a more complete reinstallation
that should be equivalent to a clean installed system.
--
Ch
actual behavior compare to what
you thought would happen?
The questions list is not complete, feel free to add your own
categorizations / failure patterns that you tend to see.
Thanks!
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproje
t works
rather differently than Btrfs, but has the ability to detect such
corruption problems and report them to the upper layer as a read error
where the normal RAID error correction can then work properly.
--
Chris Murphy
___
users mailing list -- users
On Tue, Jul 5, 2022 at 8:40 PM Joseph D Wagner wrote:
>
> Should this go here, or the devel list?
Is this filtered in any way? Can you post a complete dmesg?
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsub
firmware is BIOS. Fedora last.
If firmware is UEFI, the order doesn't matter.
I agree with the suggestions to use Windows' tools to shrink NTFS and
its partition. But more importantly make sure to disable Fast
startup.https://dev.to/xeroxism/how-to-disable-fast-start-in-ubuntu-window
it a few minutes, which is really too long). I
think the FF bug got fixed but maybe not always? So as it turns out
oomd is doing the right thing in this case, just that we're not
getting a desktop notification about what happened.
--
Chris M
effect is
invisible (all ciphertext) so the fact it's btrfs is obscured and
can't be a factor until the LUKS volume is unlocked. So I'm thinking
unlock problems are unrelated to the fs selection, and it's some other
factor (package versions, network latency, race condition).
-
-repair
I have somewhat low confidence that it can be repaired rather than
make things worse. So you should start out with the earlier mount
commands to get anything important out of the fs first. IF those don't
work and there's important information to get out, you need to use
btrfs restore.
ds up making them subject to COW again, and that's
incompatible with using them as swapfiles. The entry in fstab looks
like this:
UUID=$uuid /var/swap btrfs noatime,subvol=varswap 0 0
man 5 btrfs has a SWAPFILE SUPPORT section that's fairly detailed steps.
--
Chri
up so that you can hibernate, but
> not resume?
>
> The fix is to run "dracut -a resume -f". This will update the initramfs
> to include the bits that let resume work. In order for this to continue
> working with kernel updates, you need to add a dracut config file with
to
the only changed file.
(You could use 'btrfs send -f' and place the stream as a file on a
non-btrfs file system. But you can't really look inside of it like a
snapshot received on a btrfs file system.)
--
Chris Murphy
___
users mailing li
ou'll get both more completely lost files and more completely intact
files because single profile doesn't stripe data.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.
can you believe those two terms are synonyms?[2]
[2] part of the problem might be the English language, really. If
you've ever been confused about strip and stripe [3], it's not you,
it's the words themselves.
[3] These two terms are not synonyms. [4]
[4] It really could make
rge enough MBR gap for GRUB to be installed.
fdisk -l /dev/sdX
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproj
On Fri, Dec 31, 2021 at 9:10 AM Robert Moskowitz wrote:
>
>
>
> On 12/31/21 00:22, Chris Murphy wrote:
> > On Wed, Dec 22, 2021 at 2:03 PM Robert Moskowitz
> > wrote:
> >> so something killed it and since tomorrow is garbage day...
> >>
> >> S
from the date the statement
containing the charge was mailed to you. If it's after 60 days, card
might have an extended warranty on everything, give that a shot.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe
also detect
SSD pre-failure symptoms before anything else including the drive's
SMART reporting, by showing transient corruption. All such messages
appear in dmesg. Btrfs is more sensitive to pre-failure because it's
checksumming everything, not just the file system. So it
art superimposed
on the splash, which shows F9). And from there choose the Windows Boot
Manager.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Co
own. Workstation once had a netinstaller, but it was
dropped maybe 1/2 dozen releases or so ago.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code o
nsistency is permitted.
Each edition (working group) and spin (special interest group) can
choose their own default layout and filesystem. For the btrfs by
default change, all the desktop spins were consulted in advance with a
preview of the proposal, to address any concerns they had and how to
opt-o
On Tue, Oct 19, 2021 at 10:30 AM Chris Murphy wrote:
>
> Hi,
>
> I think it's a bug, so I filed one.
> https://bugzilla.redhat.com/show_bug.cgi?id=2015569
Yep. So the bug is that the RPM and flatpak versions use different
ID's for the same application, therefore Soft
Hi,
I think it's a bug, so I filed one.
https://bugzilla.redhat.com/show_bug.cgi?id=2015569
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Co
On Thu, Sep 30, 2021 at 4:13 PM Gordon Messmer wrote:
>
> On 9/30/21 12:41, Chris Murphy wrote:
> > Seems likely to me some service is not quitting properly, preventing /
> > from being unmounted
>
>
> If that were the case, there might be information about an exit fa
se it will persistently put a root level shell on
tty9, which is what you'll switch to with control-alt-F9 when you get
the shutdown hang. And then do:
systemctl list-jobs
df
lsof
--
Chris Murphy
___
users mailing list -- users@li
installation.
https://fedoraproject.org/wiki/QA:Testcase_partitioning_custom_btrfs_preserve_home
And yeah we need a better way to document this than a test case.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fed
Hi,
A new section in https://docs.fedoraproject.org/en-US/docs/ has
appeared specifically for Fedora Server.
https://docs.fedoraproject.org/en-US/fedora-server/
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe
On Wed, Aug 11, 2021 at 1:04 PM George Avrunin wrote:
>
> On Mon, 9 Aug 2021 12:15:20 -0600, Chris Murphy wrote:
>
> > Yeah I have a bit of a gripe with systemd that it doesn't, by default,
> > insert the sleep request in the log. What exactly requested it? User
>
ke things or if it was in fact first broken with
5.13.6 (and still broken in 5.13.9). But with such a new kernel, I
also suggest making sure vmware is up to date.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe s
if a single line of info
about sleep being initiated can be dumped into the log by default?
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Con
ccepted, if you enter something
ambiguous, it'll make suggestions:
$ sudo btrfs rep sta
btrfs replace: ambiguous token 'sta'
Did you mean one of these ?
start
status
'btrfs rep star' is unambiguous for 'btrfs replace start' - just make
up your own
eration.
> This is even weirder since as you can clearly see the directory exists in the
> given path.
>
> Any suggestions on what is going wrong ?
>
> I should tell you that a while back I had a huge BTRFS file system crash, and
> it took a lot of targeted help from the
because the problem
must have been introduced during the 5.13 development cycle and just
didn't get caught for some reason.
That's the basics. It's not that hard. But there's lots of tricks and
personal preferences that are all non-obvious, so if you get stuck,
head to irc.
king kernel in that laptop, is
> 5.12.15-300.fc34.x86_64
> I'm not any programmer nor bugzilla familiar.
> I have sent to Chris Murphy both kernel boots, working and not
> working ones. Hopefully I sent them right address...
Select the new (problem) kernel version, but don't
rq-trigger) to dump
extra debugging information into the kernel message buffer, and then
file a bug attaching dmesg.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le..
nel bugs and even
btrfs bugs. I guess you could call it a nascent online fsck, but
without repair capability. Currently it flips the file system
read-only to stop further confusion and keep data safe.
--
Chris Murphy
___
users mailing list -- users@li
a3) from 98.41GiB to max
Single device btrfs resize is straightforward. But with multiple
device Btrfs, you need to specify the devid you want resized,
otherwise it defaults to devid 1.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject
On Mon, Jul 26, 2021 at 3:25 AM Eyal Lebedinsky wrote:
>
> Is this an intentional change?
You might search https://lore.kernel.org/linux-usb/ and see if
anything pops up; and if not then ask on the same list,
linux-...@vger.kernel.org.
--
Chris
On Fri, Jul 23, 2021 at 1:56 PM Chris Murphy wrote:
>
> Even better is if you can reproduce the high load and try to capture
> one or more of the following: sysrq+l which will dump the result into
Actually, sysrq+w is also useful. The root user can use:
echo l > /proc/sysrq-tr
u can reproduce the high load and try to capture
one or more of the following: sysrq+l which will dump the result into
dmesg and will end up in the journal, which you can filter similarly:
journalctl -b -k -o short-monotonic --no-hostname > dmesg-cpustack.txt
And attach to the bug report.
Also,
7]: quitting realmd service after timeout
Yeah ok wow, so packagekit even says 11s to do some basic stuff? Okayyy...
uhh what is this??
[1.903084] kernel: i915 :00:02.0: [drm] *ERROR* Stolen
reserved area [mem 0xdf10-0xdf1f] outside stolen memory [mem
0x9f20-0xc11f
> On Sun, Jul 18, 2021 at 11:12 AM Joe Zeff wrote:
> >
> > On 7/18/21 7:38 AM, John Mellor wrote:
Oh nice, the previous email is meant for John, not Joe.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsu
td.service
> > 13.711s systemd-journal-flush.service
All three of these are suspiciously long.
Post /etc/fstab, /proc/cmdline, and the output from 'journalctl -b -o
short-monotonic --no-hostname > journal.log'
--
Chris Murphy
___
user
@lists.fedoraproject.org/
And the docs project list of sub projects
https://pagure.io/group/fedora-docs
Which includes the accessibility guide sub project
https://pagure.io/accessibility-guide
--
Chris Murphy
___
users mailing list -- users@lists.fedorap
e logs for
> > > that, but you can also add nofail to the fstab for it so at least boot
> > > won't hang.
Did you add nofail to fstab options for the /boot/efi line?
Can you post 'journalctl -b -o short-monotonic --no-hostname' somewhere?
--
Chris
rmation
> ESP: n/a
> File: └─n/a
>
>
> Is this normal ?
Yes, bootctl is for the systemd-boot bootloader, which Fedora doesn't
use right now.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.or
fstab for it so at least boot
won't hang.
The gist of what you need is one f34 bootloader in
/boot/efi/EFI/fedora/ and its grub.cfg points to the real grub.cfg at
/boot/grub2 which in turn loads blscfg.mod which finds and reads
/boot/loader/entries and then creates a GRUB menu from all the
?rd=Grub2#Changing_kernel_command-line_parameters_with_grubby
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.
in every meaningful way, but
the new destination device can be any size. Of course, it needs to be
at least as large as the data usage on the seed. [1]
--
Chris Murphy
[1]
Sorta :) Once the 2nd device is added, you are allowed to delete
things you don't want replicated. They are retained
dy an upstream bug report and a work
around is published in the bug. Or just install the proprietary driver
via RPM Fusion repo.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists
PackageKit uses libdnf. libdnf is the core library for dnf,PackageKit
and rpm-ostree.
You should generally get the same results using either dnf or PackageKit.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send
imply some kind
of layout change, and we need to consider upgrades. It has to work for dnf
and PackageKit, etc.
--
Chris Murphy
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraprojec
0:0:1: [sde] Attached SCSI disk
>
> The uas message is again from device 6:0:0:1 as before, even though the
> disks have been swapped. IOW the issue definitely comes from the dock,
> not from the physical drives themselves.
I don't know if it's coming from t
therboard with no intervening hub or splitter. It is independently
> powered via a wall socket and power block.
Does the error messages I referred to happen when the system is booted
with the drives attached separately? Or does it happen when only
connected to a particular port on the dock?
ven a quit
or terminate signal at shutdown, but it's become sufficiently busy
that it ignores it. And then systemd hits a time out 1m30s later and
kills it anyway. There is a Workstation ticket about shortening
shutdown times.
https://pagure.io/fedora-wo
e it completes, and optionally passes
some tests, would the root be switched to the updated snapshot, and
reboot. And the user can choose when that happens.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an e
says to:
[Service]
CPUQuota=25%
Save it out, and when the unit restarts (logout and login or do the
daemon-reload followed by service restart dance) you'll see packagekit
uses this value as a maximum.
--
Chris Murphy
___
users mailing
is running
uresourced. It's only enabled by default on GNOME right now. But it's
considered safe to run as an opt in for other desktops, though we want
to keep an eye on possible regressions.
There is still more work to do in this area, in particular wiring up
the IO isolation. Any time th
zram based swap because it's
more mature in the older kernels. If you are able to use an elrepo
kernel you could try changing nothing else and see if the kernel 5.8+
changes help your workload all by themselves. And if not you could
look at either zram based swap or zswap.
On Mon, Jun 21, 2021 at 10:58 AM Chris Murphy wrote:
>
> Jun 19 12:47:12 fedora kernel: sd 6:0:0:1: tag#2 uas_eh_abort_handler
> 0 uas-tag 2 inflight: IN
> Jun 19 12:47:12 fedora kernel: sd 6:0:0:1: tag#2 CDB: Mode Sense(6) 1a
> 00 08 00 18 00
Yeah and in the install-boot log i
s to use a
quirk, they'll apply it by default in a future kernel. If not, then it
becomes something you apply every boot.
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.f
ock appearing, bus appearing,
drive on bus appearing, partition map appearing. I couldn't open the
previous journal log provided, it wasn't publicly visible or I'd have
taken a gander.
--
Chris Murphy
___
users mailing list -- users@lists.f
I make fstab mount options include:
nofail,noauto,x-systemd.automount
That way it is only mounted on demand, i.e. when the mount point is "touched".
It's also possible to use x-systemd.idle-timeout=300 which will
unmount it after 5 minutes idle.
y state
on the bus shared by sysroot.
I'm suspicious that something is trying to mount it, or otherwise access
it, but I haven't seen the logs.
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email
robably not because it'll step on valid bootloader things with stale
copies. If you avoid stepping on anything in:
/boot
/etc/grub*
It might work... but you'll still have kernels that rpm database says
are installed that aren't installed; you'll have stale boot entries
for ker
eps to fix all of it after the restore.
And to my knowledge no tool knows how to do that except the installer.
And the installer only knows how to do it in the context of a clean
install. Not a repair.
--
Chris Murphy
___
users ma
xplaining all that in detail is tedious,
but maybe someone knows of a guide how to do all that.
But this process is the same whether the source is btrfs, xfs or
already ext4 and you need to migrate it to new file systems/layout.
--
Chris Murphy
___
users ma
;, \
KERNEL=="sd*[!0-9]", \
ENV{ID_SERIAL_SHORT}=="WDZ47F0A", \
RUN+="/usr/sbin/hdparm -B 100 -S 252 /dev/disk/by-id/wwn-0x5000c500a93cae8a"
$
Chris Murphy
--
Chris Murphy
___
users mailing list -- users@lists.fedorapr
you're having is a
new problem, maybe we've got a regression in 055 or something? I'm not
sure yet...still kinda in the dark on what's going wrong.
Also, it is possible it's not related to this btrfs file system at
all, but I'm throwing it out there just as something to
On Sat, Jun 12, 2021 at 11:20 AM Patrick O'Callaghan
wrote:
>
> On Sat, 2021-06-12 at 07:25 -0600, Chris Murphy wrote:
> > Both problems need logs. It's quite a bit over kill but these boot
> > parameters will help provide enough info.
> >
> > systemd
fully avoiding the dracut shell. But better to
get the shell than an indefinite hang.
journalctl -b -o short-monotonic --no-hostname > journal.log
Copy that out to a file sharing service, and post the URL.
Chris Murphy
___
users mailing list
e defaults, an ancient
kernel will mount it. But there are features that old kernels don't
support, like for example zstd compression which arrived in kernel
4.14, thus not mountable (incompatible) with older kernels. Free space
tree v2 exists since kernel 4.5, but its flag permits ro mount with
old
including the kernel, initramfs, and the whole graphics
stack. But, near term such a thing would be btrfs only unless we
dedicate a literal partition and stick a Live OS ISO image on it
(effectively).
--
Chris Murphy
___
users mailing list -- users@lists.
lems. And yeah it'll
often just stop, to seek human attention what to do about it. That's
pretty onerous, but it's also what protects your data from being
damaged even worse.
But anyway there's not much to go on here yet. We need to see dmesg
for the
way to do that is to create a new / mount
point rather than clicking on an existing one; also helpful is to not
specify a size for this mount point, just leave that 2nd field empty.
There is a test case that describes this in detail and hopefully
someone will
the inode number of a file in /usr that should be compress but
isn't and then plug that inode number into
btrfs insp dump-t -t 257 /dev/xyz | grep -C 20 $INUM
This may expose file names for other files. Doesn't matter to me if
you include the whole output of the above comment or trim to j
oint to
the EFI system partition and path to shimx64.efi or shim.efi.
Boot order can be reset by:
efibootmgr --bootorder $
Where $ is the four digit boot number for the Fedora boot entry.
No other entries need to be specified but you could optionally add a
fallback entry, e.g. --bootord
On Thu, Apr 29, 2021 at 3:44 PM Matti Pulkkinen wrote:
>
> to, 2021-04-29 kello 15:32 -0600, Chris Murphy kirjoitti:
> >
> > Looks like you found it?
> > https://bugzilla.redhat.com/show_bug.cgi?id=1955162
> >
>
> Yup. As for your earlier question about why I
1 - 100 of 1528 matches
Mail list logo
