On 11.03.20 05:15, Samuel Sieb wrote:
On 3/10/20 9:12 PM, sixpack13 wrote:
maybe (?!)
sudo dnf localinstall ./rtl8812au-kmod-4.3.14-2.x86_64.rpm
From "man dnf":
Localinstall Command
Deprecated alias for the Install Command.
Okay, something learned.
THX
--
sixpack13
On 3/10/20 9:12 PM, sixpack13 wrote:
maybe (?!)
sudo dnf localinstall ./rtl8812au-kmod-4.3.14-2.x86_64.rpm
From "man dnf":
Localinstall Command
Deprecated alias for the Install Command.
___
users mailing list --
On 11.03.20 04:32, Jamie Fargen wrote:
When installing an RPM compiled from source, seeing and error and it
doesn't look like the dnf is resolving the kernel package.
# dnf install rtl8812au-kmod-4.3.14-2.x86_64.rpm
kernel-5.5.7-200.fc31.x86_64
Last metadata expiration check: 0:17:25 ago on
On 3/10/20 8:32 PM, Jamie Fargen wrote:
When installing an RPM compiled from source, seeing and error and it
doesn't look like the dnf is resolving the kernel package.
# dnf install rtl8812au-kmod-4.3.14-2.x86_64.rpm
kernel-5.5.7-200.fc31.x86_64
Last metadata expiration check: 0:17:25 ago on
When installing an RPM compiled from source, seeing and error and it
doesn't look like the dnf is resolving the kernel package.
# dnf install rtl8812au-kmod-4.3.14-2.x86_64.rpm
kernel-5.5.7-200.fc31.x86_64
Last metadata expiration check: 0:17:25 ago on Tue 10 Mar 2020 10:09:05 PM
EDT.
Package
(On Tue, 2020-03-10 at 6:56 PM, Patrick wrote)
> ...The recommended way to upgrade is with dnf, ...
That's how I do it, just as the on-line instructions say. I'm not doing
a new installation.
> I think you're mistaken. ...
I hope you're correct! What I originally said was merely a personal
On Tue, 2020-03-10 at 13:58 -0600, home user wrote:
> I plan to upgrade to f31 in about a month. I looked thru the
> instructions for the upgrade. I know that beforehand,
> * I should do a back-up, and
> * that I should download the Fedora Workstation Live image to a USB stick.
Sounds like
> On 11 Mar 2020, at 06:00, Matthew Aguirre
> wrote:
>
> Is there a way to disable unsecured use of port 389? I am using FreeIPA, so
> the client setup uses port 389 with TLS and that is fine, but I'd like to be
> able to not allow unsecured connections as much as possible.
>
> I was able
Also note that if your directory requires authentication before any data will
be returned, you can use the require secure bind option
(http://www.port389.org/docs/389ds/howto/howto-require-secure-binds.html) to
force authentication over SSL first. In effect, no data will be returned over
the
I don't know if this will be of any help to you but here are the instructions
for RHDS 9.
https://access.redhat.com/documentation/en-us/red_hat_directory_server/9.0/html/administration_guide/secureconnections#requiring-secure-connections
On 3/10/20 4:07 PM, Rob Crittenden wrote:
Matthew Aguirre wrote:
Is there a way to disable unsecured use of port 389? I am using
FreeIPA, so the client setup uses port 389 with TLS and that is fine,
but I'd like to be able to not allow unsecured connections as much
as possible.
I was able to
Matthew Aguirre wrote:
> Is there a way to disable unsecured use of port 389? I am using
> FreeIPA, so the client setup uses port 389 with TLS and that is fine,
> but I'd like to be able to not allow unsecured connections as much
> as possible.
>
> I was able to do this in OpenLdap, but haven't
On 10.03.20 20:58, home user wrote:
stand-alone home workstation; f30; dual-boot (with windows-7); Gnome
(mainly).
I plan to upgrade to f31 in about a month. ...
just wait 11 days further, go for F32 and have more fun
No ?
--
sixpack13
___
users
Is there a way to disable unsecured use of port 389? I am using FreeIPA,
so the client setup uses port 389 with TLS and that is fine, but I'd like
to be able to not allow unsecured connections as much as possible.
I was able to do this in OpenLdap, but haven't seen a comparable solution
in
stand-alone home workstation; f30; dual-boot (with windows-7); Gnome
(mainly).
I plan to upgrade to f31 in about a month. I looked thru the
instructions for the upgrade. I know that beforehand,
* I should do a back-up, and
* that I should download the Fedora Workstation Live image to a USB
I always need to run some ximput commands when my bluetooth
mouse connects, I'm wondering if I can automagically detect
the mouse connecting and run the commands so I never have
to remember to do it manually.
The only thing I've found so far that notices a new mouse connection
is messages for the
Nelson,
Yes I confirmed we have a faulty/corrupted build. Still not sure how it
happened, but it will be fixed in the next build. I'm just waiting for
a few more fixes to get committed then I will do new Fedora builds (and
I'll send you the link to it)
Regards,
Mark
On 3/7/20 9:39 PM,
17 matches
Mail list logo
