| brocashelm | r.i.p. beowulf | 01:34 |
|---|---|---|
| Xenguy | Won't upgrade until absolutely forced | 01:40 |
| Xenguy | Beowulf was a keeper | 01:42 |
| brocashelm | oh, i see buster is still supported until june 30 by debian | 01:43 |
| brocashelm | i got beowulf on an ancient lappy that i can't upgrade over to chimaera because of how heavy it'd be | 01:44 |
| brocashelm | since it's just a pentium m with max 2 gb | 01:44 |
| brocashelm | watching videos is "doable" on it | 01:45 |
| brocashelm | so, is it confirmed beowulf is back on the main repo for now? or just use archive.devuan.org? will there still be new updates for critical packages like xorg-server? | 01:45 |
| Xenguy | Well you still have a couple months to sort that out then | 01:45 |
| brocashelm | it's just a laptop i turn on for nostalgia reasons; i got far beefier machines i main on | 01:46 |
| Xenguy | Beowulf is fine for now, but will probably be archived June'ish | 01:46 |
| onefang | So I need to put Beowulf back on the apt-panopticon checking? | 01:52 |
| Xenguy | I think it's business as usual, until June | 01:53 |
| * onefang adds a TODO item - have apt-panopticon figure out for itself which to test. | 01:53 | |
| brocashelm | since debian has yet to archive buster, i would say so | 01:53 |
| brocashelm | buster/beowulf should still get new builds until then | 01:53 |
| brocashelm | of certain software | 01:53 |
| brocashelm | i don't think it would get new updates if using archive.devuan.org? | 01:53 |
| golinux | The archiving has been reverted. | 02:03 |
| golinux | AFAICT it was a bit of an oopsie . . . | 02:04 |
| golinux | And straightened out. | 02:04 |
| onefang | OK, I have reverted apt-panopticon to match now. | 02:07 |
| Xenguy | Check | 02:09 |
| * onefang goes back to the other stuff I was gonna do today. | 02:23 | |
| brocashelm | only beowulf-updates is not working | 02:39 |
| brocashelm | but the rest are (getting new packages from beowulf-security) | 02:39 |
| rrq | is anyone tracking all networking udev rules (=eudev rules)? there seems to be a lot of stuff there | 10:45 |
| rrq | afaict none of them are especially useful. | 10:46 |
| onefang | Not me. | 11:14 |
| fsmithred | You got me curious so I looked. In ceres I see eight rules with 'net' in the name. | 11:31 |
| fsmithred | Some of them look like they're for specific hardware. | 11:32 |
| fsmithred | There's the persistent net generator which is useful, but most of the rest of that crap I can't read. | 11:32 |
| fsmithred | 24 files have net|NET in them. | 11:36 |
| rrq | I've "shadowed" all of them; none is needed for my setup since I do networking post-pivot | 11:46 |
| rrq | you see value in "net generator" ? | 11:49 |
| fsmithred | it generates 70-persistent-net.rules which preserves the interface names | 12:08 |
| fsmithred | which can help or hurt. That file has to be excluded in creating a live snapshot so that when you boot a live usb on a different computer, it can give the interface the right (first) name | 12:10 |
| rrq | ... and not needed in most cases anyhow | 12:11 |
| fsmithred | I'm not the right person to evaluate this. I hate udev rules and have absolutely no idea how to read or use them. | 12:11 |
| fsmithred | Although I have on occasion modified and used a rules file. | 12:12 |
| rrq | my worry is that udev is more and more used for decision logic about networking | 12:12 |
| fsmithred | If we remove them, can they go somewhere for reference or examples? | 12:12 |
| rrq | doing too much and then tying it to things like "systemd-networkd" and whatnot | 12:13 |
| rrq | probably the best approach still is to shadow them in /etc | 12:13 |
| fsmithred | what do you mean? | 12:13 |
| rrq | eg: ln -s /dev/null /etc/udev/rules.d/81-net-dhcp.rules | 12:14 |
| fsmithred | would it also work to make empty files with the same names? | 12:15 |
| rrq | probably ... or even files with good commenting :) | 12:15 |
| fsmithred | oh, that's a good idea | 12:16 |
| fsmithred | probably could be the same comment in all the files | 12:16 |
| rrq | well; or maybe a generic explanation as to why, and a specific explanation of what is avoided specifically | 12:17 |
| rrq | we'll have to get some techincal writer(s) though for that I guess | 12:18 |
| fsmithred | lol | 12:39 |
| brocashelm | is beowulf-updates still missing a releases file? | 12:55 |
| brocashelm | that's the only one that failed for me | 12:55 |
| fsmithred | brocashelm, I see beowulf-updates and -proposed-updates are both working again. I'm using deb.devuan.org | 13:38 |
| bgstack15 | As a general announcement, plasma41 and I are working on a newer version of systemctl-service-shim, so if anyone has any opinions that would affect the operation of that script, let us know! | 15:06 |
| bgstack15 | While we're in there, tinkering with it and able to react to additional input on it. | 15:06 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!