Start with the man pages. Running the command man followed by a space and then followed by the command you’re using will almost always give you a man page of the basics of how that command works. The fstab has its own man page too. An internet search “man fstab” or whatever command you’re interested in should also net many mirrors of the those man pages as well.

For me at least, it’s not that you’re asking questions. I answered, so obviously I’m sympathetic to confusion in this area. I’m just trying to encourage you to seek your answers in the documentation and manuals FIRST. The way your question was worded led me to believe that you had not read the manuals at all and were simply copying snippets of code and commands from some random question and answer style forum that did not teach you anything about the fundamentals of what those commands and code actually did. That’s fine too, lots of people started off that way, myself included. Reading the manuals gives you the context to step back and understand how those commands work and what they’re really doing. If you do, you’ll be much better able to troubleshoot your own problems, you’ll be able to ask better questions in forums like this, and you’ll get better and more useful responses.

With all due respect, RTFM. Mount and umount are two sides of the same operational coin. You mount the drive to use it and unmount it when you’re done. fstab is just a file system table used to remember and consistently apply the options used whether you’re mounting the drives manually or telling the system to do it at boot.

Deleting a line from fstab is not the same as unmounting, it is just a shortcut to tell the system how you want that drive mounted when you or the system run the mount command. Mount directories (usually the folders in /media/ or /mnt/ ) also do not get automatically deleted just because you “yanked the drive”. Again, those directories are just where your system is expecting to mount the drive. When the drive is mounted they will be the root path to its contents, when the drive is unmounted they will be empty but they still exist. If your planning on mounting the drive again leave them there. If you’re not planning on mounting them again, delete them.

If you’re not planning on regularly mounting a particular drive, it probably shouldn’t be listed in fstab and you should just run the mount command with the appropriate options (again fstab is just a table for remembering those options for the mount command).

Many desktop Linux distros are also capable of automatically mounting new removable drives in such a way that the user can access them and doesn’t have to worry about touching fstab or the mount directories.

I did say fancy.

Aren’t sqilte files themselves (like most other things) just fancy text files?

Blocklists are ineffective by design. Each and every member of the swarm can collect all the data necessary to flag you to your ISP. Obviously any professional collecting this kind of data can avoid a blocklist. There is no such thing as a better blocklist.

Teach us then 😭

I think this hits on another big generational difference. Those who grew up in the early days of personal computing and the Internet didn’t have teachers or a hallucinating language model to spoon feed them instant answers. They had to actually RTFM thoroughly before they could even think of asking in some arcane BBS, forum, or IRC for help from elders that had absolutely zero tolerance for incompetence or ignorance. MAN pages and help files came bundled, but the Internet (if you had it) was metered and inconvenient on a scale more like going to the library than ordering a pizza. They had to figure out how to ask the right questions. They had to figure out how to find their own answers. The Internet was so slow that all the really interesting bits were often just text. So much indexed and categorized one might need to learn a little more just to find the right details in that sea of text. There was a lot less instant gratification and no one expected to be able to solve their problems just by asking for help.

I’ve seen way too many kids give up at the first pebble in their path because they are so accustomed to the instant gratification that has pervaded our culture since the dawn of smart phones.

A decade ago we figured out blacklists were ineffective. What’s changed?

You could proyget pretty good bandwidth with a tube full of portable digital storage. Latency will suck though.

Most papers are made in TEX or LaTEX. These formats separate display from data in such a way that they can be quickly formatted to a variety of page size, margins, text size, et al with minimal effort. It’s basically an open standard typesetting format. You can create and edit TEX in any text editor and run it through a program to prepare it for print or viewing. Nothing else can handle math formulas, tables, charts, etc with the same elegance. If you’ve ever struggled to write a math paper in Microsoft word, seriously question why your professor hasn’t already forced you to learn about LaTEX.

From the article it does seem that the failure of ability isn’t strictly related to computers per SE, but to an over all inability to think about the word problems given in an abstract and mathematically coherent way. They seemed to ask participants to solve what are essentially database query, reading comprehension, critical thinking, and logic problems in the context of an email suite. Word problems can be hard for anyone that hasn’t studied and practiced how to decipher them. It’s just that using a computer kind of forces one to confront those gaps in what should be a fundamental part of highschool education. Math and science classes aren’t just solving problems by wrote memorization or memorizing the periodic table, they are about problem solving. Lots of people fall through the gaps and don’t get that one special teacher who understood this.

I wonder whatever happened to Knoppix. All I’ve been able to find online is speculation and questions.

Lars ruined Napster. BitTorrent came around some time later after Limewire, Soulseek, and DirectConnect. Lars might have had something to say about Bit Torrent, but by that point no one was listening.

Besides, back then, we really were using BitTorrent mostly for Linux ISOs. At the time it was more reliable than http. It really sucked having to download an entire ISO again because it failed the checksum. BitTorrent alleviated that.

This is gonna sound odd, but have you cleaned out the USB port lately? Weird stuff happens when pocket lint collects in there. I thought mine had a dead port until I picked out (with a non-conductive toothpick) the lint I didn’t realize had accumulated.

The amount of downvotes on this comment is a symptom of how toxic this community has become.

Not being able to identify a railroad crossing without a gate is a failing of the car not the train. Gated crossings are not guaranteed, nor should they be because they don’t make sense for every situation in which roads and tracks cross.

Don’t eat the onion.

Like every system? What’s the actual distinction you’re trying to point out?

I think the more nuanced take is that we should be making “piracy” legal by expanding and protecting fair use and rights to make personal copies. There are lots of things that are called piracy now that really shouldn’t be. Making “piracy” legal still leaves plenty of room for artists to get paid.

Docker compose is just a setting file for a container. It’s the same advantage you get using an ssh config file instead of typing out and specifying a user, IP, port, and private key to use each time. What’s the advantage to putting all my containers into one compose file? It’s not like I’m running docker commands from the terminal manually to start and stop them unless something goes wrong, I let systemd handle that. And I’d much rather the systemd be able to individually start, stop, and monitor individual containers rather than have to bring them all down if one fails.