So that went off like a lead balloon, just can't get a working iso trying to use efi as default on a machine that's running BIOS.

Ran a new one finally with grub-pc for legacy/BIOS systems and it works great, tested multiple times for proper install and it's working nicely.

As I said, I don't have an EFI machine, but I imagine you can boot this up into a live session, and replace grub-pc with grub-efi-amd64 and should be able to install into an EFI system and use grub, but I have no way of testing, would be awesome if someone could down the iso and test that, I got beer and barbecue with your name on it if you do!

Will be uploading here shortly as soon as I write some new notes in the readme.txt.

Issues all sorted, I think the only thing I have left to do is add some custom excludes to snapshot and make sure installer has a couple specific configs, then i'm ready to squash the first iso of Vuu-do 2 series.

I've got it down to 2.39 gigs on disk, which should be close to 2.1-2.2 actual...really trying to hit that under-700mb mark. Which is crazy to me, the old mini's I did were half that size, linux sure has....umm...grown since I last made myself a system with it.

But i'm happy, it's still wonderfully faster than my Mate installs, not as fast as the old ones, but nice. I think if Dan is still lurking around here he'll be like "Nice work Grasshopper" lol!

Hah! Uninstalled all the Pipewire stuff and ALSA started working correctly! Happy about that.

Sad that they apparently got rid of the equalizer function in ALSA, but I guess most music players that would get installed have one onboard anyway. So it was likely redundant anyway.

Now if I can just get rid of the "auto-removeable" nonsense that Synaptic is doing....

That and those weird visual artifacts I mentioned, if I can fix those two things i'll be in high cotton.

Yep, like Steve said, I have had pretty good luck finding older ram sticks on ebay.

One more thing just struck me, I was never able to get the original Vuu-do to hibernate, I did get suspend working when you close the lid on a laptop by adding an  /etc/acpi/events entry connecting to a small script that invokes obsession-exit -s.

Since you mentioned hibernation requires it knowing the UUID of the swap partition it's easy enough for me to do on my own machine, but is there a way to do that generic-ly during install?

And I just gotta say, great googly-moo, the stupid policy kit takes 75-100 mb of ram while it's running, what the actual? Is that really necessary?

#linuxatemyram

Yep, that's the method I mentioned at the link Rolfie posted, works great!

In addition, despite that, synaptic and other admin stuff would still not start from menu, turns out the policy kit was not starting up at boot, even though there's an entry for it in /etc/xdg/autostart, I had to add a line to start it in /home/vuudo/.config/openbox/autostart, after that everything started working fine, almost....

But my extensions for root edit/access would still not work using pkexec instead of gksu.

So I found a little code online, modded it some, and made a little script I called gksu.sh and dropped it in the $PATH, all it does when you call it is convert the gksu.sh command to a full pkexec command and then executes pkexec and the action you asked for. Keeps me from having to add a bunch of code into the .desktop exec command lines.

Working soooo smooth now, and so much faster and lighter weight than MATE, I am literally almost done building Vuu-do 2, really the only issues I have left are these:

1. Getting a bunch of video artifacts on startup, logout, and shutdown, weird stuff, the Devuan-mate-mini does it too.  My original install of Daedalus a year ago did it too at first, then for some reason it stopped doing it all on it's own, wonder what that's about?

2. Totally personal to my machine i'm sure, but whenever I boot any version of Daedalus, it hangs up right at first when you boot for a minute or two, then puts out a message "Gave up on waiting for a suspend/resume device". Not sure what it's looking for, any way to bypass that behavior on my machine?

3. Alsa doesn't seem to want to start at all, so volumeicon isn't working properly and cannot fire up alsamixer or equalizer. I pulled Pulse out (YAY!) and it installed pipewire instead, pretty stoked about dumping pulse, but have no experience with Pipewire so don't know what to expect.

4. I started this from a clean install of Devuan-mate-mini, loaded openbox stuff and got a good working environment, logged into openbox session, uninstalled all the MATE stuff in Synaptic, but now Synaptic thinks that a whole lotta important stuff is now "auto removable". We're talking stuff that would destroy the whole system if I auto-removed it, the entirety of Xorg, most prgrams and system libraries, all of gstreamer, it's bizarre, like 60-70 of the most important packages in the system. What the heck?

Thanks rolfie, the workaround posted at the link you gave me worked fine and now it's behaving as i'm used to.

I don't like either, but I seem to be an old man yelling at clouds the last couple days anyway.

But hey, I learned new things so it's a good day. Really appreciate the forum members here helping me out.

Wow @rolfie, thanks for the link big-time, sure enough that new install is doing that, su - has all access. That makes me happy and sad and confused all at the same time.

Happy because I didn't do badly, my goal with the Mate-mini was to make a 100% stock Devuan with no changes or additions by me, pure Devuan as-delivered. So I guess I did that, and if that's the way they want it, so be it. Relieved.

Confused because if this goes all the way back to Beowulf, why did it not do it on my other Devuan installs from a year ago? And also, if someone would humor an out-of-touch old curmudgeon:

Why was this necessary?
Where is it? Hard-coded into Bash?

Wow, I hadn't heard about that, will give it a check.

That's what I do, but as Steve_V rightly said if you have an active connection apt can do it for you.

There is a way to have apt resolve depends using local packages, and that's if you have set up an offline repo of your own.

I did this years ago when gnome 2 was transitioning to gawdawful 3, I downed the entire repo including all gnome 2 packages and set myself up an offline repo in case I ever wanted more programs in the gnome 2 system I was using at the time.