Now clean keyring will be prepared by qubes-builder so there will be no old
kernel.org key at all (and importing revocation key for non-existing key
fails).
Now clean keyring will be prepared by qubes-builder so there will be no old
kernel.org key at all (and importing revocation key for non-existing key
fails).
It doesn't make any sense on hvc console, but causes problems.
Problem: plymouth-quit.service is masked in VM, so plymouthd remains
running controlling console.
Apparently new-kernel-pkg does not work for grub2 config with xen
entries (new kernel isn't added to it at all). So regenerate grub2
config using grub2-mkconfig.
Apparently new-kernel-pkg does not work for grub2 config with xen
entries (new kernel isn't added to it at all). So regenerate grub2
config using grub2-mkconfig.
dracut (at least in fc13) can use only one directory with firmware, so use the
standard one (from linux-firmware package) because it contains a lot wider set
of files.
dracut (at least in fc13) can use only one directory with firmware, so use the
standard one (from linux-firmware package) because it contains a lot wider set
of files.
libusb crashes (SEGV) on some functions when no USB controller is present. This
results in annoying ABRT popup about colord-sane crash.
Enable dummy USB controller to suppress this bug. This can be reverted when we
enable (some type of) PVUSB in each domain by default.
libusb crashes (SEGV) on some functions when no USB controller is present. This
results in annoying ABRT popup about colord-sane crash.
Enable dummy USB controller to suppress this bug. This can be reverted when we
enable (some type of) PVUSB in each domain by default.
Don't use blkdev program, as isn't installed by default by dracut in FC17.
Actually it isn't necessary to get 'ro' and 'size' parameters, as they can be
read directly from sysfs.
wget downloads new linux-*.sign files and backs up the
existing files as file.1, file.2, etc. This causes false
positives during 'git status' or 'make check'
i.e.
* linux-2.6.38.3.tar.bz2.sign.1
* linux-3.2.7.tar.sign.1
Adding -N causes wget to smartly overwrite as required.
wget downloads new linux-*.sign files and backs up the
existing files as file.1, file.2, etc. This causes false
positives during 'git status' or 'make check'
i.e.
* linux-2.6.38.3.tar.bz2.sign.1
* linux-3.2.7.tar.sign.1
Adding -N causes wget to smartly overwrite as required.
