Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Linux, Unix › systemd is now default on new Arch installs
New Posts  All Forums:Forum Nav:

systemd is now default on new Arch installs

post #1 of 40
Thread Starter 
http://www.archlinux.org/news/systemd-is-now-the-default-on-new-installations/

I made the switch yesterday, to pure systemd, it was a lot easier than I thought, and every daemon I had in my rc.conf had a systemd service, even samsung-tools from the AUR.
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 2600K Asus P8Z68-V PRO PowerColor 5870 PCS++ GSkill DDR3 1600 8GB 
OSMonitorKeyboardPower
Arch Linux / Ubuntu 11.10 / Windows 7 HP ZR24w Filco Majestouch with blacks Real Power M850 
CaseMouseMouse Pad
Cooler Master HAF 932 Razer Deathadder 90x45cm l0l 
  hide details  
Reply
My System
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 2600K Asus P8Z68-V PRO PowerColor 5870 PCS++ GSkill DDR3 1600 8GB 
OSMonitorKeyboardPower
Arch Linux / Ubuntu 11.10 / Windows 7 HP ZR24w Filco Majestouch with blacks Real Power M850 
CaseMouseMouse Pad
Cooler Master HAF 932 Razer Deathadder 90x45cm l0l 
  hide details  
Reply
post #2 of 40
Quote:
Originally Posted by no1Joeno1 View Post

http://www.archlinux.org/news/systemd-is-now-the-default-on-new-installations/
I made the switch yesterday, to pure systemd, it was a lot easier than I thought, and every daemon I had in my rc.conf had a systemd service, even samsung-tools from the AUR.

I'm still fighting that particular change
post #3 of 40
I'm kind of pissed since I installed just a couple of days ago. Oh well, time to so some reading....
    
CPUMotherboardGraphicsRAM
AMD Phenom II X4 B55 Biostar A880GZ  AMD Radeon HD 4250 iGPU 8GB (2x4GB) Patriot Sector 5 DDR3 
Hard DriveHard DriveHard DriveOptical Drive
Seagate Barracuda 1TB (ST1000DM003) Western Digital Caviar SE 250GB Seagate External 1TB LG DVD Burner 
OSOSOSPower
Debian GNU/Linux 6.0.6 'Squeeze' 64-bit Arch Linux 64-bit FreeBSD 9.0 64-bit LPS Ultra 550 watt 
Case
Thermaltake V4  
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
AMD Phenom II X4 B55 Biostar A880GZ  AMD Radeon HD 4250 iGPU 8GB (2x4GB) Patriot Sector 5 DDR3 
Hard DriveHard DriveHard DriveOptical Drive
Seagate Barracuda 1TB (ST1000DM003) Western Digital Caviar SE 250GB Seagate External 1TB LG DVD Burner 
OSOSOSPower
Debian GNU/Linux 6.0.6 'Squeeze' 64-bit Arch Linux 64-bit FreeBSD 9.0 64-bit LPS Ultra 550 watt 
Case
Thermaltake V4  
  hide details  
Reply
post #4 of 40
Hey shrak, would your guide still work for systemd (now that its default) provioded you changed the way you set your daemons?
    
CPUMotherboardGraphicsRAM
AMD Phenom II X4 B55 Biostar A880GZ  AMD Radeon HD 4250 iGPU 8GB (2x4GB) Patriot Sector 5 DDR3 
Hard DriveHard DriveHard DriveOptical Drive
Seagate Barracuda 1TB (ST1000DM003) Western Digital Caviar SE 250GB Seagate External 1TB LG DVD Burner 
OSOSOSPower
Debian GNU/Linux 6.0.6 'Squeeze' 64-bit Arch Linux 64-bit FreeBSD 9.0 64-bit LPS Ultra 550 watt 
Case
Thermaltake V4  
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
AMD Phenom II X4 B55 Biostar A880GZ  AMD Radeon HD 4250 iGPU 8GB (2x4GB) Patriot Sector 5 DDR3 
Hard DriveHard DriveHard DriveOptical Drive
Seagate Barracuda 1TB (ST1000DM003) Western Digital Caviar SE 250GB Seagate External 1TB LG DVD Burner 
OSOSOSPower
Debian GNU/Linux 6.0.6 'Squeeze' 64-bit Arch Linux 64-bit FreeBSD 9.0 64-bit LPS Ultra 550 watt 
Case
Thermaltake V4  
  hide details  
Reply
post #5 of 40
Quote:
Originally Posted by jrl1357 View Post

Hey shrak, would your guide still work for systemd (now that its default) provioded you changed the way you set your daemons?

For the most part, anything regarding rc.conf won't be there as without initscripts there will be no rc.conf, the rest will work flawlessly though. I don't see a point in reinstalling though just for systemd, easy enough to uninstall initscripts, and install systemd tongue.gif

Easy enough to rewrite those to their " systemctl enable x.service " though.
post #6 of 40
Quote:
Originally Posted by Shrak View Post

Quote:
Originally Posted by jrl1357 View Post

Hey shrak, would your guide still work for systemd (now that its default) provioded you changed the way you set your daemons?

For the most part, anything regarding rc.conf won't be there as without initscripts there will be no rc.conf, the rest will work flawlessly though. I don't see a point in reinstalling though just for systemd, easy enough to uninstall initscripts, and install systemd tongue.gif

Easy enough to rewrite those to their " systemctl enable x.service " though.

ok, so as far as I can understand from the wiki, I install systemd, ctl enable/start each daemon in rc.conf (just two for me at the moment) then remove initscripts and rc.conf?
    
CPUMotherboardGraphicsRAM
AMD Phenom II X4 B55 Biostar A880GZ  AMD Radeon HD 4250 iGPU 8GB (2x4GB) Patriot Sector 5 DDR3 
Hard DriveHard DriveHard DriveOptical Drive
Seagate Barracuda 1TB (ST1000DM003) Western Digital Caviar SE 250GB Seagate External 1TB LG DVD Burner 
OSOSOSPower
Debian GNU/Linux 6.0.6 'Squeeze' 64-bit Arch Linux 64-bit FreeBSD 9.0 64-bit LPS Ultra 550 watt 
Case
Thermaltake V4  
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
AMD Phenom II X4 B55 Biostar A880GZ  AMD Radeon HD 4250 iGPU 8GB (2x4GB) Patriot Sector 5 DDR3 
Hard DriveHard DriveHard DriveOptical Drive
Seagate Barracuda 1TB (ST1000DM003) Western Digital Caviar SE 250GB Seagate External 1TB LG DVD Burner 
OSOSOSPower
Debian GNU/Linux 6.0.6 'Squeeze' 64-bit Arch Linux 64-bit FreeBSD 9.0 64-bit LPS Ultra 550 watt 
Case
Thermaltake V4  
  hide details  
Reply
post #7 of 40
Quote:
Originally Posted by jrl1357 View Post

ok, so as far as I can understand from the wiki, I install systemd, ctl enable/start each daemon in rc.conf (just two for me at the moment) then remove initscripts and rc.conf?

Yup, pretty much. Before you restart make sure to add systemd to the kernel parameters though;

/etc/default/grub
Code:
GRUB_CMDLINE_LINUX_DEFAULT="init=/usr/lib/systemd/systemd quiet"
post #8 of 40
Quote:
Originally Posted by Shrak View Post

Quote:
Originally Posted by jrl1357 View Post

ok, so as far as I can understand from the wiki, I install systemd, ctl enable/start each daemon in rc.conf (just two for me at the moment) then remove initscripts and rc.conf?

Yup, pretty much. Before you restart make sure to add systemd to the kernel parameters though;

/etc/default/grub
Code:
GRUB_CMDLINE_LINUX_DEFAULT="init=/usr/lib/systemd/systemd quiet"

so wait, the wiki says to boot grub, hit e, and then enter init=/usr/lib/systemd/systemd. will either work fine?

EDIT---

note that grub is installed in debian, not from my arch install, not sure if that makes a differance since I have one /boot partition
    
CPUMotherboardGraphicsRAM
AMD Phenom II X4 B55 Biostar A880GZ  AMD Radeon HD 4250 iGPU 8GB (2x4GB) Patriot Sector 5 DDR3 
Hard DriveHard DriveHard DriveOptical Drive
Seagate Barracuda 1TB (ST1000DM003) Western Digital Caviar SE 250GB Seagate External 1TB LG DVD Burner 
OSOSOSPower
Debian GNU/Linux 6.0.6 'Squeeze' 64-bit Arch Linux 64-bit FreeBSD 9.0 64-bit LPS Ultra 550 watt 
Case
Thermaltake V4  
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
AMD Phenom II X4 B55 Biostar A880GZ  AMD Radeon HD 4250 iGPU 8GB (2x4GB) Patriot Sector 5 DDR3 
Hard DriveHard DriveHard DriveOptical Drive
Seagate Barracuda 1TB (ST1000DM003) Western Digital Caviar SE 250GB Seagate External 1TB LG DVD Burner 
OSOSOSPower
Debian GNU/Linux 6.0.6 'Squeeze' 64-bit Arch Linux 64-bit FreeBSD 9.0 64-bit LPS Ultra 550 watt 
Case
Thermaltake V4  
  hide details  
Reply
post #9 of 40
you can do it your way, I do it that way since arch is the only install on here tongue.gif
post #10 of 40
Quote:
Originally Posted by Shrak View Post

you can do it your way, I do it that way since arch is the only install on here tongue.gif

ok, I followed the wiki insructions since it allowed a trhee step thing so I could stop if something wasn't going to work. the only thing right now that systemd is not starting is network, I am using netcfg there since it warned not to try using it in systemd but as just using network in rc.conf

the current step I am at in the wiki is a mixed systemd/sysvinit/initscripts I'm sure I can get netcfg working, but is there anything wrong with staying where I am now? it does *seem* to boot faster and I will have compatability with both systemd and rc.conf

EDIT---

and I can just have network in rc.conf. if that doesn't work, netcfg does work fine once booted so I can always set it to run on login or whatever
Edited by jrl1357 - 10/14/12 at 9:53am
    
CPUMotherboardGraphicsRAM
AMD Phenom II X4 B55 Biostar A880GZ  AMD Radeon HD 4250 iGPU 8GB (2x4GB) Patriot Sector 5 DDR3 
Hard DriveHard DriveHard DriveOptical Drive
Seagate Barracuda 1TB (ST1000DM003) Western Digital Caviar SE 250GB Seagate External 1TB LG DVD Burner 
OSOSOSPower
Debian GNU/Linux 6.0.6 'Squeeze' 64-bit Arch Linux 64-bit FreeBSD 9.0 64-bit LPS Ultra 550 watt 
Case
Thermaltake V4  
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
AMD Phenom II X4 B55 Biostar A880GZ  AMD Radeon HD 4250 iGPU 8GB (2x4GB) Patriot Sector 5 DDR3 
Hard DriveHard DriveHard DriveOptical Drive
Seagate Barracuda 1TB (ST1000DM003) Western Digital Caviar SE 250GB Seagate External 1TB LG DVD Burner 
OSOSOSPower
Debian GNU/Linux 6.0.6 'Squeeze' 64-bit Arch Linux 64-bit FreeBSD 9.0 64-bit LPS Ultra 550 watt 
Case
Thermaltake V4  
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Linux, Unix
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Linux, Unix › systemd is now default on new Arch installs