Keeping Arch-ified Manjaro installation in place

Hi,

I’m still very new to EOS, in fact I have only just discovered it an hour ago…after a lengthy absence from Manjaro forum I’m not really up to date and have to read a lot.
As some of you know, I do have some experience with both Arch and Manjaro.

On my laptop installation, I’ve already started a couple months ago to Arch-ify the system.
This includes e.g. systemd and custom kernels.

Since this installation doesn’t contain much personal data or otherwise important files, I’m thinking of converting it to EOS by following @jonathon’s guide on Manjaro forum.

Now, my question is: can I keep my customised packages?
For example, the systemd I use is almost 100% identical with Arch’s, the kernels are built in a “mixed” Arch-Manjaro way, so I think they shouldn’t cause a major problem.
Maybe some of you already have experience with the Manjaro->EOS switch.

I’ll continue reading through the forum to get used to the EOS processes, but for now, consider me a noob :slight_smile:

1 Like

You know what, I’ll just do it.
It seems that Manjaro-Arch-EOS are sufficiently close atm.
I’ll report back.

1 Like

There’s only one way to find out! :upside_down_face:
I predict it should be ok, although custom systemd sounds a little hardcore :laughing: Maybe this 0.00001%… :thinking:

be careful with systemd ,
keep always good version 245.x

there is a 246 rc , and changes about networkd is a cathedral like pottering …

also check this topic as you compile all stuff

Thanks. I’m already using 245.6 from Arch with minor mods.

I’m rebooting now, wish me luck :wink:

3 Likes

I’d say it’s worth a try (for science!), and if it fails, you can always nuke it and reinstall EOS fresh.

5 Likes

My, that was easy.

Everything went fine, I can even continue using my custom kernel, systemd, mesa, vbox etc.

Now time for some cleanups and a few changes to GRUB!

6 Likes

One thing that seems to be missing is the /etc/release file.
Doesn’t EOS come with one or did I miss a package?

Nope, it does not exist on the regular EOS install either.

Ah ok, there’s however another one called /etc/lsb-release from Arch.

Exactly. On a fresh EOS install it contains:

LSB_VERSION=1.4
DISTRIB_ID=EndeavourOS
DISTRIB_RELEASE=rolling
DISTRIB_DESCRIPTION="EndeavourOS Linux"
2 Likes

vs Arch’s:

LSB_VERSION=1.4
DISTRIB_ID=Arch
DISTRIB_RELEASE=rolling
DISTRIB_DESCRIPTION="Arch Linux"
3 Likes

in the endeavouros repo you find eos-hooks , by installing that you keep the lsb_release after update of lsrelease package… :slight_smile:

but is just what you want offcourse…

7 Likes

Thanks @ all.
eos-hooks was missing.

EDIT: marking as solved.

2 Likes