Before that there was STFU and sit still. Sadly, this was the era in which I was raised.

Any flavor of vi, Gnu Screen, lrzsz, bash with the usual cli tools (awk, sed, grep, tail, head, rev, cat, tac, and recently jq and yq). Also openssh client. Some flavor of netcat is also crazy useful too. This is a good home for me to do my thing.

Edir: oh, and git. How did I forget git?!

cpio is way worse

Compiler error: missing ‘)’

Adding Bluetooth to a vacuum cleaner does make it suck more.

To this day I still don’t upgrade OSes in general and I even evangelize “rip and replace” professionally so loudly that it’s now enforced via policy at my workplace. This must be where my ethos for this practice originated.

I think it was SLS. I know it took a pile of floppies. At some point I made a tape to make it easier to install. Why I needed to install that often eludes my aging memory but those experiences still pay to this day.

Raise hell, praise Dale!

I don’t see it.

It’s all skippable if you want… Just put a large / filesystem on a partition and be on your way. There are good reasons for using it in some cases (see my response now).

I should also point out that some modern filesystems like btrfs and zfs have these capabilities built into the filesystems natively so adding LVM into the mix there wouldn’t add anything and could, in fact, cause headaches.

In practice, you would split a disk up to keep /home separate from/ and probably other parts of the filesystem too like /var/log… this has long been an accepted practice to keep a full disk from bringing something production offline completely and/or complicating the recovery process. Now, you could use partitions but once those are set, it’s hard to rearrange them without dumping all the data and restoring it under the new tables. LVM stands for Logical Volume Manager and puts an abstraction layer between the filesystems and the partitions (or whole disk if you are into that). This means you can add Disks arbitrarily in the future and add parts of those disks to the filesystems as required. This can really minimize or even eliminate downtime when you have a filesystem getting filled up and there’s nothing you can easily remove (like a database).

It’s good to know but with the proliferation of cloud and virtual disks it’s just easier on those systems to leave off LVM and just keep the filesystems on their own virtual disks and grow the disk as required. It is invaluable when running important production systems on bare metal servers even today.

Hope this helps.

Terraform… Oh wait, Nevermind. I need to start switching to OpenTofu now.

Ext4 is the safe bet for a beginner. The real question is with or without LVM. Generally I would say with but that abstraction layer between the filesystem and disk can really be confusing if you’ve never dealt with it before. A total beginner should probably go ext4 without LVM and then play around in a VM with the various options to become informed enough to do something less vanilla.

Terminal plus Gnu Screen plus vim makes the BEST IDE /for me/.

Who dis?

A haunted House meets a corn maze. I love it!

As with all tech; it depends. It’s another tool in my toolbox and a useful one at that. Will it replace me in my job? Not anytime soon. However, it will make me more proficient at my job and my 30+ years of experience will keep its bad ideas out of production. If my bosses decide tomorrow that I can be replaced with AI in the current state, they deserve what they have coming. That said, they are willing to pay for additional tooling provided me with multiple AI engines and I can’t be more thrilled. I’d rather give AI a simple task to do the busy work than work with overseas developers that get it wrong time and time again and take a week to iterate while asking how for loops work in Python.