systemd - question, problems

cpu · 2012-09-20 08:27:32

Hello,

After moving to systemd I have some issues regarding this new init system

1. Which rc files I can delete? How can I set scheduler for my HDD like I did in rc.local?
2. Is there a way to setup pure systemd on currently running system and rid off rc files?
3. Alsa sound starts very slowly so after I get login prompt there are some info from starting systemd services - I mean alsa and dbus

tomk · 2012-09-20 09:16:10

1. Write systemd service file(s) for the command(s) that rc.local currently handles.
2. Isn't that what you're doing? It's all in the wiki and man pages.
3. https://wiki.archlinux.org/index.php/Sy … console.3F

cpu · 2012-09-20 09:24:11

But best way to install systemd from scratch is to download new install cd and setup whole system with systemd?

2. Yep, I'm trying but many rc.* files are still in system and I don't know which files I can remove
3. I've set up this already - I have different problem - system starts, some output from systemd and then I get login prompt but systemd still working - I tought that I get login prompt when everything is ready.

Trilby · 2012-09-20 11:43:49

cpu wrote:

But best way to install systemd from scratch is to download new install cd and setup whole system with systemd?

What on earth gave you that idea? No. The wiki leads you through in four (or is it five) simple steps to fully transition a current system.

tomk · 2012-09-20 11:50:47

cpu wrote:

many rc.* files are still in system

Which ones exactly? If you haven't removed the initscripts package, obviously they are still going to be there. And if you're referring to anything in the /etc/rc.d/ directory, they all belong to individual packages, and you gain nothing (apart from a miniscule amount of disk space) by removing them.

cpu · 2012-09-20 14:05:03

Ok, thanks, what about /etc/conf.d directory? Do I need this?

tomk · 2012-09-20 14:17:48

Again, files in /etc/conf.d/ belong to individual packages, so they should only be installed/removed by pacman. Applications that provide a conf.d file will use it regardless of the user's choice of init system.

As with all things in Arch, your success, or otherwise, depends on you. All this information is available in the documentation, please read it thoroughly.

ewaller · 2012-09-20 15:40:47

Moved to "Installation"

ngoonee · 2012-09-21 01:16:19

tomk wrote:

As with all things in Arch, your success, or otherwise, depends on you. All this information is available in the documentation, please read it thoroughly.

Agree here.

I'd suggest first learning about what those files are for, as you seem to be having the general idea of "hey, let's delete this stuff I don't really know about because its there". Either don't touch stuff or learn about it before touching it.

lilsirecho · 2012-09-21 02:35:12

We learn only by making mistakes..........................

ngoonee · 2012-09-21 05:29:28

lilsirecho wrote:

We learn only by making mistakes..........................

Yet we advise others against making mistakes. Especially those mistakes which indicate a user more willing to do rather than understand. Which sort of diminishes the likelihood of the post-mistake learning in any case.

Arch Linux

#1 2012-09-20 08:27:32

systemd - question, problems

#2 2012-09-20 09:16:10

Re: systemd - question, problems

#3 2012-09-20 09:24:11

Re: systemd - question, problems

#4 2012-09-20 11:43:49

Re: systemd - question, problems

#5 2012-09-20 11:50:47

Re: systemd - question, problems

#6 2012-09-20 14:05:03

Re: systemd - question, problems

#7 2012-09-20 14:17:48

Re: systemd - question, problems

#8 2012-09-20 15:40:47

Re: systemd - question, problems

#9 2012-09-21 01:16:19

Re: systemd - question, problems

#10 2012-09-21 02:35:12

Re: systemd - question, problems

#11 2012-09-21 05:29:28

Re: systemd - question, problems

Board footer