Skip to main content

When will Ubuntu clean up after updates?

It may be unfair to single-out Ubuntu in this issue, since it may also be an issue with other distributions as well.  Regardless, it is 2016 and it seems noteworthy that the annoying "Not enough free disk space" error during regular updates is still a thing.

In the faint chance that there are those who are unaware of this scenario, this is it.  The Software Updater application gathers the next round of updates.  Upon application, the following error message is encountered.

The error suggests running apt-get clean to resolve the issue.

The error suggests running the clean option against the apt-get command, which seems to be something of a red herring, as it does nothing.  Instead, the following will take care of things.

From the command line:
dpkg --get-selections | grep linux-image
This will list all the current kernels that are hogging up the /boot directory.

Run the following to remove unused kernel packages.
sudo apt-get purge UNUSED-KERNEL
There are two things to note:
  1. The UNUSED-KERNEL note will need to be replaced with the actual name of older kernels that should be removed.
  2. Do not remove linux-image-generic.
The full text of the error message is:
The upgrade needs a total of 109 M free space on disk '/boot'. Please free at least an additional 51.6 M of disk space on '/boot'. Empty your trash and remove temporary packages of former installations using 'sudo apt-get clean'
Note that the actual file sizes will vary by system and installation parameters.

The truth of the matter, is that the solution to the problem is not difficult.  It is however frustrating that the situation isn't handled automatically during the update process.  Little fit-and-finish items like this are the rough edges that Linux distributions still snag users from time-to-time.

Comments

Post a Comment

Popular posts from this blog

Remove control of Chrome being managed by organization on personal devices

Chrome may indicate that it's being managed by a user's organization. This warning is provided by the Chrome Policies feature of the browser. To know if an instance of Chrome is managed by an organization, there will be an entry at the bottom of the browser’s hamburger menu (three dot menu), on the right side of the browser window that reads, "Managed by your organization." This is likely due to an entry in the Chrome Policies listing, which can be found by loading this page in the browser: chrome://policy The policies listed in this section are stored in the computer's file system in one of the following locations as JSON files. /usr/share/chromium/policies/managed /usr/share/chromium/policies/recommended Remove the offending JSON files, and click the Reload policies button. The Managed by your organization entry in the browser menu should be gone. A notice like this on instances of Chrome for work, school, library, or other devices that belong to an organizati...
Post a Comment
Read more

Allow Windows authentication using SQL Server driver with DBeaver

DBeaver will allow Microsoft Windows single sign on access when connecting to Microsoft SQL Server using the SQL Server driver (rather than jTDS ).  From the driver properties settings, set the integratedSecurity flag to true . Open the Connection configuration panel and choose the Driver properties section. Set the integratedSecurity flag to true . A subtle, but important step is to not provide username and password credentials to the connection.
7 comments
Read more

Connecting to SQL Server with jTDS using Windows Authentication

UPDATE:   At one point the tip in this article to set the USENTLV2 flag to true was accurate, but it appears it is no longer necessary, at least as far as DBeaver 's use of the driver is concerned.  If it solves an authentication problem, then great.  The expectation is that, an update in one of the packages that make this sort of connection possible has resolved the issue that at one time made this flag necessary. Connecting to Microsoft SQL Server using jTDS with a username and password that's managed by the database manager is pretty straightforward.  It may become a little more problematic however, when trying to use Windows authentication when connecting from a Windows machine. Do not supply a username and password. Set the USENTLMV2 property to true. NOTE:   Step 1 assumes a connection being made from a Windows machine.  If the connection is being made from something else, user credentials may actually be necessary. If the connect...
7 comments
Read more