Search Results for 'boot from iso'

[Member iznit]

to convert devuan ceres (or debian sid) with runit

any other tips concerning conversion appreciated.

Unpack the initrd.gz from each distro and compare contents. A chunk of “what makes antiX act like antiX” lays within the initial RAM disk (initrd). I don’t know whether you can or should just discard the non-antiX initrd. Check the live-usb-maker script. What “bits and bobs” must it find available [[[installed]]] in order to to create a full-featured live antiX. Okay, maybe you don’t really care about live features. Still, check code within the iso-snapshot progrem. It seems to perform a wholesale [[[complete]]] replacement of the initrd. It replaces the initrd present on the running system with an initrd prepared by and packaged by antiX. I don’t know which package supplies this “stock” initrd. It must be one of the packages the snapshot pckage “depends” on.

At a minimum, without the antiX initrd the “converted” system will not recognize any of the special bootcodes//cheatcodes. Also, the system will lack many bundled external modules [[[drivers]]] for the wide range of older hardware that antiX natively supports.

[Moderator Brian Masinick]

As far as other Web browsers go, SOMETIMES I do the same thing, creating and updating personal directories of other Web browsers, such as a new version of Palemoon or an updated build of Ungoogled Chromium. I’ve been following Firefox for considerably longer than these other browsers, and while I do test them and use them from time to time, I’ve naturally been more familiar and accustomed to the behavior of Firefox, so that tends to be the one I watch, retain multiple builds for, and use most often.

I haven’t gone crazy testing twenty different browsers and ten different environments recently; I’d often have 10-12 distinct distributions on a single system, PLUS have one or two distributions on other computers in the past. I do have 4-5 computers still, but only two of them have more than a single distribution and I’m down to five commonly used distributions now: antiX, MX Linux, Debian Sid (siduction), PCLinuxOS, and EndeavourOS. All FIVE of these are surprisingly stable, despite their names and widely different use cases and reputation.

In particular, you’d expect both Debian Sid and EndeavourOS to be somewhat unstable; I have yet to find that true, and on my current systems I’ve had BOTH of them installed since I set up their current instances, and like MX Linux, PCLinuxOS and our lean favorite, antiX, each of them is stable, yet each also has their own personality and subtle differences.

On my fastest system with NVME SSD, for instance, I find that siduction seems to be able to take the most advantage of the configuration and it can boot a few to several seconds faster than the others.

Neither MX Linux nor PCLinuxOS is particularly fast in booting or shutting down; MX Linux 21 AHS (Advanced Hardware Support), in fact, is exceptionally slow SHUTTING DOWN — unless I “help it out”. I found a handy trick that works really well for MX Linux when I’m shutting down or rebooting. First, I open a terminal, then I run the command “sudo su -)” to assume root/sys admin rights, then I run the command telinit 2, which puts the console in multi-user mode (minus the full GUI capabilities), except before I actually SEE the GUI vanish, I then type either reboot, halt, or poweroff, and the system heeds my command within a maximum of a few seconds, instead of painstakingly saving logs, or whatever it does, and then eventually shutting down.

If I want to examine logs, I certainly generate them, whether automatically or through specific tasks and operations, but the majority of the time, I have no need, so when I don’t need it, I’m able to significantly accelerate the management processes to suit my needs and interests.

MX Linux is very good as a stable, middle of the road distribution, lighter than PCLinuxOS for many things; it’s a great general purpose distribution when you do want a desktop, but you don’t often need a lot of extra features.

PCLinuxOS, on the other hand, is a hodge-podge of software, solid, stable, yet pretty up-to-date. It’s best attributes are that it is a very full featured distribution with a LOT of software included, even in an Xfce only desktop; even more full and complete with a Plasma or other full featured environment. Different idea and methodology entirely than MX Linux, and yet in terms of reliability, day in, day out use they have some similarities in that you can count on them to get the job done.

Then there’s EndeavourOS: I’ve read countless reports of people over the years who swear by their particular Arch Linux setup, yet whenever I try one out, it’ll seem to be fine for a while. One time I got nearly a year out of a pure Arch Linux configuration, then an unexpectedly rogue update destroyed the distribution and threatened to compromise my entire computer; got rid of it before it worked it’s destruction on all partitions. After some time (years) of staying away, I gave Manjaro Linux a good run; like Arch, it went well, maybe a bit longer than a year, but it either broke networking or damaged itself; bottom line it broke too.

A friend told me about EndeavourOS, said it was one of his most stable, usable environments; this person is pretty trustworthy (though equally opinionated) when making comments or recommendations, so I tried it and found it to be leading edge with current software, yet a similar experience to my personal Debian Sid (and siduction) experience – good, current software, solid packaging and very good performance.

That’s been true for EndeavourOS for a couple years now on TWO of my systems.

As for antiX, I have it on ALL except one of my systems across more than a decade difference in age; only one of them has a problem – the newest one doesn’t YET support my Wireless Card (at least not in the ISO images available). I’ve been told that the support IS in the wireless driver my card uses, so my hope is that when I get my hands on the first antiX 22 build I’ll be able to test it on my newest hardware too.

AntiX without a doubt uses the fewest resources. For me that makes a lot of sense because I really don’t need the fancy features in the other distributions.

--
Brian Masinick

[Moderator Brian Masinick]

Believe it or not, when I turned off the Dell Inspiron 5558 laptop and turned ON the Lenovo X201 laptop, I WAS able to BOOT antiX 13.2_386-full.iso! Mind you, back in those days, Debian-based distributions like ours (BEFORE the systemd conflicts), had a “thing” between Debian and the Mozilla teams about the graphics and licensing, so for those who can remember, we had Iceweasel (Firefox) and Iceape (Mozilla/Seamonkey). We also have a great difference in certificates, security and many other things.

With 13.2 I WAS able to browse yahoo.com and use Basic Yahoo Mail (minus the current features) but I was NOT able to get into this forum!

Now here with a slightly newer, “Jessie-based” antiX —

inxi -I
Info:      Processes: 137 Uptime: 25 min Memory: 469.4/2959.9MB
           Client: Shell (bash) inxi: 2.2.25 
root@antiX1:/etc# inxi -b
System:    Host: antiX1 Kernel: 4.0.5-antix.1-486-smp i686 (32 bit)
           Desktop: IceWM 1.3.8
           Distro: antiX-15-V_386-full Killah P 30 June 2015
Machine:   System: LENOVO product: 3249CTO v: ThinkPad X201 serial: R987CYZ
           Mobo: LENOVO model: 3249CTO serial: 1ZHWK09G2LZ
           Bios: LENOVO v: 6QET66WW (1.36 ) date: 05/31/2011
CPU:       Dual core Intel Core i7 M 620 (-HT-MCP-) speed/max: 1199/2667 MHz
Graphics:  Card: Intel Core Processor Integrated Graphics Controller
           Display Server: X.org 1.16.4 drivers: intel (unloaded: fbdev,vesa)
           tty size: 80x28 Advanced Data: N/A for root
Network:   Card-1: Intel 82577LM Gigabit Network Connection driver: e1000e
           Card-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi
Drives:    HDD Total Size: 128.0GB (4.8% used)
Info:      Processes: 137 Uptime: 26 min Memory: 470.1/2959.9MB
           Client: Shell (bash) inxi: 2.2.25

so with antiX-15-V on DVD I can actually get into this forum. I wouldn’t use this for everyday stuff unless updated, step by step to current.

Fun note: with the 13.2 “Wheezy” release, I tried it; as you may expect, leaping all the way from Wheezy to Bullseye is WAY too much of a leap; but a few “interesting” things did happen; alas, packaging conflicts, mostly concerning the lack of proper Bullseye authentications and certificates ultimately killed the experiment. With sufficient screwning around, adding in certificates, and possibly doing a one major release jump at a time for 3, 4, releases, MAYBE it’d be possible, but certainly more than it’s actually worth. You see, I DO actually have antiX 21 runit Base installed and working on this very same system; I’m just “messing around” on DVD with some really cool OLD distros from our past.

Because of modern security related issues, we really can’t use these old relics any more, not without updating a ton of packages with newer releases, However, 15-V is workable to the point that with the DVD and using Ceni for networking, I at least got in here today.

So for those of you with super old systems, there is a VERY SLIGHT possibility to get some old stuff working, AND if you REALLY carefully update from release to release OR run only from DVD you might be able to use old versions of antiX too!

My suggestion is to definitely try one of our currently supported releases before attempting any of the VERY CRAZY exercises that I am playing with today. Keep in mind that I have multiple hardware platforms, backups, numerous USB drives from which I can install or reinstall to correct disasters, and I also have sufficient experience to understand the messages I’m receiving. All of this is for experimentation, “brain teasing” to keep at least a few of my technical skills intact as I age, and wild curiosity; I only recommend this kind of whacky stuff if you have plenty of free time, extra hardware, software, backup alternatives, a sense of humor and curiosity; if lacking any of these, DON’T try doing what I’ve been doing; you can potentially destroy any existing systems, and in the worst possible scenario you can damage hardware. Have fun, but have the tools needed IF you want to take a wacky walk on the wild side; most people should NOT try this.

--
Brian Masinick

[Member marcelocripe]

To be fair, the antiX help menu texts are saying the same thing, in as few words as possible. It is just necessary to be terse to fit into the help menu.

As I wrote above “I am not able to communicate in a language other than Brazilian Portuguese and that I depend solely and exclusively on internet translators to try to communicate with all of you”, so I need to inform you that the automatic translation of the texts of the Christophe I am able to understand, already the automatic translation of the original texts, I am not able to understand. So much so that the translation and adaptation of the pt_BR language was based on the translation and adaptation of es, de, pt and fr_BE.
The text written by Christophe has details and a much more complete description, I believe this made the work of the translation program much easier and it is about clarity in the information that I am referring to. Now it is necessary for Peter Linu to confirm whether or not he is a native of the English language (if he wants to do that), for him to compare the original texts with Christophe’s texts to know whether or not he is able to understand all the text without take into account the detailed explanations that Christophe has given in this topic.
I usually say that there are several types of texts and forms of communication, being them texts to be understood by most people and texts to be understood by a specific group of people and in a much smaller amount.

Yes, this is true. Of course, if we use terse language terminology, it is vitally important to be extremely accurate and as clear as possible when using brevity; the same can be said when we add detail and explanation; both deserve accuracy and clarity.

Would it be a problem if Christophe’s texts were used for the Help menu in English?
The antix-bootscreen-helpmenu feature and so many others can and should be reviewed, corrected and improved, even by native English speakers, that’s why there are en_US, en_GB and so many other country-specific languages.

– – – – –

To be fair, the antiX help menu texts are saying the same thing, in as few words as possible. It is just necessary to be terse to fit into the help menu.

Como eu escrevei acima “eu não sou capaz de me comunicar em um idioma diferente do Português do Brasil e que dependo única e exclusivamente dos tradutores da internet para tentar me comunicar com todos vocês”, então eu preciso informar que a tradução automática dos textos do Christophe eu sou capaz de compreender, já a tradução automática dos textos originais, eu não sou capaz de compreender. Tanto é que a tradução e adaptação do idioma pt_BR foi baseada na tradução e adaptação do es, de, pt e fr_BE.
O texto escrito pelo Christophe possui detalhes e uma descrição muito mais completa, eu acredito que isso facilitou muito o trabalho do programa de tradução e é sobre a clareza nas informações que eu estou me referindo. Agora é preciso que o Peter Linu confirme se ele é um nativo ou não do idioma Inglês (se ele quiser fazer isso), para ele comparar os textos originais aos texto do Christophe para sabermos se ele é capaz ou não de compreender todo o texto sem levar em consideração as explicações detalhas que o Christophe fez neste tópico.
Eu costumo dizer que existem vários tipos de textos e formas de comunicação, sendo eles os textos para serem compreendidos pela a maioria das pessoas e os textos para serem compreendidos por um grupo específico de pessoas e em quantidade muito menor.

Yes, this is true. Of course, if we use terse language terminology, it is vitally important to be extremely accurate and as clear as possible when using brevity; the same can be said when we add detail and explanation; both deserve accuracy and clarity.

Por acaso teria algum problema se os textos do Christophe fossem utilizados para o menu de Ajuda de ajuda em Inglês?
O recurso antix-bootscreen-helpmenu e tantos outros podem e devem ser revisados, corrigidos e melhorados, inclusive por nativos do idioma Inglês, é por isso que exite o en_US, en_GB e tantos outros idiomas específicos por país.

[Member marcelocripe]

Thanx Christophe. Very helpful.
This is an example of what needs to be in the manual.

Christophe, agora eu sou obrigado a concordar com o Peter Linu.

Para efeito de comparação, eu vou colar abaixo os textos em idioma Inglês en_US e en_GB que estão no recurso antix-bootscreen-helpmenu

(Os dois URLs do Transifex estão no texto em Inglês.)

Número da entrada e o texto na íntegra:

(Os textos do Transifex estão no texto em Inglês.)

Todos aqui sabem muito bem que eu não sou capaz de me comunicar em um idioma diferente do Português do Brasil e que dependo única e exclusivamente dos tradutores da internet para tentar me comunicar com todos vocês. Eu não sei qual é o idioma nativo do Peter Linu, caso ele seja o um nativo de um dos idiomas Ingleses en_US ou en_GB e ele não esteja conseguindo compreender os textos destes idiomas que estão no menu de Ajuda que é possível acessar com o pressionamento da tecla F1 no menu de inicialização da ISO do antiX 21, então, eu deixo aqui mais uma vez o meu pedido e convite os nativos dos idiomas en_US e en_GB para fazerem o cadastro no Transifex e começarem a revisar e corrigir os textos nos respectivos idiomas, pois estará provado que os textos resumidos e extremamente simples são incompreensíveis para os nativos dos idiomas e que só servem para os programadores experientes e que não são compreensíveis para o usuário final.
Estas explicações do Christophe poderiam e deveriam estar no Transifex para quem sabe um dia chegarem até as ISOs do antiX. Pois não é a primeira vez que eu detecto nativos do idioma Inglês não conseguindo compreender os textos em seu próprio idioma, outro dia um usuário queria desinstalar o antiX clicando no menu “antiX auto remove”.

[Member marcelocripe]

Thanx Christophe. Very helpful.
This is an example of what needs to be in the manual.

Christophe, now I have to agree with Peter Linu.

For comparison, I’ll paste below the English language texts en_US and en_GB that are in the antix-bootscreen-helpmenu resource

Entry number and full text:

96
off ……… No Persistence / No Frugal

97
persist_all ….. Save rootfs in RAM, save home on disk (save root at shutdown)

98
persist_root …. Save rootfs and homefs in RAM then saved at shutdown

99
persist_static .. Save root and home on disk with homefs separate on disk

100
p_static_root .. Save rootfs and homefs on disk together

101
persist_home …. Only home persistence

102
frugal_persist .. Frugal with root in RAM and home on disk

103
frugal_root ….. Frugal with root and home in RAM then saved at shutdown

104
frugal_static … Frugal with root on disk and home separate on disk

105
f_static_root … Frugal with root and home on disk together

106
frugal_home ….. Frugal with only home persistence

107
frugal_only ….. Only Frugal, no persistence

Everyone here knows very well that I am not able to communicate in a language other than Brazilian Portuguese and that I depend solely and exclusively on internet translators to try to communicate with all of you. I don’t know what Peter Linu’s native language is, if he is a native of one of the English languages ​​en_US or en_GB and he is not able to understand the texts of these languages ​​that are in the Help menu that you can access by pressing the F1 key in the antiX 21 ISO boot menu, so I leave here once again my request and invite the natives of the en_US and en_GB languages ​​to register in Transifex and start reviewing and correcting the texts in their respective languages, because it will be proved that the summarized and extremely simple texts are incomprehensible for the natives of the languages ​​and that they only serve for the experienced programmers and that they are not understandable for the final user.
These explanations by Christophe could and should be on Transifex so that maybe one day it will reach the antiX ISOs. It’s not the first time I’ve detected natives of the English language not being able to understand the texts in their own language, the other day a user wanted to uninstall antiX by clicking on the “antiX auto remove” menu.

I am rather new to antiX, used it with much pleasure on my Pentium 4 desktop for a few months now. I recently decided to also try it out on an old laptop with an Intel Celeron processor. I downloaded ‭antiX-21_386-base.iso, checked sums and key, and burned a DVD. So I did a regular install from the DVD iso on the HD, set up ufw firewall afterwards, then connected to internet and started to update and install some applications.

But some problems started to emerge when I tried to install the 4.19 kernel through the Package Installer.
– First problem being, which may be relevant for the developers of antiX, I could not see which kernel had been installed in the Package Installer. In other words, it gave no clue as to what kernel had been installed (so I could not select a kernel to deinstall). Checking system info showed that it was indeed 4.9. I then tried to install 4.19 through the package installer. However, the window of the terminal closed very quickly and nothing had been installed. Rebooting also showed that nothing had been installed. Grub had not changed.
After some trial and error with fresh installs, and attempting boot repairs (I first thought the problem could be related to having another partition on the HD with an ubuntu distro on it, but I now doubt that this is the case), I finally had an installation of antiX where the Package Installer did show a mark for the kernel that had been installed first (4.9.0-294-486). I then installed the 4.19 pae kernel (The Celeron M420 had a pae flag in the list, so I thought that would be allright). To my surprise both the pae and non-pae version were being installed as I saw in the grub menu. I then also installed the 5.10 kernel (because of another problem I will discuss in separate message). This also went fine as all options were there in Grub afterwards. But to my surprise the package installer could not keep hold of that and again it suggested as if not one of the listed kernels there had been installed, though I new better as I tested using Grub options and PC information.

Any comments highly appreciated.

[Member olsztyn]

christophe wrote:

So, (until/unless this live situation is able to be fixed) does it work to install antiX to hdd, install the nvidia-legacy-340 pkg into the traditional installation, then make an ISO-snapshot. Then run the ISO-snapshot as a live-usb/frugal, with nvidia-legacy-340 “pre-built” into the live instance in that way?

Thank you Christophe…
I already tested this scenario as I similarly thought the ISO snapshot should faithfully replicate the working environment. I actually tested this on MX 21 -Fluxbox, which exhibited the same issue, before I even traditionally installed antiX, just for testing sake.
Unfortunately this route did not resolve this issue. Same happened. Therefore my conjecture was that this issue must be specifically attributed to Live boot process vs. traditionally installed.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Moderator christophe]

I like BobC’s step-by-step:

1. Download the iso file you want to burn, I something suggest https://sourceforge.net/projects/antix-linux/files/Final/antiX-21/antiX-21_x64-full.iso/download
2. Put your flashdrive in that you want to burn (have you got a 4 or 8 or 16 gb one to use?)
3. Run live-usb-maker from menu or app-select or control centre
4. select the right flashdrive
5. select the iso file
6. click next to burn it
7. wait till its finished, then wait another 30 seconds just to be sure.

BobC wrote:

You should have gotten a success box popup in front of that screen. If that didn’t appear, maybe it never really finished, or being a newbie, maybe it popped up and you didn’t notice. I suppose you could try booting it and run the checks shown below.

Else, if it didn’t come up, and/or didn’t create a valid bootable usb I’m guessing you are trying to make the USB from a corrupted system, and need to try something different.

I agree completely. Try to boot the stick. Does it boot?
Please do that & report back with your results.

• This reply was modified 9 months, 4 weeks ago by christophe. Reason: emphasized the waiting after 100% done notification - to make sure "really" done

confirmed antiX frugaler, since 2019

[Member iznit]

whether you can actually create a true and effective Live antiX instance through such process, starting from a traditionally installed antiX

Yes, following the part of my post you quoted…..

iznit wrote:
from your “installed” system [[[installed to virtual hard drive]]] you can choose “ISO Snapshot” [[[from the menu shown in your screenshot]]]. This will capture the running system into an ISO file. Then choose “Live USB Maker” [[[from the menu shown in your screenshot]]] and when that program launches, browse select that brand new ISO file as the source for creating the live USB.

…..if you choose choose “personal snapshot”, it produces [[I have tested]] a perfect result. Beforehand, do take the time to review [[[and probably edit]]] the “general” and “snapshot” excludes files, so you do not wind up with any surprises as to what files have NOT been preserved.

edit

Live antiX does not do such thing as it does not know on what hardware it will run, so it is designed to detect hardware during boot time and adapt accordingly to hardware of the machine on which it happens to boot.

Well I did not read the question carefully enough. My “perfect” result, I did not test whether it is hardware-specific. The snapshot program, I did look into the source code though. It injects a prebuilt “initrd.gz” file which I expect does contain the full range of supported hardawre modules [[[drivers]]].

• This reply was modified 9 months, 4 weeks ago by iznit.

[Member olsztyn]

Brian Masinick wrote:

I think you’re right on track and your thoughts are certainly consistent with a reasonable interpretation of our implementation. Only a code inspection and an informed developer could tell us more (I’m neither of these), so I can only provide the opinion that your thoughts make good sense.

Thank you Brian…
I am hoping some antiX developers will explain these when possible. I am still hoping I am wrong on my conjecture though. It was just based on basic observations of boot behavior difference between an actual antiX Live and an antiX Live produced from ISO snapshot of antiX running on a specific machine.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member olsztyn]

iznit wrote:

from your “installed” system [[[installed to virtual hard drive]]] you can choose “ISO Snapshot” [[[from the menu shown in your screenshot]]]. This will capture the running system into an ISO file. Then choose “Live USB Maker” [[[from the menu shown in your screenshot]]] and when that program launches, browse select that brand new ISO file as the source for creating the live USB.

This pretty much expected process to create Live antiX from a traditionally installed antiX… At this time I do not have any traditionally installed antiX on any of my laptops and I am running antiX Live across the board, but I will traditionally install and test it when time allows. However I would like to hear from experts whether you can actually create a true and effective Live antiX instance through such process, starting from a traditionally installed antiX…
I may likely be wrong in my this challenge, as I am not myself sure of this. I just have some doubts, using terminology of some other posters, so please prove me wrong:
– Traditionally installed antiX, as well as other (Linux) systems detect hardware during the install process and install just appropriate drivers corresponding to hardware. Live antiX does not do such thing as it does not know on what hardware it will run, so it is designed to detect hardware during boot time and adapt accordingly to hardware of the machine on which it happens to boot.
– Creating a Snapshot image from a traditionally installed system, which has configuration of drivers and other hardware support modules pre-established during such system install, will result in such snapshot image carrying a faithful image of the traditionally installed system. Having created a Live version from such snapshot, this Live antiX will boot fine on the same machine from which the snapshot was taken as it is an image reflecting that machine hardware. However being specific to that hardware, such Live may lack the flexibility of true Live to be initially agnostic of the hardware and instead to detect hardware during boot time.

Whether my above conjecture is indeed reflecting the antiX Live design or not – this becomes very interesting and important to know if we want to understand antiX.
Hopefully antiX experts will shed some light on this and will either confirm or disprove the above stated points…

• This reply was modified 10 months ago by olsztyn.
• This reply was modified 10 months ago by olsztyn.
• This reply was modified 10 months ago by olsztyn.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Moderator Brian Masinick]

My comments are relative to post #85759; that system boots, but you could not shut down.

Regarding the fact that one version (the live one) will boot, but not shut down, that’s what my suggestion pertains to; sudo poweroff ought to work.
If not, I’d try killing the init process (process 1).

That is:

PID TTY STAT TIME COMMAND
1 ? Ss 0:00 init [5]

Regarding the “installable image”, are you booting from the same (live) image that won’t shut down, and attempt to install from the same image, but it won’t install?

If yes, that’s really curious; if not, use the live image and attempt to install from it. If no, hopefully you’ve tried a few times to get an installable image.
If the current ones don’t work, try going back, maybe to 17 (or further back, if you can find one archived somewhere). I noted in one post that you’re attempting to install version 19.4. Try earlier versions (and other versions) for comparison; same or different behavior?

--
Brian Masinick

I received an Email with the following update:

Updated Debian 11: 11.4 released

————————————————————————
The Debian Project https://www.debian.org/
Updated Debian 11: 11.4 released press@debian.org
July 9th, 2022 https://www.debian.org/News/2022/20220709
————————————————————————

The Debian project is pleased to announce the fourth update of its
stable distribution Debian 11 (codename “bullseye”). This point release
mainly adds corrections for security issues, along with a few
adjustments for serious problems. Security advisories have already been
published separately and are referenced where available.

Please note that the point release does not constitute a new version of
Debian 11 but only updates some of the packages included. There is no
need to throw away old “bullseye” media. After installation, packages
can be upgraded to the current versions using an up-to-date Debian
mirror.

Those who frequently install updates from security.debian.org won’t have
to update many packages, and most such updates are included in the point
release.

New installation images will be available soon at the regular locations.

Upgrading an existing installation to this revision can be achieved by
pointing the package management system at one of Debian’s many HTTP
mirrors. A comprehensive list of mirrors is available at:

https://www.debian.org/mirror/list

Miscellaneous Bugfixes
———————-

This stable update adds a few important corrections to the following
packages:

+—————————+—————————————–+
| Package | Reason |
+—————————+—————————————–+
| apache2 [1] | New upstream stable release; fix HTTP |
| | request smuggling issue [CVE-2022- |
| | 26377], out-of-bounds read issues |
| | [CVE-2022-28330 CVE-2022-28614 |
| | CVE-2022-28615], denial of service |
| | issues [CVE-2022-29404 CVE-2022-30522], |
| | possible out-of-bounds read issue |
| | [CVE-2022-30556], possible IP-based |
| | authentication bypass issue [CVE-2022- |
| | 31813] |
| | |
| base-files [2] | Update /etc/debian_version for the 11.4 |
| | point release |
| | |
| bash [3] | Fix 1-byte buffer overflow read, |
| | causing corrupted multibyte characters |
| | in command substitutions |
| | |
| clamav [4] | New upstream stable release; security |
| | fixes [CVE-2022-20770 CVE-2022-20771 |
| | CVE-2022-20785 CVE-2022-20792 CVE-2022- |
| | 20796] |
| | |
| clementine [5] | Add missing dependency on libqt5sql5- |
| | sqlite |
| | |
| composer [6] | Fix code injection issue [CVE-2022- |
| | 24828]; update GitHub token pattern |
| | |
| cyrus-imapd [7] | Ensure that all mailboxes have a |
| | “uniqueid” field, fixing upgrades to |
| | version 3.6 |
| | |
| dbus-broker [8] | Fix buffer overflow issue [CVE-2022- |
| | 31212] |
| | |
| debian-edu-config [9] | Accept mail from the local network sent |
| | to root@; only create |
| | Kerberos host and service principals if |
| | they don’t yet exist; ensure libsss- |
| | sudo is installed on Roaming |
| | Workstations; fix naming and visibility |
| | of print queues; support krb5i on |
| | Diskless Workstations; squid: prefer |
| | DNSv4 lookups over DNSv6 |
| | |
| debian-installer [10] | Rebuild against proposed-updates; |
| | increase Linux kernel ABI to 16; |
| | reinstate some armel netboot targets |
| | (openrd) |
| | |
| debian-installer-netboot- | Rebuild against proposed-updates; |
| images [11] | increase Linux kernel ABI to 16; |
| | reinstate some armel netboot targets |
| | (openrd) |
| | |
| distro-info-data [12] | Add Ubuntu 22.10, Kinetic Kudu |
| | |
| docker.io [13] | Order docker.service after |
| | containerd.service to fix shutdown of |
| | containers; explicitly pass the |
| | containerd socket path to dockerd to |
| | make sure it doesn’t start containerd |
| | on its own |
| | |
| dpkg [14] | dpkg-deb: Fix unexpected end of file |
| | conditions on .deb extract; libdpkg: Do |
| | not restrict source:* virtual fields to |
| | installed packages; |
| | Dpkg::Source::Package::V2: Always fix |
| | the permissions for upstream tarballs |
| | (regression from DSA-5147-1] |
| | |
| freetype [15] | Fix buffer overflow issue [CVE-2022- |
| | 27404]; fix crashes [CVE-2022-27405 |
| | CVE-2022-27406] |
| | |
| fribidi [16] | Fix buffer overflow issues [CVE-2022- |
| | 25308 CVE-2022-25309]; fix crash |
| | [CVE-2022-25310] |
| | |
| ganeti [17] | New upstream release; fix several |
| | upgrade issues; fix live migration with |
| | QEMU 4 and “security_model” of |
| | “user” or “pool” |
| | |
| geeqie [18] | Fix Ctrl click inside of a block |
| | selection |
| | |
| gnutls28 [19] | Fix SSSE3 SHA384 miscalculation; fix |
| | null pointer deference issue [CVE-2021- |
| | 4209] |
| | |
| golang-github- | Fix null pointer dereference caused by |
| russellhaering- | crafted XML signatures [CVE-2020-7711] |
| goxmldsig [20] | |
| | |
| grunt [21] | Fix path traversal issue [CVE-2022- |
| | 0436] |
| | |
| hdmi2usb-mode-switch [22] | udev: Add a suffix to /dev/video device |
| | nodes to disambiguate them; move udev |
| | rules to priority 70, to come after 60- |
| | persistent-v4l.rules |
| | |
| hexchat [23] | Add missing dependency on python3-cffi- |
| | backend |
| | |
| htmldoc [24] | Fix infinite loop [CVE-2022-24191], |
| | integer overflow issues [CVE-2022- |
| | 27114] and heap buffer overflow issue |
| | [CVE-2022-28085] |
| | |
| knot-resolver [25] | Fix possible assertion failure in NSEC3 |
| | edge-case [CVE-2021-40083] |
| | |
| libapache2-mod-auth- | New upstream stable release; fix open |
| openidc [26] | redirect issue [CVE-2021-39191]; fix |
| | crash on reload / restart |
| | |
| libintl-perl [27] | Really install gettext_xs.pm |
| | |
| libsdl2 [28] | Avoid out-of-bounds read while loading |
| | malformed BMP file [CVE-2021-33657], |
| | and during YUV to RGB conversion |
| | |
| libtgowt [29] | New upstream stable release, to support |
| | newer telegram-desktop |
| | |
| linux [30] | New upstream stable release; increase |
| | ABI to 16 |
| | |
| linux-signed-amd64 [31] | New upstream stable release; increase |
| | ABI to 16 |
| | |
| linux-signed-arm64 [32] | New upstream stable release; increase |
| | ABI to 16 |
| | |
| linux-signed-i386 [33] | New upstream stable release; increase |
| | ABI to 16 |
| | |
| logrotate [34] | Skip locking if state file is world- |
| | readable [CVE-2022-1348]; make |
| | configuration parsing stricter in order |
| | to avoid parsing foreign files such as |
| | core dumps |
| | |
| lxc [35] | Update default GPG key server, fixing |
| | creating of containers using the |
| | “download” template |
| | |
| minidlna [36] | Validate HTTP requests to protect |
| | against DNS rebinding attacks |
| | [CVE-2022-26505] |
| | |
| mutt [37] | Fix uudecode buffer overflow issue |
| | [CVE-2022-1328] |
| | |
| nano [38] | Several bug fixes, including fixes for |
| | crashes |
| | |
| needrestart [39] | Make cgroup detection for services and |
| | user sessions cgroup v2 aware |
| | |
| network-manager [40] | New upstream stable release |
| | |
| nginx [41] | Fix crash when libnginx-mod-http-lua is |
| | loaded and init_worker_by_lua* is used; |
| | mitigate application layer protocol |
| | content confusion attack in the Mail |
| | module [CVE-2021-3618] |
| | |
| node-ejs [42] | Fix server-side template injection |
| | issue [CVE-2022-29078] |
| | |
| node-eventsource [43] | Strip sensitive headers on redirect to |
| | different origin [CVE-2022-1650] |
| | |
| node-got [44] | Don’t allow redirection to Unix socket |
| | [CVE-2022-33987] |
| | |
| node-mermaid [45] | Fix cross-site scripting issues |
| | [CVE-2021-23648 CVE-2021-43861] |
| | |
| node-minimist [46] | Fix prototype pollution issue |
| | [CVE-2021-44906] |
| | |
| node-moment [47] | Fix path traversal issue [CVE-2022- |
| | 24785] |
| | |
| node-node-forge [48] | Fix signature verification issues |
| | [CVE-2022-24771 CVE-2022-24772 |
| | CVE-2022-24773] |
| | |
| node-raw-body [49] | Fix potential denial of service issue |
| | in node-express, by using node-iconv- |
| | lite rather than node-iconv |
| | |
| node-sqlite3 [50] | Fix denial of service issue [CVE-2022- |
| | 21227] |
| | |
| node-url-parse [51] | Fix authentication bypass issues |
| | [CVE-2022-0686 CVE-2022-0691] |
| | |
| nvidia-cuda-toolkit [52] | Use OpenJDK8 snapshots for amd64 and |
| | ppc64el; check usability of the java |
| | binary; nsight-compute: Move the |
| | ‘sections’ folder to a multiarch |
| | location; fix nvidia-openjdk-8-jre |
| | version ordering |
| | |
| nvidia-graphics- | New upstream release; switch to |
| drivers [53] | upstream 470 tree; fix denial of |
| | service issues [CVE-2022-21813 |
| | CVE-2022-21814]; fix out-of-bounds |
| | write issue [CVE-2022-28181], out-of- |
| | bounds read issue [CVE-2022-28183], |
| | denial of service issues [CVE-2022- |
| | 28184 CVE-2022-28191 CVE-2022-28192] |
| | |
| nvidia-graphics-drivers- | New upstream release; fix out-of-bound |
| legacy-390xx [54] | write issues [CVE-2022-28181 CVE-2022- |
| | 28185] |
| | |
| nvidia-graphics-drivers- | New upstream stable release |
| tesla-418 [55] | |
| | |
| nvidia-graphics-drivers- | New upstream stable release; fix out- |
| tesla-450 [56] | of-bounds write issues [CVE-2022-28181 |
| | CVE-2022-28185], denial of service |
| | issue [CVE-2022-28192] |
| | |
| nvidia-graphics-drivers- | New upstream stable release |
| tesla-460 [57] | |
| | |
| nvidia-graphics-drivers- | New package, switching Tesla support to |
| tesla-470 [58] | upstream 470 tree; fix out-of-bounds |
| | write issue [CVE-2022-28181], out-of- |
| | bounds read issue [CVE-2022-28183], |
| | denial of service issues [CVE-2022- |
| | 28184 CVE-2022-28191 CVE-2022-28192] |
| | |
| nvidia-persistenced [59] | New upstream release; switch to |
| | upstream 470 tree |
| | |
| nvidia-settings [60] | New upstream release; switch to |
| | upstream 470 tree |
| | |
| nvidia-settings- | New package, switching Tesla support to |
| tesla-470 [61] | upstream 470 tree |
| | |
| nvidia-xconfig [62] | New upstream release |
| | |
| openssh [63] | seccomp: add pselect6_time64 syscall on |
| | 32-bit architectures |
| | |
| orca [64] | Fix usage with webkitgtk 2.36 |
| | |
| php-guzzlehttp-psr7 [65] | Fix improper header parsing [CVE-2022- |
| | 24775] |
| | |
| phpmyadmin [66] | Fix some SQL queries generating a |
| | server error |
| | |
| postfix [67] | New upstream stable release; do not |
| | override user set default_transport in |
| | postinst; if-up.d: do not error out if |
| | postfix can’t send mail yet |
| | |
| procmail [68] | Fix null pointer dereference |
| | |
| python-scrapy [69] | Don’t send authentication data with all |
| | requests [CVE-2021-41125]; don’t expose |
| | cookies cross-domain when redirecting |
| | [CVE-2022-0577] |
| | |
| ruby-net-ssh [70] | Fix authentication against systems |
| | using OpenSSH 8.8 |
| | |
| runc [71] | Honour seccomp defaultErrnoRet; do not |
| | set inheritable capabilities [CVE-2022- |
| | 29162] |
| | |
| samba [72] | Fix winbind start failure when “allow |
| | trusted domains = no” is used; fix MIT |
| | Kerberos authentication; fix share |
| | escape issue via mkdir race condition |
| | [CVE-2021-43566]; fix possible serious |
| | data corruption issue due to Windows |
| | client cache poisoning; fix |
| | installation on non-systemd systems |
| | |
| tcpdump [73] | Update AppArmor profile to allow access |
| | to *.cap files, and handle numerical |
| | suffix in filenames added by -W |
| | |
| telegram-desktop [74] | New upstream stable release, restoring |
| | functionality |
| | |
| tigervnc [75] | Fix GNOME desktop start up when using |
| | tigervncserver@.service; fix colour |
| | display when vncviewer and X11 server |
| | use different endianness |
| | |
| twisted [76] | Fix information disclosure issue with |
| | cross-domain redirects [CVE-2022- |
| | 21712], denial of service issue during |
| | SSH handshakes [CVE-2022-21716], HTTP |
| | request smuggling issues [CVE-2022- |
| | 24801] |
| | |
| tzdata [77] | Update timezone data for Palestine; |
| | update leap second list |
| | |
| ublock-origin [78] | New upstream stable release |
| | |
| unrar-nonfree [79] | Fix directory traversal issue |
| | [CVE-2022-30333] |
| | |
| usb.ids [80] | New upstream release; update included |
| | data |
| | |
| wireless-regdb [81] | New upstream release; remove diversion |
| | added by the installer, ensuring that |
| | files from the package are used |
| | |
+—————————+—————————————–+

1: https://packages.debian.org/src:apache2
2: https://packages.debian.org/src:base-files
3: https://packages.debian.org/src:bash
4: https://packages.debian.org/src:clamav
5: https://packages.debian.org/src:clementine
6: https://packages.debian.org/src:composer
7: https://packages.debian.org/src:cyrus-imapd
8: https://packages.debian.org/src:dbus-broker
9: https://packages.debian.org/src:debian-edu-config
10: https://packages.debian.org/src:debian-installer
11: https://packages.debian.org/src:debian-installer-netboot-images
12: https://packages.debian.org/src:distro-info-data
13: https://packages.debian.org/src:docker.io
14: https://packages.debian.org/src:dpkg
15: https://packages.debian.org/src:freetype
16: https://packages.debian.org/src:fribidi
17: https://packages.debian.org/src:ganeti
18: https://packages.debian.org/src:geeqie
19: https://packages.debian.org/src:gnutls28
20: https://packages.debian.org/src:golang-github-russellhaering-goxmldsig
21: https://packages.debian.org/src:grunt
22: https://packages.debian.org/src:hdmi2usb-mode-switch
23: https://packages.debian.org/src:hexchat
24: https://packages.debian.org/src:htmldoc
25: https://packages.debian.org/src:knot-resolver
26: https://packages.debian.org/src:libapache2-mod-auth-openidc
27: https://packages.debian.org/src:libintl-perl
28: https://packages.debian.org/src:libsdl2
29: https://packages.debian.org/src:libtgowt
30: https://packages.debian.org/src:linux
31: https://packages.debian.org/src:linux-signed-amd64
32: https://packages.debian.org/src:linux-signed-arm64
33: https://packages.debian.org/src:linux-signed-i386
34: https://packages.debian.org/src:logrotate
35: https://packages.debian.org/src:lxc
36: https://packages.debian.org/src:minidlna
37: https://packages.debian.org/src:mutt
38: https://packages.debian.org/src:nano
39: https://packages.debian.org/src:needrestart
40: https://packages.debian.org/src:network-manager
41: https://packages.debian.org/src:nginx
42: https://packages.debian.org/src:node-ejs
43: https://packages.debian.org/src:node-eventsource
44: https://packages.debian.org/src:node-got
45: https://packages.debian.org/src:node-mermaid
46: https://packages.debian.org/src:node-minimist
47: https://packages.debian.org/src:node-moment
48: https://packages.debian.org/src:node-node-forge
49: https://packages.debian.org/src:node-raw-body
50: https://packages.debian.org/src:node-sqlite3
51: https://packages.debian.org/src:node-url-parse
52: https://packages.debian.org/src:nvidia-cuda-toolkit
53: https://packages.debian.org/src:nvidia-graphics-drivers
54: https://packages.debian.org/src:nvidia-graphics-drivers-legacy-390xx
55: https://packages.debian.org/src:nvidia-graphics-drivers-tesla-418
56: https://packages.debian.org/src:nvidia-graphics-drivers-tesla-450
57: https://packages.debian.org/src:nvidia-graphics-drivers-tesla-460
58: https://packages.debian.org/src:nvidia-graphics-drivers-tesla-470
59: https://packages.debian.org/src:nvidia-persistenced
60: https://packages.debian.org/src:nvidia-settings
61: https://packages.debian.org/src:nvidia-settings-tesla-470
62: https://packages.debian.org/src:nvidia-xconfig
63: https://packages.debian.org/src:openssh
64: https://packages.debian.org/src:orca
65: https://packages.debian.org/src:php-guzzlehttp-psr7
66: https://packages.debian.org/src:phpmyadmin
67: https://packages.debian.org/src:postfix
68: https://packages.debian.org/src:procmail
69: https://packages.debian.org/src:python-scrapy
70: https://packages.debian.org/src:ruby-net-ssh
71: https://packages.debian.org/src:runc
72: https://packages.debian.org/src:samba
73: https://packages.debian.org/src:tcpdump
74: https://packages.debian.org/src:telegram-desktop
75: https://packages.debian.org/src:tigervnc
76: https://packages.debian.org/src:twisted
77: https://packages.debian.org/src:tzdata
78: https://packages.debian.org/src:ublock-origin
79: https://packages.debian.org/src:unrar-nonfree
80: https://packages.debian.org/src:usb.ids
81: https://packages.debian.org/src:wireless-regdb

Security Updates
—————-

This revision adds the following security updates to the stable release.
The Security Team has already released an advisory for each of these
updates:

+—————-+————————–+
| Advisory ID | Package |
+—————-+————————–+
| DSA-4999 [82] | asterisk [83] |
| | |
| DSA-5026 [84] | firefox-esr [85] |
| | |
| DSA-5034 [86] | thunderbird [87] |
| | |
| DSA-5044 [88] | firefox-esr [89] |
| | |
| DSA-5045 [90] | thunderbird [91] |
| | |
| DSA-5069 [92] | firefox-esr [93] |
| | |
| DSA-5074 [94] | thunderbird [95] |
| | |
| DSA-5086 [96] | thunderbird [97] |
| | |
| DSA-5090 [98] | firefox-esr [99] |
| | |
| DSA-5094 [100] | thunderbird [101] |
| | |
| DSA-5097 [102] | firefox-esr [103] |
| | |
| DSA-5106 [104] | thunderbird [105] |
| | |
| DSA-5107 [106] | php-twig [107] |
| | |
| DSA-5108 [108] | tiff [109] |
| | |
| DSA-5110 [110] | chromium [111] |
| | |
| DSA-5111 [112] | zlib [113] |
| | |
| DSA-5112 [114] | chromium [115] |
| | |
| DSA-5113 [116] | firefox-esr [117] |
| | |
| DSA-5114 [118] | chromium [119] |
| | |
| DSA-5115 [120] | webkit2gtk [121] |
| | |
| DSA-5116 [122] | wpewebkit [123] |
| | |
| DSA-5117 [124] | xen [125] |
| | |
| DSA-5118 [126] | thunderbird [127] |
| | |
| DSA-5119 [128] | subversion [129] |
| | |
| DSA-5120 [130] | chromium [131] |
| | |
| DSA-5121 [132] | chromium [133] |
| | |
| DSA-5122 [134] | gzip [135] |
| | |
| DSA-5123 [136] | xz-utils [137] |
| | |
| DSA-5124 [138] | ffmpeg [139] |
| | |
| DSA-5125 [140] | chromium [141] |
| | |
| DSA-5127 [142] | linux-signed-amd64 [143] |
| | |
| DSA-5127 [144] | linux-signed-arm64 [145] |
| | |
| DSA-5127 [146] | linux-signed-i386 [147] |
| | |
| DSA-5127 [148] | linux [149] |
| | |
| DSA-5128 [150] | openjdk-17 [151] |
| | |
| DSA-5129 [152] | firefox-esr [153] |
| | |
| DSA-5130 [154] | dpdk [155] |
| | |
| DSA-5131 [156] | openjdk-11 [157] |
| | |
| DSA-5132 [158] | ecdsautils [159] |
| | |
| DSA-5133 [160] | qemu [161] |
| | |
| DSA-5134 [162] | chromium [163] |
| | |
| DSA-5136 [164] | postgresql-13 [165] |
| | |
| DSA-5137 [166] | needrestart [167] |
| | |
| DSA-5138 [168] | waitress [169] |
| | |
| DSA-5139 [170] | openssl [171] |
| | |
| DSA-5140 [172] | openldap [173] |
| | |
| DSA-5141 [174] | thunderbird [175] |
| | |
| DSA-5142 [176] | libxml2 [177] |
| | |
| DSA-5143 [178] | firefox-esr [179] |
| | |
| DSA-5145 [180] | lrzip [181] |
| | |
| DSA-5147 [182] | dpkg [183] |
| | |
| DSA-5148 [184] | chromium [185] |
| | |
| DSA-5149 [186] | cups [187] |
| | |
| DSA-5150 [188] | rsyslog [189] |
| | |
| DSA-5151 [190] | smarty3 [191] |
| | |
| DSA-5152 [192] | spip [193] |
| | |
| DSA-5153 [194] | trafficserver [195] |
| | |
| DSA-5154 [196] | webkit2gtk [197] |
| | |
| DSA-5155 [198] | wpewebkit [199] |
| | |
| DSA-5156 [200] | firefox-esr [201] |
| | |
| DSA-5157 [202] | cifs-utils [203] |
| | |
| DSA-5158 [204] | thunderbird [205] |
| | |
| DSA-5159 [206] | python-bottle [207] |
| | |
| DSA-5160 [208] | ntfs-3g [209] |
| | |
| DSA-5161 [210] | linux-signed-amd64 [211] |
| | |
| DSA-5161 [212] | linux-signed-arm64 [213] |
| | |
| DSA-5161 [214] | linux-signed-i386 [215] |
| | |
| DSA-5161 [216] | linux [217] |
| | |
| DSA-5162 [218] | containerd [219] |
| | |
| DSA-5163 [220] | chromium [221] |
| | |
| DSA-5164 [222] | exo [223] |
| | |
| DSA-5165 [224] | vlc [225] |
| | |
| DSA-5166 [226] | slurm-wlm [227] |
| | |
| DSA-5167 [228] | firejail [229] |
| | |
| DSA-5168 [230] | chromium [231] |
| | |
| DSA-5169 [232] | openssl [233] |
| | |
| DSA-5171 [234] | squid [235] |
| | |
| DSA-5172 [236] | firefox-esr [237] |
| | |
| DSA-5174 [238] | gnupg2 [239] |
| | |
+—————-+————————–+

82: https://www.debian.org/security/2021/dsa-4999
83: https://packages.debian.org/src:asterisk
84: https://www.debian.org/security/2021/dsa-5026
85: https://packages.debian.org/src:firefox-esr
86: https://www.debian.org/security/2022/dsa-5034
87: https://packages.debian.org/src:thunderbird
88: https://www.debian.org/security/2022/dsa-5044
89: https://packages.debian.org/src:firefox-esr
90: https://www.debian.org/security/2022/dsa-5045
91: https://packages.debian.org/src:thunderbird
92: https://www.debian.org/security/2022/dsa-5069
93: https://packages.debian.org/src:firefox-esr
94: https://www.debian.org/security/2022/dsa-5074
95: https://packages.debian.org/src:thunderbird
96: https://www.debian.org/security/2022/dsa-5086
97: https://packages.debian.org/src:thunderbird
98: https://www.debian.org/security/2022/dsa-5090
99: https://packages.debian.org/src:firefox-esr
100: https://www.debian.org/security/2022/dsa-5094
101: https://packages.debian.org/src:thunderbird
102: https://www.debian.org/security/2022/dsa-5097
103: https://packages.debian.org/src:firefox-esr
104: https://www.debian.org/security/2022/dsa-5106
105: https://packages.debian.org/src:thunderbird
106: https://www.debian.org/security/2022/dsa-5107
107: https://packages.debian.org/src:php-twig
108: https://www.debian.org/security/2022/dsa-5108
109: https://packages.debian.org/src:tiff
110: https://www.debian.org/security/2022/dsa-5110
111: https://packages.debian.org/src:chromium
112: https://www.debian.org/security/2022/dsa-5111
113: https://packages.debian.org/src:zlib
114: https://www.debian.org/security/2022/dsa-5112
115: https://packages.debian.org/src:chromium
116: https://www.debian.org/security/2022/dsa-5113
117: https://packages.debian.org/src:firefox-esr
118: https://www.debian.org/security/2022/dsa-5114
119: https://packages.debian.org/src:chromium
120: https://www.debian.org/security/2022/dsa-5115
121: https://packages.debian.org/src:webkit2gtk
122: https://www.debian.org/security/2022/dsa-5116
123: https://packages.debian.org/src:wpewebkit
124: https://www.debian.org/security/2022/dsa-5117
125: https://packages.debian.org/src:xen
126: https://www.debian.org/security/2022/dsa-5118
127: https://packages.debian.org/src:thunderbird
128: https://www.debian.org/security/2022/dsa-5119
129: https://packages.debian.org/src:subversion
130: https://www.debian.org/security/2022/dsa-5120
131: https://packages.debian.org/src:chromium
132: https://www.debian.org/security/2022/dsa-5121
133: https://packages.debian.org/src:chromium
134: https://www.debian.org/security/2022/dsa-5122
135: https://packages.debian.org/src:gzip
136: https://www.debian.org/security/2022/dsa-5123
137: https://packages.debian.org/src:xz-utils
138: https://www.debian.org/security/2022/dsa-5124
139: https://packages.debian.org/src:ffmpeg
140: https://www.debian.org/security/2022/dsa-5125
141: https://packages.debian.org/src:chromium
142: https://www.debian.org/security/2022/dsa-5127
143: https://packages.debian.org/src:linux-signed-amd64
144: https://www.debian.org/security/2022/dsa-5127
145: https://packages.debian.org/src:linux-signed-arm64
146: https://www.debian.org/security/2022/dsa-5127
147: https://packages.debian.org/src:linux-signed-i386
148: https://www.debian.org/security/2022/dsa-5127
149: https://packages.debian.org/src:linux
150: https://www.debian.org/security/2022/dsa-5128
151: https://packages.debian.org/src:openjdk-17
152: https://www.debian.org/security/2022/dsa-5129
153: https://packages.debian.org/src:firefox-esr
154: https://www.debian.org/security/2022/dsa-5130
155: https://packages.debian.org/src:dpdk
156: https://www.debian.org/security/2022/dsa-5131
157: https://packages.debian.org/src:openjdk-11
158: https://www.debian.org/security/2022/dsa-5132
159: https://packages.debian.org/src:ecdsautils
160: https://www.debian.org/security/2022/dsa-5133
161: https://packages.debian.org/src:qemu
162: https://www.debian.org/security/2022/dsa-5134
163: https://packages.debian.org/src:chromium
164: https://www.debian.org/security/2022/dsa-5136
165: https://packages.debian.org/src:postgresql-13
166: https://www.debian.org/security/2022/dsa-5137
167: https://packages.debian.org/src:needrestart
168: https://www.debian.org/security/2022/dsa-5138
169: https://packages.debian.org/src:waitress
170: https://www.debian.org/security/2022/dsa-5139
171: https://packages.debian.org/src:openssl
172: https://www.debian.org/security/2022/dsa-5140
173: https://packages.debian.org/src:openldap
174: https://www.debian.org/security/2022/dsa-5141
175: https://packages.debian.org/src:thunderbird
176: https://www.debian.org/security/2022/dsa-5142
177: https://packages.debian.org/src:libxml2
178: https://www.debian.org/security/2022/dsa-5143
179: https://packages.debian.org/src:firefox-esr
180: https://www.debian.org/security/2022/dsa-5145
181: https://packages.debian.org/src:lrzip
182: https://www.debian.org/security/2022/dsa-5147
183: https://packages.debian.org/src:dpkg
184: https://www.debian.org/security/2022/dsa-5148
185: https://packages.debian.org/src:chromium
186: https://www.debian.org/security/2022/dsa-5149
187: https://packages.debian.org/src:cups
188: https://www.debian.org/security/2022/dsa-5150
189: https://packages.debian.org/src:rsyslog
190: https://www.debian.org/security/2022/dsa-5151
191: https://packages.debian.org/src:smarty3
192: https://www.debian.org/security/2022/dsa-5152
193: https://packages.debian.org/src:spip
194: https://www.debian.org/security/2022/dsa-5153
195: https://packages.debian.org/src:trafficserver
196: https://www.debian.org/security/2022/dsa-5154
197: https://packages.debian.org/src:webkit2gtk
198: https://www.debian.org/security/2022/dsa-5155
199: https://packages.debian.org/src:wpewebkit
200: https://www.debian.org/security/2022/dsa-5156
201: https://packages.debian.org/src:firefox-esr
202: https://www.debian.org/security/2022/dsa-5157
203: https://packages.debian.org/src:cifs-utils
204: https://www.debian.org/security/2022/dsa-5158
205: https://packages.debian.org/src:thunderbird
206: https://www.debian.org/security/2022/dsa-5159
207: https://packages.debian.org/src:python-bottle
208: https://www.debian.org/security/2022/dsa-5160
209: https://packages.debian.org/src:ntfs-3g
210: https://www.debian.org/security/2022/dsa-5161
211: https://packages.debian.org/src:linux-signed-amd64
212: https://www.debian.org/security/2022/dsa-5161
213: https://packages.debian.org/src:linux-signed-arm64
214: https://www.debian.org/security/2022/dsa-5161
215: https://packages.debian.org/src:linux-signed-i386
216: https://www.debian.org/security/2022/dsa-5161
217: https://packages.debian.org/src:linux
218: https://www.debian.org/security/2022/dsa-5162
219: https://packages.debian.org/src:containerd
220: https://www.debian.org/security/2022/dsa-5163
221: https://packages.debian.org/src:chromium
222: https://www.debian.org/security/2022/dsa-5164
223: https://packages.debian.org/src:exo
224: https://www.debian.org/security/2022/dsa-5165
225: https://packages.debian.org/src:vlc
226: https://www.debian.org/security/2022/dsa-5166
227: https://packages.debian.org/src:slurm-wlm
228: https://www.debian.org/security/2022/dsa-5167
229: https://packages.debian.org/src:firejail
230: https://www.debian.org/security/2022/dsa-5168
231: https://packages.debian.org/src:chromium
232: https://www.debian.org/security/2022/dsa-5169
233: https://packages.debian.org/src:openssl
234: https://www.debian.org/security/2022/dsa-5171
235: https://packages.debian.org/src:squid
236: https://www.debian.org/security/2022/dsa-5172
237: https://packages.debian.org/src:firefox-esr
238: https://www.debian.org/security/2022/dsa-5174
239: https://packages.debian.org/src:gnupg2

Removed packages
—————-

The following packages were removed due to circumstances beyond our
control:

+———————+——————————-+
| Package | Reason |
+———————+——————————-+
| elog [240] | Unmaintained; security issues |
| | |
| python-hbmqtt [241] | Unamintained and broken |
| | |
+———————+——————————-+

240: https://packages.debian.org/src:elog
241: https://packages.debian.org/src:python-hbmqtt

Debian Installer
—————-

The installer has been updated to include the fixes incorporated into
stable by the point release.

URLs
—-

The complete lists of packages that have changed with this revision:

https://deb.debian.org/debian/dists/bullseye/ChangeLog

The current stable distribution:

https://deb.debian.org/debian/dists/stable/

Proposed updates to the stable distribution:

https://deb.debian.org/debian/dists/proposed-updates

stable distribution information (release notes, errata etc.):

https://www.debian.org/releases/stable/

Security announcements and information:

https://www.debian.org/security/

About Debian
————

The Debian Project is an association of Free Software developers who
volunteer their time and effort in order to produce the completely free
operating system Debian.

Contact Information
——————-

For further information, please visit the Debian web pages at
https://www.debian.org/, send mail to , or contact the
stable release team at .

--
Brian Masinick

Hiyall,
I’m trying to put the above on another computer. I created the USB, inserted it, F12…and it boots into the original OS (full).
How do I get the ‘Live’ icon to show?

Live-USB = zzz-IceWM-antiX21-runit-64-base: static persistence
VirtualBox= zzz-IceWM-antiX21-runit-64-base