Skip to main content ↑ ↓
Topic: [SOLVED] Problems after migration (Read 1252 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[SOLVED] Problems after migration

I have migrated using this guide: https://wiki.artixlinux.org/Main/Migration

1. The important one
elogind does not start sessions

Code: [Select]
~/ loginctl
No sessions.
█▓▒░qp@qptop█▓▒░ Sun Oct 27 12:12:17am 
~/

  • I have restarted after migration
  • elogind is running
  • dbus is running too
  • on livecd I have sessions so it's not hardware related

2. The not that important one
I get the message \\vmlinuz-linux is an invalid runlevel before starting the default runlevel

I don't know why it act's like there is such a runlevel, rc-status -a does not contain this runlevel.

The reason of having this error may be that /sbin/init runs with the \\vmlinuz-linux argument, and I don't know why.

Re: Problems after migration

Reply #1 –
The first one is solved by this

Code: [Select]
pacman -Sl system | grep installed | cut -d" " -f2  | sudo pacman -S -

Re: Problems after migration

Reply #3 –
Quote from: mrbrklyn – on
Doesn't that just reinstall all the system packages?

Did I miss something here?

It does exactly that.
The problem was that some programs did not want to cooperate and user stated that he had to reinstall some packages to make them work.
We took the bet (on IRC) and tried to see what would happen after reinstalling all system packages.

Plus there could be some broken pacman hooks or some other things which were solved with this.

But in other words, during the migration we need to purge all systemd infected packages (especially from system).
Maybe I am wrong here, but this is what I think.

Have a nice day.

EDIT:
Think about it this way:
During the update we ask user to change pacman.conf and to update pacmans database.
Which means that packages from [core] will be listed as either from system or from unknown source.
The command reinstalls packages which now (after the changes) shows up in system repository.
These packages are originally from [core], which means they might strongly depends on systemd stuff.
This action gets rid of them and replaces them with Artix packages.

Have a nice day.

Re: Problems after migration

Reply #4 –
Quote from: SGOrava – on
It does exactly that.
The problem was that some programs did not want to cooperate and user stated that he had to reinstall some packages to make them work.
We took the bet (on IRC) and tried to see what would happen after reinstalling all system packages.

Plus there could be some broken pacman hooks or some other things which were solved with this.

But in other words, during the migration we need to purge all systemd infected packages (especially from system).
Maybe I am wrong here, but this is what I think.

Have a nice day.

EDIT:
Think about it this way:
During the update we ask user to change pacman.conf and to update pacmans database.
Which means that packages from [core] will be listed as either from system or from unknown source.
The command reinstalls packages which now (after the changes) shows up in system repository.
These packages are originally from [core], which means they might strongly depends on systemd stuff.
This action gets rid of them and replaces them with Artix packages.

Have a nice day.


But wouldn't it be better, then, to do a forced update from the repos in the new pacman.conf file instead of depending on what is already installed from a broken configuration?

 

Re: [SOLVED] Problems after migration

Reply #5 –
Mystery 2 solved by switching to syslinux from rEFInd.