Posts by devuan_dk_fan

devuan_dk_fan · Other Issues

No error message at all that I can see, but it stops at the line:

[     9.003419] IPV6: ADDRCONF (NETDEV_CHANGE): eth0: link becomes ready

devuan_dk_fan · Other Issues

No luck There were no errors in the process at all, and there wasn't much feedback when I booted into the Devuan system either. The only thing that looked like an error was:

/bin/sh: can't access tty: job control turned off

Here is the relevant information from the process:

# update-initramfs -u -k all
update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64

Smooth. Relevant /etc/fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sdd1 during installation
UUID=f73498af-846e-447a-87d7-4f0b0b01818d /               ext4    errors=remount-ro 0       1
# /home was on /dev/sdd6 during installation
UUID=cf653dd3-5fc1-4f64-911c-cca7ee3ce248 /home           ext4    defaults        0       2
# swap was on /dev/sdd5 during installation
UUID=c6c5dab4-b097-4db1-a50a-e79e5c8628e5 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0

Relevant /boot/grub/grub.cfg info:

$ sudo nano /boot/grub/grub.cfg
menuentry "unknown Linux distribution (on /dev/sdd1)" --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-f73498af-846e-447a-87d7-4f0b0b01818d' {
        insmod part_msdos
        insmod ext2
        set root='hd3,msdos1'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos1 --hint-efi=hd3,msdos1 --hint-baremetal=ahci3,msdos1  f73498af-846e-447a-87d7-4f0b0b01818d
        else
          search --no-floppy --fs-uuid --set=root f73498af-846e-447a-87d7-4f0b0b01818d
        fi
        linux /boot/vmlinuz-3.16.0-4-amd64 root=/dev/sdd1
        initrd /boot/initrd.img-3.16.0-4-amd64

Extra credit work:

# grep -r MODULES /etc/initramfs-tools/
/etc/initramfs-tools/initramfs.conf:# MODULES: [ most | netboot | dep | list ]
/etc/initramfs-tools/initramfs.conf:MODULES=most
/etc/initramfs-tools/conf.d/driver-policy:MODULES=dep

# lsinitramfs /boot/initrd.img-3.16.0-4-amd64 | grep resume
scripts/local-premount/resume
bin/resume
conf/conf.d/resume

devuan_dk_fan · Desktop and Multimedia

My basic problem is that the MuseScore AppImage complains when I try to run it:

$ ./MuseScore-2.1-x86_64.AppImage
initScoreFonts 0x3d20bf0
PulseAudio Context Connect Failed with Error: Connection refused
init PulseAudio failed
no audio driver found
Cannot start I/O
sequencer init failed
Ignore SSL error: 6 The certificate has expired

I am experimenting with a minimal cli Devuan Jessie install with Trinity as the DE. I am new to Devuan and Trinity (as well as anything KDE related for that matter). Anyway, my main go to app for music is MuseScore. I use the AppImage version for a number of reasons, one of which is MuseScore has had a bug the developers don't seem to be able to lock down that creates static or feedback when using MIDI playback for a score.

I have discovered that Trinity uses a sound system called aRts. It seems to me that the above errors reflect a dependency on PulseAudio. If MuseScore absolutely needs PulseAudio, is it possible to get Trinity to work with PulseAudio? How? Alternatively, is it possible to get MuseScore working with aRts?

I wish the Trinity team had chosen another name, as there is so much cruft that pops up when searching for something about "Trinity", "TDE", "TDM" etc. I am hoping there are some Trinity users out there that can give some advice.

devuan_dk_fan · Other Issues

OK, this is what I got:

# update-initramfs -u -k all
update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
mkinitramfs: failed to determine device for /
mkinitramfs: workaround is MODULES=most, check:
grep -r MODULES /etc/initramfs-tools/

Error please report bug on initramfs-tools
Include the output of 'mount' and 'cat /proc/mounts'
update-initramfs: failed for /boot/initrd.img-3.16.0-4-amd64 with 1.

If the message is referring to the previous commands, there was no output, everything went smoothly, this time.

Here is what my /etc/initramfs-tools/modules file looks like:

# List of modules that you want to include in your initramfs.
# They will be loaded at boot time in the order below.
#
# Syntax:  module_name [args ...]
#
# You must run update-initramfs(8) to effect this change.
#
# Examples:
#
# raid1
# sd_mod
ehci-pci
ehci-orion
uhci-hcd

devuan_dk_fan · Other Issues

OK, I got part of the way:

# update-initramfs -k all
You must specify at least one of -c, -u, or -d.

Usage: /usr/sbin/update-initramfs [OPTION]...

Options:
 -k version     Specify kernel version or 'all'
 -c             Create a new initramfs
 -u             Update an existing initramfs
 -d             Remove an existing initramfs
 -t             Take over a custom initramfs with this one
 -b directory   Set alternate boot directory
 -v             Be verbose
 -h             This message

It looks like "-k" and "all" are the same thing. OK to just run:

# update-initramfs -k

???

Nope that doesn't work.

# update-initramfs -k vmlinuz-3.16.0-4-amd64

???

Nope. I also tried this:

# /usr/sbin/update-initramfs -k all
You must specify at least one of -c, -u, or -d.

Usage: /usr/sbin/update-initramfs [OPTION]...

Options:
 -k version     Specify kernel version or 'all'
 -c             Create a new initramfs
 -u             Update an existing initramfs
 -d             Remove an existing initramfs
 -t             Take over a custom initramfs with this one
 -b directory   Set alternate boot directory
 -v             Be verbose
 -h             This message

devuan_dk_fan · Other Issues

I am still getting an error with the following:

# mount -t devpts  /dev/pts
mount: can't find /dev/pts in /etc/fstab

Not sure if I can go ahead with the rest that you posted. Things are screwy enough as is

devuan_dk_fan · Other Issues

Hi again Ralph. I get the following error right off the bat:

# mount -t procfs none /proc
mount: unknown filesystem type 'procfs'

Probably not necessary, but I thought that I would check to see if things are in place:

# ls -l
total 92
drwxr-xr-x  2 root root  4096 Jan 25 18:20 bin
drwxr-xr-x  2 root root  4096 Jan 25 18:38 boot
drwxr-xr-x  4 root root  4096 Jan 25 18:08 dev
drwxr-xr-x 94 root root  4096 Jan 25 18:38 etc
drwxr-xr-x  2 root root  4096 Jan 25 18:07 home
lrwxrwxrwx  1 root root    31 Jan 25 18:11 initrd.img -> /boot/initrd.img-3.16.0-4-amd64
drwxr-xr-x 16 root root  4096 Jan 25 18:14 lib
drwxr-xr-x  2 root root  4096 Jan 25 18:13 lib64
drwx------  2 root root 16384 Jan 25 18:07 lost+found
drwxr-xr-x  3 root root  4096 Jan 25 18:07 media
drwxr-xr-x  2 root root  4096 Jan 25 18:08 mnt
drwxr-xr-x  2 root root  4096 Jan 25 18:08 opt
drwxr-xr-x  2 root root  4096 May  9  2016 proc
drwx------  2 root root  4096 Jan 25 19:03 root
drwxr-xr-x  3 root root  4096 Jan 26 08:33 run
drwxr-xr-x  2 root root  4096 Jan 25 18:38 sbin
drwxr-xr-x  2 root root  4096 Jan 25 18:08 srv
drwxr-xr-x  2 root root  4096 May 29  2015 sys
drwxrwxrwt  2 root root  4096 Jan 25 18:22 tmp                                                                                                                                                                    
drwxr-xr-x 10 root root  4096 Jan 25 18:08 usr                                                                                                                                                                    
drwxr-xr-x 11 root root  4096 Jan 25 18:08 var                                                                                                                                                                    
lrwxrwxrwx  1 root root    27 Jan 25 18:11 vmlinuz -> boot/vmlinuz-3.16.0-4-amd64

/boot# ls -l
total 9604
-rw-r--r-- 1 root root  157756 Dec 14 22:27 config-3.16.0-4-amd64
-rw-r--r-- 1 root root 3845607 Jan 25 18:38 initrd.img-3.16.0-4-amd64
-rw-r--r-- 1 root root 2684316 Dec 14 22:27 System.map-3.16.0-4-amd64
-rw-r--r-- 1 root root 3137712 Dec 14 22:25 vmlinuz-3.16.0-4-amd64

So at least on the surface, things look like they are where they are supposed to be. I have been searching to find a reason for the "unknown file system" error up top, but I haven't found anything relevant to this situation yet.

# mount -t sysfs none /sys
# mount -t devpts  /dev/pts
mount: can't find /dev/pts in /etc/fstab

As you can see, mounting the sys file system went fine, but the next command also kicked up an error. Am I correct in my assumption that this error means that there are no "/dev/" or UUID mount points in /etc/fstab?

devuan_dk_fan · Other Issues

Hmm. This is really outside my frame of reference, so please bear with me. As I understand it, I was supposed to make the GRUB "linux" boot line for my Devuan install to look like this when I start the computer up and temporarily edit the boot settings:

linux /vmlinuz root=/dev/sdd1 break=mount

I was expecting a cli of sorts from your description, but I just got the following:

spawning shell within the initramfs
modeprobe: module ehci-pci not found in modules.dep
modeprobe: module ehci-orio not found in modules.dep
modeprobe: module uhci-hcd not found in modules.dep

The fundamental problem is that even if I had gotten a command line, what should I have done?
A vi /etc/fstab? Not sure where I would be residing in the initrd file system, nor how I would gain access to /etc/fstab

devuan_dk_fan · Other Issues

OK, I have rechecked the sha256sum for the devuan_jessie_1.0.0_amd64_CD.iso and I have burned the .iso to another USB pen drive. I have then succeeded installing a minimal cli system without a DE on the laptop and have then added the Trinity DE repos and installed without a problem.

On the other hand, I have tried the same install on my tower computer. I erased my MiyoLinux install and then installed the same minimal cli system as installed on my laptop, but still get the same errors at boot. I have confirmed that the UUID entry in GRUB matches the actual UUID for /dev/sdd1. I have also followed Ralph's advice and used # chroot:

# mount /dev/sdd1 /mnt/devuan
leviathan brian # chroot /mnt/devuan          
# cd /sbin
root@leviathan:/sbin# ls -l
total 7004

-rwxr-xr-x 1 root root     37064 May 29  2015 init

As Ralph pointed out, the chroot made the difference as to which system install that I am in

Nothing has as of yet suggested a solution to the above errors, so while we know it isn't systemd that is at play, I have no idea what is actually going on here.

devuan_dk_fan · Other Issues

The weird thing, as you can see from above, the UUIDs for the partition and the GRUB entry are the same.

devuan_dk_fan · Other Issues

Hi Ralph. Thanks for the reply. Ahh. Understood. The main issue is however, that I am unable to get a Devuan system up and running, as no matter what I do, I consistently get the same errors:

target file system doesn't have requested /sbin/init
mounting on /root/dev failed. no such file or directory
no init found. try passing init=bootarg.
/bin/sh: cant' access tty: job control turned off.
switched to clocksource tsc

If these are unlikely to be caused by an errant systemd, what is causing them? I have tried searching and solving each error, but I don't seem to have any luck.

I am experimenting with a Miyo system running Trinity right now, but can try reinstall a minimal cli Devuan system, if I have an idea how to solve the above errors.

devuan_dk_fan · Other Issues

OK, something is definitely wrong here. I pre-formatted the partitions on the target hard drive and re-burned the devuan_jessie_1.0.0_amd64_CD.iso onto the USB pen drive. I again ran into the same errors and the same problems as above - systemd all over the place. I don't dare erase Linux Mint Sylvia KDE as I could still end up not being able to get a working Devuan system to install.

Please keep me up to date on any progress as I would like to get a working Devuan system installed.

devuan_dk_fan · Other Issues

If any of the developers at Devuan want me to mirror and upload a copy of the USB pen drive that I am using or the actual hard drive install, please let me know now (with instructions), because otherwise, I will just burn another copy of the Jessie installer and try a reinstall. I am also seriously considering wiping my Linux Mint install, to rule out the possibility of systemd infiltration.

devuan_dk_fan · Other Issues

Weird indeed:

$ sudo mkdir /mnt/devuan
$ sudo mount /dev/sdd1 /mnt/devuan  
$ cd /mnt/devuan
$ cd /sbin
$ ls -l
total 18968
lrwxrwxrwx 1 root root        20 Dec 21 13:16 init -> /lib/systemd/systemd

$ cd /lib/systemd/     
$ ls -l
total 8404
drwxr-xr-x  2 root root    4096 Nov 27 10:57 network
drwxr-xr-x 28 root root   20480 Jan 11 07:49 system
-rwxr-xr-x  1 root root 1577232 Oct 27 12:12 systemd
-rwxr-xr-x  1 root root   14600 Oct 27 12:12 systemd-ac-power
-rwxr-xr-x  1 root root   55744 Oct 27 12:12 systemd-activate
-rwxr-xr-x  1 root root   92752 Oct 27 12:12 systemd-backlight
-rwxr-xr-x  1 root root   47680 Oct 27 12:12 systemd-binfmt
-rwxr-xr-x  1 root root  105088 Oct 27 12:12 systemd-bootchart
-rwxr-xr-x  1 root root  359632 Oct 27 12:12 systemd-bus-proxyd
-rwxr-xr-x  1 root root  273616 Oct 27 12:12 systemd-cgroups-agent
-rwxr-xr-x  1 root root   92752 Oct 27 12:12 systemd-cryptsetup
-rwxr-xr-x  1 root root  307224 Oct 27 12:12 systemd-fsck
-rwxr-xr-x  1 root root   76376 Oct 27 12:12 systemd-fsckd
-rwxr-xr-x  1 root root   31152 Oct 27 12:12 systemd-hibernate-resume
-rwxr-xr-x  1 root root  339152 Oct 27 12:12 systemd-hostnamed
-rwxr-xr-x  1 root root  281808 Oct 27 12:12 systemd-initctl
-rwxr-xr-x  1 root root  326224 Oct 27 12:12 systemd-journald
-rwxr-xr-x  1 root root  347344 Oct 27 12:12 systemd-localed
-rwxr-xr-x  1 root root  618520 Oct 27 12:12 systemd-logind
-rwxr-xr-x  1 root root   51792 Oct 27 12:12 systemd-modules-load
-rwxr-xr-x  1 root root  847104 Oct 27 12:12 systemd-networkd
-rwxr-xr-x  1 root root  125520 Oct 27 12:12 systemd-networkd-wait-online
-rwxr-xr-x  1 root root   35320 Oct 27 12:12 systemd-quotacheck
-rwxr-xr-x  1 root root   35256 Oct 27 12:12 systemd-random-seed
-rwxr-xr-x  1 root root   51800 Oct 27 12:12 systemd-remount-fs
-rwxr-xr-x  1 root root   31152 Oct 27 12:12 systemd-reply-password
-rwxr-xr-x  1 root root  667664 Oct 27 12:12 systemd-resolved
-rwxr-xr-x  1 root root   92752 Oct 27 12:12 systemd-rfkill
-rwxr-xr-x  1 root root  146032 Oct 27 12:12 systemd-shutdown
-rwxr-xr-x  1 root root   72272 Oct 27 12:12 systemd-sleep
-rwxr-xr-x  1 root root   92752 Oct 27 12:12 systemd-socket-proxyd
-rwxr-xr-x  1 root root   51800 Oct 27 12:12 systemd-sysctl
-rwxr-xr-x  1 root root    1324 Oct 27 04:22 systemd-sysv-install
-rwxr-xr-x  1 root root  340016 Oct 27 12:12 systemd-timedated
-rwxr-xr-x  1 root root  141904 Oct 27 12:12 systemd-timesyncd
-rwxr-xr-x  1 root root  453240 Oct 27 12:12 systemd-udevd
-rwxr-xr-x  1 root root  281808 Oct 27 12:12 systemd-update-utmp
-rwxr-xr-x  1 root root   35256 Oct 27 12:12 systemd-user-sessions
drwxr-xr-x  2 root root    4096 Nov 27 11:22 system-generators
drwxr-xr-x  2 root root    4096 Nov 27 10:57 system-preset
drwxr-xr-x  2 root root    4096 Apr 12  2016 system-shutdown
drwxr-xr-x  2 root root    4096 Nov 27 11:22 system-sleep

devuan_dk_fan · Other Issues

OK, I reinstalled the system again (no de or wm) from the Jessie CD .iso. I tried installing the linux-image-3.16.0-4-amd64 rather than linux-image-amd64, but there was no change. I still get the same messages. Interestingly, I booted into Linux Mint and mounted the /dev/sdd1 partition where the Devuan install resides, cd into sbin and ran # ls -l The information from /sbin/init shows that it is pointing to /lib/systemd/systemd. I have a Devuan system on a laptop, with a similar system, where I later added "kde-standard", where the /sbin/init file does not point anywhere. I assume that this has something to do with the install procedure wonking out because I didn't install a boot loader, as I am using my Linux Mint GRUB on /dev/sda1. Weirdly, I didn't run into this issue when I installed this system the first time on my tower computer. The only thing that I can think of that I have done differently, from the first time around, is that I make sure that the Devuan installer doesn't format and include the swap partition for my Linux Mint install on /dev/sda5.

devuan_dk_fan · Other Issues

The two uuid entries are the same:

$ blkid
/dev/sdd1: UUID="fd47cef5-ce5e-4090-8bfa-aef277a49e3e"

and the /boot/grub/grub.cfg reads:

menuentry "unknown Linux distribution (on /dev/sdd1)" --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-fd47cef5-ce5e-4090-8bfa-aef277a49e3e' {
        insmod part_msdos
        insmod ext2
        set root='hd3,msdos1'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos1 --hint-efi=hd3,msdos1 --hint-baremetal=ahci3,msdos1  fd47cef5-ce5e-4090-8bfa-aef277a49e3e
        else
          search --no-floppy --fs-uuid --set=root fd47cef5-ce5e-4090-8bfa-aef277a49e3e
        fi
        linux /vmlinuz root=/dev/sdd1
        initrd /initrd.img

devuan_dk_fan · Other Issues

4.10 is the Linux Mint kernel. The Devuan kernel is the "unknown Linux distribution" on /dev/sdd1.

devuan_dk_fan · Other Issues

Hmm. Running into some odd behavior on a reinstall. I get the following errors:
target file system doesn't have requested /sbin/init
mounting on /dev on /root/dev failed: no such file or directory
no init found. try passing init=bootarg
/bin/sh: can't access tty: job control turned off.
switched to clocksource tsc

I have tried running fsck /dev/sdd1 to no avail.

I have a multiboot system with Linux Mint KDE Sylvia (18.3), Windows 10 and now Devuan Jessie minimal (no DE or WM).

Here is my configuration:

$ sudo fdisk -l

Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xd409f079

Device     Boot    Start        End    Sectors  Size Id Type
/dev/sda1  *        2048   33867282   33865235 16.2G 83 Linux
/dev/sda2       33873918 3907028991 3873155074  1.8T  5 Extended
/dev/sda5       33873920   33939455      65536   32M 82 Linux swap / Solaris
/dev/sda6       33941504 3907028991 3873087488  1.8T 83 Linux

Disk /dev/sdb: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B0241C9D-3B5D-4BB7-A133-5B6FEDC6C1D0

Device     Start        End    Sectors  Size Type
/dev/sdb1   2048 7814035455 7814033408  3.7T Microsoft basic data

Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00034d54

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sdc1  *          2048 1951774217 1951772170 930.7G  7 HPFS/NTFS/exFAT
/dev/sdc2       1951774720 1953519615    1744896   852M 27 Hidden NTFS WinRE

Disk /dev/sdd: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x5d0c65f5

Device     Boot    Start        End    Sectors   Size Id Type
/dev/sdd1  *        2048   34818047   34816000  16.6G 83 Linux
/dev/sdd2       34828286 1953523711 1918695426 914.9G  5 Extended
/dev/sdd5       34828288   34893823      65536    32M 82 Linux swap / Solaris
/dev/sdd6       34895872 1953523711 1918627840 914.9G 83 Linux

Disk /dev/sde: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x0007fb19

Device     Boot Start        End    Sectors  Size Id Type
/dev/sde1        2048 3907028991 3907026944  1.8T  7 HPFS/NTFS/exFAT

$ sudo update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.10.0-42-generic
Found initrd image: /boot/initrd.img-4.10.0-42-generic
Found linux image: /boot/vmlinuz-4.10.0-38-generic
Found initrd image: /boot/initrd.img-4.10.0-38-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Windows 10 (loader) on /dev/sdc1
Found unknown Linux distribution on /dev/sdd1
done

The idea is of course to upgrade to ASCII, once I can boot into the system.

devuan_dk_fan · Other Issues

Many thanks for the info. As I understand it, the only way to install KDE on Devuan at this time, is to do as I did? So the correct order would be: net install, edit the sources.list file for ascii, upgrade, and then do an apt-get install kde-standard?

devuan_dk_fan · Other Issues

No worries I always use the latest MuseScore AppImage partially because I sometimes run into dependency issues, partially because MuseScore has a MIDI issue that has been dogging them for a long time, that they don't seem to be able to stamp out. Sometimes when playing a score, there is a lot of static/feedback noise that makes it unbearable to listen to what you have written, which kind of is the point of MIDI playback in the first place

BTW, I would like to advertise another posting of mine on the forum, that I am not getting any response on:

"Vanilla KDE Jessie Devuan system prompts for USB pen drives." I still haven't been able to figure that one out yet, and now I am testing a vanilla KDE Jessie Devuan install both on a laptop as well as on a home built tower computer, so it would be nice to get it sorted.

devuan_dk_fan · Other Issues

Cool

devuan_dk_fan · Other Issues

Nice to hear from you You are doing a great job with MiyoLinux, as are all of the developers of other "spins", and much appreciated. I think that the plethora of spins is part of what makes the Devuan community vibrant and will hopefully draw new users to Devuan based systems.

I have experimented a bit with AppImages and found that all of the ones that I have tried, worked out of the box with a bog standard Devuan install, so I can confirm that everything necessary is in the official repos. A little tip, the AppImage that I have found so far with the largest amount of dependencies is the AppImage version of MuseScore musecore.org. I think the dependency issue is just a matter of not cutting into the bare metal, when doing a spin, or maybe including a disclaimer with a list of possible dependencies needed for running AppImages

All the best...

devuan_dk_fan · Other Issues

In general, I detect a certain amount of disdain these days for non-commercial Linux distributions. A narrowing of minds appears to be occurring within the sector of the Linux community that supports systemd. I dare to predict that the next major battle for hearts and minds will take place around a replacement for X11. Just search the KDE Neon for "i3" and you will discover that the Neon team originally excluded the possibility of switching DEs/WMs because the consensus was that most alternative WMs will not survive the switch to Wayland. While that may be true it doesn't preclude new WMs that can work with Wayland in the future!

devuan_dk_fan · Other Issues

I have been having an interesting exchange on http://discourse.appimage.org regarding AppImage dependencies. I have run into the problem that AppImages refuse to run on Devuan derivatives due to lacking dependencies. There are a fair amount and a bit of a bear to track down each one, so I thought that I would post a link to the exchange: https://discourse.appimage.org/t/musesc … 4bit/279/6 The final post provides a list of those dependencies that the host systems are expected to take care of.

The potential that I see for AppImage and Devuan is that I am reasonably confident that AppImages will never pull in systemd, unlike with snaps or flatpaks that very likely could draw systemd as a dependency in the sandboxed group of dependencies.

I hope this helps the Devuan team and anyone else interested in keeping a systemd free system.

devuan_dk_fan · Other Issues

Hi. I am new to Devuan (never used Debian) and have come across an irritating issue. I have a vanilla KDE Jessie Devuan system running on a laptop. Unlike other Devuan DEs, I get prompted for root (sudo) password each time that I want to mount a USB pen drive. As mentioned, this doesn't happen with the Devuan MATE or XFCE4 DEs and I am wondering - why?

$ ls -l /media | grep $USER
drwxr-x---+ 2 root root 4096 Jan 19 16:24 username

$ getfacl /media/usernamegetfacl: Removing leading '/' from absolute path names# file: media/username# owner: root# group: rootuser::rwxuser:username:r-xgroup::---mask::r-xother::---

Is this related with a KDE specific issue? How do I change this so I don't get prompted for a password all the time?

The officially official Devuan Forum!

#76 Re: Other Issues » Vanilla KDE Jessie Devuan system prompts for USB pen drives. » 2018-01-27 01:55:18

#77 Re: Other Issues » Vanilla KDE Jessie Devuan system prompts for USB pen drives. » 2018-01-26 23:16:00

#78 Desktop and Multimedia » New Devuan Trinity install on laptop - need MuseScore to work. » 2018-01-26 19:51:14

#79 Re: Other Issues » Vanilla KDE Jessie Devuan system prompts for USB pen drives. » 2018-01-26 12:02:10

#80 Re: Other Issues » Vanilla KDE Jessie Devuan system prompts for USB pen drives. » 2018-01-26 10:26:31

#81 Re: Other Issues » Vanilla KDE Jessie Devuan system prompts for USB pen drives. » 2018-01-26 10:15:55

#82 Re: Other Issues » Vanilla KDE Jessie Devuan system prompts for USB pen drives. » 2018-01-26 07:35:45

#83 Re: Other Issues » Vanilla KDE Jessie Devuan system prompts for USB pen drives. » 2018-01-25 23:39:04

#84 Re: Other Issues » Vanilla KDE Jessie Devuan system prompts for USB pen drives. » 2018-01-25 18:01:41

#85 Re: Other Issues » Vanilla KDE Jessie Devuan system prompts for USB pen drives. » 2018-01-25 16:42:46

#86 Re: Other Issues » Vanilla KDE Jessie Devuan system prompts for USB pen drives. » 2018-01-25 14:58:49

#87 Re: Other Issues » Vanilla KDE Jessie Devuan system prompts for USB pen drives. » 2018-01-25 08:49:27

#88 Re: Other Issues » Vanilla KDE Jessie Devuan system prompts for USB pen drives. » 2018-01-25 04:50:34

#89 Re: Other Issues » Vanilla KDE Jessie Devuan system prompts for USB pen drives. » 2018-01-24 17:08:16

#90 Re: Other Issues » Vanilla KDE Jessie Devuan system prompts for USB pen drives. » 2018-01-24 10:39:50

#91 Re: Other Issues » Vanilla KDE Jessie Devuan system prompts for USB pen drives. » 2018-01-24 07:07:15

#92 Re: Other Issues » Vanilla KDE Jessie Devuan system prompts for USB pen drives. » 2018-01-24 06:36:51

#93 Re: Other Issues » Vanilla KDE Jessie Devuan system prompts for USB pen drives. » 2018-01-23 23:19:44

#94 Re: Other Issues » Vanilla KDE Jessie Devuan system prompts for USB pen drives. » 2018-01-23 08:08:45

#95 Re: Other Issues » AppImage and Devuan (special note for derivatives such as MiyoLinux). » 2018-01-22 22:28:08

#96 Re: Other Issues » AppImage and Devuan (special note for derivatives such as MiyoLinux). » 2018-01-21 17:28:08

#97 Re: Other Issues » AppImage and Devuan (special note for derivatives such as MiyoLinux). » 2018-01-21 07:55:46

#98 Re: Other Issues » AppImage and Devuan (special note for derivatives such as MiyoLinux). » 2018-01-20 23:46:51

#99 Other Issues » AppImage and Devuan (special note for derivatives such as MiyoLinux). » 2018-01-20 09:53:01

#100 Other Issues » Vanilla KDE Jessie Devuan system prompts for USB pen drives. » 2018-01-20 09:39:15

Board footer