Endeavour OS ISOs Updated With Better Btrfs Support, Pacman Parallel Downloads

[phoronix]

Phoronix: Endeavour OS ISOs Updated With Better Btrfs Support, Pacman Parallel Downloads

For those after an easy-to-use desktop distribution built off Arch Linux, Endeavour OS continues filling the void left by the former Antergos project. Endeavour OS is closing out August by releasing new ISOs that include a number of updates to its installer...

https://www.phoronix.com/scan.php?page=news_item&px=Endeavour-OS-Better-Btrfs

[Quackdoc]

I used endeavor OS for about a month and a half, constantly borked AUR some how, and blacklists broadcom drivers by default for some asinine reason. well not as bad as reborn OS that would blacklist them on every single fucking updated. but still annoying.

[skeevy420]

I used endeavor OS for about a month and a half, constantly borked AUR some how, and blacklists broadcom drivers by default for some asinine reason. well not as bad as reborn OS that would blacklist them on every single fucking updated. but still annoying.

I'm not trying to be overly negative, but that's sort of to be expected if you use any of their* programs. Manjaro now and Antergors back in the day have that same issue in regards to the AUR. When you do an update you have to hope that they* rebuilt their packages the second that Arch updated their packages else you can start having dependency issues which can lead to oddball AUR and Pacman issues. They also tend to add in quality of life and helper scripts/Pacman hooks which may help some and do things for asinine reasons to others.

In 8/9 years of using Arch and Arch-based, that's pretty much the experience that I've had most every time I've strayed from plain Arch ((and installed (lots of) packages from the AUR)). For me it seemed to be worse the more often I updated; when using automatic scheduled update syncing like Manjaro/Pamac does by default...because I'd see that sys tray green ghost become red which would trigger my OCD enough to have to run an update.

*their/they meaning most anything Arch-based; not specifically EOS

[evasb]

I don't know why these arch-based distros maintainers still try to change Arch to somewhat "stabilize" their distro.

For me, plain arch is stable enough.

With the lack of a good Arch-based distro (Manjaro is atrocious and confusing) I resort to recommend Ubuntu LTS+Kisak Mesa PPA or PopOS for beginners.

[Quackdoc]

I'm not trying to be overly negative, but that's sort of to be expected if you use any of their* programs. Manjaro now and Antergors back in the day have that same issue in regards to the AUR. When you do an update you have to hope that they* rebuilt their packages the second that Arch updated their packages else you can start having dependency issues which can lead to oddball AUR and Pacman issues. They also tend to add in quality of life and helper scripts/Pacman hooks which may help some and do things for asinine reasons to others.

In 8/9 years of using Arch and Arch-based, that's pretty much the experience that I've had most every time I've strayed from plain Arch ((and installed (lots of) packages from the AUR)). For me it seemed to be worse the more often I updated; when using automatic scheduled update syncing like Manjaro/Pamac does by default...because I'd see that sys tray green ghost become red which would trigger my OCD enough to have to run an update.

*their/they meaning most anything Arch-based; not specifically EOS

no no, I agree, anybody who uses anything but vanilla arch is setting themselves up for failure. Arch isn't even hard to install, people are just too lazy to do it.

[linner]

Instead of working on stuff like parallel downloads, somebody should try fixing pacman so that its operations are fully atomic. I can't count how many systems I've have that got completely trashed by a failed pacman upgrade. I don't know why but if you have a failure (eg. hardware) during pacman upgrade it can completely trash the ENTIRE system with corrupted files all over the place. With a lot of effort I've tried numerous times to recover from these but in the end always end up having to reinstall the OS fresh. It's one reason I stay far away from Arch for servers.

[polarathene]

I don't know why but if you have a failure (eg. hardware) during pacman upgrade it can completely trash the ENTIRE system with corrupted files all over the place.

I just ran into this recently with a family member on Manjaro. They weren't using anything from AUR either, they just performed an upgrade as per usual but it froze up on them (possibly kernel panic or OOM event), they waited a while and then opted to just power it off and try again... but the bootloader was corrupted when upgrading the kernel it seems.

I figured something like Manjaro in that situation wouldn't have been prone to such a problem, there was no way they'd have been able to restore their system by themselves and they were getting quite upset about it. Their system is fine now, but I'm tempted to move them off on to something else, perhaps Fedora?

They like KDE and mostly use a web browser and GIMP, they just care about getting security updates, I suggested Pop_OS but they want to stick to KDE for DE.

It's one reason I stay far away from Arch for servers.

I've been using openSUSE Leap, haven't had any problems with that over the years, but I would like something with newer kernels and packages, the SP point release updates are quite a bit apart.

I've heard good things about TW, but I'm not sure if that's a good idea for servers, openSUSE does offer a BTRFS feature for servers called transactional updates (atomic via read-only root snapshots switched to on boot IIRC)...might be worth trying?

[Paradigm Shifter]

The only "Arch based" distro I've never had AUR issues with (other than Arch itself) was Anarchy Linux, which is basically an install script with some options to install some customisations for a desktops if desired.

Although that has it's own quirks, like defaulting Ctrl-Alt-End in Cinnamon to "shutdown right now" rather than "give me the session manager menu".

edit: Also while I've certainly had issues with Arch at various times, it was usually when I had it on a laptop which for whatever reason hadn't seen the internet (and thus updates) for months or years. At which point it would break horribly.

[Mez']

no no, I agree, anybody who uses anything but vanilla arch is setting themselves up for failure. Arch isn't even hard to install, people are just too lazy to do it.

it's not laziness. It's time and interest. I don't see the point in preparing myself for hours and learn to install it in an outdated way when I can just install Manjaro the 2005+ way (GUI).

With the lack of a good Arch-based distro (Manjaro is atrocious and confusing) I resort to recommend Ubuntu LTS+Kisak Mesa PPA or PopOS for beginners.

I beg to differ. It's neither atrocious nor confusing. It's actually very clear and pretty nice. Between command line yay and pamac, you can do whatever you see fit depending on your time and willingness to get dirty (in the command line).
I've been using Manjaro for a year and a half on the initial install with AUR and unstable repositories, and it's always clear when you'll run into dependency issues, you can always abort and wait for it to be sorted out.
It feels like it would be very difficult to break your system (unless you try to break it intentionally).

Although Ubuntu is totally alright as well.

[Quackdoc]

it's not laziness. It's time and interest. I don't see the point in preparing myself for hours and learn to install it in an outdated way when I can just install Manjaro the 2005+ way (GUI).

if you have to spend hours learning how to install arch, you have a learning disability. its literally Ikea of distros now. before it was like a kit build, now its ikea. The instructions are well thought out, and the Easy guided install is as easy as any other distro, just text.

I beg to differ. It's neither atrocious nor confusing. It's actually very clear and pretty nice. Between command line yay and pamac, you can do whatever you see fit depending on your time and willingness to get dirty (in the command line).
I've been using Manjaro for a year and a half on the initial install with AUR and unstable repositories, and it's always clear when you'll run into dependency issues, you can always abort and wait for it to be sorted out.
It feels like it would be very difficult to break your system (unless you try to break it intentionally).

Although Ubuntu is totally alright as well.

Manjaro IS atrocious. It constantly, intentionally breaks support with aur. in fact it went so far as to duplicate grub, set a conflict with old grub, and grub-customizer, just so people couldn't install it from the AUR. I remember other situations, such as linux-vfio (though I doubt that was necessarily intentional) of aur breakages. so intentional, some not. at this point they should just run their own aur.