On 2024-10-07 18:36, -pj via openSUSE Users wrote:
On 10-07-2024 04:12AM, Bengt Gördén wrote:
On 2024-10-07 04:09, -pj via openSUSE Users wrote:
What is \ above for above? How to look up a man-page for \ what's it under?
Since we are using a shell, you should look up _your_ shell. Probably bash.
man bash
"A non‐quoted backslash (\) is the escape character. It preserves the literal value of the next character that follows, with the exception of <newline>. If a \<newline> pair appears, and the backslash is not itself quoted, the \<newline> is treated as a line continuation (that is, it is removed from the input stream and effectively ignored)."
PS. A bit of caution here. Treading into the realm of line breakers and how to interpret them will keep you up at night for the foreseeable future. It is a Sisyphus task.
Good of you to share and respond. I saw Carlos' example > mkfs.f2fs -l WORLDWIDE-FSF2 -i -f -O \ extra_attr,inode_checksum,sb_checksum /dev/mapper/cr_name
Command differs from Arch Wiki Page example of
mkfs.f2fs -l mylabel -i -O extra_attr,inode_checksum,sb_checksum /dev/sdxY
Because you want it encrypted. It is not "/dev/sdxY" but "/dev/mapper/cr_something" if you want to use LUKS. That's the only important part of my example, the device. The rest is up to you.
in reference to the \
The "\" is not part of any man page like that. It simply means that the line continues below, that it is not two lines. At least while using bash.
With FSF2 a, '-f' flag..is that the correct term? Seems to be also necessary, Arch Wiki do not show that in the example. And was curious about the '\' now I see it's a bash and not a F2FS filesystem flag. Why is it helpful/important "to preserve the literal value of the next character that follows in this case?
Thanks🙂
a long line ending in \x is not a continuation. The x, or an space, or any character, visible or not, breaks the continuation. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)