antiX-26-rc1 available

[Brian MasinickModerator]

Brian Masinick wrote:

ProwlerGr wrote:

Maybe test the attached on Dinit & report back if it works well for you.
We will need to wait for @anticapitalista to get back before it is properly packaged for antiX

Tried this one first: it works!

I’ll go on to the 66 fix next; thanks!

I gave 66 a good workout this morning and everything (including the date and time) are now working as expected.
I’m on dinit now, which I said works. Everything so far is working normally. I’m using the Ungoogled Chromium Web browser without any issues or special treatment required, so the fuse module fix is indeed functioning across all variations and I have not noticed any other issues.

Since this matter about the fuse module excaped my attention until recently I’ll look for any other oddities that don’t get spotted with my pretty basic daily use cases. If I find anything else I’ll report it, but this software is getting pretty close to release quality.

I hope that other people are also giving it a good workout, because if there are no more reports this may end up going into release 26 as is.

--
Brian Masinick
Alternate "Search B":
This search page

[Brian MasinickModerator]

andfree wrote:

I noticed an issue that I don’t know if it is already known and I have no time to search about it, so I just mention it.
I can’t “pass” directly from dinit to 66; rebooting fails. However, I can reboot without problem from dinit to runit and then from runit to 66.

I haven’t explicitly tried this test case but I’m running dinit right now, so I will try switching back and forth each direction between the two. I’ll let you know the outcome.

--
Brian Masinick
Alternate "Search B":
This search page

[Brian MasinickModerator]

I noticed an issue that I don’t know if it is already known and I have no time to search about it, so I just mention it.
I can’t “pass” directly from dinit to 66; rebooting fails. However, I can reboot without problem from dinit to runit and then from runit to 66.

I’ve not found any direct correlation to booting between dinit and 66. However, every so often, one of the “newer” boot alternatives occasionally hangs up; most recently there was one with dinit; rebooted to dinit and it worked fine, then I went to 66 fine, and back to dinit fine.

There might be something in the overall init alternatives boot sequence that isn’t optimal for all of the boot alternatives. From what I can recall, dinit seems to encounter the most boot issues, but it doesn’t happen often enough to assertively call it a big problem; since we’ve both seen “something” it may be something to look out for a more effective startup procedure.

--
Brian Masinick
Alternate "Search B":
This search page

[andfreeMember]

Unfortunately, this issue that had not affected my antiX-26-rc1 systems till now, has just appeared on Vivobook (my previous posts, earlier today, were about Vaio, not about Vivobook). I can’t boot the legacy (5.10) kernel with persistence on my installed system anymore.

• This reply was modified 6 months, 3 weeks ago by andfree.

antiX utilities for processing PDF files (posted by ChPol)

[andfreeMember]

andfree wrote:

I can’t boot the legacy (5.10) kernel with persistence on my installed system anymore.

It seems that the same issue affected also the modern (6.6) kernel, but only on 66 (while with legacy kernel it affects all init programs).

antiX utilities for processing PDF files (posted by ChPol)

[Brian MasinickModerator]

@ProwlerGr, I have another question about the configuration of dinit.

The dinit service manager shows the available tty devices; there are six.
When I looked at the /usr/share/dinit/services directory, there are readable
files for [tty1-tty6].

The tool seems to ignore any attempt to remove unused, unwanted tty devices,
at least with dinit; whereas in the past I’ve been able to use some combination
of getty or service manager tools to alter the number of tty devices I want
enabled.

Is it permissible to remove some of these tty devices in the
/usr/share/dinit/services directory or will this cause a problem?

Also is there any possibility of improving the dinit service manager to
allow more flexibility in this regard?

The same is true in other alternatives; the “classic ones” appear to give
me the flexibility I am seeking; the recent init diversity additions
seem to be limited in this regard, so I am hoping to learn whether this
is a built in limitation or if it’s a configurable option that simply has
not been completely configured or not configured.

Any comments, advice, tweaks I can do myself, etc. that won’t harm the
existing environment would be something I’d love to explore; I won’t
touch the ttys in the directory cited above unless this is a safe
operation; likewise with any of the other configurations. As
always, I value and appreciate your comments and advice.

--
Brian Masinick
Alternate "Search B":
This search page

[ProwlerGrMember]

Brian Masinick wrote:

The tool seems to ignore any attempt to remove unused, unwanted tty devices,
at least with dinit; whereas in the past I’ve been able to use some combination
of getty or service manager tools to alter the number of tty devices I want
enabled.

Is it permissible to remove some of these tty devices in the
/usr/share/dinit/services directory or will this cause a problem?

Try the attached & see if it resolves the issue for you

Attachments:

1. dinit-service-boot-module-antix_0.1.8experimental2_all.deb_.zip

[Brian MasinickModerator]

ProwlerGr wrote:

Brian Masinick wrote:

The tool seems to ignore any attempt to remove unused, unwanted tty devices,
at least with dinit; whereas in the past I’ve been able to use some combination
of getty or service manager tools to alter the number of tty devices I want
enabled.

Is it permissible to remove some of these tty devices in the
/usr/share/dinit/services directory or will this cause a problem?

Try the attached & see if it resolves the issue for you

Cool! This is the same zipped package, but it appears that you added this handy feature.
Now I can (and have) removed a couple of ttys, so I guess it IS permissible to do so.
I’ll go back and see if they’ve been deleted; that would be what I’d expect.

Interesting; the files tty1 through tty6 remain present, but now the service manager
shows that they are not “active”.

My ps ax listing shows them running; I’ll restart the system and see if the
service manager will prevent them from running (or they may be removed).

--
Brian Masinick
Alternate "Search B":
This search page

[Brian MasinickModerator]

I rebooted; now it works the way I was hoping to see:

ps ax | grep tty
 1376 tty3     Ss+    0:00 /sbin/agetty tty3 38400 linux
 1377 tty2     Ss+    0:00 /sbin/agetty tty2 38400 linux
 1378 tty1     Ss+    0:00 /sbin/agetty --noclear tty1 38400 linux

Thanks!

--
Brian Masinick
Alternate "Search B":
This search page

[andfreeMember]

After running:
sudo 66 configure -e geany boot@system
making these changes:

TZ=Europe/Athens
HARDWARECLOCK=localtime

and activating them:
sudo 66 reconfigure boot@system
I’ve set the time for my system. Although this makes me glad (thanks once again @ProwlerGr), I wonder why the changes have been applied to all init programs and not only to 66.

Brian Masinick wrote:

I’ve not found any direct correlation to booting between dinit and 66.

Neither me, today.

antiX utilities for processing PDF files (posted by ChPol)

[Brian MasinickModerator]

This morning when I logged in with dinit everything came up correctly including the time.
I know that we have the set_time-and_date.sh tool to adjust the time, but I still want
to ensure that all five init alternatives automatically set the correct time; I’m not
100% certain that dinit is getting it in all cases.

The only reason I have an issue at all is that I multi-boot. At least one of my
non antiX systems (I think it may be Endeavour OS) has the time configured differently.
On my antiX and other Debian-based systems I typically install ntpsec, and that usually
snaps my systems to the correct time within the first minute or two; hopefully that
will ultimately be the case here too.

Meanwhile, at least TZ=America/New_York; export TZ gets the correct date/time at the
shell level.

--
Brian Masinick
Alternate "Search B":
This search page

[Brian MasinickModerator]

I also have a ~/bin script called fix-localtime.bash that is able to shortcut the set_time-and_date.sh tool with the following code:

sudo ln -sf /usr/share/zoneinfo/America/New_York /etc/localtime
sudo hwclock --hctosys --localtime

Nevertheless I think that our final effort ought to have time configurable and sustainable in each init alternative to provide the best possible experience for everyone as some people actually try out the various choices. The cleaner and more accurate every single component is in every way, this encourages use and participation, and I’m all for that, along of course with our lean efficiency.

--
Brian Masinick
Alternate "Search B":
This search page

[Brian MasinickModerator]

Brian Masinick wrote:

The only reason I have an issue at all is that I multi-boot. At least one of my
non antiX systems (I think it may be Endeavour OS) has the time configured differently.

I tried Endeavour OS and returned to antiX 26 RC1 and indeed it exposed the date/time issue with the dinit alternative enabled, so the time is NOT getting set in the preferred method for me, whereas it gets corrected in the other instances.

--
Brian Masinick
Alternate "Search B":
This search page

[rokytnjiForum Admin]

harry@harry:~
$ sudo update grub
[sudo] password for harry: 
sudo: update: command not found
harry@harry:~
$ sudo update grub2
sudo: update: command not found
harry@harry:~
$ sudo dist-upgrade grub
sudo: dist-upgrade: command not found
harry@harry:~
$ sudo dist-upgrade grub2
sudo: dist-upgrade: command not found

I stay in runit because it boots the fastest.
I kept the other init choices though in grub.
Not sure why I can’t show menu with the commands above though..

Drugs I on making it hard to remember commands

$ sudo update-grub
[sudo] password for harry: 
Generating grub configuration file ...
Found background: /usr/share/wallpaper/grub/back.png
Found background image: /usr/share/wallpaper/grub/back.png
Found linux image: /boot/vmlinuz-6.6.119-antix.1-amd64-smp
Found initrd image: /boot/initrd.img-6.6.119-antix.1-amd64-smp
Found linux image: /boot/vmlinuz-5.10.240-antix.1-amd64-smp
Found initrd image: /boot/initrd.img-5.10.240-antix.1-amd64-smp
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
done

I have booted the other choices but I like runit best,
Used to runit helps me also.

• This reply was modified 6 months, 3 weeks ago by rokytnji.

Sometimes I drive a crooked road to get my mind straight.
I don't suffer from insanity. I enjoy every minute of it.
Motorcycle racing is rocket science.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

[Brian MasinickModerator]

@rokytnji your “time away” has caused your brain to “forget” a few key things:
When you are using antiX apt or apt-get are always in commands to update packages.
If all you were trying to do is update the grub bootloader, that’s a different command,
as you eventually figured out: sudo update-grub

--
Brian Masinick
Alternate "Search B":
This search page

[Author]

Posts