tuxd3v | ceres just apeared in the expanse tv series :) | 02:04 |
---|---|---|
merzbird | does anyone know how i can stop the hang on startup... 'lock on ifup, already configured' & 'starting mta' adds an extra 4-5 minutes to boot unneccessarily | 04:42 |
mason | merzbird: The lock on ifup sounds like either you have it configured twice, or you have /etc/network/interfaces and Network Manager both trying, or something along those lines. | 04:43 |
merzbird | mason oic | 04:43 |
fling | How to switch to netifrc? | 10:23 |
gnarface | never heard of it | 10:25 |
fling | it is a networking initscript for openrc :> | 10:25 |
gnarface | oh | 10:27 |
gnarface | sorry, dunno, but it's probably not hard | 10:27 |
fling | sure | 10:28 |
user123456789 | hello, is there anyone online that can help me with something? | 11:08 |
user123456789 | it's in regards to lqxt, i wanted to know if there is a way to reset the theme from terminal or change it via terminal with a command, i switched it to one and it messed up my GUI | 11:10 |
gnarface | if you just uninstall the one that is selected, it'll most likely fall back to the default | 11:15 |
gnarface | i think | 11:15 |
gnarface | if i'm wrong you can always install it again | 11:15 |
user123456789 | it came with devuan | 11:15 |
gnarface | lxqt probably has a config file though | 11:15 |
user123456789 | its called bb10dark | 11:16 |
gnarface | do you have a small home directory? try: grep -rni 'bb10dark' . | 11:16 |
user123456789 | also thanks for replying | 11:16 |
gnarface | (include the ".") | 11:16 |
user123456789 | i get a bunch of weird text | 11:17 |
gnarface | file names, line number, matched text | 11:18 |
gnarface | or matched line i mean | 11:18 |
user123456789 | .config/lxqt/lxqt.conf:5:style=bb10dark but it shows this before it | 11:18 |
gnarface | there you go | 11:18 |
user123456789 | so how do i change it? | 11:18 |
user123456789 | vim into the config | 11:18 |
user123456789 | and change the name of theme? | 11:18 |
gnarface | that's [file name]:[line number]:[line contents] | 11:18 |
gnarface | yea, should work, then restart lxqt | 11:18 |
user123456789 | gotcha | 11:19 |
user123456789 | i'll try | 11:19 |
user123456789 | thanks mate | 11:19 |
gnarface | good luck | 11:19 |
AkhIL[m]1 | ok. there is a bug report https://www.devuan.org/gitlab-issues/devuan-packages.lightdm.2.html | 11:22 |
user123456789 | sorry im new to linux how to save, i do cntrl+o but it doesnt save when i check back | 11:28 |
gnarface | doh, he should have used nano i guess | 11:32 |
user123456789 | i was able to change the theme, thanks for the help! I appreciate it | 11:38 |
gour | have problem booting devuan on my netbook - separate /boot & /home, bios/gpt, xfs fs. installer quits without errors, tried re-installing from within rescue mode, chrooting into root, manually updating and re-installing grub, but still, when booting i get "OS not found". tried uefi install since my netbook had ocaccionally problem with bios/gpt, but eufi installer quits when installing grub - can't add boot-xyz entry or something...any hint? | 13:27 |
hagbard_ | /boot isn't on xfs, is it? | 13:36 |
daemon | I sometimes find with pretty much all os's except windows, sticking the 'base' operating system on the native fileformat (extfs in this case) and then partitioning the drive so that the latter half can be use for zfs or lvm or ... works quite well | 13:45 |
daemon | then you can mount heavy use partitions and such after the os is working | 13:45 |
gour | daemon: ok, will try that for the experiment | 13:51 |
daemon | ^ as an extension of that always install the minimal config | 13:58 |
Anonical_juju | hello | 14:36 |
Anonical_juju | I still haven't got wireless connections working yet. Anyone want to help with fixing it? | 14:37 |
Anonical_juju | I'll be your frend | 14:38 |
Anonical_juju | I went and got network-manager and connman but still don't know what to do. Also, I can get Bluetooth to show up so I know the card is at least in part working | 14:43 |
Anonical_juju | come on fsmithred give another noob a break | 14:55 |
fsmithred | iwlist might give you some info about the wireless | 14:56 |
fsmithred | iwlist wlan0 scan | 14:57 |
fsmithred | as root | 14:57 |
fsmithred | and replace wlan0 if that's not the right name | 14:57 |
fsmithred | rfkill might tell you something, too | 14:58 |
Anonical_juju | interface doesn't support scanning : Network is down | 14:59 |
Anonical_juju | Then why did I have the IRC Bart? Why did I have the IRC? | 14:59 |
fsmithred | ip command can bring it up | 14:59 |
fsmithred | you're using that computer now? | 15:00 |
fsmithred | talking to me? | 15:00 |
Anonical_juju | ID 2 Type wlan Device phy0 Soft unblocked Hard blocked | 15:00 |
fsmithred | is there a physical switch to turn the wireless on/off? | 15:02 |
Anonical_juju | yes, and an unreliable one at that | 15:02 |
fsmithred | I think hard blocked means the switch is off | 15:02 |
Anonical_juju | but it's pushed to the right and the WiFi LED is lit | 15:02 |
Anonical_juju | lit but amber means on but no connection I think | 15:03 |
fsmithred | try off/on | 15:03 |
fsmithred | I have to reboot | 15:05 |
fsmithred | back in a minute | 15:05 |
Anonical_juju | so the switch up front only changes the LED | 15:09 |
Anonical_juju | I remember back in the day fixing this kind of thing was all terminal driven and that part of the problem was wicd refuses to launch as root | 15:10 |
Anonical_juju | beyond that I don't have a clue what I'm supposed to be doing | 15:11 |
fsmithred | you can unblock a soft block with rfkill, but not a hard block if it's blocked at the switch | 15:11 |
fsmithred | does the wireless work with any operating system? | 15:11 |
Anonical_juju | good question | 15:12 |
Anonical_juju | I'd have installed windows if I knew it was going to come up | 15:12 |
fsmithred | maybe ubuntu or mint iso would help for testing | 15:12 |
fsmithred | if it's dead and you need wirless, you can get a usb dongle for just a few dollars | 15:13 |
Anonical_juju | I can't boot from USB any wya | 15:13 |
fsmithred | plop boot loader FTW | 15:13 |
Anonical_juju | I would rather swap in another mini PCI card | 15:14 |
fsmithred | yeah, that could work | 15:14 |
fsmithred | you mean a wireless card? | 15:14 |
Anonical_juju | but I think maybe the supervisor password on the BIOS might prohibit this configuration that I have | 15:14 |
fsmithred | there must be a way to reset that | 15:14 |
fsmithred | is it old enough to have a jumper switch to reset bios? | 15:15 |
Anonical_juju | no, well, it wants me to solder wires onto pads to reset it | 15:15 |
Anonical_juju | I was thinking of launching a program that guesses default supervisor passwords, once I had an OS | 15:16 |
fsmithred | are you the one who set the password? | 15:17 |
Anonical_juju | I don't think so | 15:17 |
fsmithred | I don't have any more ideas. | 15:19 |
Anonical_juju | how do I launch network-manager? | 15:20 |
fsmithred | set it in the desktop's application autostart | 15:20 |
fsmithred | it'll be in the tray | 15:20 |
fsmithred | right-click to edit connections | 15:21 |
Anonical_juju | wicd is in control of that atm | 15:21 |
fsmithred | you need network-manager and network-manager-gnome | 15:21 |
fsmithred | remove wicd | 15:21 |
Anonical_juju | oh I don't have the GNOME giu | 15:22 |
Anonical_juju | GUI* | 15:22 |
fsmithred | that supplies the tray applet | 15:22 |
Anonical_juju | I'd need a wired connection to get it | 15:22 |
Anonical_juju | hello devzuans | 18:45 |
Anonical_juju | I still have no wife fi | 18:45 |
Anonical_juju | and since I uninstalled wicd (got in my way) commands like rfkill disappeared as well | 18:46 |
Anonical_juju | I apt installed rfkill again but it still claims to be missing and now I'm stuck | 18:46 |
fsmithred | try /usr/sbin/rfkill | 18:47 |
fsmithred | or try 'su -' to become root | 18:48 |
Anonical_juju | I will have a look | 18:48 |
fsmithred | root's path is different depending on how you get there | 18:48 |
Anonical_juju | yeah it's in usr, sbin | 18:50 |
Anonical_juju | is there any way I can re-enable it? | 18:51 |
Anonical_juju | other commands have not been working either (ipconfig?) but they can wait | 18:52 |
fsmithred | see the release notes for how to deal with it | 18:53 |
Anonical_juju | beuwolf's release notes? or erm rfkill's? | 18:54 |
debdog | https://files.devuan.org/devuan_beowulf/Release_notes.txt | 18:54 |
fsmithred | thankd, dd | 18:55 |
Anonical_juju | which part of this am I supposed to read? | 18:57 |
fsmithred | the part about changes in su | 18:58 |
fsmithred | should be near the beginning in What's new | 18:58 |
Anonical_juju | are you saying that su is not enough to access commands like rfkill? because I was using it earlier and it worked then | 18:59 |
Anonical_juju | su is not in etc/default/ | 19:01 |
fsmithred | create it | 19:01 |
fsmithred | man su | 19:01 |
fsmithred | do the following experiment before you change anything | 19:02 |
fsmithred | su | 19:02 |
fsmithred | echo $PATH | 19:02 |
fsmithred | exit | 19:02 |
fsmithred | su | 19:02 |
fsmithred | no | 19:02 |
fsmithred | sorry | 19:02 |
fsmithred | su - | 19:02 |
fsmithred | echo $PATH | 19:02 |
fsmithred | you will see they are different | 19:02 |
Anonical_juju | usr/local/bin... usr/local/sbin... what am I supposed to have learned? | 19:06 |
Anonical_juju | oh, that regular su is ded as rfkill won't launch | 19:06 |
Anonical_juju | still says hard blocked in rfkill :( | 19:07 |
fsmithred | try the full path to the command | 19:07 |
fsmithred | /usr/sbin/rfkill | 19:07 |
fsmithred | or use 'su -' which includes the sbins in root's path | 19:07 |
Anonical_juju | I will do that from now on | 19:08 |
fsmithred | or modify /etc/default/su to restore old behavior | 19:08 |
Anonical_juju | thanks for the info | 19:08 |
Anonical_juju | I might do that yet, I don't understand the reasons for it's change | 19:08 |
Anonical_juju | rfkill is still saying hard blocked and rfkill unblock all didn't mend it | 19:09 |
fling | How to keep syslog-ng running on shutdown? | 19:10 |
Anonical_juju | gonna go anyway for now thanks for the help | 19:10 |
gnarface | fling: it should shutdown on shutdown by default, i thought.... | 20:12 |
gnarface | fling: check the symlinks? | 20:13 |
gnarface | fling: there's always rsyslog. i really don't think there's anything wrong with it that can't be explained by brazen libel. | 20:13 |
Xenguy | I understand the difference between 'su' and 'su -', but I've always been doing it the latter way, since forever. I don't see how it's a recent change, but whatever, it's muscle memory to just do 'su -' for me. | 20:16 |
fling | gnarface: is there a symlink to remove to prevent it from going down on shutdown? | 20:20 |
fling | I want to keep it running | 20:20 |
fsmithred | Xenguy, the recent change is that su got moved from the shadow package to util linux, and they changed the way it behaves. It used to be that su gave you root's path, but now it keeps the user's path. | 20:25 |
fsmithred | 'su -' is still the same. Gives you root's path and changes you to root's home | 20:26 |
hagbard_ | There's also a configuration to get the old behaviour back. | 20:28 |
gnarface | fling: that seems like a mistake to me, but yea, there is. run this command: ls -l /etc/rc?.d/*syslog* | 20:28 |
gnarface | fling: (there's some tools available to automate the manipulation of these symlinks, but it's really not a complicated task to do by hand) | 20:29 |
hagbard_ | Xenguy: you can set ALWAYS_SET_PATH yes in /etc/default/su | 20:32 |
hagbard_ | Speaking of su, here's a gimmick for .bashrc so that su can be used like sudo: suc() { su -s /bin/bash -c "$(printf "%q " "$@")"; } | 20:34 |
hagbard_ | like "suc !!" to execute the previous command as root | 20:34 |
fling | gnarface: which one to look there for? | 20:35 |
fsmithred | fling, update-rc.d if you like commands, sysv-rc-conf if you like arrows and spacebar. | 20:37 |
fling | fsmithred: I have sysv-rc-conf | 20:37 |
fling | I have 7 symlinks | 20:38 |
gnarface | fling: "K" means stop on those runlevels, and "S" means start on those runlevels | 20:38 |
fling | gnarface: thanks! :> | 20:38 |
gnarface | fling: the numbers used to be order-of-operations, but they're preempted by the LSB tags in the scripts themselves | 20:38 |
gnarface | fling: (the "K" stop operation will preempt the LSB tags in return though) | 20:39 |
gnarface | fling: there's a comment block in the heads of all the scripts themselves that's actually parsed for dependency-chain type behavior, but its a feature that was added after the symlinks and you usually won't have to mess with them | 20:39 |
fling | fsmithred: sysv-rc-conf only shows X everywhere but how to distinguish which of them starts and which stops in sysv-rc-conf ? | 20:40 |
fling | gnarface: going to just drop some symlinks there, thanks :> | 20:40 |
fsmithred | X means it runs in that runlevel | 20:41 |
fsmithred | no X means it does now | 20:41 |
fsmithred | not | 20:41 |
fling | ah | 20:41 |
fling | and which number means what? | 20:41 |
fsmithred | the numbers are the runlevels | 20:42 |
fsmithred | 2-5 are usually the same | 20:42 |
gnarface | fling: runlevel 2 is the default. the others are meaningless in the default configuration on debian derivatives; they're reserved for your own use | 20:42 |
fling | what about 0,1 and 6 ? | 20:42 |
gnarface | oh they probably do something, S probably does something, but it's not like redhat where it does something you care about | 20:43 |
gnarface | the system will boot into 2 and only ever use 2 unless you tell it otherwise | 20:43 |
gnarface | and if your symlinks contradict the LSB headers, you'll get a warning in the boot up messages but that's it. its harmless | 20:45 |
fsmithred | 0 is halt, 6 is reboot | 20:45 |
fling | ok I used X in every runlevel for syslog-ng | 20:47 |
fling | all my symlinks are now S in every runlevel | 20:47 |
fling | but it still goes down during a shutdown/reboot | 20:47 |
fsmithred | why should it do otherwise? | 20:48 |
fsmithred | or | 20:48 |
fsmithred | how could it do otherwise? | 20:48 |
fling | with openrc on gentoo I could list the services I don't want to stop in a config file | 20:49 |
fling | openrc will not stop the initscripts of these services then | 20:49 |
fling | idk how do the same on devuan | 20:50 |
fsmithred | sounds like it could cause problems | 20:50 |
onefang | By definition, when you shutdown or reboot, EVERYTHING goes down one way or another. lol | 20:51 |
fsmithred | yeah, I'm wondering how those things come back up | 20:51 |
fling | onefang: yes I just want to be able to tell init to not touch certain services on reboot/shutdown | 20:52 |
gnarface | fling: just fyi i'm pretty sure if you succeed at doing this you basically cause the shutdown process to hang on unmount, or you cause it to force shutdown without cleanly unmounting. | 21:26 |
gnarface | fling: (*decent* chance of log data and/or filesystem corruption - good way to fire-test your filesystem's journal recovery features i guess though...) | 21:26 |
rodper451 | hello! does QEMU work alright in devuan? | 23:57 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!