On 6/17/21 9:47 PM, Tim via users wrote:
Tim:
I think if you want to modify *anything* in the zone files, you'll
first need to stop the service then delete their journal files,
before editing them.
Chris Adams:
Or just freeze/thaw them - no need to stop the server, and you should
never delete
On 19/06/2021 12:45, Stephen Morris wrote:
Hi,
I've noticed when trying remediate performance issues in F34 under a vm,
that fedora does not have a swap specification in fstab anymore, but is using,
in my case, and 8GB swap partition in /dev/zram0. Does this mean that if I
create a swap pa
Patrick O'Callaghan:
>> Interesting idea. Mine is this model:
>>
>> https://www.amazon.co.uk/gp/product/B06XYJGDTH/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
>>
>> The power block says its output is 3A at 12V.
>>
>> The drives are both WD model WD10EZEX, (though the label on one
>> says it has
Hi,
I've noticed when trying remediate performance issues in F34 under
a vm, that fedora does not have a swap specification in fstab anymore,
but is using, in my case, and 8GB swap partition in /dev/zram0. Does
this mean that if I create a swap partition of a bigger size and specify
it in
On 17/6/21 05:01, Samuel Sieb wrote:
On 2021-06-16 2:15 a.m., Stephen Morris wrote:
What I'm trying to figure out how to determine is, is the issue
vmware, or its it the driver which may be supplied by Fedora or
vmware (I'm not entirely sure which), or is it the monitor not
honouring the EDID
On 19/06/2021 09:26, Chris Murphy wrote:
I make fstab mount options include:
nofail,noauto,x-systemd.automount
That way it is only mounted on demand, i.e. when the mount point is "touched".
It's also possible to use x-systemd.idle-timeout=300 which will
unmount it after 5 minutes idle.
I'll
I make fstab mount options include:
nofail,noauto,x-systemd.automount
That way it is only mounted on demand, i.e. when the mount point is "touched".
It's also possible to use x-systemd.idle-timeout=300 which will
unmount it after 5 minutes idle.
--
Chris Murphy
_
On 2021-06-18 2:17 p.m., Patrick Dupre wrote:
# ldd /lib64/libk5crypto.so.3 | grep crypto
libcrypto.so.1.1 => /lib64/libcrypto.so.1.1 (0x7fecb90ca000)
libcrypto.so.1.1 => /usr/local/scilab-6.1.0/lib/thirdparty/libcrypto.so.1.1
(0x7f4c37d2d000)
And there is your problem. Try d
On Fri, 18 Jun 2021 at 14:10, Patrick O'Callaghan
wrote:
> On Fri, 2021-06-18 at 09:02 -0300, George N. White III wrote:
> > On Fri, 18 Jun 2021 at 06:50, Patrick O'Callaghan
> >
> > wrote:
> >
> > > On Fri, 2021-06-18 at 08:58 +1000, Cameron Simpson wrote:
> > > > On 17Jun2021 12:15, Patrick O'
> Subject: Re: scilab bin
>
> On 6/18/21 1:38 PM, Patrick Dupre wrote:
> > dnf install krb5-libs
> > Last metadata expiration check: 0:44:00 ago on Fri 18 Jun 2021 09:47:24 PM
> > CEST.
> > Package krb5-libs-1.19.1-8.fc34.x86_64 is already installed.
> > Package krb5-libs-1.19.1-8.fc34.i686 is alr
On 6/18/21 1:38 PM, Patrick Dupre wrote:
dnf install krb5-libs
Last metadata expiration check: 0:44:00 ago on Fri 18 Jun 2021 09:47:24 PM CEST.
Package krb5-libs-1.19.1-8.fc34.x86_64 is already installed.
Package krb5-libs-1.19.1-8.fc34.i686 is already installed.
Dependencies resolved.
Nothing to
On Fri, Jun 18, 2021 at 2:40 PM Patrick Dupre wrote:
> But
>
> scilab-bin: symbol lookup error: /lib64/libk5crypto.so.3: undefined symbol:
> EVP_KDF_ctrl, version OPENSSL_1_1_1b
Take a look here:
https://bugzilla.redhat.com/show_bug.cgi?id=1829790
This seems to mean that scilab has its own ope
>
> On 18/06/2021 04:22, Patrick Dupre wrote:
> > Still trying to run scilab::
> > scilab-bin: symbol lookup error: /lib64/libk5crypto.so.3: undefined symbol:
> > EVP_KDF_ctrl, version OPENSSL_1_1_1b
> >
> > dnf repoquery --whatprovides 'libk5crypto.so.3'
> >
>
> [egreshko@meimei ~]$ dnf repoque
On Fri, Jun 18, 2021, 11:10 AM Patrick O'Callaghan
wrote:
>
> My problem is that one drive comes up almost instantly and the other
> takes 30 seconds. In fact I can live with that. My real gripe is that
> the kernel makes me wait even though the drive is not being accessed.
> If it just wants to
Hi,
I've just started using 5.1 audio on a Fedora 33 machine for the first
time, and I have an issue with pavucontrol. I have pipewire installed on
this machine. If I select the "Output Devices" tab, and unlock the
volume control for the 5.1 audio device, I see 6 controls, with these
labels:
On Fri, 2021-06-18 at 09:02 -0300, George N. White III wrote:
> On Fri, 18 Jun 2021 at 06:50, Patrick O'Callaghan
>
> wrote:
>
> > On Fri, 2021-06-18 at 08:58 +1000, Cameron Simpson wrote:
> > > On 17Jun2021 12:15, Patrick O'Callaghan
> > > wrote:
> > > > On Thu, 2021-06-17 at 07:20 -0300, Georg
Switched to gmail from my provider. Please ignore
--
Frank McCormick in Montreal
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproj
On Fri, 18 Jun 2021 at 10:54, Cisco Tissera
wrote:
> Hello there,
>
> I see, thanks for the explanation, I really appreciate it.
> About yum being a placeholder, it totally makes sense.
> I guess I'll remove yum then, since I've started with dnf, and because i
> am going to be using dnf.
>
This
Hello there,
I see, thanks for the explanation, I really appreciate it.
About yum being a placeholder, it totally makes sense.
I guess I'll remove yum then, since I've started with dnf, and because i am
going to be using dnf.
Thanks again.
Best regards.
francisco.
On Fri, Jun 18, 2021 at 9:25 AM
On Fri, Jun 18, 2021 at 07:25:14AM -0400, Cisco Tissera wrote:
>
> Hello there,
>
> Yes, the switch has happened indeed, since Fedora... 21?
> The point I'm trying to make is, why keep yum, since the switch to dnf has
> already happened?
> Even yum's plugins and extra utilities are still a thing.
> On 18 Jun 2021, at 12:26, Cisco Tissera wrote:
>
>
> Hello there,
>
> Yes, the switch has happened indeed, since Fedora... 21?
> The point I'm trying to make is, why keep yum, since the switch to dnf has
> already happened?
My guess is that it to do with a lot of code expecting yum and
I have not had yum installed on my system for a long time (like five years). I explicitly removed it using dnf erase yum then, and have carried on since without any apparent hitch for at least five years.
HTH, YMMV.
Ranjan
Sent: Friday, June 18, 2021 at 1:25 PM
From: "Cisco Tissera"
T
On Fri, 18 Jun 2021 at 06:50, Patrick O'Callaghan
wrote:
> On Fri, 2021-06-18 at 08:58 +1000, Cameron Simpson wrote:
> > On 17Jun2021 12:15, Patrick O'Callaghan
> > wrote:
> > > On Thu, 2021-06-17 at 07:20 -0300, George N. White III wrote:
> > > > > The technical specifications of the drives sho
Hello there,
Yes, the switch has happened indeed, since Fedora... 21?
The point I'm trying to make is, why keep yum, since the switch to dnf has
already happened?
Even yum's plugins and extra utilities are still a thing.
Best regards.
Francisco.
On Fri, Jun 18, 2021 at 7:10 AM Markus Schönhaber
18.06.21, 12:43 +0200, Cisco Tissera:
> For quite random reasons, I was wondering what would happen if I completely
> removed yum, and only used dnf.
> Is it possible to do that? or would it totally break the system?
> Another question: why keep two package managers, and not switch to dnf and
> ju
Hello everyone,
For quite random reasons, I was wondering what would happen if I completely
removed yum, and only used dnf.
Is it possible to do that? or would it totally break the system?
Another question: why keep two package managers, and not switch to dnf and
just keep dnf?
Sorry if my questio
On Fri, 2021-06-18 at 08:58 +1000, Cameron Simpson wrote:
> On 17Jun2021 12:15, Patrick O'Callaghan
> wrote:
> > On Thu, 2021-06-17 at 07:20 -0300, George N. White III wrote:
> > > > The technical specifications of the drives should mention
> > > > startup
> > > power
> > > management. There may
27 matches
Mail list logo
