Re: entropy generation
On Fri, 1 Jan 2021 19:06:44 -0700 Chris Murphy wrote: > You can remove the rng-tools package if you want. It's being removed > in Fedora 34. So where does random data come from in f34? ___ 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: entropy generation
On Fri, Jan 1, 2021 at 6:40 PM Frank McCormick wrote: > > Running Fedora 33 under systemd. > > Lately my journal log has been spammed with hundreds of these lines: > > Jan 01 20:26:56 localhost.localdomain rngd[645]: Entropy Generation is > slow, consider tuning/adding sources > Jan 01 20:26:56 localhost.localdomain rngd[645]: Entropy Generation is > slow, consider tuning/adding sources > Jan 01 20:26:56 localhost.localdomain rngd[645]: Entropy Generation is > slow, consider tuning/adding sources > Jan 01 20:26:56 localhost.localdomain rngd[645]: Entropy Generation is > slow, consider t > > What can I do about this. You can remove the rng-tools package if you want. It's being removed in Fedora 34. https://pagure.io/fedora-comps/c/1ae4e1840fd996445b47ab7a4adfa443eee48639?branch=master -- 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
entropy generation
Running Fedora 33 under systemd. Lately my journal log has been spammed with hundreds of these lines: Jan 01 20:26:56 localhost.localdomain rngd[645]: Entropy Generation is slow, consider tuning/adding sources Jan 01 20:26:56 localhost.localdomain rngd[645]: Entropy Generation is slow, consider tuning/adding sources Jan 01 20:26:56 localhost.localdomain rngd[645]: Entropy Generation is slow, consider tuning/adding sources Jan 01 20:26:56 localhost.localdomain rngd[645]: Entropy Generation is slow, consider t What can I do about 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: systemd automount
On Jan 1, 2021, at 12:10, Jorge Fábregas wrote: > > Is there a reason why Anaconda create /etc/fstab entries on a fresh > installation of Fedora 33? > > Food for thought. Probably because OS-related mountpoints need to be in the fstab for the initrd and other related boot services. An automount that requires networking is best left out. I prefer to never touch fstab on my systems, leaving the installer to create them. Mostly because automation is paramount and fstab is a monolithic config file, and modifying it with tools like puppet or Ansible can leave it in a bad state. Systemd units can be dropped in and you can set up dependencies with the systemd units. — 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: btrfs or ext4
On Fri, Jan 1, 2021 at 6:47 AM Patrick O'Callaghan wrote: > > My current backup tool is BorgBackup, which does compression and > deduplication but took some effort to set up correctly, though it's > working now. Borg is awesome.[1] Any backup you use is better than none. So I'm not going to suggest a substitution. Instead, I suggest if you're thinking of alternatives, keep the one you know in place while becoming familiar with the alternative. i.e. two backups are better than one! Many eggs in many baskets! >However it seems that Btrfs can do both these things, so > is there a case to be made for just setting it up that way, and using > send and receive for the actual copying instead of Borg? It would have > the advantage of making the backed-up files a little more accessible > without special tools. It's true. I use a variation on this article's approach: https://fedoramagazine.org/btrfs-snapshots-backup-incremental/ I can elaborate on that upon request, but probably start a new thread. I haven't done so myself, but you could checkout btrbk [1] I just came across Pika Backup which is a simplified front end for Borg. Anyone not doing backups should take a peek at Pika. It doesn't offer scheduled backups yet but can do either local or remote backups. Enormous amounts of freedom and anxiety go away if you have good backups. It's so stress reducing that I'm 100% certain that people with backups are less prone to panic induced data loss. And I've seen a lot of panic induced data loss: people freak out so badly it's like bull in China shop, and just cause more damage than if they'd just tiptoed out, and only as questions without doing *anything* until understanding the problem first. -- 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: F33 just pretends to print
On Wed, 30 Dec 2020, Jorge Fábregas wrote: 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). Worked for me, although it defaulted to single-sided. I added "another" printer with the name and configuration I wanted. That also worked. Note that, as expected, "make install" requires root privileges. When installing from source, I prefer to manipulate ownership. That way possibly buggy/hostile code does not have free reign. -- 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: btrfs or ext4
On Thu, Dec 31, 2020 at 1:58 PM Chris Murphy wrote: > > And the other one: > > btrfs device add /dev/sdXY /mnt/btrfs > btrfs balance start -dconvert=raid1 -mconvert=raid1 /mnt/btrfs It's not obvious that 'btrfs dev add' implies a few things: - mkfs. It will write Btrfs super blocks on this device and zero the areas that ordinarily get zero'd. If it detects anything it recognizes like ext4, xfs, another btrfs, maybe mdadm super blocks (not sure) it will refuse. You'll either need to wipefs the target partition, or use the -f option when adding the device. - filesystem resize. Adding a device grows the file system. Removing a device shrinks it. - conversion to raid1 will read all data, and write it back out as raid1 chunks to each of the two devices per block group (i.e. one block group becomes two chunks, one per device). One day we may have a kind of optimization like replace and use a scrub to replicate the data. But right now it will read from devid1 and then write out a new pair of chunks to both devid1 and devid2. Mirroring on Btrfs is per blockgroup, it's not mirroring an entire device. - If you like the idea of doing a regular timed scrub, which reads all the data on a Btrfs file system, and will report on any problems found and whether they were fixed up: the 'btrfsmaintenance' package is in Fedora repo. It contains a bunch of service units and timers for Btrfs related things, all of them are disabled by default. You can configure and enable the scrub timer to do a scrub once per month if you wish. I do a scrub once per month lazy style (manually and when I remember to do it). I don't do any other maintenance on any of my Btrfs file systems (either manually or scheduled). -- 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: systemd automount
On 1/1/21 12:52 PM, Jonathan Billings wrote: > Is there a reason why people are using fstab entries with long and > hard to read arguments instead of using .automount and .mount systemd > units? Is there a reason why Anaconda create /etc/fstab entries on a fresh installation of Fedora 33? Food for thought. -- 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: systemd automount
On Fri, Jan 01, 2021 at 11:52:52AM -0500, Jonathan Billings wrote: > Is there a reason why people are using fstab entries with long and hard to > read arguments instead of using .automount and .mount systemd units? > Systemd is just dynamically generating the units from the fstab entries > every boot, and they’re significantly easier to read as a plain old > systemd unit. I'm doing it because old habits die hard. :) -- Matthew Miller Fedora Project Leader ___ 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 Dec 31, 2020, at 22:49, Ed Greshko wrote: > > I have no idea of the history. But, being the curious type, I just booted an > F18 live iso and > the man page for systemd.mount only specified x-systemd.device-timeout. I > have no idea > if the other options actually existed and this was just an omission in the > documentation. Or, > if they were not yet implemented. Is there a reason why people are using fstab entries with long and hard to read arguments instead of using .automount and .mount systemd units? Systemd is just dynamically generating the units from the fstab entries every boot, and they’re significantly easier to read as a plain old systemd unit. — 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: cassert
On Fri, Jan 1, 2021 at 6:41 AM Patrick Dupre wrote: > I installed octave-devel > > Where can I find the package cassert ? Install the gcc-c++ package; cassert is a C++ header. -- 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: kdenlive not supporting internal laptop camera?
On Thu, Dec 31, 2020 at 6:50 PM Roger Heflin wrote: > I don't know about kdenlive, but you might try obs-studio, it works > very well for both recording and streaming. > > > On Thu, Dec 31, 2020 at 5:36 PM Neal Becker wrote: > > > > I need to record a video using my laptop builtin camera. The camera > works fine in other apps. I tried kdenlive installed from rpmfusion, but > there doesn't seem to be any choice for the camera input. > > Settings/configure kdenlive/capture only has tabs for: > > screencapture, blackmagic, and audio. When I search the web it seems I > should have a tab for ffmpeg, but it's not there. It does appear from > help/about that kdenlive was built with ffmpeg. > > > > Any ideas? > > Thanks, > > Neal > One option noone mentioned is to use a chrome extension. There are a number of them, one that seems good to me is called "screen recorder", surprisingly. ___ 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 Thu, 2020-12-31 at 13:58 -0700, Chris Murphy wrote: > On Thu, Dec 31, 2020 at 12:18 PM Samuel Sieb wrote: > > > > On 12/31/20 4:03 AM, Patrick O'Callaghan wrote: > > > On Wed, 2020-12-30 at 20:16 -0700, Chris Murphy wrote: > > > > 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. > > > > > > I currently have mdm RAID1 on two external drives that are used only > > > for backup. They are formatted as ext4. What would be the recommended > > > way to convert them to Brfs RAID1? > > > > Chris can correct me if I'm wrong, but this seems to be the simplest > > method. Remove one of the drives from the array. Format it as btrfs. > > Copy the files from the raid onto it. Add the other drive to btrfs > > configuring it as raid. I can't give you any specific btrfs commands > > though. > > Yeah I'm pretty conservative when it comes to breaking a raid apart > because it is introducing risk by reducing redundancy. I'd say it's > better to get a 3rd drive. But, wie du willst. > > rsync -a /mnt/mdraid/ /mnt/btrfs/ > > Now break the mdraid. Put one of them on a shelf, it can still be used > in degraded mode as an archive. I like using these kinds of broken > raid1 members as long term archives because you really don't want to > write to degraded raids anyway, so there's an added incentive to just > treat it as a read-only archive. > > And the other one: > > btrfs device add /dev/sdXY /mnt/btrfs > btrfs balance start -dconvert=raid1 -mconvert=raid1 /mnt/btrfs Thanks. Still haven't done this but here's a follow-up question: My current backup tool is BorgBackup, which does compression and deduplication but took some effort to set up correctly, though it's working now. However it seems that Btrfs can do both these things, so is there a case to be made for just setting it up that way, and using send and receive for the actual copying instead of Borg? It would have the advantage of making the backed-up files a little more accessible without special tools. 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
cassert
Hello, Trying to compile (gcc) by including oct.h I get: #include I get: /usr/include/octave-5.2.0/octave/Array.h:30:10: fatal error: cassert: No such file or directory 30 | #include I installed octave-devel Where can I find the package cassert ? Thanks. === Patrick DUPRÉ | | email: pdu...@gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988 === ___ 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
> Strictly speaking, if the checksum fails you should not let anything > install it. It could be just a stuff-up, it could be malicious. When the deltarpm rebuild fails, dnf automatically downloads the full rpm. It's not a security issue, just a waste of bandwidth. ___ 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, 2020-12-30 at 07:08 +, Andre Robatino wrote: > In the last few days, I've noticed that F33 deltarpm rebuilds often > fail with an md5 mismatch error. Strictly speaking, if the checksum fails you should not let anything install it. It could be just a stuff-up, it could be malicious. -- uname -rsvp Linux 3.10.0-1160.11.1.el7.x86_64 #1 SMP Fri Dec 18 16:34:56 UTC 2020 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ 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
Jonathan Dieter posted a bug report for this at https://bugzilla.redhat.com/show_bug.cgi?id=1911828 , I'm relieved that it's not a hardware problem on my machine. Don't know why no one else notices it, although the deltas that fail are usually very small and don't waste much bandwidth. ___ 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
Hi. On Fri, 01 Jan 2021 11:48:21 +0800 Ed Greshko wrote: > On 01/01/2021 10:44, Tim via users wrote: >> francis.montag...@inria.fr: Using autofs instead of systemd-automount would have the advantage to unmount automatically after some delay. >> Ed Greshko: >>> Not true. >> When did that change? That's how it's behaved for me, for many years. > I have no idea of the history. ... Looking at /usr/share/doc/systemd/NEWS: CHANGES WITH 220: ... * The auto-mounter logic gained support for mount point expiry, using a new TimeoutIdleSec= setting in .automount units. (Also available as x-systemd.idle-timeout= in /etc/fstab). ... — Berlin, 2015-05-22 That was thus probably available in F22. > Either way, I could see how someone not having read the man page since > F17 may be unaware of those options. :-) :-) Yes :-) The same apply also for "standard" stuff. For example re-reading the man of mount one finds: Listing the mounts The listing mode is maintained for backward compatibility only. For more robust and customizable output use findmnt(8), -- 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
