- This topic has 251 replies, 23 voices, and was last updated Nov 12-4:22 pm by Brian Masinick.
-
Posts
-
PPC
Would there be any arm in using URXVT as default terminal?
I think it is too bare-bones (at least for me). No right-click context menu, no drag-and-drop support, most of the easy help instructions in the forum answers don’t work (except running commands). It is entirely keyboard driven.
Very good point. I tried out terminology – the bodhi linux terminal. it looks great, runs on about 60 mb of RAM, has very usefull menus, but still, no drag and drop -at least not from zzzfm…
The suckless terminal is probably the lightest, but also even more bare-bones… So, no more ideas from me on that end…P.
Brian Masinick
Would there be any arm in using URXVT as default terminal?
I think it is too bare-bones (at least for me). No right-click context menu, no drag-and-drop support, most of the easy help instructions in the forum answers don’t work (except running commands). It is entirely keyboard driven.
I have no strong opinion either way, but I would agree that other terminal emulation programs, such as roxterm and lxterminal have a few more simple menu selection features. Whatever works best for packaging and overall distribution considerations is fine for me. The simple truth for those of us who are not first time users is that we can alter and configure our own configurations the way we want, and therefore, the two considerations of importance are those of the leadership and the overall community, and our founder, of course, has the right to choose whatever he prefers.
--
Brian MasinickTuxmuertox
Hello, first post in the forum; just some newbie notes.
Kernel: 5.10.57-antix.1-amd64-smp x86_64; Init: runit; Desktop, zzz-JWM
When trying to disable services like cups at startup, I’ve found some minor annoyances.
1- Menu > Applications > System > Choose services at startup. It doesn’t work. I think it points to sysv init scripts.
2- Menu > Applications > Preferences > Runit service manager, works fine. Cool!
3- running runit-service-manager.sh as non root user leads to a weird DM (slim) crash, or xorg crash. It forces relogin.
4- Slimski takes longer to login than pure slim. I have two services running at the moment, slim and slimski, is this normal? two DMs? May be some other DM like Ly might come at handy… Ly (a lightweight TUI (ncurses-like) display manager for Linux and BSD. Ly does not require systemd, and was designed not to depend on logind.That’s all. Superb work in any case, I’m using it in daily basis, cool kernel, init and Wms, what else?!
Cheers- This reply was modified 1 year, 8 months ago by Tuxmuertox.
anticapitalista
There have been a lot of changes since beta2. Have you dist-upgraded?
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
apt upgrade -y && apt dist-upgrade -y && reboot
I made it yesterday, 0 packages to update. Repo manger is untouched, all repositories from debian or artix are in bullseye.ModdIt
Pls, how do I get rid of the pinboard message, rox pinboard whatever it is
pops up everytime I start ice.Anonymous
whatever it is
Is this the “whatever” ?
No pinboard was in use…. the ‘Default’ pinboard has been selected.
Use ‘rox -p=Default’ to turn it on in future.forum search: rox pinboard
finds a topic containing 2 alternative solutionshttps://www.antixforum.com/forums/topic/antix-19-3-on-sony-vaio-picturebook-pcg-c1mzx/
edit the desktop-session.conf file and increase the Startup delay time (to 4 or 5 seconds).
or
That rox message can be avoided via boot from device with a boot cheat deskdelay=10 (The number is in seconds)
> Ly (a lightweight TUI (ncurses-like) display manager for Linux and BSD
https://github.com/nullgemm/ly FYI, the project is not yet stable/mature. vis:
81 open issue tickets https://github.com/nullgemm/ly/issues
17 unapplied merge requests, backlogged since Jun2020 https://github.com/nullgemm/ly/pulls
One of the project’s forks, active during recent months, has applied bugfixes: https://github.com/SartoxOnlyGNU/ly-reloadedSlimski takes longer to login than pure slim.
3 seconds? 300 seconds?
In another topic, or earlier in this topic, I have only noticed one other comment mentioning slowness.I have two services running at the moment, slim and slimski, is this normal? two DMs?
Unsure how you arrived at that assessment, but that outcome is essentially impossible.
Are both REALLY installed on your system, currently?
apt policy slim
apt policy slimski
Even if both (and/or other display manager programs) are present, each should check, and gracefully exit, if another display manager is already running.I have two services running at the moment
I am “out of the loop” in regard to testing under runit.
Did the “antiX-21-runit-beta2” even pre-install both slim and slimski?
Possibly the “runit services gui” is incorrectly reporting, or you are incorrectly interpreting, the displayed status of each service.
Xecure
1- Menu > Applications > System > Choose services at startup. It doesn’t work. I think it points to sysv init scripts.
That is a script included in control-centre-antix, pointing to the sysvinit service manager. I will see if I can edit the script to check if runit is running and launch the other program if installed.
3- running runit-service-manager.sh as non root user leads to a weird DM (slim) crash, or xorg crash. It forces relogin.
This is strange. When I run it as normal user, it informs me I am not root (no session stopping):
$ runit-service-manager.sh NOT RUNNING AS ROOT Cleanup and exiting4- Slimski takes longer to login than pure slim. I have two services running at the moment, slim and slimski, is this normal?
If one is running, the other is tracked by runsv but is “down” (inactive). If you use the Control Centre > Session > Login Manager > Change (if slim is installed), you can switch to slim (or whatever other login manager you install, as long as it has a runit service created and enabled) and compare the login-session time between them.
On my system they take the exact same amount of time. Would you mind installing slim + slim-themes-extra-antix, using the login manager program to “change” to slim, and then reboot and compare login session speed? It would be interesting to see the difference (if any) on other machines and try to spot the reason for the slowness.Ly (a lightweight TUI (ncurses-like) display manager for Linux and BSD. Ly does not require systemd, and was designed not to depend on logind.
If it is available in the Debian repos, I will create a runit service for it so it can work for anyone who is interested in using it. That reminds me I still have to set some up for sddm and gdm. Thanks for the reminder.
- This reply was modified 1 year, 8 months ago by Xecure.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Xecure
am “out of the loop” in regard to testing under runit.
Did the “antiX-21-runit-beta2” even pre-install both slim and slimski?EDIT: Only slimski is installed, but the service file is enabled to check if it is ever installed.
They are both enabled for when people upgrade from antix-19-runit to 21, so they don’t find that they cannot login after rebooting.
It is the same for most sysvinit services. If they are “enabled” (sudo update-rc.d service-name defaults), then they will check if they are the default DM and exit if not. The difference with runit is that runsv will keep track of the state of all enabled services (even if they are down), so it will check every few seconds if the state of the service has changed. slim will not be launched but the service “tracker” will keep watch of it.- This reply was modified 1 year, 8 months ago by Xecure.
- This reply was modified 1 year, 8 months ago by Xecure.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Brian Masinick
I’m oscillating between the antiX Beta 2 sysvinit and the antiX-21-runit-beta2 image;
running runit now.inxi -Fxz System: Kernel: 4.9.0-279-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: IceWM 2.7.0 Distro: antiX-21-b2-runit_x64-full Grup Yorum 21 August 2021 base: Debian GNU/Linux 11 (bullseye) Machine: Type: Laptop System: Dell product: Inspiron 5558o v: 01 serial: <filter> Mobo: Dell model: 086DKN v: A00 serial: <filter> UEFI: Dell v: A04 date: 08/06/2015 Battery: ID-1: BAT0 charge: 33.9 Wh (100.0%) condition: 33.9/41.4 Wh (81.7%) volts: 16.5 min: 14.8 model: Samsung SDI DELL 07G07587587 status: Full CPU: Info: Dual Core model: Intel Core i7-5500U bits: 64 type: MT MCP arch: Broadwell rev: 4 cache: L2: 4 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19155 Speed: 2403 MHz min/max: 500/3000 MHz Core speeds (MHz): 1: 2403 2: 2404 3: 2612 4: 2421 Graphics: Device-1: Intel HD Graphics 5500 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: NVIDIA GK208BM [GeForce 920M] vendor: Dell driver: N/A bus-ID: 08:00.0 Device-3: Suyin Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 2-5:3 Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 20.3.5 direct render: Yes Audio: Device-1: Intel Broadwell-U Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:03.0 Device-2: Intel Wildcat Point-LP High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 Sound Server-1: ALSA v: k4.9.0-279-antix.1-amd64-smp running: yes Network: Device-1: Intel Wireless 3160 driver: iwlwifi v: kernel port: f040 bus-ID: 06:00.0 IF: wlan0 state: up mac: <filter> Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 07:00.0 IF: eth0 state: down mac: <filter> Bluetooth: Device-1: Intel type: USB driver: btusb v: 0.8 bus-ID: 2-6:4 Report: hciconfig ID: hci0 rfk-id: 1 state: down bt-service: not found rfk-block: hardware: no software: yes address: <filter> Drives: Local Storage: total: 931.51 GiB used: 6.52 GiB (0.7%) ID-1: /dev/sda vendor: Seagate model: ST1000LM024 HN-M101MBB size: 931.51 GiB Partition: ID-1: / size: 97.87 GiB used: 6.52 GiB (6.7%) fs: ext4 dev: /dev/sda7 Swap: ID-1: swap-1 type: partition size: 7.91 GiB used: 0 KiB (0.0%) dev: /dev/sda2 Sensors: System Temperatures: cpu: 47.0 C mobo: 25.0 C sodimm: SODIMM C Fan Speeds (RPM): cpu: 2200 Info: Processes: 201 Uptime: 4m Memory: 7.77 GiB used: 500.4 MiB (6.3%) Init: runit runlevel: 2 Compilers: gcc: 10.2.1 Packages: 1619 Shell: Bash v: 5.1.4 inxi: 3.3.06Just updated the runit packages again. This image is looking pretty good.
Running the *.279 kernel on this one as shown in the inxi report.Happy to see that I can switch between the various window managers and the switching, plus the functionality has been working well.
Have been using zzzFM here and in my regular use of antiX; it has been flawless in my personal use.- This reply was modified 1 year, 8 months ago by Brian Masinick.
- This reply was modified 1 year, 8 months ago by Brian Masinick.
--
Brian MasinickTuxmuertox01
Sorry I lost the password and had to register again.
Ly (a lightweight TUI (ncurses-like) display manager for Linux and BSD
FYI, the project is not yet stable/mature.Ooops, my bad 🙁
I just wanted to quote some other minimal DM, ncurses o terminal based.Slimski takes longer to login than pure slim.
3 seconds? 300 seconds?
In another topic, or earlier in this topic, I have only noticed one other comment mentioning slowness.2 seconds more than previous slim, once the password is accepted. Also the WM starts with some delay, 1-2 seconds. It can be related to next answer about slim and slimski
I have two services running at the moment, slim and slimski, is this normal? two DMs?
Unsure how you arrived at that assessment, but that outcome is essentially impossible.
Are both REALLY installed on your system, currently?
apt policy slim
apt policy slimskiapt policy slim > Installed none
You are right. My mistake again. But I run “runit service manager” and slim is still there, state inactive, but locked (?) (startup yes). This might be the reason for slimski delay, something is still looking for slim.
Just to clarify, no two DMs running at the same time, slim is uninstalled but has left the startup entry behind.- This reply was modified 1 year, 8 months ago by Tuxmuertox01.
Brian Masinick
I do also have the 5.10.57 kernel available on the runit test partition.
I’ll see how it’s working too.--
Brian MasinickSorry guys I had to re-register an account.
– Regarding Ly DM, I just wanted to quote some terminal or ncurses DM, in favor of a lighter system. I didn’t check the issues. My bad 🙁
– For slim vs slimski: apt policy slim > Installed none. I just checked “runit service manager” and slim is still there, and locked for startup (?). That’s why I thought it was running. Slim is uninstalled but has left the startup entry behind. I’ll check slim + slim-themes-extra-antix as suggested, nice.
– The delay of slimski is two seconds after the password is accepted, and the WM shows up slower, with 1 second delay. I think this might be related to whatever slim has left behind. I’ll recheck these days.
– I’ll try to reproduce the crash I mentioned before, and re-report if I find it again.Thanks Xecure & skidoo for the time, I’m learning and I know this is a beta, but it’s really interesting
Brian Masinick
I have the 5.10.57 kernel running now and I’m getting similar results. Solid performance with either kernel when I use my Dell Inspiron 5558.
I was running an antiX 21 test with a Thinkpad X201 the other day, and that hardware was also working well.
Going over to the sysvinit side now…--
Brian Masinick
- You must be logged in to reply to this topic.
