| rwp | The main problem people will run into with all of the non-systemd inits is that the systemd folks are removing non-systemd init scripts. That causes users to need to do something to restore those such as installing orphan-sysvinit-scripts package. | 00:09 |
|---|---|---|
| rwp | But that is the same problem for all of the non-systemd inits equally. Each of them will suffer the same. | 00:09 |
| rwp | Because openrc and runit and s3 and the rest will run sysvinit scripts in compatibility mode okay. But they must be present. | 00:10 |
| gnarface | dvbst: just make sure when you're following the Debian backport instructions you remember to change the release name to the Devuan one | 01:02 |
| gnarface | (for current stable you would use daedalus where they say bookworm) | 01:03 |
| temp64 | anyone knows what's going on if 1) I managed to connect to a corporate Wi-Fi using wpa_supplicant + EAP-TLS 2) dhcpcd configured my /etc/resolv.conf with search and nameserver directives 3) I could ping www.google.com 4) I could not ping any of the corporate domains nor the nameservers from /etc/resolv.conf? | 12:21 |
| gnarface | dhcp or firewall misconfiguration, possibly? | 12:23 |
| adhoc | anything interesting in your route table ? | 12:23 |
| gnarface | hmm, yea, maybe the route thing | 12:24 |
| adhoc | gnarface: good angle, are they on private IP ranges ? | 12:24 |
| adhoc | ping is often blocked internally in large organizations | 12:25 |
| adhoc | most ICMP | 12:25 |
| adhoc | perhaps this is where dig might be useful | 12:25 |
| temp64 | yes, they were | 12:26 |
| adhoc | dig @(IP ADDRESS OF INTERNAL NAME SERVER) (SOME HOST NAME YOU EXPECT TO WORK) | 12:26 |
| temp64 | alright, I'll check it next time I'm in the office. what about the route table? is there anything I should look for there? | 12:29 |
| temp64 | I wish I could just connect to the VPN on my ThinkPad and check everything remotely but making BIG-IP work is probably going to be even harder :| | 12:31 |
| temp64 | gnarface: I actually have no idea how firewall works on Linux but I assume it would only deny incoming connections by default | 12:33 |
| djph | it's wide open by default | 12:35 |
| djph | "you know what you're doing, we're not gonna treat you like a child" | 12:35 |
| temp64 | oh... good thing my IT department has no idea what I'm up to in that case lol | 12:39 |
| temp64 | I'll have to set it up to match my corpo macbook | 12:40 |
| djph | potentially | 12:40 |
| fsmithred | You should be behind a router. | 13:04 |
| fsmithred | that has a firewall | 13:04 |
| fsmithred | if you have avahi installed and running, it will advertise services. You don't want to do that on the corporate network. | 13:05 |
| djph | Oh, I'm not saying you shouldn't set things up -- just that "exactly the same as the macbook" might not necessarily be the correct approach. | 13:07 |
| jmjl | Could nncp be added to the release list or how would this be requested? (it's available on debian) | 20:23 |
| hagbard | if it is in debian, it is in devuan also. | 20:28 |
| rwp | jmjl, nncp is already available in Devuan. https://pkginfo.devuan.org/cgi-bin/policy-query.html?c=package&q=nncp&x=submit | 20:29 |
| hagbard | I'm currently on devuan testing, and it is offered to me. | 20:29 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!