the content of conversation was going off related to main discussion.
Let’s talk here of your tests about system updates
Lets pick up from @Halano post:
I had almost 300-400mb of updates per day! That’s not acceptable.
Why ? I use arch ,& I do update the whole system every two months
and linux kernel every 3 months
IgnorePkg = linux linux-headers linux-lts linux-lts-headers linux-firmware python gimpUpdating the whole system everyday isn’t good idea, even if you’re on rolling release distro
I update my Arch every day and have no problems 
@Halano
is ok using LTS kernel or ignore kernel updates, the system have less probability to broke so often if no upgrading so frequent the kernel. But sadly there’s not only linux image and linux headers updating, I remember on Arch I daily had different upgrades not only the kernel… I remember alot of system libraries.
It’s great for you and many other users Arch daily usage, for my use case I preferred to switch to something more stable. There’s nothing personal, just personal preferences. In the end Linux is the same, no? 
I ran Arch for about 2 years also. But after a few untimely issue that I had to troubleshoot I realized it wasn’t for me. At least not on my workstations.
Even with the LTS kernel, the issue for me was that occasionally during the updates something breaks and while it’s almost always solvable I’m not interested in solving issues OS issues on my work computer.
Yes I can understand, for example last months when I was in this situation I was not liking the quantity of daily updates, and to be honest, system got broken one time: I was not able to use my computer, at least desktop environment, for almost 2 - 3 hours because mantainers delayed some system core update. (Yes, I was upgrading the system daily…)
I honestly don’t have any responsabilities about keeping a server up, but if I’m going on this situation I’ll 100% go with Debian stable.
Also at home I would like to go with Debian, but I find Debian more server - production system rather then a house primary OS.
Here’s an overview of the rolling distro options:
Last week I tested Siduction - Debian Rolling Release.
Typical for Debian, however, it does not suit me.
Terminal - pacman -Syu and oops, I forgot that I have to use apt instead of pacman 
But I have to admit that I like nala very much as a replacement for apt.
I am still waiting for that unrecoverable breakdown in Arch.
The biggest breakdown I had is an attempt to upgrade the kernel in Manjaro. Upon restarting no juice. So I followed a guide. Booted with an Arch USB. Chroot into Manjaro, changed the kernel, repaired the boot drive and voila was up and running again.
For opensuse tumbleweed, I love it but have a hard time finding wiki’s to configure it. So I have always reverted to Arch. My last attempt, I gave up because I couldn’t get to configure the firewall.
Forgive me for being nieve. But when I look at Debian testing and Debian unstable, the names alone give me a pause.
Even Siduction gives you a warning. And that was one thing why I ran from Kali too, the warning on the webpage.
Arch and Opensuse tumbleweed seems to be the opposite, so inviting.
Could be me?
If it’s a daily driver, it will come. It’s not like you just reinstall in 5 mins and return to normal.
Arguably, Arch should probably come with more of a warning than Debian Testing, to be honest. Which it actually does in the wiki i think, it mentions that it’s up to the user to avoid breaking the system and/or avoiding major issues. Which is true. If you read the news posted prior to updating, you can usually avoid or be prepared for such moments.
If I was forced to run Arch again, I would go with Manjaro acting like a buffer between straight Arch.
They should, especially SID, it’s just like Fedora Rawhide, both of these should be avoided except for special use cases like Linux software devs. But Debian Testing makes for a perfect base for many distros.
Here’s a few that pulls from deb testing:
As for Kali, it’s as they say… old stigmas don’t die young:
I would argue that due to the Kali tweaks tool included, switching to the kali-last-snapshot branch, and the documentation, that Kali is one of the most stable of the rolling release distros. The pentest tools are not installed unless you leave the box checked during the installation wizard. Beyond that Kali is generic Debian with extra oversight/testing by Kali devs for a rolling release.
openSUSE Slowroll also looks extremely promising.
@hydn @toadie
Waaa I did not know about these kind of Debian sid rolling distributions such as Sparkly or Siduction, you guys just opened to me a world.
It might be interesting trying them, I’m going to give them a chance in a virtual machine, then I’ll tell you what are my thoughts about.
Very pleasant to be in here, everyday I can learn something new and interesting.
Just to be clear for others who read this thread.
There’s:
but there’s also:
Hi guys,
I had the opportunity to test the 2 Debian rolling distribution, Siduction and Sparky, here’s my thoughts about.
Siduction: Pretty bleeding edge Debian distribution, it’s using Debian experimental kernel repository and many fresh software. It tent to broke. I downloaded and used XFCE flavour, and Siduction it’s using last XFCE release, the 4.20. The problem is at the date I’m typing this message this release is a bit buggy, specifically on dual screen setup, background wallpaper, icons and right click on desktop were not working. I googled a bit and I discoverd only recent XFCE team fixed that bug, but still not implemented in Siduction. So after install when I got broken desktop I tried to download whole XFCE from official github release and tried to install on system. After fixing some packages dependencies I was able to install the Desktop, after that it was working a better I was seeing wallpaper and right click was working, but it was still a bit buggy.
Sparky: This distribution is more “stable” then Siduction, it’s using safer packages and kernel versions. I tried also to install this distribution, in XFCE flavour as well, everything seems ok but then I tried to download and install Nvidia driver. After installed the drivers system boot up in a rescue terminal, seems something broken with lightdm. At the date I’m typing it seems Debian testing is having broken Nvidia packages, it’s the second time in a week I found Debian testing Nvidia incompatibility.
So my final thought, for what I tried and learnt from this experience, is no using Debian testing nor Sid. Maybe I just was unlucky, maybe in a couple of weeks packages will be fixed. But I won’t use a Distribution that might be accidentaly broken in a while, it’s too risky for my workflow, where I often use my computer for remote work.
Thank you for that testing @ricky89. More reasons for me to stay with Arch.
What @ricky89 reported about Rolling releases gives you MORE confidence to run one of the most bleeding edge distros? 
@shybry747 I respect you for that!! 
About 4 or 5 years ago, I still had that faith.
OOn a serious note, I think Arch really helps us learn the inner workings of Linux better than probably any other distro (close would be Slackware and Gentoo).
They don’t get caught up with all the fancy atomic updates, or try to reinvent of replace stuff like their package manage pacman, or AUR or anything that they have spent the past 20 years building on.
That is part of what makes Arch Linux so great and unique! Much like Debian they have stuck to their roots. No matter how many years pass in between, you can always circle back to Arch and know what to expect. That in itself adds a level of stability.
Talking about it, I think I will move Arch ahead of Manjaro in that stability list. Manjaro is constantly changing, lol. At this point Manjaro should just consider becoming an independent distro. 
In my experience, Arch is somewhat more stable than Manjaro or other Arch distros.
Today I updated my laptop with Archcraft for the first time after 3 weeks!
Do you know what? No problems at all!
Early this year, I updated Arch with Budgie desktop. It went over 6 months without an update. First I had to update the keyring manually.
sudo pacman-key --refresh-keys
sudo pacman -Sy --needed archlinux-keyring
Then I did the full upgrade, rebooted and like @toadie no problems at all.
These days on my daily home driver, I do an Arch update once every 1 to 2 months. And no problems yet.
Exactly my experience @shybry747. Arch runs and runs and runs
@shybry747 I guess you had almost 25-30 gb of updates lol … I won’t never keep an Arch installation without updates for 6 months… I think that’s is insane
Maybe we should do a test, a VM with Arch (e.g. Manjaro) and see how many updates there are after half a year.
In my case of the 3 weeks it was ~1300MB that had to be downloaded.
