Difference between revisions of "Talk:System maintenance"

From ArchWiki
Jump to navigation Jump to search
(Merge?)
(Deletion proposal: re)
Line 71: Line 71:
 
::::About [[Enhance_system_stability#Arch_Specific_Tips_2]], I still think much of it is about "maintenance", not "stability", and ''moving'' it here wouldn't duplicate anything (it's not ''copying'') :) Still, without another opinion we're kind of stuck here.
 
::::About [[Enhance_system_stability#Arch_Specific_Tips_2]], I still think much of it is about "maintenance", not "stability", and ''moving'' it here wouldn't duplicate anything (it's not ''copying'') :) Still, without another opinion we're kind of stuck here.
 
::::-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 13:28, 20 May 2014 (UTC)
 
::::-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 13:28, 20 May 2014 (UTC)
 +
 
::::: I think the new format reduce page readability. I skim through the whole page and get little information. Just keep it simple please. --[[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 10:11, 31 May 2014 (UTC)
 
::::: I think the new format reduce page readability. I skim through the whole page and get little information. Just keep it simple please. --[[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 10:11, 31 May 2014 (UTC)
 +
 +
::::::I'm starting to restore the previous format while trying to merge content among this article, [[Enhance system stability]], [[Pacman tips]] and maybe others if needed: I don't know how long it will take... -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 14:10, 11 June 2014 (UTC)
  
 
== Outdated 'Error Checking' section? ==
 
== Outdated 'Error Checking' section? ==

Revision as of 14:10, 11 June 2014

Merge?

Enhancing_Arch_Linux_Stability#Maintaining_Arch is a part of an article about stability, so it suggest using e.g. linux-lts, which is not necessary if we talk about maintenance.

We should decide whether we merge this article into Enhancing_Arch_Linux_Stability or do we move the maintenance part here. -- Karol (talk) 19:18, 25 December 2013 (UTC)

Good idea, I'd prefer merging Enhancing_Arch_Linux_Stability#Maintaining_Arch here and properly linking the two articles with each other. Note however that some further reorganization should probably be done, in fact sections like Enhancing_Arch_Linux_Stability#Subscribe_to_NVD.2FCVE_alerts_and_only_upgrade_on_a_security_alert should stay in Enhancing_Arch_Linux_Stability. -- Kynikos (talk) 02:49, 26 December 2013 (UTC)

Deletion proposal

This is a continuation of #Merge? above (the article has been marked for deletion).

I agree that this article is currently duplicating others, however I like the idea of having an article dedicated to maintenance (it's also linked from General recommendations).

The "Error checking" section wouldn't have a much better place to be moved to, maybe General Troubleshooting.

It's true that the "Package tasks" section duplicates Pacman Tips#Maintenance, but since Pacman Tips is already very long and has a title which could be considered a bit generic, why not do the opposite merge and move that section here?

Then, as stated in #Merge?, almost all Enhancing_Arch_Linux_stability#Maintaining_Arch could be merged here.

Finally, if we decide to keep it, it should probably be renamed to simply System maintenance.

What do you think? -- Kynikos (talk) 10:11, 12 May 2014 (UTC)

Before making the deletion proposal i should have read the talk page. I think you are right that merging other content here is better than deleting this article. I removed the deletion flag.
Then, as stated in #Merge?, almost all Enhancing_Arch_Linux_stability#Maintaining_Arch could be merged here.
>Done.
Finally, if we decide to keep it, it should probably be renamed to simply System maintenance.
>Also done.
-- Teateawhy (talk) 12:27, 12 May 2014 (UTC)
As i understand this page has its focus on tasks that need to be done regularily. Therefore i suggest using the following format:
Example
task: A short description of the task.
reason: Why this task should be done.
frequency: A suggestion for how regular this task should be done.
wiki: A list of links providing more detail, explaining how to do the task.
cronjob: If the task is suited well for running it from a cronjob with cron or Systemd/cron functionality.
(optional)procedure: The commands for how to do the tasks. Use this if there is no other wiki page and the command is very simple/short.
I have edited the section about package tasks to use this format, and it looks a lot cleaner now. My suggestion is not to go into detail about how to do the tasks here, as most are explained on other pages.
Instead focus on how often they need to be done, and make a list so it is easy to work off the list.
The sections that explained how to do system upgrades were moved back to "Enhance system stability", as they do not fit within this idea.
-- Teateawhy (talk)
Honestly I see this format as overly complicated: using the tags is redundant when you can simply write:
Do this and that because of this reason.
See This article for details.
Many tags have to be left empty too, which IMO doesn't look very good.
The tip to automate some tasks could be left at the top of the article (perhaps in a proper Tip template), with the links to systemd/cron functionality and cron. Also I wouldn't recommend frequency times, and leave that to be decided by the user.
I still think much of Enhance_system_stability#Arch_Specific_Tips_2 should really be moved to this page as you did but then reverted. I'd create a "System upgrade" section for that.
-- Kynikos (talk) 07:58, 14 May 2014 (UTC)
>using the tags is redundant
Yes, but it increases the readability.
>many tags have to be left empty, too, which doesn't look very good.
There are only 5 empty tags on the page, and i think we can still come up with something to write there. (Only 3 after removing the frequency tag.)
>I wouldn't recommend frequency times, and leave that to be decided by the user.
Good point, as you say it is a recommendation. I have removed the frequency tag now.
>I still think much of Enhance_system_stability#Arch_Specific_Tips_2 should really be moved to this page as you did but then reverted. I'd create a "System upgrade" section for that.
I disagree. This page makes much more sense to me as a collection of tasks, with no prolonged text about how to do the task, but a link instead. If we include the content here, we have the same problem as initally, duplicating the content of other pages.
Well, the tags problem is too subjective, I think we need a third opinion to solve it.
About the empty tags, maybe we can just remove them?
About Enhance_system_stability#Arch_Specific_Tips_2, I still think much of it is about "maintenance", not "stability", and moving it here wouldn't duplicate anything (it's not copying) :) Still, without another opinion we're kind of stuck here.
-- Kynikos (talk) 13:28, 20 May 2014 (UTC)
I think the new format reduce page readability. I skim through the whole page and get little information. Just keep it simple please. --Fengchao (talk) 10:11, 31 May 2014 (UTC)
I'm starting to restore the previous format while trying to merge content among this article, Enhance system stability, Pacman tips and maybe others if needed: I don't know how long it will take... -- Kynikos (talk) 14:10, 11 June 2014 (UTC)

Outdated 'Error Checking' section?

It mentions 'errors.log' and 'everything.log' which do not exist on my shiny new install (2014-03-20). I'm guessing a recommendation to check journalctl -b is more appropriate these days? (I'm a total Arch noob, so not sure) Scottt (talk) 10:21, 26 March 2014 (UTC)

+1 for adding journalctl info here. Could you help to add it? --Fengchao (talk) 12:33, 2 May 2014 (UTC)