You might also take a look at Back In Time
(https://backintime.readthedocs.io/)
~~R
Defenestrated since 1990
On 5/7/24 22:11, Frederic Muller wrote:
On 30/04/2024 16:54, Patrick O'Callaghan wrote:
On Tue, 2024-04-30 at 16:44 +0700, Frederic Muller wrote:
Hi!
I currently do weekly backups
On 5/14/24 3:06 PM, Sbob wrote:
Where do I find the logs?
The logs from the Linux system that you ran the "ifconfig" on.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Once upon a time, Michal Schorm said:
> On Tue, May 14, 2024 at 8:13 PM Tim via users
> wrote:
> > Does /boot still need to be its own partition, these days?
> > /boot/efi has to be, but that's mapped into /boot, already.
>
> Definitely not.
It does for a variety of cases, such as an encrypted
Michal Schorm wrote:
>The best *trivial* setup and usage should be having everything on
>BTRFS (except EFI, as you said),
>and maintain some amount of snapshots you can revert to anytime in
>case of any issues.
I look forward to a complete set of instructions for this approach
in the Fedora
Poking about I see that the default workstation disk layout:
https://docs.fedoraproject.org/en-US/workstation-docs/disk-config/
has /boot on a ext4 partition and everything else on btrfs.
Also, the replacement for Anaconda will not happen until Fedora 41:
On Tue, May 14, 2024 at 8:13 PM Tim via users
wrote:
> Does /boot still need to be its own partition, these days?
> /boot/efi has to be, but that's mapped into /boot, already.
Definitely not.
And it actually creates all kinds of problems when separated.
The best *trivial* setup and usage should
Where do I find the logs?
On 5/14/24 2:46 PM, Samuel Sieb wrote:
On 5/14/24 10:48 AM, Sbob wrote:
However, I have several ALMA 8 VMWare vm's and I am able to convert
them like this:
# virt-v2v -i vmx /data/vmware/Alma-HA-DR-Data3/Alma-HA-DR-Data3.vmx
-o libvirt -of qcow2 -os default -n
On 5/14/24 10:48 AM, Sbob wrote:
However, I have several ALMA 8 VMWare vm's and I am able to convert them
like this:
# virt-v2v -i vmx /data/vmware/Alma-HA-DR-Data3/Alma-HA-DR-Data3.vmx -o
libvirt -of qcow2 -os default -n default
where the original VMware folder is at
On Tue, 2024-05-14 at 08:27 -0700, richard emberson wrote:
> Back on 05/03/2024 I posted the question:
> "How to increase size of /boot partition"
> I had the same problem.
>
> As was noted by some, I had not upgraded for a long, long time:
> "This type of layout and partition sizes is
Hi;
I have just installed Fedora 40 and all the kvm/qemu/libvirt bits
I can run virt-manager and install a new guest and when I start the
guest it comes up automatically with a valid network / ip address
I also converted a fedora 38 vm that has a gui interface and it also
works fine
Back on 05/03/2024 I posted the question:
"How to increase size of /boot partition"
I had the same problem.
As was noted by some, I had not upgraded for a long, long time:
"This type of layout and partition sizes is ancient. /tmp isn't even a partition
now."
So, I decided to re-install. I
On 14 May 2024 at 4:04, ToddAndMargo via users wrote:
Date sent: Tue, 14 May 2024 04:04:46 -0700
To: Community support for Fedora users
Subject:Can an vsFTP server get swamped?
Send reply to: Community support for Fedora users
From:
Hi All,
I have a customer with four Windows workstations that
backup with Cobian Reflector to a local Fedora vsFTP server
vsftpd-3.0.5-6.fc40.x86_64
Every so often, Cobian errors out with:
ERR 2024-05-12 21:38:58 An error occurred while uploading the file
Note sure this with post to list with the Bold marked text, but
sending it to your email as well. If list rejects it will repost without
Rich Text, and Perhaps mark lines with (B) that were bold??
Good Luck.
A couple of things I would recommend.
Have an old Lenovo R61 notebook that also has a
On Tue, May 14, 2024 at 3:38 AM Patrick Dupre via users <
users@lists.fedoraproject.org> wrote:
> Hello,
>
> During an update, I get
>
> Error Summary
> -
> Disk Requirements:
>At least 7MB more space needed on the /boot filesystem.
>
>
> How can I fix it without currently
df -h /boot
Filesystem Size Used Avail Use% Mounted on
/dev/sda6 488M 445M 6.5M 99% /boot
Sent: Tuesday, May 14, 2024 at 10:02 AM
From: "Barry Scott"
To: "Community support for Fedora users"
Cc: "Patrick Dupre"
Subject: Re: /boot too small
On 14 May 2024, at 08:38,
> On 14 May 2024, at 08:38, Patrick Dupre via users
> wrote:
>
> How can I fix it without currently resizing /boot?
How big is your /boot? What does this report? df -h /boot
If its 1GB then that should be lots of space and its worth checking where the
space has been used up.
Have a look
On 14/05/2024 08:54, Michal Schorm wrote:
Hi,
for an immediate workaround, remove the oldest kernel.
Here are the steps together with an example output:
1) List installed kernel-core packages:
# rpm -qa | grep kernel-core | sort
kernel-core-6.8.4-200.fc39.x86_64
Hi,
for an immediate workaround, remove the oldest kernel.
Here are the steps together with an example output:
1) List installed kernel-core packages:
# rpm -qa | grep kernel-core | sort
kernel-core-6.8.4-200.fc39.x86_64
kernel-core-6.8.6-200.fc39.x86_64
kernel-core-6.8.7-200.fc39.x86_64
2)
Hello,
During an update, I get
Error Summary
-
Disk Requirements:
At least 7MB more space needed on the /boot filesystem.
How can I fix it without currently resizing /boot?
Thank
drwx--. 5 root root 4096 May 14 08:36 grub2
lrwxrwxrwx. 1 root root45 Mar 7 13:24
20 matches
Mail list logo
