Re: many F33 deltarpm rebuilds failing with md5 mismatch error
I'm seeing this again with the latest F33 push with texlive RPMs, using the master mirror (dl.fedoraproject.org). It says "Some packages were not download. Retrying." and then proceeds to download 194 RPMs, out of the original 259. ___ 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: automount requests
On Wed, Dec 30, 2020 at 10:12 AM Greg Woods wrote: > > My logwatch each day has dozens of messages like this: > > pub.automount: Got automount request for /pub, triggered by 242640 (PT3122): > 1 Time(s) > > I want to determine why this is happening, because the drive containing /pub > (on a different machine mounted via NFS) is spun down when idle, and these > events are likely causing it to spin up. My understanding is that the part > inside the parentheses is the command name of the process that triggered it, > but I don't know what the "PT" syntax means. > One of those should be PID. -- 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: btrfs or ext4
On Mon, Dec 28, 2020 at 2:33 AM François Patte wrote: > > Bonjour, > > I try to build a home nas to make a dlna server for audio, video and > pictures. > > I have 2 disks for the data which I want to be mounted in raid1 (software). > > I formated the two disks using btrfs > (mkfs.btrfs -m raid1 -d raid1 /dev/sda /dev/sdb) > > It works but, up to now, I can't see the advantages of this file system > vs ext4 managed by mdadm. > > One disadvantage is that it seems that monitoring the system is not > possible in case of disk failure for instance. Btrfs in a raid1 configuration is significantly different than either mdadm raid or single disk Btrfs. It will self-heal, unambiguously, both metadata and data. It detects corruption including bit rot, torn writes, misdirected writes, even when the drive doesn't report any error. It finds the good copy, and fixes up the bad copy. This happens passively during normal use. The same repair principle applies when scrubbing. A scrub reads all metadata and data, but not unused areas. mdadm raid depends exclusively on drive reported errors, it has no independent means of knowing which copy of a block is valid, because it has no integrity checking. In the case of ext4/xfs metadata checksumming detecting a checksum error in its own metadata, it doesn't know which drive contains the correct copy, and neither does mdadm. Intentionally mismatching different make/model drives actually results in a more reliable setup on Btrfs because any firmware bugs in either drive are isolated. Any bug resulting in corruption on one drive, gets fixed by btrfs from the (meta)data on the other drive. With a regular scrub you have less of a chance of getting bitten by such defects. Depending on the size of the drives and how much data is on them, 'btrfs replace' can be quite a lot faster when replacing a failed drive. This uses a variation on scrub to replicate (meta)data onto a new device. I definitely recommend 'btrfs replace' as a go to for replacing drive, rather than 'btrfs device add' followed by 'btrfs device delete'. Likewise, this will do fixups as problems are encountered as long as there's a good copy. Btrfs also won't kick a drive out of a pool when misbehaving. Kicking a drive out means any partial redundancy it could provide, is lost. Since Btrfs can unambiguously determine if any reads from a drive are corrupt, it's in a position to keep using it and handle the errors. There is an option for 'btrfs replace' to only use the drive being replaced if there are no other good copies of (meta)data found on other drives to make replacement go faster. Bitrot with anything that's already compressed, like audio, video, and images, tends to cause significantly more damage than a mere bit or byte flip might otherwise do. Detecting this and preventing corruption from replicating is a significant feature of Btrfs. Also the ability to add drives and grow the array is probably more straight forward and tolerant of different sized drives. I don't mean users will necessarily avoid confusion but the file system itself can handle it if you add oddly sized drives one after another. 'btrfs device add' iimplies mkfs, and resize. And it'll attempt to balance based on the drives with the most free space available. It is certainly possible to get confused if you don't add two drives at a time of equal size. As for monitoring, nagios check_btrfs might do what you want: https://github.com/knorrie/python-btrfs/blob/master/examples/nagios/plugins/check_btrfs There is a rather pernicious problem using consumer drives on Linux to be aware of that affects mdadm, lvm, Btrfs and (I assume) ZFS raids. And that's this esoteric annoyance of timeout mismatches: https://raid.wiki.kernel.org/index.php/Timeout_Mismatch The gist of that is, the drive firmware's command time out needs to happen before the kernel's. The typical point of confusion is that the kernel's command timer looks like it's a device timer because it's a per block device setting in sysfs. The ideal scenario is to not change the kernel's timer, but use 'smartctl -l scterc,70,70' using something like /dev/disk/by-id in a udev rule, to tell the drive to give up on errors quickly. 70 deciseconds is typical. All drives use deciseconds. If the drive has no configurable SCT ERC, then you have to change the kernel's timeout. If you don't, the kernel thinks the drive isn't responding, does a link reset, and now the whole command queue is lost and we have no idea why the drive wasn't responding. I figure a greater than 90% chance it's a bad sector and the drive is intentionally not responding because it's in "deep recovery" if it's a consumer drive. I know. I know. Sounds like bat guano. There is a dracut bug that could cause some confusion if the drives aren't both available at mount time. The btrfs udev rule causes a wait for all btrfs devices to appear for a particular fs UUID before systemd will attempt to mount it, to prevent mount failure. This
Re: Failed to start dnf makecache
On Dec 30, 2020, at 13:49, Neal Becker wrote: > > Thanks for the suggestion, > > No, rpm -qa runs just fine. Could be that the selinux labels are wrong, and cron and the dnf subprocesses can’t read the files. A ‘restorecon’ on the directory probably will fix that — 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: Newbie questions - Rust
On 31/12/2020 06:24, Patrick O'Callaghan wrote: On Wed, 2020-12-30 at 14:45 -0600, David wrote: Regarding Fedora topics for 2021: I am just curious what the general direction of rust is - especially in Fedora. Is the plan to replace specific applications or dependencies with rust ? Or to someday have a Fedora version that uses as much of rust were feasible ? What rust application should I install to give it a try ? Is the use of rust still just for developers ? Rust is a programming language. How would it not be "for developers"? I suppose if someone is truly interested in rust they could go to https://www.rust-lang.org and join the rust community. --- 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: Newbie questions - Rust
On Wed, 2020-12-30 at 14:45 -0600, David wrote: > Regarding Fedora topics for 2021: > > I am just curious what the general direction of rust is - especially in > Fedora. > > Is the plan to replace specific applications or dependencies with rust ? > > Or to someday have a Fedora version that uses as much of rust were feasible > ? > > What rust application should I install to give it a try ? > > Is the use of rust still just for developers ? Rust is a programming language. How would it not be "for developers"? 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
Newbie questions - Rust
Regarding Fedora topics for 2021: I am just curious what the general direction of rust is - especially in Fedora. Is the plan to replace specific applications or dependencies with rust ? Or to someday have a Fedora version that uses as much of rust were feasible ? What rust application should I install to give it a try ? Is the use of rust still just for developers ? David Locklear ___ 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: Failed to start dnf makecache
Thanks for the suggestion, No, rpm -qa runs just fine. On Wed, Dec 30, 2020 at 11:45 AM Jorge Fábregas wrote: > On 12/30/20 12:18 PM, Neal Becker wrote: > > Dec 30 11:01:29 nbecker8 dnf[1421142]: Error: Error: rpmdb open failed > > Do you get errors when you perform: rpm -qa ??? If so, this could be a > corrupted RPM database. > > If so try Method #1 listed here: > > https://www.cyberciti.biz/tips/rebuilding-corrupted-rpm-database.html > > -- > 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 > -- *Those who don't understand recursion are doomed to repeat 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
automount requests
My logwatch each day has dozens of messages like this: pub.automount: Got automount request for /pub, triggered by 242640 (PT3122): 1 Time(s) I want to determine why this is happening, because the drive containing /pub (on a different machine mounted via NFS) is spun down when idle, and these events are likely causing it to spin up. My understanding is that the part inside the parentheses is the command name of the process that triggered it, but I don't know what the "PT" syntax means. Thanks for any info, --Greg ___ 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: Failed to start dnf makecache
On 12/30/20 12:18 PM, Neal Becker wrote: > Dec 30 11:01:29 nbecker8 dnf[1421142]: Error: Error: rpmdb open failed Do you get errors when you perform: rpm -qa ??? If so, this could be a corrupted RPM database. If so try Method #1 listed here: https://www.cyberciti.biz/tips/rebuilding-corrupted-rpm-database.html -- 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
Failed to start dnf makecache
Any idea how to debug this? Dec 30 11:01:29 nbecker8 systemd[1]: Starting dnf makecache... Dec 30 11:01:29 nbecker8 dnf[1421142]: error: rpmdb: BDB0113 Thread/process 2496606/140314318812864 failed: BDB1507 Thread died in Berkeley DB library Dec 30 11:01:29 nbecker8 dnf[1421142]: error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery Dec 30 11:01:29 nbecker8 dnf[1421142]: error: cannot open Packages index using db5 - (-30973) Dec 30 11:01:29 nbecker8 dnf[1421142]: error: cannot open Packages database in /var/lib/rpm Dec 30 11:01:29 nbecker8 dnf[1421142]: Error: Error: rpmdb open failed Dec 30 11:01:29 nbecker8 systemd[1]: dnf-makecache.service: Main process exited, code=exited, status=1/FAILURE Dec 30 11:01:29 nbecker8 systemd[1]: dnf-makecache.service: Failed with result 'exit-code'. Dec 30 11:01:29 nbecker8 systemd[1]: Failed to start dnf makecache. -- *Those who don't understand recursion are doomed to repeat 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: F33 just pretends to print
On 12/30/20 11:15 AM, Michael Hennebry wrote: > ## added > > Thanks again. You're welcome. Did the printer finally work? I'd like to know if I wasn't just lucky! For years I used to have Postscript printers, connected thru the network via IPP. All I needed was a simple PPD file and that was it. I wasn't so pleased with the idea of purchasing this Brother printer, where rasterization is performed on your PC, and you have to install special drivers & filters from the manufacturer. However, the Linux support was there and many Linux users confirmed it. I also couldn't resist the cheap price for this laser "winprinter" :) All was good until I bumped into this issue with Fedora 33. That's when I remembered how easy & straightforward my previous printers were. -- 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: Btrfs labels
On Wed, 2020-12-30 at 10:42 -0400, Jorge Fábregas wrote: > On 12/30/20 10:32 AM, Patrick O'Callaghan wrote: > > # partprobe -s /dev/sdc > > /dev/sdc: msdos partitions 1 > > I meant to say "partprobe /dev/sdc" so that you can, afterwards, see the > *correct* label with lsblk... I see. Yes, that worked, thanks. 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: systemd automount
On 30/12/2020 22:09, François Patte wrote: Bonjour, I configured an automount of directories located on a server on my local network: in the fstab of a computer on the network I put the line: 192.168.1.16:/data /home/patte/data nfs noauto,rw,user,nofail,x-systemd.automount,x-systemd.mount-timeout=30 0 0 It works. If the server is down, no problem, the boot of the computer is OK. But if the server gets down while the computer is working, this turns in an awful way: everything on the computer becomes very slow, opening a file manager takes ages, the ls command does no work and it is impossible to unmount the directory on which the server is mounted. Did I forgot an option in the fstab? Is there a way to solve this problem without shuting down the computer (which also takes ages...). Try adding "soft" to the options. --- 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: F33 just pretends to print
On Wed, 30 Dec 2020, Jorge Fábregas wrote: On 12/30/20 1:35 AM, Michael Hennebry wrote: I've cloned the repository, but I'm unclear on a couple things Hi, On a F33 fresh install I only had to to this as root: dnf update (important; needed so that last step works properly) dnf install gcc-c++ cmake cups-devel## what I need git clone https://github.com/pdewacht/brlaser cd brlaser ## what I need cmake . make make install dnf history undo last (as I no longer need the stuff needed to build; SSDs are expensive!) ## added Thanks again. -- Michael henne...@web.cs.ndsu.nodak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards___ 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: F33 just pretends to print
On Tue, Dec 29, 2020 at 10:35 PM Michael Hennebry wrote: > I've cloned the repository, but I'm unclear on a couple things: > From README.md: > > To compile brlaser you'll need CMake and the CUPS development packages > > (libcups2-dev, libcupsimage2-dev or similar). > > I've tried yum provides '*libcups*dev*' , > but no matches found. Those are Debian package names. For Fedora, try cups-devel. -- Jerry James http://www.jamezone.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: Btrfs labels
On 12/30/20 10:32 AM, Patrick O'Callaghan wrote: > # partprobe -s /dev/sdc > /dev/sdc: msdos partitions 1 I meant to say "partprobe /dev/sdc" so that you can, afterwards, see the *correct* label with lsblk... -- 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: Btrfs labels
On Wed, 2020-12-30 at 10:21 -0400, Jorge Fábregas wrote: > On 12/30/20 10:09 AM, Patrick O'Callaghan wrote: > > Has the label changed or not? > > Did you try: > > partprobe /dev/sdc # partprobe -s /dev/sdc /dev/sdc: msdos partitions 1 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: Btrfs labels
On 12/30/20 10:09 AM, Patrick O'Callaghan wrote: > Has the label changed or not? Did you try: partprobe /dev/sdc ? -- 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: F33 just pretends to print
On 12/30/20 1:35 AM, Michael Hennebry wrote: > I've cloned the repository, but I'm unclear on a couple things Hi, On a F33 fresh install I only had to to this as root: dnf update (important; needed so that last step works properly) dnf install gcc-c++ cmake cups-devel git clone https://github.com/pdewacht/brlaser cd brlaser cmake . make make install dnf history undo last (as I no longer need the stuff needed to build; SSDs are expensive!) Then I plugged the USB cable and printer was configured automatically (and working perfectly). Hope that helps. -- 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 automount
Bonjour, I configured an automount of directories located on a server on my local network: in the fstab of a computer on the network I put the line: 192.168.1.16:/data /home/patte/data nfs noauto,rw,user,nofail,x-systemd.automount,x-systemd.mount-timeout=30 0 0 It works. If the server is down, no problem, the boot of the computer is OK. But if the server gets down while the computer is working, this turns in an awful way: everything on the computer becomes very slow, opening a file manager takes ages, the ls command does no work and it is impossible to unmount the directory on which the server is mounted. Did I forgot an option in the fstab? Is there a way to solve this problem without shuting down the computer (which also takes ages...). Thank you for helping. -- François Patte UFR de mathématiques et informatique Laboratoire CNRS MAP5, UMR 8145 Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)6 7892 5822 http://www.math-info.univ-paris5.fr/~patte FSF https://www.fsf.org/blogs/community/presenting-shoetool-happy-holidays-from-the-fsf OpenPGP_0x744E82D9D855D895.asc Description: application/pgp-keys OpenPGP_signature Description: OpenPGP digital 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
Btrfs labels
I changed a Btrfs label: $ sudo btrfs filesystem label /storage home < Before [poc@Bree Working]$ sudo btrfs filesystem label /storage storage [poc@Bree Working]$ sudo btrfs filesystem label /storage storage<-- After But: $ lsblk -af NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT [...] sdc └─sdc1 btrfshome 6496d6da-6b7a-4cdd-9bb8-767c08d1c84e 951.9G49% /storage Has the label changed or not? 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: vncserver program disappered on FC32??
On Wed, 30 Dec 2020 09:16:05 -0400 George N. White III wrote: > SPICE has been deprecated inRHEL 8 And here I was hoping it would some day have 3D graphics support :-). ___ 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: many F33 deltarpm rebuilds failing with md5 mismatch error
On Wed, 30 Dec 2020 07:08:59 - Andre Robatino wrote: > This would happen occasionally before but happens almost all the time now. I haven't noticed an increased failure rate, but I have noticed that I always get a mis-match on kernel rpms, and even when it does work it tell me things like 1% saved (which doesn't really seem worth 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: vncserver program disappered on FC32??
On Thu, 24 Dec 2020 at 13:29, Robert G. (Doc) Savage via users <
users@lists.fedoraproject.org> wrote:
> On Wed, 2020-12-23 at 18:15 +1000, Michael D. Setzer II via users wrote:
>
>
> I think if you try and run a local session and vnc session with both using
> gnome desktop there are issues with it. But I always run the vnc session
> with the xfce desktop and never had a problem. I've also had no problem
> running xfce locally with a vnc xfce session. Seems gnome is doing
> something with dbus, and causes a conflict with both sessions trying to
> use the same dbus settings??
>
>
> My situation is similar, except that I use MATE exclusively. I am trying
> to understand why the upstream maintainer's solution allows only a single
> TigerVNC logon using a particular UserID. In other words, if I have a local
> USER-A and a TigerVNC USER-A, if one is logged on the other cannot. Does
> this mean that a TigerVNC USER-A will not have access to local USER-A's
> home directory, and vice versa. If so, this is ludicrous.
>
> If TigerVNC has been so badly mangled in the name of systemd support, what
> alternative VNC can folks recommend in its place? I seriously need one to
> support development of virtual machines hosted on a server with huge
> storage, and the local console of that storage machine is not in a suitable
> place for development.
>
My use case needs VM's with a number of default installs of popular linux
distros in order to support specialized applications for users scattered
around the globe, so I can't avoid GNOME. With Fedora 29-32 I was using
SPICE on the console of the system (located in a different building, so not
always convenient) that hosted the VM's. Fedora 33 came along at the same
time as new versions of the applications and some new hardware, so I
haven't had time to look after the VM's. Getting remote access to the
VM's is on my todo list.
Some of my colleagues use macOS so I may need to add that to the mix.
SPICE ("The SPICE project aims to provide a complete open source solution
for remote access to virtual machines in a seamless way so you can play
videos, record audio, share usb devices and share folders without
complications." --https://www.spice-space.org/index.html), is not a
long-term option:
SPICE has been deprecated inRHEL 8
In RHEL 8.3, the SPICE remote display protocol has been deprecated. Note
that SPICE will remain supported in RHEL 8, but Red Hat recommends using
alternate solutions for remote display streaming:
- For remote console access, use the VNC protocol.
- For advanced remote display functions, use third party tools such
as RDP, HP RGS, or Mechdyne TGX.
I have used VirtualBox RDP support in an "enterprise" environment where
Windows was the "desktop standard", but I'm not familiar with HP RGS
or Mechdyne TGX
Re: Do you disable IPV6? - Fedora Workstation
On 30.12.2020 05:58, Chris Adams wrote: You cannot have NAT without the exact same state tracking and ALGs of a stateful firewall. guess why it is easier to break through NAT than through a stateful firewall ... smime.p7s Description: S/MIME Cryptographic 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
Re: Do you disable IPV6? - Fedora Workstation
On 29.12.2020 15:32, Chris Adams wrote: Once upon a time, Neal Becker said: Let me say up front I'm not very knowledgeable about v6 yet. One reason I don't want to enable it is the exact flip side of the address scarcity of v4. Because of that, external connections are nat'd. That seems to me to offer an additional layer of protection for devices on my network, they don't have externally routeable addresses. I think that is not true if I turn on v6. Is this correct? There is no NAT for IPv6, but that's a feature. indeed, there is no need for NAT, but you can have it, if you want see RFC 4193, the pendant to RFC 1918 ... NAT doesn't really add any security; this is wrong, the best security at all for which you don't have to do anything is included with NAT or how can you access my PC with e.g. 10.0.8.15? NAT is a combination of two things: a stateful firewall this is wrong, NAT is not a stateful firewall; or in other words your two sentences disagree or you really mean by "NAT doesn't really add any security" that a stateful firewall doesn't have any security and is useless ... smime.p7s Description: S/MIME Cryptographic 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
Re: Do you disable IPV6? - Fedora Workstation
On 29.12.2020 07:10, Ed Greshko wrote: On 29/12/2020 12:44, Tim via users wrote: The key issue is "need." I'm unaware of anything, so far, that actually needed IPv6. As yet, I think everything is still accessible through IPv4 (which is probably why my ISP is dragging their heels on making IPv6 work). When I first configured the tunnel I didn't "need" it either. But since the tunnel was free I figured it was a good opportunity experiment with it and learn about IPv6. and the most important, this is a good thing to make things IPv6 compatible; the only device which has disabled IPv6 is my printer as it can't be configured with a fixed IPv6 - only with SLAAC, which I don't use; by the way Google's Android hasn't learnt to deal with stateful DHCPv6 yet ... either IPv6 will be used as the only internet protocol in the future or it is used only be freaks now? smime.p7s Description: S/MIME Cryptographic 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
