❌

Modalità di lettura

Dietro gli applausi a Meloni le convergenze geopolitiche che servono all’Italia

Convergenze parallele e, per certi versi, anche fisiologiche. Ieri in Senato si è assistito ad un fenomeno che, in quattro anni, non si era quasi mai visto. Ovvero gli applausi a Meloni di Calenda e mezzo Pd. Come se la geopolitica, prima che politica, avesse avuto il sopravvento su contrapposizioni, insulti, contestazioni. Come se il clima pre-elettorale fosse stato messo da parte sull’altare delle cose giuste da fare e da rivendicare a Bruxelles. Il paniere di temi in questione è noto e riguarda il futuro non solo dell’Italia, ma anche della stessa Europa.

Quando la presidente del Consiglio ha spiegato che alcune dinamiche non hanno molto a che fare con la tutela dell’ambiente, ovvero il prezzo degli Ets che sale e che quindi fa salire anche il costo di produzione per l’acciaieria, la cartiera, il cementificio, la ceramica, ha posto un tema su cui nessuna parte sana può non essere d’accordo, perché riguarda la salvaguardia delle imprese.

Che non hanno colore politico, ma rispondono a logiche semplicissime: se regole sbagliate le strozzano, allora rischiano la chiusura, con conseguente perdita di posti di lavoro.

Quando Meloni ha chiesto una sospensione temporanea di alcuni obblighi sul Regolamento europeo del metano ha posto un altro tema nevralgico: ovvero che se una norma, nel passaggio dalla teoria alla pratica, produce danni o mancati benefici, semplicemente va corretta.

Infine quando ha avvertito che non è più possibile per l’Europa importare cobalto, grafite, terre rare imprescindibili per transizione energetica, transizione digitale e difesa, non fa solo una diagnosi arci nota (su cui però dei “bravi” nessuno ha dato un’accelerata fino ad oggi) ma indica la cura, proponendo Porto Marghera come uno dei primi siti europei di stoccaggio strategico di queste materie, iniziativa che potrebbe diventare un progetto pilota europeo.

“Il filo che lega tutte queste iniziative, insomma, è semplice: l’Europa deve tornare a mettere la capacità di produrre al centro delle proprie scelte”, ha detto la premier. In quel momento gli applausi di democratici e calendiani sono stati la spia che l’interesse nazionale è sentito dalle cosiddette forze responsabili presenti in Parlamento, dove l’epiteto responsabili non è il titolo di una squadra buono per un discorso carico di demagogia.

Ma la pragmatica conseguenza di scelte strutturali e lungimiranti che devono essere fatte per il bene futuro (e presente) della collettività. Che si fanno solo in un modo.

L’Europa forte che ha bisogno di Nazioni forti, parafrasando Meloni in chiusura, fa il paio con l’esigenza di un’Europa più solida e credibile all’interno di un metodo di amministrare il paese che difenda l’interesse italiano (come fanno anche tutti gli altri paesi membri).

Solo una parte delle opposizioni lo ha ben compreso.

  •  

Inside the Plague Research Labs at the Heart of a Russian Mystery

A Russian researcher, who died from an unknown illness, worked at a remote anti-plague facility. Few foreigners have visited these labs, which dot the former Soviet states, and are shrouded in secrecy.

© Irkutsk Antiplague Research Institute, via Agence France-Presse — Getty Images

A picture released by the Irkutsk Anti-Plague Research Institute showing specialists working in a laboratory in Krasnoyarsk, Russia, in 2019.
  •  

Inside the Plague Research Labs at the Heart of a Russian Mystery

A Russian researcher, who died from an unknown illness, worked at a remote anti-plague facility. Few foreigners have visited these labs, which dot the former Soviet states, and are shrouded in secrecy.

© Irkutsk Antiplague Research Institute, via Agence France-Presse — Getty Images

A picture released by the Irkutsk Anti-Plague Research Institute showing specialists working in a laboratory in Krasnoyarsk, Russia, in 2019.
  •  

Migrating to Slackware-current - LXC-7 - cgroup2

Index


Let's see how to manage unprivileged containers also in Slackware-current (16.0 to be), which -at the time I'm writing- ships kernel-7.2.x, lxc-7.0 and libcgroups-3.2.0.

Version 7 of LXC dropped cgroup v1, so we have to use cgroup v2. Thanks to 0XBF for the big support in the cgroup v2 settings as far as the limits inside the containers are concerned.

First of all, enable cgroup2 in /etc/default/cgroups

# Which version of cgroups should we mount, version 1 or version 2? 
# Please note that the rc.cgred init script (as well as the cgrulesengd 
# utility itself) will not function with cgroups version 2. Upstream 
# did not implement support for this since systemd handles it (of course). 
CGROUPS_VERSION=2 

# A list of controllers to enable in the root cgroup.subtree_control file. 
# These are only used for cgroup version 2 configurations. Note that enabling 
# the 'cpu' controller will cause the kernel to no longer use real-time 
# scheduling. For a full list of available controllers, examine the contents 
# of /sys/fs/cgroup/cgroup.controllers. The following commented list is a 
# typical full list of controllers, while the shorter one is a typical default list 
# used on systemd/logind systems. 
# Warning: the stock kernel has CONFIG_RT_GROUP_SCHED=y. Adding 'cpu' here 
# will silently prevent real-time scheduling for processes in user sessions 
# (PipeWire, JACK, rtkit). Boot with rt_group_sched=0 if you need both. 
CGROUP_V2_CONTROLLERS="cpuset io memory pids misc dmem" 
#CGROUP_V2_CONTROLLERS="memory pids" 

# Options to pass when mounting cgroup2. Prefix options with '-o'. 
# The following example adds the 'nsdelegate' option to the mount 
# of cgroup2: 
CGROUP_V2_MOUNT_OPTS="-o nsdelegate"

Disable rc.cgconfig and rc.cgred at boot time:

chmod -x /etc/rc.d/rc.cgconfig /etc/rc.d/rc.cgred

Replace the file /etc/lxc/lxc-common.conf in this way (all lxc.cgroup.* options are now lxc.cgroup2.*):

lxc.net.0.type = veth 
lxc.net.0.flags = up 
lxc.net.0.link = lxcbr0 
lxc.net.0.name = eth0 
lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx 

lxc.tty.max = 1 
lxc.pty.max = 1024 

lxc.cgroup2.devices.deny = a 
# /dev/null and zero 
lxc.cgroup2.devices.allow = c 1:3 rwm 
lxc.cgroup2.devices.allow = c 1:5 rwm 
# consoles 
lxc.cgroup2.devices.allow = c 5:1 rwm 
lxc.cgroup2.devices.allow = c 5:0 rwm 
lxc.cgroup2.devices.allow = c 4:0 rwm 
lxc.cgroup2.devices.allow = c 4:1 rwm 
# /dev/{,u}random 
lxc.cgroup2.devices.allow = c 1:9 rwm 
lxc.cgroup2.devices.allow = c 1:8 rwm 
lxc.cgroup2.devices.allow = c 136:* rwm 
lxc.cgroup2.devices.allow = c 5:2 rwm 
# rtc 
lxc.cgroup2.devices.allow = c 254:0 rwm 

# we don't trust even the root user in the container, better safe than sorry. 
# comment out only if you know what you're doing. 
lxc.cap.drop = sys_module mknod mac_override mac_admin sys_time setfcap setpcap

# you can try also this alternative to the line above, whatever suits you better. 
#lxc.cap.drop=sys_admin 

# proc & sys, remove from /etc/fstab 
lxc.mount.auto = proc:mixed sys:ro

When you start the containers, a cgroup structure is created in /sys/fs/cgroup:

# tree -d --noreport /sys/fs/cgroup 
/sys/fs/cgroup 
├── 1 
│   ├── delegated 
│   └── session 
├── elogind 
└── lxc-containers 
   ├── c1
   │   ├── delegated 
   │   │   ├── lxc.monitor.c1 
   │   │   └── lxc.payload.c1 
   │   └── session 
   ├── c2 
   │   ├── delegated 
   │   │   ├── lxc.monitor.c2
   │   │   └── lxc.payload.c2 
   │   └── session
   ├── c3
   │   ├── delegated 
   │   │   ├── lxc.monitor.c3
   │   │   └── lxc.payload.c3 
   │   └── session

Now you are able to setup container's limits inside each config file. For example, to set a memory limit to the container test just add the following in its config file:

lxc.cgroup2.memory.max = 256M

Restart the container and check that the memory limit has been set:

cat /sys/fs/cgroup/lxc-containers/test/delegated/lxc.payload.test/memory.max
268435456

Be aware that, if you want to use my scripts with slackware-current you have to download the main branch of my github instead of the latest release:

git clone https://github.com/sagredo-dev/LXC-scripts.git
  •  

Wrapper scripts for LXC unprivileged containers

Index


A common use of the LXC containers is to isolate services like sql, ftp, httpd, mail etc. in an host server where the only user who will ever login is root. In this case, handling the unprivileged containers can be quite annoying.

First of all, you would like to have all the containers' filesystems inside the same directory, let's say /lxc, while LXC installs them in the $HOME/.local/share/lxc directory of the container's owner user. In addition, root has to administer a container as its owner user (i.e. using sudo -u <user>), by defining the configuration file and other parameters by means of a long command to type and remember. If you have many unprivileged containers and have to perform tasks like start/stop/attach frequently, your patience will come to an end very quickly.

This is the reason why at a certain point I started to write my own wrapper scripts for the most common LXC commands. Nothing special, but it seems that no one has published any tools to simplify the LXC common tasks with unprivileged containers, so it may be worth posting here what I have done.

  •  

Aggiornare qmail

Changelog

  • Sep 29, 2026
    More info in the changelog
    - Modernization for compatibility with C23 and recent GCC/clang releases in #44
    - srs: do not rewrite qmail's internal envelope addresses ("#@[]" and VERP) by @yohgaki in #46
    - Improve general portability across linux and *BSD platforms in #47
  • Apr 7, 2026
    - (security) Remote Code Execution via Shell Injection in qmail-remote TLS Error Handler in #42 (tx Diep Pham)
  • Apr 2, 2026
    - qmail-remote auth improvements by pierluigi in #39
    - Fixed DKIM ed25519-sha256 signing and verification to conform to RFC8463 by @agerstla in #40
    - Updated qmail-qfilter to support filters defined in control/qfilters by @agerstla in #41
  • Feb 25, 2026
    - Improved DKIM status handling by @agerstla in #35
    - Ported over DKIM_BAD_IDENTITY support from Indimail (tx Manvendra Bhangui and Andreas Gerstlauer 1299b55)
    - SNI support for qmail-smtpd by @agerstla in #37
    - Added qmail-qfilter by @agerstla in #38
  • Apr 25, 2025
    - added a configuration script config-all, which configure and installs the control files (as per the original config-fast script), aliases, SRS (uses control/me as the srs_domain), log dirs in /var/log/qmail, tcprules (basic, just to make initial tests), supervise scripts, qmailctl script, DKIM control/filterargs and control/domainkeys dir, SURBL, smtpplugins, helodnscheck spp plugin, svtools, qmHandle, queue-repair, SSL key file (optional). 

  •  
❌