Good observation. Most of the repository is empty. You will only find packages that were changed by devuan in the devuan repositories. The packages will be in /pool, but you must be sure to get the right version.The way amprolla works is to merge the debian repos with the devuan repos and serve you the correct packages for your system.

If you want to download any packages in devuan:

apt-get download <package>
or
aptitude download <package>

If you want to download from the web, use a devuan repo url for packages that have been modified by devuan and go to packages.debian.org for packages we have not modified. DO NOT ERR! (It's safer to use the package manager to get the packages.)

I believe someone is working on a web interface for searching files, but I don't know the current status.

I think the libpolkit packages you get depend on which desktop and login manager you install. In some cases, libpolkit-backend-1-0-consolekit is needed instead of the elogind backend. There may be more changes planned for that mess.

The libsystemd0 dependency issue is well known. It would be nice to get rid of it, but it's in more and more packages with each release. And it does nothing if systemd isn't present and running. And systemd is not present and cannot be installed from devuan repositories.

I installed lxde yesterday and was getting the same error (No session for pid#). The pid is always for lxpolkit. Removing lxpolkit solved it for me. Shutdown buttons were working before and after removing lxpolkit.

I also experimented with running 'pam-auth-update' to alternately disable elogind or consolekit, and it seems to be working normally with either one.

Here's a list of the kits that were installed.

user@devuan:~$ dpkg -l | grep consolekit
ii  consolekit                             0.4.6-6                           amd64        framework for defining and tracking users, sessions and seats
ii  libpolkit-backend-1-0-consolekit:amd64 0.105-18+devuan2.4                amd64        PolicyKit backend API
user@devuan:~$ dpkg -l | grep policykit
ii  lxqt-policykit                         0.11.1-1                          amd64        LXQt authentication agent for PolicyKit
ii  lxqt-policykit-l10n                    0.11.2-1                          all          Language package for lxqt-policykit
ii  policykit-1                            0.105-18+devuan2.4                amd64        framework for managing administrative policies and privileges
ii  policykit-1-gnome                      0.105-6                           amd64        authentication agent for PolicyKit
user@devuan:~$ dpkg -l | grep elogind
ii  elogind                                234.4-1+devuan1.5                 amd64        user, seat and session management daemon
ii  libelogind0:amd64                      234.4-1+devuan1.5                 amd64        user, seat and session management library
ii  libpam-elogind:amd64                   234.4-1+devuan1.5                 amd64        elogind PAM module
user@devuan:~$ dpkg -l |grep polkit
ii  libpolkit-agent-1-0:amd64              0.105-18+devuan2.4                amd64        PolicyKit Authentication Agent API
ii  libpolkit-backend-1-0-consolekit:amd64 0.105-18+devuan2.4                amd64        PolicyKit backend API
ii  libpolkit-gobject-1-0-systemd:amd64    0.105-18+devuan2.4                amd64        PolicyKit Authorization API
ii  libpolkit-qt5-1-1:amd64                0.112.0-5                         amd64        PolicyKit-qt5-1 library
rc  lxpolkit                               0.5.3-2                           amd64        LXDE PolicyKit authentication agent

(Edited to add 'dpkg -l |grep polkit')

Edit2: I added
libpolkit-backend-1-0-elogind (0.105-18+devuan2.4)
libpolkit-gobject-1-0-elogind (0.105-18+devuan2.4)

That removed libpolkit-backend-1-0-consolekit and libpolkit-gobject-1-0-systemd. I had to run 'pam-auth-update' and enable elogind to get shutdown buttons working again.

Run 'pam-auth-update' to enable elogind and disable consolekit.
Install: libpolkit-backend-1-0-elogind libpolkit-gobject-1-0-elogind
Log out/in

I've got xfce with lightdm working with elogind on one install this way. Other install is more elusive.

FWIW, there's a newer version of desktop-base (2.0.2) in ascii-proposed that supports lightdm (you'll get the purpy background on the login screen). Not sure why you'd want d-b for miyo unless you want devuan theming or you're hacking the alternatives system to add miyo theme.

arjan, does it eventually shut down, or does it hang forever? I get about a 30-second delay during shutdown. It's a known problem. I don't know if there's a fix.

https://bugs.debian.org/cgi-bin/bugrepo … bug=792552

Someone on that thread also mentioned this one:
https://bugs.debian.org/cgi-bin/bugrepo … bug=791944

I don't understand what this is supposed to do.

tor-resolve devuanfwojg73k6r.onion
Feb 06 10:16:17.483 [warn] Got SOCKS5 status response '4': host is unreachable
Feb 06 10:16:17.483 [warn] devuanfwojg73k6r.onion is a hidden service; those don't have IP addresses. You can use the AutomapHostsOnResolve option to have Tor return a fake address for hidden services.  Or you can have your application send the address to Tor directly; we recommend an application that uses SOCKS 5 with hostnames.

I can confirm that tor and tor+http give the same results.

root@ascii:/home/user# apt-get update
Get:1 tor+http://devuanfwojg73k6r.onion/merged ascii InRelease [22.2 kB]
Get:2 tor+http://devuanfwojg73k6r.onion/merged ascii-updates InRelease [22.2 kB]                                          
Get:3 tor+http://devuanfwojg73k6r.onion/merged ascii-security InRelease [21.6 kB]                                         
Get:4 tor+http://devuanfwojg73k6r.onion/merged ascii/main amd64 Packages [7,232 kB]                                       
Get:5 tor+http://devuanfwojg73k6r.onion/merged ascii-security/main amd64 Packages [246 kB]                                
Fetched 7,545 kB in 3min 37s (34.7 kB/s)                                                                                  
Reading package lists... Done
root@ascii:/home/user# aptitude -s full-upgrade
The following packages will be upgraded: 
  chromium p7zip p7zip-full 
The following packages are RECOMMENDED but will NOT be installed:
  fonts-liberation 
3 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 47.0 MB of archives. After unpacking 657 kB will be used.

Note: Using 'Simulate' mode.
Do you want to continue? [Y/n/?] n
Abort.

root@ascii:/home/user# apt-get update
Hit:1 tor://devuanfwojg73k6r.onion/merged ascii InRelease  
Hit:2 tor://devuanfwojg73k6r.onion/merged ascii-updates InRelease
Hit:3 tor://devuanfwojg73k6r.onion/merged ascii-security InRelease
Reading package lists... Done
root@ascii:/home/user# aptitude -s full-upgrade
The following packages will be upgraded: 
  chromium p7zip p7zip-full 
The following packages are RECOMMENDED but will NOT be installed:
  fonts-liberation 
3 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 47.0 MB of archives. After unpacking 657 kB will be used.

Note: Using 'Simulate' mode.
Do you want to continue? [Y/n/?] n
Abort.

Where is suse installed, and what does the grub.cfg entry for suse look like? Did you try what I suggested in my last post on that other thread? (i.e. try booting suse from grub command-line.)

I agree that it would be helpful to have synaptic installed by default. From there, you can add whatever else you need without having to go to command line. If you want that whole list included, then what you're really asking for is a DVD, not a CD. All of that will not fit on a CD. Firefox-esr is on the CD and so is firmware. You can install those pretty easily. Mount your usb to /media/cdrom so that apt can find it. Then apt-get install firefox-esr firmware-<whatever>

Of course, if you use a third-party, unsupported usb writer, you're on your own. I don't know what rufus does. Since it uses fat32, I assume it works somewhat like refracta2usb, which you also could use to make the installer usb, and with which you would also have run into serious problems.

The recommended method is to use dd, cp or cat to image the usb. If that didn't work for you, it might make sense to figure out why and correct the situation. And if you do it that way, you will see the nice purple grub background when you boot the installer.

But I will say that your timing is good. Installer isos for ascii are coming soon, and we can look at the package selection for the CD and make some changes (I hope.) I had not looked at the package list for the CD in many months, and I forgot that synaptic is not on the CD at all.

Extlinux (syslinux) works well and is easy to configure. I posted a howto in the Documentation section a few months ago. It's easy to switch back and forth between extlinux and grub, in case you try it and don't like it.

One more thing - it would be better if you did not ask the same questions in multiple threads. Now the information is scattered all over the forum.

The default network manager is wicd.

If you want a complete desktop, and you don't want to use a network mirror, use the DVD instead of the CD, and you won't be missing so much.
What's the full name of the iso you used?

The firmware directory contains symbolic links so that they are easily found and at the same time are in their proper place in pool without having two copies on the media.

Virtualbox is in the jessie repo. You need to add contrib to your sources.
Mugshot is in the repo.
I didn't check the others you were looking for.

Cool! We're almost there.

Here's my quick summary of the situation.
- You can boot from the mint grub if you specify root=uuid.
- The resume file contains a valid uuid for your swap partition, and boot isn't hanging with a message about not being able to find some uuid that doesn't exist.
- We don't know Who's on first base.

What I would do first is boot into devuan the way you did.

- Run 'fdisk -l' to see if devuan is on /dev/sdd1 today. If it is, run

grub-install /dev/sdd

and if it's not on sdd, then use whatever it's calling itself. (whole drive, not partition)

- Reboot and press whatever key gets you the boot device menu. Might be F8 or F12, might be ESC or something else. It should tell you on screen before you get to the grub menu. When you get there, choose the drive with devuan on it. That will temporarily make it the first drive, and you should get to devuan's grub menu. Boot the first option (Devuan) to make sure it really works.

This should all work perfectly, and it will show you that devuan can boot itself from the first hard disk.

Next step - I give you special powers to turn you into a super-gnuru.

Reboot, do not go to the boot device menu. Just go to the mint grub menu.
Press "c"
You will get a prompt that says:   grub>

Type the following, and then press TAB a couple of times.

set root=(hd0

You'll get a list of partitions. You should be able to figure out which disk grub is calling hd0.
Erase the 0 and replace it with 1. Press TAB a couple of times. Repeat with 2 and 3.

Once you figure out what mint's grub wants to call the disk with devuan on it, enter the following commands. We expect it to be (hd3,msdos1) but it probably won't be. I'll just use that for the example, but you should use what you find.

set root=(hd3,msdos1)
linux /vmlinuz ro root=/dev/sdd1   #change this to wherever it is according to the previous command.
initrd /initrd.img
boot

It should boot into devuan.

If you want a menu entry for devuan in the mint boot menu (one that works, I mean) you can create a custom one.

Boot mint.
Edit /etc/grub.d/40_custom and add

menuentry 'Devuan on sdd1' {
  set root=(hd3,msdos1)  # or wherever it is
  linux /vmlinuz ro root=/dev/sdd1  # or use the root=uuid here
  initrd /initrd.img
}

Save the file and run update-grub. It will be added to mint's boot menu.

That's all.

Welcome to grub hell. GRUB and the kernel don't always agree on what is the first disk.I need to reply a few posts back before I even think about your last post.

cat /conf/conf.d/resume would give the error you got. Are you sure you didn't use a leading slash?

If you're in the extracted directory, cat conf/conf.d/resume should output the same line that's in /etc/initramfs-tools/resume and that should be your swap partition's uuid. It gets used when you return from hibernation to disk.

OK, back to the immediate problem. Do you change the order of the disks when you boot the diffrerent systems? That could be done by going into the bios and changing the hard disk order or by calling up the boot device menu and selecting different disks before the grub menu comes up.

Are you booting from usb on any of these occasions? GRUB will probably see the usb as hd0 when you do, and all the internal disks get bumped up one number.

As I understand it, right now you are using mint's grub to boot devuan. If you want to get rid of mint, you'll need to use devuan's grub to boot. Are you going to change the order of the hard disks when you do?

I'm posting this now, before I tell you to do something wrong.

Edit: This should be first. When you get to
'[     9.003419] IPV6: ADDRCONF (NETDEV_CHANGE): eth0: link becomes ready"
Press ENTER to see if you get a command prompt, or press alt-F2 to see if you get a console login screen.

OK, that's the end of the edit. Original message is below.
-------

To see what's inside resume, you'll need to extract the initrd. You can do this as ordinary user.

mkdir extracted
zcat /boot/initrd.img-3.16.0-4-amd64 | cpio -i
cat conf/conf.d/resume

It might contain a reference to a wrong or non-existent partition.

If you change or remove that file to make a modified initrd, repack it (as user)

find . -print0 | cpio -0 -H newc -o | gzip -c > ../custom-initrd

You'll have a file named custom-initrd in the directory above extracted.

Then make a backup copy of the existing initrd and copy the new one into place. (su to root or use sudo)

cp /boot/initrd.img-3.16.0-4-amd64 /boot/initrd.img-3.16.0-4-amd64.bak
cp ../custom-initrd /boot/initrd.img-3.16.0-4-amd64

Cross fingers and reboot.