On 22/03/2021 03:46, Jonathan Dieter wrote:
On Sun, 2021-03-21 at 17:52 +, Jonathan Dieter wrote:
I'm really hoping that I'm missing something obvious here, but I fear
that a good chunk of our Fedora systems will be unbootable if they're
rebooted without disabling raid-check.timer.
Just to
On 02/03/2021 17:30, Alexander Bokovoy wrote:
On ti, 02 maalis 2021, Ed Greshko wrote:
On 02/03/2021 06:03, Lennart Poettering wrote:
On Fr, 26.02.21 21:01, Alexander Bokovoy (aboko...@redhat.com) wrote:
Digital Ocean updates pushed with cloud-init use. Cloud-init does not
have any native
On 02/03/2021 06:03, Lennart Poettering wrote:
On Fr, 26.02.21 21:01, Alexander Bokovoy (aboko...@redhat.com) wrote:
Digital Ocean updates pushed with cloud-init use. Cloud-init does not
have any native support for systemd-resolved. It means it writes
something that systemd-resolved imports int
On 18/02/2021 09:18, Steve Dickson wrote:
On 2/17/21 6:55 PM, Ed Greshko wrote:
On 18/02/2021 05:11, Steve Dickson wrote:
I agree... ignoring syntax error or parsing error just does not seem
like the appropriate thing to do... Error out! Tell me what is broken
so I can fix it!!
Replace the
On 18/02/2021 05:11, Steve Dickson wrote:
I agree... ignoring syntax error or parsing error just does not seem
like the appropriate thing to do... Error out! Tell me what is broken
so I can fix it!!
Replace the "," with a " " in the DNS= entry of /etc/systemd/resolved.conf file.
And if you did
On 17/02/2021 04:24, Marius Schwarz wrote:
Am 16.02.21 um 15:03 schrieb Ed Greshko:
Thanks for the help!
FWIW, I suppose I don't know why a BZ is needed since the
/etc/systemd/resolved.conf has a sample
for the DNS= parameter showing:
I think that "," is received by a dh
On 16/02/2021 21:37, Steve Dickson wrote:
On 2/15/21 9:16 PM, Dominique Martinet wrote:
Steve Dickson wrote on Mon, Feb 15, 2021 at 09:04:52PM -0500:
I think if no IP was successfully parsed the fallback ought to kick in,
so it's a systemd-resolved bug -- do you want to report this upstream or
On 16/02/2021 09:10, Steve Dickson wrote:
On 2/15/21 7:55 PM, Ed Greshko wrote:
On 16/02/2021 08:50, Steve Dickson wrote:
But I think this is the problem...
systemctl start systemd-resolved
systemctl -o cat status systemd-resolved
Starting Network Name Resolution...
Positive Trust Anchors
On 16/02/2021 08:50, Steve Dickson wrote:
But I think this is the problem...
systemctl start systemd-resolved
systemctl -o cat status systemd-resolved
Starting Network Name Resolution...
Positive Trust Anchors:
. IN DS 20326 8 2
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
N
On 16/02/2021 08:35, Steve Dickson wrote:
On 2/15/21 7:24 PM, Ed Greshko wrote:
On 16/02/2021 08:17, Steve Dickson wrote:
On 2/15/21 7:12 PM, Ed Greshko wrote:
On 16/02/2021 06:40, Steve Dickson wrote:
I just updated to latest Fedora 33 and
I no longer have any DNS name solution.
The
I think I may have sent this off-list
On 16/02/2021 08:17, Steve Dickson wrote:
On 2/15/21 7:12 PM, Ed Greshko wrote:
On 16/02/2021 06:40, Steve Dickson wrote:
I just updated to latest Fedora 33 and
I no longer have any DNS name solution.
The network is up... but...
$ pingwww.yahoo.com
On 16/02/2021 08:17, Steve Dickson wrote:
On 2/15/21 7:12 PM, Ed Greshko wrote:
On 16/02/2021 06:40, Steve Dickson wrote:
I just updated to latest Fedora 33 and
I no longer have any DNS name solution.
The network is up... but...
$ pingwww.yahoo.com
ping:www.yahoo.com: Name or service not
On 16/02/2021 06:40, Steve Dickson wrote:
I just updated to latest Fedora 33 and
I no longer have any DNS name solution.
The network is up... but...
$ pingwww.yahoo.com
ping:www.yahoo.com: Name or service not known
I changed nothing!
How would be the bet way to debug this???
What is the outp
On 10/01/2021 09:39, Ian Laurie wrote:
I just updated a VirtualBox Rawhide guest with latest updates which included
the 5.11.0-rc2 kernel and the system hangs on boot (pic attached). The system
was updated a few days ago so was reasonably up to date before today.
Booting the previous kernel 5
On 2020-09-29 21:42, Kevin Fenzi wrote:
> On Tue, Sep 29, 2020 at 01:30:01PM +, Zbigniew Jędrzejewski-Szmek wrote:
>> On Tue, Sep 29, 2020 at 06:26:46AM -0700, Kevin Fenzi wrote:
>>> On Tue, Sep 29, 2020 at 11:12:40AM +, Cuckoo's Calling via devel wrote:
Hello All,
I came acr
On 2020-09-02 11:00, Neal Gompa wrote:
> On Tue, Sep 1, 2020 at 10:51 PM Nico Kadel-Garcia wrote:
>> On Tue, Sep 1, 2020 at 10:21 PM John M. Harris Jr
>> wrote:
>>> On Tuesday, September 1, 2020 7:14:35 AM MST Michael Catanzaro wrote:
On Mon, Aug 31, 2020 at 11:49 pm, John M. Harris Jr
On 2020-09-02 11:06, John M. Harris Jr wrote:
> On Tuesday, September 1, 2020 7:29:44 PM MST Ed Greshko wrote:
>> On 2020-09-02 10:21, John M. Harris Jr wrote:
>>
>>> I don't know what you're talking about here. Am I missing something? Is
>>> this a F3
On 2020-09-02 10:21, John M. Harris Jr wrote:
> I don't know what you're talking about here. Am I missing something? Is this
> a
> F33 Change? Exact content of my /etc/nsswitch:
Is your system an upgrade of an earlier version?
In my case I have an F32 system which has been around for a few year
On 2020-09-01 01:18, Michael Catanzaro wrote:
>
> On Mon, Aug 31, 2020 at 9:36 pm, Ed Greshko wrote:
>> But with that symlink it seems there is no integration with NetworkManager.
>> So, if one has configured (which is
>> the default) to acquire addresses automatica
On 2020-08-31 21:40, John M. Harris Jr wrote:
> On Monday, August 31, 2020 1:22:58 AM MST Ed Greshko wrote:
>> On 2020-08-30 18:30, Andreas Tunek wrote:
>>
>>> On my F33 test system (new install yesterday) I can see my NAS but I can't
>>> connect to it. Coul
On 2020-08-31 21:18, Michael Catanzaro wrote:
> On Mon, Aug 31, 2020 at 1:09 pm, Vitaly Zaitsev via devel
> wrote:
>> You system is not using systemd-resolved.
>
> It mostly is, though, via nss-resolve. Only stuff that uses resolv.conf
> directly is broken and not using resolved, which is
> htt
On 2020-08-30 18:30, Andreas Tunek wrote:
> On my F33 test system (new install yesterday) I can see my NAS but I can't
> connect to it. Could that be due to this change?
Could you me a bit more specific?
I just installed from Fedora-Workstation-Live-x86_64-33-20200829.n.0.iso to a
VM and everyt
On 2020-03-28 08:24, wen rei do wrote:
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
--
The key to getting good answers is to ask good questions.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an ema
23 matches
Mail list logo
