Unfortunately, no one can be told what Redcore Linux is. You have to see it for yourself!
You are not logged in.
Use a different mirror. You're likely using Princeton, which has been outdated since 19.03.2024. Yandex and Alpix mirrors are up-to-date. Use one of them and you will receive the update in binary form.
And when it comes to the profile switch, ignore the message. You don't have to do anything. The profile switch will happen by the end of June on Redcore's servers and come as an update. I will post about the profile change on the website like I posted a few years back when we switched from profile 13.0 to profile 17.0.
Perhaps you didn't use the correct profile. In Redcore Linux the default profile is :
default/linux/amd64/17.1/hardened
which has a minimal set of predefined USE flags, hence why /etc/portage is so extensively populated by us. It allows a "fine tuning".
Some other profiles like may enforce some USE flags such as:
default/linux/amd64/17.1/desktop/plasma/systemd/merged-usr
which will enforce systemd and plasma related USE flags
Systemd and related USE flags are masked in Redcore Linux for example. So if you want to Redcore-ify Gentoo, you need to start small and build your way up. Hence why my initial suggestion of just removing Sisyphus is a simpler approach.
A complete list of profiles can be obtained using :
eselect profile list
rc-update del apparmor boot
Followed by a reboot will disable it. However a better approach will be to fine tune it to your preferences.
For example :
aa-status
will return something like this:
apparmor module is loaded.
60 profiles are loaded.
60 profiles are in enforce mode.
/usr/bin/akonadiserver
/usr/lib/apache2/mpm-prefork/apache2
/usr/lib/apache2/mpm-prefork/apache2//DEFAULT_URI
/usr/lib/apache2/mpm-prefork/apache2//HANDLING_UNTRUSTED_INPUT
/usr/lib/apache2/mpm-prefork/apache2//phpsysinfo
apache2
apache2//DEFAULT_URI
apache2//HANDLING_UNTRUSTED_INPUT
apache2//phpsysinfo
avahi-daemon
dnsmasq
dnsmasq//libvirt_leaseshelper
dovecot
dovecot-anvil
dovecot-auth
dovecot-config
dovecot-deliver
dovecot-dict
dovecot-director
dovecot-doveadm-server
dovecot-dovecot-auth
dovecot-dovecot-lda
dovecot-dovecot-lda//sendmail
dovecot-imap
dovecot-imap-login
dovecot-lmtp
dovecot-log
dovecot-managesieve
dovecot-managesieve-login
dovecot-pop3
dovecot-pop3-login
dovecot-replicator
dovecot-script-login
dovecot-ssl-params
dovecot-stats
identd
klogd
lsb_release
mariadbd_akonadi
mdnsd
mysqld_akonadi
nscd
ntpd
nvidia_modprobe
nvidia_modprobe//kmod
php-fpm
ping
postgresql_akonadi
samba-bgqd
samba-dcerpcd
samba-rpcd
samba-rpcd-classic
samba-rpcd-spoolss
smbldap-useradd
smbldap-useradd///etc/init.d/nscd
syslogd
traceroute
zgrep
zgrep//helper
zgrep//sed
0 profiles are in complain mode.
0 profiles are in kill mode.
0 profiles are in unconfined mode.
2 processes have profiles defined.
2 processes are in enforce mode.
/usr/sbin/avahi-daemon (4418) avahi-daemon
/usr/sbin/avahi-daemon (4419) avahi-daemon
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.
0 processes are in mixed mode.
0 processes are in kill mode.
Then you can disable a certain program or profile like this :
aa-disable syslogd
Apparmor is almost unnoticeable at runtime and proactively protects the operating system and applications from external or internal threats, even zero-day attacks, by enforcing good behavior and preventing both known and unknown application flaws from being exploited. It is up to you if you're willing to take the risks or not.
Yes, that's how it's supposed to work. Install, reboot and done. Glad it is solved.
P.S. When the kernel gets updated, you just need to reboot, and dkms will recompile the modules for the new kernel.
It will work, but it may take a long time to recompile everything affected by the USE changes. It's just easier to install Redcore, remove sisyphus and use the system as you would use Gentoo. Redcore is basically Gentoo with binary packages, and sisyphus to deal with those binary packages. But you can absolutely remove sisyphus and use emerge.
P.S.: I would recommend you use zfs with an LTS kernel.
sisyphus install linux-image-redcore-lts:6.1
for kernel 6.1.xx
or
sisyphus install linux-image-redcore-lts:6.6
for kernel 6.6.xx
or
sisyphus install linux-image-redcore-lts:5.15
for kernel 5.15.xx
sisyphus install zfs
Will pull everything needed for zfs to work, including zfs-dkms. zfs-kmod is a Gentoo ebuild, and not recommended or compatible with Redcore. zfs-dkms on the other hand works with Redcore kernels. After install, you will need to reboot, and dkms will build the kernel modules.
If you encounter an error, please let me know.
You likely need to install GIMP as a flatpak as well. Flatpaks are sandboxed, so they don't interact with the rest of the system. If that works, you can uninstall the native GIMP package.
Well, when I designed sisyphus, I considered someone might want to override some defaults. In fact, I was hoping someone will eventually ask me this question. So, you don't really need to branch out. Sisyphus has a mechanism to override the defaults. Not everything in your list is possible, but 3 out of 4 are.
1. Edit /etc/portage/env/10-sisyphus-overrides and add the following lines :
CFLAGS="-O2 -march=native -mtune=generic -pipe -fno-delete-null-pointer-checks -Wno-deprecated -Wno-deprecated-declarations -fno-plt -fstack-protector-strong -fstack-clash-protection -fcf-protection=full"
CXXFLAGS="-O2 -march=native -mtune=generic -pipe -fno-delete-null-pointer-checks -Wno-deprecated -Wno-deprecated-declarations -fno-plt -fstack-protector-strong -fstack-clash-protection -fcf-protection=full"
Feel free to edit these flags however you please. The only change from Redcore's default is -march=native instead of -march=x86-64
Then, let's say you want to compile GCC with -march=native :
Edit /etc/portage/package.env/10-sisyphus-overrides and add the following line :
sys-devel/gcc 10-sisyphus-overrides
For every package you want to compile with -march=native you add another line :
category/name 10-sisyphus-overrides
2. Edit /etc/portage/package.use/10-sisyphus-overrides and add the following line :
sys-devel/gcc graphite
For every package you want to change an USE flag you add another line:
category/name USE
to enable an USE flag or
category/name -USE
to disable it
3. https://bugs.gentoo.org/715612 , this one is a work in progress, once it shows up in Gentoo's tree, you can follow the steps I described at number 2 to enable it.
4. Follow the steps at number 2 and add the following line:
app-alternatives/bzip2 -reference lbzip2
This will change the bzip2 implementation from reference (default implementation) to https://github.com/kjn/lbzip2/
or
app-alternatives/bzip2 -reference pbzip2
This will change the bzip2 implementation from reference (default implementation) to https://launchpad.net/pbzip2
Once done, the changes are permanent and sisyphus will NOT use binaries for the packages altered this way. All you have to do is run
sisyphus upgrade --ebuild
and you will notice it will offer to recompile the altered packages with your settings. If anything goes wrong, just remove the alterations and re-run
sisyphus upgrade --ebuild
Sisyphus has a fallback mechanism, so the --ebuild flag becomes automatically redundant and will use binaries if alterations are removed.
P.S.: There is no global override, changes are possible only per-package basis. Recompiling the whole system with -march=native is possible using a global override, but it is not implemented yet.
This has been meanwhile sorted. Closing!
gpasswd -a your_username deluge
Followed by a logout-login cycle *should* sort it.
emerge -NuDGav --backtrack=100 --with-bdeps=y @world
This will succeed.
I don't expect any impact on Redcore Linux.
I am happy they provide binary packages. If they did this 10 years ago, Redcore Linux wouldn't have existed, probably. For the past 10 years, we've been producing our binaries in the same way as they do in their shiny new repository.
I started Redcore Linux to make Gentoo Linux more accessible. I like to think that maybe Redcore Linux somehow influenced Gentoo Linux's decision to provide binary packages, finally.
That being said, Sisyphus will NOT be using their binary packages. Their's use the newer package format, while we use the older package format. They can use ours, thanks to backwards compatibility, we cannot use theirs, for the time being.
A migration to the newer package format is in the cards for Redcore Linux, but it will be some months away, as everything will have to be rebuilt. Not a major issue, we tend to rebuild every single package once a year anyway, the next mass rebuild will probably come with a format change as well.
The format change will potentially make the binaries of both distros interchangeable, however, at least for the time being, Gentoo Linux doesn't seem to provide binaries for the testing branch, on which Redcore Linux is based. Which means, that even with identical package formats, Redcore Linux will carry on using its own binary packages, aka business as usual.
http://mirrors.redcorelinux.org/redcore … /iso-next/
if you want to reinstall, use this BETA iso, you will avoid a very lengthy update, and no fixes are required. you just need to upgrade the system post-install, without those extra steps.
I updated the wiki before actually merging the packages. I merged them now. Try in a couple of hours so they have time to sync to the mirrors and it should work. If not, let me know.
I created a user for you on wiki, you will have the details via e-mail. Welcome to the club.
You need to follow those steps exactly and it should work.
If you reinstall, you must follow the same steps. I will release a new ISO image soon so is not required, but until then those steps are valid.
No worries, if you keep having issues, let me know.
No, it's not broken. You need to follow the instructions I posted on the website. https://redcorelinux.org/news/system-up … n-required
You can safely ignore the error you posted, and follow the next steps.
That means the system is not fully upgraded, and your latest attempt failed somehow. Try this :
emerge --sync
cd /opt/redcore-build
git fetch --unshallow
git fetch --all
git reset --hard 5361e6b8970e53046955ac5071d9122990cf77ec
emerge -va1 sisyphus sisyphus-qt
sisyphus branch master
sisyphus rescue
sisyphus upgrade
This should work. If you have issues, please let me know.
I have installed Redcore Linux on a 25 Gb partition. It seems to take up 20 GB despite my home folder being only 1.4 Gb. Why should it take up so much space and is there a way to clean up the system?
There is no bloat inside. The reason it takes so much space is we don't split packages. For example, Ubuntu will split Mesa into 10 packages or more, and generally, they don't install development headers by default. We don't do this splitting, if you install mesa in Redcore, you will install a full package as it came from upstream, not just bits and pieces based on arbitrary reasons.
If you do development on an Ubuntu system, you will find out that you need to install a significant amount of packages which contain development headers, depending on your requirements and the space occupied will come close to Redcore. On Redcore you have everything ready from the get-go.
Hello,
I think, you can disable the vmware-tools service with:
rc-update del vmware-tools default
Fred
Yes, this is the correct solution.
How do one acquire Redcore installer to install Redcore with DE else ?
The only ISO image we ship is KDE Plasma. There is and there won't be any XFCE ISO image, unless someone is willing to build it. I am willing to build the XFCE packages required and push them to the repos, but I don't have the time to build the ISO image. If someone is willing to step in, I'm more than happy to provide guidance.
GRUB_THEME="/usr/share/grub/themes/redcore/theme.txt"
Comment the above line in /etc/default/grub and run :
grub2-mkconfig -o /boot/grub/grub.cfg