-
Search Results
-
Prezados.
É com grande satisfação que compartilho a minha primeira remasterização do antiX 21 com o Kernel 4.4.0-296.
As duas remasterizações foram feitas a partir das imagens ISO “antiX-21_386-full.iso” e “antiX-21_x64-full.iso”, ambas com o sistema de inicialização de serviços SysVinit.
O objetivo destas remasterizações é de podermos ter disponíveis o antiX 21 de 32 bits e 64 bits prontos para inicializar com o Kernel 4.4.0-296. Eu removi os outros dois núcleos, o Kernel 4.9.0-279 e o Kernel 5.10.57.
Apesar do anúncio do @anticapitalista, no dia 07 de fevereiro de 2022, sobre o fim da vida útil do kernel 4.4, no tópico em idioma Inglês 4.4 kernel has reached EOL (End of life), o Kernel 4.4 é o que consegue inicializar na maioria das placas-mães que possuem placa de vídeo SIS e Via.
A única alteração que eu fiz, além do Kernel, foi corrigir o texto que é exibido no submenu do “Menu Pessoal”, ou seja, onde está escrito “Vídeos de Ajuda do Menu Pessoal” na ISO original do antiX, eu alterei para “Vídeo de Ajuda do Menu Pessoal” em idioma Português do Brasil. Infelizmente, no passado, eu enviei o texto no plural para o @anticapitalista, pois eu achava que seriam vários vídeos e na verdade é apenas um vídeo ensinando como adicionar ou remover os submenus do “Menu Pessoal”.
Estas remasterizações estão muito aquém das ISOs pseudo-antix-19 legacy bet3 com Kernel 4.4.0-264 que o @Xecure construiu a partir do “Build-iso”, que eu não tenho a mínima ideia de como utilizar o “Build-iso”.
Eu gostaria de agradecer a todas as pessoas que compartilham os seus conhecimentos para o bem das outras pessoas aqui no fórum. Aproveito para fazer um agradecimento especial ao @ensabahnur, o criador do respin Pin Linux OS, que me guiou e me ensinou a fazer cada etapa da remasterização destas ISOs, sem estes ensinamentos, estas ISOs não existiriam. Muito obrigado, @ensabahnur. Eu agradeço também ao @anticapitalista, aos desenvolvedores, aos programadores, aos tradutores voluntários, aos testadores e a todas as pessoas que contribuem de alguma forma com este sistema operacional GNU/Linux fantástico que é o antiX.
Obs.: Apesar deste tópico estar na área em idioma Português, eu irei incluir a tradução automática para o idioma Inglês.
marcelocripe
(Texto original em idioma Português do Brasil)– – – – –
Esteemed.
It is with great satisfaction that I share my first remastering of antiX 21 with kernel 4.4.0-296.
The two remasters were made from the ISO images “antix-21_386-full.iso” and “antix-21_x64-full.iso”, both with the SysVinit service boot system.
The purpose of these remasters is that we can have available antiX 21 bits and 64 bits ready to boot with Kernel 4.4.0-296. I removed the other two cores, kernel 4.9.0-279 and kernel 5.10.57.
Despite the announcement of the @anticapitalist, on February 7, 2022, on the end of Kernel 4.4, in the topic in English language 4.4 kernel has reached EOL (End of life), Kernel 4.4 is what you can initialize on most plates-mothers who have a board video sis and via.
The only change I did, in addition to the kernel, it was to correct the text that is displayed in the “Menu Pessoal” submenu, that is, where it is written “Vídeos de Ajuda do Menu Pessoal” in antiX’s original ISO, I changed to “Vídeo de Ajuda do Menu Pessoal” in Portuguese Language of Brazil. Unfortunately, in the past, I sent the text in the plural to the @anticapitalist, as I thought they would be several videos and is actually just a video teaching how to add or remove the “Menu Pessoal” submenus.
These remasters are far short of ISOs pseudo-antix-19 legacy bet3 with Kernel 4.4.0-264 that @Xecure built from “Build-iso”, which I do not have Minimum idea how to use “Build-iso”.
I would like to thank all the people who share their knowledge for the good of others here in the forum. I take this opportunity to make a special thanks to @ensabahnur, the creator of Respin Pin Linux OS, who guided me and taught me to make each stage of the remastering of these ISOs, without these teachings, these ISOs would not exist. Thank you very much, @ensabahnur. I also thank the @anticapitalist, developers, programmers, volunteer translators, testers and all people who contribute in some way with this fantastic GNU/Linux operating system that is antiX.
Note: Despite this topic being in the Portuguese language area, I will include automatic translation for English language.
marcelocripe
(Original text in Portuguese language of Brazil)Getting tripped up on something with AntiX CORE 21 on my uefi-only box – maybe you can spot my error:
Problem: Even though I’ve used live-usb maker to make a secondary writable stick, and answer the text-based menu for things like timezone, static persistence, swapfile, from=usb etc, when I reboot, it acts like I am still in the original live-usb mode with root and demo user running with the default passwords. Note that I supplied my own new passwords originally when asked by setup after indicating my persistence choices which created the new root and home files. These choices were made on the secondary writable stick, not the original which was just a dd of the iso from the repo.
I more or less followed the same procedure when I made a stick using the BASE iso. No problems there with it recognizing my new passwords, so I’m stumped at what step I’m missing with core.
The ONE thing that is different however, that might be a cause, is that on my box, I have to manually edit the menu option (2nd one which prompts you with text menu choices) by changing the kernel parameter to “nosplash” and using F10 to boot out of grub.
Also note that after using AntiX-cli-cc to make the live usb to the secondary stick, after reboot I only have ONE choice now to boot, not the usual plethora of other options to choose from. Is that normal?
I only have to edit that grub stanza with nosplash with core. I don’t need to do this with base.
But maybe that’s not the reason/bug? Or am I just missing something particular to core that I’m overlooking?
- This topic was modified 1 year, 3 months ago by PDP-8.
FYI
(and interested in reading feedback from anyone who test drives it…)http://www.slackware.com/announce/15.0.php
BREAKING NEWS, SEBEKA MINNESOTA 2022-02-02:
.
{———- snip ————}
.This has been an interesting development cycle (in the “may you live in interesting times” sense). Anyone who has followed Linux development over the years has seen the new technology and a slow but steady drift away from the more UNIX-like structure. The challenge this time around was to adopt as much of the good stuff out there as we could without changing the character of the operating system. Keep it familiar, but make it modern. And boy did we have our work cut out for us. We adopted PAM (finally) as [some] projects we needed [have] dropped support for pure shadow passwords. We switched from ConsoleKit2 to elogind, making it much easier to support software that targets that Other Init System and bringing us up-to-date with the XDG standards. We added support for PipeWire as an alternate to PulseAudio, and for Wayland sessions in addition to X11. Dropped Qt4 and moved entirely to Qt5. Brought in Rust and Python 3. Added many, many new libraries to the system to help support all the various additions. We’ve upgraded to two of the finest desktop environments available today: Xfce 4.16, a fast and lightweight but visually appealing and easy to use desktop environment, and the KDE Plasma 5 graphical workspaces environment, version 5.23.5 (the Plasma 25th Anniversary Edition). This also supports running under Wayland or X11.
We still love Sendmail, but have moved it into the /extra directory and made Postfix the default mail handler. The old imapd and ipop3d have been retired and replaced by the much more featureful Dovecot IMAP and POP3 server.
The Slackware pkgtools (package management utilities) saw quite a bit of development as well. File locking was implemented to prevent parallel installs or upgrades from colliding, and the amount of data written to storage minimized in order to avoid extra writes on SSD devices.
For the first time ever we have included a “make_world.sh” script that allows automatically rebuilding the entire operating system from source. We also made it a priority throughout the development cycle to ensure that nothing failed to build. All the sources have been tested and found to build properly. Special thanks to nobodino for spearheading this effort.
We have also included new scripts to easily rebuild the installer, and to build the kernel packages. With the new ease of generating kernel packages, we went on to build and test nearly every kernel that was released, finally landing on the 5.15.x LTS series which we’ve used for this release. There are also some sample config files to build 5.16 kernels included in the /testing directory for anyone interested in using those kernels.
There’s really just way too many upgrades to list them all here. For a complete list of included packages, see:
ftp://ftp.slackware.com/pub/slackware/slackware64-15.0/PACKAGES.TXTDownloading Slackware 15.0:
—————————The full version of Slackware Linux 15.0 is available for download from the central Slackware FTP site hosted by our friends at osuosl.org
If your machine supports x86_64, it is highly recommended that you use the Slackware64 (64-bit) version for the best possible performance:
ftp://ftp.slackware.com/pub/slackware/slackware64-15.0/The 32-bit x86 version may be found here:
ftp://ftp.slackware.com/pub/slackware/slackware-15.0/The links above are for the Slackware file tree. If you already have Slackware 14.2 installed, you can use these files and follow the instructions in the UPGRADE.TXT document to upgrade your system to Slackware 15.0. Instructions for burning the Slackware file tree onto install discs may be found in the isolinux directory.
If you’re looking for a bootable installer, ISO images are available that can be written to a DVD or (using dd) to a USB stick:
ftp://ftp.slackware.com:/pub/slackware-iso/slackware64-15.0-iso
ftp://ftp.slackware.com:/pub/slackware-iso/slackware-15.0-isoIf the sites are busy, see the list of official mirror sites here: mirrors.slackware.com
We will be setting up BitTorrent downloads for the official ISO images. Stay tuned to slackware.com and the ##slackware IRC channel on
libera.chat for the latest updates.
.
{———- snip ————}
.—
Patrick J. Volkerding {email@redact.ed}Visit us on the web at: http://slackware.com
Good to be back. Loving the new AntiX-21 !
On a lark, thought I would skip using Etcher, Rufus, dd and the like and see if I could create a bootable Anti-X from within windows without those tools and use just copy n paste. And boot it on a strict uefi-only box.
(Actually I should have named this drag-n-drop !)
Check it out:
1) Insert a fresh fat32 stick out of the packaging as your target to put antix on.
2) Download the antix iso. I used the base version.
3) Double-click the iso and windows will automount it.
4) In one fell swoop, drag and drop all the files and folders from the iso to your stick.
5) EJECT the stick nicely, and then Reboot or pop into a different machine.Done. Of course I’m going to use the live-usb maker within antix itself for full featured persistence and so forth, but at least this gets you up and running.
Pretty pleased that this works.
- This topic was modified 1 year, 3 months ago by PDP-8.
- This topic was modified 1 year, 3 months ago by PDP-8.
