IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 26 November 2019 (all times are UTC)
| 01:54 | robert45 has joined IRC (robert45!~robert45@r190-134-21-108.dialup.adsl.anteldata.net.uy) | |
| 01:56 | <robert45> hey guys, I need to run a "snap remove" command from the ltsp image but Im getting the following error: https://paste.ubuntu.com/p/JmJNBWZQQF/ any ideas how do I run this command? The command runs fine from outisde the chroot
| |
| 03:47 | gdi2k has joined IRC (gdi2k!~gdi2k@58.69.160.27) | |
| 04:01 | <alkisg> robert45: which ltsp, 5 or 19?
| |
| 04:01 | <robert45> alkisg sorry forgot to mention, ltsp5
| |
| 04:02 | <alkisg> Many programs don't run well in chroots, that's why people are moving to VMs, containers like docker or lxc etc
| |
| 04:02 | So one way would be to use a VM or the chrootless mode instead of a chroot,
| |
| 04:02 | another way would be to boot the chroot with qemu or from an nfs-rw client, so that it's normally booted and programs like snap work,
| |
| 04:03 | and the final way would be for you to find out which things need to be bind-mounted in order for snap to work inside chroots
| |
| 04:03 | That last part is why ltsp developers are not recommending chroots anymore, because we don't want to spend time on each of the 50000+ packages separately
| |
| 04:04 | !chroot
| |
| 04:04 | <ltspbot> chroot: To manage chroots with the new LTSP, see https://github.com/ltsp/community/wiki/chroots
| |
| 04:04 | <alkisg> This has some pointers on how to boot chroots with nfs-rw or qemu-kvm
| |
| 04:08 | <robert45> alkisg Im thinking the final way would be the easier one, do you know by chance which things need to be bind-mounted ?
| |
| 04:08 | <alkisg> robert45: nope, that's exactly what I wanted to avoid and stopped using chroots
| |
| 04:08 | To avoid spending 2 days to find out what snap needs to run in chroots
| |
| 04:08 | <robert45> ah I see
| |
| 04:09 | <alkisg> That's why you shouldn't be using chroots with ltsp
| |
| 04:09 | Especially if it's a fat chroot
| |
| 04:09 | *at all, not with ltsp
| |
| 04:09 | At least, with the "chroot" command; it's fine if you're using nfs-rw or lxc
| |
| 04:21 | <robert45> :/
| |
| 04:22 | alkisg cant I mount squasfs inside chroot neither?
| |
| 04:22 | <alkisg> It should be possible, with the appropriate bind-mounts
| |
| 04:22 | But for details, you should ask in the snap forums
| |
| 04:23 | Chroots were fine while all developers cared for their programs to be able to run inside them
| |
| 04:23 | That's no longer the case, and LTSP can't fix the *other* programs to be able to run inside chroots; LTSP users that need that, should contact those program developers
| |
| 04:24 | Or just accept it and boot the chroot with one of the other ways I mentioned
| |
| 04:24 | <robert45> I understand, thanks
| |
| 04:24 | <alkisg> With lxc, kvm, real client, nfs-rw etc etc
| |
| 04:24 | Or just switch to VM or chrootless which is a lot easier :)
| |
| 04:26 | <robert45> I think I found a post from you in snapcraft forums
| |
| 04:27 | <alkisg> I think you're talking about when I was trying to make snaps run properly on the booted ltsp clients
| |
| 04:28 | That part was solved, it was only a problem for a week or so
| |
| 04:29 | <robert45> ahh I see
| |
| 04:53 | robert45 has left IRC (robert45!~robert45@r190-134-21-108.dialup.adsl.anteldata.net.uy, ) | |
| 06:01 | statler has joined IRC (statler!~Georg@p5B30EE2F.dip0.t-ipconnect.de) | |
| 06:23 | woernie has joined IRC (woernie!~werner@p57A0E783.dip0.t-ipconnect.de) | |
| 07:37 | woernie has left IRC (woernie!~werner@p57A0E783.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 08:13 | os_a has joined IRC (os_a!~Thunderbi@185.135.149.39) | |
| 09:05 | georgeneophytou has left IRC (georgeneophytou!~georgeneo@217.27.33.213, Remote host closed the connection) | |
| 09:24 | statler_ has joined IRC (statler_!~Georg@gwrz3.lohn24.de) | |
| 09:53 | woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de) | |
| 10:24 | os_a has left IRC (os_a!~Thunderbi@185.135.149.39, Remote host closed the connection) | |
| 11:29 | eddyTV has left IRC (eddyTV!~eddyTV@unaffiliated/eddytv, Quit: My computer has gone to sleep. ZZZzzz…) | |
| 11:54 | eddyTV has joined IRC (eddyTV!~eddyTV@unaffiliated/eddytv) | |
| 11:59 | Faith has joined IRC (Faith!~Paty_@unaffiliated/faith) | |
| 12:03 | section1 has joined IRC (section1!~section1@178.33.109.106) | |
| 12:24 | kjackal has joined IRC (kjackal!~quassel@2a02:587:3107:2e00:86b:3cf9:f2c1:72ae) | |
| 13:11 | profesor has joined IRC (profesor!58111e12@18.red-88-17-30.dynamicip.rima-tde.net) | |
| 13:11 | <profesor> hi all
| |
| 13:11 | i have an issue with epoptes
| |
| 13:14 | when share my serve screen with 15 workstations, after few seconds the connection share screen disapear on the workstations
| |
| 13:14 | are there any log somewhere to check whats happend?
| |
| 13:14 | the client are debian machienes
| |
| 13:15 | and sometimes alert this message "unable to connect to socket connection refused (111)"
| |
| 13:36 | kjackal has left IRC (kjackal!~quassel@2a02:587:3107:2e00:86b:3cf9:f2c1:72ae, Ping timeout: 276 seconds) | |
| 13:36 | kjackal_v2 has joined IRC (kjackal_v2!~quassel@athedsl-4546118.home.otenet.gr) | |
| 13:40 | GodFather has joined IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com) | |
| 13:52 | profesor has left IRC (profesor!58111e12@18.red-88-17-30.dynamicip.rima-tde.net, Remote host closed the connection) | |
| 13:58 | linux_user2 has left IRC (linux_user2!~Roger@71-38-215-105.lsv2.qwest.net) | |
| 13:59 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 14:06 | woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Ping timeout: 268 seconds) | |
| 14:33 | woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de) | |
| 14:50 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 15:36 | pppingme has left IRC (pppingme!~pppingme@unaffiliated/pppingme, Ping timeout: 240 seconds) | |
| 15:39 | pppingme has joined IRC (pppingme!~pppingme@unaffiliated/pppingme) | |
| 16:02 | eddyTV has left IRC (eddyTV!~eddyTV@unaffiliated/eddytv, Ping timeout: 245 seconds) | |
| 16:12 | kjackal_v2 has left IRC (kjackal_v2!~quassel@athedsl-4546118.home.otenet.gr, Ping timeout: 245 seconds) | |
| 16:17 | woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 16:40 | Nikoh77 has joined IRC (Nikoh77!~Nikoh77@host148-135-static.9-79-b.business.telecomitalia.it) | |
| 17:29 | statler_ has left IRC (statler_!~Georg@gwrz3.lohn24.de, Remote host closed the connection) | |
| 18:39 | woernie has joined IRC (woernie!~werner@x4d031d6f.dyn.telefonica.de) | |
| 18:41 | woernie has left IRC (woernie!~werner@x4d031d6f.dyn.telefonica.de, Remote host closed the connection) | |
| 18:45 | woernie has joined IRC (woernie!~werner@x4d031d6f.dyn.telefonica.de) | |
| 18:46 | woernie has left IRC (woernie!~werner@x4d031d6f.dyn.telefonica.de, Remote host closed the connection) | |
| 19:10 | woernie has joined IRC (woernie!~werner@x4d031d6f.dyn.telefonica.de) | |
| 19:26 | woernie has left IRC (woernie!~werner@x4d031d6f.dyn.telefonica.de, Remote host closed the connection) | |
| 19:26 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 19:48 | woernie has joined IRC (woernie!~werner@x4d031d6f.dyn.telefonica.de) | |
| 19:52 | woernie has left IRC (woernie!~werner@x4d031d6f.dyn.telefonica.de, Remote host closed the connection) | |
| 19:59 | section1 has left IRC (section1!~section1@178.33.109.106, Quit: Leaving) | |
| 20:25 | <alkisg> !syslog
| |
| 20:25 | <ltspbot> I do not know about 'syslog', but I do know about these similar topics: 'rsyslog'
| |
| 20:25 | <alkisg> !rsyslog
| |
| 20:25 | <ltspbot> rsyslog: To enable remote client logging in Ubuntu (it possibly also works on Debian), see https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/697387/comments/9
| |
| 20:27 | <alkisg> !forget rsyslog
| |
| 20:27 | <ltspbot> The operation succeeded.
| |
| 20:27 | <alkisg> !learn rsyslog as To enable remote client logging in Ubuntu (it possibly also works on Debian), see https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/697387/comments/10
| |
| 20:27 | <ltspbot> The operation succeeded.
| |
| 20:29 | <alkisg> !netconsole
| |
| 20:29 | <ltspbot> netconsole: To log LTSP client kernel messages (and crashes) on the server: https://ltsp.org/advanced/netconsole/
| |
| 21:21 | eddyTV has joined IRC (eddyTV!~eddyTV@unaffiliated/eddytv) | |
| 21:26 | bengoa has left IRC (bengoa!~alberto@194.50.55.200, Ping timeout: 240 seconds) | |
| 21:26 | <eddyTV> So, I was looking at https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt and saw that it supports a lot of "extra" options, including hostname and DNS server:
| |
| 21:26 | ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>:<dns0-ip>:<dns1-ip>:<ntp0-ip>
| |
| 21:48 | Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving) | |
| 21:48 | bengoa has joined IRC (bengoa!~alberto@194.50.55.200) | |
| 22:10 | <eddyTV> Does LTSP19 support all those nfsroot options?
| |
| 22:12 | <vagrantc> initramfs-tools supports most of them, not sure about dns and ntp
| |
| 22:13 | and ltsp19 on debian-based systems leverages initramfs-tools ... i think.
| |
| 22:38 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 246 seconds) | |
| 23:08 | <eddyTV> Hmm. I may give it a try. Alkis' answer in https://github.com/ltsp/community/issues/63#issuecomment-557908321 only goes up to <netmask>...
| |
| 23:16 | When a system is booted with GRUB, you can specify a `gfxmode` parameter, which GRUB uses (along with `gfxpayload`, https://www.gnu.org/software/grub/manual/grub/html_node/gfxpayload.html) to configure the video for the kernel so you can use something like https://wiki.debian.org/plymouth to get a "nice" screen while booting
| |
| 23:17 | Is there any way to do that with iPXE?
| |
| 23:57 | eu^copicomsoluti has joined IRC (eu^copicomsoluti!454679d6@69.70.121.214) | |
| 23:57 | <eu^copicomsoluti> Hello
| |
| 23:59 | eu^copicomsoluti has left IRC (eu^copicomsoluti!454679d6@69.70.121.214, Remote host closed the connection) | |