On 2024-09-18 07:19, dwyatt--- via users wrote:
F40 just 'boots' to a black screen, the same for the KDE iso for F40.
Have you tried to ssh to the "hung" machine from your other one?
Have youn tried switching to CLI on the "hung" machine?
Cheers
Frank
--
--
On 2024-08-18 09:10, François Patte wrote:
Bonjour,
I installed f40 with raid1 partitions.
Every sunday an automatic program resync the partitions and a lot of
programs "pedal in the sauerkraut" (french idiom) because of this automatic
resync...
I have looked in cron.d directory, cron.weekl
On 2024-07-30 12:24, Frank Bures wrote:
On 2024-07-30 02:36, Barry wrote:
On 28 Jul 2024, at 21:13, Frank Bures wrote:
I downloaded open Android version 9 and ran it in a VM.
I found https://openandroidinstaller.org/
<https://openandroidinstaller.org/> but I do not think is wh
On 2024-07-30 02:36, Barry wrote:
On 28 Jul 2024, at 21:13, Frank Bures wrote:
I downloaded open Android version 9 and ran it in a VM.
I found https://openandroidinstaller.org/
<https://openandroidinstaller.org/> but I do not think is what you used?
Can you share a link to the a
On 2024-07-28 00:00, Frank Bures wrote:
For the record, the results of my experiments:
1.
Waydroid
is an Android emulator for Wayland. In F40 it is installable via dnf.
After initialization I was able to run it and it seems to be quite
responsive. Unfortunately, EERO app cannot be
On 2024-07-27 18:49, richard emberson wrote:
Hi,
I've wondered lately what it means to "run" an Android App on
a Linux platform:
1) If you have some kitchen appliance that has an associated App,
can you communicate with the appliance with the App using
your Linux Wifi?
In my particular case,
I am soliciting opinions on the subject.
I've done some search and I found basically two ways:
Waydroid
and
running Android in a VM
If anyone has an experience with this topic I would appreciate your opinion
on which way is better for the purpose. Basically, I just want to run EERO
app on my
On 2024-07-11 16:53, ToddAndMargo via users wrote:
I am are upgrading my office workstation. It is a bit of a work
horse with qemu-kvm virtual machines out the wazoo, so I can
upport my various customer's OS'es. I do no gaming.
I am a fan of Intel CPU and not AMD. I am also a fan of ECC.
AS
On 2024-07-02 17:35, Barry wrote:
I have a bootable external ssd that has scripts on it to mount the partitions
of my systems. Then i can fix the problem and reboot.
Good idea, thanks. I'll look into it.
Frank
--
--
___
users mailing list --
On 2024-07-02 12:56, Go Canes wrote:
Care to explain what you are trying to achieve? The USB stick would
only be useful for the existing install, and you would need the USB
stick to boot the existing install (assuming you removed any existing
/boot and/or /boot/efi from the existing install).
On 2024-07-02 10:44, Frank Bures wrote:
Hi,
I was wondering if it was possible to boot the existing F40 installation
from a USB. I tried to research this but everything I was able to find
dealt with booting a live image of F40 from USB and/or installing a live
image of F40 on a USB.
What
Hi,
I was wondering if it was possible to boot the existing F40 installation
from a USB. I tried to research this but everything I was able to find
dealt with booting a live image of F40 from USB and/or installing a live
image of F40 on a USB.
What I want is to create a USB stick with /boot
On 2024-06-28 05:14, ToddAndMargo via users wrote:
On 6/27/24 14:04, Frank Bures wrote:
On 2024-06-27 16:46, ToddAndMargo via users wrote:
On 6/27/24 11:50, Frank Bures wrote:
I followed the instructions at
https://virtio-win.github.io/Knowledge-Base/Virtiofs:-Shared-file-system
to mount
On 2024-06-28 14:25, Jeffrey Walton wrote:
Another one to avoid: cheap SSDs with duplicate serial numbers. Some
manufacturers repeat (clone?) serial numbers, and when you try to use
them in a RAID configuration, things go badly. A fellow on a Ubuntu
list struggled for months because of it.
At
On 2024-06-23 11:43, Frank Bures wrote:
On 2024-06-23 04:29, Tim wrote:
I followed
https://fedoraproject.org/wiki/GRUB_2?rd=Grub2#Updating_GRUB_2_configuration_on_UEFI_systems
and then I tried to run
grub2-emu
I get the list of installed kernels OK, but any choice for boot returns
error
On 2024-06-27 16:46, ToddAndMargo via users wrote:
On 6/27/24 11:50, Frank Bures wrote:
I followed the instructions at
https://virtio-win.github.io/Knowledge-Base/Virtiofs:-Shared-file-system
to mount two different F40 host file systems from Win11 KVM guest.
However, the mount does not
On 2024-06-27 07:09, ToddAndMargo via users wrote:
How to change the mount point from Z to something else:
REGEDIT4
; Change VirtIO-FS's mount point (letter):
; Change the M: below to you desiged letter. Remember the :
[HKEY_LOCAL_MACHINE\SOFTWARE\VirtIO-FS]
"MountPoint"="M:"
I followed t
On 2024-06-26 16:41, Thomas Cameron wrote:
On 6/26/24 2:56 PM, Mark C. Allman via users wrote:
Not telling you how to compute, just curious: why not just use native KVM?
I use KVM on my workstation to virtualize RHEL 7, RHEL8, RHEL9, Windows
2022, Windows 2019, Windows 10 and Windows 11. It J
On 2024-06-18 14:33, Roger Heflin wrote:
On mine I have md raid1 configured for /boot. Old install no
/boot/efi but it should also work for /boot/efi because even with
mdraid the bios/efi will still be able to find what it needs to find
to boot but when the OS comes up it mounts the md-raid raid
On 2024-06-23 04:29, Tim wrote:
On Sat, 2024-06-22 at 23:54 -0400, Frank Bures wrote:
This is what my efibootmgr returns:
root@ryzen:/# efibootmgr
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002,,0001
Boot Fedora
HD(1,GPT,e8838c34-c364-4347-afb7-1c516782b114,0x800,0x12c000)/\EFI
On 2024-06-22 20:59, Frank Bures wrote:
Hi,
I just did a kernel update and after reboot I ended up in a grub prompt.
I booted from USB F40 and followed instructions at
https://docs.fedoraproject.org/en-US/quick-docs/grub2-bootloader/#_restoring_the_bootloader_using_the_live_disk
However
Hi,
I just did a kernel update and after reboot I ended up in a grub prompt.
I booted from USB F40 and followed instructions at
https://docs.fedoraproject.org/en-US/quick-docs/grub2-bootloader/#_restoring_the_bootloader_using_the_live_disk
However, whatever I did I was not able to successfully
On 2024-06-18 13:52, Frank Bures wrote:
Just to explain:
I do not dd the whole /dev/sda. There are only /boot and /boot/efi
partitions on the disk, the rest is unformatted. I only dd the formatted
sectors.
The whole idea of having the same UUID on both sda and sdg is the ability
of
On 2024-06-18 11:40, Tom Horsley wrote:
On Tue, 18 Jun 2024 11:23:57 -0400
Frank Bures wrote:
Question: is this solution OK or have I done something wrong? Is there a
better way of solving this?
Using dd to back up a disk leaves the copy with the exact same UUID
as the source. So it is just
Hi,
I have a small SSD that I use for /boot and /boot/efi partitions - /dev/sda
I boot from /dev/sda
I have another small SSD that I use as a dd backup of /dev/sda - /dev/sdg
After update to a new kernel, I dd the /dev/sda to /dev/sdg so that in case
of a failure I could boot from /dev/sdg.
On 2024-05-12 16:11, Anthony Messina wrote:
Of course, you'll want to set something suitable for your system's needs
~]# cat /etc/systemd/system/fail2ban.service.d/timeout.conf
[Service]
TimeoutStopSec=5min
Thanks
Frank
--
--
___
users mailing l
Hi,
I was a target of an attack resulting in 1600 banned IP address by fail2ban.
When I reboot, f2b tries to unban those IPs but it ultimately times out and
a large number of IPs becomes orphaned. They stay in firewalld, but f2b
does not know about them anymore.
And indeed
root@ryzen:/etc/
On 2024-05-02 13:56, Charles Dennett wrote:
On 5/2/24 1:28 PM, Felix Miata wrote:
Charles Dennett composed on 2024-05-02 13:08 (UTC-0400):
...To find
the biggest offenders, cd to one of those directories (/var/cache for
example) and then use the command "sudo du -sh *" to get a listing of
ea
On 2024-04-28 12:59, Frank Bures wrote:
On 2024-04-28 11:39, Barry wrote:
On 28 Apr 2024, at 16:31, Frank Bures wrote:
The problem is that there are no connection attempts in /var/log/secure
or /var/log/messages so obviously f2b has nothing to do.
Maybe the logs are in the journal and
On 2024-04-28 11:39, Barry wrote:
On 28 Apr 2024, at 16:31, Frank Bures wrote:
The problem is that there are no connection attempts in /var/log/secure or
/var/log/messages so obviously f2b has nothing to do.
Maybe the logs are in the journal and nothing is updating the legacy /var/log
On 2024-04-28 10:58, Richard Shaw wrote:
On Sun, Apr 28, 2024 at 9:31 AM Frank Bures <mailto:bur...@gmail.com>> wrote:
Hi,
My machine is exposed to the wild and I was seeing hundreds of connection
attempts per day in my logs and in fail2ban.log.
All these nefarious a
On 2024-04-28 11:03, Charles Dennett wrote:
On 4/28/24 10:31 AM, Frank Bures wrote:
Hi,
My machine is exposed to the wild and I was seeing hundreds of connection
attempts per day in my logs and in fail2ban.log.
All these nefarious activities ceased after upgrade to F40.
Question:
Is
Hi,
My machine is exposed to the wild and I was seeing hundreds of connection
attempts per day in my logs and in fail2ban.log.
All these nefarious activities ceased after upgrade to F40.
Question:
Is there something fundamentally different in F40 connectivity?
I can still connect from outside
Any takes on this, guys?
Thanks
Frank
On 2024-03-23 11:30, Frank Bures wrote:
Hi,
I have several separate file systems, amongst them /home on btrfs and media
depository /archives on xfs (RAID-5).
I am running Win11 guest in QEMU on F39 host. I installed winfsp in the
guest and I can
Hi,
I have several separate file systems, amongst them /home on btrfs and media
depository /archives on xfs (RAID-5).
I am running Win11 guest in QEMU on F39 host. I installed winfsp in the
guest and I can access my /home in Win11 guest.
However, if I "Add Hardware" in Virtual HW details a
On 2024-03-10 12:40, Thomas Cameron wrote:
Quick definition: fora is the plural of forum, as in a web based forum to
discuss a topic or technology, like https://discussion.fedoraproject.org/.
Having said that...
I love mailing lists. I have filters set up they silently go to the correct
ma
s as expected
Note: as you upgrade VMWare versions make sure you set the
"VMWARE_VERSION=workstation-17.5.0" in the patch script (step3) to match
your version
On 1/11/24 16:39, Barry wrote:
On 11 Jan 2024, at 02:43, Frank Bures wrote:
You would not have to reinstall. Once yo
On 2024-01-10 21:03, Sherman Grunewagen via users wrote:
On 10/01/2024 16.06, Samuel Sieb wrote:
On 1/10/24 15:36, Sherman Grunewagen via users wrote:
Does anyone have VMware Workstation Pro 17.5.0 running with any of the
later 6.6.X kernels?
I'm having a hard time getting it to run with a Fed
On 2024-01-10 19:06, Samuel Sieb wrote:
On 1/10/24 15:36, Sherman Grunewagen via users wrote:
Does anyone have VMware Workstation Pro 17.5.0 running with any of the
later 6.6.X kernels?
I'm having a hard time getting it to run with a Fedora 38
installation. I'm fully updated as of 2 days ago,
On Wed, Dec 6, 2023 at 05:47 Barry Scott wrote:
>
>
> On 5 Dec 2023, at 20:06, Frank Bures wrote:
>
> Sorry, Barry, but there is no kde-wayland package in Fedora 39.
>
>
> My bad, its kwin-wayland not kde-wayland, please try that downgrade.
>
> Barry
>
Unfortuna
On 2023-12-05 14:08, Frank Bures wrote:
On 2023-12-05 03:51, Barry wrote:
On 4 Dec 2023, at 20:48, Frank Bures wrote:
I am having a problem with login page in Fedora39 KDE.
Everything was fine after original installation on a new HW, then in
about two days it stopped working.
When I
On 2023-12-05 03:51, Barry wrote:
On 4 Dec 2023, at 20:48, Frank Bures wrote:
I am having a problem with login page in Fedora39 KDE.
Everything was fine after original installation on a new HW, then in about two
days it stopped working.
When I log in I get black screen for a fraction
I am having a problem with login page in Fedora39 KDE.
Everything was fine after original installation on a new HW, then in about
two days it stopped working.
When I log in I get black screen for a fraction of a second and then I'm
back in the login screen. The system behaves the same for my acc
43 matches
Mail list logo