You are not logged in.
Pages: 1
Hello dears, I have one doubt I uses some OS without System D, but I`m stuck in start mongoDB in Devuan.
How Can I do that.
If you use sysv and there is maybe not init-file, you can try this one:
https://github.com/mongodb/mongo/blob/m … ian/init.d
What do other Devuan users use for virus and malware detection?
maldet (Linux Malware Detect) and this will use also clamav together.
Hello,
I'm new to this forum, I've been using Devuan ceres with KDE for about 2 years.
Every day it becomes more and more difficult to avoid systemd and its its infections.
Yes, that's the price for using unstable as well. Time will come and only FreeBSD will be a solution, I think.
grep cgroup /proc/mounts
What does this show? I am using lxd, but it is a little bit tricky to compile.
You may want to consider another test before going any further:
Debian 11 (sysvinit)+ext4 + LUKS encryption
This is a little bit different in the setup, but its working fine, when I choose a different
partition for saving the snapshots of the system-drive. So i put a second, luks-encrypted
Disk (partition) in the system, and I could save the snapshots (rsync) there.
I dont know, if its "normal", because i never use a system-drive as ext4. The failure in
btrfs is, that the subvolume "@" is not found on a luks-encrypted drive, ext4 uses rsync
for snapshots.
Again, I have testet all five version with sysvinit, clean, small install (no clones).
Only the one with ext4 uses rsync, the others btrfs.
Debian 11 (sysvinit) + btrfs + LUKS encryption
Devuan 4 (sysvinit) + btrfs + LUKS encryption
not working.
Debian 11 (systemd) + btrfs + LUKS encryption. <- not tested
Debian 11 (sysvinit) + btrfs + no encryption
Debian 11 (sysvinit) + ext4 + LUKS
Devuan 4 (sysvinit) + btrfs + no encryption
are working fine.
Running Timeshift v20.11.1
Hi,
First
Debian 11+btrfs + LUKS encryption
Does not work.
Debian 11+btrfs + no encryption
Is working fine (sysvinit)
# uname -a
Linux debian 5.10.0-20-amd64 #1 SMP Debian 5.10.158-2 (2022-12-13) x86_64 GNU/Linux
Devuan Chimaera+btrfs + no encryption
Is working fine (sysv)Good to know.
Seems that timeshift may be be in the clear.
Timeshift is maybe not able to detect a luks partition correctly. Because
it finds this not in /dev/mapper/crypt, it uses /dev/dm-0 - thats not the way, it should.
Now you have to be able to rule out something going haywire when btrfs is used with encryption other than LUKS.
It would have to be a widely used and tested encyption package, nothing esoteric.Fo that, the next test would be to try Devuan Chimaera+btrfs + some other encryption.
I am trusting LUKS. If I would trust my internall ssd-encryption, there is no need
for a luks-partition, but my encryption should not be with some closed-source crucial-encryption thing.
So, what would be your idea for a well known, tested and stable encryption here? I do not know.
My next try is, to check void Linux. It is also without systemd and there it should run (without lvm). This is only to
produce some logfiles, and how timeshift/luks etc. is working there. Maybe not today.
tom
Hi,
Devian Chimaera+btrfs + LUKS encryption
Does not work.
Devuan Chimaera+btrfs + no encryption
Is working fine (sysv)
Only as an interim result.
Today i got an answer of a Void Linux-User:
When I had only the luks + btrfs partition, the btrfs snapshots in timeshift worked very well.
For now I use only rsync method, because btrfs under luks and lvm is not visible in timeshift
But I will not check this all with/without LVM, too.
To be able to catch Debian developer's eyes (and maybe their interest in the problem) you'd have to be able to report that timeshift+btrfs+LUKS works with Debian Bullseye+systemd but not with Debian Bullseye+sysvinit.
Since Debian is supposed to be able to work with both sysvinit and systemd, you might be successful.
But it seems that getting the developers to actually look into a problem related to/involving sysvinit is not a given.
Thanks for this.
Yes, i think about starting a small test-system with Debian GNU, luks and btrfs to produce some good logfiles and
put this to debian-bugs. There only two, small outstanding bugs for timeshift there, so maybe this could work.
Check this on sunday and put this in bugs-debian, we will see, what happens next. I'll report here.
tom
Hi,
I have the persistent feeling that this may be related to the fact that you are running Ceres, which (by definition/design) is unstable and prone to this sort of problem. ie: it has quite a bit of loose ends.
I am using first debian, then devuan unstable for a long time with not that much bad experiences.
You may want to consider setting up a Chimaera system with a btrfs/LUKS just to rule that out.
Really good point. So i did.
[06:46:17] D: Vertrieb: devuan "4"
[06:46:17] Vertrieb: devuan "4"
[06:46:17] D: DIST_ID: devuan
[06:46:17] DIST_ID: devuan
...
[06:46:18] detect_system_devices()
[06:46:18] D: / wurde dem Gerät zugeordnet: /dev/dm-0, UUID=
[06:46:18] / wurde dem Gerät zugeordnet: /dev/dm-0, UUID=
[06:46:18] D: /boot wurde dem Gerät zugeordnet: /dev/sda1, UUID=0a8d3a38-9894-4600-8e94-8680f3f1df36
[06:46:18] /boot wurde dem Gerät zugeordnet: /dev/sda1, UUID=0a8d3a38-9894-4600-8e94-8680f3f1df36
[06:46:18] D: Searching subvolume for system at path: /
[06:46:18] Searching subvolume for system at path: /
[06:46:18] D: Found subvolume: @, on device: /dev/dm-0
[06:46:18] Found subvolume: @, on device: /dev/dm-0
...
[06:46:22] btrfs_mode=true
[06:46:22] D: Ausgewähltes Schnappschussgerät ist kein Systemlaufwerk
[06:46:22] Ausgewähltes Schnappschussgerät ist kein Systemlaufwerk
[06:46:22] D: Schnappschussgerät: '/dev/sda'
[06:46:22] Schnappschussgerät: '/dev/sda'
[06:46:22] D: Schnappschussort:
[06:46:22] Schnappschussort:
[06:46:22] D: Ausgewähltes Schnappschussgerät ist kein Systemlaufwerk
[06:46:22] Ausgewähltes Schnappschussgerät ist kein Systemlaufwerk
[06:46:22] D: Bitte BTRFS-Systemlaufwerk mit Wurzelunterlaufwerk (@) auswählen
[06:46:22] Bitte BTRFS-Systemlaufwerk mit Wurzelunterlaufwerk (@) auswählen
[06:46:22] D: Status: NO_BTRFS_SYSTEM
...
[06:46:22] btrfs_mode=true
[06:46:22] D: Ausgewähltes Schnappschussgerät ist kein Systemlaufwerk
[06:46:22] Ausgewähltes Schnappschussgerät ist kein Systemlaufwerk
[06:46:22] D: Schnappschussgerät: '/dev/dm-0'
[06:46:22] Schnappschussgerät: '/dev/dm-0'
[06:46:22] D: Schnappschussort:
[06:46:22] Schnappschussort:
[06:46:22] D: Ausgewähltes Schnappschussgerät ist kein Systemlaufwerk
[06:46:22] Ausgewähltes Schnappschussgerät ist kein Systemlaufwerk
[06:46:22] D: Bitte BTRFS-Systemlaufwerk mit Wurzelunterlaufwerk (@) auswählen
[06:46:22] Bitte BTRFS-Systemlaufwerk mit Wurzelunterlaufwerk (@) auswählen
[06:46:22] D: Status: NO_BTRFS_SYSTEM
# uname -a
Linux devuan 5.10.0-20-amd64 #1 SMP Debian 5.10.158-2 (2022-12-13) x86_64 GNU/Linux
# btrfs subvolume list /
ID 256 gen 9331 top level 5 path @
Running Timeshift v20.11.1
Thanks for your time.
Thanks for your answer!
~$
Sorry. No plans to close this repo. There's already a message redirecting to the Linux Mint fork. The version of Timeshift in this repo will continue to be available for those who need it.
So, if the original version works, you may want to stick with it for the time being.
If not, maybe contacting teejee2008 to ask about this would get you an answer to the problem.
It seems that he is open to seeing about bug fixes and minor changes.
Downloaded the Version of backports, like you described, doesnt run on my system.
Then, i compiled the archived version without any luck, same result:
$ sudo timeshift-gtk --debug
D: Vertrieb: devuan "5"
D: DIST_ID: devuan
...
D: Searching subvolume for system at path: /
D: Found subvolume: @, on device: /dev/dm-0
D: Found subvolume: @home, on device: /dev/dm-0
D: Found subvolume: @daten, on device: /dev/dm-0
D: Found subvolume: @Virtual, on device: /dev/dm-0
...
** (timeshift-gtk:9068): CRITICAL **: 02:53:38.007: tee_jee_file_system_dir_exists: assertion 'dir_path != NULL' failed
D: Ausgewähltes Schnappschussgerät ist kein Systemlaufwerk
D: Schnappschussgerät: '/dev/dm-0'
D: Schnappschussort:
D: Ausgewähltes Schnappschussgerät ist kein Systemlaufwerk
D: Bitte BTRFS-Systemlaufwerk mit Wurzelunterlaufwerk (@) auswählen
D: Status: NO_BTRFS_SYSTEM
too late for more ideas now, i will try more later.
Trying to get "timeshift" working on my devuan GNU ceres. But only get this errror:
~# timeshift --check
E: System disk not found!
Also:
https://github.com/teejee2008/timeshift/issues/862
btrfs partition in LUKS device mapper not recognized
4L3XK commented Feb 2, 2022 •
It seems timeshift need systemd to properly recognize and process a btrfs volume in a LUKS partition.
Booting the system with systemd as init made the btrfs partition available and now snapshotting is working nicely.
The system in use in this issue is MX Linux which uses sysvinit as standard init, hence the problem.
Any advice about this?
Maybe using a (really) old version of timeshift? Or compile this by myself?
Thanks.
Ok, it is now up and running.
I did not put the backports in my sources.list, so i got some older packages for building.
Thanks.
I have some of these up and running with debian and LXD (installed by snap)
and want to migrate them to devuan.
PlanB is to use voidlinux, they have no systemd and lxd in their packages.
I am not familiar with compiling software on devuan, so i ran in a lot of trouble...
I would like to have LXD running on devuan, but i did not find the right manual for compiling
or get any deb-packages.
Should be later running on raspberry4 (8G). I do not want to use this snap-crap with debian anymore
on my little server :)
Any hints are welcome, thx.
Pages: 1