On Sat, Dec 17, 2022, 11:25 PM Bill C wrote:
> I tried to copy just the "feature" vobs and such from a DVD iso using
> dvdbackup and I didn't know if anything needed to be done using dvdauthor.
> I have kind of given up on the iso to MP4 idea, though I know it can be
> done. Would an index need
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
On 12/17/22 17:48, Sam Varshavchik wrote:
ToddAndMargo via users writes:
All this silliness started as of Fedora Core 37.
There were no issues with 36.
How certain are you that you had systemd-resolved installed in 36, and
it didn't get pulled in during the upgrade to 37?
This particular
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
ToddAndMargo via users writes:
All this silliness started as of Fedora Core 37.
There were no issues with 36.
How certain are you that you had systemd-resolved installed in 36, and it
didn't get pulled in during the upgrade to 37?
This particular rpm package has a tendency to get pulled
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
> On 17 Dec 2022, at 17:47, home user wrote:
>
> On 12/17/22 10:15 AM, John Pilkington wrote:
>
>> I run it in a konsole (KDE terminal) tab and see a screenful of data
>> refreshed every 10 seconds. Mainly the interest here is on jobs run by user
>> akmods. For me it's just a guide
On Sat, 2022-12-17 at 10:51 -0800, Samuel Sieb wrote:
> I think the point here was to see what different programs say when you
> give it an invalid IP address. In general, what happens is that the
> program tries to do a DNS lookup which fails and you get an answer like
> that, not an
On 12/17/22 13:32, ToddAndMargo via users wrote:
On 12/17/22 12:32, ToddAndMargo via users wrote:
On 12/17/22 12:22, ToddAndMargo via users wrote:
On 12/17/22 11:47, Samuel Sieb wrote:
On 12/17/22 11:40, ToddAndMargo via users wrote:
On 12/16/22 22:54, Samuel Sieb wrote:
On 12/16/22 22:44,
On 12/17/22 12:32, ToddAndMargo via users wrote:
On 12/17/22 12:22, ToddAndMargo via users wrote:
On 12/17/22 11:47, Samuel Sieb wrote:
On 12/17/22 11:40, ToddAndMargo via users wrote:
On 12/16/22 22:54, Samuel Sieb wrote:
On 12/16/22 22:44, ToddAndMargo via users wrote:
On 12/16/22 22:11,
On 12/17/22 12:22, ToddAndMargo via users wrote:
On 12/17/22 11:47, Samuel Sieb wrote:
On 12/17/22 11:40, ToddAndMargo via users wrote:
On 12/16/22 22:54, Samuel Sieb wrote:
On 12/16/22 22:44, ToddAndMargo via users wrote:
On 12/16/22 22:11, Samuel Sieb wrote:
On 12/16/22 21:18,
On 12/17/2022 01:03 PM, home user wrote:
Sorry, That should be "dnf upgrade", not "dnf update".
Doesn't really matter as update is now just another name for upgrade.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an
On 12/17/22 11:47, Samuel Sieb wrote:
On 12/17/22 11:40, ToddAndMargo via users wrote:
On 12/16/22 22:54, Samuel Sieb wrote:
On 12/16/22 22:44, ToddAndMargo via users wrote:
On 12/16/22 22:11, Samuel Sieb wrote:
On 12/16/22 21:18, ToddAndMargo via users wrote:
On 12/16/22 20:23, Mike Wright
On 12/17/22 11:03 AM, Bill C wrote:
I'd there a difference in dnf upgrade and dnf distro-sync? There's a dnf
update too. I usually erase a /var/cache/dnf to clean data.
There are others in the Fedora users list much more knowledgeable about
dnf than am I. I leave it to them to answer.
On
On 12/17/22 12:03, home user wrote:
On 12/17/22 10:45 AM, home user wrote:
On 12/17/22 10:15 AM, John Pilkington wrote:
...
For some time now, I've seen another process/user "mandb" running at
the same time as or after the akmod processes at the end of (sometimes
after) "dnf update".
On 12/17/22 10:45 AM, home user wrote:
On 12/17/22 10:15 AM, John Pilkington wrote:
...
For some time now, I've seen another process/user "mandb" running at the
same time as or after the akmod processes at the end of (sometimes
after) "dnf update".
Sorry, That should be "dnf upgrade", not
On 12/17/22 11:40, ToddAndMargo via users wrote:
On 12/16/22 22:54, Samuel Sieb wrote:
On 12/16/22 22:44, ToddAndMargo via users wrote:
On 12/16/22 22:11, Samuel Sieb wrote:
On 12/16/22 21:18, ToddAndMargo via users wrote:
On 12/16/22 20:23, Mike Wright wrote:
127.0.0.0/8 is the loopback
On 12/16/22 22:54, Samuel Sieb wrote:
On 12/16/22 22:44, ToddAndMargo via users wrote:
On 12/16/22 22:11, Samuel Sieb wrote:
On 12/16/22 21:18, ToddAndMargo via users wrote:
On 12/16/22 20:23, Mike Wright wrote:
127.0.0.0/8 is the loopback address. That means that any IP that
begins with
On 12/17/22 10:51, Samuel Sieb wrote:
On 12/17/22 10:35, Patrick O'Callaghan wrote:
On Sat, 2022-12-17 at 09:46 -0800, Mike Wright wrote:
ping: 127.0.0.631: Name or service not known
Once again: 127.0.0.631 is not a valid IP address. The final octet can
never be greater than 255 (2^8-1).
I
On 12/17/22 10:35, Patrick O'Callaghan wrote:
On Sat, 2022-12-17 at 09:46 -0800, Mike Wright wrote:
ping: 127.0.0.631: Name or service not known
Once again: 127.0.0.631 is not a valid IP address. The final octet can
never be greater than 255 (2^8-1).
I think the point here was to see what
On Sat, 2022-12-17 at 17:15 +, John Pilkington wrote:
> > > See also htop, glances and several others.
> > >
> > > poc
> >
> > Is there something equivalent to atop that provides graphical
> > output?
> > The graphical system monitors that I have (e.g. ksysguard) produce
> > nice
> >
On Sat, 2022-12-17 at 09:46 -0800, Mike Wright wrote:
> ping: 127.0.0.631: Name or service not known
Once again: 127.0.0.631 is not a valid IP address. The final octet can
never be greater than 255 (2^8-1).
poc
___
users mailing list --
I'd there a difference in dnf upgrade and dnf distro-sync? There's a dnf
update too. I usually erase a /var/cache/dnf to clean data.
On Sat, Dec 17, 2022, 1:01 PM Tom Horsley wrote:
> On Sat, 17 Dec 2022 10:45:38 -0700
> home user wrote:
>
> > For some time now, I've seen another process/user
On Sat, 17 Dec 2022 10:45:38 -0700
home user wrote:
> For some time now, I've seen another process/user "mandb" running at the
> same time as or after the akmod processes at the end of (sometimes
> after) "dnf update".
That's updating the man page database the "man" command uses. It only
runs
On 12/17/22 10:15 AM, John Pilkington wrote:
I run it in a konsole (KDE terminal) tab and see a screenful of data
refreshed every 10 seconds. Mainly the interest here is on jobs run by
user akmods. For me it's just a guide showing when the system should be
able to boot without doing complex
On 12/17/22 01:09, Tim via users wrote:
Tim:
[...]
Both are valid addresses.
127.0.0.631 is *unlikely* to be in use, but is valid.
Jeffrey Walton
Huh? Citation, please.
Sorry, mental lapse there. The parts in numerical IP addresses go up
to 255, maximum.
That'll teach me to reply to an
On 12/17/22 10:14 AM, Patrick O'Callaghan wrote:
Is there something equivalent to atop that provides graphical output?
The graphical system monitors that I have (e.g. ksysguard) produce
nice displays, but don't offer all the parameters I'd like to see.
atop has more parameters, but no graphical
On 17/12/2022 16:44, home user wrote:
On 12/16/22 3:11 PM, Patrick O'Callaghan wrote:
$ dnf info atop
...
Description : An advanced interactive monitor for Linux-systems to
view the load on
: system-level and process-level.
: The command atop has some major
On Sat, 2022-12-17 at 09:44 -0700, home user wrote:
> On 12/16/22 3:11 PM, Patrick O'Callaghan wrote:
>
> > $ dnf info atop
> > ...
> > Description : An advanced interactive monitor for Linux-systems to
> > view the load on
> > : system-level and process-level.
> > :
On 12/14/22 8:45 PM, home user wrote:
Last night, I ran "dnf upgrade" in a terminal as root.
It did about 750 items.
After the clean-up phase was done, it started the akmod processing
(compiling).
After a few minutes, still during the akmod work (based on the ksysguard
display), still in
On 12/17/22 12:54 AM, Samuel Sieb wrote:
On 12/16/22 10:33, home user wrote:
I shut down nightly. So I do notice the long time. I hear at least 3
long surges of the cooling fans during shutdown. But I don't know of
a way of knowing what's really going on (the screens are blank).
Since
On 12/16/22 3:11 PM, Patrick O'Callaghan wrote:
$ dnf info atop
...
Description : An advanced interactive monitor for Linux-systems to view the
load on
: system-level and process-level.
: The command atop has some major advantages compared to other
:
On 12/16/22 12:01 PM, Robert McBroom via users wrote:
Current kernel is up to 6.0.12 going from 6.0.5 to current has tracked
without a problem of the drivers with rpmfusion. The change from 5 to 6
is the major kernel change where driver delays typically but not
exclusively occur.
That
On Sat, 2022-12-17 at 14:32 +0100, Roberto Ragusa wrote:
> On 12/17/22 12:17, Patrick O'Callaghan wrote:
> > On Sat, 2022-12-17 at 12:10 +0100, GianPiero Puccioni wrote:
>
> > > I thought that the last octet could not be 0 (address of the
> > > network)
> > > or 255 (broadcast). Is this not the
On 12/17/22 12:17, Patrick O'Callaghan wrote:
On Sat, 2022-12-17 at 12:10 +0100, GianPiero Puccioni wrote:
I thought that the last octet could not be 0 (address of the network)
or 255 (broadcast). Is this not the same for the Loopback?
127.0.0.0/8 refers to the network, not to a specific
On Sat, Dec 17, 2022 at 2:57 AM Peter Boy wrote:
> A Quick Doc article describes the procedure:
> https://docs.fedoraproject.org/en-US/quick-docs/reset-root-password/
>
> We, the Fedora Docs team, are in the process to review and improve the
> Quick Docs articles. We are (unfortunately) not
On Sat, 2022-12-17 at 12:10 +0100, GianPiero Puccioni wrote:
> On 17/12/2022 05:23, Mike Wright wrote:
>
> [snip]
>
> > 127.0.0.0/8 is the loopback address. That means that any IP that
> > begins with
> > 127 is a valid loopback address. The three 0's can each be any
> > number from 0
> >
On 17/12/2022 05:23, Mike Wright wrote:
[snip]
127.0.0.0/8 is the loopback address. That means that any IP that begins with
127 is a valid loopback address. The three 0's can each be any number from 0
through 255.
I thought that the last octet could not be 0 (address of the network) or
Tim:
>> [...]
>> Both are valid addresses.
>>
>> 127.0.0.631 is *unlikely* to be in use, but is valid.
Jeffrey Walton
> Huh? Citation, please.
>
Sorry, mental lapse there. The parts in numerical IP addresses go up
to 255, maximum.
That'll teach me to reply to an email while watching TV!
A Quick Doc article describes the procedure:
https://docs.fedoraproject.org/en-US/quick-docs/reset-root-password/
We, the Fedora Docs team, are in the process to review and improve the Quick
Docs articles. We are (unfortunately) not omniscient IT gods but need support
from Fedora community.
48 matches
Mail list logo
