Wait, TPM, you have ADHD?
Sure do - card carrying member since diagnosed in college back in the 00’s.
Mate, you’re in every lemmy community. Don’t tell me you have autism too
Lol, sorry to disappoint, but no I don’t.
I also don’t use Linux. (Well, that’s not totally true now, because I’ve been learning to use for a hobby project lately).
I can teach you some Linux!
I’d welcome any beginner tips you have!
I have Linux installed on a raspberry pi, using “Pi OS”, which I understand to be some form of Debian? I’ve learned enough to comfortably SSH into it and navigate around my file system, as well as write some really basic Python programs for the pi using nano.
I’ve only been at it casually for a few weeks, so that’s about the extent of my knowledge.
Yup, Pi OS is Debian with a few custom configs and (I think) the pixel desktop environment (though they might have changed it to Wayfire).
Btw, in Linux, everything is a file. Some are in /sys and /proc for the kernel, others in /dev for devices. So you can do neat stuff like changing your backlight by printing a number to a special file!
Also, commands have 3 streams: stdin (standard input, usually keyboard), stdout (standard output, usually terminal), and stderr (standard error, output, almost always terminal). You can often pipe programs, so one’s stdout goes to another’s stdin. Stderr is used for human-readable errors and is usually not piped.
Combining the last 2 things, if you pipe a program into /dev/null (which is like an infinite void or a trashcan), it’s like ignoring its output.
Btw, in Linux, everything is a file.
This sounds cool. Do I also understand right that file extensions aren’t anything more than the file name?
I can also conceptually appreciate the input/output/error piece, although I bet it’ll make more sense when I find a use case for it eventually. Thanks!
