switching to full systemd

cirrus · 2012-08-17 04:24:20

This is more of a question than a support thread. (heh no doubt they will come later ) Having just read http://allanmcrae.com/2012/08/are-we-re … rch-linux/ i got to wondering if switching to full systemd is going to be a must in the not too distant future ? TBH im a very happy camper with current initscripts/rc.conf method but im not totaly against change, im sure there will be other archbangers who are also wondering if it will be imperative that we make the switch in the coming weeks/months. thanks in advance.
cirrus

handy · 2012-08-17 05:50:09

You may find this thread interesting:

http://bbs.archbang.org/viewtopic.php?id=3237

& this:

http://bbs.archbang.org/viewtopic.php?id=3152

ratcheer · 2012-08-17 06:16:54

cirrus, I believe from reading the arch-dev-public mail list that you are correct, systemd will be mandatory or nearly so very soon. I am not complaining, as I have already converted my system to native systemd with no rc.conf file and everything is going great. I also converted my logs to persistent journald.

Tim

Mr Green · 2012-08-17 07:23:55

We need to create a live iso that runs systemd in the near future

cirrus · 2012-08-17 10:34:21

thank you guys thats cleared things up a bit for me , ill do a dummy run on my usb stick install ( i have 3 installs) before i move onto doing it on main machines. Maybe someone in the know could jot down a few pointers in the tips & tricks section ? as im sure it will be well read in the coming weeks.
regards

<edit> followed these steps * all partitions on same hdd

$ pacman -S systemd # getting systemd itself, and any deps

* fixed myself a hostname, vconsole.conf, locale.conf, and timezone file in /etc #see https://wiki.archlinux.org/index.php/Sy … tion_files

$ pacman -R initscripts # removing initscripts, getting a rc.conf.pacsave just in case was good.
$ pacman -R sysvinit

$ pacman -S systemd-sysvcompat # replacing init and boot with systemd

$ pacman -S systemd-arch-units # getting Arch-compatible versions of native systemd service/unit-files

$ sudo shutdown -r now #Reboot

you will boot into tty1 just login & type startx

then to enable slim,DHCP,network mgr,ntp type in terminal as root ..
systemctl enable dhcpcd@eth0.service #for dhcp network | for static ip see https://wiki.archlinux.org/index.php/Systemd#Network
systemctl enable slim.service #slim *systemctl enable kdm.service if you a KDE user
systemctl enable NetworkManager.service #network manager
systemctl enable ntpd.service #Network Time Protocol daemon ( if ntp installed)
systemctl enable systemd-readahead-collect.service systemd-readahead-replay.service #To enable readahead this should in principle improve boot time depending on your kernel version and the type of your hard drive, your mileage may vary (i.e. it might be slower). In order for the readahead to work its magic, you should reboot a couple of times.

and all is good just to set up the journaled now went easier than i thought This worked for me on a single AB install & also on my main 3xboot machine which uses sabayons grub2.

Last edited by cirrus (2012-08-21 17:29:50)

handy · 2012-08-17 17:27:41

As you may have noticed from the first link I posted previously, you can also get rid of consolekit, which is a redundant resource hog:

ConsoleKit is a framework for managing user sessions and permissions. Some of the most common usages of ConsoleKit are allowing non-root users to mount removable media and suspending/shutting down the computer through common desktop applications (e.g. Thunar, Nautilus, the GNOME shutdown menu, etc.).
Furthermore, ConsoleKit will run ~60 threads in the background, where most of them are never used. If you mind using an unmaintained application using so much threads and you only want a convenient way to mount disks as user, have a look at udev, udiskie and polkit. Otherwise you might consider switching to systemd.

https://wiki.archlinux.org/index.php/ConsoleKit

You do have to remove oblogout though, which is an Obpenbox plugin script, depending on consolekit.

cirrus · 2012-08-17 18:16:58

@handy thanks for the heads up !

fschiff · 2012-08-18 19:36:08

You should remove initscripts, *after* you get systemd working, though. Just common sense. (And the inittab file is used for part of turning off the machine)

cirrus · 2012-08-18 20:26:43

when using pacman to remove said files it behind a leaves a rc.conf .new back up,as for initab yes i suppose it should be backed up , i thought most arch users had common sense. this method has worked for many on arch forums and has worked for me on 3 seperate installs ,with no need for backing up initab , and 3 or 4 folk on these archbang forums that im aware of. when you install sysvcompat which is a systemd dep it removes init scripts i believe.
regards

Last edited by cirrus (2012-08-19 13:23:33)

ArchVortex · 2012-08-18 21:58:00

Yes, the Windozing of Linux has begun by Red Hat. Arch will eventually have to only run on full redhatd .... uh I mean poetteringd ... um .... systemd unless someone spends the time to get Arch running on OpenRC or Upstart and forks it. Gnome and eventually KDE will be the only DE for systemd. Xfce, LXDE and Unity will be the choice of non-systemd DE and WM like Openbox, Fluxbox, awesome, xmonad, etc. will continue to gain popularity.

cirrus · 2012-08-19 05:11:45

WOW thanks for that info archvortex , it will be a sad day indeed if we have to toe the party line , seems our freedoms are being ripped from us from all angles these days im not a fan of pulse audio or herr pottering.

Mr Green · 2012-08-19 05:32:18

http://en.wikipedia.org/wiki/OpenRC

Fork

https://github.com/ilikenwf/archlinux-openrc

Maybe we need an Arch fork 'Archcore' [SHJ idea not mine!]

Cannot find the redhat link only stuff about uefi licensing boot loading stuff

cirrus · 2012-08-21 15:59:42

@handy thanks i got rid of consolekit , slim and oblogout was dependencies so i uninstalled em then consolekit and reinstalled slim and set slim.conf to autologin , thanks man !!

cirrus · 2012-08-28 02:11:20

glad it worked for you ackt1c i had 0 problems ( apart from the oblogout freeze where only a hard boot would suffice) on both installs , and my pal from new jersey followed above too with no probs , so i dunno sounds like ur fstab got messed up or somin , glad it worked for ya . as handy says its wise to now get rid of oblogout and consolekit , see handys links above.

Last edited by cirrus (2012-08-28 02:12:25)

ArchVortex · 2012-08-28 03:17:49

The OpenRC for Arch is still reliant on udev. Need to port over mdev from Gentoo to get rid of udev (systemd reliance).

Mr Green · 2012-08-28 10:35:04

/etc/oblogout.conf needs editing to get working again with systemd. Arch wiki guide for systemd has all you need...

Running systemd on my desktop, am still not convinced of any real gain or advantage to using it yet!

handy · 2012-08-28 18:00:49

I doubt that Red Hat would have gone down the systemd path if it wasn't going to make their life easier. They are in the (a very successful) business of creating & servicing (their business) reliable server systems.

I think that the Red Hat administration see systemd as cost effective change.

cirrus · 2012-08-29 02:35:42

@mr green only thing ive noticed of note is faster boot / shutdown , like yourself other than that ive not noticed any other benefits , i think it has more to do with the internal workings opposed to performance gain , but hey what do i know , i still miss the arch ncurses installer

pablokal · 2012-08-29 05:15:03

Handy's quote

I doubt that Red Hat would have gone down the systemd path if it wasn't going to make their life easier. They are in the (a very successful) business of creating & servicing (their business) reliable server systems.
I think that the Red Hat administration see systemd as cost effective change.

Another quote is answering him:

Money, is what talks. If RH Inc begins to lose money over this, heads will roll, and the necessary walkbacks will happen. Their enterprise customers should raise holy hell over this. Along the lines of, "Hi, we're a Fortune 500 company, we rely on you to provide us a stable secure server platform for our critical business infrastructure. Why the fuck is Gnome development even involved, and why are you changing a critical component of our server platform for the sake of a fucking desktop environment?" That, is the best contribution anyone can make to this.
VinzC wrote:
What also pisses me off somehow is Gnome stuff ruling the rest of the system packages. *That* I really don't like. In the end, what will mostly distinguish distributions is only their package manager. One systemd to rule them all... just as if there were only one way to boot a machine, run services and manage hardware devices.

it's braindead. Completely and totally braindead. Device management is not simply a novelty item for desktop users. Linux makes its money as a server platform. Server platforms also need a dev manager. It's as though they've forgotten the world even exists outside of a home user's desktop, that people actually use linux for something other than running Gnome. How in the blue fuck someone thought it was a great idea to let THAT drive development is completely baffling to me.

source: https://forums.gentoo.org/viewtopic-t-9 … 902d3bcaa0

cirrus · 2012-09-07 10:23:14

@handy i just got round to removing slim and consolekit (which is a dep for most login managers) now i autologin via getty , and can wave bye bye to them 60 null consolekit threads which i would see in htop

Mr Green · 2012-09-11 23:20:31

Anyone tried using slim-nock

https://aur.archlinux.org/packages.php?ID=59448

Arch Linux

Announcement

#1 2012-08-17 04:24:20

switching to full systemd

#2 2012-08-17 05:50:09

Re: switching to full systemd

#3 2012-08-17 06:16:54

Re: switching to full systemd

#4 2012-08-17 07:23:55

Re: switching to full systemd

#5 2012-08-17 10:34:21

Re: switching to full systemd

#6 2012-08-17 17:27:41

Re: switching to full systemd

#7 2012-08-17 18:16:58

Re: switching to full systemd

#8 2012-08-18 19:36:08

Re: switching to full systemd

#9 2012-08-18 20:26:43

Re: switching to full systemd

#10 2012-08-18 21:58:00

Re: switching to full systemd

#11 2012-08-19 05:11:45

Re: switching to full systemd

#12 2012-08-19 05:32:18

Re: switching to full systemd

#13 2012-08-21 15:59:42

Re: switching to full systemd

#14 2012-08-28 02:11:20

Re: switching to full systemd

#15 2012-08-28 03:17:49

Re: switching to full systemd

#16 2012-08-28 10:35:04

Re: switching to full systemd

#17 2012-08-28 18:00:49

Re: switching to full systemd

#18 2012-08-29 02:35:42

Re: switching to full systemd

#19 2012-08-29 05:15:03

Re: switching to full systemd

#20 2012-09-07 10:23:14

Re: switching to full systemd

#21 2012-09-11 23:20:31

Re: switching to full systemd

Board footer