You are not logged in.
Curious about this myself. 32 bit still actually runs faster on older low-spec 64 bit machines, running it on this one.
I'd probably make 32 bit versions of anything I do if I knew for sure it would be supported for at least a few more years. There's a mega-ton of used laptops in pawnshops everywhere right now for dirt cheap that would run good on 32 bit Devuan.
Also issues relating to hibernation and sleep that seem to stem from this conflict, multiple reports including one here now.
Looks like Upower has been devuan-ified as the package in the repo has devuan in the package name, was there some systemd that needed to go bye-bye?
Known bug with older versions of Mate and upower, link: https://bugs.archlinux.org/task/40031
Maybe need updated upower in jessie for power manager to work right.
mate-about open a window like this: http://hezeh.org/img/mate-1.14.png
Did you get the mate 1.14 from ascii or backports? Still on 1.8 in jessie...
What is "mate-bout"? I can't find it neither as a package nor as a file in any package (I used debian package search on contents - this doesn't exist for devuan yet afaik).
typo, Antofox meant to say :
mate-aboutThis has been this way for months, and after re-visiting several times I am still unable to figure out a fix. I know this works in Debian as I have had an almost identical install with mate that worked properly.
Problem is when using Mate desktop and Mate-power-manager, it is supposed to use icons for the tray/notification area provided by the power manager package and located in /usr/share/mate-power-manager/icons/hicolor/*, these icons change according to power status, i.e. battery full, battery low, etc.
I have never gotten this to work in Devuan mate, it acts as though it can't find the icons and is defaulting to using a GTK dialog warning icon (yellow triangle with exclamation point), it does this no matter what icon set you choose.
Have tried copying the proper icons into various icon directories in /usr/share/icons, but no luck with that either. Nor does updating icon cache seem to help.
The polling system is not working properly to begin with, that may be why it's showing the warning-dialog icon, it's not checking the battery or the charging system periodically like it's supposed to, and so not changing the icon and the tooltip info on current charge status.
Anyone else having this issue? Any ideas? Am I missing a package somewhere?
I played with this mini.iso file this morning. It is a netinstall which pulls in what it needs as it installs. I did the install, installed refractasnapshot, and the final refracta snapshot was 273mb in size. At install I only selected the ssh server and the standard system utilities to be installed. It worked fine though.
I now have my own personal install disk to build upon.
Too cool, I gotta try it. ![]()
Possibly in /usr/share/polkit-1/actions/org.freedesktop.consolekit.policy, change "auth_admin_keep" to "yes" where appropriate, not sure this is the best way or recommended way but I imagine it will work:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE policyconfig PUBLIC
"-//freedesktop//DTD PolicyKit Policy Configuration 1.0//EN"
"http://www.freedesktop.org/standards/PolicyKit/1.0/policyconfig.dtd">
<!--
Policy definitions for ConsoleKit
-->
<policyconfig>
<action id="org.freedesktop.consolekit.system.stop">
<description>Stop the system</description>
<message>System policy prevents stopping the system</message>
<defaults>
<allow_inactive>no</allow_inactive>
<allow_active>yes</allow_active>
</defaults>
</action>
<action id="org.freedesktop.consolekit.system.stop-multiple-users">
<description>Stop the system when multiple users are logged in</description>
<message>System policy prevents stopping the system when other users are logged in</message>
<defaults>
<allow_inactive>no</allow_inactive>
<allow_active>auth_admin_keep</allow_active>
</defaults>
</action>
<action id="org.freedesktop.consolekit.system.restart">
<description>Restart the system</description>
<message>System policy prevents restarting the system</message>
<defaults>
<allow_inactive>no</allow_inactive>
<allow_active>yes</allow_active>
</defaults>
</action>
<action id="org.freedesktop.consolekit.system.restart-multiple-users">
<description>Restart the system when multiple users are logged in</description>
<message>System policy prevents restarting the system when other users are logged in</message>
<defaults>
<allow_inactive>no</allow_inactive>
<allow_active>auth_admin_keep</allow_active>
</defaults>
</action>
</policyconfig>Fixed!
Great work!! Thank you!
Hey folks, having a minor issue with one of my projects, if anybody has a sec to take a quick peek at the picture i took and maybe point me in the right direction it would be greatly appreciated!
Shutdown usually is lightning fast, but started getting this hitch of a few seconds in the process and an error message, it stops for a few seconds right after "asking all remaining processes to terminate....done", then spits out that tree and the fail message and then goes ahead and shuts down :
EDIT: Solved this but it's gonna take some explaining, I only type with two fingers so it's very slow, will get to this soon.;)

That being said, we'll look into adding a simple formatting mod.
Best policy IMO.
It's not offered as an option in this BB template? Small toolbar for the bottom that offers to tag img, url, code, quote etc.?
I just tried a 'live' Devuan RC 1.0.0 on another of my laptops, & it couldn't find a network either!
(So, maybe, it's down to Devuan itself.)
Package list on the RC doesn't show any firmware at all, so that may be why, FSR said I guess that the .debs for some stuff were on there? Guess I need to download it finally, lol, bandwidth is back to squat here today.
In Refracta, all I do is install it & wifi then works, but not in Crowz. (Running live.)
I have since tried installing Crowz, (todays JVM, downloaded), & the wifi didn't come up, tried again by using dpkg, rebooted, but still no wifi.
Having rebooted after installing the firmware should have produced a result, but it didn't, no connections were available.Anyway, I've now put GreenJeans Mate on one SDHC card, & MIYO on another, & they work in my netbook.
That's strange if this is the same machine you're talking about, the mate iso's don't have firmware-atheros or even the linux-free packages installed unless you added them.
Just checked with a live Refracta & my ath9k driver comes in firmware-atheros.
So just thinking out loud here, but a solution when using the Refracta installer/snapshot for livecd's, to keep from installing a bunch of extra firmware, is to just put the .debs for the firmware packages in /var/cache/apt/archives, that way the install can be blob-free if you want, or you can install needed firmware without having to have an internet connection first? The cached packages can even be installed with Synaptic, just fire it up normally and select them for install.
I've installed and removed packages during a livecd session with Devuan and Refracta, modded and replaced files too, so couldn't you even install the needed firmware while still in-session, and delete the unneeded .debs, and have just what you want installed?
Just checked with a live Refracta & my ath9k driver comes in firmware-atheros.
Thought maybe so, thanks for info, need to add that probably for some local installs when I do them.
@Zephyr: Tried both JWM and OB last night and they are both fun! I like the crowz graphics and colors, livecd booted quite a bit faster than mine do on my machine, the boot message was a nice touch
, gonna give them a run today again and check out netsurf browser a little more among other things.
Again I gotta say, I learn more from 5 minutes of running and looking at someone else's work, than I do from 5 hours of agonizing over my own filesystem trying to figure out how to make it run better and faster.
Test-driving iso's, much like a 5:30 beer, is always a good decision.
@greenjeans: the Oxy2-ZEN are a great looking set of icons. First time seeing them anywhere!
zephyr
Blast from the past, old gnome 2, take a look in the icons, the main menu icon is named "Mandriva.png", that ought to give you an idea of how old ![]()
greenjeans wrote:Perhaps we mini guys need to figure out a list of most commonly needed wi-fi and other firmware?
I'm pretty sure that's going to be handled in the Devuan isos in the next round. So just sit back and let the Devuan team sort it for you.
Are you sure? All I see in the new RC is firmware-linux-free, the original beta I installed from at least had firmware-realtek.
I don't understand the process like I should, just asking questions here.
I can understand if it's considered non-free software and so isn't included in Devuan's isos, but I was speaking to Zephyr more about what we as people who are working on derivatives might want to do as we have more freedom, for my part I want to include at least the most common things needed for most users to connect to the internet. Realtek and Ralink firmware alone probably covers a million machines if not more.
This is what hooked me on crunchbang back a few years ago, it worked out of the box on every machine I tried it on. Not so with Debian or Mint.
For info, the following is how it is seen on my Debian based AntiX system.
Network: Card-1: Qualcomm Atheros AR9485 Wireless Network Adapter driver: ath9k
IF: wlan0 state: up mac: <filter>
Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
IF: eth0 state: down mac: <filter>Maybe driver: ath9k is missing(?)
(I'm off for my dinner now.
)
firmware-atheros maybe? Just looked and I don't have it on the 32 mate i'm working on, guessing I don't have it on the other partitions either, is that a pretty common chipset?
If you do try it and it works, could you let me know?
Default Devuan that I started with months ago didn't have firmware-ralink package that I needed for both my laptops wi-fi. I added it to all my iso's as it's a very common wireless chipset, almost all the HP laptops i've seen for the last few years need it.
Got me to thinking about other firmware, and the necessity of some of it in mini iso's specifically. Perhaps we mini guys need to figure out a list of most commonly needed wi-fi and other firmware? Like I see bluez firmware in the repo for bluetooth devices, I hadn't even thought about bluetooth needing firmware, how common are bluetooth devices used with computers these days? I don't use any so I have no idea.
@greenjeans: Have JWM up if you are still interested in taking a spin!
https://sourceforge.net/projects/crowz/Downloading your new release of Vuudo! Like the appearance of it! : )
http://www.mrgreenjeans.net/linux/vuudo … 2_1909.isocheers
zephyr
Downloading now, bandwidth is actually excellent today for some reason, so i'm hitting it hard right now!
Your screenshots look amazing, I think we have similar tastes in color schemes ![]()
WOW, that download is already done, now i'm grabbing the openbox version too and anything else that isn't nailed down, lol.
What you've done stands on its own and deserves it's own name (if you're so inclined). I'm flattered that you kept it associated with Miyo, but that wasn't necessary by any means as far as I'm concerned friend.
Well I wasn't thinking along those lines when I did it, but more and more I think I might want to, if you're sure you're okay with me using your work as a base? I didn't want to do something like that and call it my work when it's you and everybody else's and all i'm doing is some configging.
But I just like this so much, it's still sitting there unmodded on sda3 like I finished with it, keep thinking of adding programs or re-installing something else to work on but it's just so damn pretty sitting there humming along at low idle....lol, don't know if that makes any sense.
I'll do some new artwork in the same color schemes, but was wondering too if I could keep the Miyolinux window themes onboard just as they are?
Downloading as soon as I get some bandwidth here (slow infrastructure in my area). Looking forward to the promised JWM version as JWM has piqued my interest lately for some reason.
No, don't mess with them there. You can add to core_packages and base_packages in your config file, and you can remove the stuff you don't want by adding it to the purge_packages list, or replace the purge_packages list as I did below.
Ahh, well there's the rub seemingly for the basic iso i'm trying to make to start with, not using a blend file for it, just running the basic instructions.
So i'll need to make a custom blend for the cli-iso too if I want to adjust packages in/out. And a custom rm list for some things.
For custom configs and removal of extra locales and such, it would almost seem easier if a user could just mod bootstrap-devuan-amd64.tgz prior to feeding it into the build? Or the unpacked bootstrap folder itself.
So the idea is basically, that rootfs-overlay folder is sort of an etc/skel for the entire file system, yes? But only insofar as adding things, not replacing or overwriting things already in the folders/files?
That's a lot of good info, thanks for taking the time to post all that. ![]()
cp: cannot stat '/usr/share/live/build/bootloaders/isolinux/isolinux.bin': No such file or directory
Problem is that this file appears to be missing. It should be there if you installed live-build, along with some *.c32 files. Are they there? Is live-build really installed?
It worked, I tried to edit the above post and will try again here in a sec. Have some thoughts on first run.
Oh, and you're not getting senile. I added live-build to the list of requirements kinda late.
That's what got me, copy-pasta'ed your post a day or two ago in a text file and was working off those instructions.
Okay, ran a test making just the cli-iso as detailed in the tutorial, seems all is well as I now have an iso (haven't tested it yet).
But man, iso is 341 mb, does that sound right? CLI-only with just the few packages on there ought to be like 250 or less shouldn't it? At 348 it's 13 mb larger than the fully functional openbox mini I just made.
I looked at some of the scripts and it looks like it's using xz with the extra compression of -xbcj x86, am I wrong about that?
Some other reasons why it's big from the bootstrap folder:
Giant folder with much added stuff: /usr/share/vim/vim74 = 26 mb , same folder normally on my system = 7.4 kb
Ginormous added file : /usr/share/keyrings/debian-keyring.gpg = 50 mb , there is no such file on any of my installed systems, do I need a debian-keyring?
30 mb of doc files and 60 mb of translations, guess that's standard operating procedure for the distro, i'll just have to tweak when I make a blend.
All the apt lists in /var/lib/apt/lists that I usually don't include are another 36.5 mb.
/var/cache/debconf has a couple of *.dat-old files that were left in there, 2.3 mb for one of them, not needed.
git-core in /usr/lib, 14.7 mb, don't need this
SSH server, didn't need that.
Just my .02 worth.
DISCLAIMER: I could have done something wrong, I didn't start over from beginning, just added live-build dependency and went back into the live-sdk folder and ran the commands again:
zsh -f
source sdk
load devuan <arch> <blend_name>
build_iso_dist
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I will have more to say about core and base packages. Look in live-sdk/lib/libdevuanskd/config, but don't mess with them. What you see there is what gets added to the initial debootstrap install.
You know that saying that pretty much guarantees that i'm gonna mess with them right? ;-)
aaand there's what seems to be the debian-keyring....sssh server and client...and git-core
And this line I have a question about: vars+=(arch earch) , is "earch" a thing?