Trying to make an AntiX respin. Some questions.

[Member seaken64]

Helpful

Up

1

::

Or use two USB key drives. The Rufus made one can launch the LiveUSB Maker application and then use the second USB key as the Target for a newly created LiveUSB. It can be done with one USB drive but it is easier with two.

Seaken64

[Member Mich-C]

Helpful

Up

0

::

Ok, as suggested by you guys, I normally installed Antix on my laptop.

sudo apt update
enabled Liquorix repo from Synaptic package manager
pressed Reload…
but I stil get this error:

Mich-C wrote:

GPG error: https://liquorix.net/debian sid inRelease:
The following signature couldn't be verified because the public key is not available: NO_PUBKEY 9AE40783033F8024D
The repository ìhttp://-liquorix.net/debian sid inRelease' is not signed.
[...]
N: Updating from such a repository can't be done securely, and is therefore disabled by default.

As you can see the repo remains unabled. Pobably you don’t need inxi-r but there it is.

Repos:
  Active apt repos in: /etc/apt/sources.list.d/antix.list 
  1: deb http://mirrors.rit.edu/mxlinux/mx-packages/antix/bullseye/ bullseye main nosystemd nonfree
  Active apt repos in: /etc/apt/sources.list.d/bullseye-backports.list 
  1: deb http://deb.debian.org/debian/ bullseye-backports main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
  1: deb http://ftp.us.debian.org/debian/ bullseye-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list 
  1: deb http://ftp.us.debian.org/debian/ bullseye main contrib non-free
  2: deb http://security.debian.org/ bullseye-security main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/various.list 
  1: deb http://liquorix.net/debian/ sid main

I also googled “antiX” followed by the error I got, but it only shows 2 results:

—>this
(a user suggests to go on wwww.liquorix.net and use the .sh script they provide to add the repo, but I can’t find it, and since Antix is different from Ubuntu etc, I’m not sure it’s the ideal solution).

—>and this, but the suggested fix did not fork for the guy)…

Any idea?

• This reply was modified 11 months, 1 week ago by Mich-C.
• This reply was modified 11 months, 1 week ago by Mich-C.
• This reply was modified 11 months, 1 week ago by Mich-C.

[Moderator caprea]

Helpful

Up

0

::

Try this
curl https://liquorix.net/linux-liquorix.pub | sudo apt-key add -

sudo apt update

[Member Mich-C]

Helpful

Up

0

::

caprea wrote:

Try this
curl https://liquorix.net/linux-liquorix.pub | sudo apt-key add -

Thank you, I gave that command, but it gets stuck immediately, this way:

curl https://liquorix.net/linux-liquorix.pub | sudo apt-key add -
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0[s100  3171  100  3171    0     0   6775      0 --:--:-- --:--:-- --:--:--  6775

If I press ctrl+C I get:

sudo: a password is required

[Moderator caprea]

Helpful

Up

0

::

Oh, yes. If you first do the “sudo apt update” and therefor type in your password, afterwards the command above will go through.

Edit: Or you can also type your password + enter key when the terminal gets stuck. Should work.

[Moderator Brian Masinick]

Helpful

Up

0

::

By the way I have some feedback on the use of Liquorix kernels based on recent use cases.

First, I have used Liquorix kernels. Like the antiX kernels they are well engineered. I would say that they provide a good alternative to Debian kernels because they are somewhat more specifically built for interactive work loads. I’ve had many good experiences with them.

Recently, however, I have been working with some older systems and this past week I experienced the first difficulty with a Liquorix kernel. I rebooted with an old antiX kernel that I also retained and it worked, so I tried a few other kernels. All of the antiX kernels in both the 4.* and the 5.* versions worked. I didn’t go with a Debian kernel; they’re very good too, but antiX kernels are specifically tested by both development and users; with the 1-2 instances now of an issue, isolated as it was with the Liquorix kernel, I’m favoring the use of antiX kernels for most of us. Experienced users can experiment; anyone unsure should definitely stick with antiX stuff; besides, it further strengthens the number of people using and therefore exposing any rare issues that arise so that we can keep the problems small, identified, managed and fixed.

--
Brian Masinick

[Moderator Brian Masinick]

Helpful

Up

0

::

One other thing regarding the Liquorix kernels: the ONLY reason this particular instance (the FIRST time in the MANY years that I’ve used Liquorix kernels with Debian, MX Linux, siduction, and antiX) was on a very old system. On that system, arguably the 4.9 kernel works as good or better than anything else, though I was also able to get an antiX 5.10 kernel working on that system.

--
Brian Masinick

[Author]

Posts