Re: Fedora vs. Meltdown & Spectre

On Fri, 5 Jan 2018, François Patte wrote: I could not see any kernel update yesterday or today! (f-25) And you won't for Fedora 25 which reached its end of life on 12th December 2017, so there won't be any more updates. I suggest you update to a later version of Fedora. Michael

Re: Fedora vs. Meltdown & Spectre

Le 04/01/2018 à 18:01, Matthew Miller a écrit : > On Thu, Jan 04, 2018 at 05:49:15AM -0800, Jonathan Ryshpan wrote: >> What do people know about Fedora vs. the Meltdown and Spectre bugs? > > Mitigation for Meltdown is in place in the kernel updates we released > yesterday. I could not see any

Fedora 27, slow sata hdd access

So fully updated F27, using Plasma I have a 2TB Seagate drive as a secondary storage device off a normal sata port. Accessing the disk via kdialog, Dolphin and Nautilus is slooow. Can take anywhere from 5 to 15 seconds to screens to update. Drive is perfectly normal under Win10. What could be the

Re: Fedora vs. Meltdown & Spectre

On Fri, Jan 05, 2018 at 04:07:19PM -0800, Rick Stevens wrote: > Yes, and for reference the current release is Fedora 27. Jumping > straight to F27 might be risky, so I'd do it in four steps: Note that we _do_ test "n-2" upgrades like this now, so F25 to F27 _should_ work. The transaction test

Re: how to recover from a failed system-upgrade

Eyal Lebedinsky writes: What is the correct way to complete the upgrade? (I kept an image of the failure). Unfortunately, there is no cookie-cutter, paint by numbers, recipe for recovering from this kind of a botch. Chances are good that this situation is salvageable, especially since

Re: Fedora vs. Meltdown & Spectre

On 01/05/2018 02:53 PM, Michael Young wrote: > On Fri, 5 Jan 2018, François Patte wrote: > >> I could not see any kernel update yesterday or today! (f-25) > > And you won't for Fedora 25 which reached its end of life on 12th > December 2017, so there won't be any more updates. I suggest you

how to recover from a failed system-upgrade

First: this is an upgrade of a USB system and I have an image of f26 before the upgrade to f27 and I will redo it in full. So no disaster, yet I want to understand how the upgrade process recovers from such a failure (if at all). I followed the usual process # dnf update (and such)

Re: Fedora 27, slow sata hdd access

On 01/06/18 12:14, InvalidPath wrote: > So fully updated F27, using Plasma I have a 2TB Seagate drive as a secondary > storage device off a normal sata port. Accessing the disk via kdialog, > Dolphin and > Nautilus is slooow. Can take anywhere from 5 to 15 seconds to screens to > update. > Drive

Re: Data backup- (udev problem)

Hi Samuel, if I use fstab to *mount permanently* some partitions that I made on a USB Hard Disk, *THEN, every time* I use the "find" command, I get (from nautilus) requests to open (show) these partitions. And this is not only an (very much) annoying problem.. In that eventuality I also begin

Re: Data backup- (udev problem)

*other lines of journalctl that report errors * Jan 01 12:38:12 localhost.pluto org.gtk.Private.UDisks2VolumeMonitor[2153]: index_parse.c:191: indx_parse(): *error* opening /run/media/angelo_dev/PRTZ_programming/BDMV/BACKUP/index.bdmv Jan 01 13:00:02 localhost.pluto ntfs-3g[7860]: Unmounting

Re: Data backup- (udev problem)

On 01/05/2018 12:37 AM, Samuel Sieb wrote: On 01/05/2018 12:13 AM, Angelo Moreschini wrote: Nov 12 11:02:54 localhost.pluto ntfs-3g[691]: Mounted /dev/sdb2 (Read-Write, label "PRTZ_programming", NTFS 3.1) Nov 12 19:59:58 localhost.pluto ntfs-3g[691]: Unmounting /dev/sdb2 (PRTZ_programming) I

Re: mounting a USB HD with autofs

Allegedly, on or about 4 January 2018, Angelo Moreschini sent: > To use autofs for the automatic mounting of partitions existing on > USB HD (that is permanently connected to the computer), it is also > mandatory to install NFS ? I can't see why you'd need to. If something is trying to install

Re: Data backup- (udev problem)

On 01/05/2018 12:13 AM, Angelo Moreschini wrote: _here some line of command_ : _sudo journalctl  | grep -i PRTZ_programming_*(PRTZ_programming = name of partition I made on USB HD)** * Nov 12 09:29:50 localhost.pluto gnome-session[1798]: Gjs-Message: JS LOG: Unable to mount volume

Re: Fedora vs. Meltdown & Spectre

On Thu, 2018-01-04 at 17:58 -0600, Michael Cronenworth wrote: > On 01/04/2018 05:32 PM, Patrick O'Callaghan wrote: > > Browsing a malicious website that runs Javascript can be a problem. > > Site isolation is a mitigation technique that provides partial > > protection. Hints for Chrome can be

Re: Device or resource busy when trying to do a software update

On Thu, 04 Jan 2018 21:09:05 +0100 Martin Wagner wrote: > On Thu, 2018-01-04 at 13:06 +0100, Wolfgang Pfeiffer wrote: > > Ah, I see: I missed that in your first message - sorry. But if dnf > > upgrades work, your concerns about not being not be able to upgrade > > to >

[389-users] Re: [important] Removing i686 support

On 04 Jan 2018, at 2:09 AM, William Brown wrote: > We have begun the process to remove i686 support from the server. You > should plan that all 1.4.x builds will support 64bit platforms only. > > https://pagure.io/389-ds-base/issue/49514 > > We recommend that you move to a