genfstab: add page

[peterbabic]

• The page (if new), does not already exist in the repo.
• The page is in the correct platform directory (common/, linux/, etc.)
• The page has 8 or fewer examples.
• The PR title conforms to the recommended templates.
• The page follows the content guidelines.
• The page description includes a link to documentation or a homepage (if applicable).

[CLAassistant]

All committers have signed the CLA.

[tldr-bot]

The build for this PR failed with the following error(s):

Error: Parse error on line 4:
...ripts/genfstab.8.en>- Generate the out
-----------------------^
Expecting 'END_INFORMATION_LINK_URL', got 'NEWLINE'
pages/linux/genfstab.md:4: TLDR011 Page never contains more than a single empty line

Please fix the error(s) and push again.

[tldr-bot]

The build for this PR failed with the following error(s):

pages/linux/genfstab.md:6: TLDR005 Example descriptions should end in a colon with no trailing characters
pages/linux/genfstab.md:10: TLDR005 Example descriptions should end in a colon with no trailing characters
pages/linux/genfstab.md:14: TLDR005 Example descriptions should end in a colon with no trailing characters
pages/linux/genfstab.md:18: TLDR005 Example descriptions should end in a colon with no trailing characters

Please fix the error(s) and push again.

[peterbabic]

add maintainer suggestions

EDIT: do not know what to do, still reluctantly learning Github
EDIT2: somehow added maintainer suggestions into "batch" and committed them, hopefully this was expected

[bl-ue]

Hi @peterbabic, thank you for the new page! I've left some comments below for you to review.

[peterbabic]

Unfortunately I do not agree wit any of the changes @bl-ue suggested, not meaning to be rude by any way. I have provided explanations to all of them.

[bl-ue]

@peterbabic no problem! Sometimes we have difficulty communicating through a purely textual medium :) I've responded to your comments.

[peterbabic]

@bl-ue no poblem as well! Thanks for suggestions. Did not know about the nature of "an ef-es-tab file" 😄

[bl-ue]

Okay, thanks for the help @navarroaxel. @peterbabic I have only two more comments.

[peterbabic]

I have added another commit where I believe the changes are the most consistent. I have also removed backticks around fstab as it is word, not a code nor a path.

[peterbabic]

Maybe the last thing I would check is if volume is the right word, as filesystem, block device, disk, partition or disk partition would all suit as well depending on use case.

I would keep volume there.

[bl-ue]

@peterbabic - Looks good to me, except the sentence "A usual way to generate an fstab file, requires root permissions:" is a little inconsistent with the rest of our pages. If that is the most common example, then I think you should:

1. Move the example to the top, so it's what the user sees first, and
2. Change the example description to "Generate an fstab file (requires root permissions):"

[sbrl]

Looks pretty much good to go to me - I think we can probably merge this.

I've left a comment on the requires root permissions issue, but that doesn't necessarily need to block the merge of this PR - and I can see some significant discussion has already happened - so I'm leaning on the side of getting this merged sooner rather than later.

[bl-ue]

@sbrl that was actually already resolved :) - #5215 (comment)

[bl-ue]

Thank you @peterbabic, and welcome to tldr-pages!

[sbrl]

Ok, whatever was done there is fine then :-)

[bl-ue]

We picked not to use sudo because that command is normally run in a boot environment where tee may not be available.