We've never had any problems - these or any of the others mentioned. We've used
XFS on single HDD and SSD physical workstations, but have since migrated those
to VMs, so they're on hardware RAID now, as are most of our systems - whether
VM or bare metal. Since we've not encountered a corrupt
Sorry. We don't actually run clusters. They get called that, but they're really
farms managed by LSF.
From: owner-scientific-linux-us...@listserv.fnal.gov
on behalf of Miles ONeal
<0be99a30c213-dmarc-requ...@listserv.fnal.gov>
Sent: Monday, December 4
Cirrus isn't a lab, but we run clusters, have over a thousand workstations, and
have many more infrastructure systems. We haven't used ext4 in a good while
except on a few legacy hosts. xfs has been fast and stable. I don't recall the
last time I saw fsck run, but it was before moving to xfs.
Yes, for better or worse, that's part of "binary compatible". If you need bugs
fixed faster than RedHat is fixing them, you need to fix them yourself, or get
someone else to. Sometimes you can find newer versions with fixes in other
public repos, but again, the onus is on you to provide the fix
I see these for Fedora (thank you). Are they available for EL7 or derivatives?
Nico said:
Oh, heck, that's why I publish RPMs for tvtwm.
The person doing test installs here of RHEL 8.3 wasn't any happier.
It feels like a lot of the Linux developers are all trying to beat Windows and
MacOS at their own games. Barf.
From: owner-scientific-linux-us...@listserv.fnal.gov
on behalf of Larry Linder
FKonstantin said:
...
| For me, the issues are not policital, but technical:
Agreed. One of mine is that the surety of being able to drop a lower runlevel
and back up is gone. I have always managed my systems the way I learned in the
early days (probably from
The concurrency argument was always absurd. It could easily gave been added to
SysVInit.
Get Outlook for
