‘sort’ produces output in a weird order
Consider the following input to sort:
coreutils
uname -p -i are unknown
Why does this happen? Everything else printable with uname is shown.
I am not looking into fixing this. Even the manual page of uname says that it’s a common output.
Trailing slashes on symbolic links to directories
I’m trying to emulate the process of path resolution (see man page path_resolution) in unix-like systems.
Why do I have “join: extra operand ‘/dev/fd/62′” error?
I have a script equijoin2:
How does the “1 month ago” option in date command work?
I’m not sure if this gets the past date within the current day or if it only takes 30 or 31 days to it.
Why is cp –reflink=auto not the default behaviour?
Why is cp --reflink=auto not the default behaviour? Could it cause any harm to enable it?
How is the order in which tar works on files determined?
$ touch dir/{{1..8},{a..p}} $ tar cJvf file.tar.xz dir/ dir/ dir/o dir/k dir/b dir/3 dir/1 dir/i dir/7 dir/4 dir/e dir/a dir/g dir/2 dir/d dir/5 dir/8 dir/c dir/n dir/f dir/h dir/6 dir/l dir/m dir/j dir/p I would have expected it to be alphabetical. But apparently it’s not. What’s the formula, here? Answers: Thank you for visiting the … Read more
What is the added value of the -T option in GNU cp and mv?
Why do some GNU Coreutils commands have the -T/--no-target-directory option? It seems like everything that it does can be achieved using the semantics of the . (self dot) in a traditional Unix directory hierarchy.