On 02/05/14 15:01, Canek Peláez Valdés wrote:
[snip]
If you are using GRUB2, change /etc/default/grub and modify
GRUB_CMDLINE_LINUX so it has "init=/usr/lib/systemd/systemd". Then run
grub2-mkconfig again.
Beware, systemd requires some kernel config options set or it will not
work. For systemd 208, these are:
AUTOFS4_FS
BLK_DEV_BSG
CGROUPS
DEVTMPFS
DMIID
EPOLL
FANOTIFY
FHANDLE
INOTIFY_USER
IPV6
NET
PROC_FS
SECCOMP
SIGNALFD
SYSFS
TIMERFD
Also, the following kernel config options should *NOT* be set:
IDE
SYSFS_DEPRECATED
SYSFS_DEPRECATED_V2
GRKERNSEC_PROC
Lastly, if you have /usr in a different partition from /, you *need*
an initramfs (this is now true also for OpenRC). Please check the
instructions set in:
https://wiki.gentoo.org/wiki/Systemd
To finish, let me remark that systemd never had problems in your
system. The problem was that you were not running systemd.
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
Thank you for correction. You are correct I would need to switch to new
systemd.
I think for now I'll go back to udev as I'm afraid something might not
work
after switching :-/
Why don't you give it a try? You are almost there.
When booting, edit the grub entry and add
init=/usr/lib/systemd/systemd. If it works, great; otherwise, you
reboot and get back to where you were.
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
I've tried to switch my backup system to systemd by adding line
init=/usr/lib/systemd/systemd to grub donfig and as I suspected the system
did not boot. I got a kernel paanic.
can not open root device "hda3" or unknown block (0,0): error -6
It probably could be fixed, but it will take time and info about your
system (partition arrangement, if you use or not an initramfs, how do
you created it, etc.)
Perhaps you would prefer to get back to OpenRC+udev. Just be aware
that, if you had installed systemd, it was because something requires
it. If you don't use systemd, you will have degraded functionality,
since more and more things require systemd or parts of it
(specifically logind). This not only applies to GNOME 3, but also to
Xfce (which uses a lot of GNOME/Gtk+/glib infrastructure). KDE is also
analyzing how to better use systemd provided technologies.
You can try to set USE="-systemd consolekit" and do a emerge -uDNv
world. That will bring back much (but not all) of the functionality;
just be aware that ConsoleKit is unmaintained and it will eventually
bitrot.
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
I have to create new boot strap CD (as the one I have have old kernel) and get
to they system first to change grub.conf.
Will get back to you.
--
Joseph
