#devuan

19:04:18 <Xenguy> Hah, you're right, more is less, I must have been feeling contrary

19:05:12 <onefang> Maybe if you fix things up you'll have more less.

19:05:51 <Xenguy> I came across another similar type of utility called 'most', but didn't bother with it much

19:06:02 <onefang> Oh wait that was brocashelm. I need more sleep.

19:06:27 <Xenguy> onefang, Not bad though, that's kind of like having more slack :-)

19:48:36 <DashiePie> would intel's optane feature interfere with Devuan's installer? say, make it unable to detect the internal disk drives?

19:53:44 <DashiePie> I've done everything else, but the installer just doesn't detect anything but the stick it's already on

19:56:22 <DashiePie> I haven't disabled optane yet, so if that's the problem, probably not, but if that's not the problem, I wouldn't know what is

19:57:27 <Xenguy> So troubleshoot what you can, and then come share your sorrows here : -)

20:01:32 <DashiePie> just wanted to use it to play WoW from 2005

20:01:46 <DashiePie> instead, I get hell in the form of an OS

20:05:49 <DashiePie> the actual 1 TB drive is set to ahci or something similar, and the optane volume is nvme, and is classed as a cache

20:08:41 <rrq> any variant setting for the nvme that might work?

20:24:13 <DashiePie> I haven't tried it yet, but if that's the problem, disabling it should work, I just don't know if that's the problem, hence why I asked here

20:34:05 <DashiePie> not that I care it's not supported, but yeah

21:27:15 <DashiePie> it seems like intel's optane feature changed the status of one of the "physical disks" from cache to non-raid

21:27:27 <DashiePie> just information for all of you, in case this ever comes up again

21:31:40 <DashiePie> and it still doesn't detect the drive, only the stick

23:32:53 <andlabs19> ⧸!\ TΗIᏚ СНᎪNNᎬᒪ ΗAS ϺOVЕᎠ TO IᎡC․LIBΕᎡA．CHAΤ ＃HAΜᖇADІO ／︕⧵

23:32:54 <andlabs19> /！\ THE JΕWS ᕼΑVЕ TAKEΝ OᏙЕR FᖇEᎬNODΕ, CHATS HАVE MОᏙΕᎠ ТO ⅠRⲤ․ᒪІВЕᎡA.CᕼAT ⧸！\

23:32:55 <andlabs19> /!﹨ JOIⲚ ＃НᎪΜRADΙO TODΑY. TΗІS CዘАΝNΕⅬ ᕼAS ΜⲞVED ΤO IᎡС．LΙBΕᎡA．ᏟᎻΑT ＃HᎪMRΑDΙО /！\

23:32:59 <andlabs19> TዘΙЅ OFFIᏟІᎪLᏞⲨ EⲚᗪORSEⅮ MΕSSAᏀᎬ ᎳᎪS ⲂᖇⲞUԌΗТ ᎢO YⲞU BY ᏞIBEᖇᎪ․ϹᕼAᎢ STAᖴᖴ

23:55:25 <DashiePie> I think this is what you were waiting for buZz

07:58:22 <Katje> Question came up in another channel. What is the largest production install of devuan ?

08:00:51 <Katje> as in largest number of devuan instances running in production

08:34:54 <buZz> Katje: not sure such data would be public :)

08:36:27 <Katje> I have 7 physical machines plus lots of VM's, a snarky systemd loving "friend" said "Wow, that must be one of the largest devuan installs out there" and now I want to slap him with proof that people do use devuan

08:49:01 <Joril> Well at my workplace I've built a two-node Devuan-based cluster, and on top of it I have 4 Devuan VMs and some Ubuntu VMs (to be converted to Devuan in the hopefully-near future)

10:05:19 <Beer> Katje: golinux shared on DNG a link to distrowatch showing a lot of users giving a high score to Devuan. No idea what level of trust to put on that kind of data, but it seems to show a lot of people like (hence use?) that system. From a variety of users will come a variety of use cases

11:04:14 <golinux> Katje: Here's the link https://distrowatch.com/dwres.php?resource=ranking

11:06:13 <golinux> Katje: You can read the reviews here https://distrowatch.com/dwres.php?resource=ratings&distro=devuan

11:07:36 <golinux> Many are in-depth. Reviews for other distros seem to be rather superficial.

11:18:27 <Beer> How does one clear a package in an "unknown" state as shown by dpkg?

11:19:40 <GyrosGeier> the "unknown" is the package selection state

11:20:04 <GyrosGeier> which hasn't been used for fifteen years or so

11:21:04 <GyrosGeier> normally you'd only see these in "config-files unknown ok" state

11:21:24 <GyrosGeier> you can remove those with dpkg --purge

11:39:44 <GyrosGeier> but the key is: this line has three fields: the current state, the desired state according to dselect, and whether action is required

13:02:14 <rwp> Beer, Where are you seeing "unknown" from? I can't recall ever having run into that state before.

13:04:22 <rwp> I wormed around "grep '^Status:.*unknown' /var/lib/dpkg/status" on my systems and didn't get a match upon any of mine.

13:18:22 <fsmithred> I've seen it when a package didn't install correctly. Look for 'U' in the first field.

14:23:28 <rwp> fsmithred, I guess I am confusing it in my mind with Unpacked. But okay. Package install started, preinst or postinst fails. conffiles unpacked so state is Uc and Status: unknown error installed presumably maybe.

14:35:34 <rwp> fsmithred, I didn't set up a test case. It would be interesting to do so. But no free time for it at the moment.

14:35:58 <rwp> That's why I put a "maybe" at the end of my comment. Because I was making a presumption at that point.

15:26:04 <hendrikboom3> I'm having trouble getting tinydns to work.

15:26:21 <hendrikboom3> The log just reports @4000000060b93adc2b4c6b54 tinydns: fatal: unable to bind UDP socket: address not available

15:26:55 <hendrikboom3> But as ar as I can see, port 53 has no listeners, udp or tcp.

15:31:26 <Beer> Anyone ever tried to use armoured GPG keys in /etc/apt/trusted.gpg.d/ with a .asc extension?

15:31:31 <sadsnork> hendrikboom3, are you checking for listeners with netstat? And is it possible tinydns doesn't have enough priv to listen on 53?

15:32:12 <Beer> man apt-key talks about the .asc extension, which is normally used for armoured GPG keys... however, having done that, the key I try does not seem to be recognised

15:34:23 <hendrikboom3> netstat --tcp --udp --listening --program | grep 53

15:34:47 <sadsnork> I just checked mine with... netstat -plun | grep ":53"

15:35:17 <sadsnork> Unbound showed right away. I suspect yours should work pretty much the same

15:35:34 <sadsnork> Well, not that unbound would show up later. :-)

15:36:38 <hendrikboom3> That command you gave me just shows avahi-daemon on 5353.

15:37:38 <sadsnork> With nothing currently listening on 53 I would suspect permissions to open the port.

15:38:27 <hendrikboom3> Ah! An idea. There's a file /etc/tinydns/env/IP It contains an IP number.

15:38:40 <hendrikboom3> What IP number is supposed to be there?

15:38:59 <hendrikboom3> The IP number of the interface to look for port 53 on?

15:39:11 <sadsnork> ohhh, I have never setup tinydns - but it sounds like that might tell it what IP or interface to bind to 53

15:39:48 <hendrikboom3> Or the public IP number that the world should be using to find the authoritative domain name server.

15:40:33 <hendrikboom3> I be you're right. What's changed is that (my server died). I moved the disks into another machine.

15:41:27 <hendrikboom3> And put that machine behind a VDSL router in coffee-house mode instead of in brifdge mode.

15:41:57 <Beer> sadsnork: Mmmh Seems it might be a false alarm. It seems a cache Docker layer was misleading

15:42:04 <hendrikboom3> let me make the changeand try again.

15:43:38 <sadsnork> A quick ddg gives me the impression that it should be the IP that it will open 53 on.

15:44:23 <sadsnork> But does that mean it is working now Beer?

15:45:00 <hendrikboom3> It's not complaining about the socket any more.

15:46:02 <Beer> sadsnork: Yes it is! It would have been *very* surprising such a feature was broken *and* the corresponding man would be broken...

15:46:59 <hendrikboom3> It works! dig @8.8.8.8 topoi.pooq.com gives me the right IP number now.

15:47:52 <UsL> what is the public ip you guys talking about?

15:51:14 <UsL> .. never seen that ip or heard of it and been using windows since 1996 and *nix since 2004....

15:52:18 <sadsnork> hendrikboom3, shouldn't that be "dig @127.0.0.1 topoi.pooq.com"?

15:59:52 <UsL> guess I never saw the ips of the root servers before. 1.1.1.1 is easier to remember though.

16:03:19 <sadsnork> Just to nitpick ('cause I am a pain in the ass)... neither 8.8.8.8 [Google] or 1.1.1.1 [Cloudflare] are root actually servers. The list of roots can be found at https://www.internic.net/domain/named.root

16:04:25 <sadsnork> And client devices should of course not query them directly. :-)

16:05:22 <UsL> I don't think they even respond to us peasants

16:27:51 <hendrikboom3> sadsnork, No. @8.8.8.8. I wanted to make sure a DNS resolver *outside* my LAN could find topoi.pooq.com.

16:28:28 <hendrikboom3> You can try http://topoi.pooq.com if you like and see if it finds a web site.

16:30:04 <sadsnork> Ah! So you're using tinydns as your authoritative. I'm a little slow but catching up eh.

16:30:12 <sadsnork> Booyeah! The web site works for me hendrikboom3!

16:30:27 <hendrikboom3> That internic page is for the very top-level servers The ones you go to for looking up .com, .org, and the like.

16:30:49 <hendrikboom3> They give you other servers for looking up, say, pooq.com.

16:31:15 <hendrikboom3> Going to the DNS for pooq.com is where you go to look up topoi.pooq.com.

16:31:40 <hendrikboom3> My machine contains the authoritative DNS server for subdomains of pooq.com.

16:32:06 <hendrikboom3> And yes, thanks for testing my web site for me -- from outside.

17:14:28 <hendrikboom3> sadsnork, I didn't know tinydns *could* be used other than as an authoritative DNS.

17:18:33 <hendrikboom3> sadsnork, And my email backlog from since Sunday is starting to flow in now that DNS works again.