On fedora 29 , sane-backends 1.0.27.
scanimage -L shows a number of scanners that are no longer connected,
and haven't been used in years.
In what file is this info stored ? Couldn't find any reference under
Is there a way to remove the old scanners from the command line ?
I recall that a few years ago, I somehow checked my Fedora system for disk fragmentation. I also think the tool came with Fedora; i did not have to install it separately. Now, I don't recall the name of the tool that did that. Nor can I find any tool to do that. How do I check my F-28 system for disk fragmentation?
upgrade and running F30 without any trouble.
***a big thanks folks !!!***
I'm runnning baikal to sync calendars, etc. between thunderbird and my android smartphone.
baikal currently doesn't support php 7.3.x (only 7.2.x) !
there are some info's in the wild that workaround's being in worked on (not tested so far: a VM with F29 serves my F30 Thunderbird since yesterday)
Questions, esp. to the php experts:
1. Is it feasibility to temporally "downgrade" ( e.g. F29 packages) to php 7.2 *without* breaking my really smooth running F30 ???
my box is a workstation running httpd only to sync between box/smartphone, so I guess nothing really special
2. any hints ?
I want to build my own installation media (on USB). I would like to include additional packages for an offline installation. However all I could find is this page: https://fedoraproject.org/wiki/How_to_create_a_Fedora_install_ISO_for_tes..., which is horribly out of date. Does anyone know a more current set of steps?
I have tried asking on #fedora-devel, but didn't receive any response yet.
Thanks for any pointers.
Open source is the future. It sets us free.
I have a fedora28 system with apache-2.4.34 and would like to try to
do some more advanced logging to report on bandwidth, users, and other
I've identified this script as part of munin called apache_logger that
requires a change to how apache logs by default.
I've added the following to my virtual domain:
CustomLog "|/usr/share/munin/apache_pipelogger" "%v %p %m %B %D %s"
When reloading apache, it reports the following in the error_log:
[Wed Apr 03 14:35:50.129503 2019] [log_config:warn] [pid 18084:tid
140401642026752] (32)Broken pipe: [client 188.8.131.52:59383] AH00646:
Error writing to |/usr/share/munin/plugins/apache_pipelogger %v %p %m
%B %D %s
Is that the correct format? Perhaps this is the format for an
apache-2.2 script and the one for apache-2.4 is different?
I've tried several variations of this, including setting the LogFormat
and providing a name for it, but it always results in the same "error
The script I am using is here:
Would someone take a look for me and see what I'm doing wrong?
Also, does spawning a new shell for every hit cause a significant
amount of overhead? Should I consider doing this another way? What's
the best way to get stats from apache like bandwidth, users, page
views, error codes, etc in the form of a graph similar to what munin
I have a no-name netbook-style laptop running up-to-date Fedora 29.
When I close the lid, fedora almost always puts the notebook in sleep
mode. Unfortunately, once in a while, it does not. And then my battery
The notebook has a light that indicates sleep by blinking slowly.
Unfortunately, it is not visible while the lid is closed. Bad design.
I could put the notebook to sleep and then close the lid, but this is
quite a bit more fiddly.
Why would Fedora fail to sleep once in a while?
Does anyone else experience this?
How would you go about diagnosing this problem?
(My fear is that this is a firmware bug. I'm pretty sure that there will
never be firmware updates.)
I'm interested in configuring grub to allow selecting different sets of
kernel parameters at boot time. I know I can edit the boot command line
by hand, but this is tedious and error-prone. (An example might be to
choose between the Nouveau and Nvidia drivers by selecting the
appropriate menu entry). And of course I'd want this updated
automatically with each new kernel version (i.e. each kernel would then
have two alternative entries).
How feasible is this?
On every version of Fedora in the last ten years or so, the basic
network configuration is stored in files under /etc/sysconfig. When the
machine boots or I run "systemctl restart network" (or "service network
restart"), those files determine how the network gets set-up. After
that, I can change the configuration with several tools. For example, I
can run something like,
# ip address add 192.168.0.37/24 dev eth0 label eth0:xx
and a new interface alias will be created. But how do I make this alias
resilient so that it will appear automatically after a boot or a network
For a primary interface with a static address, I may be able to add the
information as IPADDR2 (etc) in ifcfg-eth0. But how do I do this if the
primary interface gets its address via DHCP?