April 2023 - CRUX - lists.crux.nu

Thoughts on making Crux more `alive' and `attractive'.
by Hans Bezemer 16 Mar '24

16 Mar '24

Dear fellow Crux-users, Recently there was some discussion in the IRC channel about how to make crux more `alive' and `attractive'. Being a relative new user I would like to share my thoughts. First of all, Crux has a lot of good things to offer: It's simplicity and script based orientation are unique. The package management through ports is simple but effective. Also there is some good documentation (but may be improved). And (last but not least) there's a friendly and helpful community. When I started out with Crux it took a while before I had everything up and running. Although I had used Arch for some while, went through the LFS-book twice, there was still a lot of ground to make up before I had my laptop configured the same way when using Arch. I had to hone several skills: building my own kernel, creating some udev rules, setting up networking using wpa_supplicant only (I know nm is at hand) and so on. Although the somewhat steep learning curve belongs to the way Crux works, there can be some minor improvements made which may help newcomers finding their way around more easily. First of, maybe Crux can become a rolling distro, with a new iso every month / 2 months. In practice it already seems to be. There are unofficial updated iso's and once you got everything installed everything can be kept up-to-date. As a new user I used the official iso (which is good practice I think), but after building the kernel, running a sysup was a bit of a showstopper. Almost all of the packages needed to be updated. When using the more recent unofficial iso, this is obvious not the case. Secondly, there is a lot of good documentation -especially on the Crux specific parts- but having two sources (Handbook and wiki) is somewhat confusing sometimes. Maybe merge the handbook into the wiki with an entry for installing Crux (like the installation guide on the Arch wiki)? The guide will walk the new user through a basic installation with links to several options (e.q. encrypting harddrive, using different bootloaders). At the end of the guide there can be some links to other entry (how to install packages, e.d.). It would be helpful if there is a basic `how to compile your own kernel'-tutorial. Something along the lines of `make defconfig', enabling audio and video support, untick some of the wlan firmware drivers, etc. Copying the bzImage and System.map and updating the boatloader. Lastly a guide on creating and maintaining your own repo (which is part of the charm of using Crux I think), would be very helpful. Beerman / Tim's guide would be a great starting point IMHO. https://gist.github.com/TimB87/6cf010c0c10d67faf98ae03e62ffb029 As for the documentation, for the most part it's a matter of reorganizing. Maybe a `further reading' section can be added at the end of an entry, with links to useful sources like the Arch wiki / offical kernel documentation and so on. The goal here is to keep it simple (of course ;-)) I'll be happy to help out with (re)writing some parts. What do you think? Would this be helpful? Or are there other / better options? Kind regards, Hans

9 13

ports/contrib (3.7): [notify] python3-pyqt6: 6.4.2 -> 6.5.0 new dependency python3-tomli
by crux＠crux.nu 30 Apr '23

30 Apr '23

commit a2abdac675386100180f7e7eba0cf20506d73695 Author: Danny Rawlins <contact(a)romster.me> Date: Sun Apr 30 13:55:30 2023 +1000 [notify] python3-pyqt6: 6.4.2 -> 6.5.0 new dependency python3-tomli diff --git a/python3-pyqt6/.footprint b/python3-pyqt6/.footprint index 1eb795417..e246151a3 100644 --- a/python3-pyqt6/.footprint +++ b/python3-pyqt6/.footprint @@ -5,10 +5,10 @@ drwxr-xr-x root/root usr/bin/ drwxr-xr-x root/root usr/lib/ drwxr-xr-x root/root usr/lib/python3.10/ drwxr-xr-x root/root usr/lib/python3.10/site-packages/ -drwxr-xr-x root/root usr/lib/python3.10/site-packages/PyQt6-6.4.2.dist-info/ --rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6-6.4.2.dist-info/INSTALLER --rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6-6.4.2.dist-info/METADATA --rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6-6.4.2.dist-info/RECORD +drwxr-xr-x root/root usr/lib/python3.10/site-packages/PyQt6-6.5.0.dist-info/ +-rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6-6.5.0.dist-info/INSTALLER +-rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6-6.5.0.dist-info/METADATA +-rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6-6.5.0.dist-info/RECORD drwxr-xr-x root/root usr/lib/python3.10/site-packages/PyQt6/ -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/QtCore.abi3.so -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/QtCore.pyi @@ -152,6 +152,7 @@ drwxr-xr-x root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtCore/ -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtCore/qsystemsemaphore.sip -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtCore/qtemporarydir.sip -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtCore/qtemporaryfile.sip +-rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtCore/qtenvironmentvariables.sip -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtCore/qtextboundaryfinder.sip -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtCore/qtextstream.sip -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtCore/qthread.sip @@ -161,6 +162,8 @@ drwxr-xr-x root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtCore/ -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtCore/qtimezone.sip -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtCore/qtranslator.sip -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtCore/qtransposeproxymodel.sip +-rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtCore/qtversion.sip +-rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtCore/qtypes.sip -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtCore/qurl.sip -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtCore/qurlquery.sip -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtCore/quuid.sip @@ -275,6 +278,7 @@ drwxr-xr-x root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtGui/ -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtGui/qtransform.sip -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtGui/qundogroup.sip -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtGui/qundostack.sip +-rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtGui/qutimimeconverter.sip -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtGui/qvalidator.sip -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtGui/qvectornd.sip -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtGui/qwindow.sip @@ -289,6 +293,7 @@ drwxr-xr-x root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtNetwork/ -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtNetwork/qhostaddress.sip -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtNetwork/qhostinfo.sip -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtNetwork/qhstspolicy.sip +-rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtNetwork/qhttp1configuration.sip -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtNetwork/qhttp2configuration.sip -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtNetwork/qhttpmultipart.sip -rw-r--r-- root/root usr/lib/python3.10/site-packages/PyQt6/bindings/QtNetwork/qlocalserver.sip diff --git a/python3-pyqt6/.signature b/python3-pyqt6/.signature index 2d89a1c71..16499e78d 100644 --- a/python3-pyqt6/.signature +++ b/python3-pyqt6/.signature @@ -1,5 +1,5 @@ untrusted comment: verify with /etc/ports/contrib.pub -RWSagIOpLGJF31K+gi30tgQm/X0sivkzIZ5Aql2blHykrqrcfzY3RqOHDA6pC2GD4ad1RQOcEY+0gMiUJvUdQCu62bNfvvEJJA8= -SHA256 (Pkgfile) = 2a090fd263478d0a9538279295300994c7711d735783147b01e407c3adc4c1a9 -SHA256 (.footprint) = 6991a5a57511546419e28420799c6780696e43d461f460308575963d47329863 -SHA256 (PyQt6-6.4.2.tar.gz) = 740244f608fe15ee1d89695c43f31a14caeca41c4f02ac36c86dfba4a5d5813d +RWSagIOpLGJF31sFvFvqpuBNuvdsGrQZ+znNiZ/Xr6NvsslDjyZ11L0aLfqLFwLNWWHmUG4sN8q8bOWqR9bDUfEJP5KEeZ5HaQQ= +SHA256 (Pkgfile) = 2e6df260b9e67157ec9a60aeb8f94e2bd056c4836a8057882e1b8b6b3da9dd6f +SHA256 (.footprint) = f243f274ad750d707ae7c862c0133df00a6cdab2a45737507422f0c7c4bbfc38 +SHA256 (PyQt6-6.5.0.tar.gz) = b97cb4be9b2c8997904ea668cf3b0a4ae5822196f7792590d05ecde6216a9fbc diff --git a/python3-pyqt6/Pkgfile b/python3-pyqt6/Pkgfile index 05e7fa30f..f4240709a 100644 --- a/python3-pyqt6/Pkgfile +++ b/python3-pyqt6/Pkgfile @@ -1,11 +1,11 @@ # Description: Python bindings for the QT6 toolkit # URL: https://riverbankcomputing.com/software/pyqt/intro # Maintainer: Tim Biermann, tbier at posteo dot de -# Depends on: python3-opengl python3-packaging python3-ply python3-pyqt-builder python3-pyqt6-sip qt6-base sip +# Depends on: python3-tomli python3-opengl python3-packaging python3-ply python3-pyqt-builder python3-pyqt6-sip qt6-base sip # Optional: dbus-python3 qt6-connectivity qt6-declarative qt6-location qt6-multimedia qt6-quick3d qt6-remoteobjects qt6-sensors qt6-serialport qt6-svg qt6-tools qt6-webchannel qt6-websockets name=python3-pyqt6 -version=6.4.2 +version=6.5.0 release=1 source=(https://pypi.python.org/packages/source/P/PyQt6/PyQt6-$version.tar.…

1 0

Apollo Lake - No sound on jack connector
by Gasel SARL 14 Apr '23

14 Apr '23

Hi everybody, I've been using Thinstation (based on Crux) for several years to connect Nano PCs to a Windows Terminal Server in an elementary school. I recently purchased several nano PCs based on Apollo Lake (Celeron N3350). Everything works fine, except for the analog audio jack connector. Pavucontrol only shows "Dummy output" If I connect a screen via HDMI, the sound works without any problem. Only the jack connector does not work. Here is my module.list : |module ac97_bus module soundcore module snd module snd-hda-intel module snd-hda-codec module snd-hda-codec-hdmi module snd-soc-core module snd-compress module snd-pcm-dmaengine module snd-soc-acpi-intel-match module snd-soc-acpi module snd-soc-sst-ipc module snd-soc-sst-dsp module snd-intel-dspcfg module snd-hwdep module snd-hda-core module snd-pcm module snd-timer module i915 module x86_pkg_temp_thermal module intel_powerclamp module coretemp module crct10dif-pclmul module i2c-algo-bit module crc32-pclmul module intel-gtt module ttm module crc32c-intel module i2c-i801 module ghash-clmulni-intel module i2c-smbus module lpc_ich module drm_kms_helper module ahci module libahci module cec module libata module joydev module mei-me module drm module igc module scsi_mod module mei module thermal | I removed snd_soc_skl according to https://bkhome.org/news/201912/sound-fix-for-54-kernel-on-apollo-lake.html, without success... Can you help me ? -- Cet e-mail a été vérifié par le logiciel antivirus d'Avast. www.avast.com

2 1

Re: Hack to control ninja parallelism
by Daryl F 09 Apr '23

09 Apr '23

On Sun, 9 Apr 2023, ooga(a)e.email wrote: > 2023-04-08T20:51:59Z Daryl F <wyatt(a)prairieturtle.ca>: > >> After scouring the web for a solution to ninja overrunning my meager RAM when compiling qtwebengine I discovered there is no easy one. People have been looking for a solution for a long time. > > Edit your pkgmk.conf to have something like this: > > [ "$name" = "qtwebengine" ] && JOBS=4 || JOBS=8 > export JOBS > > Pkgfile and pkgmk.conf are still bash scripts, sharing the same "namespace" (they are "sourced-in" by pkgmk in this order). > > PS. Memory consumption is larger when linking objects. The llvm project has an option to specify the number of parallel link jobs. > > That is a good way to make the wrapper only affect qtwebengine builds but ninja does not respect the JOBS environment variable so the wrapper is still required.

1 0

Hack to control ninja parallelism
by Daryl F 09 Apr '23

09 Apr '23

After scouring the web for a solution to ninja overrunning my meager RAM when compiling qtwebengine I discovered there is no easy one. People have been looking for a solution for a long time. Apparently the ninja developers have no intention of providing an environment variable even though they've had patches volunteered. They seem think that a wrapper is the solutions. It is not a good solution for all situations. Some Arch users have switched to samurai, a controllable replacment for ninja but I'm not ready to try that. I don't know if samurai will keep pace with ninja changes. Because I wanted to control parallelism from pkgmk.conf I wrote this wrapper. Normally I let everything use the number returned by nproc. This doesn't work well for qtwebengine. It will begin swapping terribly and takes about 8 hours to compile with 16GB of RAM. nproc returns 8 on my machine. If I set JOBS=4 in pkgmk.conf qtwebengine will compile in about 4 hours with no swapping using this wrapper. The wrapper is: #!/bin/bash # to use this wrapper: # mv /usr/bin/ninja /usr/bin/ninja-piggy # put this script in /usr/bin/ninja # # in pkgmk.conf add: # export JOBS=n # whenever ninja should be restricted to 'n' processors. # # if JOBS is not set, below will default to the results from 'nproc'. JOBS=${JOBS:-$(nproc)} newargs=\"$(echo $@ | sed -e "s/-j[ ]\{0,\}[0-9]\{1,\}/-j$JOBS/g")\" exec ninja-piggy "$newargs" # End of file The downside is: it gets overlayed every time the ninja port is updated. Sigh. So I keep a copy of it in /usr/bin/ninja-lite. Cheers, Daryl

2 1

"Failed to load ldlinux.c32"
by lain. 07 Apr '23

07 Apr '23

Greetings. I installed Crux on an old ThinkPad by following the handbook religiously. At first I couldn't get it to boot at all, but I already solved that one by marking the main partition as bootable. But now when I boot up, I'm getting the message "Failed to load ldlinux.c32 Boot failed: please change disks and press a key to continue.". When looking up online, I only get results of people being unable to boot either Ubuntu or Arch from USB (which is not the case here), or people who are supposed to install for UEFI but installed for BIOS instead (my laptop is pure BIOS, UEFI on laptops other than MacBooks didn't exist yet at the time this laptop came out). So how can I fix this? -- lain. Did you know that? 90% of all emails sent on a daily basis are being sent in plain text, and it's super easy to intercept emails as they flow over the internet? Never send passwords, tokens, personal information, or other volunerable information without proper PGP encryption! If you're writing your emails unencrypted, please consider sending PGP encrypted emails for security reasons. You can find my PGP public key at: https://fair.moe/lain.asc Every good email client is able to send encrypted emails. If yours can't, then you should consider switching to a secure email client, because yours just sucks. My recommendations are Claws Mail or NeoMutt. For instructions on how to encrypt your emails: https://unixsheikh.com/tutorials/gnupg-tutorial.html

4 11

[PATCH] document parallelism configuration for cmake and ctest
by Liu Yubao 05 Apr '23

05 Apr '23

Building llvm and clang often get OOM killed because they use ninja which doesn't respect MAKEFLAGS. The two new environment variables benefit all CMake/Ninja based packages, I also committed a patch[1] to Venom Linux to automatically adjust parallel jobs for llvm and clang packages, it's very easy to port to ports/opt.git. [1] https://github.com/venomlinux/ports/pull/4287 --- pkgmk.conf | 2 ++ pkgmk.conf.5.in | 10 ++++++++++ 2 files changed, 12 insertions(+) diff --git a/pkgmk.conf b/pkgmk.conf index e6a8abc8..5063e77e 100644 --- a/pkgmk.conf +++ b/pkgmk.conf @@ -7,6 +7,8 @@ export CXXFLAGS="${CFLAGS}" # export JOBS=$(nproc) # export MAKEFLAGS="-j $JOBS" +# export CMAKE_BUILD_PARALLEL_LEVEL=$JOBS +# export CTEST_PARALLEL_LEVEL=$JOBS case ${PKGMK_ARCH} in "64"|"") diff --git a/pkgmk.conf.5.in b/pkgmk.conf.5.in index 3e054362..bd9c099f 100644 --- a/pkgmk.conf.5.in +++ b/pkgmk.conf.5.in @@ -29,6 +29,16 @@ Set make options. .br Default: none .TP +\fBexport CMAKE_BUILD_PARALLEL_LEVEL='NUMBER'\fP +Set Specifies the maximum number of concurrent processes to use when building using the cmake --build command line Build Tool Mode. +.br +Default: none +.TP +\fBexport CTEST_PARALLEL_LEVEL='NUMBER'\fP +Set Specify the number of tests for CTest to run in parallel. +.br +Default: none +.TP \fBPKGMK_SOURCE_MIRRORS=('STRING')\fP Set mirrors to check and download source archives from. .br -- 2.39.2

2 1