Today I've updated the isos for daedalus, and the openbox version is already available.

You can configure the right-click menu by editing $HOME/.dxmenurc. Default values are:

[xmenu-config]

json_menu_path=
font=SansRegular:size=11,Verdana:size=11
background_color=#162431
foreground_color=#dddddd
selbackground_color=#00509f
selforeground_color=#e0effd
separator_color=#dddddd
border_color=#162431
width_pixels=130
height_pixels=28
border_pixels=4
separator_pixels=20
gap_pixels=6
max_items=0
alignment=0
triangle_width=6
triangle_height=10
iconpadding=2
horzpadding=10
hasicon=1

[dxmenu-xdg-config]

application_launcher=gmrun
terminal_emulator=sakura
file_manager=spacefm
web_browser=icecat
mail_client=claws-mail
logout_dialog=ulogout

Selbackground and selforeground stand selected background and foreground (the foreground color is the text color).

Shortly the ulogout dialog will provide suspend and hibernate options.

The line containing the grep command itself is supposed to be printed at the end due to its higher pid -and then it'll be ignored thanks to the use of the regex 'cron$'-, but who knows...

Actually, the boot time with vdev as device manager is optimized for runit only (indead, the default init system shown by choose-init-udeb in the installer-isos), and according to my analog tests, the times recorded do not substantially differ when compared to eudev. However, I have in mind to extend this optimization for other inits, although I won't do that until august. In the meantime, if you are running gnuinos with vdev and sysvinit, I suggest that you either change the init system to runit (apt-get install runit runit-init getty-run) or that you replace the device manager with eudev (apt-get install eudev).

While I'm particularly happy with vdev, there is room to do things in the project. For example, another possible idea I'm considering is to unify both libeudev and libudev-compat in a way that the behaviour of the shared library will depend on the running device manager. It wouldn't be that complicated. But I'm aware that I made some mistakes in the past during the vdev integration that might have broken the system, and I'll ensure that it never happens again. Thanks for your patience!

Some dhcp client, maybe? /etc/network/interfaces is for ifupdown

Thanks for your work!

As a suggestion, you may consider using

sv check dbus || exit <some_value>

instead of

sv start dbus || true

in the runscript of those services that depend on dbus, like elogind and so on.

After all, this is the point of /etc/sv/dbus/check. Isn't it?

I don't recommend you to change the init system from a running system next time. The already running init, whether runit-init or sysvinit, will be removed and the system won't shutdown properly. For example, it won't be able to determine the current runlevel. For this reason, I suggest you to use a live system instead.

From the live session, run the following command to determine the partitions. One sample:

liveuser@devuan:~$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0    7:0    0 756.3M  1 loop /lib/live/mount/rootfs/filesystem.squashfs
loop1    7:1    0   4.9M  0 loop /dev/metadata/hwdb
sda      8:0    0 465.8G  0 disk 
├─sda1   8:1    0  93.2G  0 part 
├─sda2   8:2    0     1K  0 part 
├─sda5   8:5    0 368.8G  0 part /mnt
└─sda6   8:6    0   3.7G  0 part 
sdb      8:16   1   7.2G  0 disk 
├─sdb1   8:17   1   877M  0 part /lib/live/mount/medium
└─sdb2   8:18   1   1.4M  0 part 
sr0     11:0    1  1024M  0 rom

In this concrete case /dev/sda1 is the root partition (/) in the attached internal disk, /dev/sda5 the home partition and /dev/sda6 the swap. Mount  the root partition (i.e. the system) in /mnt with the command:

# mount --rw /dev/sda1 /mnt

bind /sys, /proc and /dev and chroot the mounted system:

# mount -o bind /sys /mnt/sys
# mount -t proc proc /mnt/proc
# mount -o bind /dev /mnt/dev
# mount -o bind /dev/pts /mnt/dev/pts
# chroot /mnt

Now you're in a chroot jail and you'll be able to use apt within the mounted system. Install sysvinit-core and runit-init will be removed automatically. In addition, you an also purge other superfluous packages like runit and getty-run:

# apt-get update
# apt-get install sysvinit-core
# dpkg --purge runit getty-run
# apt-get clean

Exit the jail and unmount the partitions:

# exit
# umount /mnt/dev/pts
# umount /mnt/dev
# umount /mnt/proc
# umount /mnt/sys
# umount /mnt

Done.

You can ffmpeg. For example, download this video in mp4:

wget https://gnuinos.org/videos/shamsia.mp4

Note that i'm using https instead of http. The folloging command will cut the interval between 01:01 and 01:27 minutes:

ffmpeg -i shamsia.mp4 -ss 00:01:01 -t 00:01:27 -c copy output1.mp4

As a result, you will get output1.mp4

Now, one example about how to crop the result:

ffmpeg -i output1.mp4 -filter:v "crop=150:200:iw-100:0" output2.mp4

And you will get output2.mp4

You can find more examples searching the web.

Assuming I have understood your question, you're asking about how to install gnuinos from the live iso in a similar way than when you debootstrap the system:

https://gist.github.com/varqox/42e213b6 … filesystem  (***)

If so, below instructions (not tested) might help you.

To start with, download the iso image and create the following two folders at your home directory:

$ mkdir isoimage sqfs

As root, mount the iso image in the earlier one (extracting the iso file is that straightforward and, more often than not, you don't need any additional software):

# mount -o loop gnuinos-5.0.0-daedalus_preview-2023.06.21-xfce_i686.iso isoimage/

Now uncompress the squashfs filesystem to the latter folder:

# mount -t squashfs -o loop isoimage/live/filesystem.squashfs sqfs

At this point you can follow one by one the steps detailed in the above howto (***), but replacing the paragraph "Install base system" which consists in debootstrapping the system via debootstrap --arch amd64 stable /mnt https://deb.debian.org/debian with the command below:

# rsync -v -rlt -a sqfs/ /dev/PARTITION

This command would copy the whole lot to a separate folder in your /dev/PARTITION.

Bear in mind that you need to unmount the squashfs filesystem afterwards:

# umount sqfs/

Good luck!

Did you try with the following ruleset in your /etc/doas.conf?

permit zapper as root
deny zapper as root cmd /bin/bash

You can define more rules for other shells like /bin/sh, /bin/zsh, ...

If this proposal is pushed through, I'll be in Stockholm.

If it turns out that I'm updating the repo in the meantime, it won't work correctly throughout the update process and you have to wait for a period of time before trying again.

Did you install the server iso? If so, I recommend you to beep up the wired device using ifupdown and install simple-netaid-cdk afterwards, that is the ncurses interface for simple-netaid. But don't forget to add yourself to the netaid group in order to get ubus working in simple-netaid. In doing so, you'll be able to make use of some networking tools such as wpasupplicant, ifupdown, ip, etc, without root permissions. In summary, all you need to do is:

# ifup eth0
# apt-get update
# apt-get install simple-netaid-cdk
# usermod -aG netaid $USER

Then reboot the system and run simple-netaid-cdk as a regular user.

Pay attention to your /etc/network/interfaces.

Same at me.