From e022e043c6f83437a1fbcdf4010d01506e8313f0 Mon Sep 17 00:00:00 2001 From: Aneta Šteflová Petrová Date: Aug 22 2017 17:42:14 +0000 Subject: Fill assembly files with the right content --- diff --git a/en-US/sysadmin_user_stories/assembly-adding_new_user_accounts.adoc b/en-US/sysadmin_user_stories/assembly-adding_new_user_accounts.adoc index 8c35ed2..67b2844 100644 --- a/en-US/sysadmin_user_stories/assembly-adding_new_user_accounts.adoc +++ b/en-US/sysadmin_user_stories/assembly-adding_new_user_accounts.adoc @@ -1,21 +1,11 @@ -// Include an 'ID' that corresponds to the title of the assembly -// The ID will be used as an anchor for linking to the title -// Do not change the ID to make sure existing links keep working -[#doing_several_tasks_in_sequence] -= Doing Several Tasks in Sequence +[#adding-a-new-user-account] += Adding a New User Account -_Start the title with a verb in the gerund form, such as Creating or Configuring._ +This section describes how you can add a new user account so that another person can use the system as a regular user. -// Ideally, base the name of the file on the title to avoid confusion -// Use a consistent system for filenames and IDs, e.g.: -// * Only substitute spaces with underscores -// * Don't use any CAPS +// Can be adapted from https://bex.fedorapeople.org/fedora-docs-web/f26/system-administrators-guide/basic-system-configuration/Managing_Users_and_Groups.html -_Use this template to document a user story -- any series of tasks that the user must perform in a specific order to accomplish something._ - -This paragraph explains what the user will accomplish by working through the tasks in sequence. It sets context or explains the benefit the user will gain by performing the tasks that comprise the story. May include more than 1 paragraph, and may include concept modules if needed to fully explain the context, benefits, and other things the user must understand to complete the tasks successfully. - -.Prerequisites +== Prerequisites * Sentence or a bulleted list of pre-requisites that must be in place or done before the user starts this task. @@ -23,19 +13,19 @@ This paragraph explains what the user will accomplish by working through the tas * Text can be a link to a pre-requisite task that the user must do before starting this task. -.Procedure +include::concept-what_is_a_user.adoc[leveloffset=+1] -_Can link to or include task modules, depending on the writer's choice based on information needs. If you link to task modules, add each link as 1 step in a numbered list. The order of included task modules or of the linked steps is important to a repeatable successful outcome. Following is an example of linking to task modules in numbered steps._ +include::concept-what_is_a_group.adoc[leveloffset=+1] -. Link to 1st task to perform. +include::concept-what_happens_when_a_new_user_is_created.adoc[leveloffset=+1] -. Format the step line as an unnumbered bullet if the procedure includes only 1 step (exception to numbering the steps). +include::procedure-useradd.adoc[leveloffset=+1] -. Link to 3rd task to perform. +include::procedure-groupadd.adoc[leveloffset=+1] -. Link to the Nth task to perform. +include::procedure-adding_users_to_user_groups.adoc[leveloffset=+1] -.Related Information +== Additional Resources * Bulleted list of links to concepts, reference, or other tasks closely related to this user story. diff --git a/en-US/sysadmin_user_stories/assembly-adjusting_file_permissions.adoc b/en-US/sysadmin_user_stories/assembly-adjusting_file_permissions.adoc index 8c35ed2..83b0f31 100644 --- a/en-US/sysadmin_user_stories/assembly-adjusting_file_permissions.adoc +++ b/en-US/sysadmin_user_stories/assembly-adjusting_file_permissions.adoc @@ -1,21 +1,11 @@ -// Include an 'ID' that corresponds to the title of the assembly -// The ID will be used as an anchor for linking to the title -// Do not change the ID to make sure existing links keep working -[#doing_several_tasks_in_sequence] -= Doing Several Tasks in Sequence +[#adjusting-file-permissions] += Adjusting File Permissions -_Start the title with a verb in the gerund form, such as Creating or Configuring._ +This section describes how you can adjust permissions for a file or directory so that a specific user or user group can read, write, or execute the file or directory. -// Ideally, base the name of the file on the title to avoid confusion -// Use a consistent system for filenames and IDs, e.g.: -// * Only substitute spaces with underscores -// * Don't use any CAPS +// Can be adapted from https://bex.fedorapeople.org/fedora-docs-web/f26/system-administrators-guide/basic-system-configuration/Managing_Users_and_Groups.html -_Use this template to document a user story -- any series of tasks that the user must perform in a specific order to accomplish something._ - -This paragraph explains what the user will accomplish by working through the tasks in sequence. It sets context or explains the benefit the user will gain by performing the tasks that comprise the story. May include more than 1 paragraph, and may include concept modules if needed to fully explain the context, benefits, and other things the user must understand to complete the tasks successfully. - -.Prerequisites +== Prerequisites * Sentence or a bulleted list of pre-requisites that must be in place or done before the user starts this task. @@ -23,19 +13,13 @@ This paragraph explains what the user will accomplish by working through the tas * Text can be a link to a pre-requisite task that the user must do before starting this task. -.Procedure - -_Can link to or include task modules, depending on the writer's choice based on information needs. If you link to task modules, add each link as 1 step in a numbered list. The order of included task modules or of the linked steps is important to a repeatable successful outcome. Following is an example of linking to task modules in numbered steps._ - -. Link to 1st task to perform. - -. Format the step line as an unnumbered bullet if the procedure includes only 1 step (exception to numbering the steps). +include::procedure-navigating_to_a_file_or_a_directory.adoc[leveloffset=+1] -. Link to 3rd task to perform. +include::procedure-chown_chmod_on_directory_for_user_group.adoc[leveloffset=+1] -. Link to the Nth task to perform. +include::reference-permission_types.adoc[leveloffset=+1] -.Related Information +== Additional Resources * Bulleted list of links to concepts, reference, or other tasks closely related to this user story. diff --git a/en-US/sysadmin_user_stories/assembly-changing_default_database_location.adoc b/en-US/sysadmin_user_stories/assembly-changing_default_database_location.adoc index 8c35ed2..115ec4e 100644 --- a/en-US/sysadmin_user_stories/assembly-changing_default_database_location.adoc +++ b/en-US/sysadmin_user_stories/assembly-changing_default_database_location.adoc @@ -1,21 +1,11 @@ -// Include an 'ID' that corresponds to the title of the assembly -// The ID will be used as an anchor for linking to the title -// Do not change the ID to make sure existing links keep working -[#doing_several_tasks_in_sequence] -= Doing Several Tasks in Sequence +[#changing-default-mariadb-database-location] += Changing Default MariaDB Database Location -_Start the title with a verb in the gerund form, such as Creating or Configuring._ +This section describes how you can change the default location for MariaDB. -// Ideally, base the name of the file on the title to avoid confusion -// Use a consistent system for filenames and IDs, e.g.: -// * Only substitute spaces with underscores -// * Don't use any CAPS +// Can be adapted from https://docs.fedoraproject.org/en-US/Fedora/25/html/SELinux_Users_and_Administrators_Guide/sect-Managing_Confined_Services-MariaDB-Configuration_Examples.html#sect-Managing_Confined_Services-MariaDB-Configuration_Examples-Changing_Database_Location -_Use this template to document a user story -- any series of tasks that the user must perform in a specific order to accomplish something._ - -This paragraph explains what the user will accomplish by working through the tasks in sequence. It sets context or explains the benefit the user will gain by performing the tasks that comprise the story. May include more than 1 paragraph, and may include concept modules if needed to fully explain the context, benefits, and other things the user must understand to complete the tasks successfully. - -.Prerequisites +== Prerequisites * Sentence or a bulleted list of pre-requisites that must be in place or done before the user starts this task. @@ -23,19 +13,13 @@ This paragraph explains what the user will accomplish by working through the tas * Text can be a link to a pre-requisite task that the user must do before starting this task. -.Procedure - -_Can link to or include task modules, depending on the writer's choice based on information needs. If you link to task modules, add each link as 1 step in a numbered list. The order of included task modules or of the linked steps is important to a repeatable successful outcome. Following is an example of linking to task modules in numbered steps._ - -. Link to 1st task to perform. - -. Format the step line as an unnumbered bullet if the procedure includes only 1 step (exception to numbering the steps). +// include::concept-.adoc[leveloffset=+1] -. Link to 3rd task to perform. +// include::procedure-.adoc[leveloffset=+1] -. Link to the Nth task to perform. +// include::reference-.adoc[leveloffset=+1] -.Related Information +== Additional Resources * Bulleted list of links to concepts, reference, or other tasks closely related to this user story. diff --git a/en-US/sysadmin_user_stories/assembly-verifying_file_permissions.adoc b/en-US/sysadmin_user_stories/assembly-verifying_file_permissions.adoc index 8c35ed2..c40725a 100644 --- a/en-US/sysadmin_user_stories/assembly-verifying_file_permissions.adoc +++ b/en-US/sysadmin_user_stories/assembly-verifying_file_permissions.adoc @@ -1,21 +1,9 @@ -// Include an 'ID' that corresponds to the title of the assembly -// The ID will be used as an anchor for linking to the title -// Do not change the ID to make sure existing links keep working -[#doing_several_tasks_in_sequence] -= Doing Several Tasks in Sequence +[#verifying-file-permissions] += Verifying File Permissions -_Start the title with a verb in the gerund form, such as Creating or Configuring._ +This section describes how you can verify what the permissions for a directory are file so that you can make sure which user or user group can access which files or directories. You can also verify what files or directories can you access. -// Ideally, base the name of the file on the title to avoid confusion -// Use a consistent system for filenames and IDs, e.g.: -// * Only substitute spaces with underscores -// * Don't use any CAPS - -_Use this template to document a user story -- any series of tasks that the user must perform in a specific order to accomplish something._ - -This paragraph explains what the user will accomplish by working through the tasks in sequence. It sets context or explains the benefit the user will gain by performing the tasks that comprise the story. May include more than 1 paragraph, and may include concept modules if needed to fully explain the context, benefits, and other things the user must understand to complete the tasks successfully. - -.Prerequisites +== Prerequisites * Sentence or a bulleted list of pre-requisites that must be in place or done before the user starts this task. @@ -23,19 +11,13 @@ This paragraph explains what the user will accomplish by working through the tas * Text can be a link to a pre-requisite task that the user must do before starting this task. -.Procedure - -_Can link to or include task modules, depending on the writer's choice based on information needs. If you link to task modules, add each link as 1 step in a numbered list. The order of included task modules or of the linked steps is important to a repeatable successful outcome. Following is an example of linking to task modules in numbered steps._ - -. Link to 1st task to perform. - -. Format the step line as an unnumbered bullet if the procedure includes only 1 step (exception to numbering the steps). +include::.procedure-navigating_to_a_file_or_a_directory.adoc[leveloffset=+1] -. Link to 3rd task to perform. +include::procedure-listing_files_in_a_directory.adoc[leveloffset=+1] -. Link to the Nth task to perform. +include::reference-permission_types.adoc[leveloffset=+1] -.Related Information +== Additional Resources * Bulleted list of links to concepts, reference, or other tasks closely related to this user story.