1)

When and when not is it needed to make a section or segment readable?
In one of the example in the "fasm" none of sections readable:




2) Does the order of sections/segments matter?


Any difference between this one and the original example?

1) The OS probably gives all sections the readable attribute even if you don't specify it, but this is only my guess. You will need to check the docs to see what Linux does here. Usually only executable sections make sense to be non-readable and non-writeable.

2) The order does not matter, You can put things in any order you want.

The sections in ELF format do not have an attribute that would mean "readable". Only the run-time segments have, but they are a different entity (defined in "Program Header").

Actually, Linux set all segments readable and executable by default, even if the segment is neither readable, writeable nor executable, as long as your executable file does not contain a gnu-stack-segment. So if you create a executable file, please use »segment gnustack«, if you create an object-file, please link everything with »ld -z noexecstack«. Anyway, afaik everything is readable, even if you did not actually set this flag.

Afaik there where some linux-versions, where the last segment must be writeable (I guess, it had something to do with the stack, that should be, of course, writeable), but I do not know, whether this is true for section or not.