August 2022 - 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.6): [notify] open-vm-tools: updated to version 12.1.0-20219665
by crux＠crux.nu 24 Aug '22

24 Aug '22

commit a1128aed1f57a8ec32cdaf9a30253dd7f3fcf01e Author: Matt Housh <jaeger(a)crux.ninja> Date: Tue Aug 23 19:38:43 2022 -0500 [notify] open-vm-tools: updated to version 12.1.0-20219665 Resolves CVE-2022-31676, see https://www.vmware.com/security/advisories/VMSA-2022-0024.html diff --git a/open-vm-tools/.signature b/open-vm-tools/.signature index 3c5c8d03b..34ec8ccac 100644 --- a/open-vm-tools/.signature +++ b/open-vm-tools/.signature @@ -1,6 +1,6 @@ untrusted comment: verify with /etc/ports/contrib.pub -RWSagIOpLGJF32uSzAsxOODUCG43NBcHvrs9EuUhKVuef5G3zQRu0UPVU38uGxZse9km9k0qUC+K6XfbTF2NUmauba9dz26kMgo= -SHA256 (Pkgfile) = db78ee2f7132ea4424606d0f5db1a4e166a8e285f7e726a897459e6a7b190f97 +RWSagIOpLGJF39ZzsqhbJ7GqMXWJynzW/4DjL31BlO30UpuQRtY41LShHm39BYpSNO4FF8ca4ZLXM7ujzQ33n9y8XYzLkLzHWwI= +SHA256 (Pkgfile) = 53f2a854318147ed0c3e8140e911af80e7718fc91b2a5cbadfe21e52ccee6103 SHA256 (.footprint) = 31a83b9969a7d02f6464a4234ef5c2177349ce714f889030ed13a5200aa289bf -SHA256 (open-vm-tools-12.0.5-19716617.tar.gz) = f591fbf927d971ebbcc2dfc826f652eb1c287460f481bfec2c69381472292f9a +SHA256 (open-vm-tools-12.1.0-20219665.tar.gz) = f9cff769cb60d3e570b8dfed98179b345b089ee3cc31a60d80a4fcca1cc220ee SHA256 (vmtoolsd) = a443b32dd7b0505db463ed20ff10c0ea3aefc41f003feb704921afa4c72325d8 diff --git a/open-vm-tools/Pkgfile b/open-vm-tools/Pkgfile index 02593531f..36e9834ac 100644 --- a/open-vm-tools/Pkgfile +++ b/open-vm-tools/Pkgfile @@ -4,7 +4,7 @@ # Depends on: libmspack libdnet glib rpcsvc-proto fuse name=open-vm-tools -version=12.0.5-19716617 +version=12.1.0-20219665 release=1 source=(https://github.com/vmware/$name/releases/download/stable-${version%… \ vmtoolsd)

1 0

opt/babl-0.1.94 configure fails if git is installed
by Richard Dunbar 22 Aug '22

22 Aug '22

Running command: /usr/bin/git rev-parse --is-inside-work-tree --- stdout --- --- stderr --- fatal: not a git repository (or any of the parent directories): .git babl-0.1.94/meson.build:450:11: ERROR: Command "/usr/bin/git rev-parse --is-inside-work-tree" failed with status 128. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- My workaround was to uninstall git, update babl, reinstall git.

1 0