You are not logged in.
Systemd is in core and many people use and will use it or try to set up pure systemd systems.
However there are some stuff that are not described in the wiki. For example there is no systemd reference in NetworkManager, ntp, avahi etc.
Usually what needs to be added is something like a systemctl enable foo.servive.
And before someone asks why don't you do it yourself i will say that i don't feel comfortable contributing in an "Official" documentation project like the wiki. There is a great chance that i ll be wrong.
Thanks.
Offline
The daemons arrray in /etc/rc.conf should be loaded automatically by systemd. If something you need is not loaded you can try manually by
systemctl enable foo.service
. Those stuff are pretty basic.
I 'm not sure what else you are asking.
Offline
Aw, don't be afraid of editing the wiki! It's fun, and if you make a mistake someone will correct it, so it's no problem.
Offline
The daemons arrray in /etc/rc.conf should be loaded automatically by systemd. If something you need is not loaded you can try manually by
systemctl enable foo.service
. Those stuff are pretty basic.
I 'm not sure what else you are asking.
I went for a pure systemd system and i found that some instructions were missing. Yes it might be basic but for someone who is just starting an installation it might be useful. All i am asking is to add something like:
For systemd users
systemctl enable foo.service
wherever is needed. (network manager, avahi, ntp) A guide for a pure systemd system could also be usefull but its quite big of a task i think.
Aw, don't be afraid of editing the wiki! It's fun, and if you make a mistake someone will correct it, so it's no problem. smile
It might be fun but i don't think there will be fun for someone that might follow the wrong instructions. So i think is a job for someone thats more knowledgeable.
Offline
You've got the wrong idea about the wiki, and possibly about wikis in general. The wiki is definitely NOT an "official documentation project" - it is created and maintained by the user community, and at any given time, it will contain many errors and omissions. These are corrected over time, as part of the ongoing review and maintenance process.
That said, it is understandable if you don't feel confident enough yet to make direct changes. In that case, consider using the "discussion" tab at the top of any wiki page to make suggestions.
Offline
You've got the wrong idea about the wiki, and possibly about wikis in general. The wiki is definitely NOT an "official documentation project" - it is created and maintained by the user community, and at any given time, it will contain many errors and omissions. These are corrected over time, as part of the ongoing review and maintenance process.
Well not for all the wikis but in a project like Arch where the wiki is the goto place for finding a solution i would expect things to be more "strict" and controlled in a way.
Anyway.
Offline
tomk wrote:You've got the wrong idea about the wiki, and possibly about wikis in general. The wiki is definitely NOT an "official documentation project" - it is created and maintained by the user community, and at any given time, it will contain many errors and omissions. These are corrected over time, as part of the ongoing review and maintenance process.
Well not for all the wikis but in a project like Arch where the wiki is the goto place for finding a solution i would expect things to be more "strict" and controlled in a way.
Anyway.
The reason its the goto place is because of strong community participation and generally strong community technical ability. Not to minimize the contributions of the devs, but all the devs+TUs together couldn't put together something that comprehensive, its a community effort.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
It might be fun but i don't think there will be fun for someone that might follow the wrong instructions. So i think is a job for someone thats more knowledgeable.
Do you mean someone more knowledgable than yourself? If you don't know what you're doing, just how did you discover that some steps in the process were missing from the wiki? Or, if you mean someone more knowledgeable about editing wikis, well, time you spend complaining here is time that could be spent learning.
Offline
89c51 wrote:It might be fun but i don't think there will be fun for someone that might follow the wrong instructions. So i think is a job for someone thats more knowledgeable.
Do you mean someone more knowledgable than yourself? If you don't know what you're doing, just how did you discover that some steps in the process were missing from the wiki? Or, if you mean someone more knowledgeable about editing wikis, well, time you spend complaining here is time that could be spent learning.
More knowledgeable in linux than myself. I just follow the instructions and google. There is a big difference from someone who reads wikis and googles to someone who knows that the thing that he will suggest will work. Especially in a document that will be read by a lot of people. To give you an example ntp needs some setting up to work with NetworkManager which i still haven't figured out completely. I don't think you would like me to write an article in the wiki on that subject.
Offline
I've an analogy. When we start to learn Linux, we are all given a dunce cap to wear. As we learn we are given awards; little stickers of little stars, or cresent moons, As a reward, we are allowed to put these stickers on our dunce caps. Eventually after we earn enough rewards and have stuck them to our caps, we start to look like wizards
Don't be bashful -- you are starting to look like a wizard
Last edited by ewaller (2012-06-16 23:37:19)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
I've an analogy. When we start to learn Linux, we are all given a dunce cap to wear. As we learn we are given awards; little stickers of little stars, or cresent moons, As a reward, we are allowed to put these stickers on our dunce caps. Eventually after we earn enough rewards and have stuck them to our caps, we start to look like wizards
Don't be bashful -- you are starting to look like a wizard
I fully endorse this product and/or service.
Burninate!
Offline
Came here to ask a similar question. Is it standard policy now to update any instructions regarding adding daemons in rc.conf to include instructions for systemd services? Some instructions include the use of rc.d start .. which need alternative methods on a systemd only system.
Offline
I suggest using the {{out of date}} template to mark wiki pages that need updating for systemd. In particular, use the reason argument: {{out of date | systemd}}.
Offline
Came here to ask a similar question. Is it standard policy now to update any instructions regarding adding daemons in rc.conf to include instructions for systemd services? Some instructions include the use of rc.d start .. which need alternative methods on a systemd only system.
There IS no 'policy' as such. If the wiki is outdated, fix it (preferably) or mark it outdated.
Key word - community effort.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline