- This topic has 63 replies, 17 voices, and was last updated Dec 7-8:34 am by newmant1.
-
Posts
-
ile
hello anticapitalista
a2 has me saying “You are going to love antiX bullseye.”
live session automatic wlan ; mem after twelve hours.
screenshot with rgbpaint version screenshot,,mtrgbmtpaint, ,
a2 is quick. crisp.Attachments:
ModdIt
Does connman-vpnd always have to run, noticed yesterday although no vpn in use.
wlan spikes looks like the familiar connmann issue. Adding time servers
and backup timeservers calms the network activity after some uptime.
anticapitalista
Does connman-vpnd always have to run, noticed yesterday although no vpn in use…
You can remove it if you don’t use a vpn or connman
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
@anticapitalista thanks for info regarding connman-vpn.
a2, Live USB clone not getting past continue in settings window. Sticks are fine and plenty big enough.
Anonymous
FYI, I tested “personal snapshot” ( iso-snapshot-antix v0.4.3 ) ~~ it worked fine
Prior to creating snapshot, I had removed one of the preinstalled kernels.
Later, while booted from the snapshot…
IIRC the stray pair of (stranded? unused) initrd.1 and vmlinuz..1 files were still present.
The extra 5MB or so used on the boot device is no biggie, but their lingering presence invites confusion.
christophe
On a new instance of live-usb:
I performed all upgrades. New 4.9 kernel upgraded just fine.
5.10 kernel: the 5.10.22 kernel that the iso came with works fine. But the 5.10.27 kernel will not boot for me from the live-usb. I even uninstalled the kernel & reinstalled it. Always, I get this error:
Fatal Error
Neither aufs nor overlayfs is available(and I can choose to reboot or shut down.)
confirmed antiX frugaler, since 2019
calciumsodium
The antix-bullseye-a2-full with the updated 5.10.27 boots up very fast and runs very well on my old Satellite C55-B5300 laptop. It seems to boot up faster than my antix 19.1 system but not as fast as the antix-bullseye-a2-runit. Firefox-esr, chromium, dosbox, wine, and Kodi 19 work very well with a2-full. I think a2-full is very solid. There are some cosmetic things which I have noted previously as also seen in the a2-runit. But they are small.
Comparing a2-runit with a2-full: after @Xecure had alerted us that a2-runit accesses the harddrive by creating log files every second or so, I can actually hear my harddrive running with a2-runit almost all the time. Whereas, with a2-full, I can hardly hear my hardrive except when I launch a program. The sound difference is night and day.
In a2-full, at boot, I see the message SELinux: could not open policy file /etc/selinux/targeted/policy/policy.33 no such file or directory.
However, this does not seem to affect any performance. Is there a way to disable this message? I tried looking at past forum threads regarding selinux policy 33, but I must not have found an answer.
Is there a way to disable this message?
Try adding this to your bootline:
selinux=0
Post a followup to let us know whether or not this suppresses the message.If the above does not solve, another “thing to try” would be:
sudo touch /etc/selinux/targeted/policy/policy.33Hi @skidoo,
1. By bootline, do you mean added selinux=0 to the /boot/grub/grub.cfg file?
I added the following in that file. I tried both SElinux=0 and selinux=0. Both didn’t work.
linux /boot/vmlinuz-5.10.27-antix.1-amd64-smp root=UUID=15296ed6-712c-49a1-805b-0ab39f5a3d4f ro quiet SElinux=0
It did not work in that I still get the policy 33 error.
If this is not what you were suggesting, can you please give me further instruction?
2. As for your second suggestion regarding, sudo touch /etc/selinux/targeted/policy/policy.33, I looked at my file structure. There is no /etc/selinux/targeted directory under /etc/selinux, and hence, no /etc/selinux/targeted/policy directory, and hence no policy.33 file.
It seems like I cannot install zzzfm-common_1.0.7-1_all.deb on antiX-bullseye-a2-full using gdebi. After clicking install, it says installing…, and then gets stuck.
Gdebi was able to install zzzfm-common_1.0.7-1_all.deb on antiX 19.1.I was able to circumvent this by using terminal to install.
$ sudo apt install /home/username/zzzfm-common_1.0.7-1_all.deb
then
$ sudo apt install /home/username/zzzfm_1.0.7-1_amd64.deb
After I used menu manager to display zzzFM in the menu, I noticed that there was no icon in front of zzzFM in the menu in a2-full. This icon was present in the antiX 19.1 menu.
Thanks
Xecure
After I used menu manager to display zzzFM in the menu, I noticed that there was no icon in front of zzzFM in the menu in a2-full.
I also saw this, but though it was because I have been changing so many options while testing the new alpha I thought I was to blame. Because the icon does appear on the toolbar and on App Select.
1. By bootline, do you mean added selinux=0 to the /boot/grub/grub.cfg file?
If booting on live USB, you need to edit:
A) if Legacy_BIOS boot, edit the custom option in /live/boot-dev/boot/isolinux/isolinux.cfg and /live/boot-dev/boot/syslinux/syslinux.cfg (I cant remember which exactly right now)
B) If UEFI boot, you edit the custom option in /live/boot-dev/boot/grub/grub.cfgMore info on this on the wiki: https://antixlinuxfan.miraheze.org/wiki/Boot_Parameters#LIVE_or_FRUGAL_install
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Hi @Xecure,
I am booting antiX-bullseye-a2-full with 5.10.27 kernel from hard drive.
I get this message SELinux: could not open policy file /etc/selinux/targeted/policy/policy.33 no such file or directory
during boot. I thought it has something to do with a2-full.As it turns out, in a separate test, I installed the 5.10.27 kernel on my main antiX 19.1 OS. The kernel was previously 4.9.0-264 on this system. And I do get the same message on booting
SELinux: could not open policy file /etc/selinux/targeted/policy/policy.33 no such file or directory
I then uninstalled the 5.10.27 kernel on my antiX 19.1 OS and then that message is gone.
So is this message unique to the 5.10.27 kernel?
If so, how do I disable this message if I boot from hard drive.
Your previous thread offered options if booting from live USB.
ThanksXecure
For installed systems, you need to edit the /etc/default/grub file as described in the wiki: https://antixlinuxfan.miraheze.org/wiki/Boot_Parameters#Making_boot_parameters_permanent_for_grub
Add selinux=0 at the end of GRUB_CMDLINE_LINUX_DEFAULT line. Then you can follow the instructions in the wiki article linked above.
This selinux issue started with 5.1.X kernels (here a similar post), as selinux files are no longer included in the kernel build for antiX (no idea if other kernels use them).
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Thank you @Xecure.
Your suggestion, initially proposed by @Koo in that previous thread, disabled the selinux message.Interestingly, even without the selinux=0 command, my a2-runit install does not show the message
SELinux: could not open policy file /etc/selinux/targeted/policy/policy.33 no such file or directory
even though it was running the 5.10.27 kernel. I am curious why that is so.
Thanks again @Xecure and @Koo
Brian Masinick
I happen to be logged into MX Linux 19.4 right now; there is a /etc/selinux directory, but only one configuration file; no policy file /etc/selinux/targeted/policy/policy.33 at all, nor a /etc/selinux/targeted directory.
I suspect a similar situation by default with antiX.
There are distributions oriented to commercial use and security specific details; these would likely have more SELinux features.
- This reply was modified 2 years ago by Brian Masinick.
--
Brian Masinick
- You must be logged in to reply to this topic.
