-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.xml
executable file
·46 lines (37 loc) · 3.2 KB
/
index.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Gregory Shimansky blog</title>
<link>https://gshimansky.github.io/</link>
<description>Recent content on Gregory Shimansky blog</description>
<generator>Hugo -- gohugo.io</generator>
<language>en-us</language>
<lastBuildDate>Tue, 08 Oct 2019 21:40:58 -0500</lastBuildDate>
<atom:link href="https://gshimansky.github.io/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Fix for HP CUPS driver in Ubuntu</title>
<link>https://gshimansky.github.io/posts/00003-hp-cups-driver-fix/</link>
<pubDate>Tue, 08 Oct 2019 21:40:58 -0500</pubDate>
<guid>https://gshimansky.github.io/posts/00003-hp-cups-driver-fix/</guid>
<description>Symptom: In /var/log/cups/error_log there is a message (/usr/lib/cups/filter/hpcups) crashed on signal 11. and printer doesn&rsquo;t print anything. The problem is that hpcups is buggy in Ubuntu 19.04. A solution is to install HP printer driver from sources from https://developers.hp.com/hp-linux-imaging-and-printing. There are several problems with this however.
Delete all printer configurations from /etc/cups/printers.conf. First download and run HPLIP main source hplip-3.19.8.run and a plugin for it hplip-3.19.8-plugin.run. Use whatever version is latest from HP site.</description>
</item>
<item>
<title>Vagrant Libvirt Plugin Build on Ubuntu</title>
<link>https://gshimansky.github.io/posts/00002-vagrant-libvirt-plugin-build-on-ubuntu/</link>
<pubDate>Tue, 26 Feb 2019 09:45:10 -0600</pubDate>
<guid>https://gshimansky.github.io/posts/00002-vagrant-libvirt-plugin-build-on-ubuntu/</guid>
<description>On modern Ubuntu versions vagrant plugin vagrant-plugin fails to build. It is necessary to specify correct locations of libvirt headers and librarires. Possible solution can be found here:
CONFIGURE_ARGS=&quot;with-libvirt-include=/usr/include/libvirt with-libvirt-lib=/usr/lib64&quot; vagrant plugin install vagrant-libvirt Installing the 'vagrant-libvirt' plugin. This can take a few minutes... Building native extensions. This could take a while... Fetching: fog-libvirt-0.5.0.gem (100%) Fetching: vagrant-libvirt-0.0.43.gem (100%) Installed the plugin 'vagrant-libvirt (0.0.43)'! </description>
</item>
<item>
<title>How to clone a libvirt VM controlled by Vagrant</title>
<link>https://gshimansky.github.io/posts/00001-clone-libvirt-vm-controlled-by-vagrant/</link>
<pubDate>Thu, 30 Aug 2018 10:16:00 -0500</pubDate>
<guid>https://gshimansky.github.io/posts/00001-clone-libvirt-vm-controlled-by-vagrant/</guid>
<description>Strangely enough, googling about this problem doesn&rsquo;t produce any meaningful results. So here are steps which allow cloning a libvirt VM controlled by Vagrant. Imagine that you have a VM named testvm1 which you want to clone into testvm2.
Shutdown all VMs with vagrant halt or at least from inside of VM with sudo shutdown -h 0.
Figure our real VM name with virsh list --all | grep testvm1.</description>
</item>
</channel>
</rss>