IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 15 December 2017 (all times are UTC)
| 00:01 | GodFather has joined IRC (GodFather!~rcc@47.33.250.142) | |
| 00:10 | GodFather has left IRC (GodFather!~rcc@47.33.250.142, Ping timeout: 248 seconds) | |
| 02:32 | lucascastro has joined IRC (lucascastro!~lucas@189.90.39.144.jupiter.com.br) | |
| 02:36 | lucas_ has joined IRC (lucas_!~lucas@201.182.221.14) | |
| 02:38 | lucascastro has left IRC (lucascastro!~lucas@189.90.39.144.jupiter.com.br, Ping timeout: 272 seconds) | |
| 03:01 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 255 seconds) | |
| 03:36 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 04:38 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 05:13 | onixx has joined IRC (onixx!1000@bas1-stetherese38-174-91-240-137.dsl.bell.ca) | |
| 05:15 | <onixx> good evening everyone. I am trying to set the LANGUAGE variable to fr_CA:fr can this be done in lts.conf ?
| |
| 05:22 | bitchecker has left IRC (bitchecker!~bitchecke@31.131.20.132, Ping timeout: 248 seconds) | |
| 05:25 | bitchecker has joined IRC (bitchecker!~bitchecke@31.131.20.132) | |
| 05:38 | <alkisg> onixx: LDM_LANGUAGE=fr_CA:fr
| |
| 05:42 | <onixx> alkisg: thanks. I have tried this and it does not work.. for some reasons, this sets the LANG variable
| |
| 05:42 | alkisg: then LANGUAGE variable is left untouched whatever I do
| |
| 05:42 | <alkisg> onixx: hmm yeah you're probably right
| |
| 05:42 | Btw, why do you need to set the LANGUAGE, isn't LANG enough?
| |
| 05:43 | For example, display managers only allow setting LANG, not LANGUAGE...
| |
| 05:44 | <onixx> looks like its not... unless I am doing something wrong... I installed xfce4 and it is 50% french ;-) for some reasons
| |
| 05:44 | <alkisg> Are you using a chroot, or ltsp-pnp?
| |
| 05:44 | What's the output of sudo ltsp-info
| |
| 05:44 | <onixx> alkisg: a chroot
| |
| 05:44 | <alkisg> OK
| |
| 05:45 | So run: sudo ltsp-chroot check-language-support
| |
| 05:45 | What's the output of that? Put it to pastebin
| |
| 05:45 | <onixx> don't have that command...check-language-support
| |
| 05:46 | <alkisg> Ah sorry, are you using thin clients or fat clients?
| |
| 05:46 | <onixx> thin
| |
| 05:46 | <alkisg> ok... why? :D
| |
| 05:46 | What's the output of this, directly on the server then? check-language-support
| |
| 05:47 | <onixx> alkisg: testing for now
| |
| 05:47 | not much firefox-locale-en firefox-locale-fr language-pack-en language-pack-gnome-en language-pack-gnome-fr wamerican wbritish wfrench ... probably missing something with xfce4
| |
| 05:48 | <alkisg> Those are localization packages that you're missing
| |
| 05:48 | run sudo apt install $(check-language-support) on the server
| |
| 05:48 | Then try again to login on the thin client
| |
| 05:49 | <onixx> alkisg: makes a lot of sense !
| |
| 05:49 | <alkisg> :)
| |
| 05:52 | <onixx> alkisg: alkisg : weird... still not 100%.
| |
| 05:53 | <alkisg> And is it 100% on the server itself?
| |
| 05:53 | <onixx> alkisg: server is english. (ubuntu server, no X)
| |
| 05:53 | alkisg: well it has X now but never ran it
| |
| 05:54 | <alkisg> onixx: ok, how can we learn if it's missing translations in ubuntu in general, or if it's an issue with ltsp?
| |
| 05:54 | E.g. do you have another installation without ltsp that actually has all the translations?
| |
| 05:56 | <onixx> alkisg: hold on :-) I did a LOT of screwing around... let restore the VM and try this again
| |
| 06:01 | alkisg: ok, I am restored now.. I have added the LANG and LDM_LANGUAGE vars in lts.conf
| |
| 06:01 | alkisg: adding language-pack-fr now
| |
| 06:03 | now running sudo apt install $(check-language-support)...
| |
| 06:06 | alkisg: I am installing language-pack-fr in the chroot too right ?
| |
| 06:10 | alkisg: ok, I am back up. the login screen is in french
| |
| 06:11 | alkisg: and only some parts of xfce4 are french. most of it is in english
| |
| 06:12 | <alkisg> onixx: have you ran xfce4 anywhere else and saw that it's translated in french?
| |
| 06:12 | Because if it's not, ...it's not an ltsp issue :D
| |
| 06:12 | <onixx> alkisg: ok, now, there's one way to get it in french all the way on the thinclient
| |
| 06:13 | i change /etc/default/locale and modify the language var
| |
| 06:13 | <alkisg> Normally /etc/default/locale does not contain a LANGUAGE var
| |
| 06:14 | So the correct way would be to delete it
| |
| 06:14 | <onixx> alkisg: ok. I will try that. this is from the vanilla installation of ubuntu 16.04
| |
| 06:14 | <alkisg> Which one, server or desktop .iso?
| |
| 06:14 | <onixx> server
| |
| 06:14 | <alkisg> And you didn't manually edit that file/
| |
| 06:15 | Statler has joined IRC (Statler!~Georg@p5B30E7CF.dip0.t-ipconnect.de) | |
| 06:15 | <alkisg> ?
| |
| 06:15 | Btw, ltsp assumes a desktop installation
| |
| 06:15 | !ltsp-manager
| |
| 06:15 | <ltsp> ltsp-manager: LTSP Manager is a GUI tool that makes LTSP maintenance easy. It's the recommended way to install LTSP in common setups. More info: http://wiki.ltsp.org/wiki/Ltsp-manager
| |
| 06:15 | <onixx> alkisg: well, I just restored to vm to the point where I started to screw witn language
| |
| 06:15 | <alkisg> This ^ is the usual way to install ltsp
| |
| 06:15 | <onixx> alkisg: so the file was likely like this but I can confirm later... deleting the entry for now
| |
| 06:17 | alkisg: hah !
| |
| 06:18 | alkisg: work well now ! language is now unset on the thin and xfce is in french
| |
| 06:18 | <alkisg> Cool
| |
| 06:18 | <onixx> alkisg: let me boot the vm before I installed anything on it (really, just after the initial ubuntu install...) I want to check that file
| |
| 06:20 | alkisg: its there...
| |
| 06:21 | alkisg: possibly because of locale selection during install
| |
| 06:21 | <alkisg> onixx: it's not for me (Greek, desktop installation with locale selection)
| |
| 06:21 | Either french does something differently, or the server iso
| |
| 06:23 | <onixx> alkisg: could be the server iso ... its says # File generated by update-locale in the header
| |
| 06:23 | <alkisg> Same here from the desktop iso
| |
| 06:24 | <onixx> alkisg: odd... at least found why ... thanks so much for this
| |
| 06:25 | <alkisg> np
| |
| 06:26 | The most important thing to look for though is why you're using a server installation with a chroot
| |
| 06:26 | Instead of the most common installation methods like ltsp-pnp, ltsp-manager etc
| |
| 06:26 | And why you're using thin clients instead of diskless ltsp fat clients
| |
| 06:28 | <onixx> alkisg: no, for sure I did not... on the VM I just checked, it was just after setup completed of the server iso
| |
| 06:28 | alkisg: sorry, up arrow...
| |
| 06:28 | <alkisg> :)
| |
| 06:30 | <onixx> alkisg: for fat or thin, I am still not sure what I will do, I have a bunch of old thin clients that I want to be able to use
| |
| 06:30 | <alkisg> which cpu exactly and how much ram?
| |
| 06:30 | <onixx> alkisg: I may or may not end up doing it
| |
| 06:30 | alkisg: old wyse .. very slow to run any browser
| |
| 06:31 | <alkisg> OK, thin then. Nothing newer there that could benefit from a fat chroot? All clients are thin?
| |
| 06:31 | <onixx> alkisg: not sure what cpu and all yet, I need to look into them... I had a fat setup too which was working
| |
| 06:31 | <alkisg> OK; a fat setup serves thins as well without difference
| |
| 06:32 | <onixx> alkisg: had both up and running, yes, I had installed apps inside the chroot and was working too
| |
| 06:32 | alkisg: played arounf with the ram variable
| |
| 06:33 | alkisg: reason I went without a gui on the server just because it runs on a vm and I just ssh to it for now
| |
| 06:34 | <alkisg> onixx: you installed a desktop environment, so now it's the same as if you had installed a desktop iso
| |
| 06:34 | I.e. you just followed a weird installation path without reason :)
| |
| 06:34 | (and maybe having bad sideeffects like the language)
| |
| 06:35 | kjackal has joined IRC (kjackal!~quassel@2a02:587:3100:c900:d8d2:1956:e358:88e1) | |
| 06:35 | <onixx> alkisg: haha, well, I started 20 years ago on slackware... I like the command line
| |
| 06:36 | <alkisg> The command line is fine. Following uncommon installation methods and bumping into additional bugs... isn't :D
| |
| 06:37 | LTSP developers test and recommend a couple of installation methods, if you use uncommon ones, you bump into bugs that noone has seen...
| |
| 06:37 | <onixx> alkisg: well, I pretty much followed ltsp-pnp
| |
| 06:38 | <alkisg> Ehhh no, ltsp-pnp doesn't use a chroot
| |
| 06:40 | <onixx> alkisg: I may redo ... really, at this time I do nothing with the chroot other than generating my image
| |
| 06:41 | alkisg: thanks for everything
| |
| 06:41 | <alkisg> You're welcome
| |
| 06:41 | <onixx> alkisg: got to go now, REALLY appreciated. have a great night
| |
| 06:41 | onixx has left IRC (onixx!1000@bas1-stetherese38-174-91-240-137.dsl.bell.ca, Quit: leaving) | |
| 07:24 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 07:25 | Statler has left IRC (Statler!~Georg@p5B30E7CF.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 07:33 | kjackal has left IRC (kjackal!~quassel@2a02:587:3100:c900:d8d2:1956:e358:88e1, Remote host closed the connection) | |
| 07:38 | jeremies has joined IRC (jeremies!5b7ef0a7@gateway/web/freenode/ip.91.126.240.167) | |
| 07:40 | fuzzmew has joined IRC (fuzzmew!~fuzzmew@96.18.71.242) | |
| 07:40 | <jeremies> There is some hardware (like a better network card or something) to increase the speed of the video in thin clients?
| |
| 07:41 | <fuzzmew> Hello, is it possible to get ltsp working on mint linux?
| |
| 07:47 | <alkisg> jeremies: yes, gigabit network cards display video better than 100 mbps network cards
| |
| 07:47 | fuzzmew: yes, linux mint should work fine with ltsp
| |
| 07:47 | Although ubuntu-mate is better, as it's an official ubuntu flavor
| |
| 07:47 | <fuzzmew> I have tried literally everything and it just won't connect.
| |
| 07:48 | <alkisg> Mention specific error messages etc
| |
| 07:48 | "won't connect" maybe even refer to " you didn't put the power plug to the client"
| |
| 07:48 | !ltsp-manager
| |
| 07:48 | <ltsp> ltsp-manager: LTSP Manager is a GUI tool that makes LTSP maintenance easy. It's the recommended way to install LTSP in common setups. More info: http://wiki.ltsp.org/wiki/Ltsp-manager
| |
| 07:48 | <alkisg> !ltsp-pnp
| |
| 07:48 | <ltsp> ltsp-pnp: ltsp-pnp is the recommented method to install and maintain LTSP for "usual" setups. Since it doesn't involve chroots, it requires little to no command line to maintain it. It automatically supports both thin and fat ltsp clients. https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
| |
| 07:48 | <alkisg> These are the 2 best tutorials to get ltsp up and running, including on linux mint
| |
| 07:48 | <fuzzmew> Oops. Ok, the client just spins at the DHCP and never connects to the server
| |
| 07:49 | <alkisg> Then this isn't related to mint or not, since the OS hasn't even loaded yet
| |
| 07:49 | <fuzzmew> tried pnp, no joy
| |
| 07:49 | <alkisg> It's just misconfigured dhcp/tftp etc
| |
| 07:49 | So take it from the start. Are you currently using an ltsp-pnp setup?
| |
| 07:49 | <fuzzmew> Yes, typed in everything it told me to.
| |
| 07:50 | <alkisg> OK, then run this:
| |
| 07:50 | !vnc-edide
| |
| 07:50 | <ltsp> vnc-edide: To share your screen with me, open Epoptes → Help menu → Remote support → Host: srv1-dide.ioa.sch.gr, and click the Connect button
| |
| 07:54 | <fuzzmew> Remote support: no such option
| |
| 07:54 | <alkisg> Hmmm
| |
| 07:54 | !vnc-dide
| |
| 07:54 | <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.
| |
| 07:54 | <alkisg> Try this then ^
| |
| 07:54 | x11vnc should already be installed
| |
| 07:56 | <jeremies> alkisg: thank you!
| |
| 08:00 | <alkisg> fuzzmew: eeer this isn't an ltsp-pnp setup :D
| |
| 08:00 | You have isc-dhcp server installed, a bad ltsp.conf in dnsmasq etc etc
| |
| 08:01 | ...shall I fix a couple of things there, uninstall etc?
| |
| 08:01 | <fuzzmew> That is strange, I could swear I put in the pnp one, I will try it and report back if you want
| |
| 08:01 | <alkisg> fuzzmew: and you have a chroot, ltsp-pnp doesn't use a chroot
| |
| 08:02 | fuzzmew: so yeah please start over, using this tutorial:
| |
| 08:02 | !ltsp-manager
| |
| 08:02 | <ltsp> ltsp-manager: LTSP Manager is a GUI tool that makes LTSP maintenance easy. It's the recommended way to install LTSP in common setups. More info: http://wiki.ltsp.org/wiki/Ltsp-manager
| |
| 08:02 | jeremies has left IRC (jeremies!5b7ef0a7@gateway/web/freenode/ip.91.126.240.167, Quit: Page closed) | |
| 08:02 | <alkisg> use the mint version that corresponds to ubuntu 16.04 lts
| |
| 08:05 | fuzzmew: try booting a client
| |
| 08:06 | <fuzzmew> ok
| |
| 08:07 | dang. still at DHCP not finding it
| |
| 08:07 | <alkisg> I don't see a dhcp request
| |
| 08:07 | Is it connected to the 192.168.1.x network?
| |
| 08:07 | <fuzzmew> yes
| |
| 08:15 | <alkisg> fuzzmew: any idea why dnsmasq isn't listening on proxydhcp ranges?
| |
| 08:15 | Did you modify something to block it?
| |
| 08:15 | <fuzzmew> I have no idea, not to my knowledge
| |
| 08:16 | <alkisg> (you did modify a lot of .conf files there... :D)
| |
| 08:20 | fuzzmew: wow that was a quite broken setup :D
| |
| 08:21 | It's like you copy/pasted half the pages from 10 tutorials
| |
| 08:21 | <fuzzmew> It seems to be my poopy luck :(
| |
| 08:21 | <alkisg> ...not following one; but 10 half ones :D
| |
| 08:21 | <fuzzmew> oh boogers
| |
| 08:21 | <alkisg> I think you just need to focus on following ONE tutorial, not many
| |
| 08:21 | Btw now your DNS may be broken
| |
| 08:21 | Check after reboot if it works or not
| |
| 08:22 | <fuzzmew> Ok, reboot server now.
| |
| 08:22 | <alkisg> OK
| |
| 08:23 | Time for me to go; I'll be back later...
| |
| 08:23 | <fuzzmew> ok will reboot now
| |
| 08:23 | <alkisg> I'd suggest doing a clean install while following this:
| |
| 08:23 | !ltsp-manager
| |
| 08:23 | <ltsp> ltsp-manager: LTSP Manager is a GUI tool that makes LTSP maintenance easy. It's the recommended way to install LTSP in common setups. More info: http://wiki.ltsp.org/wiki/Ltsp-manager
| |
| 08:23 | <alkisg> ...follow exactly what it says :)
| |
| 08:24 | <fuzzmew> well, I guess I gotta backup my home directory
| |
| 08:24 | <alkisg> You can install ubuntu while leaving /home there
| |
| 08:24 | But whatever suits you best
| |
| 08:24 | <fuzzmew> oh do you mean "install alongside" option?
| |
| 08:25 | <alkisg> No, there's an option for "manual specify where to install",and if you select an already existing partition, it just removes /usr etc, leaving home intact
| |
| 08:25 | Google it
| |
| 08:25 | <fuzzmew> u dare me? :)
| |
| 08:25 | hehe
| |
| 08:25 | <alkisg> :D
| |
| 08:25 | <fuzzmew> will do.
| |
| 08:25 | * alkisg waves, later... | |
| 08:25 | <fuzzmew> A google dare. Later and thank you very much
| |
| 08:25 | <alkisg> np
| |
| 08:31 | fuzzmew has left IRC (fuzzmew!~fuzzmew@96.18.71.242, Quit: Leaving) | |
| 09:05 | fuzzmew has joined IRC (fuzzmew!~fuzzmew@96-18-71-242.cpe.cableone.net) | |
| 09:06 | <fuzzmew> Is this the correct page? https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
| |
| 09:07 | I have done re install and that is it
| |
| 09:27 | Well im gonna take the plunge on this one, and if it don't work, I won't paste anything in it or try to fix it, I will let you have a look at it instead.
| |
| 09:34 | wait, I found the ltsp manager page. I'm going for that suggested one first.
| |
| 09:44 | Process stopped: client does not boot
| |
| 09:54 | https://pastebin.com/CDMfAhnR
| |
| 10:09 | neil_ has joined IRC (neil_!~neil@robert491.lnk.telstra.net) | |
| 10:09 | Didier_Spaier has joined IRC (Didier_Spaier!~didier@2a01:e34:ec0b:630:8575:f9d2:7159:b93a) | |
| 10:09 | <neil_> I have a LTSP setup, but some of the logins are using Gnome, and some are using Mate, how do I make all use the Mate desktop?
| |
| 10:38 | neil_ has left IRC (neil_!~neil@robert491.lnk.telstra.net, Remote host closed the connection) | |
| 10:52 | Didier_Spaier has left IRC (Didier_Spaier!~didier@2a01:e34:ec0b:630:8575:f9d2:7159:b93a) | |
| 12:26 | kjackal has joined IRC (kjackal!~quassel@2a02:587:3100:c900:d8d2:1956:e358:88e1) | |
| 12:41 | lucas_ has left IRC (lucas_!~lucas@201.182.221.14, Ping timeout: 272 seconds) | |
| 12:47 | GodFather has joined IRC (GodFather!~rcc@47.33.250.142) | |
| 12:57 | Statler has joined IRC (Statler!~Georg@gwrz3.lohn24.de) | |
| 14:07 | gvy has joined IRC (gvy!~mike@altlinux/developer/mike) | |
| 14:58 | <alkisg> fuzzmew: mint has "install recommends" disabled by default, against debian policy (breaking yet another thing)
| |
| 14:59 | When installing ltsp and the rest of the packages, use the "--install-recommends" parameter
| |
| 15:10 | Da-Geek has joined IRC (Da-Geek!~Da-Geek@88.98.209.152) | |
| 15:22 | <bcg> Is there a way to lock screen on fat client, running gnome shell? If I install gnome-screensaver, locking works, but unlock doesn't. This is probably because my terminal user doesn't have password in /etc/shadow in client, it's only on server.
| |
| 15:23 | Current gnome shell uses gdm to lock screen, but ldm doesn't support that.
| |
| 15:26 | <alkisg> !password
| |
| 15:26 | <ltsp> I do not know about 'password', but I do know about these similar topics: 'ROOT_PASSWORD_HASH', 'LDM_PASSWORD_HASH'
| |
| 15:26 | <alkisg> !LDM_PASSWORD_HASH
| |
| 15:26 | <ltsp> LDM_PASSWORD_HASH: LDM_PASSWORD_HASH=True in lts.conf saves the password hash to /etc/shadow on login, so that the users can unlock the screensaver etc. If they happen to change their password though, that only takes effect until logout.
| |
| 15:26 | <alkisg> bcg: ^
| |
| 15:27 | <bcg> thanks.
| |
| 15:31 | funny. I see hash in /etc/shadow, but gnome-screensaver still refuses it
| |
| 15:33 | same for xscreensaver
| |
| 15:34 | same for "ssh localhost"
| |
| 15:35 | sshd[3144]: Failed password for b from 127.0.0.1 port 37642 ssh2
| |
| 15:39 | <alkisg> ssh localhost? You have localhost running on fat clients?
| |
| 15:39 | <bcg> If I manually change it with passwd command then it works.
| |
| 15:39 | <alkisg> Try su - user
| |
| 15:39 | <bcg> So the hash created by LDM_PASSWORD_HASH=True is wrong.
| |
| 15:39 | <alkisg> Are you also using any weird pam setup, e.g. ldap or whatever?
| |
| 15:39 | <bcg> nope
| |
| 15:40 | <alkisg> It sounds strange for it to be wrong as many people are using it
| |
| 15:40 | Which distro/version is that?
| |
| 15:40 | <bcg> rhel7
| |
| 15:40 | <alkisg> Check if it does support the hash method that the code uses
| |
| 15:40 | E.g. if it's using sha256, and rhel considers it unsafe, etc etc
| |
| 15:41 | <bcg> already did, the random part ($6$random$) is longer than what ldm creates
| |
| 15:41 | <alkisg> That doesn't matter, normally many hashes are supported
| |
| 15:41 | <bcg> I mean, ldm creates longer random what passwd does.
| |
| 15:41 | <alkisg> Again, it doesn't matter
| |
| 15:42 | passwd may be configured to support multiple hashes
| |
| 15:42 | <bcg> sure, hash is same for both.
| |
| 15:42 | <alkisg> Check the specific configuration that rhel ships with
| |
| 15:42 | <bcg> hash-function.
| |
| 15:44 | ldm created "b:$6$PnGG849ugMiBW1ry$..." (longer salt), passwd created "b:$6$JVGRU8TD$...", that's the only diff I see.
| |
| 15:45 | <alkisg> I mean,check the code, not the result
| |
| 15:45 | man shadow for the different types of salt
| |
| 15:45 | and crypt methods
| |
| 15:45 | *man crypt
| |
| 15:49 | <bcg> oh. ldm created encrypted password which is one char too long, ending with "!": ...A/0!:17515:...
| |
| 15:49 | size should be fixed to 86 chars, chars a–zA–Z0–9./
| |
| 15:51 | If I remove that ! then it works
| |
| 16:00 | gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving) | |
| 16:17 | <alkisg> Sounds like a sed issue?
| |
| 16:22 | <bcg> yep, shadow.sed created by ldm assumes that /etc/shadow contains :!: when in contains :!!:
| |
| 16:27 | does debian/ubuntu use :!: for "no password"? redhat uses :!!:
| |
| 16:38 | <alkisg> bcg, yes
| |
| 16:41 | <bcg> ok. I already patched my ldm to assume :!!: and it works now.
| |
| 16:44 | maybe that sed-line could be $s@!!*@crypted@ ... it works for both cases.
| |
| 16:45 | now it's $s:!:crypted:
| |
| 16:45 | well, no need to change : to @...
| |
| 16:45 | just change "!" to "!!*"
| |
| 16:47 | <alkisg> Sure, file a bug report, personally I no longer work on ltsp...
| |
| 16:48 | <bcg> that's a pity. who does?
| |
| 16:49 | <alkisg> I think vagrant still does a bit of maintenance
| |
| 16:54 | <quinox1> "Two exclamation points in the password field of /etc/shadow mean the account is locked."
| |
| 16:54 | meh
| |
| 16:55 | I'd make it '!!?', using * in regex is usually not nice
| |
| 16:55 | <bcg> I tried with !!? first but that didn't work.
| |
| 16:56 | bug filed, with patch.
| |
| 16:56 | <quinox1> escape the ? perhaps
| |
| 16:56 | regex is awesome, but all the flavours that exist is maddening
| |
| 16:56 | <bcg> that should not be required.
| |
| 16:57 | try from shell:
| |
| 16:57 | > echo 'foo:!:bar' | sed 's:!!?:encrypt:'
| |
| 16:57 | foo:!:bar
| |
| 16:57 | > echo 'foo:!:bar' | sed 's:!!*:encrypt:'
| |
| 16:57 | foo:encrypt:bar
| |
| 16:58 | <quinox1> $ echo 'foo:!:bar' | sed 's:!!\?:encrypt:'
| |
| 16:58 | foo:encrypt:bar
| |
| 16:58 | :)
| |
| 17:00 | <bcg> why \ is required? there are '' so shell doesn't need it.
| |
| 17:00 | <quinox1> yes
| |
| 17:00 | it's not bash escaping, it's sed escaping
| |
| 17:00 | or whatever it's called
| |
| 17:01 | ? is a literal question mark
| |
| 17:01 | \? is a optional group
| |
| 17:02 | <bcg> anyway, I'm more worried about alkisg's "not working on ltsp" than regex flavors.
| |
| 17:02 | <quinox1> if you use double quotes you'll have to use \\? - \\ for bash escaping to make it a \
| |
| 17:02 | it's unfortunate yes... I guess we all have to pick up the slack :)
| |
| 17:03 | <bcg> ldm is written in C so it has to be \\\\? if bash is involved too :-)
| |
| 17:04 | <quinox1> wanna know something weird... under linux you have argv right which is an array... no such thing under Windows, you just get a string which you'll have to split yourself
| |
| 17:05 | <bcg> I don't want to know that.
| |
| 17:05 | <quinox1> that's why there are a lot of DOS tools which break on quotes, or silently drop quotes where you wouldn't expect it
| |
| 17:05 | <bcg> Ugggh.
| |
| 17:05 | <quinox1> yeah :-/
| |
| 17:07 | <bcg> https://bugs.launchpad.net/ltsp/+bug/1738447 is the bug, I added your :!!\?: (or :!!\\?: as it's C)
| |
| 17:08 | <quinox1> +1
| |
| 17:08 | good job
| |
| 17:09 | (the +1 is an unfortunate side effect of hanging out on Github / Whatsapp for long periods of time)
| |
| 17:09 | s/Whatsapp/Telegram/
| |
| 17:10 | <bcg> in slack it would be :+1:
| |
| 17:13 | <quinox1> I'm really happy with LTSP, and I switch our setup to the latest non-LTS Ubuntu every 6 months... hopefully we can keep LTSP working for many years to come
| |
| 17:15 | <bcg> I have to install three new LTSP sites before new year.
| |
| 17:21 | <quinox1> All Redhat as well?
| |
| 17:23 | <bcg> yes
| |
| 17:23 | <quinox1> cool
| |
| 17:51 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 18:46 | stgraber has left IRC (stgraber!~stgraber@ubuntu/member/stgraber, Quit: kernel update) | |
| 18:47 | <fuzzmew> Do you mean I should repeat installing the ltsp manager with the --install-recommends or the ltsp pnp page?
| |
| 19:04 | <vagrantc> ltsp on debian-based systems needs Recommends installed by default
| |
| 19:04 | lucascastro has joined IRC (lucascastro!~lucas@189.90.38.210.jupiter.com.br) | |
| 19:04 | <vagrantc> unless you know what you're doing
| |
| 19:04 | is this linuxmint?
| |
| 19:04 | <alkisg> fuzzmew: yes; and better yet, do it for all programs that you install :)
| |
| 19:04 | Hi vagrantc :)
| |
| 19:06 | * vagrantc waves | |
| 19:09 | <alkisg> bcg: I haven't read the code, but why replace only ! or !!, instead of anything between the first two :
| |
| 19:09 | E.g. the debian shadow man page also mentions "*", but I think that even if there's a valid password entry already there, it should be overwritten...
| |
| 19:11 | <vagrantc> alkisg: you and your clever ideas.
| |
| 19:12 | <fuzzmew> Ok reinstalled, but still does not client boot.
| |
| 19:16 | Statler has left IRC (Statler!~Georg@gwrz3.lohn24.de, Remote host closed the connection) | |
| 19:20 | stgraber has joined IRC (stgraber!~stgraber@ubuntu/member/stgraber) | |
| 19:20 | <highvoltage> u
| |
| 19:20 | lucascastro has left IRC (lucascastro!~lucas@189.90.38.210.jupiter.com.br, Remote host closed the connection) | |
| 19:23 | enick_706 has left IRC (enick_706!bennabiyma@gateway/shell/matrix.org/x-ftaysnpwtwoehzdh, Changing host) | |
| 19:23 | enick_706 has joined IRC (enick_706!bennabiyma@unaffiliated/bennabiy) | |
| 19:23 | enick_706 has joined IRC (enick_706!bennabiyma@gateway/shell/matrix.org/x-ftaysnpwtwoehzdh) | |
| 19:23 | enick_706 is now known as bennabiy1 | |
| 19:31 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 19:37 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 19:38 | <alkisg> fuzzmew: mention error messages, "does not boot" again might mean you don't have power :)
| |
| 20:08 | jeremies has joined IRC (jeremies!~jeremies1@91.126.23.159) | |
| 20:09 | <jeremies> if I connect a nic server directly to nic thin client ltsp, should ipxe boot correctly?
| |
| 20:10 | I try it but didn't work
| |
| 20:10 | <alkisg> Only if you have 192.168.67.1 as the ip on your server nic
| |
| 20:11 | <jeremies> ok
| |
| 20:13 | <bcg> alkisg: original code used ":!:", I just did quick for me. Surely best way whould be to replace anything between first two :, but that would take more time to write, like up to 10 minutes.
| |
| 20:14 | <vagrantc> bcg: you're the one with all the redhat patches i lost track of, aren't you? :)
| |
| 20:14 | * vagrantc should have looked them over for the recent ldm/ltsp versions | |
| 20:14 | <bcg> probably
| |
| 20:14 | they are in lp
| |
| 20:15 | <vagrantc> bcg: i'll see if i can get to them this year :)
| |
| 20:15 | <bcg> there's also another ldm patch by me in bug tracker.
| |
| 20:17 | https://bugs.launchpad.net/ltsp/+bug/1698523 lot of patches, i see
| |
| 20:17 | kjackal has left IRC (kjackal!~quassel@2a02:587:3100:c900:d8d2:1956:e358:88e1, Ping timeout: 240 seconds) | |
| 20:18 | <bcg> ltsp-stuff in https://code.launchpad.net/~bcgss/ltsp/+git/ltsp-rhel7
| |
| 20:19 | lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14) | |
| 20:27 | <alkisg> bcg: something like this: echo 'root:!:17347:0:99999:7:::' | sed 's/:[^:]*:/:CRYPT_RESULT_HERE:/'
| |
| 20:27 | root:CRYPT_RESULT_HERE:17347:0:99999:7:::
| |
| 20:28 | <bcg> almost, but instead of / you should use @, as CRYPT_RESULT_HERE can contain /
| |
| 20:29 | <alkisg> OK
| |
| 20:29 | * alkisg isn't going to commit anything, just chatting :) | |
| 20:29 | <bcg> ok, i'll commit it to my ldm clone
| |
| 20:33 | - "# Generated by LTSP, for LDM rc.d script manipulation\n$s:!:%s:",
| |
| 20:33 | + "# Generated by LTSP, for LDM rc.d script manipulation\n$s@:[^:]*:@:%s:@",
| |
| 20:34 | <alkisg> Seems better :)
| |
| 20:36 | <vagrantc> bcg: regarding "g_type_init" ... it is basically un-needed in newer versions? there's nothing it needs to be replaced with?
| |
| 20:36 | <bcg> yes.
| |
| 20:40 | kjackal has joined IRC (kjackal!~quassel@2a02:587:3100:c900:a8fb:9a2c:99f9:7602) | |
| 20:47 | <vagrantc> bcg: doing some compile testing now, if it passes, i'll merge it.
| |
| 20:47 | <bcg> wow. it only took half an year to get merged. :-)
| |
| 20:48 | <vagrantc> bcg: sorry.
| |
| 20:49 | <bcg> no worries, i've been running my clone all this time.
| |
| 20:50 | <vagrantc> bcg: did you also have patches for ltsp, or just ldm?
| |
| 20:50 | <bcg> 22:18 < bcg> ltsp-stuff in https://code.launchpad.net/~bcgss/ltsp/+git/ltsp-rhel7
| |
| 20:52 | <vagrantc> most of that i can't realistically evaluate, but since nobody else works on it, and as long as it doesn't break anything i can test, that should be easy to merge :)
| |
| 21:01 | * vagrantc gave up on trying to port LTSP to guixsd and nixos ... just too many hard-coded /usr/lib and /usr/share | |
| 21:10 | <vagrantc> bcg: the ltsp branch doesn't seem to merge cleanly.
| |
| 21:10 | deleted by them: client/Redhat/rwtab.d/ltsp.rwtab
| |
| 21:10 | both modified: client/Redhat/share/ltsp/init-ltsp.d/00-overlay
| |
| 21:10 | both modified: server/share/ltsp/plugins/ltsp-build-client/Redhat/009-mock-chroot
| |
| 21:10 | i'd be surprised if i touched any of those redhat specific files ... unless someone did some whitespace cleanup or soemthing
| |
| 21:11 | kjackal has left IRC (kjackal!~quassel@2a02:587:3100:c900:a8fb:9a2c:99f9:7602, Ping timeout: 255 seconds) | |
| 21:14 | <vagrantc> bcg: other than that, i don't see anything i wouldn't be fine with merging, caveat being i have no idea about Redhat but i'll just trust you :)
| |
| 21:15 | we really need some automated testing on stupid things like trailing whitespace.
| |
| 21:17 | hah! Switch from /var/cache/ltsp to /run/ltsp (LP: #1560344).
| |
| 21:17 | well, that would explain it
| |
| 21:18 | knowing that's the only change, shouldn't be hard to merge
| |
| 21:19 | bcg: i'll see if i can't merge this, then
| |
| 21:19 | bcg: hopefully the switch to /run/ltsp isn't a problem for Redhat?
| |
| 21:20 | <bcg> hmm... /run/ltsp is fine. might need some minor tweaking, but i'll do it then.
| |
| 21:22 | tomorrow...
| |
| 21:23 | <vagrantc> bcg: you have NFS working with overlay fs?
| |
| 21:24 | bcg: i'm nto quite confident in merging the difference, but if you can rebase against master, i'll merge it :)
| |
| 21:24 | <bcg> yes, kind of kludge, but works.
| |
| 21:25 | <vagrantc> i know the FAI folks also are using NFS with overlay fs, so i've been meaning to try and figure it out for Debian again
| |
| 21:25 | * vagrantc suspects it is some combination of mount options | |
| 21:25 | <bcg> does lp allow rebase, or just merge from master?
| |
| 21:25 | pull+merge
| |
| 21:26 | it's too late, better continue tomorrow.
| |
| 21:28 | * vagrantc isn't sure | |
| 21:28 | <vagrantc> a separate branch wouldn't hurt anyways
| |
| 22:20 | Da-Geek has left IRC (Da-Geek!~Da-Geek@88.98.209.152, Quit: Leaving) | |
| 22:33 | jeremies has left IRC (jeremies!~jeremies1@91.126.23.159, Ping timeout: 264 seconds) | |
| 22:48 | jeremies has joined IRC (jeremies!~jeremies1@91.126.23.159) | |
| 22:53 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 23:06 | jeremies has left IRC (jeremies!~jeremies1@91.126.23.159, Quit: Leaving) | |