| unixbsd | It would be great if the bugs to format of mkfs.ext3 amd64 works in some years. it fails to format on disks. i386 works but amd64 fails. | 12:16 |
|---|---|---|
| unixbsd | Wireless slow, ultra slow bug: also the wlan of devuan ascii and buster sometimes does not work anymore on devuan. On debian, it looks a bit more stable. | 12:17 |
| unixbsd | fsck.xfs does not call xls_repair. another bug. | 12:18 |
| unixbsd | (optional) the stable vi, less or elvis aren't anywhere by default in debian and devuan. su needs today '-', which is not necessary. | 12:20 |
| unixbsd | The rest is ok and running. | 12:21 |
| unixbsd | another bug: shutdown never happens. this is also pretty new. shutdown may hang time to time. | 12:22 |
| unixbsd | tmux does not work either by default: "tmux: need UTF-8 locale (LC_TYPE) but have ANSI_X3.4-1968" <- this is another bug found. | 12:24 |
| * man_in_shack grumbles | 14:09 | |
| man_in_shack | need to find out what's hanging my system | 14:11 |
| unixbsd | another bug..." apt-get install gcc make " will not install <stdio.h>. you forgot it in the deb. But, apt-get clang will install the right lib bin ;) | 19:10 |
| fsmithred | unixbsd, you get stdio.h with libc6-dev. If you did 'apt-get install build-essential' you would have gotten that along with gcc and make and a couple other things. | 19:16 |
| Wonka | $ dpkg -S /usr/include/stdio.h | 19:16 |
| Wonka | libc6-dev:amd64: /usr/include/stdio.h | 19:16 |
| Wonka | well, fsmithred said it better already... slow me. | 19:16 |
| fsmithred | and any bug reports on those packages should go to debian. Pretty sure we don't fork any of those. | 19:17 |
| unixbsd | this is ubuntu, gcc should or *must* had link to the lib stdio.h. This is very important!. stdio.h is ultra important. "apt-get install build-essential" | 19:18 |
| fsmithred | what "this" is ubuntu? | 19:18 |
| unixbsd | build-essential is a way to install a loooot of junk food (libs) and non necessary for a compilation method. For simplicist compilation, in like clang deb (it has stdio) i.e. link, apt-get install gcc should be possible by default. | 19:21 |
| brocashelm | yeah, wtf is "ubuntu"? lol | 19:25 |
| unixbsd | ubuntu method is to advise to install all web to compile a little hello world. | 19:27 |
| fsmithred | is it possible to use gcc without stdio.h? | 19:28 |
| fsmithred | I'm gonna guess that it is possible, and that's why it's not a hard dependency for gcc. | 19:28 |
| fsmithred | oh, the other way to get stdio.h is to install gcc and do not exclude Recommends. | 19:29 |
| jeha2 | hi, does someone know where to fine-tune xfce4/devuan powermanagement? | 19:30 |
| fsmithred | which is the default setting | 19:30 |
| fsmithred | so one would have to go out of their way not to get stdio.h when installing gcc | 19:30 |
| unixbsd | well, developers can try to install gcc and to compile something without stdio.h. good luck! It may still be possible somehow. | 19:30 |
| fsmithred | jeha2, you found the power manager in the settings menu? | 19:30 |
| jeha2 | fsmithred, yes. but suspend-to-ram does not work. suspend-to-disk works fine. pm-utils suspend-hybrid works find. i want to tell xfce to use suspend-hybrid instead suspend-to-ram. | 19:32 |
| fsmithred | I'm surprised that suspend doesn't work. | 19:34 |
| fsmithred | Not surprised if you're just complaining about the lid. | 19:34 |
| fsmithred | you have to select suspend from the menu or else do stuff with acpi to make it automatic | 19:35 |
| golinux | unixbsd: You do know that mixing ubuntu pkgs into devuan is a recipe for disaster, right? | 19:37 |
| fsmithred | I don't think that was the issue | 19:37 |
| fsmithred | it was just a reference to bloat | 19:37 |
| fsmithred | I guess the real issue is that excluding bloat can sometimes exclude something you want. | 19:38 |
| jeha2 | ok, i guess you're right. i think with acpid/pm-utils i could work | 19:39 |
| fsmithred | look on the forum. It's been discussed at least a couple of times, and you can find sample scripts. | 19:39 |
| fsmithred | btw, in chimaera, lid close does trigger suspend. I don't know what they did to fix that. | 19:40 |
| brocashelm | suspend/hibernate have never worked for me on xfce | 19:41 |
| fsmithred | even from the menu? | 19:42 |
| brocashelm | suspend makes it impossible for me to restore my session and hibernate immediately wakes up again | 19:42 |
| brocashelm | yes | 19:42 |
| fsmithred | maybe something is missing | 19:43 |
| brocashelm | and i'm not even using a laptop; the os just stalls | 19:43 |
| brocashelm | i can only do a hard shutdown to resolve this | 19:43 |
| brocashelm | i don't use any display managers; i use tty to log in | 19:43 |
| jeha2 | fsmithred, thanks. i have to confess i forgot about the devuan forum. i was using only google... bye bye | 19:46 |
| fsmithred | good luck | 19:46 |
| unixbsd | brocashelm: tty coool. me too, you may find or use pibox.c ... a cool login manager for autologin: https://termbin.com/b067 | 19:48 |
| brocashelm | unixbsd: thanks, i'll check it out | 19:54 |
| unixbsd | startx is quite cool way still. In BSD, this is still a retro method, many use it still today. By the way, does wayland have startx still... | 19:57 |
| phogg | unlikely since it's not X | 20:08 |
| unixbsd | phogg: well, we will have to learn how to use Wayland soon or later. even without startx if not there. | 20:22 |
| luser978 | anyone running android studio on beowulf? it's slow here but it swaps, only 2GB ram. how much ram makes it happy? | 20:56 |
| fling | How to log init to syslog? | 20:58 |
| gnarface | luser978: try out zram swap | 21:05 |
| gnarface | fling: there's some package that makes it easy... boot[something] | 21:05 |
| gnarface | fling: bootlogd, i think | 21:05 |
| gnarface | fling: (possibly not the only way) | 21:06 |
| gnarface | luser978: (i don't actually know but using zram block devices for swap instead of your disk is turning out to be a huge boon to systems with ~2GB fixed ram) | 21:07 |
| gnarface | luser978: (and no, i know. you'd think it'd be slower, and in the 90's it would have been, but it's really not anymore) | 21:08 |
| fling | gnarface: on gentoo there is logger option in rc.conf | 21:33 |
| fling | it writes to /var/log/rc.log which can then be read with syslog hmmm | 21:34 |
| gnarface | fling: my assumption is that it's basically the same thing; a userspace daemon that launches immediately to catch dmesg into a boot log | 21:35 |
| gnarface | fling: been a while since i used gentoo but my experience is that they'd have made it pretty transparent what the name is | 21:36 |
| fling | but dmesg is logged anyway hmm | 21:37 |
| gnarface | fling: is it? | 21:37 |
| gnarface | fling: i don't know for sure that it is not | 21:38 |
| fling | sure kernel messages will sit and wait for syslog | 21:38 |
| gnarface | fling: what is it you're trying to capture, exactly? afaik to get anything earlier than dmesg you will need a serial cable | 21:38 |
| fling | output of init, different initscripts, the stuff you will see in boot console | 21:39 |
| gnarface | fling: check /var/log/daemon.log - the default log location for daemons (make sure you actually installed rsyslogd and i strongly recommend logrotate too) | 21:39 |
| fling | I'm running devuan in lxd, no need for serial | 21:39 |
| fling | What is writing /var/log/daemon.log ? | 21:43 |
| gnarface | fling: uh... rsyslogd, i think | 22:02 |
| gnarface | fling: same with most the logs in /var/log/ | 22:02 |
| fling | not, what I want then. | 22:03 |
| gnarface | fling: it's not the only option though, and some stuff (like apache) logs for itself | 22:03 |
| gnarface | fling: and /var/log/boot isn't it, either? | 22:04 |
| fling | I don't have /var/log/boot | 22:04 |
| gnarface | hmmm | 22:05 |
| fsmithred | install bootlogd to get /var/log/boot | 22:06 |
| gnarface | you might also need to set BOOTLOGD_ENABLE=yes in /etc/default/bootlogd? | 22:07 |
| fling | I have it in another container though | 22:07 |
| fling | but the log says nothing has been logged yet | 22:08 |
| gnarface | fling: did you check /etc/default/bootlogd? | 22:08 |
| fling | if you are still eseing this message your current init system might not write bootup messages to the system console at all | 22:08 |
| fling | I don't have /etc/default/bootlogd | 22:08 |
| fling | hmmm | 22:08 |
| gnarface | fling: check /etc/default/rcS, too | 22:09 |
| gnarface | fling: /etc/default/bootlogd should have been installed with the bootlogd package afaik though. if it wasn't, check /usr/share/doc/bootlogd/ or /usr/share/doc/bootlogd/examples/ or something like that | 22:09 |
| gnarface | not sure why i have /var/log/boot here without bootlogd... | 22:10 |
| gnarface | but i'm on ceres | 22:10 |
| gnarface | so who knows | 22:10 |
| fsmithred | same here on beowulf | 22:10 |
| fling | atleast I can see messages in console | 22:10 |
| gnarface | i had really assumed it's rsyslogd doing it | 22:10 |
| gnarface | i mean the list of usual suspects is not long here | 22:10 |
| gnarface | this isn't systemd | 22:10 |
| gnarface | there isn't much to it other than that rcS script and what's in /etc/init.d/ | 22:11 |
| gnarface | maybe your init scripts just don't have much to say? | 22:11 |
| fling | I have no /etc/default/rcS | 22:11 |
| gnarface | hmmm | 22:11 |
| gnarface | now i'm wondering if your post-install hooks didn't fire right or something | 22:11 |
| gnarface | your install is starting to seem suspect | 22:11 |
| gnarface | are you using a weird shell? | 22:12 |
| gnarface | even dash can cause compatibility issues from time to time | 22:12 |
| gnarface | bashisms sneak into startup scripts occasionally when they're not supposed to | 22:12 |
| fling | I have no idea :D | 22:12 |
| fling | the idea is to read boot log with syslog-ng and send it to a remote | 22:14 |
| gnarface | well, mabye the choice of syslog-ng over rsyslogd is actually the difference between your system and ours | 22:16 |
| gnarface | but fyi rsyslogd can remote log over the network, too | 22:16 |
| gnarface | i don't remember what my issue was with syslog-ng. all i know is rsyslogd doesn't do it | 22:17 |
| gnarface | (or does do it, as the case may be... maybe this was the issue) | 22:18 |
| fling | init/rc/whatever writes boot log from init start and to login prompt | 22:18 |
| fling | syslog daemon can be configured to use this log as a source | 22:18 |
| fling | then syslog can write it to messages or send it to a remote | 22:18 |
| fling | it does not matter if you use rsyslogd or syslog-ng | 22:18 |
| fling | like this -> file("/var/log/rc.log" program-override("rc") ); | 22:20 |
| fling | rc_logger="YES" in /etc/rc.conf makes /var/log/rc.log to appear on gentoo hmmm | 22:21 |
| gnarface | fling: do you have the "initscripts" package? | 22:22 |
| fling | yes | 22:22 |
| gnarface | fling: according to my sources the /etc/default/rcS file should have been in that package. what happens if you reinstall it? | 22:22 |
| fling | how to reinstall it? | 22:23 |
| gnarface | fling: apt-get update && apt-get --reinstall install initscripts | 22:23 |
| gnarface | fling: if it says you need to add --force then add it | 22:24 |
| fling | now I have it! | 22:24 |
| gnarface | sweet | 22:24 |
| gnarface | what was the other one? oh, bootlogd | 22:24 |
| gnarface | if this happened to that package it probably happened to others. your install is suspect, though i can't be sure what went wrong. | 22:25 |
| fling | also reinstalled bootlogd | 22:26 |
| gnarface | you could probably write a easy 4-line shell script to loop through your package list and reinstall all of them though | 22:26 |
| fling | Does it require something in inittab? | 22:26 |
| gnarface | not as far as i can tell | 22:26 |
| gnarface | though ... i mean | 22:26 |
| gnarface | you didn't take out all the gettys did you? | 22:27 |
| gnarface | i don't test a lot without them | 22:27 |
| gnarface | so if you're missing them too all bets are off | 22:27 |
| fling | looks like I have all the ttys commented out | 22:28 |
| gnarface | packages add themselves to sysvinit startup typically by 1) adding a shell script to /etc/init.d/ and 2) adding appropriately-named kill/start symlinks to the /etc/rc?.d/ directories | 22:28 |
| gnarface | typically nothing changes the inittab | 22:28 |
| gnarface | and typically i don't mess with it unless i'm connecting a serial console | 22:28 |
| gnarface | that's assuming you are actually using sysvinit which i'm now also skeptical of | 22:29 |
| gnarface | if you've replaced it with an out-of-repo openrc then the gentoo documentation actually may be more relevant | 22:30 |
| fling | how to check what I'm using? :P | 22:31 |
| gnarface | dpkg -l |grep openrc | 22:31 |
| fling | I only have devuan repos | 22:31 |
| gnarface | maybe | 22:31 |
| fling | empty ^ | 22:31 |
| gnarface | ok, you're probably fine then but you should still try to figure out why your config scripts didn't get installed | 22:31 |
| gnarface | i mean nothing really works without them (not even xorg, all the time, despite what they say) | 22:32 |
| fling | maybe because they were ascii before hmm | 22:32 |
| fling | What am I using instead of openrc? | 22:38 |
| fsmithred | sysvinit is the default | 22:38 |
| fling | And how can I see console without any tty in inittab? :S | 22:38 |
| gnarface | fling: i think you don't, but i'm not sure | 22:39 |
| gnarface | fling: the tty sorta is the console | 22:40 |
| fling | I mean I see the console output but I don't see where is it coming from looking into inittab. | 22:41 |
| fsmithred | 1:2345:respawn:/sbin/getty 38400 tty | 22:42 |
| fling | ^ going to uncomment this one | 22:42 |
| fsmithred | who commented it? | 22:42 |
| fling | whoever maintains lxd image | 22:43 |
| fsmithred | oh | 22:43 |
| gnarface | fling: oh, you didn't even make this image? | 22:54 |
| gnarface | fling: that explains a lot | 22:55 |
| fling | I'm using default images, everything works just fine except for bootlogd :> | 22:55 |
| fsmithred | does a container actually boot? | 22:56 |
| fling | yes | 22:57 |
| gnarface | fling: well, or so it probably seemed on the surface, the omission of the config files you were missing seems like evidence of deeper breakage somewhere, possibly in image creation | 22:57 |
| gnarface | fling: it indicates the potential for other stuff to be broken less obviously elsewhere | 22:57 |
| fling | but the containers are old and were created from random ascii images in the past | 22:57 |
| fling | or converted from debian | 22:57 |
| gnarface | fling: well, it seems like someone tried to solve a conflict with one config file by omitting all the config files, and probably omitted a little too much | 22:58 |
| fling | But I updated a lot since then | 22:58 |
| fling | And run dist-upgrade | 22:58 |
| gnarface | yea, that's weird | 22:58 |
| gnarface | but one reinstall got you your /etc/defaults/rcS file back, no? | 22:58 |
| fling | I never noticed missing configs before. | 22:59 |
| gnarface | so maybe ... hmm, but what else could have caused it? | 22:59 |
| fling | Yes, I have /etc/defaults/rcS now | 22:59 |
| gnarface | unsolved mysteries | 22:59 |
| fling | I have no idea, I'm using zfs, files don't just disappear. | 22:59 |
| gnarface | well i'd put my money on it being something to do with the container, but it's not clear whether it's an accident or a mistake | 23:01 |
| fling | Where can I see the script used for creating the images? | 23:03 |
| fling | Maybe it contains an obvious mistake or something. | 23:03 |
| gnarface | fling: the lxc images? i don't know... are they even part of the distro or did the lxc team make them? | 23:22 |
| fling | gnarface: lxd images. I thought devuan people maintain them. | 23:26 |
| gnarface | fling: oh, maybe they do | 23:27 |
| gnarface | fling: if there's scripts they'd be in the gitlab | 23:27 |
| fling | gnarface: you just run `lxd launch images:devuan/ascii my-container` and it crates new container using the official image | 23:29 |
| fling | lxc launch ^ | 23:29 |
| gnarface | hmmm | 23:31 |
| gnarface | maybe there is some option to make it not ditch all the config files? | 23:32 |
| gnarface | lol i don't know | 23:32 |
| fling | haha | 23:32 |
| fling | Btw how to install lxd on devuan? | 23:33 |
| gnarface | lxc or lxd? | 23:40 |
| gnarface | they're both packages | 23:40 |
| fling | lxd uses lxc, criu, lxcfs, etc | 23:41 |
| fling | it all depends on how it is packaged | 23:41 |
| gnarface | i suspect that what you're looking for is in the lxc package, and the lxd package refers to something else in debian | 23:42 |
| gnarface | oh, no it doesn't but just isn't present | 23:42 |
| gnarface | lxde comes up in searches for it | 23:42 |
| fling | does this mean there is no lxd in devuan? | 23:43 |
| gnarface | here, run this command: apt-cache search ^lxc | 23:43 |
| fling | I see lxc and I don't see lxd ;< | 23:44 |
| gnarface | are you sure lxd is not in the lxc package? | 23:46 |
| fling | it should not be there | 23:46 |
| gnarface | did you ever try installing the lxc package? | 23:46 |
| fling | no but I will try later | 23:47 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!