You are not logged in.
I masked the udisks2 service on the VM system, such that the pupils (as live users later on) are unable to mount their own hard disks and look for solutions to the exam questions.
Why not a program that restores the service with the need of a secret password? You can write it in the blackboard at the end of the exam.
ralph.ronnquist wrote:You'd probably be better off playing on "plughw" rather than "hw" as it includes audio format translations...
Thank you very much, you are right!
I take my words back.
"plughw" works, after this command the sound from alsa started working.Regards.
Does amixer-gtk work with plughw, or are you using qasmixer instead? The ALSA amixer command doesn't work in my computer with this device:
$ amixer -D plughw
ALSA lib control.c:1528:(snd_ctl_open_noupdate) Invalid CTL plughw
amixer: Mixer attach plughw error: No such file or directory
When amixer-gtk is launched without arguments, i.e. without specifying the audio device, it'll try to auto-detect the one capable for playback streaming via snd_pcm_open (...) that creates a handle and opens a connection to the audio interface. The selected card is printed in the command output together with the mixer controls. However, you can also specify the card in the command line if you wish. For example:
$ amixer-gtk --card 0 --systray
Simple mixer control 'Master',0
Simple mixer control 'Headphone',0
Simple mixer control 'Speaker',0
Simple mixer control 'Speaker+LO',0
Simple mixer control 'PCM',0
Simple mixer control 'Front Mic',0
Simple mixer control 'Front Mic Boost',0
Simple mixer control 'Line Out',0
Simple mixer control 'Beep',0
Simple mixer control 'Capture',0
Simple mixer control 'Auto-Mute Mode',0
Simple mixer control 'Loopback Mixing',0
Simple mixer control 'Rear Mic',0
Simple mixer control 'Rear Mic Boost',0
Simple mixer control 'Master',0
Capabilities: pvolume pvolume-joined pswitch pswitch-joined
Playback channels: Mono
Limits: Playback 0 - 87
Mono: Playback 0 [0%] [-65.25dB] [off]
Simple mixer control 'Headphone',0
Capabilities: pvolume pswitch
Playback channels: Front Left - Front Right
Limits: Playback 0 - 87
Mono:
Front Left: Playback 87 [100%] [0.00dB] [on]
Front Right: Playback 87 [100%] [0.00dB] [on]
Simple mixer control 'Speaker',0
Capabilities: pswitch
Playback channels: Front Left - Front Right
Mono:
Front Left: Playback [on]
Front Right: Playback [on]
Simple mixer control 'Speaker+LO',0
Capabilities: pvolume
Playback channels: Front Left - Front Right
Limits: Playback 0 - 87
Mono:
Front Left: Playback 87 [100%] [0.00dB]
Front Right: Playback 87 [100%] [0.00dB]
Simple mixer control 'PCM',0
Capabilities: pvolume
Playback channels: Front Left - Front Right
Limits: Playback 0 - 255
Mono:
Front Left: Playback 255 [100%] [0.00dB]
Front Right: Playback 255 [100%] [0.00dB]
Simple mixer control 'Front Mic',0
Capabilities: pvolume pswitch
Playback channels: Front Left - Front Right
Limits: Playback 0 - 31
Mono:
Front Left: Playback 0 [0%] [-34.50dB] [off]
Front Right: Playback 0 [0%] [-34.50dB] [off]
Simple mixer control 'Front Mic Boost',0
Capabilities: volume
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 3
Front Left: 0 [0%] [0.00dB]
Front Right: 0 [0%] [0.00dB]
Simple mixer control 'Line Out',0
Capabilities: pswitch
Playback channels: Front Left - Front Right
Mono:
Front Left: Playback [on]
Front Right: Playback [on]
Simple mixer control 'Beep',0
Capabilities: pvolume pswitch
Playback channels: Front Left - Front Right
Limits: Playback 0 - 31
Mono:
Front Left: Playback 0 [0%] [-34.50dB] [off]
Front Right: Playback 0 [0%] [-34.50dB] [off]
Simple mixer control 'Capture',0
Capabilities: cvolume cswitch
Capture channels: Front Left - Front Right
Limits: Capture 0 - 31
Front Left: Capture 0 [0%] [-16.50dB] [off]
Front Right: Capture 0 [0%] [-16.50dB] [off]
Simple mixer control 'Auto-Mute Mode',0
Capabilities: enum
Items: 'Disabled' 'Speaker Only' 'Line Out+Speaker'
Item0: 'Line Out+Speaker'
Simple mixer control 'Loopback Mixing',0
Capabilities: enum
Items: 'Disabled' 'Enabled'
Item0: 'Disabled'
Simple mixer control 'Rear Mic',0
Capabilities: pvolume pswitch
Playback channels: Front Left - Front Right
Limits: Playback 0 - 31
Mono:
Front Left: Playback 0 [0%] [-34.50dB] [off]
Front Right: Playback 0 [0%] [-34.50dB] [off]
Simple mixer control 'Rear Mic Boost',0
Capabilities: volume
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 3
Front Left: 0 [0%] [0.00dB]
Front Right: 0 [0%] [0.00dB]
Device: hw:0
'Master',0
'Headphone',0
'Speaker',0
'Speaker+LO',0
'PCM',0
'Front Mic',0
'Front Mic Boost',0
'Line Out',0
'Beep',0
'Capture',0
'Auto-Mute Mode',0
'Loopback Mixing',0
'Rear Mic',0
'Rear Mic Boost',0
(...)
How to make it so I don't have to type xfce4-panel -r everytime?
You can create a desktop entry ~/.config/autostart/xfce4-panel-reload.desktop containing something like this:
[Desktop Entry]
Type=Application
Name=Xfce4-panel-reload
Exec=/bin/sh -c 'sleep 2;xfce4-panel -r'
StartupNotify=false
Terminal=false
Another way might be using a post-login script in your login manager, but it should wait for xfce4 to be running:
until p=$(pidof xfsettingsd)
do
sleep 1
done
xfce4-panel -r
Hi,
happy to be wrong about this, but as far as I know there is no s6-init package in Devuan.. you can install the s6 package, but all the init integration is not provided, so you have to serve yourself.
According to https://www.devuan.org/os/init-freedom s6 is supported, but I cannot manage to select it.
That page says " either available or being considered for inclusion "; I think only runit and openrc are provided as alternative init *for now*
Lorenzo
There is a gnuinos image build with s6 for trial use and testing:
https://www.gnuinos.org/mirror/daedalus … rimental)/
The announcement:
yemuyin wrote:Hola a tod@s
Es mi primer post para saludar a la comunidad, espero aprender y colaborar juntos con este estupendo SO Devuan Daedalus
Un saludo cordialBienvenido!
O bienvenida...!
Hola a tod@s
Es mi primer post para saludar a la comunidad, espero aprender y colaborar juntos con este estupendo SO Devuan Daedalus
Un saludo cordial
Bienvenido!
I've updated the isos
Btw, a fully jwm iso install, complete with jwmkit installed, would be interesting and awesome. Aka, first run would be already activated, etc...
Not strictly needed, necessary but it would be awesome.
Hi zapper, I did have the JWMkit in mind from the very beginning because the work done by Calvin Kent is realy impressive. As to gnuinos daedalus images, I explained in earlier posts -and also in the DNG mailing list- that I'm trying to fix some issues arising in the behavior of volume mount operations with vdev as device manager, that have been partially solved. Thus, the images will be released when I deem fit and, for sure, trying to cover a broader range of window managers and desktops, along with xfce and openbox.
Use "yt-dlp". Seems old (March) but is actually upto date & works fine.
Yes, it worked. Thanks.
The package is empty in daedalus
Most of our packages are from debian, unchanged. That includes python3-venv.
I guess that the required package is python3.X-venv (e.g, python3.11-venv in daedalus), instead of python3-venv.
I installed the following packages (in daedalus x86_64):
# apt-get install ninja-build meson texinfo python3-sphinx:native python3-sphinx-rtd-theme libcapstone-dev libaio-dev libjack-dev libpulse-dev libbpf-dev \
libbrlapi-dev libcap-ng-dev libcurl4-gnutls-dev libfdt-dev libfuse3-dev libiscsi-dev libncurses-dev libvirglrenderer-dev libva-dev libdrm-dev libgbm-dev libnfs-dev \
libnuma-dev libcacard-dev librbd-dev libglusterfs-dev libsasl2-dev libsdl2-dev libseccomp-dev libslirp-dev libspice-server-dev \
librdmacm-dev libibverbs-dev libibumad-dev liburing-dev libusb-1.0-0-dev libusbredirparser-dev libssh-dev libvdeplug-dev libxen-dev libpmem-dev \
device-tree-compiler gcc-s390x-linux-gnu gcc-alpha-linux-gnu gcc-powerpc64-linux-gnu gcc-sparc64-linux-gnu fcode-utils gcc-hppa-linux-gnu \
gcc-riscv64-linux-gnu gcc-arm-none-eabi flex bison gcc-power-pc-linux-gnu bc python3.11-venv
And the ./configure script of qemu-8.1.0-rc0 worked.
How to run another OS from a USB stick running live devuan_chimaera_4.0.3_amd64_desktop-live.iso? Without installing Devuan itself on the computer?
I tried installing QEMU, but it gives an error:
wget https://download.qemu.org/qemu-8.1.0-rc0.tar.xz
tar xvJf qemu-8.1.0-rc0.tar.xz
cd qemu-8.1.0-rc0
./configureUsing './build' as the directory for build output
WARNING: unrecognized host CPU, proceeding with 'uname -m' output 'x86_64'
python determined to be '/usr/bin/python3'
python version: Python 3.9.2*** Ouch! ***
Python's ensurepip module is not found.
It's normally part of the Python standard library, maybe your distribution packages it separately?
(Debian puts ensurepip in its python3-venv package.)
Either install ensurepip, or alleviate the need for it in the first place by installing pip and setuptools for '/usr/bin/python3'.ERROR: python venv creation failed
I tried in daedalus after installing python3.11-venv, and the configure script worked. But it's supposed to work with python3.7, python3.8,... as well. Look at the line 526 of configure.
Additional suggestion: configure your locales first.
If you want to install qemu, it would be easier to install it from the devuan repo instead of compiling it from source.
The lower version 8.0.3 should work:
Both Gnuinos Chimaera (installed on hdd) and Daedalus (from the live ISO) boot fine and run great here.
I am using the 64-bit Xfce version in both cases, from the last ISO.
Thank you Aitor!
Welcome
I you are using Xfce, I recommend you to upgrade both usbmount and xfce4-hopman-plugin. On the other hand, I use to disable the volume management in Thunar because there are some conflicts between vdev and gvfs-daemons/udisks not fixed yet. Devices are mounted/unmounted without issues, but it seems that cancellable operations like:
g_volume_mount (G_VOLUME (device->device),
G_MOUNT_MOUNT_NONE,
mount_operation,
cancellable,
thunar_device_operation_finish,
op);
don't receive any response and, therefore, the callback thunar_device_operation_finish -responsible for stopping the spinner when the operation finishes- is run only once the timeout has been expired, taking too long. The same goes for the umount process. And I think that this bug is related to libudev-compat.
Thanks for the info.
I am interested in the openbox version mainly. Are there any plans for an openbox live iso for daedalus?
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.
prospero wrote:Both Gnuinos Chimaera (installed on hdd) and Daedalus (from the live ISO) boot fine and run great here.
I am using the 64-bit Xfce version in both cases, from the last ISO.
Thank you Aitor!
please look at your booting time and compare with the same time at Star/Crowz linux!
I asked you if you were using vdev with sysvinit. Please, can you give me some details about your installation?
SpongeBOB wrote:Thank you all for your reply !
Thank you that have confirmed my thinking. I'm shocked that some people can post "tutorial" without mastering a bit the topic.... Internet peoples..
@boughtonp, oh great indeed I will use also a regex expression in grep to avoid to have the grep itself in the results.
ps aux | grep 'cron$'
Another way to avoid the unwanted expression might be using the syntax grep -v "unwanted_regex_expression". Therefore, you can avoid the grep itself as follows:
ps aux | grep "cron" | grep -v " grep "
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...
Thank you all for your reply !
Thank you that have confirmed my thinking. I'm shocked that some people can post "tutorial" without mastering a bit the topic.... Internet peoples..
@boughtonp, oh great indeed I will use also a regex expression in grep to avoid to have the grep itself in the results.
ps aux | grep 'cron$'
Another way to avoid the unwanted expression might be using the syntax grep -v "unwanted_regex_expression". Therefore, you can avoid the grep itself as follows:
ps aux | grep "cron" | grep -v " grep "
actually, my new system was unused. it boots in under 15 s.
Yesterday the comparable analog test with gnuinos need very more than one minute.
As because of electricity sparing because of the attack from Biden against Russia I am turning off the PC each time a go away and start new all the day of lot of times, this aspect of the use become a very important detail. Gnuinos is now dead for me, if I don´t find some way to change that...
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!
Hi,
As a suggestion, you may consider using
sv check dbus || exit <some_value>
instead of
sv start dbus || true
(sv start) is equal to (sv up + sv check), so the subtle difference is that I'm forcing the wanted status to be 'up' before the check;
as for true vs exit <some_value> I'm using the latter for hard dependency and true for soft dependency. Of course I may have wrongly set a dependency as soft instead of hard..
Ok, I understand. My thought was that sv check dbus started the service in case it was down.
Do you have a script that doesn't work for your use case? If yes please report it and I'll have a look again.
No, I haven't. Your scripts worked fine during the time I have spent testing them in daedalus. Nonetheless, if this happens, I'll let you know. Thanks!
Who the hell does control the network connections?
Some dhcp client, maybe? /etc/network/interfaces is for ifupdown
I've just installed Chimeara on my new(ish) Acer Aspire 3.
It hasn't set up wifi - when I ran the install it would only recognise the wired connection, so I completed the install with that.
I want to get WiFi working for use around the house and elsewhere, but it hasn't set anything up for it.I tried putting an entry in /etc/network/interfaces, just:
allow-hotplug wlan0
wlan0 inet dhcpand rebooted, but still ip address just shows the loopback and eth0 connections.
Any suggestions?
The machine came with Win 11 on it, and when I did the Windoze setup it didn't see wifi either, but when I had completed setup I was able to turn on
Wifi and connect without any problem.
Short answer from my mobile:
iface wlan0 inet dhcp
Your line is incomplete.
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?
Thanks Lorenzo. I thought that /lib/runit/runit-init was installed in runit-init, but it belongs to runit.