freenode/#devuan/ Wednesday, 2018-07-11

aitorhi, mtnman, i was greeting to g4560n, we are in the #devuan-mx channel00:25
mtnmanwhat is -mx for?00:30
g4570nes for spanish is abandoned, mx is now uses for spanish comunity00:31
mtnmang4570n my spanish is poor so i will not be joining but gracias for the invitacion.00:50
g4570nde nada :)00:51
mtnmananyone know the default password for user devuan on the arm images?01:02
mtnmannevermind... logged in as root and will change password.01:03
mtnmanah! there is no user devuan01:04
golinux_mtnman: Have you looked at this?
mtnmani did read that a few days ago01:49
mtnmangood news is i now have two machines running devuan01:51
mtnmanthe trickiest part was getting usb networking running on the beagebone without a monitor01:53
* mtnman is almost ready to upgrade from live boot to disk installation.01:54
mtnmani enabled ip forwarding on gateway (box1) and did "route add default gw {address-of-gateway-box} on box2 but cannot access internet from box2. did i miss something?02:19
crimson_kingHi folks. On a fresh ASCII install, I tried to git clone a github repository via ssh but it failed with "permission denied(public key)". Since this worked on a fresh Debian Stretch install, I'm assuming it is related to Devuan somehow. More info: .ssh folder is drwx------, while private keys are -rw------- and public keys are -rw-r--r--03:28
Acaciacrimson_king: it most likely means your public key isn't in the list of allowed keys in the ssh server03:29
crimson_kingAcacia, strange, I used it just yesterday. I keep distrohopping and restoring these keys all the time.03:30
gnarfacei note you checked the permissions03:32
gnarfacebut what about user and group ownership of those files?03:32
gnarfaceyou said you copied them from another distro, did you remember to change the uid and gid of the files?03:32
crimson_kinggnarface, the .ssh folder and its files belong to my user and my group.03:37
crimson_kingfunny, my gitlab key worked03:40
gnarfacemaybe it is on their end then03:43
gnarfacethough i suppose if the key is old enough, there could have been a format change or something and its not working anymore03:43
crimson_kingyeah, I might just generate a new one03:44
gnarfacei do vaguely recall that being a problem semi-recently (within the last 5 years) with a really old key... (probably 20 years old)03:44
gnarfaceif i'm remembering the issue right, the format change was one that was visually distinct03:44
gnarfaceas in, you could LOOK at the key in plain text and see that it was too old to work03:44
gnarfacebut i would expect that "ssh -v -v -v ..." would give some complaint about it in that case too03:45
gnarfacethey also may have simply stopped allowing keys shorter than a certain byte-length03:46
gnarfacei would expect verbose ssh execution to give some contextual complaint about that too, though03:46
TheBlueWizardhiya all...when I insert the USB drive in, it doesn't seem to recognize the drive...any idea why? I'm looking at menu > settings > rem. drives and media and I see no checkmarks are being that why?05:27
* TheBlueWizard discovers an online help, and is now reading it :-)05:38
xrogaan/etc/pam.d/lightdm-greeter as a line `session   optional' which obviously will generate an error or warning in the logs.05:57
eyalrozBCMM: So, you're here too, then?12:37
eyalrozWell, let's try this channel. I'm having a keyboard layout issue:
eyalrozEssentially, some X apps don't accept Hebrew characters, others do.12:46
eyalrozSo when I'm in the `il` keyboard layout, spaces and punctuation marks register, but characters don't. But there's no clear rule - or at least not clear to me - as to which apps reject Hebrew characters, and I can't figure out where to look for the source of this issue12:47
eyalrozor what I can do to circumvent it.12:47
gnarfacei think that is something that is up to the program creator to support or not12:50
gnarfacebut in theory it could be a font problem too..12:50
eyalrozgnarface: But wouldn't that just mean I get junk instead of the correct glyph?13:21
eyalrozAlso, it's not just one or two programs, it's dozens13:21
eyalrozso it must be something more fundamental13:21
eyalrozIf only I could see some kind of error log...13:22
gnarfaceit might give you a blank glyph in some cases, but there's no reason to expect programs will accept invalid characters if they know they are invalid13:25
gnarfacesure there may also be one or two differently-behaving shared libraries that the misbehaved programs have in common with each other13:25
gnarfacei'm sure there's a log but i'm not sure which one13:26
gnarfacecheck in /var/log13:26
gnarfacealso try running dmesg13:26
gnarfacesometimes errors also go to the console X was started from, but they could be redirected elsewhere too13:27
gnarfacealso sometimes you can get gtk errors dumped to stderr/stdout too13:27
eyalrozgnarface: So, no empty glyphs - deleting a glyph takes me right back to the one before the beginning of the suppose Hebrew char sequence. Also, nothing on stdout or stderr.16:36
eyalrozNothing in dmesg or syslog - which makes sense, since we're talking about processes without the permission to write there.16:38
BeerbelottDoes anyone know where bash auto-completion for `groups` command comes from?16:40
KatolaZBeerbelott: /usr/share/bash-completion/bash_completion16:53
BeerbelottThat I know. Which file in it? :)17:00
KatolaZBeerbelott: that one is a file...17:01
BeerbelottOK my bad17:02
BeerbelottI was looking into the completions directory on the side17:02
BeerbelottThe question is now... There is the 'standard' groups command which auto-completes w/ users17:03
KatolaZBeerbelott: have you tried searching for "groups" in that file, for instance?17:03
Beerbelottthere also is a 'members' package containing the `members` command, but it does not come with auto-completion17:03
BeerbelottYes I found it thx17:03
BeerbelottCool I made a bash completion file for the members command inspired by what is existing for groups :)17:08
BeerbelottI now need to learn how to submit that to the upstream ;)17:08
BeerbelottAs simple as `complete -g members`17:09
eyalrozBeerbelott: Two possible places17:26
eyalrozBeerbelott: /usr/share/bash-completion17:27
eyalrozoh, sorry, looks like you got your answer already.17:27
Beerbelottnp thx for helping anyway :)17:29
BeerbelottI am going to submit my idea to the maintainer of the package some time 'round17:29
fsrmuep_, all the installer isos are bios and uefi bootable. The amd64 desktop-live iso is bios and uefi bootable (and installable)20:05
muep_good to know20:05
fsrand if you happen to have an old macbook that uses amd64 OS with 32-bit uefi, there's a way to install that, too.20:07
DocScrutinizer05(ot) new:
nacelle32bit uefi/64bit cpu macbooks are great!21:30
* nacelle has a few macs that do that21:30
nacellecore2duo things21:30
nacelle(and I upgraded a 1,1 to a 2,1)21:30
fsrnacelle, how did you install?21:43
NewGnuGuyDoes anyone know of a good program for diffing two sqlite databases?22:17
DocScrutinizer05diff <(dump1) <(dump2) ?22:39
nacellefsr: none of them are running devuan, if thats what you're asking22:41
fsryeah, that's what I was askin22:43
nacellei imagine reFind would somehow be involved22:52
fsrnacelle, no, you don't need refind22:59
nacelleI believe thats how I do openbsd on the macbook I have23:00
nacelleis it going to be much different than the debian instructions?23:02
nacelleapparently theres a grub that does 32bit uefi23:02
fsryeah, boot the desktop-live amd64 iso...23:02
fsrthen install grub-efi-ia32 but don't let it install the bootloade23:03
fsrthen run the installer23:03
fsrI think it'll work that way23:03
fsrother way is to run the installer first, then install the package in chroot23:03
fsrthe deb is in the root of the filesystem23:03
fsrand all the grub*-bin packages are installed already23:04

Generated by 2.17.0 by Marius Gedminas - find it at!