IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 7 June 2018 (all times are UTC)
| 00:05 | adrianor1 has joined IRC (adrianor1!~adrianorg@177.18.99.250) | |
| 00:07 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 00:08 | adrianorg has left IRC (adrianorg!~adrianorg@179.179.77.238, Ping timeout: 240 seconds) | |
| 00:15 | adrianor1 is now known as adrianorg | |
| 00:17 | lucascastro has joined IRC (lucascastro!~lucas@177-185-139-208.isotelco.net.br) | |
| 00:52 | gdi2k has left IRC (gdi2k!~gdi2k@180.191.113.3, Ping timeout: 260 seconds) | |
| 01:05 | gdi2k has joined IRC (gdi2k!~gdi2k@222.127.254.113) | |
| 01:16 | kjackal has left IRC (kjackal!~quassel@50-201-118-110-static.hfc.comcastbusiness.net, Ping timeout: 245 seconds) | |
| 01:22 | kjackal has joined IRC (kjackal!~quassel@50-201-118-110-static.hfc.comcastbusiness.net) | |
| 01:48 | kjackal has left IRC (kjackal!~quassel@50-201-118-110-static.hfc.comcastbusiness.net, Ping timeout: 276 seconds) | |
| 02:22 | gdi2k has left IRC (gdi2k!~gdi2k@222.127.254.113, Ping timeout: 248 seconds) | |
| 02:24 | cwinebrinner has joined IRC (cwinebrinner!~cwinebrin@173-16-225-56.client.mchsi.com) | |
| 02:26 | <cwinebrinner> is anyone using a RPi 3B+ as a thin client using TFTP and NBD?
| |
| 03:27 | cwinebrinner has left IRC (cwinebrinner!~cwinebrin@173-16-225-56.client.mchsi.com, Quit: Goodbye.) | |
| 04:22 | kjackal has joined IRC (kjackal!~quassel@50-201-118-110-static.hfc.comcastbusiness.net) | |
| 04:40 | kjackal has left IRC (kjackal!~quassel@50-201-118-110-static.hfc.comcastbusiness.net, Ping timeout: 240 seconds) | |
| 04:49 | derick_ has joined IRC (derick_!7aa838b0@gateway/web/freenode/ip.122.168.56.176) | |
| 04:55 | derick_ has left IRC (derick_!7aa838b0@gateway/web/freenode/ip.122.168.56.176, Quit: Page closed) | |
| 05:04 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Ping timeout: 240 seconds) | |
| 05:07 | Statler|Home has joined IRC (Statler|Home!~Georg@p54897F92.dip0.t-ipconnect.de) | |
| 05:19 | ricotz has joined IRC (ricotz!~ricotz@p5B2A8F9B.dip0.t-ipconnect.de) | |
| 05:19 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 06:19 | Statler|Home has left IRC (Statler|Home!~Georg@p54897F92.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 07:02 | alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg) | |
| 09:19 | gvy has joined IRC (gvy!~mike@altlinux/developer/mike) | |
| 09:45 | derick_ has joined IRC (derick_!ab3c92a0@gateway/web/freenode/ip.171.60.146.160) | |
| 09:54 | derick_ has left IRC (derick_!ab3c92a0@gateway/web/freenode/ip.171.60.146.160, Ping timeout: 260 seconds) | |
| 11:52 | damu^ubumate-lts has joined IRC (damu^ubumate-lts!3b5a6675@gateway/web/freenode/ip.59.90.102.117) | |
| 12:00 | Faith has joined IRC (Faith!~Paty_@unaffiliated/faith) | |
| 13:12 | lucascastro has left IRC (lucascastro!~lucas@177-185-139-208.isotelco.net.br, Ping timeout: 240 seconds) | |
| 13:20 | lucascastro has joined IRC (lucascastro!~lucas@177-185-139-176.isotelco.net.br) | |
| 13:22 | ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu) | |
| 13:34 | cvillasboa has left IRC (cvillasboa!c9d90c1a@gateway/web/freenode/ip.201.217.12.26, Ping timeout: 260 seconds) | |
| 13:47 | Faith_ has joined IRC (Faith_!~Paty_@2001:12d0:2080:200::231:49) | |
| 13:47 | Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Read error: Connection reset by peer) | |
| 13:47 | gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving) | |
| 14:15 | kjackal has joined IRC (kjackal!~quassel@50-201-118-110-static.hfc.comcastbusiness.net) | |
| 14:25 | derick_ has joined IRC (derick_!ab3c92a0@gateway/web/freenode/ip.171.60.146.160) | |
| 14:26 | cvillasboa has joined IRC (cvillasboa!c9d90c1a@gateway/web/freenode/ip.201.217.12.26) | |
| 14:26 | derick_ has left IRC (derick_!ab3c92a0@gateway/web/freenode/ip.171.60.146.160, Client Quit) | |
| 14:29 | <cvillasboa> good morning alkisg are you here?
| |
| 14:34 | <alkisg> cvillasboa: hello; for a bit....
| |
| 14:35 | <cvillasboa> it could be useful vnc-viewer for your connection?
| |
| 14:35 | <alkisg> !vnc-dide
| |
| 14:35 | <ltsp`> vnc-dide: To share your screen with me, run this: sudo apt-get --yes install x11vnc; x11vnc -connect srv1-dide.ioa.sch.gr - this is a reverse connection, it doesn't need port forwarding etc.
| |
| 14:36 | <cvillasboa> ok
| |
| 14:52 | alkisg: I already have x11vnc installed, I understand that this command should be executed below x11vnc -connect srv1-dide.ioa.sch.gr
| |
| 14:53 | <alkisg> Indeed
| |
| 14:53 | <cvillasboa> my query is where it should be executed, since my ltsp server is hosted in a virtualbox, inside my pc
| |
| 14:54 | Should I run it on my PC or in my VM?
| |
| 14:56 | <alkisg> What does your pc run, linux?
| |
| 14:57 | <cvillasboa> yes, Debian 9.3
| |
| 14:57 | <alkisg> OK, run it there then
| |
| 14:59 | <cvillasboa> perfect, we do it now or we leave it for the schedule that we established yesterday?
| |
| 14:59 | because now I have other tasks assigned
| |
| 15:00 | 8:30 is equivalent to 13:30 in my country
| |
| 15:01 | <alkisg> cvillasboa: 08:30 in the morning is night in your country :)
| |
| 15:01 | It was 10 hours ago
| |
| 15:03 | <cvillasboa> I'm sorry, I thought you told me at 8:30 in the night of your country, I think there was a misunderstanding.
| |
| 15:03 | we can do it when you tell me
| |
| 15:04 | <alkisg> (09:36:51 μμ) alkisg: cvillasboa: I'll be around 8:30 - 11:30 Greek timezone tomorrow
| |
| 15:04 | (09:37:06 μμ) alkisg: (morning)
| |
| 15:04 | cvillasboa: I need to go now, I don't think we can arrange a specific time due to big difference in our timezones
| |
| 15:04 | Just ping me and see when I'm available
| |
| 15:11 | <cvillasboa> Okay, I'll do it, but I'd like to know what time it is there, according to Google, it's 6:00 PM, right?
| |
| 15:12 | 6:11 PM
| |
| 15:13 | <alkisg> Right
| |
| 15:14 | So 8:30 in the morning was 10 hours ago
| |
| 15:20 | <cvillasboa> It really is difficult to establish a specific schedule because it is a big difference of time, it will be good to write to you when you are available nothing more, thanks for the help
| |
| 15:37 | alkisg: I have an idea, Monday in my country is a holiday, I could connect from my home to my personal computer according to their schedule, I have no problems to make an effort and be awake a couple of hours, the only problem I would have is to verify personally the thin client.
| |
| 15:38 | since I will not be at work
| |
| 15:41 | <alkisg> cvillasboa: no need to make things difficult; I'm around some of your mornings, we can just use vnc and a vm client
| |
| 15:41 | It's just that your mornings are afternoons here, so I have 10 mins available, then 1 hour busy, then 10 mins available etc
| |
| 15:46 | <cvillasboa> I understand you, let's see how it is presented tomorrow, to see if we achieve it
| |
| 16:22 | lucascastro has left IRC (lucascastro!~lucas@177-185-139-176.isotelco.net.br, Remote host closed the connection) | |
| 16:59 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 17:17 | <vagrantc> !nbd
| |
| 17:17 | <ltsp`> I do not know about 'nbd', but I do know about these similar topics: 'disable-nbd-proxy', 'nbd-proxy', 'nbd-compression', 'quick-nbd-tests', 'nbd-client', 'nbd-server-bug', 'nbd-trusty-bug', 'nbd-client-breaks-nm', 'nbd-bug', 'nbd-checkupdate'
| |
| 17:17 | <vagrantc> !nbd-checkupdate
| |
| 17:17 | <ltsp`> nbd-checkupdate: To avoid bug https://github.com/NetworkBlockDevice/nbd/issues/59, put this in lts.conf: INIT_COMMAND_RM_NBD_CHECKUPDATE="rm -rf /usr/share/ldm/rc.d/I01-nbd-checkupdate"
| |
| 17:45 | <alkisg> Eh, -r there isn't needed :D
| |
| 17:47 | <vagrantc> heh
| |
| 17:48 | alkisg: so, i'm working on updating the maintainer addresses for ltsp related packages in debian ... set up a team at https://tracker.debian.org/teams/ltsp/
| |
| 17:48 | alkisg: don't know if you're up for subscribing
| |
| 17:48 | alkisg: although maybe you're subscribed to individual packages?
| |
| 17:49 | <alkisg> vagrantc: I just got a mail and replied
| |
| 17:49 | Holger Levsen wrote: please reply
| |
| 17:49 | <vagrantc> alkisg: yes, heard through the grapevine :)
| |
| 17:49 | <alkisg> I'm up for subscribing, sure
| |
| 17:50 | I don't know how etc, but if you can subscribe me, go ahead
| |
| 17:50 | (brb in 30')
| |
| 18:05 | derick_ has joined IRC (derick_!ab3c92a0@gateway/web/freenode/ip.171.60.146.160) | |
| 18:09 | lucascastro has joined IRC (lucascastro!~lucas@201.182.221.154) | |
| 18:13 | <vagrantc> highvoltage: i see you didn't actually push ldm-themes to salsa ... working on that now ... should i update to use your debian.org email address while i'm at it?
| |
| 18:13 | <alkisg> vagrantc: back, checking the link...
| |
| 18:14 | <vagrantc> alkisg: i tried adding you, don't know if it worked. sent a test mail just now
| |
| 18:14 | alkisg: er, a bit ago
| |
| 18:15 | <alkisg> vagrantc: I think it worked; I'm having issues logging in though because of my expired alioth certificate
| |
| 18:15 | need_ltsp_help has joined IRC (need_ltsp_help!297284a1@gateway/web/freenode/ip.41.114.132.161) | |
| 18:15 | <alkisg> Trying...
| |
| 18:16 | <vagrantc> alkisg: and alioth is gone, too
| |
| 18:16 | <alkisg> Yeah, I tried to update it before it went down, and I couldn't
| |
| 18:17 | <vagrantc> i think there's a big todo item about that general issue
| |
| 18:18 | <alkisg> Heh, no user with that email given
| |
| 18:18 | I think that one was using my alkisg-guest@alioth email
| |
| 18:18 | <vagrantc> yeah, that's no good anymore :)
| |
| 18:18 | <derick_> vagrantc: alkisg: can I please get some help with my ltsp problem
| |
| 18:19 | <alkisg> Oh well I'll wait a bit, I'm sure they'll solve it for all of us noob dms :D
| |
| 18:19 | <vagrantc> !ask | echo derick_
| |
| 18:19 | <ltsp`> derick_ ask: Don't ask to ask a question, simply ask it, and if someone knows the answer, they'll respond. Please hang around for at least a full hour after asking a question, as not everybody constantly monitors the channel.
| |
| 18:20 | <derick_> vagrantc: I am unable to login with my user from ltsp client - https://www.youtube.com/watch?v=4ue23MVEd9g&t=9s
| |
| 18:20 | made a video about it.
| |
| 18:21 | <vagrantc> could you describe the issue, rather than just a video?
| |
| 18:21 | <derick_> yes. I am able to boot from the client. but when I login it says public key denied
| |
| 18:22 | <alkisg> Yey! After trying really really hard, I managed to read the email with the 3 lines saying "if you don't have an account, register" :P :D
| |
| 18:24 | vagrantc: I see that I can subscribe both to source or binary packages. If I only subscribe to source packages, do I get notifications for binary package bug reports?
| |
| 18:24 | <vagrantc> alkisg: i thought bugs were a separate issue
| |
| 18:25 | <highvoltage> vagrantc: hmm odd, ok yes please
| |
| 18:25 | <vagrantc> highvoltage: jcc ?
| |
| 18:25 | <alkisg> vagrantc: I'm not sure I understand what "subscribe to binary packaging" means then....
| |
| 18:26 | <vagrantc> alkisg: i think it means package uploads ... e.g. you'll get a notice for every architecture when it completes building
| |
| 18:27 | <highvoltage> vagrantc: yep
| |
| 18:27 | vagrantc: sorry been juggling a bunch of things the last two weeks so I got some wires crossed here and there
| |
| 18:28 | <vagrantc> highvoltage: don't we all. :)
| |
| 18:29 | <derick_> I would need help with this issue. I have ltsp-pnp setup on debian buster vagrant box
| |
| 18:30 | I am able to boot. but not able to login. It says public key denied
| |
| 18:30 | <alkisg> vagrantc: do we need to do the same with "Debian Epoptes Maintainers"?
| |
| 18:32 | <vagrantc> derick_: not sure how that would happen with ltsp-pnp...
| |
| 18:32 | lucascastro has left IRC (lucascastro!~lucas@201.182.221.154, Remote host closed the connection) | |
| 18:33 | <vagrantc> alkisg: i think that's using the launchpad list ... which has other issues which arguably make it non-compliant ...
| |
| 18:35 | <alkisg> How do you feel about MS aquiring github? More points for keeping ltsp in launchpad? :D
| |
| 18:38 | <vagrantc> heh
| |
| 18:44 | <derick_> vagrantc : okay, If I could get a little information on how ltsp users ssh keys. then maybe I will be able to solve this one
| |
| 18:45 | <vagrantc> derick_: users don't typically use keys, but there should be a list of host keys in /etc/ltsp/ssh_known_hosts, if i'm remembering correctly
| |
| 18:46 | derick_: do you have lts.conf configured with SERVER= ?
| |
| 18:46 | derick_: in general, that should be unecessary, and sometimes breaks things like this
| |
| 18:47 | kjackal has left IRC (kjackal!~quassel@50-201-118-110-static.hfc.comcastbusiness.net, Remote host closed the connection) | |
| 18:47 | <derick_> vagrantc : okay, on my server there are only 2 files in /etc/ltsp ltsp-update-image.excludes update-kernels.conf
| |
| 18:48 | <vagrantc> derick_: er, /etc/ssh/ssh_known_hosts
| |
| 18:48 | derick_: also, lts.conf is typically served from tftp directory, not /etc anymore
| |
| 18:49 | <derick_> vagrantc : there is no ssh_known_hosts in /etc/ssh maybe this is the issue
| |
| 18:50 | <vagrantc> derick_: ltsp-update-image should run ltsp-update-sshkeys which should generate it
| |
| 18:52 | <derick_> vagrantc : okay. I will try this. It takes a little bit time to update image. I hope I dont waste your much time
| |
| 18:54 | derick_ has left IRC (derick_!ab3c92a0@gateway/web/freenode/ip.171.60.146.160, Quit: Page closed) | |
| 18:55 | <vagrantc> ugh.
| |
| 18:55 | basically, i'm confused how you created an image that boots without the ssh_known_hosts file ... but
| |
| 18:55 | * vagrantc sighs | |
| 18:56 | lucascastro has joined IRC (lucascastro!~lucas@201.182.221.154) | |
| 18:58 | epoptes_user5 has joined IRC (epoptes_user5!be62f89a@gateway/web/freenode/ip.190.98.248.154) | |
| 18:59 | <epoptes_user5> hello ?
| |
| 18:59 | kjackal has joined IRC (kjackal!~quassel@50-201-118-110-static.hfc.comcastbusiness.net) | |
| 18:59 | derick_ has joined IRC (derick_!ab3c92a0@gateway/web/freenode/ip.171.60.146.160) | |
| 19:01 | <derick_> for some reason ssh_known_hosts is not created
| |
| 19:02 | vagrantc : I am following this -dashohoxha.fs.al/ltsp-pnp/
| |
| 19:02 | <alkisg> epoptes_user5: hi
| |
| 19:03 | <derick_> ltsp-pnp is setup on vagrant box so maybe there are some issues.
| |
| 19:04 | <epoptes_user5> i was using epoptes normally , everything working perfect....until a blackout
| |
| 19:04 | now , all my configuration dissapear
| |
| 19:04 | <vagrantc> derick_: i've never used vagrant, no idea what could be wrong
| |
| 19:05 | <alkisg> epoptes_user5: do you mean ~/.config/epoptes/settings.json?
| |
| 19:05 | What do you have in that folder? Open them with an editor and see
| |
| 19:05 | cvillasboa has left IRC (cvillasboa!c9d90c1a@gateway/web/freenode/ip.201.217.12.26, Ping timeout: 260 seconds) | |
| 19:07 | <epoptes_user5> in the epoptes folder , just 2 files (groups.json - settings)
| |
| 19:08 | <alkisg> Do they have the data you're looking for?
| |
| 19:08 | Open them with gedit/pluma/vi something
| |
| 19:08 | <epoptes_user5> just the default info , both
| |
| 19:08 | <vagrantc> derick_: the instructions in the howto you're following seem a bit strange for configuring dnsmasq
| |
| 19:09 | derick_: not that that will solve your ssh key issue
| |
| 19:09 | derick_: does the server have /etc/ssh/ssh_host* ?
| |
| 19:09 | <alkisg> epoptes_user5: So the problem is that you had settings in those files, then you had a blackout, and then they were re-created and you lost your settings?
| |
| 19:10 | <derick_> vagrantc : yes, server has those
| |
| 19:10 | <epoptes_user5> yes, and the new settings doesn't keep in
| |
| 19:10 | <vagrantc> derick_: is ldm-server installed?
| |
| 19:10 | <alkisg> epoptes_user5: maybe you run sudo epoptes and they were chowned to root? Can you modify them with gedit?
| |
| 19:11 | <vagrantc> derick_: and you run ltsp-update-sshkeys ... and it doesn't create /etc/ssh/ssh_known_hosts ?
| |
| 19:11 | <derick_> vagrantc : no its not installed. Is it really important?
| |
| 19:11 | <vagrantc> derick_: ldm-server is pretty important for ldm clients to be able to log in, yes.
| |
| 19:11 | <derick_> vagrantc : I used same step and am able to boot from ubuntu 14 trusty box
| |
| 19:12 | <vagrantc> derick_: maybe ubuntu 14 trusty has some random packages installed that satisfy the very barebones minimal dependencies
| |
| 19:12 | <epoptes_user5> both files had "644" permissions
| |
| 19:12 | <vagrantc> derick_: you're probably missing a bunch of dependencies
| |
| 19:12 | derick_: which is why we have the ldm-server package
| |
| 19:13 | derick_: along with a few things that make session selection, language selection, etc. possible
| |
| 19:13 | <derick_> vagrantc : okay. It is possible. I will install ldm-server.
| |
| 19:13 | <vagrantc> though it should still generate ssh_known_hosts regardless, if the host keys are present
| |
| 19:14 | <derick_> vagrant : will it solve the public key denied issue?
| |
| 19:14 | <vagrantc> derick_: try it and find out ? :P
| |
| 19:14 | derick_: it might be a bad error message; something else might be wrong
| |
| 19:15 | <derick_> I hope it works. Thank you
| |
| 19:16 | vagrantc : I still have 2 days to solve this. Or else I may on my gsoc project on ltsp.
| |
| 19:18 | <epoptes_user5> #solved : chmod .....
| |
| 19:18 | thnx !!
| |
| 19:20 | <need_ltsp_help> hello
| |
| 19:22 | when using a fat client, is proccessing done only on the client or on the server too?
| |
| 19:25 | <vagrantc> fat clients run everything locally, though the home directories are mounted from the server
| |
| 19:26 | <alkisg> epoptes_user5: it sounds like your ~/.config or other folder is broken, maybe owned by root.
| |
| 19:26 | find ~ -uid 0
| |
| 19:27 | <need_ltsp_help> thanks
| |
| 19:30 | derick_ has left IRC (derick_!ab3c92a0@gateway/web/freenode/ip.171.60.146.160, Quit: Page closed) | |
| 19:36 | derick_ has joined IRC (derick_!ab3c92a0@gateway/web/freenode/ip.171.60.146.160) | |
| 19:36 | kjackal has left IRC (kjackal!~quassel@50-201-118-110-static.hfc.comcastbusiness.net, Ping timeout: 264 seconds) | |
| 20:06 | lucascastro has left IRC (lucascastro!~lucas@201.182.221.154, Remote host closed the connection) | |
| 20:14 | need_ltsp_help has left IRC (need_ltsp_help!297284a1@gateway/web/freenode/ip.41.114.132.161, Quit: Page closed) | |
| 20:19 | derick_ has left IRC (derick_!ab3c92a0@gateway/web/freenode/ip.171.60.146.160, Quit: Page closed) | |
| 20:37 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 20:42 | kjackal has joined IRC (kjackal!~quassel@50-201-118-110-static.hfc.comcastbusiness.net) | |
| 20:44 | lucascastro has joined IRC (lucascastro!~lucas@177-185-139-176.isotelco.net.br) | |
| 20:45 | Faith_ has left IRC (Faith_!~Paty_@2001:12d0:2080:200::231:49, Quit: Leaving) | |
| 20:58 | kjackal has left IRC (kjackal!~quassel@50-201-118-110-static.hfc.comcastbusiness.net, Ping timeout: 260 seconds) | |
| 20:58 | kjackal has joined IRC (kjackal!~quassel@50-201-118-110-static.hfc.comcastbusiness.net) | |
| 21:20 | <vagrantc> so glad i added support for lz4 compression ... "ltsp-update-image --cleanup --compression=lz4 /" is a bit larger resulting image, but *much* faster to build
| |
| 21:21 | e.g. 780MB image vs. 1040MB
| |
| 21:23 | * vagrantc wonders if it's worth adding zstd too | |
| 21:24 | <vagrantc> 0m18.476s with lz4 ... testing mksquashfs default (gzip?) ....
| |
| 21:26 | epoptes_user5 has left IRC (epoptes_user5!be62f89a@gateway/web/freenode/ip.190.98.248.154, Ping timeout: 260 seconds) | |
| 21:27 | <vagrantc> real 4m5.731s with default/gzip
| |
| 21:27 | that's worth 250MB of disk space
| |
| 21:28 | zstd apparently isn't yet available in mksquashfs (at least not the version in debian)
| |
| 21:28 | but it's in the kernel
| |
| 21:46 | derick_ has joined IRC (derick_!b64680d6@gateway/web/freenode/ip.182.70.128.214) | |
| 22:03 | ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection) | |
| 22:18 | kjackal has left IRC (kjackal!~quassel@50-201-118-110-static.hfc.comcastbusiness.net, Remote host closed the connection) | |
| 23:08 | <derick_> lz4 compression works perfectly :)
| |
| 23:09 | <vagrantc> almost wonder if it shouldn't be the default...
| |
| 23:11 | <derick_> yeah
| |
| 23:13 | <vagrantc> it's over an order of magnitude faster for only 20-30% reduction in compression
| |
| 23:13 | * vagrantc wonders how widely supported it is across distro versions | |
| 23:14 | <vagrantc> oh, it's not even an option for debian stable, without using a backports kernel
| |
| 23:14 | so let's leave the default as is ... but document lz4 support :)
| |
| 23:15 | <derick_> I can test them on distro. If you want
| |
| 23:17 | <vagrantc> should wait until buster releases, at least ... maybe longer
| |
| 23:18 | would be good to get CONFIG_SQUASHFS_LZ4=y into all the distros now, though (and zstd too, if possible)
| |
| 23:19 | defaults should generally be the lowest common denominator
| |
| 23:20 | or a more complicated approach is to detect the combinations supported by the server and client, and enable selectively ... but probably not worth it
| |
| 23:21 | but the server needs support in mksquashfs, and the client needs support in the kernel
| |
| 23:21 | at minimum
| |
| 23:24 | <derick_> vagrantc : I have installed ldm-server and updated the image.
| |
| 23:24 | there are significant improvments in UI of client. But still unable to boot
| |
| 23:27 | <vagrantc> how can you see the UI if it can't boot? :P
| |
| 23:27 | !shell
| |
| 23:27 | <ltsp`> I do not know about 'shell', but I do know about these similar topics: 'shell-screen', 'gnome-shell'
| |
| 23:28 | <vagrantc> !shell-screen | echo derick_
| |
| 23:28 | <ltsp`> derick_ shell-screen: One way to get local root access to troubleshoot a thin client is to use a shell SCREEN: https://help.ubuntu.com/community/UbuntuLTSP/ClientTroubleshooting#Using%20a%20shell%20SCREEN
| |
| 23:28 | <vagrantc> oh... i don't know about that one
| |
| 23:28 | that should really just tell you the line to add to lts.conf
| |
| 23:29 | <derick_> vagrantc : Sorry I meant unable to login. I am able to boot :p
| |
| 23:30 | <vagrantc> !learn shell-screen as to enable a root debug shell, add SCREEN_02=shell and SCREEN_07=ldm to lts.conf
| |
| 23:30 | <ltsp`> The operation succeeded.
| |
| 23:30 | <vagrantc> !shell-screen
| |
| 23:30 | <ltsp`> shell-screen: (#1) One way to get local root access to troubleshoot a thin client is to use a shell SCREEN: https://help.ubuntu.com/community/UbuntuLTSP/ClientTroubleshooting#Using%20a%20shell%20SCREEN, or (#2) to enable a root debug shell, add SCREEN_02=shell and SCREEN_07=ldm to lts.conf
| |
| 23:31 | <vagrantc> !root
| |
| 23:31 | <ltsp`> I do not know about 'root', but I do know about these similar topics: 'ROOT_PASSWORD_HASH'
| |
| 23:31 | <vagrantc> !root_password_hash
| |
| 23:31 | <ltsp`> root_password_hash: To be able to login as root in vt1, with password "qwer1234", put this in lts.conf: INIT_COMMAND_ROOT_HASH="sed 's!^root:[^:]*:!root:\$6\$p2LdWE6j\$PDd1TUzGvvIkj9SE8wbw1gA/MD66tHHlStqi1.qyv860oK47UnKcafSKqGp7cbgZUPlgyPv6giCVyCSCdJt1b0:!' -i /etc/shadow"
| |
| 23:31 | <vagrantc> that's another option
| |
| 23:32 | <derick_> okay. I will try these too.
| |
| 23:33 | derick_ has left IRC (derick_!b64680d6@gateway/web/freenode/ip.182.70.128.214, Quit: Page closed) | |
| 23:34 | <vagrantc> you don't need to reboot to try any of those...
| |
| 23:35 | derick_ has joined IRC (derick_!b64680d6@gateway/web/freenode/ip.182.70.128.214) | |
| 23:36 | <derick_> Sure. I will not reboot.
| |