| Hydragyrum | from the homepage: This site can be mentioned as “dev dash 1 dot org” as it is reached via dev-one.org and dev-1.org. | 00:00 |
|---|---|---|
| Cenbe | thanx | 00:02 |
| golinux | Left here for reference an audio from 2015 from one of the VUAs: http://web.archive.org/web/20151103211726/https://devuan.org/ | 00:04 |
| UsL | I always pronounced it Dev one. But think of it as The vuan. A lone bearded mage, hacking away in a cottage. | 01:14 |
| aitor | hi | 01:17 |
| aitor | GNU IceCat web browser is available for devuan chimaera | 01:18 |
| aitor | https://www.gnuinos.org/screenshots/icecat.png | 01:18 |
| aitor | i debianized it this weekend taking the sources fron the git repo of savannah | 01:21 |
| aitor | https://git.savannah.gnu.org/cgit/gnuzilla.git | 01:21 |
| aitor | you can find the packages in the repo of gnuinos: | 01:23 |
| aitor | http://packages.gnuinos.org/gnuinos/pool/main/i/icecat/ | 01:23 |
| aitor | higher versions should be built in ceres | 01:26 |
| aitor | bye :) | 01:28 |
| UsL | that's pretty great. | 01:50 |
| onefang | "A lone bearded mage, hacking away in a cottage." I resemble that remark. lol | 03:13 |
| systemdlete | I so wish that the qemu devs would continually change the command line options. This would help to confuse me even more, which must be a good thing, right? | 07:11 |
| systemdlete | Seriously, where can I find docs for JUST qemu 3.1.0? There are docs galore on the web for qemu, but none of them seem to be for 3.1.0 | 07:12 |
| onefang | man qemu-* | 07:25 |
| onefang | I read various things on the web for qemu, then check the man pages to see what the version I'm actually running does. | 07:26 |
| onefang | tmux is just as bad, they always change some config option I'm using for each release. | 07:27 |
| systemdlete | I'm looking at those qemu-* man pages. That's the problem; they don't seem to fully document the program. | 07:28 |
| onefang | Also true. | 07:29 |
| systemdlete | vbox continually modifies and "enhances"(!?) their GUI, but do little to improve more basic issues. There are bugs for e1000 that date back 10 years, according to some. | 07:29 |
| systemdlete | So I was advised to run openwrt under qemu to see if it improves wireless performance any. So I am trying to do that. But I get errors and bugs and problems, and there doesn't seem to be any straightforward answers to anything. | 07:30 |
| systemdlete | I am only able to implement USB passthrough thanks to stumbling over an article that matched a few keywords, but was about something else entirely. | 07:30 |
| systemdlete | I'm not against changes. I'm not against updates, upgrades. I'm certainly not against security patches. | 07:31 |
| systemdlete | I just wish that devs would limit those changes to whatever their current interfaces are so they don't break everything else around them. | 07:31 |
| onefang | Last time I messed with qemu command line options, the Arch docs where mostly useful, followed by the man pages, then some experimentation. | 07:32 |
| systemdlete | They don't even finish updating docs for these changes, and that's really the problem. | 07:32 |
| systemdlete | Yeah, I notice Arch and ubuntu have more shrift about qemu than some others. The stackexchange sites are also marginally helpful in these cases, but there, people ask a question get a few responses then the thread goes dead for 2 years | 07:33 |
| systemdlete | dox, people, dox! | 07:33 |
| systemdlete | we need those | 07:33 |
| systemdlete | not everyone has the time or patience to read through their source code | 07:34 |
| debdog | here are docs for some qemu versions: https://qemu.weilnetz.de/doc/ | 07:34 |
| systemdlete | thanks, debdog | 07:34 |
| onefang | Lemme know if that works for you. | 07:34 |
| systemdlete | you know, the readthedocs.io for qemu has two "versions" -- "current" and "stable" | 07:34 |
| systemdlete | neither of them match the options in 3.1.0 | 07:35 |
| onefang | Coz I'm considering a siesta now. | 07:35 |
| systemdlete | Whoa! debdog, they have all of the docs by release! nice | 07:35 |
| debdog | well, at least one can figure out which options are available for each release. | 07:37 |
| systemdlete | the only problem is that when I go to 3.1, and open the html doc, it shows it is for 3.0.92 | 07:37 |
| systemdlete | and the page looks identical to others I have found that purport to be for 3.1 | 07:37 |
| debdog | yeah, I am not entirely familiar with qeum's versioning scheme. I just pck the closest one | 07:38 |
| debdog | and that worked so far | 07:39 |
| systemdlete | idk... I really don't have many problems running stuff under vbox these days. I mean, they also screw around with stuff far too much. But overall, things continue to work from release to release. It is rare that upgrades cause devastating damage for me, and I do run a few dozen different VMs in vbox. | 07:39 |
| systemdlete | I felt it was fair to give this a go, though, so I am trying very hard to make this all work. | 07:39 |
| debdog | IDK, do not have much experience with different VMs. I just use qemu because I started with it back then | 07:41 |
| systemdlete | you mean different virtualizers? | 07:43 |
| systemdlete | I'll go to #openwrt and ask them for a "template" for qemu 3.1.0 | 07:44 |
| systemdlete | I'm guessing someone there probably has done this | 07:44 |
| systemdlete | (their docs are outdated and also deal with older qemu versions) | 07:44 |
| debdog | virtualizers, right | 07:45 |
| armouredheart | Does anyone know of a resource (such as a book) that defines the core, consistent language features in C? I want to be sure any software I write can be compiled on any C compiler or hardware that may exist in the future by reducing dependencies as much as possible, especially dependency on a particular (beurocratically defined) ISO/ANSI standard. | 13:56 |
| buZz | armouredheart: how about K&R's C book? | 13:59 |
| buZz | this one ; https://en.wikipedia.org/wiki/The_C_Programming_Language | 13:59 |
| buZz | pretty much the #1 resource about C | 13:59 |
| buZz | they wrote it during implementing the language the first time | 13:59 |
| armouredheart | sweet thanks | 14:00 |
| buZz | i really liked reading it | 14:01 |
| used____ | C ANSI is different from most other standards, it was defined after the de facto industry standard C was in use, and simply followed that 99%. | 17:47 |
| systemdlete | Not sure if my last messages went through, so here it is again: | 18:49 |
| systemdlete | I want to prevent a certain module from EVER autoloading. | 18:49 |
| systemdlete | So I added "blacklist <modulename>" to my /etc/modprobe.d/blacklist.conf (I had to create the file). Then I ran update-initramfs -u. | 18:49 |
| systemdlete | Is this sufficient to achieve my goal? | 18:49 |
| used____ | Yes, but in your current session, issue: sudo rmmod $themod; if loaded | 18:53 |
| systemdlete | I did rmmod it. Troulbe is, soon it was autoloaded again anyway | 18:55 |
| used____ | It should not reload once it's in blacklist | 18:56 |
| systemdlete | even before reboot? | 18:56 |
| used____ | Yes. Iirc. | 18:56 |
| systemdlete | ok | 18:56 |
| systemdlete | that seems to be working so far... thanks | 19:00 |
| systemdlete | used____: That is definitely working. I've been running since I last wrote here and blacklist is working. Thanks. | 19:22 |
| av6 | here's another way to make sure modules don't load: https://linux-audit.com/kernel-hardening-disable-and-blacklist-linux-modules/ | 21:47 |
| av6 | "install pcspkr /bin/true" | 21:48 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
