FEED Validator

Congratulations!

This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

• line 20, column 34: Self reference doesn't match document location [help]

        type="application/rss+xml"/>
                                    ^

• line 83, column 48: description should not contain relative URL references: /#content [help]

  now and up to sync, so happy downloading!&lt;/p></description>
                                                  ^

Source: http://sotirov-bg.net/news/feed?f=rss

1. <?xml version="1.0" encoding="utf-8"?>
2.  
3.  <?xml-stylesheet type="text/xsl" href="/style/rss.en.xsl"?>
4.  <?xml-stylesheet type="text/css" href="/style/rss.css"?>
5. <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"
6.  xmlns:blogChannel="http://backend.userland.com/blogChannelModule">
7.  <channel>
8.    <title>Sotirov-BG.Net News</title>
9.    <link>https://sotirov-bg.net/news/</link>
10.    <description>News from Sotirov-BG.Net</description>
11.    <language>en</language>
12.    <copyright>Copyright (c) 2004-2023 Georgi D. Sotirov</copyright>
13.    <pubDate>Sun, 13 Feb 2022 18:36:36 GMT</pubDate>
14.    <lastBuildDate>Sun, 13 Feb 2022 18:46:25 +0000</lastBuildDate>
15.    <managingEditor>gdsotirov@gmail.com (Georgi D.
16.      Sotirov)</managingEditor>
17.    <webMaster>gdsotirov@gmail.com (Georgi D. Sotirov)</webMaster>
18.    <generator>Perl 5.034000</generator>
19.    <atom:link href="https://sotirov-bg.net/news/feed.en?f=rss" rel="self"
20.      type="application/rss+xml"/>
21.    <image>
22.      <title>Sotirov-BG.Net News</title>
23.      <url>https://sotirov-bg.net/img/sotirov_net</url>
24.      <link>https://sotirov-bg.net/news/</link>
25.    </image>
26.    <item>
27.      <title>Upgrade to Slackware 15.0</title>
28.      <link>https://sotirov-bg.net/news/?id=38</link>
29.      <description>&lt;p>Last Friday (11/02) the server was upgraded to
30. <a
31. href="http://www.slackware.com/announce/15.0.php">Slackware 15.0</a>.
32.  The
33. upgrade of the system itself took about an hour, but it was necessary to
34. re-configure and fix problems with many services. It was also necessary to
35. upgrade to <a
36.  href="https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html">MySQL
37. 8.0</a>, because MySQL 5.7 would simply not start (as <a
38. href="https://slackpack.eu/search.cgi?q=%22mysql%22&lo=1">existing
39.  packages</a>
40. are build for older Slackware versions with old libraries). Due to strange
41. error (manifesting itself as <code>ListUtil.c: loadable library and perl
42. binaries are mismatched (got handshake key 0xdb00080, needed
43.  0xeb00080)</code>
44. when <code>perl</code> or <code>cpan</code> commands are run),
45.  all Perl modules
46. had to be reinstalled. In addition to this there was also a boot
47.  problem.</p>
48. <p>Thus the server was completely or partially inaccessible from about
49. 2022-02-11 17:50 <abbr title="Eastern European Time">EEST</abbr> to
50.  2022-02-12
51. 03:00 <abbr title="Eastern European Time">EEST</abbr>, but on the
52.  next day and
53. the day after more problems with public and private services were tackled.
54.  Some
55. more problems with hosted applications and sites were fixed as well.</p>
56. <p>Both Slackware 15.0 and MySQL 8.0 were much needed upgrades and I'm
57.  happy
58. to be running both now.&lt;/p></description>
59.      <author>ibeleva@nbu.bg (Ivelina Beleva-Sotirova)</author>
60.      <guid isPermaLink="true">https://sotirov-bg.net/news/?id=38</guid>
61.      <pubDate>Sun, 13 Feb 2022 18:36:36 GMT</pubDate>
62.    </item>
63.    <item>
64.      <title>Disk replacement (affecting mirrors)</title>
65.      <link>https://sotirov-bg.net/news/?id=37</link>
66.      <description>&lt;p>Just about an hour ago finished the replacement of
67. a potentially
68. failing disk drive on the server. Unfortunately, this affected the
69. <a href="/#content">mirrors</a>, because their partition was on the
70. drive without a backup. So mirrors were unavailable between about
71. 2021-09-27 20:06 <abbr title="Eastern European Summer
72.  Time">EEST</abbr>
73. and about 2021-09-28 05:41 <abbr title="Eastern European Summer
74.  Time">EEST</abbr>.
75. Sorry for that, but the replacement was necessary to prevent the
76. consequences of imminent drive failure.</p>
77. <p>The new drive is 4 times the size of the previous one, so eventually
78. more mirrors and/or other content may come soon. The mirrors of <a
79. href="https://www.gnu.org/"><abbr title="GNU's Not
80.  Unix">GNU</abbr></a>
81. and <a href="http://www.slackware.com/">Slackware</a> are available
82.  again
83. now and up to sync, so happy downloading!&lt;/p></description>
84.      <author>gdsotirov@dir.bg (Georgi Sotirov)</author>
85.      <guid isPermaLink="true">https://sotirov-bg.net/news/?id=37</guid>
86.      <pubDate>Tue, 28 Sep 2021 03:35:19 GMT</pubDate>
87.    </item>
88.    <item>
89.      <title>Improved web sites security</title>
90.      <link>https://sotirov-bg.net/news/?id=36</link>
91.      <description>&lt;p>I was considering dropping support for &lt;a
92. href="https://en.wikipedia.org/wiki/Transport_Layer_Security">
93. <abbr title="Transport Layer Security">TLS</abbr></a> v1.0
94. and v1.1 protocols for <a
95. href="https://sotirov-bg.net/index.en#content">the hosted web sites</a>
96. since 2016, when it was suggested, but I was still seeing such
97. clients in the logs (and unfortunately I still do even today).
98. I was thus reluctant, because such clients would NOT be able to
99. access the sites anymore. However, we are 2021 now and there are
100. no excuses for using too old and insecure clients (i.e. browsers).</p>
101. <p>Therefore, since about 12:00 <abbr
102. title="Universal Time Coordinated">UTC</abbr> today the hosted
103. sites are no longer supporting TLS v1.0 and v1.1 clients. I also
104. disabled weaker ciphers like <abbr title="Cipher Block
105.  Chaining">CBC</abbr>.
106. This effectively cuts the following browsers as <a
107. href="https://www.ssllabs.com/ssltest/analyze.html?d=sotirov-bg.net">SSL
108. Labs' report</a> shows:</p>
109. <ul>
110. <li><a href="https://www.android.com/">Android</a> 4.3 and
111. earlier;</li>
112. <li><a
113.  href="https://www.microsoft.com/en-us/download/internet-explorer.aspx">In
114.  ternet
115. Explorer</a> 10 and earlier;</li>
116. <li><a href="https://www.oracle.com/java/">Java</a> 7 and
117. earlier;</li>
118. <li><a href="https://www.apple.com/safari/">Safari</a> 8 and
119. earlier.</li>
120. </ul>
121. <p>If you are still using any of these apart from testing purposes
122. in isolated environments (like me), then too bad for you. It is
123. really time to upgrade!</p>
124. <p>This is considered a necessary step for improving web sites
125. security and something that perhaps should have been done earlier.
126. The changes were done following <a
127. href="https://wiki.mozilla.org/Security/Server_Side_TLS">Mozilla's
128. Server Side TLS recommendations</a>. It is not possible to enable
129. TLS v1.3 for now, because this requires <a
130. href="https://www.openssl.org/">OpenSSL</a> 1.1.1 or later, which
131. would become available with <a
132. href="http://slackware.com/">Slackware</a> 15.0 hopefully later
133. this year.</p>
134. <p>Happy surfing and stay safe!</p>
135. <p><strong>Update 2021-01-26</strong>: Apparently, <abbr
136. title="National Security Agency">NSA</abbr> <a
137. href="https://tech.slashdot.org/story/21/01/21/1646211/nsa-urges-system-adm
138.  inistrators-to-replace-obsolete-tls-protocols">urged</a>
139. for the same just three days ago :-)&lt;/p></description>
140.      <author>gdsotirov@dir.bg (Georgi Sotirov)</author>
141.      <guid isPermaLink="true">https://sotirov-bg.net/news/?id=36</guid>
142.      <pubDate>Sat, 23 Jan 2021 13:19:59 GMT</pubDate>
143.    </item>
144.    <item>
145.      <title>Internet connection upgrade</title>
146.      <link>https://sotirov-bg.net/news/?id=35</link>
147.      <description>&lt;p>Today, I finally managed to upgrade the Internet
148. connection.
149. The server is now connected through a high speed <abbr
150. title="Gigabit Passive Optical Network">GPON</abbr> network
151. provided by <a href="https://www.vivacom.bg/bg">Vivacom</a> with
152. maximum (unwarranted) upload speed of 300 <abbr
153. title="Megabits per second">Mb/s</abbr> from the whole world.
154. This is three times higher than the previous capacity and seems
155. more relevant nowadays. The new connection should make the access
156. to my content and the mirrors faster and more reliable.</p>
157. <p>Unfortunately, due to change of the service, I had to change also
158. the <abbr title="Internet Protocol">IP</abbr> address (it is now
159. 46.10.161.161), which caused some unexpected unavailability, but
160. for not more than 5-10 minutes as the <abbr
161. title="Domain Name System">DNS</abbr> servers updated quickly.</p>
162. &lt;p>Cheers!&lt;/p></description>
163.      <author>gdsotirov@dir.bg (Georgi Sotirov)</author>
164.      <guid isPermaLink="true">https://sotirov-bg.net/news/?id=35</guid>
165.      <pubDate>Tue, 03 Nov 2020 21:31:18 GMT</pubDate>
166.    </item>
167.    <item>
168.      <title>Server replacement</title>
169.      <link>https://sotirov-bg.net/news/?id=34</link>
170.      <description>&lt;p class="img_left">&lt;a
171. href="https://sotirov-bg.net/news/img/new_server">
172. <img alt="New server picture"
173.  src="https://sotirov-bg.net/news/img/new_server" width="250" title="New
174.  server" />
175. </a></p>
176. <p>Today, between 18:40 and 20:00 <abbr title="Eastern European
177.  Summer Time">EEST</abbr>
178. the server was not accessible, because I was finally able to move the
179.  system
180. to the new machine (<a
181.  href="https://www.dell.com/en-us/work/shop/povw/poweredge-r340">Dell
182. PowerEdge R340</a>). The operation took so long, because I wanted to
183.  copy
184. the bootable <abbr title="Solid State Drive">SSD</abbr> disk to the
185.  new drive
186. that came with the server, but I was not able to install it - a special
187. bracket is required to fit 2.5'' <abbr title="Solid State
188.  Drive">SSD</abbr>s
189. into Dell's 14<sup>th</sup> generation 3.5'' carriers.</p>
190. <p>After I moved all the drives I got myself into cabling, which took me
191.  some
192. more time although my new rack is well organized. I first chose patch
193.  cables
194. with the wrong length and then I had to reorganize some existing cables, so
195. I could fit around the new ones.</p>
196. <p>The first boot was smooth as expected with the default kernel, but I
197.  forgot
198. to comment out the persistent interface rules of udev for the network
199.  adapters
200. of the previous machine, so the server was without network. After fixing it
201.  I
202. decided to reboot once again to test that everything would get up
203.  properly.</p>
204. <p>I had to tune several other things after the server was up, but
205.  nothing
206. that would disrupt its normal work. The server is now ready to serve its
207. purpose.</p>
208. &lt;p>Cheers!&lt;/p></description>
209.      <author>gdsotirov@dir.bg (Georgi Sotirov)</author>
210.      <guid isPermaLink="true">https://sotirov-bg.net/news/?id=34</guid>
211.      <pubDate>Wed, 17 Jun 2020 20:50:44 GMT</pubDate>
212.    </item>
213.    <item>
214.      <title>Downtime for equipment movement</title>
215.      <link>https://sotirov-bg.net/news/?id=33</link>
216.      <description>&lt;p class="img_left">&lt;a
217. href="https://sotirov-bg.net/news/img/new_rack">
218. <img alt="New rack picture"
219.  src="https://sotirov-bg.net/news/img/new_rack" width="250" title="New
220.  rack" />
221. </a></p>
222. <p>Today between 10:40 <abbr title="Eastern European Summer
223.  Time">EEST</abbr>
224. and 11:40 <abbr title="Eastern European Summer Time">EEST</abbr> the
225.  server
226. was unavailable as I was moving my equipment to a new server rack. I could
227. have done this faster and in future I plan less downtime, but the important
228. thing is that now all my equipment except the server itself is into the
229.  rack.
230. I'm now waiting for the new server to arrive in about 10 days, so I could
231. move the current tower server into the rack.</p>
232. <p>Earlier this year I noticed that the server is shutting down even
233.  though
234. the <abbr title="Uninterruptible Power Supply">UPS</abbr> still has
235.  power to
236. support it. So, three weeks ago I changed the batteries, but as everything
237.  is
238. connected to it, currently the expected runtime is about 40 minutes at
239.  best.
240. However, I had some troubles with the power recently and in one of the
241.  cases
242. there was no line power for about 2 hours (due to accident). I'm now
243. considering increasing the runtime of my systems on batters or in other
244.  words
245. buying a new and more powerful <abbr title="Uninterruptible Power
246.  Supply">UPS</abbr>.
247. I'll need more than one to sustain my two servers and network devices for
248.  at
249. least 2 hours that is the power interruption I could expect from time to
250. time.</p>
251. &lt;p>Cheers until I have better news!&lt;/p></description>
252.      <author>gdsotirov@dir.bg (Georgi Sotirov)</author>
253.      <guid isPermaLink="true">https://sotirov-bg.net/news/?id=33</guid>
254.      <pubDate>Sat, 30 May 2020 17:52:46 GMT</pubDate>
255.    </item>
256.    <item>
257.      <title>Memory upgrade</title>
258.      <link>https://sotirov-bg.net/news/?id=32</link>
259.      <description>&lt;p>An hour ago I upgraded the memory of the server to
260. 16 <abbr
261. title="Giga Bytes">GB</abbr>. And the server was not accessible for
262. half an hour between 19:30 and 20:00 <abbr title="Eastern European
263.  Summer Time">EEST</abbr>,
264. because I accidentally loose the <abbr title="Serial AT
265.  Attachment">SATA</abbr>
266. connector of one of the hard drives :-(</p>
267. <p>After I added a new 8 <abbr title="Giga Bytes">GB</abbr>
268.  <abbr
269. title="Double Data Rate">DDR</abbr>3 module the server started normally.
270. I thought everything is OK and left it, but then I tried to connect
271. and wasn't able. So, I went back to check the server and on the
272. console there were many <abbr title="Fourth extended
273.  filesystem">EXT4</abbr>
274. error messages. I had to stop the machine again, check the devices in
275. <abbr title="Basic Input/Output System">BIOS</abbr>. Since one of the
276. hard drives was missing I immediately checked the connectors and solved
277. the problem.</p>
278. <p>I should have done this upgrade long ago, but until recently I
279. though the memory is enough for all the services running. Anyway,
280. the server has enough memory now.&lt;/p></description>
281.      <author>gdsotirov@dir.bg (Georgi Sotirov)</author>
282.      <guid isPermaLink="true">https://sotirov-bg.net/news/?id=32</guid>
283.      <pubDate>Thu, 16 Apr 2020 17:29:55 GMT</pubDate>
284.    </item>
285.    <item>
286.      <title>Inaccessibility due to router replacement</title>
287.      <link>https://sotirov-bg.net/news/?id=31</link>
288.      <description>&lt;p>Today between 12:30 &lt;a
289. href="https://www.timeanddate.com/time/zones/eet">
290. <abbr title="Eastern European Time">EET</abbr></a> and 14:30 <a
291. href="https://www.timeanddate.com/time/zones/eet"><abbr
292. title="Eastern European Time">EET</abbr></a> the server was not
293.  accessible
294. due to router replacement and change of <abbr title="Internet
295.  Protocol">IP</abbr>
296. addresses. Although, the replacement was planned and prepared previously,
297.  some
298. unforeseen circumstances occurred with the configuration of the device
299.  itself
300. as well as with the server.</p>
301. <p>The expected change with the replacement is better network
302.  performance for
303. the increasing outer and inner traffic.&lt;/p></description>
304.      <author>gdsotirov@dir.bg (Georgi Sotirov)</author>
305.      <guid isPermaLink="true">https://sotirov-bg.net/news/?id=31</guid>
306.      <pubDate>Sun, 17 Dec 2017 20:10:15 GMT</pubDate>
307.    </item>
308.    <item>
309.      <title>Downtime for disk replace</title>
310.      <link>https://sotirov-bg.net/news/?id=30</link>
311.      <description>&lt;p>Last night while &lt;a hreflang="bg"
312. href="https://bg.wikipedia.org/wiki/%D0%A1%D1%82%D1%83%D0%B4%D0%B5%
313. D0%BD%D1%82%D1%81%D0%BA%D0%B8_%D0%BF%D1%80%D0%B0%D0%B7%D0%BD%D0%B8%
314. D0%BA_(%D0%91%D1%8A%D0%BB%D0%B3%D0%B0%D1%80%D0%B8%D1%8F)">all
315. students were celebrating</a>, I spent replacing a failing <a
316. href="https://www.samsung.com/us/support/owners/product/64gb-ssd-830-series
317.  ">Samsung
318. 830</a> <abbr title="Solid State Drive">SSD</abbr> on the
319.  server.
320. The disk was so rotten that it's copy with <code>dd</code> took about
321.  5 hours,
322. which is why the server was offline somewhere between 2017-12-08 22:00
323.  <a
324. href="https://www.timeanddate.com/time/zones/eet"><abbr
325. title="Eastern European Time">EET</abbr></a> and 2017-12-09 05:00
326.  <a
327. href="https://www.timeanddate.com/time/zones/eet"><abbr
328. title="Eastern European Time">EET</abbr></a>. The disk started
329.  failing in
330. beginning of September, but recently the number of reallocated sectors
331.  become
332. extremely high and I started detecting bad sectors on some system files.
333.  The
334. read performance had also dropped and during the copy it fell to 5 <abbr
335. title="Mega Bytes per second">MB/s</abbr> (!), which explains the fore
336. mentioned slow copy of just 64 <abbr title="Giga Bytes">GB</abbr>
337.  between
338. the old and new <abbr title="Solid State Drive">SSD</abbr>. The disk
339. failed only after about 24 000 power on hours (i.e. about 2 years and 9
340.  months),
341. which is rather strange, but maybe this is the normal life span of consumer
342. <abbr title="Solid State Drive">SSD</abbr>s?</p>
343. <p>Anyway, the drive is now replaced with a brand new <a
344.  href="http://www.adata.com/us/feature/410">ADATA SU800</a>
345. 128 <abbr title="Giga Bytes">GB</abbr>, which unfortunately is not
346.  yet in
347. <code>smartctl</code> database (see <a
348.  href="https://www.smartmontools.org/ticket/954">ticket 954</a>).
349. The server is back online and fully operational.&lt;/p></description>
350.      <author>gdsotirov@dir.bg (Georgi Sotirov)</author>
351.      <guid isPermaLink="true">https://sotirov-bg.net/news/?id=30</guid>
352.      <pubDate>Sat, 09 Dec 2017 04:01:15 GMT</pubDate>
353.    </item>
354.    <item>
355.      <title>Upgrade to Slackware 14.2</title>
356.      <link>https://sotirov-bg.net/news/?id=29</link>
357.      <description>&lt;p>Last Sunday (28/08) the server was upgraded to
358. <a href="http://www.slackware.com/">Slackware</a>
359. 14.2, which itself passed flawlessly, but then there was a need for
360.  re-install
361. of all the additionally used Perl modules and upgrade of some packages
362.  (e.g. <a
363. href="http://sotirov-bg.net/slackpack/search.cgi?name=openldap&slac
364.  k=142&latestonly=1">OpenLDAP</a>,
365. <a
366.  href="http://sotirov-bg.net/slackpack/search.cgi?name=rrdtool&sla
367.  ck=142&latestonly=1">RRDTool</a> and
368. <a
369.  href="http://sotirov-bg.net/slackpack/search.cgi?name=freeradius&
370.  slack=142&latestonly=1">FreeRadius</a>),
371. which I haven't upgraded/rebuilt yet.</p>
372. <p>Yesterday, evening the datbase server was also upgraded to MySQL
373.  5.7.13, so
374. it now remains only to upgrade the kernel to a <abbr title="Long Term
375.  Support">LTS</abbr>
376. version from 4.4 series.&lt;/p></description>
377.      <author>gdsotirov@dir.bg (Georgi Sotirov)</author>
378.      <guid isPermaLink="true">https://sotirov-bg.net/news/?id=29</guid>
379.      <pubDate>Tue, 30 Aug 2016 09:34:17 GMT</pubDate>
380.    </item>
381.  </channel>
382. </rss>
383.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

1. Download the "valid RSS" banner.

2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

3. Add this HTML to your page (change the image src attribute if necessary):

   <a href="http://www.feedvalidator.org/check.cgi?url=http%3A//sotirov-bg.net/news/feed%3Ff%3Drss"><img src="valid-rss-rogers.png" alt="[Valid RSS]" title="Validate my RSS feed" /></a>

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//sotirov-bg.net/news/feed%3Ff%3Drss

Home · About · News · Docs · Terms