tuxd3v | hello, does anyone knows if syslinux is on arm64 repos? | 02:45 |
---|---|---|
tuxd3v | i need to create a menu entry for it | 02:45 |
tuxd3v | thanks | 02:45 |
tuxd3v | :) | 02:45 |
Xenguy | I'm getting errors when I try to update, on ascii | 02:47 |
tuxd3v | what type of errors? | 02:48 |
Xenguy | Err:12 http://deb.devuan.org/merged ascii-security/main amd64 libqt5xml5 amd64 5.7.1+dfsg-3+deb9u2 | 02:48 |
Xenguy | 404 Not Found [IP: 130.225.254.116 80] | 02:48 |
Xenguy | E: Failed to fetch http://mirrors.dotsrc.org/debian-security/pool/updates/main/q/qtbase-opensource-src/libqt5core5a_5.7.1+dfsg-3+deb9u2_amd64.deb 404 Not Found [IP: 130.225.254.116 80] | 02:48 |
Xenguy | Dead mirror? | 02:48 |
Xenguy | I'm using deb.devuan.org in my sources.list | 02:49 |
gnarface | probably a dead mirror. just retry. there's 13 mirrors in the DNS round-robin. don't panic unless you start getting multiple failures in a row | 02:51 |
gnarface | 13 volunteer mirrors isn't really enough to generate a complete illusion of 100% uptime | 02:52 |
Jjp137 | wait deb9u2? even Debian's package website is still showing deb9u1 so this is really new | 02:52 |
Jjp137 | so it's likely the mirrors haven't even caught up yet | 02:53 |
gnarface | yea i think you can catch them mid-update and get a failure similar to this | 02:53 |
gnarface | it would happen with Debian too, but it's less common because they have hundreds of mirrors | 02:53 |
yeti | tuxd3v: on armHF: $ apt-cache show syslinux | 02:55 |
yeti | N: Can't select versions from package 'syslinux' as it is purely virtual | 02:55 |
tuxd3v | yeti, thanks I was concerned with arm64 | 02:55 |
tuxd3v | to add support for Devuan in a new board :) | 02:56 |
tuxd3v | rockpi4A | 02:56 |
tuxd3v | :) | 02:56 |
yeti | http://packages.roundr.devuan.org/devuan/pool/main/s/syslinux/ | 02:56 |
fsmithred | I see syslinux-common and syslinux-efi in the arm64 Packages.gz | 02:56 |
yeti | too late for my eyes or no .deb | 02:56 |
yeti | my am64ers are sleeping... only i386/amd64 and armhf are "on" | 02:57 |
yeti | nah... ARM64ers are sleeping | 02:58 |
tuxd3v | yeah I don't have now any board running on arm64 only armhf | 02:58 |
yeti | that way | 02:58 |
tuxd3v | I wanted one that has the binary :) | 02:58 |
tuxd3v | '/usr/bin/syslinux' | 02:58 |
yeti | where should that come from? | 02:58 |
yeti | is ist unpatched by devuan? | 02:58 |
tuxd3v | the Idea is create a Menu for devuan to boot the desirable kernel :) | 02:58 |
yeti | than grab it from debian | 02:59 |
fsmithred | packages.debian.org only has amd64 and i386 for syslinux | 02:59 |
yeti | ok | 02:59 |
yeti | I expected such | 02:59 |
yeti | because it boots old stuff | 02:59 |
fsmithred | will syslinux work on that arch? | 02:59 |
yeti | I vote fror no | 02:59 |
tuxd3v | well I understand your concer fsmithred, and yeti | 02:59 |
tuxd3v | its very real | 03:00 |
yeti | unless arm boards get a 86 emu ike vga cards | 03:00 |
fsmithred | you're using fat32? | 03:00 |
tuxd3v | but it turns out that Uboot | 03:00 |
tuxd3v | when finds a directory and menu in /boot | 03:00 |
tuxd3v | 'extlinux/extlinux.conf' | 03:00 |
fluffywolf | I purchased 4 wooden snap traps, 2 plastic snap traps, 2 bait stations with poison bait, and 4 glue traps. whatever rat killed my car is going to have lots of options tonight for how to kill itself. | 03:00 |
fluffywolf | grr, wrong window | 03:00 |
tuxd3v | the first thing he will do is... call ''/usr/bin/syslinux', *only* to be able to interpret the menu file :) | 03:01 |
tuxd3v | then it boots up the system :) | 03:01 |
* yeti afk... for caffeine refill... | 03:02 | |
fsmithred | it actually needs syslinux, or it just needs a syslinux-style menu? | 03:02 |
tuxd3v | uboot call s internally syslinux, only to be able to parse the file | 03:02 |
tuxd3v | when parsed it forget syslinux | 03:02 |
tuxd3v | and itself boots the system :) | 03:03 |
tuxd3v | its a nice way for us to have a menu at boot with several options :) | 03:03 |
fsmithred | you might have to compile it yourself. | 03:04 |
tuxd3v | yeah maybe, I don't have here a arm64 machine with a sdcard to boot and check if devuan arm64 has the bynari in some package | 03:05 |
tuxd3v | bynari -> binary | 03:05 |
tuxd3v | I don't know how toficult it isto compile it, or cross compile it.. | 03:06 |
gnarface | the binary package for syslinux? | 03:06 |
gnarface | if it doesn't show up in packages.debian.org then probably not, and probably due to a broken compiler | 03:06 |
tuxd3v | I added to 'include' in debootstrap syslinuc and syslinux-commun | 03:06 |
tuxd3v | but the system image don't have the package I believe that its not there.. | 03:07 |
tuxd3v | gnarface, yup | 03:07 |
tuxd3v | to be able to create a '/boot/extlinux/extlinux.conf' | 03:07 |
tuxd3v | menu file | 03:07 |
tuxd3v | uboot can later boot it :) | 03:07 |
tuxd3v | but if he finds that file he will automatically forget about everything , and call syslinux to be able to parse the file | 03:08 |
tuxd3v | when he gets the representation of the parsing he forget about syslinux and boots the system :) | 03:08 |
tuxd3v | its a nice way to have a menu with several kernels for example to boot :) | 03:09 |
tuxd3v | for now I am with a 'boot.scr' boot script | 03:10 |
fsmithred | the boot script can't give you a choice of systems to boot? | 03:10 |
gnarface | you might be able to get the functionality you want with just more complex boot.scr scripting. i've heard of such things, but never tested them myself | 03:11 |
tuxd3v | fsmithred, be default no | 03:11 |
gnarface | i know for sure you can also just have multiple *.scr files that boot different kernels and partitions. it'll call the boot.scr one by default unless otherwise specified, but you can specify it at boot time like with LILO | 03:11 |
tuxd3v | I believe what gnarface is telling may be possible but it needed a very experienced Guru in Uboot | 03:12 |
tuxd3v | :) | 03:12 |
gnarface | anarsoul has a fancy one in his github somewhere. i didn't try it, it frightened me. | 03:13 |
tuxd3v | heheh | 03:13 |
tuxd3v | it could be | 03:13 |
gnarface | it might be worth digging up to look at though as an example | 03:13 |
tuxd3v | I need to talk to anarsoul | 03:13 |
tuxd3v | :) | 03:13 |
tuxd3v | yeah definitly | 03:13 |
gour | morning | 09:31 |
gour | which package you recommend for time-syncing, opentpd, ntp for desktop machine? | 09:32 |
gnarface | it probably won't matter | 09:36 |
gnarface | but openntpd is the bsd one, so for an all-linux setup of multiple systems, use the ntp one for less chance of compatibility issues | 09:36 |
gour | ok | 09:38 |
gour | i'm still shocked how my desktop machine does work with devuan (xfce) in comparison with systemd-powered manjaro/gnome...it looks as if i got a brand new hw :-D | 09:45 |
gnarface | a lot of people say that | 09:45 |
JackFrost | I'm not entirely sure if that's a fair comparison. | 09:45 |
gour | why not? | 09:46 |
sedrosken | I've got a few little complaints to iron out with my openrc config | 09:46 |
JackFrost | Xfce to GNOME. | 09:46 |
sedrosken | and hopefully transitioning from sysvinit/openrc paired to openrc whole-way | 09:46 |
gour | JackFrost: ahh, with systemd i was not able to boot without passing 'iommu=soft' and it was not possible to do clean shutdown after systemd-update | 09:47 |
gour | gnome --> xfce is just another benefit | 09:47 |
gour | atm, i'm still with sysvinit and whatever i need it does work. if devuan is going to deploy openrc/runit in the future, i do not mind much, since it can't bet worser than systemd :-) | 09:48 |
sedrosken | I vastly prefer OpenRC to sysvinit myself, I'm just waiting for the right time to completely break my install, hehe | 09:49 |
gour | is openrc still actively developed? | 09:52 |
sedrosken | oh heck yeah it is | 09:52 |
gour | what about openrc vs runit? | 09:52 |
sedrosken | it's gentoo's default | 09:52 |
sedrosken | openrc is the more robust one I say, but runit has a vast speed advantage | 09:52 |
sedrosken | not that boot speeds should be priority, but I'd use openrc on my server and runit on my laptop, for example | 09:53 |
gour | sedrosken: i had short encounter with runit on voidlinux in the past and i recall it was very easy to use, but no experience with openrc whatsoever | 09:53 |
sedrosken | well, ill put it this way, if you like sysv I'll bet you'll love openrc | 09:54 |
gour | to use == to manage services | 09:54 |
sedrosken | may follow this guide later today/tomorrow https://dev1galaxy.org/viewtopic.php?id=2788 | 09:58 |
sedrosken | well, "guide" loosely speaking | 09:58 |
sedrosken | I'll use his trials as a blueprint to my own transition | 09:59 |
sedrosken | I don't mind keeping sysvinit installed since openrc still depends on it (I think) | 09:59 |
gour | runit has not been (yet) considered as an option? | 10:01 |
sedrosken | I think they're considering it for later releases | 10:01 |
sedrosken | getting OpenRC playing nice is apparently enough work as it is, heh | 10:01 |
gour | btw, i need wine32 for some legacy apps. i see it's not available for ceres? | 10:01 |
sedrosken | did you add the i386 arch? | 10:02 |
gour | yep | 10:02 |
sedrosken | that was my screwup earlier, i didn't add it and was trying to get i386 packages | 10:02 |
gour | apt search does not report wine32 | 10:03 |
sedrosken | honestly would not know, I use the wine-staging repo that's meant for debian (but works on devuan) | 10:03 |
gour | although repos is dsynced: et:13 http://deb.devuan.org/merged ceres/main i386 Packages [8.311 kB] | 10:04 |
gour | ok, i might try wine-staging. maybe i had to use it under sid as well | 10:04 |
gordonDrogon | Hi. A possibly dumb question (or I've missed something obvious): Running ASCII. Trying to upgrade to 2.1, but the usual apt-get update/upgrade/dist-upgrade doesn't seem to pull in the 4.x kernel. Any clues? Thanks. | 10:07 |
gordonDrogon | (fwiw: Debian user since day 0, switched to devuan when I could a while back) | 10:08 |
gnarface | gordonDrogon: maybe somehow you didn't get the linux-image-amd64 meta-package | 10:10 |
* gordonDrogon checks. | 10:10 | |
sedrosken | yeah I'm not feeling froggy enough to tackle moving to pure openrc tonight, I think it's time I went to bed | 10:10 |
gnarface | or linux-image-i386 as appropriate | 10:10 |
gordonDrogon | ii linux-image-3.16.0-4-amd64 3.16.51-3 amd64 Linux 3.16 for 64-bit PCs | 10:11 |
gordonDrogon | maybe I picked the wrong one from the 'netinst'... | 10:11 |
gnarface | there should be linux-image-amd64 and linux-headers-amd64 meta-packages you can install to get kernel upgrades along with everything else | 10:12 |
gnarface | otherwise you have to install them individually | 10:12 |
gordonDrogon | search finds linux-image-amd64 - I'll install that. what's the worst ... | 10:13 |
gordonDrogon | here goes nothing.. | 10:17 |
gordonDrogon | ok. seems to now have 4.9. Thanks. I guess I just picked the wrong one when I did the 'netinst' thing. | 10:21 |
gnarface | that might be a possibility, or maybe it was a really old netinst image? | 10:22 |
gordonDrogon | it was ASCII. I was already running Jessie, but decided on a fresh install. | 10:22 |
gordonDrogon | I do recall it giving me a choice of kernels but don't recall what I did at that step.. ah wel. | 10:23 |
gour | sedrosken: for which version you use wine-staging repo? i tried with bullseye, but got Failed to fetch http://debian.bio.lmu.de/debian/pool/main/s/systemd/libsystemd0_244.1-3_amd64.debt | 11:32 |
sedrosken | I used buster since I'm on beowulf | 11:36 |
gour | aha...what would you recommend for ceres? | 11:37 |
gour | which iso should i put on a stick to serve for rescue-mode when required?? | 13:11 |
fsmithred | gour, any of the installer isos will work | 13:19 |
gour | ok | 13:34 |
phaoost | Hi all. I've just updated my system and unable to boot now. cryptsetup fails with message: libgcc_s.so.1 must be installed for pthread_cancel to work | 16:17 |
phaoost | Can someone point me on some bootable ISO with the recent devuan version? Ascii won't work on my hardware | 16:18 |
fsmithred | phaoost, what did you upgrade from (and to what?) | 16:23 |
fsmithred | or are you just looking to do a fresh install? | 16:23 |
phaoost | I am looking for bootable iso to repair my system | 16:23 |
phaoost | I upgraded from ceres to ceres | 16:24 |
fsmithred | oh | 16:24 |
fsmithred | there aren't any official beowulf isos yet | 16:24 |
phaoost | right, maybe some nightly pre-alpha? | 16:24 |
phaoost | my network won't load on kernel less than 4.14 | 16:25 |
fsmithred | there's an unofficial beowulf desktop-live iso made by aitor (gnuinos), there's an unofficial desktop-live with backports kernel that I made, | 16:25 |
fsmithred | there's a refracta-beowulf-beta iso that I made - if you want to repair from a live system, this is a good choice | 16:25 |
GyrosGeier | "libgcc_s.so.1 must be installed for pthread_cancel to work" sounds like something weird happened while building the initrd | 16:25 |
fsmithred | if you want to use the installer's rescue system, use the one aitor made | 16:26 |
GyrosGeier | as in "this is a should-not-happen" error | 16:26 |
phaoost | I don't think I need installer | 16:26 |
fsmithred | yeah, that is a weird error | 16:26 |
phaoost | just need some system to boot and hook up encrypted rootfs | 16:26 |
fsmithred | https://get.refracta.org/files/testing/ | 16:27 |
GyrosGeier | I mean, I understand that glibc tries to avoid a hard dependency on libgcc_s, because that dependency would be cyclic | 16:27 |
GyrosGeier | but all the other programs would have a dependency, so it should definitely be present | 16:27 |
phaoost | cool, thanks, I'll check it | 16:28 |
phaoost | yeah weird, I'll check if I can add libgcc_s.so.1 to initrd | 16:29 |
specing | phaoost: boot into old kernel? | 16:29 |
specing | phaoost: old initramfs? Or where is cryptsetup erroring out? | 16:29 |
phaoost | kernel was not updated with recent updates, it's 5.4 I believe and it was booting fine | 16:30 |
phaoost | but after recent update I got this error. but I'll try older one, I think I have 4.9 still | 16:30 |
phaoost | I am getting this error after entering passphrase | 16:31 |
phaoost | even hitting enter with no passphrase give the same error | 16:31 |
specing | do you have encrypted system or just data? | 16:38 |
gnu_srs1 | phaoost: Which version of gcc is installed, on debian-devel there is a lot of discussions and bugs on libgcc_s.so.1 | 16:39 |
phaoost | specing: rootfs is encrypted | 16:39 |
phaoost | gnu_srs1: with recent update I've gotten gcc10 installed but I think I still have 9 also | 16:40 |
specing | phaoost: then it is not system update that broke it | 16:40 |
specing | if it fails before mounting system | 16:40 |
specing | but an initramfs problem, and going back to old initramfs should fix that | 16:40 |
gnu_srs1 | See #950525 and #950624 | 16:40 |
phaoost36 | ok thanks all, I'll check and be back soon hopefully ;) | 16:44 |
gnu_srs1 | See also #950254 and #950551 | 16:49 |
phaoost | ok looks like older image really worked | 16:51 |
phaoost | so how would I fix newer image? should I repack it manually to include libgcc_s.so.1 ? | 16:55 |
fsmithred | phaoost, try rebuilding with 'update-initramfs -u -k all' and then check the new initramfs with 'lsinitramfs /boot/initrd.img-<version> | grep libgcc_s.so.1' | 16:58 |
gnu_srs1 | which version of initramfs-tools do you have? | 16:58 |
phaoost | I see only gcc-10-base was installed with the recent update | 16:58 |
fsmithred | bbiab | 16:59 |
phaoost | initramfs is 0.136 here | 16:59 |
phaoost | hm | 17:00 |
phaoost | lsinitramfs /boot/initrd.img-5.4.0-3-amd64 |grep libgcc_s.so.1 shows nothing, while lsinitramfs /boot/initrd.img-5.4.0-2-amd64 |grep libgcc_s.so.1 shows usr/lib/x86_64-linux-gnu/libgcc_s.so.1 | 17:01 |
phaoost | I would refrain from rebuilding all images as I can get totally unbootable system | 17:02 |
gnu_srs1 | I think the solution is in: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950551 | 17:03 |
phaoost | thank you, this is it | 17:07 |
GyrosGeier | hm | 17:15 |
GyrosGeier | should we perhaps teach debootstrap a mapping between distribution codenames and keyrings? | 17:16 |
GyrosGeier | E: Release signed by unknown key (key id CBF8D6FD518E17E1) The specified keyring /usr/share/keyrings/devuan-archive-keyring.gpg may be incorrect or out of date. You can find the latest Debian release key at https://ftp-master.debian.org/keys.html | 17:16 |
mason | GyrosGeier: It would be a bit out of scope for debootstrap to imbibe signing keys. | 17:35 |
GyrosGeier | it seems there is a mapping, and "jessie" is hardcoded to use the Devuan keyring | 17:40 |
GyrosGeier | so one cannot debootstrap a VM or container with Debian jessie in it | 17:40 |
fsmithred | my initrd for 5.4 does not have libgcc_s.so.1 but I can boot my encrypted root. | 17:43 |
fsmithred | I just upgraded my ceres a few minutes ago. | 17:43 |
fsmithred | coffee... | 17:44 |
GyrosGeier | hmm | 17:44 |
GyrosGeier | Devuan reportbug configures reportbug.debian.org as SMTP host by default | 17:44 |
GyrosGeier | that is kind of broken | 17:44 |
fluffywolf | reportbug is fairly broken in general, since you generally can't randomly send smtp from home connections anymore, with most isps blocking all relevant ports in and out, and usually not even being nice enough to provide a smarthost anymore. | 17:46 |
fluffywolf | it needs to use some other method to submit its reports. | 17:46 |
fluffywolf | it can't send smtp directly, and who ever configures working local mail on a desktop anymore? | 17:46 |
fsmithred | send bug reports to submit@bugs.devuan.org | 17:47 |
fsmithred | replies to bug#NN@bugs.devuan.org | 17:48 |
fsmithred | NNN | 17:48 |
fluffywolf | imho, it should be modified to report bugs over https. even if it just dumps the email to a little script that forwards it to the mta on the bugtracker. | 17:49 |
GyrosGeier | fluffywolf, it works for Debian, because they run an SMTP server that accepts incoming bug mail | 17:51 |
fluffywolf | except it doesn't, because ISPs block outgoing SMTP, by blocking all common ports, and often doing deep packet inspection of various kinds to find smtp on non-standard ports, to prevent zombie windows boxes sending spam. | 17:53 |
GyrosGeier | mmh | 17:55 |
fluffywolf | and even if your ISP provides a smarthost, that's setup that many people aren't going to want to do just to report a bug, and ISPs seem to be increasingly rarely providing one. and MTAs on the desktop seem like a dead concept now. | 17:56 |
GyrosGeier | true | 17:56 |
GyrosGeier | that doesn't change the fact that we have a package that generates an annoying non-working configuration | 17:56 |
Evilham | https://wiki.debian.org/reportbug | 17:57 |
Evilham | Configuration -- Using a custom SMTP server | 17:57 |
Evilham | needed by pretty much everypony | 17:57 |
fluffywolf | the easiest fix would be for the reportbug server to have a trivial script that accepts an email over https and feeds it to the local mta, and reportbug to fire up wget, curl, whatever and post the email to this script. | 17:57 |
GyrosGeier | we still shouldn't default to "reportbug.debian.org" though | 17:57 |
GyrosGeier | that is pretty much always guaranteed not to accept mail to the Devuan BTS | 17:58 |
fluffywolf | Evilham: what percentage of gmail users do you think know what SMTP is? heh | 17:58 |
fluffywolf | also, as I said, most ISPs these days block smtp, either by blocking all standard ports, or also by packet inspection. | 17:59 |
fluffywolf | I can't remember the last time I saw a residential ISP allow outgoing smtp. | 17:59 |
Evilham | fluffywolf: actually, that wiki is soon to be outdated: gmail is deprecating IMAP and SMTP | 17:59 |
phaoost | fsmithred: hm, what could be the issue then? are you using 5.4.0-3 ? | 17:59 |
fsmithred | yes, with encrypted lvm | 17:59 |
fluffywolf | it used to be they insisted you send anything through their smarthost, but now it seems many don't even provide one. | 17:59 |
phaoost | aha, I don't have lvm | 18:00 |
fluffywolf | with the assumption that you can use webmail, or fuck off. | 18:00 |
fluffywolf | I mostly blame gmail for this. | 18:00 |
fluffywolf | for making people think webmail was a good idea... | 18:00 |
fluffywolf | my ISP doesn't even provide you with an email address at all, and I think this is slowly becoming the norm. | 18:01 |
fluffywolf | that is, they run no mail servers of any kind, and you have to find email elsewhere. | 18:01 |
GyrosGeier | outgoing SMTP works fine both at home and on mobile for me | 18:02 |
fluffywolf | last time I used reportbug, I ended up scp its dump of the email to my web server and feeding it manually to the mta there. | 18:03 |
fluffywolf | this pissed me off. | 18:03 |
fluffywolf | I haven't reported any bugs since. This is not because I haven't encountered any bugs, but rather than the process of reporting them took excessive effort. | 18:04 |
fluffywolf | s/than/that | 18:04 |
GyrosGeier | precisely | 18:05 |
GyrosGeier | that is why it needs to be fixed | 18:05 |
fsmithred | wtf?? gmail is going to webmail only? | 18:05 |
fluffywolf | even configuring a custom SMTP server, like shown in the wiki, exceeds the difficulty most desktop users are prepared for. | 18:05 |
fluffywolf | it should default to something that Just Works, and have the option to be configured some other way for advanced users. | 18:06 |
GyrosGeier | that is what I'm saying | 18:06 |
GyrosGeier | reportbug --configure asks you "do you run your own SMTP server?", and if you say no, it configures Debian's server for you | 18:06 |
phaoost | I think gmail will close imap soon. I was receiving some notice about that time ago. so smtp will be probably closed too | 18:07 |
GyrosGeier | which is a reasonable default for Debian, but doesn't work for anyone else | 18:07 |
fluffywolf | hell, at the rate we're going, it wouldn't surprise me if a non-trivial percentage of new users have never even used email... SMS, telegram, facebook messenger, discord, amino, whatever... | 18:07 |
GyrosGeier | email isn't going away | 18:07 |
GyrosGeier | neither is IRC | 18:07 |
fluffywolf | I didn't say it was going away. I said it's possible a percentage of new users have not used it. | 18:07 |
fluffywolf | and none of them have used IRC. we're all old farts. :P | 18:08 |
GyrosGeier | also, I'm fairly sure everyone is using email | 18:08 |
GyrosGeier | because it's still the lowest common denominator protocol | 18:08 |
GyrosGeier | until Russia and China agree that they want their companies to communicate internally via Facebook | 18:09 |
fluffywolf | really? you mention email these days to anything under 25, and they give you that patronizing-the-old-fogey look. :P | 18:09 |
GyrosGeier | they don't use email for private stuff | 18:10 |
GyrosGeier | but they will send a nicely formatted PDF as an attachment when applying for a job | 18:11 |
fluffywolf | LOL. maybe for tech jobs... | 18:11 |
GyrosGeier | also, it seems my setup is broken | 18:11 |
GyrosGeier | I haven't received a security update for sudo | 18:11 |
GyrosGeier | Security Advisories | 18:12 |
GyrosGeier | None so far. | 18:12 |
GyrosGeier | nevermind then | 18:12 |
fluffywolf | it's getting really hard to get people onto IRC these days too... and I've lost channel members to telegram, discord, and amino in particular... | 18:13 |
specing | fluffywolf: the best way is not to use those chat services | 18:14 |
specing | then you are only available on IRC | 18:14 |
fluffywolf | I don't use them. eventually I'll be sitting here alone. :P | 18:14 |
specing | yes | 18:15 |
golinux | No you won't | 18:16 |
* fluffywolf sits on golinux's lap for company | 18:17 | |
specing | golinux: they will, I know from personal experience ;) | 18:20 |
fluffywolf | bbl, thawing out outside, working on car. | 18:25 |
tuxd3v | hello guys, | 18:40 |
tuxd3v | does anybody knows what is the miniSSDP demoan? | 18:40 |
fsmithred | minissdpd - keep memory of all UPnP devices that announced themselves | 18:41 |
tuxd3v | I am tryin got migrate my desktop to beowulf... I need it to create arm beowulf images based on crossdebootstrap.. | 18:43 |
tuxd3v | in this process , it his asking me about if it should start automatically anow and at boot time? | 18:43 |
tuxd3v | I don't know what to say :) | 18:44 |
tuxd3v | it shoulçd be started automatically? | 18:44 |
tuxd3v | in a desktop? | 18:44 |
fsmithred | I don't know anything about it. | 18:45 |
fsmithred | brb | 18:45 |
tuxd3v | l say no to this Upnp, is something intrusive right? | 18:46 |
tuxd3v | dlna and others.. | 18:47 |
tuxd3v | for what I see: http://miniupnp.free.fr | 18:48 |
tuxd3v | it was introduced in debian in 2017 iirc | 18:48 |
fsmithred | I don't think I've ever had it installed | 18:54 |
Pali | tuxd3v: Hi! I know what is minissdpd | 18:58 |
Pali | if you are not using upnp network devices, you do not need it | 18:59 |
Pali | and if you do not use upnp clients then you do not need it too | 18:59 |
Pali | and if you properly configure your firewall (to do not drop multicast replies from upnp devices) you probably do not need it too | 19:00 |
Pali | see https://github.com/miniupnp/miniupnp/blob/master/miniupnpc/README section * Linux firewall configuration for UPnP clients * | 19:02 |
tuxd3v | hello all, | 21:17 |
tuxd3v | In the process to transit to beowulf in my main desktop, I took the very unwise path, and decided to do that in a graphical environment.. | 21:17 |
sedrosken | gour: I honestly would not know | 21:18 |
tuxd3v | after some time the list of 1.8GB od data to install.. run bad as X crashed.. | 21:18 |
tuxd3v | and so dist-upgrade crashed with it.. | 21:18 |
tuxd3v | let me in the dark | 21:18 |
sedrosken | you should be able to do another dist-upgrade from console and it should pick up where it left off | 21:19 |
sedrosken | it did for me | 21:19 |
sedrosken | or maybe an apt --fix-broken install | 21:19 |
tuxd3v | with hundreds of packages at mid starte, some installed but majority don't | 21:19 |
tuxd3v | well, at least apt was nice enough to tell me that some hundred of packages were kept back :) | 21:19 |
tuxd3v | I made a script took that list and apt-get install --reinstall all of them | 21:20 |
tuxd3v | I recovered mostly of my desktop | 21:20 |
tuxd3v | I believe | 21:20 |
tuxd3v | lol | 21:20 |
tuxd3v | but there are still some anoiances | 21:20 |
tuxd3v | like sound | 21:20 |
tuxd3v | I don't have sound in xfce | 21:20 |
sedrosken | kinda like how last night I ripped out consolekit in favor of having 100% elogind -- apt was giving me a scarily huge list of stuff to autoremove, and I eventually got it figured out I think | 21:21 |
sedrosken | even if a lot of deps are now considered "manually installed" | 21:21 |
tuxd3v | the blueman applet to deal with bluetooth was also broken | 21:21 |
sedrosken | yeah I still haven't quite got it going, it complains about dbus | 21:21 |
tuxd3v | also the marvel solution that I and fsmithred found | 21:21 |
tuxd3v | for correcting my screen resolution doesn't load in .config/autostart | 21:22 |
GyrosGeier | I'm kind of nervous that there still hasn't been a security update for sudo | 21:22 |
tuxd3v | sudo is not my principal concern right now, but what is hapening with it? | 21:23 |
specing | there is a security update for sudo | 21:23 |
specing | it's "remove sudo" :) | 21:23 |
tuxd3v | don't understand, sudo is working for me | 21:23 |
tuxd3v | ..maybe I still have the older one :D | 21:24 |
sedrosken | what's insecure about it now? | 21:24 |
tuxd3v | after all the update crash wasn't in vain :) | 21:24 |
fsmithred | tuxd3v, is pulseaudio installed? | 21:24 |
tuxd3v | I have a pulse audio plugin | 21:26 |
tuxd3v | but alsamixer crashs | 21:27 |
tuxd3v | and the audio simbol is with '-' | 21:27 |
tuxd3v | means mute, or no sound | 21:27 |
tuxd3v | I have my eyes hurting from the console zillion things that I already made.. | 21:27 |
tuxd3v | but now I have graphical environment | 21:28 |
sedrosken | I wonder if there's a way to apply truetype fonts to actual ttys | 21:28 |
sedrosken | or would that require being in a graphical mode | 21:29 |
GyrosGeier | the latter | 21:29 |
yeti | eeeek | 21:29 |
tuxd3v | fsmithred, I will try to install or '--reinstall' pulseaudio plugin | 21:29 |
tuxd3v | :) | 21:29 |
fsmithred | tuxd3v, why? | 21:29 |
sedrosken | Sad! | 21:29 |
GyrosGeier | you could probably render a monospaced TT font out to bitmaps | 21:29 |
sedrosken | oh well | 21:29 |
GyrosGeier | and then use that | 21:29 |
yeti | my eyes hurt less when not using a GUI | 21:29 |
sedrosken | ooh, yeah that actually sounds like a fun project there | 21:29 |
GyrosGeier | I just use ratpoison as a WM and a fullscreen xterm | 21:30 |
yeti | tuxd3v: maybe you shouldn't use a 5x7 font in xterm | 21:30 |
yeti | .-Þ | 21:30 |
tuxd3v | yeti, but the problem here was that I had to type hundreds of packages by hand, so visually intense.. | 21:30 |
GyrosGeier | same effect, but full acceleration | 21:30 |
tuxd3v | also update-alternatives --all by hand | 21:30 |
fsmithred | I don't think that pulseaudio plugins will do anything if you're not using pulseaudio | 21:30 |
tuxd3v | no copy & paste | 21:31 |
sedrosken | I use urxvt and a solarized color scheme, they were right, it's going to be hard to ever go back | 21:31 |
sedrosken | solarized dark | 21:31 |
yeti | tuxd3v: redirection... or install gpm | 21:31 |
tuxd3v | I noticed that the grub theme, the cinnabar one.. | 21:31 |
yeti | or screen or tmox... they can do it | 21:31 |
tuxd3v | at beguining was showing me the devuan entry | 21:31 |
tuxd3v | but after some mooves and install of kernel 4.19 | 21:32 |
tuxd3v | it cowardly call the entry 'debian' | 21:32 |
fsmithred | tuxd3v, you can change that with a simple edit and update-grub | 21:32 |
fsmithred | in /etc/os-release ID=devuan | 21:33 |
sedrosken | yeah it calls this debian and so does hexchat's sysinfo plug | 21:33 |
tuxd3v | in '/etc/default/grub' ? | 21:33 |
fsmithred | in /etc/os-release ID=devuan | 21:33 |
tuxd3v | fsmithred, thanks | 21:33 |
fsmithred | then run 'update-grub' to regenerate the menu | 21:33 |
tuxd3v | I will do that | 21:33 |
tuxd3v | and then update-grub2 ;) | 21:33 |
tuxd3v | thanksyou! | 21:34 |
sedrosken | did that myself, thanks for the pointer | 21:34 |
tuxd3v | thank you! | 21:34 |
sedrosken | I wonder if that'll make sysinfo see it as devuan now or if it just won't no matter what lol | 21:34 |
fsmithred | it got changed to ID=debian so that some third-party software will recognize us | 21:34 |
fsmithred | what is this hexchat sysinfo? | 21:34 |
sedrosken | that's weird, I'd have figured the ID-LIKE thing would be enough | 21:34 |
sedrosken | Client: HexChat 2.14.2 • OS: Debian 10.0 • CPU: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (1.60GHz) • Memory: Physical: 15.2 GiB Total (10.2 GiB Free) Swap: 16.4 GiB Total (16.4 GiB Free) • Storage: 2.0 TB / 8.0 TB (6.0 TB Free) • VGA: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] @ Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller • Uptime: 14h 33m 17s | 21:34 |
sedrosken | says I'm running debian 10 when I am very much not | 21:35 |
specing | Isn't devuan what debian should have been? | 21:35 |
fsmithred | specing, yes, pretty much | 21:35 |
sedrosken | well, yeah, but i'd appreciate it seeing Devuan 3 instead of Debian 10.0 | 21:35 |
fsmithred | did you restart hexchat? | 21:36 |
GyrosGeier | specing, not yet | 21:36 |
sedrosken | just did | 21:36 |
sedrosken | i run znc so that's pretty quick and painless | 21:36 |
sedrosken | Client: HexChat 2.14.2 • OS: Debian 10.0 • CPU: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (1.60GHz) • Memory: Physical: 15.2 GiB Total (10.1 GiB Free) Swap: 16.4 GiB Total (16.4 GiB Free) • Storage: 2.0 TB / 8.0 TB (6.0 TB Free) • VGA: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] @ Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller • Uptime: 14h 35m 4s | 21:36 |
fsmithred | is that a plugin that gives you the system info? | 21:36 |
sedrosken | still says that | 21:36 |
sedrosken | yeah | 21:36 |
sedrosken | I mean, it sees Artix as "Unknown Distro" so maybe it's better this way :P | 21:37 |
fsmithred | lol | 21:37 |
sedrosken | at least it says something comparable | 21:37 |
fsmithred | I was going to suggest looking at the source code - it might be an easy fix | 21:37 |
fsmithred | otherwise, just don't look at it | 21:37 |
sedrosken | I'm not super worried about it, just a little annoyed | 21:37 |
sedrosken | it's not like I'm using that for support or anything, just to brag in other channels :P | 21:38 |
fsmithred | yeah, I get annoyed when I see 'debian' in the boot menu | 21:38 |
sedrosken | I wonder what applications work with ID=debian that don't with ID=devuan? I never noticed anything funny when it was calling it Devuan | 21:38 |
fsmithred | also confuse, because I do have at least one debian vm floating around here somewhere | 21:38 |
fsmithred | third-party enterprise stuff | 21:39 |
sedrosken | I still need to set up some of my server stuff -- apache2, vsftpd, samba, maybe even nfs | 21:40 |
sedrosken | samba and vsftpd because I run some older machines on the LAN that need that to access my network shares | 21:41 |
tuxd3v | fsmithred, thanks | 21:44 |
tuxd3v | the /etc/or-release solved the grub thing ;) | 21:44 |
tuxd3v | even the icon is there, up and kicking! | 21:44 |
tuxd3v | :) | 21:44 |
tuxd3v | I installed the pulse audio packages 'pulseaudio xfce4-pulseaudio-plugin libpulse0 pulseaudio-module-bluetooth' | 21:44 |
fsmithred | tuxd3v, do you like using pulseaudio? | 21:45 |
tuxd3v | I have a xfce4 pulse audio plugin icon in desktop, i believe that I were using it with blueman for bluethooth audio | 21:46 |
tuxd3v | but When I click on it it says 'stablishing conection with pulse audio.Please wait' | 21:46 |
tuxd3v | but nothing appears | 21:47 |
fsmithred | make sure it's running | 21:47 |
fsmithred | you might need to edit /etc/pulse/client.conf.d/00-disable-autospawn.conf | 21:47 |
fsmithred | comment out the line that says autospawn=no | 21:48 |
tuxd3v | fsmithred, man...you rock! | 21:49 |
tuxd3v | its correct now apears the gui. I will check if sound comes out :) | 21:49 |
tuxd3v | sound via jack is working | 22:03 |
tuxd3v | but I can't start blueman | 22:03 |
tuxd3v | and bluetooth adaptors gui, only shows a close button...yeah only a close button :) | 22:04 |
tuxd3v | couldn't stablish what is wrong with my bluetooth manager(blueman) | 23:35 |
tuxd3v | its noit working.. | 23:35 |
tuxd3v | noit -> not | 23:35 |
tuxd3v | someone mentioned a problem with sudo? | 23:35 |
tuxd3v | what problem? | 23:35 |
fsmithred | local root exploit: https://www.linux.com/news/debian-sudo-security-announcement/ | 23:38 |
tuxd3v | thanks | 23:39 |
fsmithred | no! | 23:39 |
fsmithred | that's from 2002 | 23:39 |
fsmithred | sorry | 23:39 |
fsmithred | https://security-tracker.debian.org/tracker/source-package/sudo | 23:40 |
tuxd3v | fsmithred, thanks | 23:44 |
tuxd3v | they say that in 1.8.26 was introduced a change in EOF handling that by itself prevents it from happening , but the issue by itself was only corrected in 1.8.31, which let us in the middle of something.. :) | 23:47 |
tuxd3v | can anyone access to: https://deb.devuan.org | 23:51 |
yeti | tuxd3v: Error code: SSL_ERROR_BAD_CERT_DOMAIN | 23:53 |
tuxd3v | yeah I get the same | 23:53 |
yeti | http://deb.devuan.org/ is ok | 23:53 |
tuxd3v | try it :) | 23:53 |
tuxd3v | I think its not :) | 23:54 |
yeti | I can update via http: | 23:55 |
tuxd3v | to me it gives the exact same error about certificate | 23:55 |
tuxd3v | which is strange | 23:56 |
tuxd3v | unless there are a redirect somewere from http to https | 23:56 |
yeti | rotation? | 23:56 |
tuxd3v | it could be | 23:56 |
yeti | some mirrors have a https-problem, some not? | 23:56 |
tuxd3v | it can also be :) | 23:57 |
tuxd3v | it redirects to https | 23:58 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!