ukine | what pure-FOSS driver supporting USB WiFi adapter would you kind folks recommend? | 03:20 |
---|---|---|
gnarface | is there even one? | 03:31 |
gnarface | i'm not sure ther eis | 03:31 |
gnarface | not sure there is* | 03:32 |
MinceR | the Wi-Pi might qualify, as i could use it in an installation process that lacked firmware for the built-in WiFi adapter... | 03:34 |
ukine | i have the internal one working with iwlwifi, i was just curious. | 03:35 |
ukine | it may come down to being the difference in linux security between pre-intel ME machines (Golan series wifi, in my case with a pre-ME laptop), and ME supporting stuff relatively right after the time period of my laptop, in .gov eyes. | 03:37 |
ukine | as they say, curiosity killed the cat XD | 03:37 |
MinceR | curiosity keeps the cat fed | 03:46 |
ukine | i have reason to allow certain acting that keeps me (externally, at least) on the straight and narrow :] | 03:48 |
ukine | also, Wi-Pi if broadcom too (like regular Pi's i'm assuming) is gchq-ware | 03:49 |
ukine | there's no escaping big brother lol | 03:50 |
ukine | america's, at least ;) | 03:51 |
ukine | maybe pinebook does security right. i shouldn't have been so bold with that last line. | 03:55 |
MinceR | its module is rt2800usb, whatever that is | 03:55 |
MinceR | apparently ralink | 03:55 |
ukine | realtek i'm guessing | 03:55 |
ukine | oic | 03:55 |
ukine | cool cool :] | 03:56 |
ukine | not to mention that it's been seeping (in a positive way) into my internal form nicely. | 03:59 |
ukine | trusting no-one goes against nature…now we're way off topic in this channel so i'll stop. | 04:00 |
MinceR | :) | 04:01 |
ukine | <3 man, lots of it. i'm just hyper-reactionary heh. | 04:02 |
Vall | Hello everyone, long time no see. | 15:07 |
Vall | Just dist-upgraded a test VM here from ASCII to Beowulf. | 15:07 |
Vall | Worked without a hitch, except I wasn't able to use the ceres-backports repo... | 15:08 |
Vall | Meaning, having the following lines in /etc/apt/sources.list threw an error during `apt-get update`: | 15:09 |
Vall | # apt install --yes dpkg-dev linux-headers-$(uname -r) linux-image-amd64 | 15:09 |
Vall | oops | 15:09 |
Vall | I mean: | 15:09 |
Vall | deb http://deb.devuan.org/merged ceres-backports main | 15:11 |
Vall | deb-src http://deb.devuan.org/merged ceres-backports main | 15:11 |
Vall | And the error is: | 15:11 |
Vall | E: The repository 'http://deb.devuan.org/merged ceres-backports Release' does not have a Release file. | 15:11 |
Vall | --- | 15:12 |
Vall | So, what am I doing wrong? Or is the ceres-backports repo f*cked? | 15:12 |
Vall | (I really want to use the ceres-backports, among other things, for ZFS 0.8.x) | 15:13 |
fsmithred | hi Vall | 15:14 |
fsmithred | what you're doing wrong is trying to use ceres-backports. There's no such thing. Ceres is Unstable (sid) | 15:15 |
Vall | LOL | 15:15 |
Vall | I knew I was messing up somehow ;-) | 15:15 |
fsmithred | you should have upgraded to beowulf, which is =buster | 15:15 |
fsmithred | and we don't have anything corresponding to debian testing (bullseye) yet. | 15:15 |
fsmithred | Did you upgrade to ceres? | 15:16 |
Vall | nope, to beowulf | 15:16 |
fsmithred | whew! | 15:16 |
fsmithred | beowulf-backports is active as of a couple days ago | 15:16 |
fsmithred | I'm not seeing any zfs in beowulf-backports | 15:18 |
fsmithred | maybe later | 15:18 |
Vall | But please see here: https://i.imgur.com/62Ehwv3.png | 15:21 |
Vall | That was what gave me the impression that a ceres-backports would be available | 15:21 |
Vall | isn't `beowulf-backports` supposed to be used in ASCII systems when one wants packages from Beowulf that had been backported to ASCII? | 15:22 |
Vall | That was the way I always thought about it... | 15:23 |
Vall | (ie, the distro in the sources-list 'backports' referring to the *next* version, not the current one) | 15:24 |
fsmithred | yes, and there's zfs in ascii-backports, so I would expect that whoever did that might backport 0.8 for beowulf. | 15:24 |
fsmithred | that's what I meant by 'maybe later' | 15:25 |
fsmithred | unless you want to do it. | 15:25 |
Vall | hummmrmrmr | 15:25 |
Vall | so if someone is running eg Beowulf, he is supposed to have "beowulf-backports" lines in /etc/apt/sources.list, and *not* "ceres-backports" lines? | 15:26 |
Vall | (I ask because I've had "beowulf-backports" lines in my *ASCII* machines since forever, and it always worked) | 15:27 |
fsmithred | you should have been getting error messages about beowulf-backports until a couple days ago | 15:27 |
Vall | SO I supposed the same (ie, "N+1 on the release name for the backports line) would apply to Beowulf too | 15:28 |
fsmithred | when running ascii, you can use ascii-backports. It should not be enabled by default. | 15:28 |
fsmithred | use beowulf-backports with beowulf | 15:28 |
fsmithred | It means "things that have been backported to work on beowulf." | 15:29 |
Vall | OK, so the general rule is to use the same release name (and not the next one) in the backports line, correct? | 15:29 |
fsmithred | yes | 15:30 |
fsmithred | and don't use it for everything possible | 15:30 |
fsmithred | because that never gets tested | 15:30 |
Vall | Thanks for setting me straight, fsmithred. I've been making that mistake since forever... :-/ | 15:30 |
fsmithred | yw | 15:30 |
fsmithred | it's also not a bad idea to pin backports to a lower priority (e.g. 100) in case the repo has it set to the wrong priority, which has happened in the past. | 15:31 |
fsmithred | or just enable it when you want to install something from bpo. | 15:31 |
Vall | seems the easier way to get ZFS 0.8.x on Devuan right now is to compile from source... it can generate .deb files that I can then install manually | 15:32 |
Vall | thanks for the tip re: backport pinning, will set it here | 15:32 |
fsmithred | yeah, download the debianized source package and build it on beowulf | 15:32 |
fsmithred | that might work easily | 15:32 |
Vall | actually, with zfs we download their standard tar.gz then run `./configure && make && make deb` | 15:33 |
Vall | s/download/download+extract | 15:33 |
Vall | Another question: the better way to pin BPO is to create a specific file for that under /etc/apt/apt.conf.d/, right? | 15:35 |
fsmithred | in /etc/apt/preferences.d/ | 15:36 |
fsmithred | you can have multiple pins in one file | 15:36 |
fsmithred | see man apt_preferences | 15:36 |
mason | Vall: In case you haven't seen it, details about custom package creation are here: https://github.com/zfsonlinux/zfs/wiki/Custom-Packages | 15:36 |
Vall | thanks mason, I had it already | 15:37 |
Vall | fsmithred ok | 15:37 |
fsmithred | Pin: * | 15:38 |
fsmithred | no | 15:38 |
fsmithred | Pakcage: * | 15:38 |
fsmithred | Pin: origin n=beowulf-backports | 15:38 |
fsmithred | Pin-Priority: 100 | 15:38 |
fsmithred | nope: should be a=beowulf-backport (not n=) | 15:39 |
fsmithred | shit | 15:40 |
fsmithred | second line should be: Pin: release a=beowulf-backports | 15:40 |
fsmithred | this is why I need two monitors | 15:40 |
Vall | OK | 15:41 |
Vall | would 'Pin: release a=*-backports' work? | 15:42 |
Vall | (ie, wildcard in the release name? | 15:42 |
fsmithred | yes | 15:42 |
Vall | OK, will set it that way then | 15:42 |
fsmithred | you don't need buster-backports | 15:42 |
fsmithred | and you don't need ascii-backports anymore | 15:42 |
fsmithred | but wildcard will cover you for upgrade to chimaera (I hope I spelled that right.) | 15:43 |
Vall | yep, my idea with '*-backports' is to set it permanently, including when/if I upgrade to future versions | 15:49 |
Vall | OK, done and working | 15:51 |
Vall | (apt-get update gives me no errors) | 15:51 |
ravencrow | good morning all | 17:35 |
furrywolf | heyas | 17:36 |
golinux | fsmithred: You did spell it correctly | 17:43 |
mason | It's certainly a chimerical spelling. | 17:51 |
Vall | mason: or chimaerical? ;-) | 18:19 |
mason | Vall: Very likely, yes. | 18:20 |
golinux | mason: Check for yourself: https://minorplanetcenter.net//iau/lists/MPNames.html | 18:21 |
mason | golinux: I have utter faith that Chimaera is how it's spelled, and it's a chimerical spelling indeed. | 18:23 |
golinux | Minor Planet #623 is Chimaera | 18:23 |
mason | golinux: So, is the plan to stick with minor planets, or is the field open to a range of planets from a range of places? | 18:24 |
furrywolf | we shouldn't pick names that people will constantly typo and wonder why their apt sources don't work... | 18:24 |
mason | golinux: And... Are those in the solar system, or does that include stuff we've seen further off? | 18:24 |
mason | furrywolf: Eh, I think it's a fine name. I'm just being difficult with related words that have alternate spellings. | 18:25 |
golinux | Probably some Brit named it. | 18:25 |
golinux | Minor planets all the way. nextime was an astronomer | 18:26 |
golinux | There are plenty of names there to choose from. | 18:27 |
mason | Ah, they are all from the Solar System: https://en.wikipedia.org/wiki/List_of_minor_planets | 18:27 |
golinux | Yes. | 18:27 |
mason | Maybe as we increase our ability to detect exoplanets we can expand outwards. :) | 18:27 |
golinux | furrywolf: One must be attentive to details to use Linux. | 18:28 |
golinux | We'll all be dead by then so useless to worry about. | 18:28 |
furrywolf | and one must not frustrated with the users joining #devuan to ask why their apt doesn't work. :) | 18:28 |
mason | furrywolf: We can point them to it being linked to libelogind0 =cough= | 18:29 |
golinux | Let's take this to #debianfork | 18:30 |
golinux | Just realized we're on #devuan | 18:30 |
mason | Oh, libsystemd.so.0 I mean. I thought we were relinking but of course we're not. | 18:30 |
gnu_srs | fsmithred: Is there a need for beowulf-backports, beowulf is not even released yet? | 18:52 |
mason | gnu_srs: Yes. It provides things folks might need if running Beowulf. | 18:52 |
mason | gnu_srs: Remember that Beowulf == Buster, and there are valid reasons to want Buster backports. | 18:53 |
fsmithred | gnu_srs, yes - new hardware needs newer kernel | 19:07 |
fsmithred | I even made a couple of live-isos with beowulf-backports kernel for that purpose. | 19:07 |
gnu_srs | I have to add that to sources.list then, working on eudev for beowulf. | 19:26 |
fsmithred | you shouldn't need to put eudev in beowulf-backports since beowulf hasn't been released yet. Just put the new version in beowulf if it's ready. | 19:38 |
fsmithred | gnu_srs, ^^^ | 19:38 |
gnu_srs | fsmithred: I meant upgrading my thest images to beowulf., sorry. The latest eudev is built for unstable for now. | 20:03 |
fsmithred | after I test slim from unstable, I can test eudev. Maybe 20 minutes. | 20:04 |
gnu_srs | I have an updated version not yet available. With a lot of eudev.{pre,post},{inst,rm} changes. Testing now. | 20:27 |
gnu_srs | fsmithred: Can I send the debs to you privately until it is built for unstable? | 20:28 |
fsmithred | yes | 20:28 |
fsmithred | me at gmail.com | 20:29 |
gnu_srs | fsmithred: Mailed them to you. | 20:36 |
fsmithred | gnu_srs, installs ok, removes libudev1 and boots ok. I didn't install the -dev package. | 21:25 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!