Back to OpenRC

Discussions Regarding Software

Moderator: Moderators

Post Reply
sqlpython
Technological Hen
Posts: 386
Joined: Mon Jun 18, 2007 7:01
Location: If It Moves Compile It
Contact:

Back to OpenRC

Post by sqlpython » Fri Aug 09, 2013 17:29

I abandoned systemd after having used it on my main laptop Thinkpad sl410 since May.
One change, after the Update to Kernel 3.7.xx, & my method of actuating systemd which was via this line in Grub2 no longer worked (but that was OK)
I was simply calling init=/usr/lib/systemd/systemd from Grub.
Instead the New method simplified starting systemd by running eselect such as

Code: Select all

eselect sysvinit set systemd 
I returned to an Openrc boot again by running

Code: Select all

eselect sysvinit set sysvinit
Under a systemd I was beginning to see errors on boot of
system/IO
type. In fact 3 during boot. As I was having other boot issues with this kernel and booting to New Artwork.
I didn't see the need to work on both issues while each were Only small but nagging in nature.
PLUS under the Grub2 systemd boot the Pink Artwork splash was Magnified. I was staring a the Pink screen for a longer period. With openrc the boot is longer but the Pink Artwork of Sabayon 13 is only a quick FLash.
When you are Caffeinated to the Max the Pink iridescent screen sets you teeth to chattering.. :lol:
I will give systemd another try on the next upgrade.. too bad for me.. I liked it.
Criticism accepted for Solutions that work. ;^)
Sabayon 13-DEBIAN 8- #! -Sid-Slackware 14-Calculate 13-Bridge

Post Reply