Moderators: kirk, jamesbond, p310don, JakeSFR, step, Forum moderators
Hi! I used Porteus 5.0 for some time. The kernel used in it, with some adjustments, is compatible with FatDog64. If someone like me, eager for updates, bored with "staying at home" wants to test ... I have a frugal second installation of FatDog64 just for testing "news", advise everyone to do too.
You can download it from: It is no longer available!
Is it necessary for single user desktop systems, and/or running a AMD system? I've read ...
that could allow an unprivileged local attacker to bypass conventional system security controls to cause system wide denial-of-service condition. This specific flaw is only known to affect Intel-based processors.
The Multihit iTLB errata can be exploited by a malicious guest running on a virtualized system, performing a denial of service attack, causing an unrecoverable blocking of the CPU (most Intel Core and Xeon processors).
This does not affect systems where there is no virtualization in use.
Another useful parameter in the kernel line is to add "lockdown = confidentiality", improving the security of Linux, more suitable for systems used in companies. But, nothing prevents us from using it!
I believe that all measures that reinforce security, and that do not significantly affect the performance of the system, at the discretion of each user, can be taken!
Other simple measures like: Surfing the net with the updated browser, adblock enabled, unmount drives, checking downloaded files with antivirus ... Each one protects himself as he can! I don't use savefiles! After each system startup, my previously customized browser installs as if it were your first time.
All my main programs are ROXapps. The base (fd64.sfs - 212Mb), I get through the fatdog-iso-builder, with the edited sfs-baselist where I remove: gimp-2.8.22-x86_64-1; libreoffice-6.2.8.1-x86_64-1; libreoffice-dict-en-6.2.8.1-x86_64-1; seamonkey-2.49.5-x86_64-1; flash-plugin-32.0.0.156-x86_64-1.txz; vlc-plugin-2.0.6-x86_64-1_vlc303.txz; armagetronad-0.2.8.3.4-x86_64-1; pipepanic-0.1.3-x86_64-1; xinvaders3d-1.3.6-x86_64-1; gtktetris-0.6.2b-x86_64-1; and sven-2020.08-x86_64-1
And I include packages, necessary for the operation of web browsers (Firefox, Vivaldi, Google Chrome, Opera):
gtk3-3.22.30-x86_64-1; at-spi2-core-2.28.0-x86_64-1; at-spi2-atk-2.26.2-x86_64-1; glib-networking-2.56.1-x86_64-1; gsettings-desktop-schemas-3.28.0-x86_64-1; libsoup-2.62.3-x86_64-1; librest-0.8.1-x86_64-1; and libnotify-gtk3-0.7.8-x86_64-1.
My personal settings are loaded into an extrasfs (sv64.sfs - 5.6Mb).
We can compile Clamav with the binaries downloaded directly from the source, download the microcode directly from the source, download the browsers and libreoffice directly from the official sources and adapt them to FatDog64.
I have a goal that I still don't know how to achieve it. One day I want to be able to compile my kernel straight from the official source (Kernel.org).
I am sure that the fastest way to achieve this goal is to remain a FatDog64 user and try to learn and progress from this point.
In addition, I want to see FatDog64 working like this!
"The simple things are the things that work ..."