Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 2
    Welcome to the site. Please edit your post to indicate what you already tried and where you ran into problems. That way contributors can understand what tools you have available/are familiar with, and you can avoid receiving proposed solutions that you already know won't work. Commented Jul 7, 2021 at 10:50
  • Normally, I do indicate what I tried before. But in this case my intentions exceed my very basic knowledge at several points, especially what concerns the aspect to bring the potential solutions for each single problem together. Therefore, indicating my aproaches would end in a non-comprehensive patchwork. What I do not understand is why you miss a description, where I 'run into problems'. My problems are listed in the middle part of the post (points a to e)!? Commented Jul 7, 2021 at 12:12
  • What I meant with "where you run into problems" refers to the request to show what you already tried. Usually, contributors on this site expect askers to present a concrete question where they need help in solving an error condition, or where an approach expected to work turned out not to (e.g. "I used this command/script to do task XX, but instead of the expected output I got this"). Your points (a) to (e) are challenges to overcome while developing the script, but not "problems" in the sense of a script not doing what it is supposed to do. Commented Jul 7, 2021 at 14:01