![]() ![]() Worst can happen with C libraries or different GCC versions using different ABIs, or But this is hard to do, and error prone at times. This is generally handledĬorrectly by apt-get dependencies, assuming the maintainer did a really good job Them will either need to be upgraded, or their icons break. ![]() Now, in the new icons package, some old icons have been removed. ThisĬool and new application depends on the latest icons, which apt also correctly installs. Why is this a problem? Well, it all has toĭo with dependencies, backward compatibility and the fact that they may not alwaysįor example: let's say you install a cool new gnome application from unstable. Packages by defautl, but allow you to do a manual override to install from "testing"īefore starting, it's worth noting that this might not be for the faint of hearts: mixing and matching debian releases For example, you can configure apt-get to install "stable" Release of Debian, which might not be the right version for you.Īlso, people don't often realize that it's easy to use more than one "release" Or well, "true" if you stick to the "stable" Will raise is the fact that it only has "old packages", it is not updated When talking about using Debian, one of the first objections people Something it was not quite designed to do: persistent development environments.īefore attacking me violently for committing such a horrible sin, Over the last year, however, I learned to love to use docker for Hermetic environment for your build or test system to run on, withĪ new container instantiated for each run of your build or test, deleted It's what you do when you compose one or more containers to create an It's what you do when you use a plain Dockerfile to package an applicationĪnd all its dependencies into a container at build or release time, forĮxample, to then instantiate (and delete) that container on your production machines (kubernetes?). To then be deleted as soon as the work is done or the application needs To mind are disposable containers: containers that are instantiatedĪs many times as necessary to run an application or to complete some work, When thiking about Docker and what it is designed to do, what comes What you're up to before going around touching the wiring. So that your incredibly cheap and naive SATA controller and linux system knows Linux kernel, fairly easy to do, and worked really well for me.Īll you need to do is to make sure you type a few more commands from your shell, Not for the faint of hearts, but turns out this is possible with a stock No hardware raid controller, just the cheapest SATA support offered by the cheapestĪtom motherboard that you bought 10 years ago that happened to have enough In use, read write without unmounting it, and without rebooting the machine).Īll of this with consumer hardware, that DOES NOT SUPPORT ANY SORT OF HOT SWAP. The size of the raid5 volume and, well, you want to do it live (with the partition It has been running strong for the last 10 years, with the occasional disk replaced.Īnd now, you want to replace the old disks for the new ones, increase.You literally set this up 10 years ago - 4 disks 2 Tb each.On top of it, you have a few LVM volumes, and LUKS encrypted partitions.You have a linux software raid (raid5, in my case, created with mdadm).This suggests the problem is "Executable path is not absolute", so I opened the file /usr/lib/systemd/user/xscreensaver. Апр 03 18:07:22 nestor-Eve-V systemd: rvice: Cannot add dependency job, ignoring: Unit rvice is not loaded properly: Exec format error. Апр 03 18:07:22 nestor-Eve-V systemd: /usr/lib/systemd/user/rvice:5: Executable path is not absolute: xscreensaver Loaded: error (Reason: Exec format error) See user logs and 'systemctl -user status rvice' for details. Systemctl -user start rviceĪfter the last command I got the message: Failed to start rvice: Unit rvice is not loaded properly: Exec format error. Sudo apt-get purge -auto-remove gnome-screensaver Then I followed the instructions here and I did: sudo apt-get remove -auto-remove gnome-screensaver I guess, this is good and excludes the possibility that screensaver just doesn't get automatically started on start-up. If after a restart I type xscreensaver -nosplash I get: xscreensaver: 18:39:29: already running on display :0 (window 0x1a000de) I was afraid to delete the sktop file, so I out commented everything in it. Curiously, when I type locate sktop I get: /etc/xdg/autostart/sktop But If I wait for the screen to time out, it just goes blank black like the gnome-screensaver does, despite that I have gnome-screensaver installed. If I lock the screen with Cntrl+Alt+L then the xscreensaver starts. I don't understand Linux and sys-admin stuff, but I have installed recently xscreensaver Ubuntu 18.04.4 LTS as described here and I have followed all the steps.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |