Re: /boot problem.

2023-05-18 Thread Samuel Sieb
On 5/18/23 20:36, Tim via users wrote: On Thu, 2023-05-18 at 20:15 -0600, home user wrote: What's the correct, best-practice way to remove the oldest kernel? To remove a kernel, make sure that you're not currently using it. Then it's simply rpm --erase or dnf erase kernel-(with the full versi

Re: /boot problem.

2023-05-18 Thread Tim via users
On Thu, 2023-05-18 at 20:15 -0600, home user wrote: > What's the correct, best-practice way to remove the oldest kernel? To remove a kernel, make sure that you're not currently using it. Then it's simply rpm --erase or dnf erase kernel-(with the full version numbers). On my system these are inst

Re: /boot problem.

2023-05-18 Thread Tim via users
On Thu, 2023-05-18 at 20:25 -0600, home user wrote: > The boot partition has been big enough for over 10 years, including > the time I've had 4 kernels + 1 rescue kernel (since late last > year).  I'm puzzled about how the /boot partition is now too small.  > Has the kernel grown significantly? No

Re: /boot problem.

2023-05-18 Thread home user
On 5/18/23 7:24 PM, home user wrote: On 5/18/23 6:30 PM, Felix Miata wrote: home user composed on 2023-05-18 16:21 (UTC-0600): [... snip ...] I vaguely recall late last year being advised by this list to expand this from 3 to 4 or 5.  I did that, to 4, but I don't remember how. Q1: How do I

Re: /boot problem.

2023-05-18 Thread home user
On 5/18/23 6:17 PM, Tim via users wrote: Bill: During this afternoon's patching (via dnf), a warning GUI popped up saying /boot is full.  It offered me the option to move /boot files to trash, but no option to delete anything. If I might make a suggestion: You might want a larger boot partiti

Re: /boot problem.

2023-05-18 Thread home user
On 5/18/23 5:53 PM, Lukas Middendorf wrote: On 19/05/2023 00:21, home user wrote: [... snip ...] The actual grub menu entry is caused by a file in /boot/loader/entries . If you manually remove the rescue files (initramfs and vmlinuz) but leave the file in /boot/loader/entries in place, you wi

Re: /boot problem.

2023-05-18 Thread home user
On 5/18/23 6:30 PM, Felix Miata wrote: home user composed on 2023-05-18 16:21 (UTC-0600): [... snip ...] Added information: This workstation is 10 years old; Fedora was installed on it in spring 2013. How many kernels are installed, more than two? If yes, uninstall the oldest. 4 kernels. I

Re: /boot problem.

2023-05-18 Thread Felix Miata
home user composed on 2023-05-18 16:21 (UTC-0600): > (f37 stand-alone dual-boot workstation) > During this afternoon's patching (via dnf), a warning GUI popped up saying > /boot is full. ... > I'm comfortable using rm in regular hard drive areas like /home. But I'm > neither a trained nor a p

Re: /boot problem.

2023-05-18 Thread Tim via users
Bill: > During this afternoon's patching (via dnf), a warning GUI popped up > saying /boot is full.  It offered me the option to move /boot files > to trash, but no option to delete anything. If I might make a suggestion: You might want a larger boot partition.  If you're not lacking space in ot

Re: /boot problem.

2023-05-18 Thread Lukas Middendorf
On 19/05/2023 00:21, home user wrote: > During this afternoon's patching (via dnf), a warning GUI popped up > saying /boot is full. [...] After the dnf patching > finished, I removed the rescue file via the rm command. But when I > rebooted, the rescue option was still in the grub menu. The act

/boot problem.

2023-05-18 Thread home user
(f37 stand-alone dual-boot workstation) During this afternoon's patching (via dnf), a warning GUI popped up saying /boot is full. It offered me the option to move /boot files to trash, but no option to delete anything. I tried moving the rescue file to trash, but the GUI said it couldn't. A

Re: blkid fully broken too chroot has losen sense in addition fstab has received an update not smart and luckily locate works with type the button star

2023-05-18 Thread John Pilkington
On 18/05/2023 20:49, Mike Wright wrote: On 5/18/23 05:21, Dorian ROSSE wrote: Hello everybody and the team fedora, blkid fully broken too chroot has losen sense in addition fstab has received an update not smart so it has losen a lot of part and luckily locate works without type the button s

Re: blkid fully broken too chroot has losen sense in addition fstab has received an update not smart and luckily locate works with type the button star

2023-05-18 Thread Mike Wright
On 5/18/23 05:21, Dorian ROSSE wrote: Hello everybody and the team fedora, blkid fully broken too chroot has losen sense in addition fstab has received an update not smart so it has losen a lot of part and luckily locate works without type the button star finally thanks you in advance to repa

Re: blkid fully broken too chroot has losen sense in addition fstab has received an update not smart and luckily locate works with type the button star

2023-05-18 Thread Felix Miata
Dorian ROSSE composed on 2023-05-18 12:21 (UTC): > blkid fully broken too chroot has losen sense in addition fstab has received > an update not smart so it has losen a lot of part and luckily locate works > without type the button star finally thanks you in advance to repair whole, Please have

blkid fully broken too chroot has losen sense in addition fstab has received an update not smart and luckily locate works with type the button star

2023-05-18 Thread Dorian ROSSE
Hello everybody and the team fedora, blkid fully broken too chroot has losen sense in addition fstab has received an update not smart so it has losen a lot of part and luckily locate works without type the button star finally thanks you in advance to repair whole, Have a nice week, Regards.

Re: Cannot install skypeforlinux

2023-05-18 Thread Tim via users
On Wed, 2023-05-17 at 19:20 -0400, Jeffrey Walton wrote: > The reason for short lived certificates is to keep CRLs small, > especially for mobile devices. In the past, mobile clients were asked > to download 60 MB CRLs over a 2G or 3G connection. UI's literally hung > while trying to perform the re