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 38, column 42: description should not contain relative URL references: /#content_apps (3 occurrences) [help]

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

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