#debian-1-1 — Public Fediverse posts

Debian 11 Bullseye raggiunge la fine del supporto LTS ufficiale. Scopri cosa cambia da settembre e quali sono le opzioni per continuare a ricevere aggiornamenti. #Debian #Linux #Bullseye #Debian11 #OpenSource https://www.linuxeasy.org/debian-11-bullseye-termina-il-supporto-lts-cosa-cambia-e-come-aggiornare/

Debian 11 LTS ends on August 31, 2026. Discover upgrade options and extended paid support details for enterprises still running the older Linux version.

#Debian11 #Linux #CyberSecurity #OpenSource #TechNews

http://securityonline.info/debian-11-lts-ends-upgrade/?utm_source=mastodon&utm_medium=jetpack_social

🛑 Debian 11 „Bullseye” a ajuns la sfârșitul duratei de viață (EOL) și nu mai primește suport oficial!

Publicația Linuxiac informează că versiunea Debian 11 „Bullseye” (lansată inițial în august 2021) a ajuns la finalul perioadei sale de suport Long-Term Support (LTS), ceea ce înseamnă că proiectul Debian a încetat furnizarea actualizărilor de securitate și a remedierilor de erori pentru această distribuție.

✨ Punctele cheie ale acestei tranziții:

⚠️ Fără actualizări de securitate:
• Echipa de securitate Debian și echipa LTS nu mai produc pachete de securitate pentru Debian 11, expunând sistemele care continuă să o ruleze la posibile vulnerabilități (CVE-uri) necorectate.

🔄 Recomandare de upgrade:
• Administratorii de sistem și utilizatorii sunt îndemnați insistent să facă trecerea la o versiune suportată — Debian 12 „Bookworm” (care beneficiază de suport LTS activ) sau Debian 13 „Trixie”.

🌐 Opțiunea Freexian ELTS (Extended LTS):
• Pentru organizațiile care nu pot efectua un upgrade imediat, singura opțiune de a continua să primească patch-uri de securitate critice este serviciul comercial terț Extended LTS (ELTS) oferit de compania Freexian.

📌 Comandă rapidă pentru verificarea versiunii curente:

Dacă doriți să verificați ce versiune de Debian rulează pe serverul dumneavoastră:

Bash
lsb_release -a
# sau
cat /etc/os-release
#Debian #Debian11 #Bullseye #Linux #SysAdmin #EndofLife #Linuxiac #CyberSecurity #OpenSource #TechNews

Debian 1.1.4 on 86Box with Socket 7 (Dual Voltage) [1996]

Debian 1.1.4 is the first stable version of this Linux distribution that was released on June 17th, 1996, under the codename “Buzz”. This version of Debian uses Linux version 2.0, and it provides you with a minimal X11 server (XFree86).

Our focus in this article is testing Debian 1.1.4 on an 86Box emulated machine with a Socket 7 (Dual Voltage) [1996] motherboard. You can download it from here. We have also extracted the required floppy disk files, which you can download here.

We’ve configured the virtual machine as follows:

We’ve configured a virtual machine to run with:

• Machine type: [1996] Socket 7 (Dual Voltage)
• Machine: [i430VX] Azza PT-5IV
• CPU: Intel Pentium @ 166 MHz
• Memory: 128 MB
• Video: [PCI] S3 Trio64 (Phoenix)
• Keyboard: AT Keyboard
• Mouse: Microsoft Serial Mouse (COM1)
• Sound card: [ISA16] Gravis Ultrasound
• Floppy disk controller: Internal device
• Hard disk controller 1: Internal device
• New hard disk: RH5.vhd
  • C/H/S: 2080/16/63
  • Size: 1024 MB
  • Bus: IDE
  • Channel: 0:0
• CD-ROM drive 1: MATSHITA CD-ROM CR-583 1.07 (8x)

Once everything is configured as above, we can now start the virtual machine. First, insert both the boot floppy disk to the drive and the Debian 1.1.4 ISO to the CD-ROM reader, then set the BIOS to recognize the floppy disk.

After that, let it boot to the Debian 1.1 installer, inserting the root floppy disk in the process.

After that, we’re asked to create partitions for the Debian installation. We’ve selected /dev/hda as the disk drive, which is the first drive on primary IDE controller. Afterwards, we’ve created two partitions:

• /dev/hda1: Linux, 980.44 MB, bootable
• /dev/hda2: Linux Swap, 43.32 MB

Finally, we’ve written the partition tables so that the installer can recognize our newly created partitions, which we will format to be usable in the installation.

Now, we will initialize and activate the swap partition, which will be used by Debian 1.1.4. After the swap partition has been activated, we’re told to select a partition to initialize the EXT2 file system. We’ve chosen the Linux partition, which is the only partition that we’ve set up on this disk.

After the file system was created, we’ve mounted the root filesystem so that the installer will be able to install the minimal base system from the three base floppy disks.

Now, we’ll install the base system from the three floppy disks (base14-1.bin through base14-3.bin) inserted to the first floppy drive, /dev/fd0.

After that, we’ll install the kernel to the new system. Insert the boot floppy disk, then proceed.

Now, you’ll be asked if you need some additional modules. Since we don’t have any extra hardware that requires the use of the available modules, just press ENTER when you see the below screen.

After that, you’ll be asked to provide both the keyboard layout (which we’ve answered Yes here) and the timezone.

The hostname and the network setup comes next. We’ve selected the appropriate hostname, and this system is intentionally set up not to connect to a network, so we’ve answered No to the network connection question.

Afterwards, the bootloader installation comes next. We’ve set up the LILO bootloader so that it installs to the master boot record of /dev/sda, which is the disk that has our newly-installed system, along with making /dev/sda1 the default boot entry.

After that, we restart the machine after ejecting the boot floppy from the floppy drive, since we don’t intend to create a “boot floppy”.

The new installation booted up to the prompt where we’re asked to provide both the root password and info for a new user that will be created. The password must be at least 6 characters long for it to be accepted.

Package installation comes next, but we’ll have to set up dselect so that it reads the Debian 1.1.4 CD-ROM and the packages contained within. The kernel boot messages that we’ve seen indicates that /dev/hdb is the CD-ROM reader, which we will use.

We will go to “Access”, then provide the above path to the block device that points to the CD-ROM reader. Afterwards, we let it detect the packages for both the stable and the contrib sections from /debian/stable/binary-i386 and /debian/contrib/binary-i386, respectively. However, since this CD-ROM doesn’t contain non-free and local sections, we leave them blank.

Now, go to “Update”, and see it recognize the package list.

Now, we’ll go to “Select”, which lets us select packages that we want to install or remove. We have marked all LaTeX-related packages as removed by pressing the minus sign on our keyboard when those packages are highlighted. To find them, press the slash key, then write latex or tex, and remove all related packages. This saves the installation time and disk space.

After that, we’ll install XFree86 3.1.2 and its S3 server, FVWM2, GWM, and various X11-related packages by pressing + on the keyboard.

After that, press ENTER, and remove the remaining LaTeX packages that are dependencies. Keep pressing ENTER and marking dependent packages until pressing ENTER takes you to the main menu, with “Install” highlighted. Now, we’ll install packages.

When setting up packages, you’ll be prompted to set up a variety of packages yourself, such as the mail server. Occasionally, you may see the “file modified” prompts, which you’ll have to answer N. As for the mail server, press 5 then ENTER. Keep answering with defaults until you get to the XFree86 configuration.

Now, we are in the XFree86 configuration, with the mouse setup being the first section. Since we have selected Microsoft Mouse (2 buttons, COM1) during the virtual machine configuration, we’ve selected 1, then disabled ChordMiddle (for old Logitech mice using Microsoft Mouse protocol) and enabled Emulate3Buttons (press LEFT and RIGHT mouse buttons to emit MIDDLE click event). After that, we’ve specified /dev/cua0 as the mouse block device, which corresponds to COM1 that the mouse was connected to.

After that, we will configure the monitor sync frequencies. Since we’re on a virtual machine, selecting the monitor sync frequencies didn’t matter, as long as they grant us access to higher resolutions, like 1024×768 that we’ll set up.

After that, the video card configuration comes. We have installed the S3 Trio64 graphics card to this machine, so we will have to browse the video card database until we found the S3-Trio64 (generic) entry. After that, we’ve specified 123 as the graphics card ID, and it says that the XFree86 S3 server will be used.

Select the accelerated XFree86 S3 server by pressing 5, then specify the video RAM that is installed to the graphics card. For instance, we’ve selected 4096 KB because the card was configured to use this amount of video RAM.

The configuration program then asks you if you want to extract the probed clock information. Since this isn’t required, we just answer n to the question, which means that clock information won’t be parsed. Change all modes (256 colors, 16-bit colors, and 24-bit colors) so that 1024×768 will only be used.

Let the configuration program write the configuration file, but don’t test the X server yet. Ignore the package configuration error that appears, and answer N or O to the question that says that the Xserver file has been modified, since answering Y or I can invalidate your X server configuration. Enable xdm, but don’t start it yet.

Afterwards, go to “Config” and “Remove”, and let them perform remaining configuration and clean-up operations, then exit the dselect program.

You should see the login screen like below.

Since the serial port doesn’t seem to configure properly during system boot, we’ll have to manually run the below command, which causes the serial port to be recognized. Ensure that the serial port works by using cat /dev/cua0, then moving the mouse. If everything works, press CTRL + C, then execute reset in case garbled characters appear when you’re writing commands.

The command you’ll have to execute to configure the serial port is setserial -b /dev/cua0 auto_irq autoconfig session_lockout. If xdm works after a reboot but you can’t move the mouse, press ALT + F3, use this command, verify that the mouse works, then go back to the X server using ALT + F1.

Once the mouse works, now we can start the X server using startx. The X server works!

We can verify that xlock’s modes work, such as xlock -mode flag. It shows a waving “LINUX” word in a nice color hue gradient.

To run GWM, exit the X server by pressing CTRL + ALT + Backspace, then edit the /etc/X11/window-managers file using vi to point to the GWM binary path (/usr/X11R6/bin/gwm).

Then, start the X server again. Below shows a demo of the GWM window manager.

@prsfalken jaja el #Debian11 es oldstable ahora, el LTS termina en agosto/2026.

Igual sí, debería haber hecho el upgrade hace tiempo :P

Uih, was für ein Aufwand 😱

#RaspberryPiOS: Inplace-Upgrade auf aktuelle Bookworm-Basis | heise online https://www.heise.de/hintergrund/Raspberry-Pi-OS-InPlace-Upgrade-von-Bullseye-auf-Bookworm-wagen-9999516.html #Linux :tux: #OpenSource #Debian :debian: #DebianBullseye #Debian11 #DebianBookworm #Debian12

Because my web host has increased the prices, I have rented a #vServer again, although I lack the motivation to constantly configure it. I had already decided some time ago to try #Yunohost in this case.

But I'm already annoyed because I had the #VPS installed with #Debian12 and Yunohost requires #Debian11. I'll try it anyway, but I'll be pretty annoyed if it goes wrong.

Weil mein Webhoster die Preise erhöht hat, habe ich mir nun doch wieder einen #vServer gemietet, obwohl mir die Motivation für dessen ständiger Konfiguration fehlt. Schon vor geraumer Zeit hatte ich für diesen Fall beschlossen, dann einmal #Yunohost auszuprobieren.

Aber ich bin schon jetzt genervt, weil ich den #VPS mit #Debian12 installieren ließ und Yunohost #Debian11 verlangt. Ich werde es trotzdem versuchen, werde aber ziemlich angefressen sein, wenn es schiefgeht. 😤

Cielo de #Soria (la semana pasada) #viernesdeescritorio #debian11 #cinammon

Does anyone here know anything about why my #proxmox VMs for #debian12 just *will not* run cloud-init?

I have downloaded the "genericcloud" images and configured a cloudinit disk on proxmox but unlike when I did the same thing with #debian11 no cloudinit things happen on boot, so no hostname SSH keys etc.

Upgraded a virtual server from #Debian11 to #Debian12 and it worked perfectly, no errors during the upgrade or on reboot. Currently upgrading a laptop that my wife tends to use, leaving only one laptop to go and my two core servers - one at home and one remote. Everything else has been upgraded for months, but I've held back on the servers for a while to avoid any disruption.

Pro tip: you can upgrade #DreamCompute's #Debian11 image to #Debian12, I just did it a few hours ago by following #Debian's release notes upgrade guide. There might be a #Linux kernel listed as a dropped package, but if you're using a newer one you can probably remove it just fine. Back up your configs and installed packages first, though.

#selfhosting #DreamHost

I'm on the fence, should I leave #OpenMediaVault that's on #Debian11 or switch to #Debian12 and just use the command line instead of a webui?

Edit: I use it as a nfs server, samba server, and running my docker services.

@f3kh6f

Hier, gerade gefunden, gutes Video für Neuinstallation #mailman3 auf #debian11

https://www.youtube.com/watch?v=mNvfgHi7shg (09.10.2021)

Ich werde es (auf neuem Server) so probieren, die alten Datenbank + Daten zu migrieren.

Beachte unbedingt die zahlreichen Kommentare unter dem - flotten - Video.

Shapiro (mailman3) empfiehlt allerdings die Installation mit venv, siehe https://docs.mailman3.org/en/latest/install/install.html

Das Video erscheint mir jedenfalls sehr brauchbar. Als ich mit mailman3 anfing, existierte das nicht.

@j5s7 We (the three of us including you) have similar resource and usage profiles. It might be his install of Ubuntu and the Snap image he has. I'm on #Qubes with #Debian11 AppVMs so different OS. I have slowness issues on some sites like WormHole.App. So mine isn't as driven as his situation.

Looks like I'll be staying on #Debian11 for our #Mastodon instances. While you *can* install node.js v16, #Debian12 makes v18 the default, and which means a bunch of extra work.

https://github.com/mastodon/mastodon/issues/20968

Kdybych tu měl čistě náhodou zkušeného linuxáka, který umí upgradnout Debian 11 na dvanáctku a nerozbít přitom Mastodon, a který by mi s tím chtěl helfnout, byl bych moc rád. Ozvěte se. Díky.

#debian11 #upgrade

A Step-by-Step Guide To Upgrade To Debian 12 From Debian 11 #Debian12 #DebianBookworm #Debian11 #DebianBullseye #UpgradeDebian #Linux #Linuxadmin #Linuxhowto
https://ostechnix.com/upgrade-to-debian-12-from-debian-11/

Ya hablamos de #debian 12 y ahora le toca a #huayra 6 que ya está disponible

https://youtu.be/OeHOBLoZKhQ

#huayra6 #debian11 #mate #educacion

Bande annonce de l'Emmabuntüs DE 4

https://peertube.fr/w/3fCAureH3yxT4x2kEhsvGH

EmmaDE 4 installation Calamares

https://peertube.fr/w/2xUPDeLLkgoKSNjBjbHKfJ