On 6/6/23 21:23, Robert McBroom via users wrote:
The flame icon on a message in the Inbox used to send the message
immediately to "Bulk Mail". It has stopped doing that. Messages that the
email provider flags do go to the "Bulk Mail". Now the message has to be
manually trashed. It was very
The flame icon on a message in the Inbox used to send the message
immediately to "Bulk Mail". It has stopped doing that. Messages that the
email provider flags do go to the "Bulk Mail". Now the message has to be
manually trashed. It was very nice to just flag messages and have them
go away.
I just tried 'sudo akmods --force' and it failed. An updated package
nvidia-470xx-kmod-470.182.03-2.fc37
was placed in testing on 27 May. I haven't tried it yet.
fails to compile on f38 kernel 6.3.4
akmod-nvidia-470xx-470.182.03-2.fc38.x86_64
is now good on kernels up to the current
On Thu, 2023-06-01 at 20:56 -0700, Mike Wright wrote:
> Have you requested a PTR record? I use two different hosting companies
> and both of them have accommodated me for whichever VMs I have spun up.
I don't think it's possible. I don't have a virtual machine, it's a
virtually hosted website
On 06/06/2023 19:03, John Pilkington wrote:
On 06/06/2023 18:46, Steve Underwood wrote:
On 02/06/2023 23:54, John Pilkington wrote:
On 02/06/2023 21:49, Robert McBroom via users wrote:
On 5/31/23 15:47, John Pilkington wrote:
On 31/05/2023 20:21, John Pilkington wrote:
On 31/05/2023 18:39,
On 06/06/2023 18:46, Steve Underwood wrote:
On 02/06/2023 23:54, John Pilkington wrote:
On 02/06/2023 21:49, Robert McBroom via users wrote:
On 5/31/23 15:47, John Pilkington wrote:
On 31/05/2023 20:21, John Pilkington wrote:
On 31/05/2023 18:39, home user wrote:
On 5/31/23 10:20 AM, Barry
On 02/06/2023 23:54, John Pilkington wrote:
On 02/06/2023 21:49, Robert McBroom via users wrote:
On 5/31/23 15:47, John Pilkington wrote:
On 31/05/2023 20:21, John Pilkington wrote:
On 31/05/2023 18:39, home user wrote:
On 5/31/23 10:20 AM, Barry Scott wrote:
When there's a new kernel
If the bond is an active/passive (non-LACP) then the older setup
scripts/bonding module would put the mac address for the first
interface it finds on the bond device and on both underlying physical
interfaces and in the bond.
Using the old scripts/bonding module (with LACP) both underlying
Could it be a programming error in 389-ds-base?
After all, the error message we're getting is:
[06/Jun/2023:14:41:05.346079522 +0200] - ERR - slapi_ldap_bind - Could not send
bind request for id [cn=replication manager,cn=config] authentication mechanism
[SIMPLE]: error -1 (Can't contact LDAP
On Mon, 05 Jun 2023 15:14:49 +0200
François Patte wrote:
> Bonjour,
>
> Today I tried to upgrade from fc34 to fc36.
>
> Downloading the package was okay. Problems occur when I agreed to
> system-upgrade-reboot:
> 1- No display... I could only dee the led showing HDD accesses
> 2- After
Hi Brian,
Unfortunately you can't because Cockpit calls the DS CLI tools (dsconf,
dsctl, etc) which must be run as a privileged user in order to work
correctly.
Regards,
Mark
On 6/6/23 7:58 AM, Brian Mattey (UK) wrote:
Hi,
I would like to grant a non-privileged user (cannot sudo to
Once upon a time, lejeczek said:
> To start with the most basic of what I ponder over - basic in my
> mind though I get, that it does not have to be that or
> simple/obvious - is MACSEC with 'bond' as parent or in other words:
> macsec "on" a 'bond' network interface.
> Should such a "thing"
Hi guys.
Looking at macsec I've only started - so go easy on me with
my possibly trivial questions - and write here in hope,
that some of you have expertise to tell...
To start with the most basic of what I ponder over - basic
in my mind though I get, that it does not have to be that or
Actually, trusting the certificate made everything worse.
# trust list | grep ISRG\ Root\ X1
yielded the same certificate twice, and the supplier was then unable to connect
to the consumer (or itself), yielding "unable to get issuer certificate" (so
not only when replicating, but also when
Hi,
I would like to grant a non-privileged user (cannot sudo to root) access to
389-ds configuration in Cockpit. (I've googled a _lot_ for this and can't find
any way to do it).
Thanks,
Brian
___
389-users mailing list --
Sadly, the problem persists after executing "trust anchor .pem" for both
the ISRG Root X1 and Let's Encrypt R3 cert files as extracted from the
fullchain.pem provided by Certbot.
Regards
Jakob
___
389-users mailing list --
Bonjour,
I am following advices given in answering my previous post "issue"
and I get f38 installer.
The installer complains that there is a duplicate UUID on some disks :
parts sde1 and sdf1
That's true! Running blkid gives:
/dev/sde1: UUID="4a28174a-f38b-4938-233f-85f76ce585a8"
Le 2023-06-05 18:20, Patrick O'Callaghan a écrit :
On Mon, 2023-06-05 at 12:41 -0300, George N. White III wrote:
On Mon, Jun 5, 2023 at 10:15 AM François Patte <
francois.pa...@mi.parisdescartes.fr> wrote:
> Bonjour,
>
> Today I tried to upgrade from fc34 to fc36.
>
> Downloading the package
Le 2023-06-05 20:19, Samuel Sieb a écrit :
On 6/5/23 06:14, François Patte wrote:
Today I tried to upgrade from fc34 to fc36.
Downloading the package was okay. Problems occur when I agreed to
system-upgrade-reboot:
What exact commands did you run?
When downloading f36 packages ends, the
19 matches
Mail list logo
