You are not logged in.
there must be a matching Ubuntu version for any given Devuan distribution version, that has the crucial libraries should be in the same place, right? If so, a Launchpad PPA with custom packages based on the Devuan packaging metadata (the `debian` subdir) ought not be too risky?
Yes, the packaging is the same, so libraries all go to the same places in debian, devuan and ubuntu. But ubuntu is based on debian sid, not debian testing after freeze, so library versions might not correspond between comparable releases of ubuntu and either debian or devuan. YMMV.
Another option is to start with devuan and kalify it with this script.
https://github.com/LionSec/katoolin
I tried it in January and it works. I think the script gives you choices of different groups of packages to install, and I think I either chose not to install all of them or could not install some of them. There's a list of missing packages in my work directory, but I don't recall why they are missing.
Thanks. Welcome to Devuan.
Edit: (Sarcastic joke removed)
When I say testing, I mean whichever suite is in testing at the moment. I absolutely DO NOT mean that 'testing' should appear in your sources.
USE CODENAMES!
Whether or not you use chimaera or ceres or both is not my decision. If you're ok with unexpected breakage, then go for it.
Ceres tracks Sid. It should be no more than a few hours behind. So if you run pure ceres, you are likely to get un-devuanized versions of packages that we fork. (recent example: dbus)
But this can happen in devuan testing, too. Right now, ceres and chimaera are in pretty good shape, because someone got on the packaging early, even before beowulf was released. So you can probably get away with any combination of chimaera and/or ceres. Rest assured that something will eventually break and then eventually get fixed. That's likely to happen more than once.
I didn't think about that with Devuan. Does this mean with Devuan testing we suffer twice the freeze delay? The first one when debian testing freeze, then the second one when Devuan freezes its testing?
Devuan doesn't have a freeze. We bust ass up to the last second to put forked packages into the repo before release. OK, slight exaggeration there. The time between "no new packages go into repo" and actual release is about a week, maybe two. And the time between debian testing freeze and devuan release is long. (slight understatement there)
I don't know if it's still common, but one thing people used to do with debian is run a mixed testing/unstable system. That's basically a testing system with unstable repo enabled but pinned to a lower priority. That way, you can pull selected packages from unstable to get fixes faster while at the same time avoiding pulling packages from unstable that will break stuff.
Such an arrangement will work in devuan only until debian testing goes stable, and then we're behind by one release. If you switch to the next devuan testing at that time, the forked packages won't be ready for that release. So when bullseye goes stable, I guess you would either stick with chimaera or go with pure ceres. I'm not sure which would be the least painful.
always from the Debian/Devuan installer when you create an encrypted partition you have to use LVM to write on it...
It's possible to create encrypted partitions without lvm using debian installer. It goes like this - http://distro.ibiblio.org/refracta/misc … rypt-4.ogv
I'm only a little bit surprised you don't know about this. It's not obvious or intuitive. The 4 in the filename is the number of times it took me to do it right, and I've done it many times before.
If you want more than one partition encrypted this way, you'll end up with a password (or keyfile) for each.
I think the newer versions will work on wheezy. If not, there are older versions here: https://sourceforge.net/projects/refracta/files/tools/
I think the installer will work on all releases. Newer versions of refractasnapshot should work on wheezy, but they might not work on jessie. There was a function to edit init to work around a change in util-linux, and that function has been removed. That should not affect wheezy.
If this is the problem as what you linked to, then Devuan is at fault.
That would be an absurd condition halting the boot process just because the os is unhappy about the network status.
Nope. Not our fault. We get it like that from Debian, and it's way down on our list of priorities for a couple reasons. It doesn't require systemd, and there are some easy fixes.
Are you sure it's not this issue?
https://dev1galaxy.org/viewtopic.php?id=1688
Jessie has reached end of life. Let her go.
If you're running chimaera, then you are already pulling from bullseye. If you add a bullseye line to sources.list you will be able to bypass the filter that keeps you from installing banned packages and you can screw up your system that way. Don't do it.
There's no kodi in chimaera because there's no kodi in bullseye. The version of kodi in ceres (sid) should migrate into chimaera after a couple weeks, I think. That's the normal procedure. If it doesn't, then it means there's a problem either with the package or the maintainer.
You can pull the packages you need from ceres and see if it works, or you can wait until it shows up in chimaera.
Edit: Or maybe not. (I just read the bug report.)
Here's the SDK page on the new git:
https://git.devuan.org/devuan-sdk
Here's a discussion about using live-sdk. I haven't looked at it in a long time, and there may have been some changes that were not documented. If you clone the live-sdk repo and use one of the existing blends, it should work. This is how the official devuan live isos are made.
https://dev1galaxy.org/viewtopic.php?id=551
The easiest way to make an installable live-iso is to install a system the way you want it. You can do it on hardware or in a VM. Add refractainstaller and refractasnapshot. Run refractasnapshot, and it will make the iso.
https://refracta.org/docs/readme.refractasnapshot.txt
Using the testing suite in a business is probably not a good idea. There may be times when the system is temporarily broken while you wait for new packages to arrive in the repo. If you need a kernel newer than 4.19 you can get 5.x from beowulf-backports.
Depends: libpam-systemd". Xfce's focus started following the mouse cursor. I had to change it to click manually.
Forgot to comment on this. Install libpam-elogind to satisfy the dependency on libpam-systemd. network-manager works in beowulf.
I was never able to list and mount lvm with gui in debian. Plain encrypted partitions, yes, but not lvm. Find out how those others do it, and maybe it can be replicated. Maybe something is missing.
If you want user to be able to mount a logical volume that's part of an active volume group, you should be able to add a line to fstab for that lv. Something like:
/dev/mapper/vg0-mylv /some/mountpoint ext4 defaults,noauto,user 0 0Then the user can either mount it in terminal, or you could put the mount and unmount commands into panel buttons or a menu item.
In xfce, there's a setting to allow removable drives to show up on the desktop. It used to be that the setting affected only removable drives, but it no longer does that. I think the change occurred with xfce 4.12, but I'm not certain.
Internal drives will now show up along with the removable drives, unless they are listed in fstab. (I listed a few of mine and gave them 'none' for a mount point just to get them off the desktop.) It's the same in beowulf (3.0).
Start it from a terminal and there may be some error messages.
Maybe gvfs-backends is needed. It doesn't get installed with gvfs.
One way to have that volume auto-mount is to add it to /etc/fstab.
I think you can ignore those warnings.
https://unix.stackexchange.com/question … bytes-read
I'm not surprised that gnome won't let you change an icon. The gnome devs are in love with the idea of brand identity. They don't want you to change the way the desktop looks.
The problem is that Devuan boots just fine, but I can't mount any LVMs inside my VG that Devuan is booting from. I tried:
$ sudo udisksctl unlock -b /dev/sda2 Passphrase: Error unlocking /dev/sda2: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/sda2: Failed to activate device: File exists $ sudo udisksctl mount -b /dev/mapper/vg1-storage Error looking up object for device /dev/mapper/vg1-storage $ sudo vgscan | grep vg1 Found volume group "vg1" using metadata type lvm2 $ sudo lvscan | grep storage ACTIVE '/dev/vg1/storage' [xxx GiB] inheritEven Thunar and pcmanfm is failing to do so, while pcmanfm just repeats the message on terminal "Error unlocking /dev/sda2: Failed to activate device: File exists" and Thunar silently fails. Tried so many config changes around the web, but didn't help.
If the system is running on a logical volume inside the luks container, then the luks container is already open and the volume group is already active. You should be able to mount whatever /dev/mapper/something that needs to be mounted. Or maybe mount /dev/vg1/storage.
Or maybe I'm missing something because I don't know udiskctl. I always use cryptsetup, vgchange and mount to manually mount encrypted lvm.
Onward, if I install Gnome3, I assume the udevd worker problem may arise.
Maybe, but that's not the case here. It boots fine with gnome and 5.6 bpo kernel. Here's the package list from that system.
http://distro.ibiblio.org/refracta/misc/pkglist_gnome
Also, desktop-live installed and with 5.6 kernel added works fine.
I am going through boot messages while udevd got stuck. It says "1 urandom warning(s) missed due to ratelimiting". Is this related to the entropy bug too? I already installed haveged.
I've seen that warning on systems that boot. I don't think it's a problem.
I added bluez and then blueman, rebooting after each. Still can't reproduce the problem. You may need to install things one at a time and see which package breaks it.
...nothing much...
'apt install' appears on 47 lines. I realize some of those are repeated because they did not run the first time, but there was still a lot added.
You added ubuntu repository keys, so I have to wonder what was installed from ubuntu that might cause problems.
Looks like you installed the 5.7 kernel from unstable.
And you purged and reinstalled other stuff.
I can't tell what went wrong or when it happened.
Tell me exactly what you installed and how you installed it. Reinstalling the kernel and xorg did not break anything here.
fsmithred wrote:Link no longer working - 404
Thanks! Here's the new link:
https://git.devuan.org/devuan/documenta … aintainers
(Fixed in first post, too.)
The oblx5.6 iso excludes Recommends from installing and there are few or no metapackages, no display manager, no policykit, no elogind or libpam-elogind, just has libelogind0.
Here's a full list of config files that were changed in the oblx5.6 iso. The only thing in this list that was changed to fix a boot delay was lvm.conf, and that was changed in the desktop-live isos, too.
# debsums -ca
/usr/lib/os-release
/etc/initramfs-tools/initramfs.conf
/etc/pam.d/login
/usr/share/lxdm/themes/Industrial/nobody.png
/etc/lxdm/lxdm.conf
/etc/pmount.allow
/etc/sysctl.conf
/usr/bin/refractainstaller-yad
/etc/xdg/user-dirs.defaultsMaybe an answer in these lists, but for sure a lot of noise:
Packages in oblx5.6 that are not in the desktop-live:
http://distro.ibiblio.org/refracta/misc … p-live.txt
Packages in desktop-live that are not in oblx5.6:
http://distro.ibiblio.org/refracta/misc … blx5.6.txt