virt-viewer vs virt-manager for sound
Hi, I'm successfully using virt-viewer to display a Fedora 40 KVM running on my Fedora 40 host. The one problem I have is that sound from the KVM only works in virt-manager and not in virt-viewer. If I passthrough my headset to the KVM, sound works fine in virt- viewer. Otherwise, I don't hear anything from my speakers, unless I use virt-manager. Is there a plugin or some configuration parameter I'm missing that would make sound work in virt-viewer without having to passthrough my headset? -- Ranbir -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: What is Castor ? Att.Jonathan Billings.
On 5/8/24 1:13 PM, John Pilkington wrote: On 08/05/2024 20:13, Samuel Sieb wrote: On 5/8/24 10:50 AM, John Pilkington wrote: The harware was working well, before my recent upgrades from f38, briefly to f39 and now to f40. Then I was using the rpmfusion 470xx builds of the nvidia legacy drivers. Now the dual-boot box has no nvidia or nouveau rpms installed (rpm -qa) although I suppose bits of config might remain; inxi still finds nvidia traces: Nouveau is included with the kernel, it doesn't have its own package. xorg-x11-drv-nouveau is supplied by fedora, but I was told that the kernel driver was more up to date, so I removed the fformer. xorg-x11-drv-nouveau is the xorg driver that uses (and requires) the kernel driver. You need both. llvmpipe means it's using software 3D rendering because it doesn't have a 3d hardware driver. I don't think I want 3D KDE/wayland uses 3D rendering. API: Vulkan v: 1.3.280 drivers: N/A surfaces: xcb,xlib,wayland $ sudo dmesg | less [ 0.00] Command line: BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.8.8-300.fc40.x86_64 root=/dev/mapper/fedora_localhost--live-root ro rd.driver.blacklist=nvidia modprobe.blacklist=nvidia nomodeset resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet rd.driver.blacklist=nvidia modprobe.blacklist=nvidia nomodeset There are a lot of duplicates in that list. If you include "nomodeset", then you'll be using the lowest common factor display options. Is there a reason you don't want to use the rpmfusion drivers? It appears that nouveau isn't working for your system, or else something is mixed up. You could check the logs for a previous boot that didn't work. I have happily used the rpmfusion builds of 470xx until a few weeks ago; but it was said that wayland support was missing, and for some time akmods failed to build anyway. I hoped to be able to use the reverse-engineered FOSS drivers. And a few days ago, after reverting to 470xx, kwin_wayland appeared to be running 4 cpu cores at 90% and the mouse was unusable. As far as I know, the NVidia drivers have had Wayland support for a long time. That CPU usage is likely if you're using software 3D rendering. You need to sort out what you have installed. On the linux-only box I have nvidia-gpu-firmware installed. It may not be loading (MythTV says vdpau isn't available) but that system currently does the jobs that I want. My apologies, by the way, for what looks like a hijack. Yes, you definitely should have started a new thread. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: What is Castor ? Att.Jonathan Billings.
On 08/05/2024 20:13, Samuel Sieb wrote: On 5/8/24 10:50 AM, John Pilkington wrote: The harware was working well, before my recent upgrades from f38, briefly to f39 and now to f40. Then I was using the rpmfusion 470xx builds of the nvidia legacy drivers. Now the dual-boot box has no nvidia or nouveau rpms installed (rpm -qa) although I suppose bits of config might remain; inxi still finds nvidia traces: Nouveau is included with the kernel, it doesn't have its own package. xorg-x11-drv-nouveau is supplied by fedora, but I was told that the kernel driver was more up to date, so I removed the fformer. ohn@FedWin4c1:~$ inxi -G Graphics: Device-1: NVIDIA GK208B [GeForce GT 710] driver: N/A Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.6 compositor: kwin_wayland driver: X: loaded: nvidia This is the xorg nvidia drive, but I assume it's not working if the kernel driver isn't loaded. unloaded: fbdev,modesetting,nouveau,vesa gpu: N/A resolution: 800x600 API: EGL v: 1.5 drivers: kms_swrast,swrast platforms: gbm,wayland,x11,surfaceless,device API: OpenGL v: 4.5 vendor: mesa v: 24.0.6 renderer: llvmpipe (LLVM 18.1.1 256 bits) llvmpipe means it's using software 3D rendering because it doesn't have a 3d hardware driver. I don't think I want 3D API: Vulkan v: 1.3.280 drivers: N/A surfaces: xcb,xlib,wayland $ sudo dmesg | less [ 0.00] Command line: BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.8.8-300.fc40.x86_64 root=/dev/mapper/fedora_localhost--live-root ro rd.driver.blacklist=nvidia modprobe.blacklist=nvidia nomodeset resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet rd.driver.blacklist=nvidia modprobe.blacklist=nvidia nomodeset There are a lot of duplicates in that list. If you include "nomodeset", then you'll be using the lowest common factor display options. Is there a reason you don't want to use the rpmfusion drivers? It appears that nouveau isn't working for your system, or else something is mixed up. You could check the logs for a previous boot that didn't work. I have happily used the rpmfusion builds of 470xx until a few weeks ago; but it was said that wayland support was missing, and for some time akmods failed to build anyway. I hoped to be able to use the reverse-engineered FOSS drivers. And a few days ago, after reverting to 470xx, kwin_wayland appeared to be running 4 cpu cores at 90% and the mouse was unusable. On the linux-only box I have nvidia-gpu-firmware installed. It may not be loading (MythTV says vdpau isn't available) but that system currently does the jobs that I want. My apologies, by the way, for what looks like a hijack. John -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: What is Castor ? Att.Jonathan Billings.
On 5/8/24 10:50 AM, John Pilkington wrote: The harware was working well, before my recent upgrades from f38, briefly to f39 and now to f40. Then I was using the rpmfusion 470xx builds of the nvidia legacy drivers. Now the dual-boot box has no nvidia or nouveau rpms installed (rpm -qa) although I suppose bits of config might remain; inxi still finds nvidia traces: Nouveau is included with the kernel, it doesn't have its own package. ohn@FedWin4c1:~$ inxi -G Graphics: Device-1: NVIDIA GK208B [GeForce GT 710] driver: N/A Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.6 compositor: kwin_wayland driver: X: loaded: nvidia This is the xorg nvidia drive, but I assume it's not working if the kernel driver isn't loaded. unloaded: fbdev,modesetting,nouveau,vesa gpu: N/A resolution: 800x600 API: EGL v: 1.5 drivers: kms_swrast,swrast platforms: gbm,wayland,x11,surfaceless,device API: OpenGL v: 4.5 vendor: mesa v: 24.0.6 renderer: llvmpipe (LLVM 18.1.1 256 bits) llvmpipe means it's using software 3D rendering because it doesn't have a 3d hardware driver. API: Vulkan v: 1.3.280 drivers: N/A surfaces: xcb,xlib,wayland $ sudo dmesg | less [ 0.00] Command line: BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.8.8-300.fc40.x86_64 root=/dev/mapper/fedora_localhost--live-root ro rd.driver.blacklist=nvidia modprobe.blacklist=nvidia nomodeset resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet rd.driver.blacklist=nvidia modprobe.blacklist=nvidia nomodeset There are a lot of duplicates in that list. If you include "nomodeset", then you'll be using the lowest common factor display options. Is there a reason you don't want to use the rpmfusion drivers? It appears that nouveau isn't working for your system, or else something is mixed up. You could check the logs for a previous boot that didn't work. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: What is Castor ? Att.Jonathan Billings.
On 08/05/2024 17:54, Roger Heflin wrote:
On Wed, May 8, 2024 at 5:09 AM John Pilkington wrote:
On 08/05/2024 10:18, Tim via users wrote:
On Tue, 2024-05-07 at 17:36 -0400, Jonathan Billings wrote:
Some home router/gateways will remember the hostname a system used as
part of their network, and when handing out the same IP to a new
host, re-uses the saved hostname.
I've yet to come across a home gateway that handles name resolution,
they just dole out numerical IPs from their DHCP server, it also seems
to be a bit of a rarity for a client to accept a hostname that a DHCP
server does supply (if it does). DHCP clients can also request the
DHCP server lets them use their own hostname, and that's often ignored,
too.
More often than not, a client would to a reverse DNS look-up on its
assigned IP to see what domain/hostname is associated with that IP
(which could be a DNS query, but first it looks in the hosts file).
Not everyone has a DNS server, or a configurable one, nor adjusts their
hosts file (often fighting with Network Mangler over it). So:
Set your preferred hostname either in GNOME Settings (or whatever
DE’s settings) or with hostnamectl.
Which stores a setting somewhere naming itself consistently, whatever
IP address you get given.
This can get messy if you get assigned different numerical IPs from
time to time.
It occurs to me that my new 'dual-boot' problems with F40 KDE might be
related to this, but I'm not clear how I could test it. I've posted
both here and on the kde list.
I have two screen-devices, HDMI tv and vga monitor. By default booting
is to Windows, but 'escape' early on goes to an HP-provided
boot-selection sequence and grub.
Choosing "modesetting" starts booting with both screens active, but
freezes shortly after a cursor appears.
"nomodeset" gives a usable system, but with the vga screen never active
and final HDMI resolution fixed at 800x600.
Could this perhaps be a conflict of hostnames set at power-on and by Fedora?
John P
No.
Whatever the hostname is it really does not matter for booting or not.
The fact that nomodeset works tells me that the graphics driver in the
kernel is unable to handle your card and/or monitors in some critical
way.
What kind of vga/video card do you have?
Thanks, Tim and Roger, for both these replies.
The harware was working well, before my recent upgrades from f38,
briefly to f39 and now to f40. Then I was using the rpmfusion 470xx
builds of the nvidia legacy drivers. Now the dual-boot box has no
nvidia or nouveau rpms installed (rpm -qa) although I suppose bits of
config might remain; inxi still finds nvidia traces:
{{{
ohn@FedWin4c1:~$ inxi -G
Graphics:
Device-1: NVIDIA GK208B [GeForce GT 710] driver: N/A
Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.6
compositor: kwin_wayland driver: X: loaded: nvidia
unloaded: fbdev,modesetting,nouveau,vesa gpu: N/A resolution: 800x600
API: EGL v: 1.5 drivers: kms_swrast,swrast
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.5 vendor: mesa v: 24.0.6 renderer: llvmpipe (LLVM 18.1.1
256 bits)
API: Vulkan v: 1.3.280 drivers: N/A surfaces: xcb,xlib,wayland
$ sudo dmesg | less
[0.00] Command line:
BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.8.8-300.fc40.x86_64
root=/dev/mapper/fedora_localhost--live-root ro
rd.driver.blacklist=nvidia modprobe.blacklist=nvidia nomodeset
resume=/dev/mapper/fedora_localhost--live-swap
rd.lvm.lv=fedora_localhost-live/root
rd.lvm.lv=fedora_localhost-live/swap rhgb quiet
rd.driver.blacklist=nvidia modprobe.blacklist=nvidia nomodeset
Mose variations of this give a frozen system.
}}}
John
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: What is Castor ? Att.Jonathan Billings.
On Wed, May 8, 2024 at 5:09 AM John Pilkington wrote: > > On 08/05/2024 10:18, Tim via users wrote: > > On Tue, 2024-05-07 at 17:36 -0400, Jonathan Billings wrote: > >> Some home router/gateways will remember the hostname a system used as > >> part of their network, and when handing out the same IP to a new > >> host, re-uses the saved hostname. > > > > I've yet to come across a home gateway that handles name resolution, > > they just dole out numerical IPs from their DHCP server, it also seems > > to be a bit of a rarity for a client to accept a hostname that a DHCP > > server does supply (if it does). DHCP clients can also request the > > DHCP server lets them use their own hostname, and that's often ignored, > > too. > > > > More often than not, a client would to a reverse DNS look-up on its > > assigned IP to see what domain/hostname is associated with that IP > > (which could be a DNS query, but first it looks in the hosts file). > > > > Not everyone has a DNS server, or a configurable one, nor adjusts their > > hosts file (often fighting with Network Mangler over it). So: > > > >> Set your preferred hostname either in GNOME Settings (or whatever > >> DE’s settings) or with hostnamectl. > > > > Which stores a setting somewhere naming itself consistently, whatever > > IP address you get given. > > > > This can get messy if you get assigned different numerical IPs from > > time to time. > > It occurs to me that my new 'dual-boot' problems with F40 KDE might be > related to this, but I'm not clear how I could test it. I've posted > both here and on the kde list. > > I have two screen-devices, HDMI tv and vga monitor. By default booting > is to Windows, but 'escape' early on goes to an HP-provided > boot-selection sequence and grub. > > Choosing "modesetting" starts booting with both screens active, but > freezes shortly after a cursor appears. > > "nomodeset" gives a usable system, but with the vga screen never active > and final HDMI resolution fixed at 800x600. > > Could this perhaps be a conflict of hostnames set at power-on and by Fedora? > > John P No. Whatever the hostname is it really does not matter for booting or not. The fact that nomodeset works tells me that the graphics driver in the kernel is unable to handle your card and/or monitors in some critical way. What kind of vga/video card do you have? -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: What is Castor ? Att.Jonathan Billings.
On Wed, 2024-05-08 at 11:08 +0100, John Pilkington wrote: > It occurs to me that my new 'dual-boot' problems with F40 KDE might be > related to this, but I'm not clear how I could test it. I've posted > both here and on the kde list. > > I have two screen-devices, HDMI tv and vga monitor. By default booting > is to Windows, but 'escape' early on goes to an HP-provided > boot-selection sequence and grub. > > Choosing "modesetting" starts booting with both screens active, but > freezes shortly after a cursor appears. > > "nomodeset" gives a usable system, but with the vga screen never active > and final HDMI resolution fixed at 800x600. > > Could this perhaps be a conflict of hostnames set at power-on and by Fedora? I wouldn't have thought so (re DNS, IPs, & DHCP). Video output (other than networked KVM kind of things) is direct hardware to monitor, no network should be involved. I don't recall you mentioning KVM, though could have forgotten. Normally, screen set up is long before networking starts. Manual modesetting overrides the OS automatically picking a graphics mode, to some degree. Normally a monitor identifies itself, and the graphics system works out a list of compatible modes that the monitor and the graphics card can both use, and picks the highest resolution possible with the fastest refresh rate. If you have a monitor that doesn't identify itself, or doesn't do it properly (and some don't), or your graphic card is just as bad at it, than manual overrides is the way to go. I seem to remember it was Tom Horsley who had a website page detailing his battles with such things. Hardware KVMs can have the same problems with display ID data, they may have a broken implementation of it. Or only support one mode. Or, alternatively, they could be a solution, forcing a mode that works for you. If you simply prefer a different graphics mode (different scan/refresh rates, different resolutions), then that should be possible to select after you've booted up with the display settings. 800 by 600 is a bit nasty. While it may produce a screen size that some people want, many GUIs expect bigger screen dimensions and don't fit, or you're left with a looking-through-a-keyhole view of them. This EDID info is sent over different wires (DDC) in the video connector than the picture signal. It is possible to have broken pins in the plugs or sockets, or wiring in the cable, that stops this info. If the cable can be completely unplugged from monitor *and* PC, it may be worth trying another. And sometimes a clean toothbrush scrub of the connector contacts fixes problems up. -- NB: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the list. The following system info data is generated fresh for each post: uname -rsvp Linux 6.2.15-100.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 11 16:51:53 UTC 2023 x86_64 -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Who moved my journald.conf?
On Wed, 2024-05-08 at 12:25 +0200, Michael Schwendt wrote: > On Wed, 08 May 2024 10:49:12 +0100, Patrick O'Callaghan wrote: > > > As stated earlier, it hasn't been modified by me. > > > > > What is in your /etc/systemd/journald.conf file compared with the > > > default in /usr/lib/systemd/journald.conf? > > > > They are identical except for comments: > > That proves my point. The file contents don't come from within the > systemd > package where the file is just a %ghost. Then it must have come from some previous iteration of the package. I note that it has been there a long time: $ ls -l --time=creation /etc/systemd/journald.conf /usr/lib/systemd/journald.conf -rw-r--r--. 1 root root 1282 Jul 16 2022 /etc/systemd/journald.conf -rw-r--r--. 1 root root 1406 Apr 24 12:36 /usr/lib/systemd/journald.conf poc -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Who moved my journald.conf?
On Wed, 08 May 2024 10:49:12 +0100, Patrick O'Callaghan wrote: > As stated earlier, it hasn't been modified by me. > > > What is in your /etc/systemd/journald.conf file compared with the > > default in /usr/lib/systemd/journald.conf? > > They are identical except for comments: That proves my point. The file contents don't come from within the systemd package where the file is just a %ghost. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: What is Castor ? Att.Jonathan Billings.
On 08/05/2024 10:18, Tim via users wrote: On Tue, 2024-05-07 at 17:36 -0400, Jonathan Billings wrote: Some home router/gateways will remember the hostname a system used as part of their network, and when handing out the same IP to a new host, re-uses the saved hostname. I've yet to come across a home gateway that handles name resolution, they just dole out numerical IPs from their DHCP server, it also seems to be a bit of a rarity for a client to accept a hostname that a DHCP server does supply (if it does). DHCP clients can also request the DHCP server lets them use their own hostname, and that's often ignored, too. More often than not, a client would to a reverse DNS look-up on its assigned IP to see what domain/hostname is associated with that IP (which could be a DNS query, but first it looks in the hosts file). Not everyone has a DNS server, or a configurable one, nor adjusts their hosts file (often fighting with Network Mangler over it). So: Set your preferred hostname either in GNOME Settings (or whatever DE’s settings) or with hostnamectl. Which stores a setting somewhere naming itself consistently, whatever IP address you get given. This can get messy if you get assigned different numerical IPs from time to time. It occurs to me that my new 'dual-boot' problems with F40 KDE might be related to this, but I'm not clear how I could test it. I've posted both here and on the kde list. I have two screen-devices, HDMI tv and vga monitor. By default booting is to Windows, but 'escape' early on goes to an HP-provided boot-selection sequence and grub. Choosing "modesetting" starts booting with both screens active, but freezes shortly after a cursor appears. "nomodeset" gives a usable system, but with the vga screen never active and final HDMI resolution fixed at 800x600. Could this perhaps be a conflict of hostnames set at power-on and by Fedora? John P -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Who moved my journald.conf?
On Wed, 2024-05-08 at 01:12 +0200, Michael Schwendt wrote: > On Tue, 07 May 2024 23:22:53 +0100, Patrick O'Callaghan wrote: > > > In that case I assume it was put there under F39. Seems very odd > > that > > the upgrade just kept it in addition to the one in > > /usr/lib/systemd. > > Depends. > > You cannot rely on just "rpm -qf ..." since that only queries the > package > file list regardless of what the file contents are. And that includes > %ghost files which possibly don't exist. Also, it is not only a > %ghost > file but also still marked as %config, and if it has been modified by > you, > RPM package upgrades would handle it like a config file. As stated earlier, it hasn't been modified by me. > What is in your /etc/systemd/journald.conf file compared with the > default in /usr/lib/systemd/journald.conf? They are identical except for comments: $ diff /etc/systemd/journald.conf /usr/lib/systemd/journald.conf 9,11c9,13 < # should be created by either modifying this file, or by creating "drop-ins" in < # the journald.conf.d/ subdirectory. The latter is generally recommended. < # Defaults can be restored by simply deleting this file and all drop-ins. --- > # should be created by either modifying this file (or a copy of it placed in > # /etc/ if the original file is shipped in /usr/), or by creating "drop-ins" > in > # the /etc/systemd/journald.conf.d/ directory. The latter is generally > # recommended. Defaults can be restored by simply deleting the main > # configuration file and all drop-ins located in /etc/. poc -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: What is Castor ? Att.Jonathan Billings.
On Tue, 2024-05-07 at 17:36 -0400, Jonathan Billings wrote: > Some home router/gateways will remember the hostname a system used as > part of their network, and when handing out the same IP to a new > host, re-uses the saved hostname. I've yet to come across a home gateway that handles name resolution, they just dole out numerical IPs from their DHCP server, it also seems to be a bit of a rarity for a client to accept a hostname that a DHCP server does supply (if it does). DHCP clients can also request the DHCP server lets them use their own hostname, and that's often ignored, too. More often than not, a client would to a reverse DNS look-up on its assigned IP to see what domain/hostname is associated with that IP (which could be a DNS query, but first it looks in the hosts file). Not everyone has a DNS server, or a configurable one, nor adjusts their hosts file (often fighting with Network Mangler over it). So: > Set your preferred hostname either in GNOME Settings (or whatever > DE’s settings) or with hostnamectl. Which stores a setting somewhere naming itself consistently, whatever IP address you get given. This can get messy if you get assigned different numerical IPs from time to time. -- uname -rsvp Linux 3.10.0-1160.114.2.el7.x86_64 #1 SMP Wed Mar 20 15:54:52 UTC 2024 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
