On Fri, 2022-12-23 at 10:19 +, J.Witvliet--- via users wrote:
> -Original Message-
> From: Patrick O'Callaghan
> Sent: Thursday, December 22, 2022 2:54 PM
> To: users@lists.fedoraproject.org
> Subject: Re: Tip: how to make your own resolv.conf
>
> On Wed, 2022
-Original Message-
From: Patrick O'Callaghan
Sent: Thursday, December 22, 2022 2:54 PM
To: users@lists.fedoraproject.org
Subject: Re: Tip: how to make your own resolv.conf
On Wed, 2022-12-21 at 15:18 -0800, ToddAndMargo via users wrote:
> On 12/21/22 14:28, Patrick O'Callaghan wr
On Thu, 2022-12-22 at 09:01 -0500, Tom Horsley wrote:
> On Thu, 22 Dec 2022 13:53:59 +
> Patrick O'Callaghan wrote:
>
> > compared to, say, Arch
>
> On the other hand, I can't count the number of things I've found
> well documented in the Arch web pages that were utterly confusing
> in every
On Thu, 22 Dec 2022 13:53:59 +
Patrick O'Callaghan wrote:
> compared to, say, Arch
On the other hand, I can't count the number of things I've found
well documented in the Arch web pages that were utterly confusing
in every other particle of documentation I found elsewhere, so it
is good that
On Wed, 2022-12-21 at 15:18 -0800, ToddAndMargo via users wrote:
> On 12/21/22 14:28, Patrick O'Callaghan wrote:
> > Fedora is a bleeding-
> > edge distro for a reason.
>
> That is a common, forgivable misunderstanding.
>
> Fedora is not next to bleeding edge. Fedora has a
> army of testers
> On 21 Dec 2022, at 23:19, ToddAndMargo via users
> wrote:
>
> On 12/21/22 14:28, Patrick O'Callaghan wrote:
>> Fedora is a bleeding-
>> edge distro for a reason.
>
> That is a common, forgivable misunderstanding.
>
> Fedora is not next to bleeding edge. Fedora has a
> army of testers
On 12/21/22 14:28, Patrick O'Callaghan wrote:
Fedora is a bleeding-
edge distro for a reason.
That is a common, forgivable misunderstanding.
Fedora is not next to bleeding edge. Fedora has a
army of testers that keep the junk out that
does not work right.
The only ones I have know the
On Thu, 2022-12-22 at 08:45 +1030, Tim via users wrote:
> Tim:
> > > This is why I don't install a new release over the top of the
> > > old,
> > > you end up with a Rube Goldberg / Heath Robinson contraption
> > > trying
> > > to keep things going.
>
> Patrick O'Callaghan:
> > That only happens
Tim:
>> This is why I don't install a new release over the top of the old,
>> you end up with a Rube Goldberg / Heath Robinson contraption trying
>> to keep things going.
Patrick O'Callaghan:
> That only happens if you don't make sure that your modifications carry
> over into the new version. I
> On 21 Dec 2022, at 19:11, ToddAndMargo via users
> wrote:
>
> This time they disabled named-chroot, but I
> caught it instantly.
Who is they?
I use named-chroot and no one disabled it when I upgraded from f36 to f37.
Barry
___
users mailing
On 12/21/22 11:35, Barry Scott wrote:
On 21 Dec 2022, at 19:11, ToddAndMargo via users
wrote:
This time they disabled named-chroot, but I
caught it instantly.
Who is they?
Fedora's developers.
I use named-chroot and no one disabled it when I upgraded from f36 to f37.
H.
On 12/21/22 07:39, Patrick O'Callaghan wrote:
That only happens if you don't make sure that your modifications carry
over into the new version. I regularly update from one release to the
next, check the .rpmnew and .rpmsave files (using rpmconf) and haven't
had any problems. Of course if you
On Wed, 2022-12-21 at 11:13 +1030, Tim via users wrote:
> On Tue, 2022-12-20 at 21:21 +, Jonathan Billings wrote:
> > Now you have a system that won't do things that most fedora systems
> > do out of the box. You've got a system that might pull in systemd-
> > resolved at some point in the
On 12/20/22 16:43, Tim via users wrote:
On Tue, 2022-12-20 at 21:21 +, Jonathan Billings wrote:
Now you have a system that won't do things that most fedora systems
do out of the box. You've got a system that might pull in systemd-
resolved at some point in the future if a dependency of
On Tue, 2022-12-20 at 21:21 +, Jonathan Billings wrote:
> Now you have a system that won't do things that most fedora systems
> do out of the box. You've got a system that might pull in systemd-
> resolved at some point in the future if a dependency of some other
> package updates, and break
>> On 12/20/22 05:25, Mickey Mouse (A.K.A. His Resplendence) wrote:
On 12/20/22 13:21, Jonathan Billings wrote:
Its not maintainable because instead of figuring out the solution, you hacked
out parts of the OS until you got something that looks something kinda sorta
like what you're used to
On 12/20/22 13:21, Jonathan Billings wrote:
Now you have a system that won't do things that most fedora systems do out of
the box. You've got a system that might pull in systemd-resolved at some point
in the future if a dependency of some other package updates, and break your
setup. You
> On 12/20/22 05:25, Mickey Mouse wrote:
>
>
> It is really easy for me to maintain.
>
> It also gives me breathing room
> to trying and figure out the new mess.
>
> I am missing your point. What part is
> not maintainable?
Now you have a system that won't do things that most fedora systems
On 12/20/22 05:25, Jonathan Billings wrote:
But you're basically setting up an unmaintainable mess, something
It is really easy for me to maintain.
It also gives me breathing room
to trying and figure out the new mess.
I am missing your point. What part is
not maintainable?
My machine
> On 12/19/22 15:55, Mickey Mouse wrote:
>
> Not so far it has not. And it has had opportunities
> out the wazoo to do such:
>
> # cat /etc/resolv.conf
> search acme.local
> nameserver 127.0.0.1
>
> By the way, you missed the part about me
> uninstalling systemd-resolved. Someone
> (a.k.a.
On 12/19/22 17:39, Samuel Sieb wrote:
On 12/19/22 17:05, ToddAndMargo via users wrote:
On 12/19/22 16:02, Tim via users wrote:
Jonathan Billings:
If you are using systemd-resolved, then /etc/resolv.conf should
simply have "nameserver 127.0.0.53"
ToddAndMargo:
It puts it there and things
On 12/19/22 17:05, ToddAndMargo via users wrote:
On 12/19/22 16:02, Tim via users wrote:
Jonathan Billings:
If you are using systemd-resolved, then /etc/resolv.conf should
simply have "nameserver 127.0.0.53"
ToddAndMargo:
It puts it there and things ago foo bar
There's your new hostname,
On 12/19/22 14:01, Tom Horsley wrote:
On Mon, 19 Dec 2022 13:53:13 -0800
Samuel Sieb wrote:
My systems are using a combination of legacy and new configs with no
problems.
If you install f37 from scratch, you have to install
NetworkManager-initscripts-ifcfg-rh.x86_64
to get NetworkManager
On 12/19/22 16:29, Chris Adams wrote:
Once upon a time, Tim said:
But being serious, I did start looking through the man files for the
new networking schemes (man systemd-resolved). And supposedly,
/etc/resolv.conf is a link to /run/systemd/resolve/stub-resolv.conf
And when it is, it controls
On 12/19/22 16:02, Tim via users wrote:
Jonathan Billings:
If you are using systemd-resolved, then /etc/resolv.conf should
simply have "nameserver 127.0.0.53"
ToddAndMargo:
It puts it there and things ago foo bar
There's your new hostname, fubar-a-go-go... ;-)
But being serious, I did
On 12/19/22 15:55, Jonathan Billings wrote:
On Dec 19, 2022, at 17:36, ToddAndMargo via users
wrote:
On 12/19/22 13:02, Jonathan Billings wrote:
I don't understand why you keep calling things "Mickey Mouse and Friends" and
acting like you've solved something. As far as I can understand,
Once upon a time, Tim said:
> But being serious, I did start looking through the man files for the
> new networking schemes (man systemd-resolved). And supposedly,
> /etc/resolv.conf is a link to /run/systemd/resolve/stub-resolv.conf
> And when it is, it controls the file its linked to.
Yeah,
On Mon, 19 Dec 2022 16:05:38 -0800
Samuel Sieb wrote:
> > nmcli connection migrate
> >
> > to move all the ifcfg files to "keyfiles".
>
> Oh, nice! They did implement something for that.
I waited one release cycle to try it in the hopes that
any possible bugs might be resolved by then.
On 12/19/22 14:01, Tom Horsley wrote:
On Mon, 19 Dec 2022 13:53:13 -0800
Samuel Sieb wrote:
My systems are using a combination of legacy and new configs with no
problems.
If you install f37 from scratch, you have to install
NetworkManager-initscripts-ifcfg-rh.x86_64
to get NetworkManager
Jonathan Billings:
>> If you are using systemd-resolved, then /etc/resolv.conf should
>> simply have "nameserver 127.0.0.53"
ToddAndMargo:
> It puts it there and things ago foo bar
There's your new hostname, fubar-a-go-go... ;-)
But being serious, I did start looking through the man files for
On Dec 19, 2022, at 17:36, ToddAndMargo via users
wrote:
>
> On 12/19/22 13:02, Jonathan Billings wrote:
>> I don't understand why you keep calling things "Mickey Mouse and Friends"
>> and acting like you've solved something. As far as I can understand, you
>> renamed /etc/resolv.conf
On 12/19/22 13:02, Jonathan Billings wrote:
I don't understand why you keep calling things "Mickey Mouse and Friends" and
acting like you've solved something. As far as I can understand, you renamed
/etc/resolv.conf (which is normally a symlink) and expect it to work?
As soon as Micky and
On 12/19/22 13:01, Jonathan Billings wrote:
You saw how it fell apart when it put different
DNS servers on different interfaces and that
did not match resolv.conf? And how I kept
over riding my manual configurations.
This hurt me more than a Windows upgrade.
I use Linux to avoid that kind of
On 12/19/22 13:49, Barry wrote:
On 19 Dec 2022, at 19:50, ToddAndMargo via users
wrote:
On 12/19/22 09:57, Barry wrote:
On 18 Dec 2022, at 21:28, Tom Horsley wrote:
On Sun, 18 Dec 2022 21:19:02 +
Barry wrote:
That like my router config. Except I use systemd-networkd not
On Mon, 19 Dec 2022 13:53:13 -0800
Samuel Sieb wrote:
> My systems are using a combination of legacy and new configs with no
> problems.
If you install f37 from scratch, you have to install
NetworkManager-initscripts-ifcfg-rh.x86_64
to get NetworkManager to pay any attention to the old
style
On 12/19/22 13:49, Barry wrote:
On 19 Dec 2022, at 19:50, ToddAndMargo via users
wrote:
On 12/19/22 09:57, Barry wrote:
On 18 Dec 2022, at 21:28, Tom Horsley wrote:
On Sun, 18 Dec 2022 21:19:02 +
Barry wrote:
That like my router config. Except I use systemd-networkd not
> On 19 Dec 2022, at 19:50, ToddAndMargo via users
> wrote:
>
> On 12/19/22 09:57, Barry wrote:
On 18 Dec 2022, at 21:28, Tom Horsley wrote:
>>>
>>> On Sun, 18 Dec 2022 21:19:02 +
>>> Barry wrote:
>>>
That like my router config. Except I use systemd-networkd not
On 12/19/22 12:45, Tom Horsley wrote:
On Mon, 19 Dec 2022 12:12:44 -0800
Samuel Sieb wrote:
Which gui are you using? I use nm-connection-editor and have had no
issues with any network types I've setup. Which buttons are you finding
disabled?
That's the gui I was using. According to my old
I don't understand why you keep calling things "Mickey Mouse and Friends" and
acting like you've solved something. As far as I can understand, you renamed
/etc/resolv.conf (which is normally a symlink) and expect it to work?
___
users mailing list --
> You saw how it fell apart when it put different
> DNS servers on different interfaces and that
> did not match resolv.conf? And how I kept
> over riding my manual configurations.
>
> This hurt me more than a Windows upgrade.
> I use Linux to avoid that kind of nonsense.
I'm not sure how
On Mon, 19 Dec 2022 12:12:44 -0800
Samuel Sieb wrote:
> Which gui are you using? I use nm-connection-editor and have had no
> issues with any network types I've setup. Which buttons are you finding
> disabled?
That's the gui I was using. According to my old notes I could
never figure out how
On 12/19/22 12:07, Tom Horsley wrote:
It took a long time to define all my network stuff correctly,
and I found I could only do it with the nmcli command because
the GUI provided is utterly useless. It leaves buttons I want to
push disabled, and won't tell you why they are disabled.
Which gui
On Mon, 19 Dec 2022 11:49:26 -0800
ToddAndMargo via users wrote:
> I have all my network configured in
> /etc/sysconfig/network-scripts/
> which is probably were most of the issue lies
Those ifcfg files aren't even supported in a fresh install
of fedora these days. As attempting to avoid
On 12/19/22 02:03, Peter Boy wrote:
Am 18.12.2022 um 09:24 schrieb ToddAndMargo via users
:
On Sat, 2022-12-17 at 16:38 -0800, ToddAndMargo via users wrote:
If you are tired of all the bugs and Micky Mouse
surrounding /etc/resolv.conf, here is how to make
your own that Micky can't alter:
On 12/19/22 09:57, Barry wrote:
On 18 Dec 2022, at 21:28, Tom Horsley wrote:
On Sun, 18 Dec 2022 21:19:02 +
Barry wrote:
That like my router config. Except I use systemd-networkd not networkmanager.
Its been stable over lots of fedora releases.
Right up till the release when they
On 12/18/22 23:08, Samuel Sieb wrote:
Do you really want to do this?
Yes I do.
I don't know about "those" people, but one server of mine has 12
interfaces including physical, vlans, vpns, and VMs and I have no
problems with it using only NetworkManager. I did override the
resolv.conf
> On 18 Dec 2022, at 21:28, Tom Horsley wrote:
>
> On Sun, 18 Dec 2022 21:19:02 +
> Barry wrote:
>
>> That like my router config. Except I use systemd-networkd not networkmanager.
>> Its been stable over lots of fedora releases.
>
> Right up till the release when they decide to
> Am 18.12.2022 um 09:24 schrieb ToddAndMargo via users
> :
>
>
>> On Sat, 2022-12-17 at 16:38 -0800, ToddAndMargo via users wrote:
>>> If you are tired of all the bugs and Micky Mouse
>>> surrounding /etc/resolv.conf, here is how to make
>>> your own that Micky can't alter:
>
>
> I do not
On 12/18/22 22:37, ToddAndMargo via users wrote:
On 12/18/22 18:00, Samuel Sieb wrote:
On 12/18/22 17:57, ToddAndMargo via users wrote:
On 12/18/22 17:10, Samuel Sieb wrote:
On 12/18/22 15:34, ToddAndMargo via users wrote:
Chuckle. All is took was giving the developers a
"doggy chew toy"
On 12/18/22 18:00, Samuel Sieb wrote:
On 12/18/22 17:57, ToddAndMargo via users wrote:
On 12/18/22 17:10, Samuel Sieb wrote:
On 12/18/22 15:34, ToddAndMargo via users wrote:
Chuckle. All is took was giving the developers a
"doggy chew toy" (fake resolv.conf) to distract
them from messing up
On 12/18/22 17:57, ToddAndMargo via users wrote:
On 12/18/22 17:10, Samuel Sieb wrote:
On 12/18/22 15:34, ToddAndMargo via users wrote:
Chuckle. All is took was giving the developers a
"doggy chew toy" (fake resolv.conf) to distract
them from messing up my networking and all suddenly
worked.
On 12/18/22 17:10, Samuel Sieb wrote:
On 12/18/22 15:34, ToddAndMargo via users wrote:
Chuckle. All is took was giving the developers a
"doggy chew toy" (fake resolv.conf) to distract
them from messing up my networking and all suddenly
worked.
Clearly you missed the documentation that that's
On 12/18/22 15:34, ToddAndMargo via users wrote:
Chuckle. All is took was giving the developers a
"doggy chew toy" (fake resolv.conf) to distract
them from messing up my networking and all suddenly
worked.
Clearly you missed the documentation that that's how to do it.
The must think
On 12/18/22 13:42, Felix Miata wrote:
Tom Horsley composed on 2022-12-18 16:27 (UTC-0500):
On Sun, 18 Dec 2022 21:19:02 + Barry wrote:
That like my router config. Except I use systemd-networkd not networkmanager.
Its been stable over lots of fedora releases.
Right up till the release
On 12/18/22 13:54, Samuel Sieb wrote:
On 12/17/22 16:38, ToddAndMargo via users wrote:
If you are tired of all the bugs and Micky Mouse
surrounding /etc/resolv.conf, here is how to make
your own that Micky can't alter:
Your problem appears to be that you're trying to configure your system
On 12/18/22 06:22, Roger Heflin wrote:
From what I can tell they developers expect everyone to do the config
in exactly one way.
If you do the config differently (ie the old way, and if dns is not
configured/defined I assume from dhcp and/or directly in the Network
manager config), then
On 12/17/22 16:38, ToddAndMargo via users wrote:
If you are tired of all the bugs and Micky Mouse
surrounding /etc/resolv.conf, here is how to make
your own that Micky can't alter:
Your problem appears to be that you're trying to configure your system
outside of the normal tools to do so.
Tom Horsley composed on 2022-12-18 16:27 (UTC-0500):
> On Sun, 18 Dec 2022 21:19:02 + Barry wrote:
>> That like my router config. Except I use systemd-networkd not networkmanager.
>> Its been stable over lots of fedora releases.
> Right up till the release when they decide to eradicate it
>
On Sun, 18 Dec 2022 21:19:02 +
Barry wrote:
> That like my router config. Except I use systemd-networkd not networkmanager.
> Its been stable over lots of fedora releases.
Right up till the release when they decide to eradicate it
because everyone must use NetworkManager :-).
That's why I
> On 18 Dec 2022, at 08:25, ToddAndMargo via users
> wrote:
>
> On 12/17/22 19:24, Tim via users wrote:
>>> On Sat, 2022-12-17 at 16:38 -0800, ToddAndMargo via users wrote:
>>> If you are tired of all the bugs and Micky Mouse
>>> surrounding /etc/resolv.conf, here is how to make
>>> your own
>From what I can tell they developers expect everyone to do the config in
exactly one way.
If you do the config differently (ie the old way, and if dns is not
configured/defined I assume from dhcp and/or directly in the Network
manager config), then the software rewrites the file with a valid
On 12/17/22 19:24, Tim via users wrote:
On Sat, 2022-12-17 at 16:38 -0800, ToddAndMargo via users wrote:
If you are tired of all the bugs and Micky Mouse
surrounding /etc/resolv.conf, here is how to make
your own that Micky can't alter:
What I don't get is *why* it does this interference when
On Sat, 2022-12-17 at 16:38 -0800, ToddAndMargo via users wrote:
> If you are tired of all the bugs and Micky Mouse
> surrounding /etc/resolv.conf, here is how to make
> your own that Micky can't alter:
What I don't get is *why* it does this interference when you've either
manually configured
ToddAndMargo via users composed on 2022-12-17 17:40 (UTC-0800):
> Felix Miata wrote:
>> All my current Fedora
>> installations have been migrated to using systemd-network. They don't need
>> "managing".
> Details please!
Largely copied from:
You have to love developers erroring out on boot because they cannot update
resolv.conf.
I have written enough code to evaluate errors and report minor errors and
not give up. If you give up on all errors the system is not going to be
very robust.
On Sat, Dec 17, 2022 at 8:13 PM Tom Horsley
On Sat, 17 Dec 2022 19:30:32 -0600
Roger Heflin wrote:
> Add a chattr +i /etc/resolv.conf as the last step to be save. You will
> have to -i it if you want to change the file later.
That may work on Fedora, but the last time I tried it on Ubuntu, the system
refused to boot past trying to
On 12/17/22 17:34, Felix Miata wrote:
Tom Horsley composed on 2022-12-17 19:54 (UTC-0500):
All my current Fedora
installations have been migrated to using systemd-network. They don't need
"managing".
Details please!
___
users mailing list --
On 12/17/22 17:30, Roger Heflin wrote:
Add a chattr +i /etc/resolv.conf as the last step to be save. You will
have to -i it if you want to change the file later.
I tried that. I does not work on a link.
I threw that on the source file it links to.
Micky and Friends found a way around it.
Tom Horsley composed on 2022-12-17 19:54 (UTC-0500):
> On Sat, 17 Dec 2022 16:38:43 -0800 ToddAndMargo wrote:
>> 3) create your own resolv.conf file
> Not good enough. In the /etc/NetworkManager/NetworkManager.conf
> file under the "[main]" section add a line like so:
> [main]
> dns=none
>
Add a chattr +i /etc/resolv.conf as the last step to be save. You will
have to -i it if you want to change the file later.
On Sat, Dec 17, 2022 at 7:05 PM ToddAndMargo via users <
users@lists.fedoraproject.org> wrote:
> On 12/17/22 16:54, Tom Horsley wrote:
> > On Sat, 17 Dec 2022 16:38:43
On 12/17/22 16:54, Tom Horsley wrote:
On Sat, 17 Dec 2022 16:38:43 -0800
ToddAndMargo via users wrote:
3) create your own resolv.conf file
Not good enough. In the /etc/NetworkManager/NetworkManager.conf
file under the "[main]" section add a line like so:
[main]
dns=none
Otherwise a DHCP
On Sat, 17 Dec 2022 16:38:43 -0800
ToddAndMargo via users wrote:
> 3) create your own resolv.conf file
Not good enough. In the /etc/NetworkManager/NetworkManager.conf
file under the "[main]" section add a line like so:
[main]
dns=none
Otherwise a DHCP lease renewal will replace resolv.conf yet
Hi All,
If you are tired of all the bugs and Micky Mouse
surrounding /etc/resolv.conf, here is how to make
your own that Micky can't alter:
-T
How to make your own permanent entries in /etc/resolv.conf
1) remove resolvconf and systemd-resolved
# dnf remove resolvconf systemd-resolved
73 matches
Mail list logo
