Пишу о Linux и администрировании серверов.
Связаться с автором: @servers
Реклама на канале не размещается.
Заметки в браузере: https://journald.ru/
Буст канала: https://t.me/sysadminnotes?boost
Created
20 April 2016 — measured — cross-checked against a third-party dataset (ext.tg_channel)
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
55 measurements spanning 97 days, net +23. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 12,648–12,812 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 55
Measured (UTC)
Subscribers
Change
10 Nov 2026, 12:08
12,691
-1
8 Nov 2026, 23:59
12,692
-99
7 Nov 2026, 13:51
12,791
-2
6 Nov 2026, 12:08
12,793
+3
5 Nov 2026, 08:49
12,790
+3
4 Nov 2026, 05:49
12,787
+2
3 Nov 2026, 06:10
12,785
+3
1 Nov 2026, 03:15
12,782
+2
31 Oct 2026, 00:09
12,780
+4
30 Oct 2026, 01:37
12,776
+4
29 Oct 2026, 05:07
12,772
+4
26 Oct 2026, 23:08
12,768
-2
25 Oct 2026, 23:20
12,770
+1
24 Oct 2026, 23:55
12,769
-3
23 Oct 2026, 20:48
12,772
+2
22 Oct 2026, 20:30
12,770
+2
21 Oct 2026, 18:50
12,768
+2
20 Oct 2026, 15:40
12,766
-2
19 Oct 2026, 18:41
12,768
+3
18 Oct 2026, 21:38
12,765
first reading
Engagement
39 posts held, back to 21 March 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 64 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
23.2%
avg views ÷ 12,691 subscribers
Avg views / post
2,950
5 posts measured
Reaction rate
1.05%
reactions ÷ views · ER floor
Posts in window
5
of 39 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
What these figures were computed from
Window
Rolling 30 days · latest post in window 9 November 2026
Posts held
39 (21 March 2026 – 9 November 2026)
Views total
14,740
Reactions total
155
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
11 Nov 2026, 20:32 UTC
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
Photos
≈696
Videos
≈31
Links
≈2,570
Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
1,343 reactions across 39 posts, in 25 distinct kinds. The most used accounts for 42.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
568
42.3%
🔥
232
17.3%
🎉
194
14.4%
❤
82
6.11%
😁
51
3.80%
🤝
42
3.13%
🤡
36
2.68%
custom 5298552796314879115
33
2.46%
🤔
28
2.08%
💯
18
1.34%
🍾
14
1.04%
👏
10
0.745%
🤮
7
0.521%
👀
6
0.447%
👎
5
0.372%
🤯
5
0.372%
🤣
3
0.223%
🖕
2
0.149%
🌚
1
0.074%
🗿
1
0.074%
5 further kinds
5
0.372%
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 39 of the 39 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 1,343 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 39 most recent posts we hold, published 21 March 2026 to 9 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Telegram Stars
Stars received
176
across the posts below
Posts paid on
7
of 39 we hold a reading for · 18%
Most on one post
154
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @SysadminNotes. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 39 most recent posts we hold for this entry, published 21 March 2026 to 9 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 5 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Друзья, добрый вечер! 👋
Наверняка вы уже почувствовали дыхание зимы ❄️, и лично нам хочется снова увидеть знакомые лица, послушать, кто над чем работает, познакомиться с новыми людьми.
Надеемся, что у вас за год накопилось что рассказать: о работе, upstream или собственном проекте, до которого руки доходят только по выходным.
Поэтому 7 декабря собираемся на RULKC CONF 2026! Конференцию в лучших традициях OSDevConf,…
🐦 Стек виртуализации в Linux.
Ну и, собственно, сам раздел, который появился на сайте. И который точно ещё будет дорабатываться мной, но в текущем виде его будь-то бы уже не стыдно показать:
https://journald.ru/virtualization/#00
На странице приведено 20 сценариев, которые происходят в системе, когда пользователь что-то делает с виртуальной машиной - создаёт, запускает, делает снимки, выключает, удаляет и т. п. Дл…
Знаете, наверное, впервые за долгое время, я испытал интерес к процессу создания чего-то этакого. Все помнят чем закончилась история с sysadmin.pm - сайт мёртв, бекапы потеряны, восстановлены только несколько десятков html страниц из веб-архива. Потом были попытки это дело поднять и запустить на отдельном домене, знакомство с hugo, тестовые версии сайта, но всё это так или иначе ничем действительно результативным не …
🛠 excise - tui утилита для проверки информации о занятости места на диске...
https://github.com/findyourexit/excise
Из дополнительного удобного:
- Вывод в виде таблицы или визуальной карты;
- Вывод в JSON для дальнейшей обработки где-либо.
Форкнули disconaut и, похоже, сделали лучше и визуально приятнее.
#disk #util #будничное
💿 Cracking the Linux Boot Code - занятное чтиво от инженеров Oracle о диагностике запуска и загрузки системы...
- Linux Boot-Time Diagnostics Foundations;
- Deep-Dive Linux Boot Diagnostics.
Первая статья описывает базовые методы диагностики загрузки, а вторая показывает углублённые техники и подходы.
#linux #boot #debug
🕹 Побаловаться на выходных - Quake на CSS, и Quake в ASCII. В браузере доступно по ссылкам:
- https://cssquake.com/
- http://asciiquake.wtf/
Github проектов:
- https://github.com/layoutit/cssQuake
- https://github.com/apresmoi/asciiQuake
P. S. Переключиться можно сразу на конкретный уровень, указав его в параметрах URL, например - https://cssquake.com/?map=e1m7
#quake #игори
⚙️ А вот тут менеджер виртуальных машин прямо в терминале - kudu.
Для тех, кому интересен tui аналог virt-manager'а...
https://github.com/pythops/kudu
#qemu #virtualization #tui
🛰 CERN's migration path from CentOS Linux to Debian - CERN мигрирует 2200 промышленных компьютеров (если я правильно понимаю, управляющих систем ускорителей) с CentOS на Debian. Переход рассматривался и ранее, но решающим стало изменение в RHEL - оптимизация под архитектуры x86-64-v2 и x86-64-v3...
https://lwn.net/SubscriberLink/1092512/0772b817c369632b/
Ситуация, когда смена ОС оказалась более выгодной с т. з. эко…
👍9🔥5🤔4
Showing the 12 most recent of 39 posts we hold for @SysadminNotes. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
The shares total 128%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 39 most recent posts we hold, published 21 March 2026 to 9 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
ServerAdmin.ru @srv_admin · 32,701 Telegram ranks this channel #6 of 96 here — alongside 95 others — read 5 September 2026
Типичный Сисадмин @sysodmins · 40,818 Telegram ranks this channel #31 of 93 here — alongside 92 others — read 31 August 2026
Системный администратор @i_odmin · 26,713 Telegram ranks this channel #34 of 89 here — alongside 88 others — read 12 September 2026
Книги для Системного Администратора @i_odmin_book · 18,778 Telegram ranks this channel #42 of 83 here — alongside 82 others — read 5 October 2026
Bash Days | Linux | DevOps @bashdays · 23,621 Telegram ranks this channel #42 of 94 here — alongside 93 others — read 18 September 2026
DevOps&SRE Library @devopslibrary · 19,870 Telegram ranks this channel #48 of 94 here — alongside 93 others — read 30 September 2026
BZD • Книги для программистов @bzd_channel · 36,213 Telegram ranks this channel #53 of 57 here — alongside 56 others — read 1 September 2026
ДЕВОПСИНА | DevOps | Linux @devopsina · 23,569 Telegram ranks this channel #56 of 90 here — alongside 89 others — read 18 September 2026
DevOps by REBRAIN @rebrain_devops · 28,735 Telegram ranks this channel #58 of 94 here — alongside 93 others — read 9 September 2026
Open Source @open_source_friend · 52,669 Telegram ranks this channel #59 of 87 here — alongside 86 others — read 24 August 2026
Devops Jobs — вакансии и резюме @devops_jobs_feed · 22,291 Telegram ranks this channel #79 of 95 here — alongside 94 others — read 22 September 2026
Linux для чайника @os_linux_ru · 19,526 Telegram ranks this channel #83 of 87 here — alongside 86 others — read 1 October 2026
DevOps @DevOPSitsec · 23,892 Telegram ranks this channel #83 of 90 here — alongside 89 others — read 18 September 2026
Секреты сисадмина | DevOps, Linux, SRE @sysadmin_library · 25,689 Telegram ranks this channel #83 of 85 here — alongside 84 others — read 13 September 2026
Информация опасносте @alexmakus · 18,748 Telegram ranks this channel #84 of 85 here — alongside 84 others — read 5 October 2026
MikroTik-сэнсэй @mikrotik_sensei · 19,662 Telegram ranks this channel #86 of 92 here — alongside 91 others — read 1 October 2026
DevOps community for love @devopsforlove · 44,606 Telegram ranks this channel #87 of 95 here — alongside 94 others — read 9 September 2026
Selectel @Selectel · 62,423 Telegram ranks this channel #88 of 96 here — alongside 95 others — read 21 August 2026
IT STAND @ITSTAND_ORG · 164,814 Telegram ranks this channel #98 of 98 here — alongside 97 others — read 9 September 2026
This channel appears in 19 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 10 November 2026 — this
entry's latest reading, not the date you are reading this.
“Записки админа” (@SysadminNotes), 12,691 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/SysadminNotes.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.