See a psychiatrist. You already have root on these systems… if you are truly a split personality then fences aren’t going to prevent your other self from doing whatever they want.

From the beginning of computing there has been a problem with bootstrapping knowledge… the person creating a tool gives it a name, and describes it, but knowing that someone solved the problem you have and what the name of that tool was always a challenge.

But that is nothing new… you posted in English but if you were to learn a different language you would have a very similar problem, and one of the most universal strategies for making that transition is to drill on vocabulary. Once you have built a small vocabulary then you can expand it using a dictionary.

The real message behind someone saying RTFM is that there are so many educational and search resources now that asking some rando on the Internet to rewrite a Howto on the fly is lazy. Simply typing the exact same question into Google will bring up a kickstarter set of vocabulary and resources. If you actually do this your question will often answer itself, and if it doesn’t and you start by pointing out why your efforts failed to help you with your specific problem and use the vocabulary (at least briefly) that your research turned up to guide the reader toward where your problem is, you should get less RTFM responses.

You must be off by a decade. Your reference mentions no OS and Unic was developed around 1970.

If you are invested in Windows software… don’t run Linux. Being able to run Windows software is like a “patch” to get you by until you find a Linux equivalent. Pretending you can have your cake and eat it too will just leave you disappointed.

Linux has amazing software… but in most cases it feels very different from Windows. If you learn why it is different then you may start to appreciate Linux for what it gives you rather than what it takes from you.

Boss has different people for different functions within the company. A monoculture is more susceptible to systematic flaws, but it is also less expensive to maintain. It is not OPs place to decide how the company manages is computing facilities, so if WSL or Cygwin are not accepable compromises (OP and company have to both agree) then OP has to decide whether they are willing to go along with Windows or find another job.

Something to talk about during the exit interview anyway.

Trying too hard to get a reaction by threatening to load Windows, the hardware hog? Way too low to even be believable.

First thing that comes to mind with a thrifted laptop is that you need to use an older distro compiled for 32bit cpu. But honestly, modern laptops are cheap and the overall experience regardless of OS is that very old hardware is going to look bad by comparison with anything on a store shelf so unless you are familiar with Linux already and committed to rehab old hardware (e.g. for standalone use) then it probably isn’t worth your time.

That is not an ideal experience. However, hardware gremlins are not a universal experience either.

Others have pointed out that getting a slightly older laptop to put Linux on can give the tinkerers time to get the key drivers working, and avoiding bleeding edge revisions of your distro can help.

It is quite possible that my comfortable experience with Mint and Ubuntu over the years have been influenced by my low expectations of getting all the bells and whistles working the way they would in Windows. I like the software environment that typically comes on Linux and I don’t stress when Windows software (esp games) doesn’t work (though Steam makes a lot of games work anyway).

I did have to spend more time getting the bios and fingerprint reader straightened out on my latest laptop (Dell Inspiron), but Google and blogs walked me through it and the only remaining problem is that sometimes when the fingerprint prompt times out I have to use the password until I reboot.

They are a record of the process of adding to the Linux kernel. Such background can be used to trace the history of contributions if those contributions turn out to have had malicious intent or were derived from code that came from sources that were not compatible with the GNU license that the kernel is released under.

It is not recursive though. A directory is a special kind of inode that enumerates file inode numbers and when that list changes then the contents of that “directory inode” change. But if /home/user/.bashrc is deleted then the timestamp for /home will not be affected because the timestamps are associated with inodes rather than directory entries (assuming no symbolic links are involved).

https://www.redhat.com/en/blog/inodes-linux-filesystem https://en.wikipedia.org/wiki/inode

Just to second that, the model series is Latitude, not Inspiron. and yeah, the i5 processor options I got over the years beat the i7 on processing power. The Precision models are a step up, but not any kind of low cost and seem not quite as tough.

Bash is always there, and bash scripts and snippets are precise. Describing gui manipulations when the GUI keeps changing is also quite hard… what if the person you are interacting with has a 2-yo system and you have the bleeding edge? Even knowing which menu the settings are in can be frustrating for the helper.

Windows users (e.g. me at work) get grumpy when Microsoft starts changing the menu structure after keeping it consistent for 20 years and start thinking of powershell scripts to create consistency between our engineering workstations.

They are text files. If there is anything weird about them it is that they are indented with spaces and if you are inconsistent with indentation they won’t read into the yaml import function, but I can’t imagine why vim or nano would have a problem with opening them. Maybe the ones you were using were not actually yaml.

Totally lost me. Why the hate on YAML?

I have only skimmed the surface of learning Rust, but I am wondering what it has over Ada. The memory safety features that Rust emphasizes have been standard there for 40 years, and just as unglamorous compared to C++.

I tend to focus on scripting nowadays… R and Pyrhon… with the odd C++ for high-speed algorithms because it is popular. But is Rust merely a new face on Ada?

When you come across some Python code for something written 5 years ago and they used four contributed packages that the programmers have changed the API on three times since then, you want to set up a virtual environment that contains those specific versions so you can at least see how it worked at that time. A small part of this headache comes from Python itself mutating, but the bulk of the problem is the imported user-contributed packages that multiply the functionality of Python.

To be sure, it would be nice if those programmers were all dedicated to updating their code, but with hundreds of thousands of packages that could be imported written by volunteers, you can’t afford to expect all of them them to stop innovating or even to continue maintaining past projects for your benefit.

If you have the itch to fix something old so it works in the latest versions of everything, you have that option… but it is really hard to do that if you cannot see it working as it was designed to work when it was built.

Using sudo when it isn’t necessary, and the real cannon: sudo su… Adding sudo to your command lines indiscriminately causes files you create to be owned by root even though they are in your home directory, and then you end up using sudo to make changes to the files… and then the filesystem permissions cannot prevent you from successfully running an accidental “sudo rm -rf /” command.

Seriously… sudo is not a “habit” to develop in order to avoid dealing with filesystem permissions problems.

Noob question?

You do seem confused though… Debian is both a distribution and a packaging system… the Debian Stable distribution takes a very conservative approach to updating packages, while Debian Sid (unstable) is more up-to-date while being more likely to break. While individual packages may be more stable when fully-updated, other packages that depend on them generally lag and “break” as they need updating to be able to adapt to underlying changes.

But the whole reason debian-based distros exist is because some people think they can strike a better balance between newness and stability. But it turns out that there is no optimal balance that satifies everyone.

Mint is a fine distro… but if you don’t like it, that is fine for you too. The only objection I have to your objection is that you seem to be throwing the baby out with the bathwater… the debian packaging system is very robust and is not intrinsically unlikely to be updated.

Did you check ownership and permissions for .profile?