Just a few minutes ago via Archlinux Hispano official twitter a news has come to me from the official website of Archlinux and is that the packages systemd y udev now they form a single package called systemd-tools which also includes some new tools.
To substitute udev For this new package we proceed to update the repositories and execute the following command:
pacman -Sf systemd-tools
Note the parameter -f since it has to overwrite some man pages. Once the installation is finished we execute this other command to verify that the startup image de Linux:
mkinitcpio -p linux
Once everything is finished, it is only necessary to install the updates of the packages that required one or both packages.
Thanks for the news I had no idea
I set up
regards
And the advantages ?? or changes?
Only that, that udev is now inside that package, they do not specify much more except what I comment in the article
Thanks for the info. Updated without problems.
I thought using the "–force" option was not highly recommended. In this case you say it is to replace that man file.
I have simply followed the steps that I have found in the news on the arch linux home page:
Update the system normally:
pacman -Syu
Finally, if the "linux" package has been updated or some package has updated the boot image:
mkinitcpio -p linux
Makes a pacman -Qk
And see if you are missing files from a package, the safest thing is that systemd-tools is missing man files, in that case you reinstall it with the -f option
A clarification, by option f I meant force, it would be pacman -Sf
I hope I don't confuse people xDD
to see if someone can help me, update and restart and I get the tty1, and update the image; with mkinitcpio -p linux and I don't enter graphic mode, I don't know what to do anymore
Could you be more specific
Remember that the "mkinitcpio -p linux" is done immediately after updating, otherwise it will not go through grub on restart.
Something similar happened to me, but related to catalyst drivers
As I already mentioned in the article, after installing systemd-tools you have to update the system.
If you do not update the Xorg packages (I update them after installing the package) run pacman -Syyu (yes, with 2 and)
nothing man, stay the same
There are several posts on the Arch forum and some say they are doing this or creating a symbolic link.
I leave you the link to the Arch forum search engine, you have to go to sleep that tomorrow morning and I will not be able to answer, although I prefer that you use the forum to comment on this, so we have it more organized
Ufff…. The problems I have had with the systemd. Having catalyst installed I need xorg111. At the end of a while, I have managed to have catalyst with xorg111 and systemd-tools.
I have completely re-installed the xorg and installed cataylst-total from the AUR.
Now it works, but I don't know if when I restart it will work ...
I can use gnome, but gdm does not start ... Since I'm busy this week, I'm going to temporarily use Fedora 17. From here two weeks I'm going to try again 🙂
Thanks, everything worked perfect, I look forward to more articles about our dear ArchLinux, there are very few in this blog. They give more importance to Debian and Fedora.
Are you sure there are very few? … Hahaha, believe me, I love Arch more than Debian, I used it for a longer time. Check out all the Arch articles we've posted here:
https://blog.desdelinux.net/tag/archlinux
Compared to the articles out there for Debian, there are very few. You have to know how to read. But there are idiots on this blog, who want to fight for everything.
The package does not need to be expressly installed as it is automatically updated in the next pacman -Syu.
You should never but never force the package to install with the -f switch unless you are completely sure what you are doing ...
Systemd benefits ?, NONE
Disadvantages? Everything is very centralized, even the logs must be viewed with journalctl unless you do a hybrid installation. Another thing, the startup of services goes through the priority lining and it is not surprising that your network is not enabled because it does not find the interface eth0 that should have been started before, and NO, the after and before directives of the service do not pay attention.
In my opinion, a step back in Linux / GNU, a real rubbish that does not give more than headaches.