On 2021-08-15 7:45 a.m., stan via users wrote:
On Sun, 15 Aug 2021 18:13:02 +0530
Sreyan Chakravarty wrote:
I have not specified any size for the root partition in the anaconda
installer, hence it will use all the remaining space, so it should be
at least 920 GiB for the root partition right ?
On 2021-08-15 5:43 a.m., Sreyan Chakravarty wrote:
I am doing a clean install of Fedora 33 and I can't understand why all
my space is not being used properly.
Why 33 and not 34?
I have a 1 TB SATA HDD.
I have selected Custom Partitioning with Thin LVM Provisioning.
These are my
On 2021-07-28 1:12 a.m., Chris Murphy wrote:
On Tue, Jul 27, 2021 at 3:36 PM old sixpack13 wrote:
...
is your GPU from intel ?
if so:
- I get it too, sometimes while browsing with FF.
- Crtl+Alt+F3 to get a console (?) and do dmesg => ...GPU Crash dump ... GPU
hang...
+++ EDIT +++
I should
On Sun, 15 Aug 2021 18:13:02 +0530
Sreyan Chakravarty wrote:
> I am doing a clean install of Fedora 33 and I can't understand why
> all my space is not being used properly.
>
> I have a 1 TB SATA HDD.
>
> I have selected Custom Partitioning with Thin LVM Provisioning.
>
> These are my
Hi,
I am doing a clean install of Fedora 33 and I can't understand why all my
space is not being used properly.
I have a 1 TB SATA HDD.
I have selected Custom Partitioning with Thin LVM Provisioning.
These are my configurations:
1 MiB for /boot/efi (EFI System Partition)
1024 MiB for
On 8/12/21 2:35 PM, Mauricio Tavares wrote:
While I agree with the "add the pvs to the vgs, pvmove data,
remove old pvs" approach, I would like to ask more about why you do
not use the entire disk for a raid, instead partition both drives in
many volumes and then create raid1 volumes
Bonjour,
Sometimes selinux blocks access to a file without any clear reasons:
yesterday it was ok, today it is blocked... Why? I don't know, I changed
nothing, did not make any upgrade...
Today dictd cannot start:
SELinux forbids dictd an open access to /var/log/dictd.log.
Suggestion:
#
