IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 15 August 2017 (all times are UTC)
| 00:01 | stgraber has left IRC (stgraber!~stgraber@2001:470:b368:1000:1::1, Changing host) | |
| 00:01 | stgraber has joined IRC (stgraber!~stgraber@ubuntu/member/stgraber) | |
| 00:11 | alexxtasi[m] has joined IRC (alexxtasi[m]!alexxtasim@gateway/shell/matrix.org/x-tsdhbithkmkwsbyi) | |
| 01:00 | Freejack has left IRC (Freejack!~quassel@unaffiliated/freejack, Quit: No Ping reply in 180 seconds.) | |
| 01:02 | Freejack has joined IRC (Freejack!~quassel@unaffiliated/freejack) | |
| 01:44 | lucascastro has joined IRC (lucascastro!~lucas@186.227.186.18) | |
| 05:14 | Statler has joined IRC (Statler!~Georg@p579FE7ED.dip0.t-ipconnect.de) | |
| 05:30 | lucascastro has left IRC (lucascastro!~lucas@186.227.186.18, Remote host closed the connection) | |
| 06:34 | lucjayjay has joined IRC (lucjayjay!c32570e2@gateway/web/freenode/ip.195.37.112.226) | |
| 06:36 | <lucjayjay> hey guys, I've got a quick question. Is the thin client supposed to see the root filesystem of the server instead of the chroot filesystem ?
| |
| 06:38 | mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk) | |
| 06:43 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 07:03 | alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg) | |
| 07:04 | <alkisg> lucjayjay: thin clients before login get the chroot file system
| |
| 07:04 | after login, the session is on the server, so they see the server filesystem
| |
| 07:04 | In general it's suggested to use ltsp fat clients instead
| |
| 07:04 | !fatclients
| |
| 07:04 | <ltsp> fatclients: Nowadays LTSP supports thin and fat clients. They are both diskless and netbooted from the same LTSP chroot, but while thin clients run the session on the server and transfer the screen, fat clients run the session locally with their own CPU/RAM, thus performing amazingly better. See also !ltsp-pnp and https://help.ubuntu.com/community/UbuntuLTSP/FatClients
| |
| 07:04 | <alkisg> !ltsp-pnp
| |
| 07:04 | <ltsp> ltsp-pnp: ltsp-pnp is an alternative (upstream) method to maintain LTSP installations for thin and fat clients that doesn't involve chroots: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
| |
| 07:08 | lucjayjay has left IRC (lucjayjay!c32570e2@gateway/web/freenode/ip.195.37.112.226, Quit: Page closed) | |
| 07:08 | lucjayjay has joined IRC (lucjayjay!c32570e2@gateway/web/freenode/ip.195.37.112.226) | |
| 07:10 | <alkisg> lucjayjay: did you see my answer?
| |
| 07:16 | <lucjayjay> yes
| |
| 07:17 | but runny fat clients wont be a solution because if have multiple office wine installations which are different for every client
| |
| 07:17 | that would bloat the image to much and would make it hard to mantain
| |
| 07:17 | <alkisg> lucjayjay: that doesn't really make sense
| |
| 07:17 | Where do you put the wine apps?
| |
| 07:17 | Usually wine apps go in /home/username/.wine
| |
| 07:18 | Which isn't part of the image
| |
| 07:18 | <lucjayjay> hm
| |
| 07:18 | true
| |
| 07:19 | <alkisg> If you don't have any specific reasons against it, ltsp-pnp is the easiest way to maintain ltsp fat clients, even if you're using wine
| |
| 07:20 | <lucjayjay> but it does take away the concept of using old spare computers as clients
| |
| 07:20 | <alkisg> No, because ltsp-pnp automatically boots them as thins
| |
| 07:21 | So if they're fast, they automatically get to be fat clients, if they're slow, they become thins
| |
| 07:21 | So you can e.g. have a computer lab with 6 thin clients and 6 fat without doing any configuration at all
| |
| 07:27 | <lucjayjay> so whats the main diffrence of ur ltsp version compared to the normal one ?
| |
| 07:27 | I've read the pnp article but didnt see any significant changes in the setup article
| |
| 07:29 | <alkisg> It doesn't have a chroot
| |
| 07:29 | <lucjayjay> Sorry to bug you with so many questions ^^
| |
| 07:29 | <alkisg> It's using the server installation, /, as a template
| |
| 07:29 | Also, it's not "my" ltsp version, it's the main ltsp version now
| |
| 07:29 | The main ltsp supports both ltsp-pnp and the older chroot method
| |
| 07:30 | And ltsp-pnp is the recommented one, unless someone needs the old method for some reason
| |
| 07:30 | <lucjayjay> ok.. i guess the repos from ubunutu ore outdated then
| |
| 07:31 | <alkisg> It's been in Ubuntu since 14.04
| |
| 07:31 | So no, they're not outdated
| |
| 07:32 | I'm using Ubuntu to develop LTSP, so it would be weird to have it outdated there :)
| |
| 07:32 | <lucjayjay> well then why did my ltsp create a chroot ? :/ I just ran ltsp-build-client
| |
| 07:33 | <alkisg> Because you ran the old command
| |
| 07:33 | ltsp-build-client = old method
| |
| 07:33 | ltsp-update-image -c / = new method
| |
| 07:33 | Both are supporteed
| |
| 07:34 | That's what reading the wiki would tell you :)
| |
| 07:37 | <lucjayjay> well I've read through many pages of docs and tutorials all stating different things, so i got a little confused
| |
| 07:38 | <alkisg> It's true that the ubuntu wiki has a lot of oudated pages
| |
| 07:38 | *outdated
| |
| 07:38 | <lucjayjay> so the pnp version creates a image based on my system but the clients are all fat clients with mounted home dirs right ?
| |
| 07:38 | <alkisg> Yes, except not "all fats", but only those that have > 500 MB RAM
| |
| 07:38 | If they have less RAM, they become thins
| |
| 07:39 | (configured via FAT_RAM_THRESHOLD)
| |
| 07:39 | <lucjayjay> so they log into the server and can see the root directory
| |
| 07:39 | when they have less ram
| |
| 07:39 | <alkisg> Yes
| |
| 07:39 | <lucjayjay> aaaah ok
| |
| 07:40 | <alkisg> So basically you only install the apps once, instead of installing them both on the server and in the chroot
| |
| 07:40 | <lucjayjay> sounds good
| |
| 07:40 | <alkisg> But note that before switching to the ltsp-pnp mode, do remove the existing /opt/ltsp/i386 chroot
| |
| 07:40 | <lucjayjay> i may try this
| |
| 07:40 | <alkisg> So that you don't get confused by which image is used
| |
| 07:40 | sudo mv /opt/ltsp /opt/ltsp-bak should do it
| |
| 07:41 | <lucjayjay> one thign that bugged my is that thin clients can see the lts.conf
| |
| 07:41 | and with that the clear text passwords from auto login users
| |
| 07:43 | <alkisg> Yeah that's bad design choice. You can allow only root to read it though
| |
| 07:44 | It'll be changed with ltsp6
| |
| 07:44 | <lucjayjay> tried that, but then the clients dont have the settings cause they cant read it
| |
| 07:44 | <alkisg> Which tftpd are you using, dnsmasq or tftpd-hpa?
| |
| 07:45 | ltsp-pnp uses dnsmasq, while classic ltsp uses tftpd-hpa
| |
| 07:45 | <lucjayjay> tftpd-hpa i think
| |
| 07:45 | since im using the classic version atm
| |
| 07:46 | <alkisg> Check if it's using e.g. tftpd-hpa as the daemon user
| |
| 07:46 | ps aux | grep tftp
| |
| 07:46 | If so, chown lts.conf to be readable by the daemon user
| |
| 07:46 | (or just switch to dnsmasq)
| |
| 07:46 | <lucjayjay> root 766 0.0 0.0 15180 904 ? Ss Aug14 0:00 /usr/sbin/in.tftpd --listen --user tftp --address :69 --secure /var/lib/tftpboot
| |
| 07:46 | well root is running it
| |
| 07:47 | what do u mean by deamon user
| |
| 07:48 | <alkisg> If it's running as root, it should be able to read /var/lib/tftpboot/ltsp/i386/lts.conf without issues, even if you only make it readable by root
| |
| 07:48 | dnsmasq 1287 0.0 0.0 52880 2792 ? S 10:02 0:00 /usr/sbin/dnsmasq -x /var/run/dnsmasq/dnsmasq.pid -u dnsmasq -r /var/run/dnsmasq/resolv.conf -7 /etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new --local-service
| |
| 07:48 | ...while dnsmasq has a special user named dnsmasq, so you'd need to run chown dnsmasq lts.conf
| |
| 07:48 | <lucjayjay> well i chmodded it 750
| |
| 07:48 | lts.conf
| |
| 07:48 | didnt work
| |
| 07:50 | <alkisg> Try it again
| |
| 07:50 | Go to tftp, chmod it
| |
| 07:50 | In a client, run: ltsp-localapps xterm
| |
| 07:50 | In the xterm, try to get lts.conf with tftp
| |
| 07:50 | !tftp
| |
| 07:50 | <ltsp> tftp: Here's a page to help you troubleshoot TFTP problems in Ubuntu: https://help.ubuntu.com/community/UbuntuLTSP/Troubleshooting/TFTP
| |
| 07:51 | <alkisg> ...there's a tftp command in that wiki page, don't read the page only get the command
| |
| 08:10 | Statler has left IRC (Statler!~Georg@p579FE7ED.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 08:49 | Statler has joined IRC (Statler!~Georg@p579FEFD2.dip0.t-ipconnect.de) | |
| 08:54 | lurky has left IRC (lurky!~url@111-251-137-100.dynamic-ip.hinet.net, Ping timeout: 240 seconds) | |
| 09:02 | <lucjayjay> ok will try that
| |
| 09:07 | is it possible to run ldm/rc scripts in the pnp ?
| |
| 09:07 | <alkisg> Of course, the whole boot process is common
| |
| 09:07 | <lucjayjay> ok
| |
| 09:07 | <alkisg> The only change in pnp is ltsp-update-image -c / vs ltsp-build-client
| |
| 09:07 | All the code is common
| |
| 09:08 | <lucjayjay> sounds good
| |
| 09:08 | will try that, tahnk you very much
| |
| 09:11 | <alkisg> np
| |
| 09:25 | mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving) | |
| 09:27 | mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk) | |
| 09:32 | <lucjayjay> tried the tftp
| |
| 09:32 | it says permission denied
| |
| 09:33 | i chmodded lts.conf with 750
| |
| 09:33 | owner is root group is root
| |
| 09:33 | <alkisg> lucjayjay: if you want, run vnc for me to see...
| |
| 09:33 | !vnc-alkisg
| |
| 09:33 | <ltsp> vnc-alkisg: To share your screen with me, run this: sudo apt-get --yes install x11vnc; x11vnc -connect alkisg.no-ip.org This is a reverse connection, it doesn't need port forwarding etc.
| |
| 09:34 | <alkisg> !forget vnc-alkisg
| |
| 09:34 | <ltsp> The operation succeeded.
| |
| 09:34 | <alkisg> !learn vnc-alkisg as To share your screen with me, run this: sudo apt-get --yes install x11vnc; x11vnc -connect alkisg.dtdns.net This is a reverse connection, it doesn't need port forwarding etc.
| |
| 09:34 | <ltsp> The operation succeeded.
| |
| 09:43 | <alkisg> lucjayjay: ok, the problem was that tftpd-hpa required --permissive
| |
| 09:43 | dnsmasq doesn't have that issue...
| |
| 09:44 | <lucjayjay> so tftp has its own permissio nchecks or what does this do ?
| |
| 09:44 | <alkisg> Yes
| |
| 09:44 | man tftpd to learn more
| |
| 09:45 | <lucjayjay> can i reverse that ownership change ?
| |
| 09:47 | <alkisg> Of course, run chown
| |
| 09:48 | and/or chmod, whatever you like
| |
| 09:48 | <lucjayjay> so its not needed to have the file in the tftp group ?
| |
| 09:48 | cause the default tftp user is tftp
| |
| 09:48 | <alkisg> If you want it to be readable by tftp only, you put it in that group
| |
| 09:49 | So yes, you need to have it in that group if you don't want the users to be able to cat it
| |
| 09:49 | <lucjayjay> well if its owned by root only ?
| |
| 09:49 | <alkisg> It's normal user permissions
| |
| 09:49 | <lucjayjay> like 750
| |
| 09:49 | <alkisg> Anyways, try it however you want
| |
| 09:49 | And see
| |
| 09:49 | <lucjayjay> ok
| |
| 09:49 | thank u again
| |
| 09:49 | <alkisg> It's just normal file system permissions, there are thousands of wiki pages about that
| |
| 09:50 | <lucjayjay> well was curious about the ownership change
| |
| 09:50 | <alkisg> That again was related to normal file permissions
| |
| 09:51 | <lucjayjay> yeah but is the user/group ownership of tftp required ?
| |
| 09:51 | guess will try
| |
| 09:51 | helped me alot though
| |
| 09:55 | lucjayjay has left IRC (lucjayjay!c32570e2@gateway/web/freenode/ip.195.37.112.226, Quit: Page closed) | |
| 10:52 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.) | |
| 10:56 | book` has left IRC (book`!~book`@68.ip-149-56-14.net, Quit: Leaving) | |
| 11:19 | book` has joined IRC (book`!~book`@68.ip-149-56-14.net) | |
| 12:53 | lucascastro has joined IRC (lucascastro!~lucas@186.227.185.10) | |
| 12:58 | fnurl has joined IRC (fnurl!~url@36-227-32-102.dynamic-ip.hinet.net) | |
| 13:35 | alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg) | |
| 14:01 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.) | |
| 14:10 | administrador has joined IRC (administrador!be3ef435@gateway/web/freenode/ip.190.62.244.53) | |
| 14:15 | alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg) | |
| 14:18 | mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving) | |
| 14:48 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.) | |
| 14:58 | alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg) | |
| 16:05 | Statler has left IRC (Statler!~Georg@p579FEFD2.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 17:52 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.) | |
| 18:11 | alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg) | |
| 18:32 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.) | |
| 19:05 | alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg) | |
| 19:10 | lucascastro has left IRC (lucascastro!~lucas@186.227.185.10, Remote host closed the connection) | |
| 20:43 | lucascastro has joined IRC (lucascastro!~lucas@186.227.186.18) | |
| 20:54 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.) | |
| 21:31 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 21:42 | adrianor1 has joined IRC (adrianor1!~adrianorg@179.187.25.28.dynamic.adsl.gvt.net.br) | |
| 21:45 | adrianorg has left IRC (adrianorg!~adrianorg@177.18.48.244, Ping timeout: 248 seconds) | |
| 22:20 | zamba has left IRC (zamba!marius@flage.org, Ping timeout: 240 seconds) | |
| 22:21 | zamba has joined IRC (zamba!marius@flage.org) | |