| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts the use of the blkid cache.
This cache is a broken concept and should not be used. It's only
intended to be used for LABEL/UUID conversion.
From the upstream maintainer:
<kzak> coling: -p provides more information, the cache is designed for
LABEL/UUID conversion -- and the goal is to avoid the cache if possible
(it's mostly for backward compatibility). The ideal solution is to read
the information from udev DB.
<kzak> coling: man blkid (at least the latest version contains some hint
about this issue)
<kzak> coling: I'd like to learn people to use lsblk -- it's designed
more friendly for end-users as well as for scripts and it reads info
from udev, libblkid is only fallback here.
Longer term we should kill off the use of blkid and perhaps move to
lsblk or some perl-udev (if such a thing exists) usage instead:
<kay> coling: avoid the blkid cache, it is a completely broken idea
<kay> kzak: you should really kill that thing :)
<kzak> kay: I'd like to kill blkid at all and keep it as "to test the
library" binary...
<kay> kzak: tools with options like that talk for their sanity
themselves :) " -g Perform a garbage collection pass on the blkid
cache to remove devices which no longer exist."
<kay> kzak: it's just silly, really silly to ever do that :)
<kay> kzak: yeah, sounds fine to let blkid and its cache die in the long
run
<kzak> lsblk is maintainable and extendable -- fix blkid(8) is
impossible to fix...
This reverts r6891.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
to be manually called from delete_event callback in pure gtk+ cases (eg: mcc)
|
|
|
|
| |
(mga#1812)
|
| |
|
| |
|
|
|
|
| |
format it again (for draklive-install, mga#7822)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Hodgins, mga#8335)
perl_checker didn't find it b/c it saw a chain of module require (but
in reallity it's not here b/c only one or a couple subs actually lazy
load most modules in that chain so the odds of it being done are 0 in
practice :-( )
Xconfig::glx -> detect_devices -> fs::proc_partitions ->
partition_table -> fs -> fs::remote::* -> network::network ->
network::shorewall -> services
|
| |
|
|
|
|
| |
else drakboot crashes
|
| |
|
|
|
|
|
|
| |
(from rosa but cleaned)
(also rosa work is way incomplete: no filling of $booloader and the
like...)
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
#7641):
- not to remove radeon-firmware in draklive-install if a matching card is present
- to install radeon-firmware during install
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
also avoid fork a useless shell
(remove_fonts) fix a potential similar issue
|
|
|
|
| |
process (mga#7403)
|
|
|
|
|
|
| |
rationale: we don't detect anymore printers since commit r245200 on
2008-09-15 ("do not use anymore printerdrake and thus do not detect
printers anymore")
|
| |
|
| |
|
| |
|
|
|
|
| |
mga#7380)
|
| |
|
| |
|
|
|
|
|
|
| |
- crypto: aesni_intel
- input: hid-aureal synaptics_usb
- wifi: qmi_wwan, mwifiex_usb
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
o adapt to usbfs death
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When working out which initrds to regenerate, it is likely that the
same initrd symlink is used by multiple bootloader entries (i.e.
typically the initrd.img symlinked initrd is used by both the current
and the failsafe entry).
If the earlier entry does have vga= but the latter entry does not,
then the latter entry will end up being the value used when
checking the vga= argument when deciding if the initrd
needs to be regenerated.
Thus we only expand the symlink if the vga= value is set
which means that any initrd that needs to be regenerated
definitely will be regenerated.
This will hopefully solve the problem seen on mga2 when
and updated theme package had to be pushed but the initrds
didn't seem to be updated.
|