This is an OT question, but one that I am sure someone here will likely know the answer to, given how much help I have received here on such questions in the past.
So, I store e-mails sent by me to others using the "From" field to a folder called "/sent"
So, I use in my .procmailrc:
And it used to work fine. However, recently I have also started forwarding my e-mail from the address: user(a)outlook.com and what is happening is that the e-mail envelope of every forwarded message now contains the header: Resent-From.*user(a)outlook.com so all forwarded e-mail is being saved to the sent folder.
Is it possible to have a double condition? That is something that says that if both Resent-From and From have *user(a)outlook.com, then it should go to the sent-folder. In other words, is it possible to use a AND or OR or Negation condition.
Thanks very much in advance for your time, and also your help and suggestions in answering this question!
This trivial issue has bugged me since I first ran a windows VM:
When windows starts up and plays the silly startup sound. it
sounds absolutely dreadful like it is being clipped and bursts
of static introduced at random times.
Is there any way to get more reliable audio while windows
is busy starting up? Sound is much better after the machine
has fully booted.
Just a trivia question for Christmas :-).
between users. [SOLVED]
On 21Dec2019 10:53, home user <mattisonw(a)comcast.net> wrote:
>In the testing for this thread, I mostly fully signed off one account
>and fully logged in to the other rather than using "su". For renaming
>and "ls" kinds of things, I did use "su". But for viewing,
>screen-capturing, and the localectl and locale commands, I wasn't sure,
>so I did the full logout and login.
>For what is "su" good enough, and for what is the full logout and
>login needed? A full detailed list is impractical, but could someone
>provide some good guiding principles?
It depends solely on what needs initialising.
An su will produce a new shell with the latest environment settings. So
you can test terminal level locale changes etc. If you _invoke_ a new
GUI programme from that shell, it should inherit this stuff too.
A GUI logout/login will initialise the desktop, which tends to happen
before any terminal shell. So if you're fiddling GUI stuff and _not_
invoking programmes from a shell, the thing you've invoking them from
needs to see the changes. For a GUI, that tends to mean restarting the
desktop (since you invoke GUI programmes from desktop
buttons/icons/menus usually). And a logout/login restarts the desktop.
Cameron Simpson <cs(a)cskk.id.au>
My home partition is on a 2T HDD using btrfs
I am reading the material at
but still I am not that clear on some items.
If I want to to add a second 2T drive to work as a mirror (RAID1) it looks
like I do not have to invoke mdadm or anything similar, it seems like btrfs
will handle it all internally. Am I understanding this right?
Also, before I add a new device, do I have to partition the drive or does
btrfs take over all these duties (partitioning, formating) when it adds the
device to the filesystem?
What has been the experience like with such a system?
|O O| pepebuho(a)gmail.com
~~~~ Javier Perez
~~~~ While the night runs
~~~~ toward the day...
m m Pepebuho watches
from his high perch.
i have been having problems upgrading or installing Fedora 31 on an HP
360 Spectre Laptop.
Description of problem: After an upgrade or fresh install to fc31 I get
long delay to X login, then after login I get grey screen. On my
original attempt, it started properly once, I was going to FC32 and it
let me login and I was able to perform an upgrade to FC32. When I didn't
like that I did a fresh install to FC31 and saw the problem. Virtual
terminals were also unavailable. I then did a fresh install of FC30 that
went okay although I think that it's a little slow to get to the login
prompt, but after I login things work okay. I then upgraded to FC31 that
version and saw the same delay and grey screen after login as before. I
then went back to FC30 and I will include some info from FC30
[brian@localhost ~]$ inxi -GxxSMza System: Host: localhost.localdomain
Kernel: 5.3.16-200.fc30.x86_64 x86_64 bits: 64 compiler: gcc v: 9.2.1
rd.luks.uuid=luks-323281ed-242f-40db-85cb-75ab350dbb43 rhgb quiet
Desktop: Gnome 3.32.2 wm: gnome-shell dm: GDM Distro: Fedora release 30
(Thirty) Machine: Type: Convertible System: HP product: HP Spectre x360
Convertible 15-ch0xx v: N/A serial: <filter> Chassis: type: 31 serial:
<filter> Mobo: HP model: 83BA v: 57.20 serial: <filter> UEFI: AMI v:
F.04 date: 01/23/2018 Graphics: Device-1: Intel UHD Graphics 620 vendor:
Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 chip ID:
8086:5917 Device-2: NVIDIA GP108M [GeForce MX150] vendor:
Hewlett-Packard driver: nouveau v: kernel bus ID: 01:00.0 chip ID:
10de:1d10 Display: wayland server: Fedora Project X.org 1.20.5 driver:
nouveau compositor: gnome-shell resolution: 3840x2160~60Hz OpenGL:
renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2) v: 4.5 Mesa
19.1.8 compat-v: 3.0 direct render: Yes Version-Release number of
selected component (if applicable): FC31 How reproducible: Every time.
Steps to Reproduce: 1.Install or upgrade on my laptop 2. 3.
Thanks in advance for any assistance you can provide,
On 12/24/19 2:36 PM, Samuel Sieb wrote:
> On 12/24/19 11:20 AM, Frank McCormick wrote:
>> BTW, systemd-modules-load.service doe not make any mention of
>> directories with lists of kernel modules??
> # cat /usr/lib/systemd/system/systemd-modules-load.service
> Description=Load Kernel Modules
> Documentation=man:systemd-modules-load.service(8) man:modules-load.d(5)
> Before=sysinit.target shutdown.target
> # ls /usr/lib/modules-load.d
> open-vm-tools.conf soundtracker.conf
> # cat /usr/lib/modules-load.d/soundtracker.conf
There are none so blind as those who will not see :)
On 12/24/19 12:57 PM, Samuel Sieb wrote:
> On 12/24/19 8:02 AM, Frank wrote:
>> I am running a freshly updated Fedora 31. I noticed this morning that
>> the systemd-modules-load.service failed. I saw it on boot
>> and later in the journal log.
>> There is no explanation why it failed, just the notification.
> I've seen this for a long time on multiple computers, but haven't
> bothered to take the time to figure it out. Although now that I check
> it, it was successful on this computer. Look in the service file
> /usr/lib/systemd/system/systemd-modules-load.service to see the list of
> directories and check which modules it would be trying to load.
I have since discovered that the problem originates from Grub loading
the wrong kernel which is another problem I have to solve.
I run two Linux distros on this computer (in addition to Windows 10),
Debian Sid and Fedora. I have been installing grub from Debian into
/dev/sda, the main disk. I suspect the problem exists because the Debian
version of update-grub (to create the new grub.cfg file) sorts the
Fedora Kernels in the wrong order, putting the recovery entry first,
then the oldest kernel followed by the newest kernel. So just hitting
the Grub entry for Fedora on booting results (sometimes) in the oldest
kernel, or occasionally the recovery entry.
I'll have to take this up with users on the Debian list.
BTW, systemd-modules-load.service doe not make any mention of
directories with lists of kernel modules??
Sorry for the noise.
I am running a freshly updated Fedora 31. I noticed this morning that
the systemd-modules-load.service failed. I saw it on boot
and later in the journal log.
There is no explanation why it failed, just the notification.
[frank@franklin ~]$ systemctl status systemd-modules-load.service
● systemd-modules-load.service - Load Kernel Modules
(/usr/lib/systemd/system/systemd-modules-load.service; static; vendor
Active: failed (Result: exit-code) since Tue 2019-12-24 10:44:34
EST; 5min ago
Process: 750 ExecStart=/usr/lib/systemd/systemd-modules-load
Main PID: 750 (code=exited, status=1/FAILURE)
How can I debug this ?