01:33 | yanu has left IRC (yanu!~yanu@178-116-55-218.access.telenet.be, Ping timeout: 245 seconds) | |
04:48 | quinox has left IRC (quinox!~quinox@ghost.qtea.nl, *.net *.split) | |
04:48 | Sleaker has left IRC (Sleaker!quasselcor@2604:880:a:7::e1b, *.net *.split) | |
04:48 | Sleaker has joined IRC (Sleaker!quasselcor@2604:880:a:7::e1b) | |
04:54 | quinox has joined IRC (quinox!~quinox@ghost.qtea.nl) | |
06:40 | woernie has joined IRC (woernie!~werner@p5B296964.dip0.t-ipconnect.de) | |
06:55 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
09:04 | mze has joined IRC (mze!~mze@2001:16b8:5599:1e00:692c:7b06:5c73:2299) | |
09:09 | <mze> Hi, i'm new to ltsp and triing to get it work for some days now. i have ubuntu 18.4 desktop and followed the installation steps from the wiki for chrootless clients. i have a raspberry pi with berryterminal that i want to use as client. when starting the rpi, i get a login screen. when i try to login i get the message "no response from server, restarting". on the server i found "sshd: Connection closed by authenticating user xxx
| |
09:09 | xxx.xxx.xxx.xxx port xxxxx [preauth] in auth.log. does someone have an idea whats going wrong?
| |
09:41 | yanu has joined IRC (yanu!~yanu@178-116-54-5.access.telenet.be) | |
09:44 | <alkisg> !ltsp-update-sshkeys | echo mze:
| |
09:44 | <ltsp> mze: ltsp-update-sshkeys: If you changed your server IP, you need to run ltsp-update-sshkeys, and if you're using NBD (Ubuntu) you also need ltsp-update-image afterwards
| |
09:45 | <alkisg> mze, it could be that
| |
09:47 | Although note that berryterminal is using an ancient ltsp version afaik, which might even be incompatible
| |
09:50 | <mze> thanks for the advice. didnt work :(. same behavior.
| |
09:50 | is there a other way to try ltsp with raspberry pi?
| |
09:52 | <alkisg> !raspberrypi
| |
09:52 | <ltsp> raspberrypi: (#1) Ubuntu/LTSP on Pi 2: https://help.ubuntu.com/community/UbuntuLTSP/RaspberryPi, or (#2) Debian/LTSP (with raspbian chroot) on Pi: http://cascadia.debian.net/trenza/Documentation/raspberrypi-ltsp-howto/, or (#3) unofficial Ubuntu/LTSP (with raspbian chroot) on Pi: http://pinet.org.uk/
| |
09:53 | <alkisg> Unfortunately LTSP is having a big update now, from version 5 to version 19, and raspberry pi isn't yet ready for the new ltsp 19, where it would be much easier
| |
09:54 | and version 5 isn't very actively maintained, so.. (#1) and (#3) should work, but they might need a bit of tinkering
| |
09:54 | The best way would be to use ltsp 19 with raspbian chroot, but it's not documented yet
| |
09:58 | <mze> all options using raspbian/arm chroot? i'd like to use chrootless because of not linking raspbian gui much and i would like to use some old windows apps with wine
| |
09:59 | but thanks i'll read and maybe try
| |
09:59 | <alkisg> mze, chrootless means that raspbian has intel/amd cpu
| |
09:59 | *raspberry
| |
10:00 | Which it doesn't, so you can't use chrootless
| |
10:00 | Now you *think* you're using chrootless, but you're not, you're using the "berryterminal chroot" in the sd card
| |
10:00 | You can however make the raspberry pi function as a thin client, and connect to the server (like remote desktop), and run x86 applications there, wine and all
| |
10:01 | <mze> confused :D
| |
10:04 | what could be the minimal setup for the pi that boots him to the remote login as a thin client?
| |
10:05 | <alkisg> This is called a "thin chroot". It's what berryterminal also does, but it puts it to the sd card instead of the server
| |
10:05 | All those #3 options above support both thin and fat mode
| |
10:06 | A fat chroot can also work as a thin chroot
| |
10:06 | LTSP_FATCLIENT=False in lts.conf is all that is needed for that switch
| |
10:07 | It's also possible to run some applications locally and some remotely, using `ltsp-localapps`
| |
14:51 | woernie has left IRC (woernie!~werner@p5B296964.dip0.t-ipconnect.de, Remote host closed the connection) | |
17:00 | woernie_ has joined IRC (woernie_!~werner@p5B296964.dip0.t-ipconnect.de) | |
18:09 | GodFather has joined IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com) | |
20:03 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
20:19 | woernie_ has left IRC (woernie_!~werner@p5B296964.dip0.t-ipconnect.de, Remote host closed the connection) | |
22:31 | MWALTERS has left IRC (MWALTERS!~ubox@c-73-152-61-86.hsd1.va.comcast.net, Ping timeout: 245 seconds) | |