Fedora, an example of giant tech compromise...

  • DNS Benchmark v2 is Finished and Available!
    Guest:
    That's right. It took an entire year, but the result far more accurate and feature laden than we originally planned. The world now has a universal, multi-protocol, super-accurate, DNS resolver performance-measuring tool. This major second version is not free. But the deal is, purchase it once for $9.95 and you own it — and it's entire future — without ever being asked to pay anything more. For an overview list of features and more, please see The DNS Benchmark page at GRC. If you decide to make it your own, thanks in advance. It's a piece of work I'm proud to offer for sale. And if you should have any questions, many of the people who have been using and testing it throughout the past year often hang out here.
    /Steve.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

Fedora is not a server version of the OS and also is not intended for mainstream use... it's designed to be the OS where they try new things that will eventually get rolled into the pay to play RHEL. I'm fairly certain the core isolation technologies are not going to be hobbled on a server platform.
 
Fedora is not a server version of the OS and also is not intended for mainstream use... it's designed to be the OS where they try new things that will eventually get rolled into the pay to play RHEL. I'm fairly certain the core isolation technologies are not going to be hobbled on a server platform.
At issue is NOT Fedora, but Systemd, your certainty maybe wrongly misplaced. Watch the video....
 
Then perhaps you should have chosen your thread subject more carefully?


Again, thread title should reflect content.


I did. It was mostly some nobody trying to get hype.
Flattering, but enough about my poor writing skills and the content creator's possible motivations, would you care to provide your technical expertise and enlighten us about what might have been exaggerated in his analysis of Systemd 257 and our current Linux distributions as suggested in the video? That was my interest in posting the information here on GRC.
 
Last edited:
He's looking for hype because he says every little thing he claims to find is "impact: critical". I don't see where he had anything negative to say about SystemD other than if the system faults and some logs COULD be lost. While that's not good, it certainly isn't likely "critical" in any way. As for the fact that SystemD does too much... this is a common complaint, and I don't care to get involved in this particular flame war. It's how it is, and it's mostly working, and there will always be someone who thinks it should have been done another way.
 
  • Like
Reactions: cschuber
He's looking for hype because he says every little thing he claims to find is "impact: critical". I don't see where he had anything negative to say about SystemD other than if the system faults and some logs COULD be lost. While that's not good, it certainly isn't likely "critical" in any way. As for the fact that SystemD does too much... this is a common complaint, and I don't care to get involved in this particular flame war. It's how it is, and it's mostly working, and there will always be someone who thinks it should have been done another way.
Hype? May I ask; do you use Linux, and with what and how do you audit your system(s)?
Critical? Yeah, I know a part mentioned in the beginning of the video was serious enough that Steve created a tool to help identify the issue. Sounds to me serious!
https://www.grc.com/inspectre.htm
 
He's looking for hype because he says every little thing he claims to find is "impact: critical". I don't see where he had anything negative to say about SystemD other than if the system faults and some logs COULD be lost. While that's not good, it certainly isn't likely "critical" in any way. As for the fact that SystemD does too much... this is a common complaint, and I don't care to get involved in this particular flame war. It's how it is, and it's mostly working, and there will always be someone who thinks it should have been done another way.
Agreed.
 
do you use Linux
I have plenty of OS experience, thanks. I've been using UNIX (not Linux) since we cared whether or not someone was on AT&T versus BSD. (The late 80's.)

To be fair, I do not currently run Linux on anything I consider publicly exposed or system critical, but I have in the past. If I wanted to audit any system, I would probably be doing so against the STIGs.