| barnyard | hey | 00:30 |
|---|---|---|
| barnyard | why is sdl2 gone from the repositiories | 00:30 |
| barnyard | also | 00:30 |
| barnyard | there seems to be a lot of packages missing | 00:31 |
| barnyard | from the normal repos | 00:31 |
| KatolaZ | Besnik_b: ? | 00:31 |
| KatolaZ | barnyard: what are you talking about? | 00:31 |
| KatolaZ | define "normal" | 00:31 |
| barnyard | for example | 00:31 |
| barnyard | when I try to install irssi | 00:31 |
| barnyard | I get Depends: libval14 but it is not installable | 00:31 |
| KatolaZ | barnyard: which repos are you using? | 00:32 |
| KatolaZ | are you mixing repos? | 00:32 |
| muep_ | I guess you did run apt update (or equivalent) already? | 00:32 |
| barnyard | yeah | 00:32 |
| KatolaZ | barnyard: irssi installs just fine on ascii | 00:32 |
| KatolaZ | and on jessie | 00:32 |
| barnyard | yeah I have jessie | 00:33 |
| KatolaZ | are you sure you don't have non-devuan repos? | 00:33 |
| barnyard | I'm only using the stardard repos | 00:33 |
| KatolaZ | apt-cache policy irssi | 00:33 |
| barnyard | http://packages.devuan.org/devuan/ | 00:33 |
| KatolaZ | apt-cache policy libval14 | 00:34 |
| barnyard | what do those do | 00:34 |
| KatolaZ | blows your computer off... | 00:34 |
| KatolaZ | s/s// | 00:34 |
| KatolaZ | :) | 00:34 |
| KatolaZ | gotta go sorry | 00:35 |
| KatolaZ | o/ | 00:35 |
| barnyard | and the latest kenerl I can get is 3.5? | 00:36 |
| barnyard | there has to be a mistake | 00:36 |
| barnyard | are there more packages on ascii? | 00:37 |
| barnyard | because if so how can I update from jessie to ascii? | 00:37 |
| barnyard | anyone? | 00:47 |
| golinux | Hold on a day or so an there will be plenty of documentation to guide you. | 00:49 |
| barnyard | so ascii hasn't been released yet? | 00:49 |
| barnyard | also I have no make | 00:50 |
| barnyard | build-essentials doesn't exist | 00:50 |
| golinux | Your sources must be mixed up | 00:55 |
| golinux | This is what you should have for ascii: | 00:57 |
| golinux | deb http://deb.devuan.org/merged ascii main | 00:57 |
| golinux | deb http://deb.devuan.org/merged ascii-updates main | 00:57 |
| golinux | deb http://deb.devuan.org/merged ascii-security main | 00:57 |
| barnyard | seems like it | 00:57 |
| barnyard | I have jesse | 00:57 |
| barnyard | the ones here | 00:57 |
| barnyard | https://devuan.org/os/documentation/dev1fanboy/migrate-to-jessie | 00:57 |
| barnyard | are good, right? | 00:58 |
| barnyard | deb http://pkgmaster.devuan.org/merged jessie main deb http://pkgmaster.devuan.org/merged jessie-updates main deb http://pkgmaster.devuan.org/merged jessie-security main deb http://pkgmaster.devuan.org/merged jessie-backports main | 00:58 |
| barnyard | yeah, seems to be working great now | 00:59 |
| golinux | deb.devuan.org is a round robin of maybe a dozen mirrors. | 00:59 |
| golinux | Great! | 01:00 |
| barnyard | should I switch ascii anytime soon? | 01:00 |
| golinux | That's up to you. | 01:00 |
| golinux | and what your needs are. | 01:00 |
| xrogaan | so, logged in today and mate didn't had a window manager (didn't know what was up). | 02:57 |
| xrogaan | I started mate tweak and it informed me so. | 02:57 |
| xrogaan | it is weird | 02:58 |
| barnyard_ | does devuan have amdgpu drivers | 04:58 |
| barnyard_ | or does that come with linux standard | 04:58 |
| barnyard_ | have some bad perfomance with minetest, runs usually good when I ran it on manjaro | 04:59 |
| golinux | Maybe it's in non-free? | 05:01 |
| Jjp137 | barnyard_, the package you're looking for is named firmware-amd-graphics, which is indeed in non-free | 05:16 |
| Jjp137 | further more, if you're still on jessie, it can only be found in jessie-backports | 05:16 |
| barnyard_ | is there a free alternative? | 05:16 |
| Jjp137 | oh uh there should be but let me see | 05:17 |
| Jjp137 | although I'm not really familiar with amd/ati as much (I get to bang my head against nvidia's nonsense instead) but here's a page on Debian's wiki: https://wiki.debian.org/AtiHowTo | 05:19 |
| Jjp137 | what's your GPU? | 05:19 |
| barnyard_ | RX 480 | 05:19 |
| barnyard_ | also, is the transtion to ascii relatively painless? I'm thinking of upgrading if its stable enough | 05:21 |
| Jjp137 | barnyard_, the xserver-xorg-video-amdgpu package is in jessie-backports too, but you might also need a newer kernel from backports as well; unless you really want to stay on jessie, you might as well upgrade to ascii | 06:00 |
| Jjp137 | the transition should be mostly painless from what I've heard, and I have a feeling it's going to be released pretty soon anyway :) | 06:00 |
| xrogaan | there is no more free/proprietary package for recent amd GPU as the two projects have merged. | 06:13 |
| xrogaan | It's based from AMD's will to unify the experience, they actually contribute to the opensource thing instead of releasing their own proprietary installer (fglrx). | 06:13 |
| xrogaan | it's called something "AMDGPU-UNIFIED-LINUX" | 06:14 |
| xrogaan | So, it's in non-free because the opensource driver uses AMD proprietary blobs. Which means the code isn't in the kernel. Overall, it's way easier this way than to install fglrx. | 06:34 |
| KatolaZ | DocScrutinizer05: /topic | 07:26 |
| KatolaZ | https://devuan.org/os/debian-fork/ascii-stable-announce-060818 | 07:26 |
| KatolaZ | :) | 07:26 |
| ipe | congratulation | 07:35 |
| ipe | time to install | 07:35 |
| Hestben | Congratulation to the stable ascii release | 07:44 |
| Hestben | Also, that announcement on devuan mailing list, that support for devuan jessie will end June 2018, was that correct, not just a mistake writing 2019? Then there seems to be some hurry to upgrade... | 07:46 |
| KatolaZ | Hestben: which announcement? | 07:46 |
| golinux | I think Jessie goes for 2 more years LTS | 07:48 |
| Hestben | KatolaZ: from leftoft to dng@lists.dyne.org on May 21 2018. | 08:29 |
| Hestben | KatolaZ: https://www.mail-archive.com/dng@lists.dyne.org/msg20998.html | 08:33 |
| Hestben | There is no year there, so maybe they mean 2021? Or have I misinterpreted it? | 08:34 |
| Jjp137 | Hestben, that is pretty much based on: https://www.debian.org/security/2018/dsa-4205 | 08:38 |
| Jjp137 | there will still be LTS support for Devuan Jessie until at least some time in 2020 (source: https://twitter.com/DevuanOrg/status/867999950155763713) | 08:40 |
| Jjp137 | to be more exact, Debian's LTS support for Jessie ends on June 30, 2020, so at least that long | 08:42 |
| Hestben | Jjp137: Thanks for calming me down :) | 08:47 |
| Jjp137 | you're welcome :) | 08:49 |
| AlexLikeRock | https://twitter.com/DevuanMX/status/1005330158432202752 | 09:11 |
| AlexLikeRock | happy holly days | 09:11 |
| AlexLikeRock | i go to sleep | 09:11 |
| AlexLikeRock | bye | 09:11 |
| AlexLikeRock | we celebrate SPANISH comunity too | 09:11 |
| batmore | Congratulations all, and thanks much for the stable ascii release! | 09:13 |
| alexandru | hi everyone, I understand that you can replace OpenRC with runit in Devuan. How can I do that? | 09:35 |
| alexandru | actually, nvm, found this https://sysdfree.wordpress.com/2017/12/07/162/ | 09:52 |
| xrogaan | wait, is it better to use elogind? | 10:36 |
| xrogaan | oh, not for mate, alright. | 10:36 |
| aitor | alexandru: today i want to share an image with runit | 10:47 |
| aitor | i'm fixing an issue with the gpg key while building debian-installer | 10:48 |
| aitor | debmirror is taking to long with packages.gnuinos.org, and i don't know why (but it works): | 10:50 |
| aitor | Updating remote trace files (using rsync) ... | 10:50 |
| aitor | saturday's coffee, bb in a few minuts :) | 10:52 |
| xrogaan | W: The repository 'http://deb.devuan.org/merged ascii-proposed Release' does not have a Release file. | 10:55 |
| xrogaan | oh, it's /devuan and not /merged | 10:56 |
| DocScrutinizer05 | re /topic, I guess you want that improved, ASCII replacing Jessie? | 10:57 |
| DocScrutinizer05 | and really | 10:59 |
| DocScrutinizer05 | !ISODATE | 10:59 |
| infobot | i guess isodate is USE https://en.wikipedia.org/wiki/ISO_8601 *ONLY*, HELL AND BRIMSTONE, or "In representations for interchange, dates and times are arranged so the largest temporal term (the year) is placed to the left and each successively smaller term is placed to the right of the previous term.", or https://xkcd.com/1179/ | 10:59 |
| alexandru | aitor: interesting, to say the least :D | 11:10 |
| aitor | hi again | 11:15 |
| alexandru | hi | 11:16 |
| DocScrutinizer05 | the "imperial" MMDDYY is so damn puzzling, it's close to trumpism to use it in international context | 11:47 |
| DocScrutinizer05 | KatolaZ: shall ASCII replace the part about Jessie in /topic ? | 11:48 |
| DocScrutinizer05 | KatolaZ: I gather both are "stable", though iirc Jessie is LTS, so... no clue here | 11:49 |
| eyalroz | Is someone around to answer a newbie question? | 13:13 |
| gnarface | you'll never know unless you ask the question | 13:20 |
| eyalroz | Ok. So - I've used Debian, Lubuntu and Linux Mint over the past 2 decades, currently mostly the latter two. I won't go into details about my experiences which have had ups and downs, but right now I'm mostly ok with them as a lay user, up to issues with CUDA and an nvidia GPU not used for display. | 13:44 |
| eyalroz | Anyway, I was quite annoyed with the choice by major Linux distributions, Debian in particular, w.r.t. systemd, and I want to put my PC where my mouth is - by switching to Devuan. However, I'm worried about user experience, and developer experience, deterioration. What can you tell me, or what can I read, which would assuage my reservations enough to brave a switch to Devuan when I next upgrade my desktop's distro in a few months (from Mint 18.3)? | 13:44 |
| KatolaZ | eyalroz: define user experience | 13:45 |
| KatolaZ | and, possibly, define "deterioration" :) | 13:45 |
| eyalroz | @KatolaZ: A bit difficult to define. Apps and/or UI elements not behaving as you would expect / not working, the need for lots of configuration file tweaking just to get daily lay user activity to work properly, issues with the support for common hardware, stuff like that. | 13:47 |
| aitor | arrrrrrrrr !! | 13:49 |
| eyalroz | @aitor: ? | 13:49 |
| aitor | sources.list.udeb.local -> deb [trusted=yes] http://gnuinos.org/debian-installer/ jessie main/debian-installer | 13:49 |
| aitor | i am an idiot | 13:49 |
| aitor | add me to the list of idiots :) | 13:49 |
| aitor | need to reboot, see you | 13:51 |
| gnarface | eyalroz: gnome is busted, most of the rest is still fine | 13:58 |
| gnarface | was busted? did anyone ever make a patch for that? | 13:59 |
| eyalroz | @gnarface: Oh, I forgot to mention I'm an anti-gnomer. I use Cinnamon (if it doesn't crash on me) or XFCE | 13:59 |
| gnarface | i think people are using mate instead | 13:59 |
| gnarface | xfce is the default | 13:59 |
| gnarface | some little stuff is broken with temperature sensors and hibernate functionality | 14:00 |
| gnarface | in places where support was removed | 14:00 |
| gnarface | here and there | 14:00 |
| gnarface | most stuff will still work with lm-sensors | 14:01 |
| eyalroz | @gnarface: But generally, I can expect it to be as "smooth-feeling" as Debian (Which is perhaps less than Mint, but still pretty good)? | 14:06 |
| gnarface | you won't notice any performance difference if that's what you mea | 14:06 |
| gnarface | *mean | 14:06 |
| gnarface | it's the same kernel, the same drivers, the same packages (mostly) | 14:07 |
| gnarface | where systemd grants blanket permissions to the logged-in user, devuan is still using the same permissions setup as debian was in wheezy and before, for the most part with only minor updates here and there | 14:08 |
| gnarface | it should look very familiar to you | 14:08 |
| gnarface | eyalroz: i guess the short version is that it's not deteriorated very much yet. it's still very much salvageable. you're getting in early enough. | 14:37 |
| eyalroz | @gnarface: Wait, so, you're saying there will gradually be more, rather than less, deterioration / breakage? I would have assumed you took a hit initially turning off systemd, and gradually things would get better | 15:34 |
| gnarface | eyalroz: you failed to account for asshattery. that's what you should hope for, but what you should plan for is a steadily increasing amount of vandalism until they eventually force a full fork, which can be staved off longer the more developers join the project to help | 15:42 |
| gnarface | nonetheless, with your help i'm confident we can still save it | 15:42 |
| gnarface | the debian that was | 15:42 |
| gnarface | so far it's working well | 15:43 |
| eyalroz | @gnarface: I'm actually not much of an OS distro guy. I've written couple of Thunderbird extensions, | 15:43 |
| eyalroz | yes, another distressted project... | 15:43 |
| eyalroz | but next time I'm employed I'll definitely make a donation | 15:43 |
| gnarface | it's really the only serious attempt to preserve the general distro design/behavior of debian wheezy and earlier | 15:44 |
| gnarface | for software going forward | 15:44 |
| gnarface | as that, it's doing really well, but obviously more help would mean less delay | 15:45 |
| grillon | hi there | 15:45 |
| grillon | I need arm-none-eabi-gcc6 how can I install it on devuan ascii? I guess it's in testing? | 15:46 |
| gnarface | eyalroz: but what i meant about you getting in early enough is primarily that as of ascii, they really haven't broken much | 15:46 |
| eyalroz | Ah | 15:46 |
| grillon | Hi MinceR | 15:46 |
| gnarface | eyalroz: and for the most part it's all been fixed for the ascii release | 15:46 |
| eyalroz | Do we know that there's planned additional breakage? | 15:46 |
| eyalroz | e.g. by systemd taking over more of the system, | 15:47 |
| eyalroz | or stronger dependencies on its facilities? | 15:47 |
| gnarface | there's been a worrisome pattern of them removing stuff that "nothing was using anymore" like /etc/resolv.conf ... | 15:47 |
| gnarface | but for the most part those types of things get corrected in devuan | 15:47 |
| MinceR | hay grillon | 15:48 |
| grillon | :) | 15:48 |
| gnarface | grillon: it might be named slightly differently | 15:48 |
| grillon | it's been a long time MinceR, nice to see you | 15:48 |
| grillon | hmmm, so how could I find it? | 15:49 |
| gnarface | apt-cache show gcc-arm-none-eabi | 15:50 |
| gnarface | what does that show you? | 15:50 |
| grillon | only the version 5.4.1 | 15:50 |
| gnarface | oh | 15:50 |
| gnarface | hmmm | 15:50 |
| gnarface | i see 6.3.1 in ceres | 15:51 |
| gnarface | check ascii-backports, otherwise you'll have to backport it yourself or install it in a ceres chroot or something like that... | 15:51 |
| grillon | not in ascii-backports | 15:52 |
| grillon | hmm let's try chroot, thank you for your help :) | 15:54 |
| gnarface | no problem | 15:54 |
| barnyard | ascii is looking good | 16:26 |
| muep_ | which common GNU/Linux distribution does not use resolv.conf anymore? afaik at least all of debian, fedora, ubuntu still use it just fine | 16:44 |
| gnarface | maybe it was rc.local? | 16:55 |
| muep_ | I think that one still works as well on all of those | 16:56 |
| muep_ | it's a bit less of a free-for-all than it used to, though, because there is an expectation there that the processes started from rc.local also terminate in some reasonable time | 17:00 |
| DocScrutinizer05 | where to report a ssh bug? (upstream, also after checking source) | 19:57 |
| DocScrutinizer05 | >>client: no timeout in negotiation after server stops responding during negotiation<< | 19:58 |
| yann-kaelig | elo. How long should I wait for a new stable release of a package like opennebula and last stable release 5.4.13 https://opennebula.org/software/ | 20:03 |
| Artemis3 | https://fossbytes.com/debian-without-systemd-devuan-2-0-download-features/ | 20:12 |
| DocScrutinizer05 | any devel around who could point me to ssh client upstream? | 20:49 |
| DocScrutinizer05 | sorry I suck at this | 20:49 |
| KatolaZ | DocScrutinizer05: ? | 20:55 |
| DocScrutinizer05 | KatolaZ: I think I found a bug in ssh client, want to check upstream source | 20:55 |
| DocScrutinizer05 | and bugtracker | 20:56 |
| KatolaZ | apt-cache source PACKAGE | 20:56 |
| KatolaZ | we haven't forked ssh | 20:56 |
| KatolaZ | the package comes form Debian | 20:56 |
| DocScrutinizer05 | yeah, I'm more interested about where to find upstream | 20:56 |
| DocScrutinizer05 | the genuine bugtracker and upstream repo | 20:57 |
| KatolaZ | it should be in the corresponding orig.tar.gz | 20:57 |
| KatolaZ | or in the upstream branch | 20:57 |
| KatolaZ | depending on how it's maintained | 20:57 |
| DocScrutinizer05 | :-) I'll try to find my way along that | 20:57 |
| DocScrutinizer05 | though *maybe* aunt google can help me out | 20:57 |
| DocScrutinizer05 | or - DUH - a man ssh | 20:58 |
| DocScrutinizer05 | hmm no, manpages are not helpful | 20:59 |
| Jjp137 | DocScrutinizer05, ssh is OpenSSH I believe, so here: https://www.openssh.com/report.html | 21:01 |
| DocScrutinizer05 | oh great! thanks a lot | 21:01 |
| Jjp137 | np | 21:02 |
| Jjp137 | (yea it is OpenSSH: https://packages.debian.org/stretch/ssh, see the right sidebar) | 21:03 |
| DocScrutinizer05 | I found the bug on a pretty old version of ssh (2015) on a Suse distro, but I know of this bug since 10+ years and I want to check if it's fixed meanwhile. Since it's hard to reproduce I can't check the easy way, I was lucky to encounter it while running ssh -vvv today, first time ever | 21:08 |
| bill-auger | 2015 is pretty old huh? | 21:09 |
| DocScrutinizer05 | see http://paste.ubuntu.com/p/3YtMnM62TM/ | 21:09 |
| bill-auger | lemme think now .... when did jessie come out? | 21:09 |
| bill-auger | s'a tough one eh doc :) | 21:09 |
| DocScrutinizer05 | indeed | 21:10 |
| DocScrutinizer05 | I *guess* the devels simply didn't think of a reply never arriving so are sitting idly waiting happily for reply until hell freezes over | 21:13 |
| DocScrutinizer05 | alas with packet loss it's not exactly unlikely that a reply during negotiations gets lost | 21:13 |
| yann-kaelig | very good choice openrc as init, now you can move on S6 ^^ | 21:18 |
| Artemis3 | runit | 21:31 |
| Wonka | but... shouldn't tcp resend stuff? | 21:35 |
| nacelle | tcp should retry and time out | 21:47 |
| nacelle | openssh is well thought out, beat up and tested pretty hard at this point | 21:48 |
| aitor | hi all | 21:49 |
| nacelle | DocScrutinizer05: do you have the ClientAliveInterval and ClientAliveCountMax settings set? (do those even come into play if the connection isnt established?) | 21:54 |
| nacelle | or ServerAliveInterval 15 | 21:54 |
| nacelle | ServerAliveCountMax 3 | 21:54 |
| nacelle | etc. | 21:54 |
| DocScrutinizer05 | no, aiui they don't | 21:55 |
| nacelle | i got 'em backwards | 21:55 |
| nacelle | client should have the ServerAlive... | 21:55 |
| nacelle | not sure if that applies when connection isnt up | 21:55 |
| DocScrutinizer05 | funny enough in latest sources I can find a "SSH2_MSG_NEWKEYS sent" but no "SSH2_MSG_SERVICE_REQUEST sent" | 21:55 |
| aitor | DocScrutinizer05 has been in Manhattan | 21:57 |
| DocScrutinizer05 | Wonka: I guess the scenario is: TCP packet client->server succeeds: reply server->client gets eaten completely by packet loss and server gives up on resending | 21:57 |
| DocScrutinizer05 | nacelle: ^^^ | 21:58 |
| nacelle | this seems dubious | 21:59 |
| nacelle | tcp retransmits | 21:59 |
| nacelle | you wouldnt have it do that | 21:59 |
| DocScrutinizer05 | so what? when connection has 100% packet loss | 21:59 |
| nacelle | like you're able to get a few packets out and then your internet connection fails? | 21:59 |
| DocScrutinizer05 | no, in this case the server internet connection failed with 98% packet loss | 22:00 |
| DocScrutinizer05 | so fact is my client got stuck forever on http://paste.ubuntu.com/p/3YtMnM62TM/ | 22:00 |
| nacelle | i know i've hit it before | 22:01 |
| DocScrutinizer05 | obviously no timeout on application protocol layer | 22:01 |
| nacelle | there might be one you can set and a reason why its not by default | 22:01 |
| nacelle | but there could be a bug | 22:01 |
| nacelle | (i'd be cautious about calling it a bug outright, but you know you have questionable behavior for now) | 22:02 |
| DocScrutinizer05 | I guess it's not showing up too frequently, since connection has to be up and delivering to send the request, then goes down completely before response arrives at client | 22:03 |
| nacelle | it smells bug-esque | 22:03 |
| nacelle | yeah | 22:03 |
| nacelle | like a gateway transition could cause it if they're not using state so well | 22:03 |
| nacelle | firewall failover, etc. | 22:03 |
| DocScrutinizer05 | or random packet loss like in my case | 22:04 |
| nacelle | might happen if you're trying to do state over a common port they give up on tracking state over, like 80 or something | 22:04 |
| nacelle | eh i doubt it | 22:04 |
| nacelle | tcp retransmits | 22:04 |
| DocScrutinizer05 | dosn't help | 22:04 |
| nacelle | it doesnt just send one thing out and stop | 22:04 |
| nacelle | it does! | 22:04 |
| DocScrutinizer05 | random does whatever you want, you just have to wait for it | 22:05 |
| nacelle | right, this gets around it | 22:05 |
| nacelle | some things shoudl randomly get through | 22:05 |
| nacelle | so tcp retrying packets it sent off will randomly get them through, in theory | 22:05 |
| nacelle | otherwise you end up with a socket timeout | 22:05 |
| nacelle | and that will be seen | 22:05 |
| DocScrutinizer05 | fact is the connection went down after first ping when I ran a mtr against server, so what are we discussing here? | 22:06 |
| DocScrutinizer05 | the socket timeout is on server side | 22:06 |
| nacelle | socket is formed in the client, yo | 22:06 |
| DocScrutinizer05 | client side doesn't see any connectivity ussues | 22:06 |
| nacelle | that particular socket will timeout | 22:06 |
| DocScrutinizer05 | no obviously not | 22:07 |
| nacelle | tcp will not see responses and will stop | 22:07 |
| DocScrutinizer05 | why would it? | 22:07 |
| DocScrutinizer05 | huh? | 22:07 |
| * nacelle sighs | 22:07 | |
| nacelle | go read this: https://www.amazon.com/TCP-Illustrated-Vol-Addison-Wesley-Professional/dp/0201633469 | 22:08 |
| DocScrutinizer05 | we're talking application layer protocol here, not a SYN/ACK whatnot TCP layer issue | 22:08 |
| DocScrutinizer05 | TCP has no keep-alive pings built in | 22:08 |
| DocScrutinizer05 | that's why a ssh connection idles for hours even when server rebooted | 22:09 |
| nacelle | uh, no | 22:09 |
| DocScrutinizer05 | unless you have keep-alive | 22:09 |
| * nacelle wanders off | 22:09 | |
| DocScrutinizer05 | maybe a established TCP connection tomes out, after hours or days | 22:11 |
| DocScrutinizer05 | times out, even | 22:11 |
| DocScrutinizer05 | or maybe there's no TCP connection established in this case, and my ssh client waits for a new inbound connection from server? No, can't be since this wouldn't fly for a number of reasons, NAT being only one of them | 22:12 |
| DocScrutinizer05 | so ssj has --keep-alive for a reason: to avoid NAT closing the session on *idle* TCP connections, when neither client nor server send data. Server can get nuled off the globe and client wouldn't even notice until next time tryong to send a packet | 22:14 |
| aitor | i updated the repo of gnuinos, doing d-i compatible with linux-4.9 | 22:14 |
| aitor | http://packages.gnuinos.org/gnuinos/pool/main/d/debian-installer/ | 22:14 |
| aitor | need to reboot again: live-sdk :) | 22:17 |
| DocScrutinizer05 | I can ssh from PC into my phone via WLAN, then take the phone out for a walk for half an hour with no WLAN connection for sure, come back home and the ssh session still is up and running as if server (phone) never vanished | 22:17 |
| DocScrutinizer05 | no timeout on any sockets | 22:18 |
| DocScrutinizer05 | since no packet got sent either direction | 22:18 |
| nacelle | ssh reestablishes if you have keys | 22:20 |
| nacelle | its some pretty magic stuff | 22:20 |
| nacelle | you'll still tcp timeout (your client doesnt see an ack in time and cools off) | 22:20 |
| DocScrutinizer05 | ACK for what? | 22:21 |
| nacelle | whatever it sent | 22:21 |
| DocScrutinizer05 | when there's no data to send, there's no ACK to reply to such data sent | 22:21 |
| nacelle | it sent a request? | 22:22 |
| DocScrutinizer05 | so? thst arrived | 22:22 |
| DocScrutinizer05 | and got its ACK | 22:22 |
| nacelle | can you take this to #openssh? | 22:22 |
| nacelle | i'll join you there | 22:22 |
| aitor | kmod replaces to module-init-tools? | 22:39 |
| aitor | i had the sources.list set to ascii | 23:09 |
| aitor | i'm building gnuinos jessie with the live-sdk with the new repo; it'll take some time | 23:11 |
| tom13 | note to community: if running devuan ceres, gimp upgrade from 2.8 to 2.10 requires you to add an additional package gimp-python, to maintain scripting functionality | 23:26 |
| DocScrutinizer05 | ssh topic "solved": http://susepaste.org/10830225 http://susepaste.org/26438994 HMMM there's something in there evein in 6.2p2, but I fail to understand where timeout var gets set to a non-null value, and for sure I don't see the logit("Connection to %.200s timed out while " "waiting to read", get_remote_ipaddr()); | 23:28 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!