(I’ll have to go back and read this thread after posing this - 83 is a lot)
For decades now I have been downloading various “stuff”, and early on I got in the habit of recoding a url.txt
with them, or a urls.txt
if there were multiple sites associated with it, adding see: ../some/other/related/folder
as need.
About a month ago I started (alt-dir
) adding the files .alt
(with descriptive one-liners) and .description
(with multi-line descriptions) into interesting folders, that a shell command can process: als
or dls
. With dls
I can also put all subtree .alt
and .description
files in a seperated tree mirrored .dir
folder, in which nothing is hidden, so its easy to edit, and you can see whats not documented yet (useful for repository parents, or seperating generic info /.dir/
, or syncing info seperate from current filesystem).
Even tho they are unstructered text (not format, except 80 wrap if time allows), the commands can render inline $(shell command)
and ${VAR}
at runtime, including color, bold, underline etc if I choose (useful in /home/.description
for current user name, and in /
root to show the actual “root filesystem device”).
BTW I created alt-dir
to help give “unpolluted” FileSystem feedback (because they are hidden .dot files) for a “L1Techs-Devember” filesystem catalog.
As an example, I can put a .dir/
folder in the parent of my serenity
repo, and add issues and comments, descriptions, or observations into the seperated tree mirror (keeping the repo free of non-source files), and generate some of that content at dls
run-time dynamically from the GitHub repo Issues or Pull Requests (which are not part of a Git repo). There is also no reason I could not add a .todo
file to that OR even re-use the .dir/
structure as TODO only usage.
while creating /.dir/
I decided to add .history
files for more extensive reading and creating inline archeological records that could be used in “a living OS” (like the origins of /sbin
, /usr
and /home
, and the historical usage of /usr/local
- basically all the extra stuff you wont find in the man pages)
Cheers
Paul
EDIT: example (and every file/folder name is output ls --color=always
at the terminal):
/ - the ROOT directory
This is the ROOT of the filesystem, everything else is mounted somewhere
inside this filesystem tree.
$ lsblk -l | grep "/$"
mmcblk0p2 179:2 0 96.7G 0 part /
------------------------------------------------------------------------
bin ROOT CLI Binary folder soft-link /bin -> usr/bin
boot (no alt-dir info)
dev (no alt-dir info)
etc (no alt-dir info)
home (no alt-dir info)
iozone (no alt-dir info)
lib ROOT Library soft-link /bin -> usr/bin
lost+found (no alt-dir info)
media (no alt-dir info)
mnt (no alt-dir info)
opt (no alt-dir info)
proc (no alt-dir info)
root (no alt-dir info)
run (no alt-dir info)
sbin ROOT System Binary folder soft-link /bin -> usr/bin
share (no alt-dir info)
srv (no alt-dir info)
sys (no alt-dir info)
tmp (no alt-dir info)
usr (no alt-dir info)
var (no alt-dir info)
pi@raspberrypi:/ $