Re: How do I fix my messed up F31 boot partition setup ?
On 11/2/20 11:49 PM, linux guy wrote: I'm running a live install via USB. I'm looking in /dev/fedora/root mounted as root on my live session. /home/liveuser/root/var/log/anaconda cat program.log | grep boot 06:49:24,131 INFO program: Running... grub2-mkconfig -o /boot/grub2/grub.cfg That's curious. It appears the original install was not EFI, so where did the EFI bits come from? Hopefully everything is correctly setup for EFI. Try this command and see if it works: efibootmgr -c -w -L Fedora -d /dev/sdb -p 2 -l \EFI\fedora\shimx64.efi ___ 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
Re: How do I fix my messed up F31 boot partition setup ?
I'm running a live install via USB. I'm looking in /dev/fedora/root mounted as root on my live session. /home/liveuser/root/var/log/anaconda cat program.log | grep boot 12:39:33,557 INFO program: No FCoE boot disk information is found in EDD! 06:41:50,804 INFO program: Running... mount -t ext4 -o defaults /dev/sda1 /mnt/sysimage/boot 06:41:53,970 INFO program: Running... rsync -pogAXtlHrDx --exclude /dev/ --exclude /proc/ --exclude /sys/ --exclude /run/ --exclude /boot/*rescue* --exclude /etc/machine-id /run/install/source/ /mnt/sysimage 06:49:24,131 INFO program: Running... grub2-mkconfig -o /boot/grub2/grub.cfg 06:49:24,925 INFO program: Found linux image: /boot/vmlinuz-4.5.5-300.fc24.x86_64 06:49:24,925 INFO program: Found initrd image: /boot/initramfs-4.5.5-300.fc24.x86_64.img 06:49:24,925 INFO program: Found linux image: /boot/vmlinuz-0-rescue-c1d3ebaecd08428ba86f4aba3749efca 06:49:24,925 INFO program: Found initrd image: /boot/initramfs-0-rescue-c1d3ebaecd08428ba86f4aba3749efca.img ___ 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
Re: How do I fix my messed up F31 boot partition setup ?
On 11/2/20 11:41 PM, linux guy wrote: /dev/sda is the live USB drive. Ok, if the efibootmgr line references /dev/sda, I would suggest putting /dev/sdb instead. ___ 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
Re: How do I fix my messed up F31 boot partition setup ?
cat program.log | grep efi
06:41:48,437 INFO program: Running [15] lvm vgs --noheadings --nosuffix
--nameprefixes --unquoted --units=b -o
name,uuid,size,free,extent_size,extent_count,free_count,pv_count fedora
--config= devices { preferred_names=["^/dev/mapper/", "^/dev/md/",
"^/dev/sd"] } log {level=7 file=/tmp/lvm.log} ...
06:41:48,651 INFO program: Running [18] lvm vgs --noheadings --nosuffix
--nameprefixes --unquoted --units=b -o
name,uuid,size,free,extent_size,extent_count,free_count,pv_count fedora
--config= devices { preferred_names=["^/dev/mapper/", "^/dev/md/",
"^/dev/sd"] } log {level=7 file=/tmp/lvm.log} ...
06:41:49,718 INFO program: Running [20] lvm vgs --noheadings --nosuffix
--nameprefixes --unquoted --units=b -o
name,uuid,size,free,extent_size,extent_count,free_count,pv_count fedora
--config= devices { preferred_names=["^/dev/mapper/", "^/dev/md/",
"^/dev/sd"] } log {level=7 file=/tmp/lvm.log} ...
06:49:25,569 INFO program: Running... /usr/sbin/authconfig --update
--nostart --enableshadow --passalgo=sha512 --enablefingerprint
??
___
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
Re: How do I fix my messed up F31 boot partition setup ?
/dev/sda is the live USB drive. On Tue, Nov 3, 2020 at 2:39 AM Samuel Sieb wrote: > On 11/2/20 11:30 PM, linux guy wrote: > > So the boot process is supposed to find /dev/sdb5 and then mount > > /dev/sdb2 to the efi directory in it. Then it finds /fedora/root, and > > mount /fedora/home to /fedora/root/home ? > > The boot process finds the kernel and initramfs from /dev/sdb5, loads > them and starts the kernel. In the initramfs is code to mount the > /fedora/root partition and start everything. Part of that process will > be mounting /dev/sdb2 and /fedora/home as described in the /etc/fstab file. > > I just realized now, that all this refers to /dev/sdb. What's on /dev/sda? > ___ > 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 > ___ 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
Re: How do I fix my messed up F31 boot partition setup ?
On 11/2/20 11:32 PM, linux guy wrote: I'm confused. Exactly what do I do ? In the /fedora/root partition, you need to find /var/log/anaconda/program.log. In there is the efibootmgr command that was run on install to setup the boot. Run that command again to add the Fedora boot option to the BIOS. ___ 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
Re: How do I fix my messed up F31 boot partition setup ?
On 11/2/20 11:30 PM, linux guy wrote: So the boot process is supposed to find /dev/sdb5 and then mount /dev/sdb2 to the efi directory in it. Then it finds /fedora/root, and mount /fedora/home to /fedora/root/home ? The boot process finds the kernel and initramfs from /dev/sdb5, loads them and starts the kernel. In the initramfs is code to mount the /fedora/root partition and start everything. Part of that process will be mounting /dev/sdb2 and /fedora/home as described in the /etc/fstab file. I just realized now, that all this refers to /dev/sdb. What's on /dev/sda? ___ 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
Re: How do I fix my messed up F31 boot partition setup ?
I'm confused. Exactly what do I do ? Thanks for the help, btw ! It's late here. I'll run it in the morning. ___ 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
Re: How do I fix my messed up F31 boot partition setup ?
So the boot process is supposed to find /dev/sdb5 and then mount /dev/sdb2 to the efi directory in it. Then it finds /fedora/root, and mount /fedora/home to /fedora/root/home ? ___ 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
Re: How do I fix my messed up F31 boot partition setup ?
On 11/2/20 11:28 PM, linux guy wrote: I'm looking at it with a live image right now. This is what is in fedora: ls BOOTIA32.CSV fwupia32.efi grub.cfg grubx64.efi shimia32.efi BOOTX64.CSV fwupx64.efi grub.cfg.rpmsave mmia32.efi shimia32-fedora.efi fonts gcdia32.efi grubenv mmx64.efi shimx64.efi fw gcdx64.efi grubia32.efi shim.efi shimx64-fedora.efi Ok, then you're all set. Find that "efibootmgr" command from the log, run it, and it should boot. ___ 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
Re: How do I fix my messed up F31 boot partition setup ?
I'm looking at it with a live image right now. This is what is in fedora: ls BOOTIA32.CSV fwupia32.efi grub.cfg grubx64.efi shimia32.efi BOOTX64.CSV fwupx64.efi grub.cfg.rpmsave mmia32.efi shimia32-fedora.efi fonts gcdia32.efi grubenv mmx64.efishimx64.efi fwgcdx64.efigrubia32.efi shim.efi shimx64-fedora.efi ___ 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
Re: How do I fix my messed up F31 boot partition setup ?
On 11/2/20 11:19 PM, linux guy wrote: Here is in /dev/sdb5: The efi directory is empty. Right, that's the mount point for /dev/sdb2. Here is what is in /dev/sdb2: ls EFI Boot fedora Microsoft What's in "fedora"? You might actually have all the files and just need to add the boot entry. That can sometimes be done directly in the BIOS, or else you need to boot a live image and use "efibootmgr" to add it. On the installed system, look in /var/log/anaconda/program.log to find the original command used. ___ 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
Re: Fedora-33 Instal method -
On 03/11/2020 14:45, Samuel Sieb wrote: On 11/2/20 10:39 PM, Chris Murphy wrote: On Mon, Nov 2, 2020 at 1:34 PM Bob Goodwin wrote: Is there any way to install Fedora 33 without using the install GUI? Netinstaller has an option to boot in text mode. Edit the command line and add 'inst.text' and you'll get the text installer. It is limited in what options you get. I have not been able to get past the language selection screen, the first one, in the network fedora server GUI, w/ould like to know if it offers the/ LVM or the "standard partitions?" I want the "standard partitions" not the LVM. There are four preset schemes, same as in the GUI: Btrfs, LVM, LVM Thin, Standard. But there's no other choices to customize these. You pick the scheme and get that scheme's "automatic" partitioning. You do get a choice whether to use only free space on the disk (default) or erase it. There was also a custom partitioning option, but I couldn't make any sense of it. +1 And now I have a headache from trying. --- The key to getting good answers is to ask good questions. ___ 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
Re: How do I fix my messed up F31 boot partition setup ?
Here is in /dev/sdb5: ls 520f44320ac640c68996d2e055036d31 config-5.3.11-200.fc30.x86_64 config-5.3.11-300.fc31.x86_64 config-5.4.8-200.fc31.x86_64 efi elf-memtest86+-5.01 extlinux grub2 initramfs-0-rescue-6e82390ebac04e6ebc14c7543a31c1e8.img initramfs-5.3.11-200.fc30.x86_64.img initramfs-5.3.11-300.fc31.x86_64.img initramfs-5.4.8-200.fc31.x86_64.img loader lost+found memtest86+-5.01 System.map-5.3.11-200.fc30.x86_64 System.map-5.3.11-300.fc31.x86_64 System.map-5.4.8-200.fc31.x86_64 vmlinuz-0-rescue-6e82390ebac04e6ebc14c7543a31c1e8 vmlinuz-5.3.11-200.fc30.x86_64 vmlinuz-5.3.11-300.fc31.x86_64 vmlinuz-5.4.8-200.fc31.x86_64 The efi directory is empty. Here is what is in /dev/sdb2: ls 6e82390ebac04e6ebc14c7543a31c1e8 EFI mach_kernel System ls EFI Boot fedora Microsoft On Tue, Nov 3, 2020 at 2:00 AM Samuel Sieb wrote: > On 11/2/20 10:50 PM, linux guy wrote: > > I believe that the files in /dev/sdb5 are the proper boot files. > > Would it be as simple as moving the files from that directory to the > > FAT32 partition ? > > In particular, you're looking for a path like EFI/fedora/grubx64.efi > ___ > 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 > ___ 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
Re: F32->F33: Upgrade or reinstall?
On Mon, Nov 2, 2020 at 5:45 AM Patrick O'Callaghan wrote: > > I'd normally upgrade, but my /dev/sda uses LVM to handle root, /home > etc. and from what I read this cannot be converted directly to BTRFS, > which I'm interested in using. ext4 can be converted to Btrfs but I can't strongly recommend it because you're not going to get the same layout as a default installation. The conversion won't remove LVM, and it won't add the subvolume layout we're using where "home" and "root" subvolumes are assigned to /home and / mountpoints respectively. > > What would be the best way to approach this?: > > 1) Do a system upgrade and then convert to BTRFS by backing everything > up and restoring it (I'd need guidance on how to do this). > > 2) Do a complete system install and then restore from backups. > > I'm guessing that (2) is the simplest answer, but I'd appreciate any > comments, especially from people who have actually done either of > these. Top choice: Backup /home. Optionally /etc. And hand it over to the installer for complete wipe and clean install. From scratch setup. And after going through initial setup, restore /home (specifically restore the contents of ~/ for each user). Probably the most straightforward. Second choice: Esoteric but a rather neat trick, is btrfs conversion, snapshot root and home. And use Btrfs send/receive to populate a new Btrfs file system with those snapshots. The conversion to Btrfs is merely a means to being able to use send/receive to replicate them. You get to keep your customizations without a clean install, but you do get the subvolume layout of a clean install. It is a bit partition-ninja. And there are post steps like all the bootloader stuff. It really depends on how comfortable you are with a rather low level process of migrating the data, almost inevitably messing it up, and working through the screwups. I've done quite a few of these and manage to screw it up somehow, and have to backtrack but I also don't panic easily, not least of which is a bunch of backups. So no matter how badly I mess it up I know I'm not losing things I care about. -- Chris Murphy ___ 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
Re: How do I fix my messed up F31 boot partition setup ?
On 11/2/20 10:50 PM, linux guy wrote: I believe that the files in /dev/sdb5 are the proper boot files. Would it be as simple as moving the files from that directory to the FAT32 partition ? In particular, you're looking for a path like EFI/fedora/grubx64.efi ___ 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
Re: How do I fix my messed up F31 boot partition setup ?
I believe that the files in /dev/sdb5 are the proper boot files.Would it be as simple as moving the files from that directory to the FAT32 partition ? On Tue, Nov 3, 2020 at 1:43 AM Samuel Sieb wrote: > On 11/2/20 10:35 PM, linux guy wrote: > > I can't remember exactly what I did, but I think I copied an F31 install > > onto an existing F31 install on a hard drive that had Windows 10 on > > it. I did this in early 2020. Didn't keep notes. :( > > > > Now I have a hard drive that will boot Windows 10 fine, via the Windows > > 10 Boot Manager. > > > > When I go into the BIOS manager, it shows 2 boot options: Windows 10 via > > the Windows 10 Boot Manager and the hard drive device itself. > > > > If I choose Windows 10, Win 10 boots fine. :( > > If I choose the hard drive device itself, the BIOS says to insert a > > valid boot device. > > > > When I look at the hard drive with GParted, I see this: > > > > Samsung SSD 850 EVO mSATA 500 GB with: > > /dev/sdb1 ntfs Recovery (Windows) > > /dev/sdb2 fat32 EFI System Partition Has a boot flag > > /dev/sdb3 unknown type Microsoft Reserved Partition > > /dev/sdb4 ntfs Basic data partition > > /dev/sdb5 ext4<--- this is the boot partition, has the boot stuff > > on it. Has a boot flag. > > /dev/sdb6 lvm2 pv fedora > > > > A fedora "device" which has 3 partitions: > > /dev/fedora/home ext4 the home directory > > /dev/fedora/root ext4 > > /dev/fedora/swap linuxswap > > > > I used a live USB version to facilitate the copy. I suspect that the > > live boot got installed (thus the FAT32 partition) instead of the real > > boot partition, which is /dev/sda5 right now. > > The FAT32 partition is the EFI boot partition. Did this disk ever work > with Fedora? I expect that you didn't copy the Fedora files that were > in that partition on wherever you copied it from. It's tricky to fix > that. Do you still have whatever drive you copied it from originally? > ___ > 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 > ___ 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
Re: Fedora-33 Instal method -
On 11/2/20 10:39 PM, Chris Murphy wrote: On Mon, Nov 2, 2020 at 1:34 PM Bob Goodwin wrote: Is there any way to install Fedora 33 without using the install GUI? Netinstaller has an option to boot in text mode. Edit the command line and add 'inst.text' and you'll get the text installer. It is limited in what options you get. I have not been able to get past the language selection screen, the first one, in the network fedora server GUI, w/ould like to know if it offers the/ LVM or the "standard partitions?" I want the "standard partitions" not the LVM. There are four preset schemes, same as in the GUI: Btrfs, LVM, LVM Thin, Standard. But there's no other choices to customize these. You pick the scheme and get that scheme's "automatic" partitioning. You do get a choice whether to use only free space on the disk (default) or erase it. There was also a custom partitioning option, but I couldn't make any sense of it. ___ 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
Re: How do I fix my messed up F31 boot partition setup ?
On 11/2/20 10:35 PM, linux guy wrote: I can't remember exactly what I did, but I think I copied an F31 install onto an existing F31 install on a hard drive that had Windows 10 on it. I did this in early 2020. Didn't keep notes. :( Now I have a hard drive that will boot Windows 10 fine, via the Windows 10 Boot Manager. When I go into the BIOS manager, it shows 2 boot options: Windows 10 via the Windows 10 Boot Manager and the hard drive device itself. If I choose Windows 10, Win 10 boots fine. :( If I choose the hard drive device itself, the BIOS says to insert a valid boot device. When I look at the hard drive with GParted, I see this: Samsung SSD 850 EVO mSATA 500 GB with: /dev/sdb1 ntfs Recovery (Windows) /dev/sdb2 fat32 EFI System Partition Has a boot flag /dev/sdb3 unknown type Microsoft Reserved Partition /dev/sdb4 ntfs Basic data partition /dev/sdb5 ext4 <--- this is the boot partition, has the boot stuff on it. Has a boot flag. /dev/sdb6 lvm2 pv fedora A fedora "device" which has 3 partitions: /dev/fedora/home ext4 the home directory /dev/fedora/root ext4 /dev/fedora/swap linuxswap I used a live USB version to facilitate the copy. I suspect that the live boot got installed (thus the FAT32 partition) instead of the real boot partition, which is /dev/sda5 right now. The FAT32 partition is the EFI boot partition. Did this disk ever work with Fedora? I expect that you didn't copy the Fedora files that were in that partition on wherever you copied it from. It's tricky to fix that. Do you still have whatever drive you copied it from originally? ___ 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
Re: Fedora-33 Instal method -
On Mon, Nov 2, 2020 at 1:34 PM Bob Goodwin wrote: > > Is there any way to install Fedora 33 without using the install GUI? Netinstaller has an option to boot in text mode. Edit the command line and add 'inst.text' and you'll get the text installer. It is limited in what options you get. > I have not been able to get past the language selection screen, the > first one, in the network fedora server GUI, w/ould like to know if it > offers the/ LVM or the "standard partitions?" I want the "standard > partitions" not the LVM. There are four preset schemes, same as in the GUI: Btrfs, LVM, LVM Thin, Standard. But there's no other choices to customize these. You pick the scheme and get that scheme's "automatic" partitioning. You do get a choice whether to use only free space on the disk (default) or erase it. -- Chris Murphy ___ 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
How do I fix my messed up F31 boot partition setup ?
I can't remember exactly what I did, but I think I copied an F31 install onto an existing F31 install on a hard drive that had Windows 10 on it. I did this in early 2020. Didn't keep notes. :( Now I have a hard drive that will boot Windows 10 fine, via the Windows 10 Boot Manager. When I go into the BIOS manager, it shows 2 boot options: Windows 10 via the Windows 10 Boot Manager and the hard drive device itself. If I choose Windows 10, Win 10 boots fine. :( If I choose the hard drive device itself, the BIOS says to insert a valid boot device. When I look at the hard drive with GParted, I see this: Samsung SSD 850 EVO mSATA 500 GB with: /dev/sdb1 ntfs Recovery (Windows) /dev/sdb2 fat32 EFI System Partition Has a boot flag /dev/sdb3 unknown type Microsoft Reserved Partition /dev/sdb4 ntfs Basic data partition /dev/sdb5 ext4<--- this is the boot partition, has the boot stuff on it. Has a boot flag. /dev/sdb6 lvm2 pv fedora A fedora "device" which has 3 partitions: /dev/fedora/home ext4 the home directory /dev/fedora/root ext4 /dev/fedora/swap linuxswap I used a live USB version to facilitate the copy. I suspect that the live boot got installed (thus the FAT32 partition) instead of the real boot partition, which is /dev/sda5 right now. How do I fix this ? Thanks ___ 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
Re: BTFS - Raid1 for System Disk
On Mon, Nov 2, 2020 at 2:14 PM Jorge Fábregas wrote: > > On 11/2/20 3:48 PM, Chris Murphy wrote: > > Short version: If you want unattended degraded RAID boot, use mdadm > > and put Btrfs on top of it. > > Hi Chris, > > I get it now. Thanks. I see it's not that straightforward at this point :( > > I guess I'll continue to use ext4 but now I'll consider it over mdadm > (RAID 1) for my next setup as suggested. I'll miss the self-healing > properties of a BTRFS RAID-1 setup but don't want the hassle at this > point when ext4 has served me well. You don't have those issues with Btrfs on mdadm raid1. You'll still get metadata self-healing from DUP metadata profile, and you'll get error detection for data. That's not something mdadm does on its own. -- Chris Murphy ___ 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
Re: New parallel port card won't work
On 2020-11-02 17:04, Samuel Sieb wrote: On 11/2/20 3:25 PM, ToddAndMargo via users wrote: On 2020-11-02 14:33, Samuel Sieb wrote: lspci -nn # lspci -nn Ok, so nothing there. Any luck with the driver? I will have to wait till tomorrow. ___ 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
Re: New parallel port card won't work
On 11/2/20 3:25 PM, ToddAndMargo via users wrote: On 2020-11-02 14:33, Samuel Sieb wrote: lspci -nn # lspci -nn Ok, so nothing there. Any luck with the driver? ___ 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
Re: New parallel port card won't work
On 2020-11-02 14:33, Samuel Sieb wrote: lspci -nn # lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5918] (rev 05) 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics P630 [8086:591d] (rev 04) 00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31) 00:14.2 Signal processing controller [1180]: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem [8086:a131] (rev 31) 00:15.0 Signal processing controller [1180]: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #0 [8086:a160] (rev 31) 00:15.1 Signal processing controller [1180]: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #1 [8086:a161] (rev 31) 00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31) 00:16.3 Serial controller [0700]: Intel Corporation 100 Series/C230 Series Chipset Family KT Redirection [8086:a13d] (rev 31) 00:17.0 SATA controller [0106]: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] [8086:a102] (rev 31) 00:1c.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 [8086:a110] (rev f1) 00:1c.5 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #6 [8086:a115] (rev f1) 00:1c.6 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #7 [8086:a116] (rev f1) 00:1c.7 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #8 [8086:a117] (rev f1) 00:1d.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 [8086:a118] (rev f1) 00:1f.0 ISA bridge [0601]: Intel Corporation C236 Chipset LPC/eSPI Controller [8086:a149] (rev 31) 00:1f.2 Memory controller [0580]: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller [8086:a121] (rev 31) 00:1f.3 Audio device [0403]: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller [8086:a170] (rev 31) 00:1f.4 SMBus [0c05]: Intel Corporation 100 Series/C230 Series Chipset Family SMBus [8086:a123] (rev 31) 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-LM [8086:15b7] (rev 31) 01:00.0 Parallel controller [0701]: MosChip Semiconductor Technology Ltd. MCS9900 Multi-I/O Controller [9710:9900] 6c:00.0 Ethernet controller [0200]: Intel Corporation I210 Gigabit Network Connection [8086:1533] (rev 03) 6d:00.0 PCI bridge [0604]: Tundra Semiconductor Corp. Device [10e3:8113] (rev 01) 6f:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242] 70:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 [144d:a804] ___ 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
Re: Fedora-33 Instal method -
On 2020-11-02 16:38, Samuel Sieb wrote: So my question boils down to is the installer GUI the only way to install Fedora 33? There is a text mode interface, but it's not easy to use, especially the partitioning. I couldn't really figure it out. Also, I think the resulting installed system will not boot to a graphical interface by default either. . /I normally boot from a text display, I have trouble with the graphic too./ Another method is to create a kickstart file to automate the install, but it's quite a bit of work for a single install. . The 'simple install' is not simple for me to use ... I may have to rely on my helpers then but I will look into the kick start process. Thanks for responding, Bob -- Bob Goodwin - Zuni, Virginia, USA FEDORA-32/64bit LINUX XFCE Fastmail POP3 ___ 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
Re: Fedora-33 Instal method -
On 11/2/20 2:38 PM, Ed Greshko wrote: On 03/11/2020 05:38, Samuel Sieb wrote: On 11/2/20 12:33 PM, Bob Goodwin wrote: Is there any way to install Fedora 33 without using the install GUI? I have not been able to get past the language selection screen, the first one, in the network fedora server GUI, w/ould like to know if it offers the/ LVM or the "standard partitions?" I want the "standard partitions" not the LVM. All the installers use the same installer program "anaconda" and the "standard partitions" option is always available. LVM is just the default. Hasn't that changed in F33? Isn't btrfs now the default? Good point. I haven't done an F33 install yet and I usually use kickstarts anyway. ___ 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
Re: Fedora-33 Instal method -
On 03/11/2020 05:38, Samuel Sieb wrote: On 11/2/20 12:33 PM, Bob Goodwin wrote: Is there any way to install Fedora 33 without using the install GUI? I have not been able to get past the language selection screen, the first one, in the network fedora server GUI, w/ould like to know if it offers the/ LVM or the "standard partitions?" I want the "standard partitions" not the LVM. All the installers use the same installer program "anaconda" and the "standard partitions" option is always available. LVM is just the default. Hasn't that changed in F33? Isn't btrfs now the default? --- The key to getting good answers is to ask good questions. ___ 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
Re: New parallel port card won't work
On 11/2/20 2:21 PM, ToddAndMargo via users wrote: On 2020-11-02 13:14, Samuel Sieb wrote: What about the other info I asked for in the previous email? Which one did I miss? It was easy to miss in the rest of the text. Can you show the output of "lspci -nn" for the other devices around this one? ___ 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
Re: New parallel port card won't work
On Mon, 2 Nov 2020 at 17:15, Samuel Sieb wrote: > On 11/2/20 10:31 AM, ToddAndMargo via users wrote: > > On 2020-11-02 01:59, Samuel Sieb wrote: > >There's also a Linux driver > >> available at https://www.asix.com.tw/en/support/download if you want > >> to try it. > > > > You have to recompile the linux kernel > > No, you don't. Unpack the tar file, go into the directory and run: > make -C /lib/modules/`uname -r`/build M=$PWD > > You will end up with a 99xx.ko file. Do "insmod 99xx.ko". I can't do > that because I have secure boot enabled. You will need to turn it off > if you do. (Or figure out how to sign the module and register the key.) > You may be able to use a Machine Owner Key (MOK). See https://docs.fedoraproject.org/en-US/Fedora/23/html/System_Administrators_Guide/sect-enrolling-public-key-on-target-system.html This process worked for me in Fedora 32 and is the same for other distros. https://wiki.debian.org/SecureBoot#MOK_-_Machine_Owner_Key might be useful. -- George N. White III ___ 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
Re: New parallel port card won't work
On 2020-11-02 13:14, Samuel Sieb wrote: On 11/2/20 10:31 AM, ToddAndMargo via users wrote: On 2020-11-02 01:59, Samuel Sieb wrote: There's also a Linux driver available at https://www.asix.com.tw/en/support/download if you want to try it. You have to recompile the linux kernel No, you don't. Their directions said you did. But ... Unpack the tar file, go into the directory and run: make -C /lib/modules/`uname -r`/build M=$PWD You will end up with a 99xx.ko file. Do "insmod 99xx.ko". I can't do that because I have secure boot enabled. You will need to turn it off if you do. (Or figure out how to sign the module and register the key.) What about the other info I asked for in the previous email? Which one did I miss? ___ 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
Re: Fedora-33 Instal method -
On 11/2/20 12:33 PM, Bob Goodwin wrote: Is there any way to install Fedora 33 without using the install GUI? I have not been able to get past the language selection screen, the first one, in the network fedora server GUI, w/ould like to know if it offers the/ LVM or the "standard partitions?" I want the "standard partitions" not the LVM. All the installers use the same installer program "anaconda" and the "standard partitions" option is always available. LVM is just the default. So my question boils down to is the installer GUI the only way to install Fedora 33? There is a text mode interface, but it's not easy to use, especially the partitioning. I couldn't really figure it out. Also, I think the resulting installed system will not boot to a graphical interface by default either. Another method is to create a kickstart file to automate the install, but it's quite a bit of work for a single install. ___ 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
Re: New parallel port card won't work
On 11/2/20 10:31 AM, ToddAndMargo via users wrote: On 2020-11-02 01:59, Samuel Sieb wrote: There's also a Linux driver available at https://www.asix.com.tw/en/support/download if you want to try it. You have to recompile the linux kernel No, you don't. Unpack the tar file, go into the directory and run: make -C /lib/modules/`uname -r`/build M=$PWD You will end up with a 99xx.ko file. Do "insmod 99xx.ko". I can't do that because I have secure boot enabled. You will need to turn it off if you do. (Or figure out how to sign the module and register the key.) What about the other info I asked for in the previous email? ___ 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
Re: BTFS - Raid1 for System Disk
On 11/2/20 3:48 PM, Chris Murphy wrote: > Short version: If you want unattended degraded RAID boot, use mdadm > and put Btrfs on top of it. Hi Chris, I get it now. Thanks. I see it's not that straightforward at this point :( I guess I'll continue to use ext4 but now I'll consider it over mdadm (RAID 1) for my next setup as suggested. I'll miss the self-healing properties of a BTRFS RAID-1 setup but don't want the hassle at this point when ext4 has served me well. I've been using BTRFS for 7 years now without issues (for my internal backup drive) and will continue to do so. The only major "enhacement" I'll do is to convert its profile from SINGLE to DUP when I get to replace the HDD soon (for a 2X larger one). Thanks for that wonderful feedback Chris. It was very useful! Best regards. -- Jorge ___ 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
Re: F32->F33: Upgrade or reinstall?
On 11/2/20 4:45 AM, Patrick O'Callaghan wrote: I'd normally upgrade, but my /dev/sda uses LVM to handle root, /home etc. and from what I read this cannot be converted directly to BTRFS, which I'm interested in using. https://fedoraproject.org/wiki/Btrfs ___ 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
Fedora-33 Instal method -
Is there any way to install Fedora 33 without using the install GUI? This morning, out of desperation, I tried the Network Installer for Fedora Server but it is just another .iso that uses the same GUI as the others I have used that I am no longer able to deal with. I was hoping it would be a command line operation which I can still deal with. In order to use the GUI I need some one to do it for me while I tell them how to respond to the menu items, difficult since it is something I do infrequently although I can usually muddle through, it is inconvenient at best. I have not been able to get past the language selection screen, the first one, in the network fedora server GUI, w/ould like to know if it offers the/ LVM or the "standard partitions?" I want the "standard partitions" not the LVM. So my question boils down to is the installer GUI the only way to install Fedora 33? Bob -- Bob Goodwin - Zuni, Virginia, USA FEDORA-32/64bit LINUX XFCE Fastmail POP3 ___ 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
Re: BTFS - Raid1 for System Disk
On Mon, Nov 2, 2020 at 8:32 AM Jorge Fábregas wrote: > I'd like to have my system drive with BTRFS on a RAID1 profile. I was > experminenting with a simple / (root filesystem) subvolume but it > appears GRUB2 can't work properly with it. I get the famous: > > "Sparse file is not allowed" during boot (and no way to access GRUB2 > menu). It boots fine but I can't longer edit the GRUB2 menu during boot. I'm not exactly sure what condition results in this error, but I suspect it's a bug. The message we should see when grubenv is on Btrfs is that grubenv writes on btrfs are disallowed. This is because GRUB (in the pre-boot environment) writes to grubenv not via file system writes but by directly overwriting the two 512 byte blocks that make up grubenv. On btrfs, this is indistinguishable from corruption because the checksum isn't also updated. Further, this 1KiB grubenv file is so small it tends to be an inline extent, i.e. it's sorted inside the 16KiB leaf alone with its inode. If the file were overwritten, it'd invalidate the entire 16KiB leaf. It's possibly a very serious corruption. But GRUB has known this since forever and doesn't do writes to files on Btrfs (or LUKS, or mdraid volumes, and maybe not to LVM). So I suspect this message is just an artifact of having put your /boot on Btrfs on a BIOS system. On BIOS systems, the grubenv is located in /boot/grub2/grubenv which means if you put /boot on Btrfs, it's on Btrfs and can't use GRUB_DEFAULT=saved or the variable GRUB hidden menu feature where it checks for successful boots. Basically, GRUB can't reset the count, so it sees boots as always successful. You can reveal the GRUB menu by F8 (often this includes using Fn key). Or you can do it permanently by `grub2-editenv - unset menu_auto_hide` Meanwhile on UEFI systems, grubenv is always on the FAT formatted EFI System partition. > Fine, I read somewhere that /boot wasn't allowed with BTRFS in Fedora? It's allowed but not the default. > I'd like my desktop to have a RAID1 setup for my main drive and be able > to remove either disk and boot seamlessly. Is this possible with BTFS & > GRUB2 these days? Short version: If you want unattended degraded RAID boot, use mdadm and put Btrfs on top of it. Long version: GRUB is not a factor at all in this. It has had Btrfs support for 11 years, and knows about all the profiles. It supports all the raid types including the new raid1c3 and raid1c4, and knows how to find things even when degraded, and can even reconstruct from parity if /boot were on a raid5 or raid6 with missing disks. The issue is that there's no such thing as automatic degraded mounts in Btrfs. If a device has failed or is missing, you will get a long delay followed by being dropped to a dracut prompt. (At least it used to, I vaguely recall one or two issues where systemd waits for sysroot indefinitely, which seems like it should be a bug.) Why? Missing features to make automatic degraded mounts safe. i.e. if the missing device reappears, it needs to be "caught up" with all the changes since it went missing. Right now you have to do a scrub of the entire volume, and there's no partial scrubs. Where with mdadm raid, there is a write intent bitmap that tells mdadm how to kick off a partial resync. There is some bad advice on the internet (imagine that), suggesting removing the btrfs udev rule that waits for all Btrfs devices to show up before attempting to mount, and also add 'degraded' mount option to fstab. The problem is, any small delay by any device during boot means an immediate degraded mount. And without a scrub to catch up the late device, the mirrors can end up in kind of "split brain" situation, and that's not recoverable or repairable. -- Chris Murphy ___ 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
Re: Install Fedora -
On Mon, Nov 2, 2020 at 3:50 AM Patrick O'Callaghan wrote: > > On Sun, 2020-11-01 at 19:00 -0700, Chris Murphy wrote: > > On Sun, Nov 1, 2020 at 6:51 AM John Mellor wrote: > > > On 2020-10-31 10:46 p.m., Tim via users wrote: > > > > On Sat, 2020-10-31 at 16:11 +, lancelasset...@gmail.com wrote: > > > > > Will NFS tell you data has been corrupted during the transfer and > > > > > write process? > > > > Does any filing system? In general, writes to storage are assumed to > > > > have worked unless something throws up an error message. Your hard > > > > drive could be silently corrupting data as it writes to the drive due > > > > to various reasons (defects in its media, bugs in its firmware, > > > > glitches from bad power supplies). You'd never know unless your > > > > filing system did a sanity check after writing. Some specialised ones > > > > might do that, but the average ones don't > > > > > > > You are correct for some very popular filesystems. EXT2/3/4, XFS, NTFS > > > etc. will not detect this situation. However, newer filesystems (<10 > > > years old) do handle silent data glitches, bad RAM and cosmic ray hits > > > correctly. > > > > > > BTRFS has been the default filesystem on SUSE Linux for years, and is > > > now the default filesystem on Fedora-33. ZFS is an optional filesystem > > > on Ubuntu-20 and all the Berkeley-derived Unixen like FreeBSD, and > > > standard on Oracle Linux and Solaris. BTRFS and ZFS are both COW > > > filesystems using checksumming of both data and metadata. When you push > > > something to the disk(s) with some kind of RAM error or power glitch, > > > the first write will be stored with the error, and then the checksummed > > > metadata is simply redirected to reference the new stuff. This will > > > detect the checksum errors on the data on ZFS with the reread to verify > > > the checksum, but I believe that BTRFS will return a successful write > > > without one of the RAID configurations set on the pool. If you are > > > running one of the RAID configurations, the checksum error will be > > > detected before the write completes. To guard against on-disk > > > corruption (bit rot), both ZFS and BTRFS will also correct it on the > > > next read of that data if you are running the filesystem in one of the > > > RAID-z configurations (multiple copies stored), or upon running a > > > filesystem integrity check. > > > > Short story: > [...] > > Thanks. That more or less matches what I thought. So BTRFS does not do > read-after-write verification and ZFS does, correct? Just trying to > clarify. Btrfs doesn't do that, and I'm not aware of such an option in ZFS. https://github.com/openzfs/zfs/issues/2526 https://www.illumos.org/issues/2008 Btrfs and ZFS both do checksum verification of every read, and also have a scrub option. -- Chris Murphy ___ 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
Re: New parallel port card won't work
On 2020-11-02 01:59, Samuel Sieb wrote: There's also a Linux driver available at https://www.asix.com.tw/en/support/download if you want to try it. You have to recompile the linux kernel ___ 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
Re: Deprecating SCP
Joe makes a good point re: hardening. We ( a very large IT company, top 10 in size) are mandated to have sftp turned off except on specific servers. As such, we use scp extensively. It would be better off for everybody involved to "fix" scp's shortcomings as opposed to expecting the world at large to drop scp, turn on sftp, and use sftp (not to mention that command line sftp pretty much stinks re: passing the commands needed to move files. --- Regards, Kevin Martin On Mon, Nov 2, 2020 at 10:14 AM Joe Wulf via users < users@lists.fedoraproject.org> wrote: > Improving the state of security for SCP is overdue. Like you've said, > Jakub, the code just hasn't been worked on in a long time, nor been > well-maintained. > > I am curious to better understand if the scp binary, as implemented, has > security-related issues of concern here (along with old code), or if the > protocol being used is the significant issue; or maybe a mixture of both. > > At this point, almost any direction to improve scp is welcome and > appreciated by many. One challenge for adoption of the method you are > proposing (and working on), is that conflict between the easy/casual use of > scp via established channels where ssh is already accepted (keys, etc) > versus those environments (or set of systems) where an sftp server running > is forbidden due to security hardening requirements. > > Security hardening is a scrupulous effort in many places. Reduce the > attack surface, is but one mantra. As others have pointed out, the ease > with which to quickly move some files will never go away, and in that > regard, scp has been 'good enough' both from a functionality, as well as > security-hardening, perspectives. > > Proposing/discussing how to approach the deprecation of > scp-as-we-know-it-today would help, too. > > Thank you. > > R, > -Joe Wulf > > On Monday, November 2, 2020, 10:54:59 AM EST, Jakub Jelen < > jje...@redhat.com> wrote: > > > On 11/2/20 4:36 PM, Kamil Dudka wrote: > > On Monday, November 2, 2020 3:44:39 PM CET Jakub Jelen wrote: > >> Hi Fedora users! > >> > >> Over the last years, there were several issues in the SCP protocol, > >> which lead us into discussions if we can get rid of it in upstream [1]. > >> Most of the voices there said that they use SCP mostly for simple ad-hoc > >> copy and because sftp utility does not provide simple interface to copy > >> one or couple of files back and forth and because of people are just > >> used to write scp rather than sftp. > >> > >> Some months ago, I wrote a patch [2] for scp to use SFTP internally > >> (with possibility to change it back using -M scp) and ran it through > >> some successful testing. The general feedback from upstream was also > >> quite positive so I would like to hear also opinions from our users. > >> > >> It still has some limitations (missing -3 support, it will not work if > >> the server does not run sftp subsystem, ...), but it should be good > >> enough for most common use cases. > >> > >> Today, I set up a copr repository with the current openssh from Fedora + > >> the patch [2] for anyone to test and provide feedback, either here on > >> the mailing list, or in the github PR according to ones preferences. > >> > >> I am looking for any kind of feedback from the idea through the > >> usability, implementation. Is this something you would like to see in > >> Fedora soon? Do you have something against this? Is your use case > missing? > >> > >> [1] > >> > https://lists.mindrot.org/pipermail/openssh-unix-dev/2020-June/038594.html > >> [2] https://github.com/openssh/openssh-portable/pull/194/ > >> [3] https://copr.fedorainfracloud.org/coprs/jjelen/openssh-sftp/ > > > > How is the "compatibility scpd to support old clients" going to differ > > from the current implementation? > > I can think of a solution that in the end, there will be just the server > parts of the current scp and the client code branches will be gone or > support sftp only. But this can change as we are not there yet. > > > libcurl implements its own SCP client over libssh. Will this > implementation > > continue to work after OpenSSH gets updated on servers? > > With the above update, everything will work as before -- it affects only > the client scp binary. > > > Applications often allow users to pass arbitrary URLs to libcurl. So > one can, > > for example, use scp:// URLs to specify a kickstart for Anaconda. The > fact > > that scp utility will be reimplemented over SFTP does not help much in > this > > case. Each build of libcurl that supports scp:// supports sftp:// as > well. > > But libcurl will not transmit scp:// requests over sftp:// in case SCP > is not > > supported by the remote server any more. > > As Simo wrote, I think it is something that will have to happen sooner > or later inside of libcurl or libssh or in users configurations. But > again, the above change should not have any effect on this. > > Regards, > -- > Jakub Jelen > Senior Software Engineer >
Re: systemd-resolved and NM-managed dnsmasq both running
On Mon, Nov 02, 2020 at 09:18:00AM -0600, Ian Pilcher wrote: > I've been using NetworkManager's dnsmasq plugin (dns=dnsmasq) on my > laptop for years. After upgrading to Fedora 33, I see that > systemd-resolved is running (as expected), but the NetworkManager- > spawned dnsmasq instance is also running. > > Is dnsmasq providing any benefit in this case? My understanding from > the earlier systemd-resolved threads is that it is supposed to handle > the "split DNS" scenario that led me to use dnsmasq in the first place. I have a similar configuration, and at first I tried to get the dnsmasq to be used by systemd-resolved but it kept "forgetting" it and switching back to what DHCP used, so I just stopped, disabled and masked systemd-resolved.service, deleted /etc/resolv.conf and restarted NetworkManager to get a working configuration back. -- Jonathan Billings ___ 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
Re: Deprecating SCP
Improving the state of security for SCP is overdue. Like you've said, Jakub, the code just hasn't been worked on in a long time, nor been well-maintained. I am curious to better understand if the scp binary, as implemented, has security-related issues of concern here (along with old code), or if the protocol being used is the significant issue; or maybe a mixture of both. At this point, almost any direction to improve scp is welcome and appreciated by many. One challenge for adoption of the method you are proposing (and working on), is that conflict between the easy/casual use of scp via established channels where ssh is already accepted (keys, etc) versus those environments (or set of systems) where an sftp server running is forbidden due to security hardening requirements. Security hardening is a scrupulous effort in many places. Reduce the attack surface, is but one mantra. As others have pointed out, the ease with which to quickly move some files will never go away, and in that regard, scp has been 'good enough' both from a functionality, as well as security-hardening, perspectives. Proposing/discussing how to approach the deprecation of scp-as-we-know-it-today would help, too. Thank you. R,-Joe Wulf On Monday, November 2, 2020, 10:54:59 AM EST, Jakub Jelen wrote: On 11/2/20 4:36 PM, Kamil Dudka wrote: > On Monday, November 2, 2020 3:44:39 PM CET Jakub Jelen wrote: >> Hi Fedora users! >> >> Over the last years, there were several issues in the SCP protocol, >> which lead us into discussions if we can get rid of it in upstream [1]. >> Most of the voices there said that they use SCP mostly for simple ad-hoc >> copy and because sftp utility does not provide simple interface to copy >> one or couple of files back and forth and because of people are just >> used to write scp rather than sftp. >> >> Some months ago, I wrote a patch [2] for scp to use SFTP internally >> (with possibility to change it back using -M scp) and ran it through >> some successful testing. The general feedback from upstream was also >> quite positive so I would like to hear also opinions from our users. >> >> It still has some limitations (missing -3 support, it will not work if >> the server does not run sftp subsystem, ...), but it should be good >> enough for most common use cases. >> >> Today, I set up a copr repository with the current openssh from Fedora + >> the patch [2] for anyone to test and provide feedback, either here on >> the mailing list, or in the github PR according to ones preferences. >> >> I am looking for any kind of feedback from the idea through the >> usability, implementation. Is this something you would like to see in >> Fedora soon? Do you have something against this? Is your use case missing? >> >> [1] >> https://lists.mindrot.org/pipermail/openssh-unix-dev/2020-June/038594.html >> [2] https://github.com/openssh/openssh-portable/pull/194/ >> [3] https://copr.fedorainfracloud.org/coprs/jjelen/openssh-sftp/ > > How is the "compatibility scpd to support old clients" going to differ > from the current implementation? I can think of a solution that in the end, there will be just the server parts of the current scp and the client code branches will be gone or support sftp only. But this can change as we are not there yet. > libcurl implements its own SCP client over libssh. Will this implementation > continue to work after OpenSSH gets updated on servers? With the above update, everything will work as before -- it affects only the client scp binary. > Applications often allow users to pass arbitrary URLs to libcurl. So one can, > for example, use scp:// URLs to specify a kickstart for Anaconda. The fact > that scp utility will be reimplemented over SFTP does not help much in this > case. Each build of libcurl that supports scp:// supports sftp:// as well. > But libcurl will not transmit scp:// requests over sftp:// in case SCP is not > supported by the remote server any more. As Simo wrote, I think it is something that will have to happen sooner or later inside of libcurl or libssh or in users configurations. But again, the above change should not have any effect on this. Regards, -- Jakub Jelen Senior Software Engineer Crypto Team, Security Engineering Red Hat, Inc. ___ 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 ___ 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:
Re: F32->F33: Upgrade or reinstall?
On Mon, 2020-11-02 at 08:19 -0500, Sam Varshavchik wrote: > Patrick O'Callaghan writes: > > > I'd normally upgrade, but my /dev/sda uses LVM to handle root, /home > > etc. and from what I read this cannot be converted directly to BTRFS, > > which I'm interested in using. > > > > What would be the best way to approach this?: > > > > 1) Do a system upgrade and then convert to BTRFS by backing everything > > up and restoring it (I'd need guidance on how to do this). > > > > 2) Do a complete system install and then restore from backups. > > > > I'm guessing that (2) is the simplest answer, but I'd appreciate any > > comments, especially from people who have actually done either of > > these. > > If you're set on this kind of a disruption, a clean install, followed by > restoring your home directory from backups, will be more reliable. > Attempting to do /full/ reinstall of the /entire/ system from backups is a > much more complicated affair. Your backup/restore method must correctly not > just reinstall files and set their ownership and permissions, but also all > other extended attributes, specifically selinux contexts. I'm not aware of > anything in Fedora that uses other extended attributes for something, but > there may be. > > This is less of an issue when restoring just your home directory from > backups. That makes sense, thanks. I will also need to restore some things in /etc of course, but that can be done manually. 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
Re: Deprecating SCP
On Mon, Nov 02, 2020 at 03:44:39PM +0100, Jakub Jelen wrote: > Over the last years, there were several issues in the SCP protocol, which > lead us into discussions if we can get rid of it in upstream [1]. Most of > the voices there said that they use SCP mostly for simple ad-hoc copy and > because sftp utility does not provide simple interface to copy one or couple > of files back and forth and because of people are just used to write scp > rather than sftp. > > Some months ago, I wrote a patch [2] for scp to use SFTP internally (with > possibility to change it back using -M scp) and ran it through some > successful testing. The general feedback from upstream was also quite > positive so I would like to hear also opinions from our users. Has that testing included performance measurements, both on high bandwidth low-latency transfers and low bandwidth high-latency transfers? At least in the past SFTP used to be worse than SCP on high-latency connections. Jakub ___ 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
Re: Deprecating SCP
On 02/11/2020 15:44, Jakub Jelen wrote: Hi Fedora users! Over the last years, there were several issues in the SCP protocol, which lead us into discussions if we can get rid of it in upstream [1]. Most of the voices there said that they use SCP mostly for simple ad-hoc copy and because sftp utility does not provide simple interface to copy one or couple of files back and forth and because of people are just used to write scp rather than sftp. Some months ago, I wrote a patch [2] for scp to use SFTP internally (with possibility to change it back using -M scp) and ran it through some successful testing. The general feedback from upstream was also quite positive so I would like to hear also opinions from our users. [..] In July there was an article in Fedoramagazine about switching from scp to rsync as "the OpenSSH project stated that they consider the scp protocol outdated, inflexible, and not readily fixed". In fact for the simple use "rsync FILE dest:DIR" instead of "scp FILE dest:DIR" is easy to do. I suppose it's time G P.S. Sorry for the mail Jakub, I did a "reply" instead of "Reply List" -- GianPiero Puccioni|Istituto dei Sistemi Complessi-CNR gianpiero.pucci...@isc.cnr.it |Via Madonna del Piano, 10 T:+39 0555226682 |50019 Sesto F. (Firenze) ITALY ___ 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
Re: Deprecating SCP
Hi. On Mon, 02 Nov 2020 15:44:39 +0100 Jakub Jelen wrote: > Is this something you would like to see in Fedora soon? No. I prefer a lot to use rsync, because scp: - has no dry-run mode - is not incremental - follows symlinks when used with the -r option - has too few options: no --chown --chgrp > Do you have something against this? No: users should be free to continue using it (but not with the -r option IMO). > Is your use case missing? With scp no, but I use sshfs for years. This is IMO something to promote. Ex: Example: a simple 3-way copy, assuming you have root SSH access (with keys) mkdir /mnt/hostA sshfs -o transform_symlinks root@hostA:/ /mnt/hostA rsync -a --delete /mnt/hostA/etc/skel/ root@hostB:/etc/skel -- francis ___ 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
Re: Deprecating SCP
On 11/2/20 4:36 PM, Kamil Dudka wrote: On Monday, November 2, 2020 3:44:39 PM CET Jakub Jelen wrote: Hi Fedora users! Over the last years, there were several issues in the SCP protocol, which lead us into discussions if we can get rid of it in upstream [1]. Most of the voices there said that they use SCP mostly for simple ad-hoc copy and because sftp utility does not provide simple interface to copy one or couple of files back and forth and because of people are just used to write scp rather than sftp. Some months ago, I wrote a patch [2] for scp to use SFTP internally (with possibility to change it back using -M scp) and ran it through some successful testing. The general feedback from upstream was also quite positive so I would like to hear also opinions from our users. It still has some limitations (missing -3 support, it will not work if the server does not run sftp subsystem, ...), but it should be good enough for most common use cases. Today, I set up a copr repository with the current openssh from Fedora + the patch [2] for anyone to test and provide feedback, either here on the mailing list, or in the github PR according to ones preferences. I am looking for any kind of feedback from the idea through the usability, implementation. Is this something you would like to see in Fedora soon? Do you have something against this? Is your use case missing? [1] https://lists.mindrot.org/pipermail/openssh-unix-dev/2020-June/038594.html [2] https://github.com/openssh/openssh-portable/pull/194/ [3] https://copr.fedorainfracloud.org/coprs/jjelen/openssh-sftp/ How is the "compatibility scpd to support old clients" going to differ from the current implementation? I can think of a solution that in the end, there will be just the server parts of the current scp and the client code branches will be gone or support sftp only. But this can change as we are not there yet. libcurl implements its own SCP client over libssh. Will this implementation continue to work after OpenSSH gets updated on servers? With the above update, everything will work as before -- it affects only the client scp binary. Applications often allow users to pass arbitrary URLs to libcurl. So one can, for example, use scp:// URLs to specify a kickstart for Anaconda. The fact that scp utility will be reimplemented over SFTP does not help much in this case. Each build of libcurl that supports scp:// supports sftp:// as well. But libcurl will not transmit scp:// requests over sftp:// in case SCP is not supported by the remote server any more. As Simo wrote, I think it is something that will have to happen sooner or later inside of libcurl or libssh or in users configurations. But again, the above change should not have any effect on this. Regards, -- Jakub Jelen Senior Software Engineer Crypto Team, Security Engineering Red Hat, Inc. ___ 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
Re: [Fedora] Deprecating SCP
On 11/2/20 3:57 PM, Walter Cazzola wrote: Hi, I don't know if and how the internet protocol scp: is related to the scp command. But I suppose it is. Hi, SCP is not an internet protocol -- it is simple protocol that is used inside of encrypted SSH session, similarly to SFTP protocol. The name comes from RCP which actually was unencrypted internet protocol and which is hopefully gone. I'm using scp: a lot to edit remote files with vim and I'm pretty sure that many remote admins are doing the same. So I'm wondering how this change will affect my use case scenario and if you have considered it when moving to sftp. That is a good question! When I try to use scp://host/file I am getting errors that vim is trying to use `rcp` command (yuck!). But using the same with sftp://host/file works like a charm. I believe vim is using just scp to fetch the file so if the connection to the server will work also with sftp, it should continue to work (but I recommend using sftp protocol anyway). The simplest way to try is to try with sftp:// or try the previously mentioned package, but my best bet is that it will keep on working as before (even though I never used this inside of vim up until today). Regards, Jakub Thank you Walter On Mon, 2 Nov 2020, Jakub Jelen wrote: Hi Fedora users! Over the last years, there were several issues in the SCP protocol, which lead us into discussions if we can get rid of it in upstream [1]. Most of the voices there said that they use SCP mostly for simple ad-hoc copy and because sftp utility does not provide simple interface to copy one or couple of files back and forth and because of people are just used to write scp rather than sftp. Some months ago, I wrote a patch [2] for scp to use SFTP internally (with possibility to change it back using -M scp) and ran it through some successful testing. The general feedback from upstream was also quite positive so I would like to hear also opinions from our users. It still has some limitations (missing -3 support, it will not work if the server does not run sftp subsystem, ...), but it should be good enough for most common use cases. Today, I set up a copr repository with the current openssh from Fedora + the patch [2] for anyone to test and provide feedback, either here on the mailing list, or in the github PR according to ones preferences. I am looking for any kind of feedback from the idea through the usability, implementation. Is this something you would like to see in Fedora soon? Do you have something against this? Is your use case missing? [1] https://lists.mindrot.org/pipermail/openssh-unix-dev/2020-June/038594.html [2] https://github.com/openssh/openssh-portable/pull/194/ [3] https://copr.fedorainfracloud.org/coprs/jjelen/openssh-sftp/ Thanks, -- Jakub Jelen Senior Software Engineer Crypto Team, Security Engineering Red Hat, Inc. ___ 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
Re: BTFS - Raid1 for System Disk
On 11/2/20 11:31 AM, Jorge Fábregas wrote: > I tried to followed link [1] but it doesn't work with Fedora33. Sorry, here it is: http://www.gattis.org/Work-and-Tech/operating-systems-and-applications/unix/file-systems/btrfs-raid-boot -- Jorge ___ 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
BTFS - Raid1 for System Disk
Hi everyone, I'm experimenting with Fedora 33 & BTRFS on VM for a setup I'd like to do in my desktop in the near future. I'd like to have my system drive with BTRFS on a RAID1 profile. I was experminenting with a simple / (root filesystem) subvolume but it appears GRUB2 can't work properly with it. I get the famous: "Sparse file is not allowed" during boot (and no way to access GRUB2 menu). It boots fine but I can't longer edit the GRUB2 menu during boot. Fine, I read somewhere that /boot wasn't allowed with BTRFS in Fedora? ok, I then tried to create a separate ext4 /boot partition (using Anaconda) but it created a mess (partition-wise) so I'm going to install it again with just one disk as /dev/vda1 for /boot and vda2 for BTRFS , then afterwards I'll copy partition tables to /dev/vdb, rsync /boot and balance to RAID1. I'd like my desktop to have a RAID1 setup for my main drive and be able to remove either disk and boot seamlessly. Is this possible with BTFS & GRUB2 these days? I tried to followed link [1] but it doesn't work with Fedora33. Does anyone know of any online guide to accomplish this with F33? Also , is it really necessary to have a separate /boot partition? Aren't there any workarounds? I'd like to keep stuff simple and have only BTRFS / & /home subvolumes. Thanks! -- Jorge ___ 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
systemd-resolved and NM-managed dnsmasq both running
I've been using NetworkManager's dnsmasq plugin (dns=dnsmasq) on my laptop for years. After upgrading to Fedora 33, I see that systemd-resolved is running (as expected), but the NetworkManager- spawned dnsmasq instance is also running. Is dnsmasq providing any benefit in this case? My understanding from the earlier systemd-resolved threads is that it is supposed to handle the "split DNS" scenario that led me to use dnsmasq in the first place. -- In Soviet Russia, Google searches you! ___ 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
Re: Deprecating SCP
On 11/2/20 8:44 AM, Jakub Jelen wrote: I am looking for any kind of feedback from the idea through the usability, implementation. Is this something you would like to see in Fedora soon? Do you have something against this? Is your use case missing? What impact will this have on compatibility with other operating systems (Windows 10, etc.)? -- In Soviet Russia, Google searches you! ___ 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
Re: [Fedora] Deprecating SCP
Hi, I don't know how if and how the internet protocol scp: is related to the scp command. But I suppose it is. I'm using scp: a lot to edit remote files with vim and I'm pretty sure that many remote admins are doing the same. So I'm wondering how this change will affect my use case scenario and if you have considered it when moving to sftp. Thank you Walter On Mon, 2 Nov 2020, Jakub Jelen wrote: Hi Fedora users! Over the last years, there were several issues in the SCP protocol, which lead us into discussions if we can get rid of it in upstream [1]. Most of the voices there said that they use SCP mostly for simple ad-hoc copy and because sftp utility does not provide simple interface to copy one or couple of files back and forth and because of people are just used to write scp rather than sftp. Some months ago, I wrote a patch [2] for scp to use SFTP internally (with possibility to change it back using -M scp) and ran it through some successful testing. The general feedback from upstream was also quite positive so I would like to hear also opinions from our users. It still has some limitations (missing -3 support, it will not work if the server does not run sftp subsystem, ...), but it should be good enough for most common use cases. Today, I set up a copr repository with the current openssh from Fedora + the patch [2] for anyone to test and provide feedback, either here on the mailing list, or in the github PR according to ones preferences. I am looking for any kind of feedback from the idea through the usability, implementation. Is this something you would like to see in Fedora soon? Do you have something against this? Is your use case missing? [1] https://lists.mindrot.org/pipermail/openssh-unix-dev/2020-June/038594.html [2] https://github.com/openssh/openssh-portable/pull/194/ [3] https://copr.fedorainfracloud.org/coprs/jjelen/openssh-sftp/ Thanks, -- ___ 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
Deprecating SCP
Hi Fedora users! Over the last years, there were several issues in the SCP protocol, which lead us into discussions if we can get rid of it in upstream [1]. Most of the voices there said that they use SCP mostly for simple ad-hoc copy and because sftp utility does not provide simple interface to copy one or couple of files back and forth and because of people are just used to write scp rather than sftp. Some months ago, I wrote a patch [2] for scp to use SFTP internally (with possibility to change it back using -M scp) and ran it through some successful testing. The general feedback from upstream was also quite positive so I would like to hear also opinions from our users. It still has some limitations (missing -3 support, it will not work if the server does not run sftp subsystem, ...), but it should be good enough for most common use cases. Today, I set up a copr repository with the current openssh from Fedora + the patch [2] for anyone to test and provide feedback, either here on the mailing list, or in the github PR according to ones preferences. I am looking for any kind of feedback from the idea through the usability, implementation. Is this something you would like to see in Fedora soon? Do you have something against this? Is your use case missing? [1] https://lists.mindrot.org/pipermail/openssh-unix-dev/2020-June/038594.html [2] https://github.com/openssh/openssh-portable/pull/194/ [3] https://copr.fedorainfracloud.org/coprs/jjelen/openssh-sftp/ Thanks, -- Jakub Jelen Senior Software Engineer Crypto Team, Security Engineering Red Hat, Inc. ___ 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
Re: F32->F33: Upgrade or reinstall?
Patrick O'Callaghan writes: I'd normally upgrade, but my /dev/sda uses LVM to handle root, /home etc. and from what I read this cannot be converted directly to BTRFS, which I'm interested in using. What would be the best way to approach this?: 1) Do a system upgrade and then convert to BTRFS by backing everything up and restoring it (I'd need guidance on how to do this). 2) Do a complete system install and then restore from backups. I'm guessing that (2) is the simplest answer, but I'd appreciate any comments, especially from people who have actually done either of these. If you're set on this kind of a disruption, a clean install, followed by restoring your home directory from backups, will be more reliable. Attempting to do /full/ reinstall of the /entire/ system from backups is a much more complicated affair. Your backup/restore method must correctly not just reinstall files and set their ownership and permissions, but also all other extended attributes, specifically selinux contexts. I'm not aware of anything in Fedora that uses other extended attributes for something, but there may be. This is less of an issue when restoring just your home directory from backups. pgpdrKO1865A9.pgp Description: PGP signature ___ 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
F32->F33: Upgrade or reinstall?
I'd normally upgrade, but my /dev/sda uses LVM to handle root, /home etc. and from what I read this cannot be converted directly to BTRFS, which I'm interested in using. What would be the best way to approach this?: 1) Do a system upgrade and then convert to BTRFS by backing everything up and restoring it (I'd need guidance on how to do this). 2) Do a complete system install and then restore from backups. I'm guessing that (2) is the simplest answer, but I'd appreciate any comments, especially from people who have actually done either of these. 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
Re: mkdir problem
On Mon, 02 Nov 2020 10:52:27 + Patrick O'Callaghan wrote: > On Mon, 2020-11-02 at 11:50 +0100, Frank Elsner via users wrote: > > Hi, > > > > I need help as I don't understand my problem. > > > > I've a local directory > > > > [root@siffux misc]# ls -la > > total 4 > > drwxr-xr-x 3 root root0 Nov 2 09:54 . > > dr-xr-xr-x. 21 root root 4096 Jul 7 13:28 .. > > drwxr-xr-x 2 root root0 Nov 2 09:54 Media > > > > I don't understand > > > > [root@siffux misc]# mkdir Backups > > mkdir: cannot create directory ‘Backups’: Permission denied > > Is the filesystem mounted read-only? No, problem solved. It was the running autofs. --Frank ___ 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
Re: mkdir problem
On Mon, 2020-11-02 at 11:50 +0100, Frank Elsner via users wrote: > Hi, > > I need help as I don't understand my problem. > > I've a local directory > > [root@siffux misc]# ls -la > total 4 > drwxr-xr-x 3 root root0 Nov 2 09:54 . > dr-xr-xr-x. 21 root root 4096 Jul 7 13:28 .. > drwxr-xr-x 2 root root0 Nov 2 09:54 Media > > I don't understand > > [root@siffux misc]# mkdir Backups > mkdir: cannot create directory ‘Backups’: Permission denied Is the filesystem mounted read-only? 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
Re: Install Fedora -
On Sun, 2020-11-01 at 19:00 -0700, Chris Murphy wrote: > On Sun, Nov 1, 2020 at 6:51 AM John Mellor wrote: > > On 2020-10-31 10:46 p.m., Tim via users wrote: > > > On Sat, 2020-10-31 at 16:11 +, lancelasset...@gmail.com wrote: > > > > Will NFS tell you data has been corrupted during the transfer and > > > > write process? > > > Does any filing system? In general, writes to storage are assumed to > > > have worked unless something throws up an error message. Your hard > > > drive could be silently corrupting data as it writes to the drive due > > > to various reasons (defects in its media, bugs in its firmware, > > > glitches from bad power supplies). You'd never know unless your > > > filing system did a sanity check after writing. Some specialised ones > > > might do that, but the average ones don't > > > > > You are correct for some very popular filesystems. EXT2/3/4, XFS, NTFS > > etc. will not detect this situation. However, newer filesystems (<10 > > years old) do handle silent data glitches, bad RAM and cosmic ray hits > > correctly. > > > > BTRFS has been the default filesystem on SUSE Linux for years, and is > > now the default filesystem on Fedora-33. ZFS is an optional filesystem > > on Ubuntu-20 and all the Berkeley-derived Unixen like FreeBSD, and > > standard on Oracle Linux and Solaris. BTRFS and ZFS are both COW > > filesystems using checksumming of both data and metadata. When you push > > something to the disk(s) with some kind of RAM error or power glitch, > > the first write will be stored with the error, and then the checksummed > > metadata is simply redirected to reference the new stuff. This will > > detect the checksum errors on the data on ZFS with the reread to verify > > the checksum, but I believe that BTRFS will return a successful write > > without one of the RAID configurations set on the pool. If you are > > running one of the RAID configurations, the checksum error will be > > detected before the write completes. To guard against on-disk > > corruption (bit rot), both ZFS and BTRFS will also correct it on the > > next read of that data if you are running the filesystem in one of the > > RAID-z configurations (multiple copies stored), or upon running a > > filesystem integrity check. > > Short story: [...] Thanks. That more or less matches what I thought. So BTRFS does not do read-after-write verification and ZFS does, correct? Just trying to clarify. 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
mkdir problem
Hi, I need help as I don't understand my problem. I've a local directory [root@siffux misc]# ls -la total 4 drwxr-xr-x 3 root root0 Nov 2 09:54 . dr-xr-xr-x. 21 root root 4096 Jul 7 13:28 .. drwxr-xr-x 2 root root0 Nov 2 09:54 Media I don't understand [root@siffux misc]# mkdir Backups mkdir: cannot create directory ‘Backups’: Permission denied [root@siffux misc]# ___ 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
Re: New parallel port card won't work
On 11/1/20 11:59 PM, ToddAndMargo via users wrote: On 2020-11-01 14:13, Samuel Sieb wrote: On 10/31/20 11:53 PM, ToddAndMargo via users wrote: # modprobe -r lp # modprobe -r parport_pc # modprobe parport_pc # modprobe lp # echo 9710 9900 > /sys/bus/pci/drivers/parport_pc/new_id But still no lp0 showing in CUPS or Printer Admin (notice I used the Linux term for it!) After running the new_id command, do "lspci -k" again and see if it picked it up. All the lcpci command pick it up. They always do. There is never an instance where they do not. # lspci -k -s 01:00.0 01:00.0 Parallel controller: MosChip Semiconductor Technology Ltd. MCS9900 Multi-I/O Controller Subsystem: Device a000:2000 There is one other possible option to try. echo ":01:00.0" > /sys/bus/pci/drivers/parport_pc/bind It probably won't work either. I haven't looked at the kernel code, but I wouldn't be surprised if there is some special code for each device, so adding a new device won't match any existing checks. After further research, I found the datasheet for this device is available. The parallel port should be function 2. I'm not entirely clear on what that means and the Subsystem line is showing the right value for the parallel port. Can you show the output of "lspci -nn" for the other devices around this one? There's also a Linux driver available at https://www.asix.com.tw/en/support/download if you want to try it. ___ 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
Re: New parallel port card won't work
On 2020-10-30 20:38, ToddAndMargo via users wrote: Hi All, Here we go again. I now have a Siig JJ-E01211-S1 Single Parallel Port PCIe Card https://stage.siig.com/products/it-products/serial-parallel/parallel/pcie/single-parallel-port-pcie-card.html System Requirements: ... Linux kernel 2.6 and later version Works with Linux but not supported And Printer Admin and CUPS do not find it. Troubleshooting: 1) connected a USB to Parallel converter card. Printer work fine 2) boot off of Fedora-Xfce-Live-x86_64-33-1.2.iso. Printer admin still can't find the card. 3) With # modprobe -r lp # modprobe -r parport_pc # modprobe parport_pc io=0x378 irq=11 # modprobe lp the card does show up and you can print to it, but the jobs instantly disappear and nothing shows on the printer's status screen What next? -T Here is some data on the card # udevadm info --attribute-walk /dev/lp0 Unknown device "/dev/lp0": No such device # lspci -nn | grep -i moschip 01:00.0 Parallel controller [0701]: MosChip Semiconductor Technology Ltd. MCS9900 Multi-I/O Controller [9710:9900] # lspci -vv -s 01:00.0 01:00.0 Parallel controller: MosChip Semiconductor Technology Ltd. MCS9900 Multi-I/O Controller (prog-if 03 [IEEE1284]) Subsystem: Device a000:2000 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Interrupt: pin A routed to IRQ 11 Region 0: I/O ports at e010 [disabled] [size=8] Region 1: I/O ports at e000 [disabled] [size=8] Region 2: Memory at ac001000 (32-bit, non-prefetchable) [disabled] [size=4K] Region 5: Memory at ac00 (32-bit, non-prefetchable) [disabled] [size=4K] Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: Data: Capabilities: [78] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [80] Express (v1) Legacy Endpoint, MSI 00 DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <1us, L1 <2us ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr- TransPend- LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s (ok), Width x1 (ok) TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb: Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending- InProgress- VC1: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable- ID=0 ArbSelect=Fixed TC/VC=00 Status: NegoPSiig JJ-E01211-S1 MosChip MCS9900 parallel port card not recognizedending- InProgress- Capabilities: [800 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+ AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn- MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- HeaderLog: I just opened: Siig JJ-E01211-S1 MosChip MCS9900 parallel port card not recognized: https://bugzilla.redhat.com/show_bug.cgi?id=1893631 ___ 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
Re: New parallel port card won't work
On 11/1/20 11:59 PM, ToddAndMargo via users wrote: On 2020-11-01 14:13, Samuel Sieb wrote: On 10/31/20 11:53 PM, ToddAndMargo via users wrote: # modprobe -r lp # modprobe -r parport_pc # modprobe parport_pc # modprobe lp # echo 9710 9900 > /sys/bus/pci/drivers/parport_pc/new_id But still no lp0 showing in CUPS or Printer Admin (notice I used the Linux term for it!) After running the new_id command, do "lspci -k" again and see if it picked it up. All the lcpci command pick it up. They always do. There is never an instance where they do not. You're misunderstanding what I meant by "pick it up". I'm looking for a "Kernel driver in use:" or "Kernel modules:" line which doesn't seem to be showing up. "lspci" will always show the device because it exists regardless of whether or not there's a driver for it. # lspci -k -s 01:00.0 01:00.0 Parallel controller: MosChip Semiconductor Technology Ltd. MCS9900 Multi-I/O Controller Subsystem: Device a000:2000 > If not, then try "echo 1 > /sys/bus/pci/rescan" and check > again. Ran it anyway. No joy. Strange. I wonder why that isn't working. Given the similar supported ids, I expected that to work. Sorry, I have no more suggestions. Btw, your original attempt at using the legacy ports is certainly not going to work. I saw this in one of your earlier emails: Region 0: I/O ports at e010 [disabled] [size=8] Region 1: I/O ports at e000 [disabled] [size=8] Region 2: Memory at ac001000 (32-bit, non-prefetchable) [disabled] [size=4K] Region 5: Memory at ac00 (32-bit, non-prefetchable) [disabled] [size=4K] ___ 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
