You are not logged in.
- Topics: Active | Unanswered
#151 Re: News & Announcements » It'll be when It's ready, I know, but an approximation? » 2020-01-06 22:21:17
Head_on_a_Stick wrote:basati wrote:The group of developers has to have an idea of where things are going
I can't speak for the developers but fsmithred has just released the first beowulf beta for Refracta so the release is approaching.
Yup. As soon as we get the installer isos right, we'll let you play with them. Meanwhile, I switched my main box to beowulf. (Bye bye Jessie. I'm sorry it didn't work out as we first expected, but I had nothing to do with that. I kept you as pure as I could.)
My main box would be beowulf if I could install wine32. Other than that. beowulf works beautifully on my machine.
[edit: Ack! I just checked, and I was able to install wine32! So I can run the one program that I need to run in wine. Ironically, wine (64-bit) won't install because of a few held back packages. I'm sure it will get sorted, but I don't need it anyway. My main box is now beowulf!]
#152 Re: Off-topic » This should be fun... » 2019-12-12 01:24:24
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...
#153 Re: Off-topic » This should be fun... » 2019-12-11 17:43:53
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.
#154 Re: Off-topic » ladies, gentlemen and whomever else: your fifth freedom... » 2019-12-11 01:33:55
What happened to my comment? It was there a minute ago.
#155 Re: Off-topic » ill just use the mailing list » 2019-12-11 00:31:19
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.
#156 Re: Devuan » Debian considering going systemd init only » 2019-12-09 01:14:15
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. ..
#157 Re: Off-topic » This should be fun... » 2019-12-09 00:05:59
do we know the timeframe on this? when does it close?
I believe it's 20 days.
#158 Off-topic » This should be fun... » 2019-12-08 22:26:04
- sgage
- Replies: 24
Just posted on Slashdot:
Debian Begins Vote on Supporting Non-Systemd Init Options
#159 Re: Devuan » Debian considering going systemd init only » 2019-12-07 22:00:55
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'.
#160 Re: Devuan » Debian considering going systemd init only » 2019-12-07 20:13:03
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...
#161 Re: Desktop and Multimedia » SOLVED: MATE: any way to convert Applications-Places-System to single » 2019-12-05 01:45:46
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.
#162 Re: Off-topic » your irc client » 2019-11-18 20:44:42
Hexchat is good - relatively full-featured, but easy to use right away.
#163 Re: Installation » ascii 2.1 iso with openrc install doesnt work » 2019-11-07 17:35:38
Just another data point: I installed using the ascii 2.1 iso, selected the openrc option, and it all worked fine.
#164 Re: Desktop and Multimedia » Choosing an email client » 2019-10-24 22:54:33
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.
#165 Re: News & Announcements » ASCII 2.1 point release » 2019-10-23 15:40:31
I installed from the new iso (netinst) in order to check out the openrc option. It installed without issue, and openrc is working fine!
#166 Re: Other Issues » 32bit packages on a 64bit system » 2019-09-23 12:07:52
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 :-)
#167 Re: Other Issues » /etc/os-release error » 2019-09-22 23:58:56
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 :-)
#168 Re: Other Issues » 32bit packages on a 64bit system » 2019-09-22 21:38:21
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 :-)
#169 Other Issues » /etc/os-release error » 2019-09-22 20:06:43
- sgage
- Replies: 3
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. ;-) ;-) ;-)
#170 Re: Other Issues » Devuan and chroot » 2019-09-02 21:40:24
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...
#171 Re: Other Issues » Devuan and chroot » 2019-09-02 21:09:09
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).
#172 Re: Other Issues » [beowulf] Packages being held back. » 2019-08-29 12:30:11
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?
#173 Re: Other Issues » [beowulf] Packages being held back. » 2019-08-19 22:33:30
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'?
#174 Other Issues » [beowulf] Packages being held back. » 2019-08-19 21:38:55
- sgage
- Replies: 5
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?
#175 Re: Hardware & System Configuration » PulseAudio? Seriously!? » 2019-07-04 22:11:37
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...
Board footer
