Why do I get these errors on "apt upgrade"?

You asked this same questions 7 months ago:

https://www.linode.com/community/questions/21805/what-are-these-errors-on-apt-upgrade

Asked & answered.

-- sw

I think the answer might be here. Can anyone validate?

https://www.manniwood.com/2021_11_07/set_the_resume_variable_to_override_this.html

Looks like the answer to me…

FWIW, what the link you cited asks you to do doesn't modify your system in any way…until the next kernel upgrade (which is what apt upgrade is complaining about).

Then, again, I don't use Ubuntu…or Linux…anymore…

-- sw

@acanton77 if you're using Linode Backups on your Linode, you may not want to set that workaround as restoring from a backup will result in a different UUID for your disks which may cause issues booting up after a restore.

FWIW, those errors are pretty harmless in my experience so it might be easier to leave your system as is in this case but that's entirely up to you.

sw wrote:

Then, again, I don't use Ubuntu…or Linux…anymore…

What are you running? FreeBSD?

What are you running? FreeBSD?

Yep. I do my own backups to a block storage drive. Works great.

I've only had one problem with it…an obscure problem with my (SLAAC-allocated) IPv6 address "expiring" periodically (kinda like a DHCP lease expiration). I solved it by starting rtsold (router solicitation daemon) at boot time.

-- sw

I ran FreeBSD for15 years on a dedicated server, but it was managed through Pair Networks so I didn't have to do any system work.

I never had a problem with it… so long as I ran the bash shell and not the csh shell… which I never did figure out!

I don't know why FreeBSD is not a Linode option….

https://www.linode.com/docs/guides/choosing-a-distribution/

…. instead of having to go through this ordeal:

https://www.linode.com/docs/guides/install-a-custom-distribution-on-a-linode/

I'm told there has been some attrition in the FreeBSD community such that packages (ports/binaries) have been slower to be released than a few years ago… but this is just what I've heard… don't know the veracity of it.

I guess the question most people would have is "Why FreeBSD over Linux?"

For me, FreeBSD is a 'real' self-contained operating system… not a small kernel with a ton of 3rd party stuff bolted on to it to make it work… as is Linux.

If I had the time and the technical 'chops' I'll run FreeBSD like you.

I never had a problem with it… so long as I ran the bash shell and not the csh shell… which I never did figure out!

HP-UX had the csh shell… Back in the dark ages, it was the preferred option among the cognoscenti over the original (circa 1970s) Bourne shell. I learned it early on (this was pre-ksh in the early 1980s).

I use GNU bash, version 5.1.16(0)-release…

I don't know why FreeBSD is not a Linode option….
 
https://www.linode.com/docs/guides/choosing-a-distribution/

Nor do I… Almost all of Linode's competitors offer FreeBSD (believe me…I checked them all out after I heard about the acquisition by Akamai).

instead of having to go through this ordeal:
 
https://www.linode.com/docs/guides/install-a-custom-distribution-on-a-linode/

Yep…although it's not as bad as it seems…

I'm told there has been some attrition in the FreeBSD community such that packages (ports/binaries) have been slower to be released than a few years ago… but this is just what I've heard… don't know the veracity of it.

I would have to say that this is mostly not true… It may have been true once, but it's not my experience that what you describe is no longer the case.

The distribution model is different. Packages are basically distributed as source (there's a co-channel that distributes stuff as binaries and it is definitely slower) but the source distributions are, for the most part, current with the Linux distributions.

When you install packages by compiling source, you better be f****ng sure that it compiles and works. That puts extra overhead on the distributor to compile/test the package on FreeBSD (the emphasis on test is intentional). Mostly, things work out of the box on FreeBSD…no weird, obscure configuration BS that you have to search the interwebs far and wide for like on Linux…

I guess the question most people would have is "Why FreeBSD over Linux?"

It's better-engineered, more secure and isn't under the thumb of a sociopathic control freak with (severe) anger issues.

For me, FreeBSD is a 'real' self-contained operating system… not a small kernel with a ton of 3rd party stuff bolted on to it to make it work… as is Linux.

More accurately, it's a development environment -- kernel (which you can modify), compiler, linker, etc (which are all light years ahead of gcc in terms of performance -- both in terms of compile speed and code generated). For example, the kernel I build that is specific to Linode is 20Mb smaller than the GENERIC kernel (the kernel that boots on all supported platforms). Some of that is due to the compiler (no kernel debug) and some of it is due to configuration (you don't need bluetooth drivers on a VM, etc).

FreeBSD just works. Things are installed in rational places. Security is engineered in and not an afterthought (try doing hardware crypto on Linux without major psychic pain!).

If I had the time and the technical 'chops' I'll run FreeBSD like you.

Just take the plunge… About the biggest impact is that stuff you install ends up in /usr/local/<etc,lib,bin> instead of /etc and /usr/<lib,bin>. Dealing with ports system doesn't have any of the pitfalls you describe above.

ZFS is a dream… My backup partition is on a RAID-5 drive in block storage (which Linode guarantees is triple-redundant) that I was able to create in about 5 minutes.

-- sw

I have an account with D.O and so I think I'll spin up a small FreeBSD server with them today and see how long it takes me to crash it!!!

I hope there are some docs on how to install the LAMP stuff and create a virtual host for Apache (probably similar to Linux.) I'll put up a test domain I have laying around.

Should I use UFS or ZFS?

I've never compiled ports. Binaries are easier and faster. Is there an "apt update / upgrade" function in FreeBSD to find out what needs to be replaced?

I've read the FreeBSD "handbook." It makes an Arch Linux installation look like a walk in the park! :-)

I checked them all out after I heard about the acquisition by Akamai).

Why don't you run with D.O. instead of Linode and avoid the arcane Linode install procedure with FreeBSD?

I hope there are some docs on how to install the LAMP stuff and create a virtual host for Apache (probably similar to Linux.) I'll put up a test domain I have laying around.

LAMP runs the same as it does on Linux so so setting up a virtual host is the same as it is on Linux.

Should I use UFS or ZFS?

ZFS… definitely!

I've never compiled ports. Binaries are easier and faster. Is there an "apt update / upgrade" function in FreeBSD to find out what needs to be replaced?

There are 2 ways to install ports:

• as binaries using pkg install <portname> or
• build from source by doing

cd /usr/ports/<section>  # <-- mail, database, security, www, etc.
cd <port>              # <-- apache24, php81, postfix, etc.
sudo make config       # <-- configures the port...optional
sudo make              # <-- downloads the port source and builds it
sudo make install      # <-- installs the port
sudo make clean        # <-- removes the artifacts from the build

The last 4 steps can be abbreviated: sudo make config install clean

The binaries in the pkg system are created this way so installing from the pkg repository and building/installing the port yourself are essentially the same thing. Most "common" stuff is available in pkg (e.g., apache24, php81, mysql -- the stuff you'll need for LAMP).

One reason you might build a port is to configure it differently than the pkg binaries are configured. For example, the pkg binaries for postfix don't compile in sqlite3 support. I need that…so I build postfix from the port so I can configure it with sqlite3 support.

Another reason would be that the port might not be available in pkg. Most of the common stuff is already in pkg but some of the more obscure stuff is not.

To upgrade all your installed pkgs, you enter sudo pkg upgrade. To update your ports tree, you enter sudo portsnap fetch update. To upgrade all your installed ports, you enter sudo portmaster -af (add -n for a dry-run…you install portmaster as a binary with pkg).

I have very few things installed from ports…almost everything is installed from pkg.

In FreeBSD, the command is ps -ax…not ps -ef. ps -ef works but it doesn't show you what you think you ought to see…

I've read the FreeBSD "handbook." It makes an Arch Linux installation look like a walk in the park! :-)

The FreeBSD Handbook is not a step-by-step, "how-to" guide. It's a reference manual.

Why don't you run with D.O. instead of Linode and avoid the arcane Linode install procedure with FreeBSD?

DO is home to lots of spammers and script kiddies whose sole purpose in life is to cause others pain. Supposedly, there are rules but it seems there is virtually no enforcement.

-- sw

DO is home to lots of spammers and script kiddies whose sole purpose in life is to cause others pain.

People say the same thing about AWS, Linode, Vultr, etc.

Thanks for the info on FreeBSD. I'm going to set up a small server on D.O. and see how it works. If I like it (i.e. I don't screw it up) maybe I'll try doing the same on Linode… which is way more difficult… or so it seems.

I am kind of amazed that FreeBSD is not a Linode choice. Maybe there is just no demand for it?

I'm going to set up a small server on D.O. and see how it works.

You'll probably have to upgrade it to the current version of FreeBSD (13.0-p10) once you get it set up. This is easily accomplished with freebsd-update… Also, to get the leanest/meanest kernel for your VM, you'll have to build a custom kernel. The GENERIC kernel is horribly bloated with every driver known to man. However, it's the one you want to use for bring-up and rescue operations so you should keep a copy of it around.

If I like it (i.e. I don't screw it up) maybe I'll try doing the same on Linode… which is way more difficult… or so it seems.

It's not hard if you follow the directions exactly.

I am kind of amazed that FreeBSD is not a Linode choice. Maybe there is just no demand for it?

All of the Linode infrastructure (API, backups, snapshots, images, etc) is built around Linux with ext filesystems. It would be a monster of a task to enhance all that for zfs/ufs. Maybe an upside of the Akamai acquisition is that Linode will get on the ball with it…

I was hoping that OpenZFS would have taken more hold in the Linux world by now but the control freak with anger issues has a severe case of NIH with respect to it…

-- sw

I looked at the FreeBSD docs on D.O. and they were rather sketchy compared to the quality and completeness of those on Linux.****

I'll see if I can find a video or a website with a step-by-step tutorial on bringing up and locking down a FreeBSD instance on D.O. or a cloud platform who will support it. Linode is obviously not the right venue for this.

All in all, this is just for fun. At the end of the day,to just run a dozen or so low-volume websites, Ubuntu is fine.

Sometimes "good enough" is good enough :-)

**** The docs for Linux on D.O. pale in comparison to those on Linode. Warts and all, Linode is a better choice for those (of us) who need a bit more in the way of documentation hand-holding.

Ubuntu is fine.

Except for systemd/systemctl…a horribly bloated solution looking for a problem…

-- sw

First, full disclosure: I stopped reading around the time that the convo switched to "BSD isn't like Linux … Just a kernel with a bunch of 3rd party …" So the question may already be resolved.

I found in the Ubuntu forums that you should be able to simply uninstall cryptsetup, since you don't use encrypted drives.
Make sure to update grub afterwards, and generate a new initramfs before reboot.

Reference: https://askubuntu.com/questions/316486/problems-with-cryptsetup-during-update