You are not logged in.
fsmithred wrote:OK, I read A.6 and if I read it again, I'm sure I'll get a headache.
I think we're screwed. As I see it, there should only be two options on this vote:
1. systemd only
2. some kind of support for other inits.Then if 2 wins, figure out the details.
Yea... Was wondering this exact thing when reading through the options. Lots of fragmented options for non-systemd.
If Debian goes full systemd, what will this mean for Devuan?
Surely that is the question...
OK, I read A.6 and if I read it again, I'm sure I'll get a headache.
I think we're screwed. As I see it, there should only be two options on this vote:
1. systemd only
2. some kind of support for other inits.Then if 2 wins, figure out the details.
Exactly. But this way they can make it come out any way they want :-/
Yes, I think we're screwed.
What happened to my comment? It was there a minute ago.
someday maybe theyll fix this forum.
in about two seconds, someones going to tell you that "there is no problem."
theyre right, of course. no problem, at all. ive seen the list-- and ill take it over this. AGAIN.
its about my "hate," of course.
thats what they told me last time. funny, thats what torvalds said, too. look it up, its pretty classic.
Simmer down, man! It's not all about you, y'know. I think you are overreacting just a tad. I agree with most of what you've been saying, but you seem to be seeing enemies where they're not.
You make a lot of good points. Is there any way for anything good not to get co-opted by the corporate borg? That's what i find myself wondering. ..
do we know the timeframe on this? when does it close?
I believe it's 20 days.
Just posted on Slashdot:
Debian Begins Vote on Supporting Non-Systemd Init Options
ToxicExMachina wrote:https://lists.debian.org/debian-devel-a … 00002.html
Options for voting are very interesting: according to description every option (except further discussion) is for SystemD.From mailing listt:
[ ] Choice 1: F: Focus on systemd
[ ] Choice 2: B: Systemd but we support exploring alternatives
[ ] Choice 3: A: Support for multiple init systems is Important
[ ] Choice 4: D: Support non-systemd systems, without blocking progress
[ ] Choice 5: H: Support portability, without blocking progress
[ ] Choice 6: E: Support for multiple init systems is Required
[ ] Choice 7: G: Support portability and multiple implementations
[ ] Choice 8: Further DiscussionDoublespeak at work. Here's what the options really are:
[ ] Choice 1: F: Systemd only
[ ] Choice 2: B: Systemd only
[ ] Choice 3: A: Systemd only
[ ] Choice 4: D: Systemd only
[ ] Choice 5: H: Systemd only
[ ] Choice 6: E: Multiple Init Systems
[ ] Choice 7: G: Something unrelated to dilute votes for 6
[ ] Choice 8: Do nothingThere are essentially two options here: Make systemd default, or support multiple init systems. Anything else is bullshit. How they managed to come up with 7 choices out of 2 is amusing.
It basically seems like what they did for the original systemd vote back in jessie, only 3 times worse. I.e., bullshit. Or if you want to be polite, 'disingenuous'.
https://lists.debian.org/debian-devel-a … 00002.html
Options for voting are very interesting: according to description every option (except further discussion) is for SystemD. There is also sjw-related stuff in description for some of options.
Another interesting fact: systemd-homed will be merged with SystemD code very soon. It looks like someone want to turn Debian into SystemD-exclusive for systemd-homed promotion.
This is getting to be very depressing. What is wrong with LP? Does he really have Linus-envy, and want to have his own Lennax? Why can't he just stop? I have a bad feeling about this...
I think it was in Ubuntu MATE that I saw a dialog, probably in MATE Tweak, to choose from a number of different look-and-feels. I much prefer the single menu instead of Applications-Places-System. Does Devuan MATE have an option to do so? I didn't see it in MATE Tweak.
Yes, you can remove all that from the panel, and add the menu of your choice. I'm not in MATE now, but if you right-click on the App/Place/Sys thing, you can delete it. Then right click on the panel and add the menu of your choice. Some people like the Brisk Menu (I don't). There's also a simple menu. Just poke around and see what you like.
No, this is not something you do from MATE Tweak.
Hexchat is good - relatively full-featured, but easy to use right away.
Just another data point: I installed using the ascii 2.1 iso, selected the openrc option, and it all worked fine.
I use Thunderbird, have been for years. It runs on everything. I typically have several OSes on my system, and all of them share a Thunderbird email database on my data partition, and they all share the Google calendar. I have years and years of old emails that once in a while it's good to be able to search through.
I've tried them all, and nothing beats TB for me. For me it's all about interoperability. No matter what OS I boot up, my mail/calendar presents as identical, and functions identically.
I installed from the new iso (netinst) in order to check out the openrc option. It installed without issue, and openrc is working fine!
If you spend enough time, you can figure out which exact versions of the 64-bit packages you need, so that you can "apt-get install thatpackagename=1.3.4" with exact version numbers. What happened was the i386 packages have a newer version released in the Devuan repos, before the amd64 packages. In a multiarch installation, it appears that all architectures must have the exact same version number for a named package. I ran into this issue on Ceres but maybe that conversation can guide you a little.
Yes, I had read that thread. I can't really seem to figure out what's going on. I'll just wait for the 64-bit packages to catch up to the 32-bit packages :-)
Um, we did that. It's in /etc/os-release. ID=debian magically makes third-party software work with devuan. I think there's another reason for it, but I don't remember what it is. What I don't get is why /etc/lsb-release doesn't override it like it used to.
In my poking around re: this issue, I got the impression that lsb_release has change a bit over the last few interations. Seems to be somewhat of a moving target.
I changed it to Devuan in my system, and haven't noticed any ill effects, but is something suddenly stops working, I'll know where to look. I really don't care what lsb_release reports :-)
Note that there is version competition between the i386 and amd64 for some packages.
In particular the util-linux group of packages have got version mismatch between these architectures (with i386 the newer). This results in a bit of a havoc if one attempts to install something (like wine32) that (indirectly) depends on one of those, as it essentially ends up wanting to replace almost everything.
It's something to careful with.
I will be grateful when things are rectified - I would like to install wine 32 in beowulf. I have one stinkin' program that I need to run daily, so I'm mostly stuck in ascii. Which is no hardship, to be honest :-)
I have been running a beowulf installation for some time, and I only just noticed that lsb_release -a reported 'Debian' as the 'Distributor ID'. The os-release file has Debian instead of Devuan as the ID, and that's what gets reported.
This is a very serious, show-stopper bug, and I trust that the entire Devuan Project will drop what they're doing and turn their attention 100% to this issue until it is fixed. ;-) ;-) ;-)
In my case system is /dev/sdb3 and target to chroot to is /dev/sdb6
root@blinc:~# mount /dev/sdb6 /mnt
root@blinc:~# mkdir -p /mnt/boot/efi
root@blinc:~# mount /dev/sdb3 /mnt/boot/efi
root@blinc:~# mount --bind /dev /mnt/dev
root@blinc:~# mount --bind /proc /mnt/proc
root@ginc:~# mount --bind /sys /mnt/sys
root@blinc:~# chroot /mnt
chroot: failed to run command ‘/bin/bash’: No such file or directoryNote: These are fresh unaltered Devuan installs.
Are you sure about your EFI partition? It's generally (always?) partition 1...
Not sure you need to mount the EFI partition, depending on what you're chrooting to do - I always mount it because I'm often reinstalling grub or something like that...
Somehow my usual chroot tricks dont work on Devuan.
I have two Devuan installations on the same disk.
One on /dev/sdb3 and another on /dev/sdb6I want to chroot devuan on /dev/sdb6 while I am in devuan on /dev/sdb3
While I am root user in Devuan on /dev/sdb3 I do.
mount /dev/sdb6 /sdb6
mount -t proc none /sbd6/proc
mount -t proc none /sdb6/proc
mount --rbind /sys /sdb6/sys
mount --rbind /dev /sdb6/dev
chroot /sdb6 /bin/bashI now get
chroot: failed to run command ‘/bin/bash’: No such file or directoryWhy doesnt this work in Devuan ?
It worked on Debian
I have never added '/bin/bash' to the chroot command - I just use chroot (location of mounted system), and have never had a problem.
My formula goes like this (system on sda5):
sudo mount /dev/sda5 /mnt
sudo mkdir -p /mnt/boot/efi
sudo mount /dev/sda1 /mnt/boot/efi
sudo mount --bind /dev /mnt/dev
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys
sudo chroot /mnt
It's never failed me (yet).
I have the same problem, where elogind and related packages in my multiarch setup are being held back. This problem affects wine32 which depends on one of these. I also like using elogind versus consolekit which I think might also be related/affected.
I removed wine32 and its hangers-on, and the upgrade completed successfully. I only use wine32 for one program that isn't essential in daily use, so I'll just wait until this gets sorted.
This is a beowulf system updated from ascii. Is there a proper beowulf installer so I could try a clean install?
Perhaps it's due to the version disagreement of libuuid1:amd64 and libuuid1:i386 (in beowulf) (and in unstable).
Ah, perhaps. :amd64 is 2.32.1-0.12.32.1, while the upgrade candidate for :i386 is 2.32.1-0.12.33.1, and cascading dependencies takes care of the rest. Best to just wait for :amd64 to 'catch up'?
For the past week or two, I've been getting this:
# apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
elogind libblkid1:i386 libelogind0 libmount1:i386 libpam-elogind
libuuid1:i386
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
Is there a problem somewhere, or do I just have to wait for some dependency issue to be resolved?
I really like MATE, the fork of Gnome 2. Does everything I need. I really don't care for XFCE. Forget about Gnome Shell or KDE...
No thanks people learn when they put their mind to it I know that go for a walk game no thanks take care I'll go get help somewhere else I ain't playing that shit again I will learn linux if I have to take aterol to stay awake kthxbai or designer drugs no thanks I'm good on the Griffin bullshit ty.
No game - that was sincerely meant advice. It's what I do when I get twisted up, as you so clearly are, and it works for me. You are either a deep troll (always a possibility online), or seriously tightly wrapped and need help of a kind that you will not find on tech forums.
Good luck and good-bye.