better now? 

That one isn't finding kernel modules also. and fails in other ways...sry, I didn't copy errors.
Off to find that ascii mini that worked for me and SAVE it this time..LoL

asta

Yes..thanks for sharing!
This IS great for someone like myself...who dislikes the gaagle control and intrusive ads! 
I don't visit the site...just input the link - and wah`la... ad-less!
A shame that public treasures, got owned by corporate smucks.

and yes...works on MANY other sites!!

Would someone ask those 2 guys, to move off-camera!?
Where's everyone's 'name-tag'? I donno whose who...Even the bearded guy ~ we get to watch allot.   Whom is he?
LoL...
nuff 4 2day....have fun folks.

Your having trouble installing 'Tor', in Heads? or simply want to add it to your working devuan?
The rate Tor updates (and often), might be a good reason it's not in the repos.

Must you have the 'source' package?
Tor's package here, is an 'extract' and 'works' install--
from where-ever you decide to run it from. And 'updates' on it's own.   (with your knowledge & approval)

We also have access to Opendns (memory might be off!) that I use in my home router.
Another option is OpenVPN...

Yes fsmithred, intel-microcode package installed...I also checked that cpio, gzip, & others were installed.
miyoxtra's lite on preinstalling abunch of packages...its good to check.
As noted above somewhere, I first successed unpacking the img file in Refracta9.

~$ file /boot/initrd.img-4.9.0-8-amd64
	/boot/initrd.img-4.9.0-8-amd64: XZ compressed data

That worked just as you typed it would, being XZ compressed data.

I then checked my 5 other installs with the same result of:

$ file /boot/initrd.img-4.9.0-5-amd64
/boot/initrd.img-4.9.0-5-amd64: ASCII cpio archive (SVR4 with no CRC)

Same result for the /boot/initrd.img-4.19.0-2-amd64.
Now that's answered -

ralph.ronnquist, thanks for your post...this is my official 1st introduction to cpio.

$ cat initrd.img-4.9.0-5-amd64 | ( cpio -i ; file - )
62 blocks
/dev/stdin: ASCII cpio archive (SVR4 with no CRC)

That unpacked a kernel folder,->x86 folder->microcode folder->AuthenticAMD.bin file.

$ cat initrd.img-4.9.0-5-amd64 |  ( cpio -i ; gunzip | cpio -i )
62 blocks

gzip: stdin: not in gzip format
cpio: premature end of archive

Again, a kernel folder, ->x86 folder->microcode folder->AuthenticAMD.bin file.
New to me, but you guys know this already.
Now on to:

$ cat initrd.img-4.9.0-5-amd64 |  ( cpio -i ; cat > ramdisk.gz )
62 blocks

$ ls
initrd.img-4.9.0-5-amd64  kernel  ramdisk.gz

I just had to try...

$ gunzip ramdisk.gz
gzip: ramdisk.gz: not in gzip format

Ol`well, it's ok to try things.

$ cat ramdisk.gz |  ( cpio -i ; gunzip | cpio -i )
3102 blocks
cpio: etc/console-setup/null: Cannot mknod: Operation not permitted
160946 blocks
$ ls
bin   etc   initrd.img-4.9.0-5-amd64  lib    ramdisk.gz  sbin     usr
conf  init  kernel                    lib64  run         scripts

That's it! wow ~ both awesome & as jaromil typed "elegance"!
Nothing left to do, but repack it all now...   fsmithred post #2 was the fix - no resume file in conf/conf.d.
I think I'll do this again, on the other installs - after successful repacking of course

Oh, fsmithred - Did the info answer post #12 questions? If not let me know - I'll find `em.
Shoot, long post - I'm done for this nite!
asta ~~

This is moving off topic now (?) and really has little to do with derivatives or MiyoXtra,
I suppose a new topic in "Other Issues" or "DIY", might be best...?
Documentation? I donno...somewhere!

I finally did that, and rebooted with the 4.9.0-5-amd64, which still showed the symbols - but, with NO delay!
So I'll mark this solved, although I'm still continuing trying to unpack the initrd.

Yes, those commands complain...

:~$ xzcat initrd.img | cpio -d -i -m
xzcat: initrd.img: No such file or directory
cpio: premature end of archive

and with the help of that 'file' command...

:~$ file initrd.img
	initrd.img: ASCII cpio archive (SVR4 with no CRC)

Frustrating to me, it didn't work on miyoXtra, as quick as it did on refracta9. That's why I thought
maybe you had a 'helping' package installed on your system - that is not on miyo's.??
Well, I have more research to search.
Thanks again fsmithred..

This looks in /boot dir?

:~/extracted$ zcat /initrd.img | cpio -i

gzip: /initrd.img: not in gzip format
cpio: premature end of archive

:~/extracted$ zcat /boot/initrd.img-4.9.0-5-amd64 | cpio -i

gzip: /boot/initrd.img-4.9.0-5-amd64: not in gzip format
cpio: premature end of archive

I did run bleachbit couple times, to reduce snapshot size.

:~/extracted$ zcat /boot/initrd.img-4.19.0-2-amd64 | cpio -i

gzip: /boot/initrd.img-4.19.0-2-amd64: not in gzip format
cpio: premature end of archive

I'm gonna reinstall on other partition, and do all this before install - than after -
and before upgrading the image, then after (if thats possible?).

Then redo again with your edit to /usr/bin/refractasnapshot.

What`ta ya think? 

That answers one of my questions, but the suspend/resume device uuid shows it might?
anyway...
Did a image upgrade early in the wee hours, from - 4.9.0-5-amd64, to 4.19.0-2-amd64 and
all delays and waiting has gone.
Will boot back to 4.9 and see if continues there.

Yep ~ still there.
Well, I'd say - someone please delete this post! 

Howdy fsmithred..
I'm in a fresh install & now tweaking refractasnapshot.config.
Line # 55-57

# Set to yes to create boot files for uefi.

make_efi="yes"

Is this creating both 'uefi' and 'efi', boot files?
Well, I hope your giggling - at least... I just know its 2 boot methods - no more!
thx..

line 73:

# rsync -av / myfs/ ${rsync_option1} ${rsync_option12} ${rsync_option3} \

might miss line 77

rsync_option2=" --delete-excluded"

I'll stop now..