|01:07||Angel_ has joined IRC (Angel_!bdd55dab@gateway/web/freenode/ip.126.96.36.199)|
|01:09||Angel_ has left IRC (Angel_!bdd55dab@gateway/web/freenode/ip.188.8.131.52, Client Quit)|
|01:15||GodFather has joined IRC (GodFatheremail@example.com)|
|01:20||angel_ has joined IRC (angel_!bdd55dab@gateway/web/freenode/ip.184.108.40.206)|
|01:20||* vagrantc waves|
|01:21||GodFather has left IRC (GodFatherfirstname.lastname@example.org, Ping timeout: 240 seconds)|
someone can help me with lts.conf, y need to put parameters for my touchscreen, is a elotouch. Someone have an example?
!lts.conf | echo angel_
angel_ lts.conf: (#1) http://manpages.ubuntu.com/lts.conf, or (#2) lts.conf manpage is available in the ltsp-docs package
angel_: there appears to be USE_TOUCH options. never used them myself
|02:30||Eric4 has joined IRC (Eric4email@example.com)|
|02:34||Eric4 has left IRC (Eric4firstname.lastname@example.org, Ping timeout: 248 seconds)|
|04:21||vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)|
angel_: start with "what steps do you need to do without ltsp to make your touchscreen work?"
After you have the answer to that, ask here so that we tell you how to do it the "ltsp way"
E.g. https://wiki.ubuntu.com/Touchscreen mentions elotouch, maybe that's what you need to do
|05:18||Statler has joined IRC (Statler!~Georg@p579FE770.dip0.t-ipconnect.de)|
|05:34||ricotz has joined IRC (ricotz!~ricotz@p5B2A8E6B.dip0.t-ipconnect.de)|
|05:34||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
I do not know about 'root', but I do know about these similar topics: 'ROOT_PASSWORD_HASH'
I do not know about 'password', but I do know about these similar topics: 'ROOT_PASSWORD_HASH', 'LDM_PASSWORD_HASH'
ROOT_PASSWORD_HASH: to be able to login as root in vt1, with password "qwer1234", put this in lts.conf: INIT_COMMAND_01="sed 's!^root:[^:]*:!root:$6$p2LdWE6j$PDd1TUzGvvIkj9SE8wbw1gA/MD66tHHlStqi1.qyv860oK47UnKcafSKqGp7cbgZUPlgyPv6giCVyCSCdJt1b0:!' -i /etc/shadow"
alkisg: i'm working on one, but it's using gnustep (not gtk, nor qt)
tarzeau: er, I'
Er, I'm not sure this choice will be popular to potential contributors
people can port it, i use it
Porting is overrated, not many people want to maintain forks :) But sure, for your own use, you do whatever you like...
|06:30||mikkel has joined IRC (email@example.com)|
|06:30||* gehidore maintains his forks, and spoons and knives...|
|06:31||Eric4 has joined IRC (Eric4firstname.lastname@example.org)|
|07:27||Statler has left IRC (Statler!~Georg@p579FE770.dip0.t-ipconnect.de, Quit: Leaving)|
|07:29||Statler has joined IRC (Statler!~Georg@p579FEE8F.dip0.t-ipconnect.de)|
|07:56||ABIX_Adamj has joined IRC (ABIX_Adamjemail@example.com)|
|09:47||GodFather has joined IRC (GodFatherfirstname.lastname@example.org)|
|10:09||fnurl_c has joined IRC (email@example.com)|
|10:10||Eric5 has joined IRC (Eric5firstname.lastname@example.org)|
|10:12||fnurl has left IRC (email@example.com, Read error: Connection reset by peer)|
|10:12||Eric4 has left IRC (Eric4firstname.lastname@example.org, Read error: Connection reset by peer)|
|10:14||ben_nabiy has left IRC (ben_nabiy!~bennabiy@unaffiliated/bennabiy, Ping timeout: 240 seconds)|
|10:14||ben_nabiy has joined IRC (ben_nabiy!~bennabiy@unaffiliated/bennabiy)|
|11:11||antares has joined IRC (antares!c1929682@gateway/web/freenode/ip.220.127.116.11)|
hello... moved chroot from i386 machine to x86_64. image is served ok and clients run, but can't chroot due to an exec format error.
I've been fiddling around but no success so far. maybe setarch could solve the issue?
By the way, the chroot is armhf
any direction would be appreciated. Thanks!
antares: Can you chroot to the armhf directory on the i386 machine?
vlt: yes, there is no problem with that. I've been trying with setarch but no success
but wait.. the working machine is x86_64 as well
sorry for the annoyance. But the problem still exists
the "new" machine uname -r throws
Linux portpel 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1 (2016-12-30) x86_64 GNU/Linux
|11:36||os_a has joined IRC (os_a!c3707416@gateway/web/freenode/ip.18.104.22.168)|
while the machine in which ltsp (pinet) was installed at first says
Linux pequepel 4.4.0-24-generic #43-Ubuntu SMP Wed Jun 8 19:27:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Привет! 1.Скорость записи на usb-flash носитель(подключенный к терминалу) с сервера составляет менее 500 киллобит. Как ускорить? ЛЦП5 сеть 100 мегабит, утилизация близка к 0 2. Где я могу натий правило монтирования усб-флэш на сервер с терминала?
Hello! 1. The speed of writing to usb-flash media (connected to the terminal) from the server is less than 500 kilobits. How to speed up? LTSP5 network of 100 megabit, utilization close to 0 2. Where can I mount a usb-flash rule on the server from the terminal?
|11:48||Eric5 has left IRC (Eric5email@example.com, Ping timeout: 240 seconds)|
vlt: a first success, I've realized that qemu wasn't installed in the nuew machine. Installed it and the exec error disappears.
Now i get an can't execute /bin/bash no such file or directory
os_a: does it work fast if you use ltsp fat clients?
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
alkisg: Yes, exactly
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
|12:28||lucascastro has joined IRC (firstname.lastname@example.org)|
|12:28||Eric5 has joined IRC (Eric5email@example.com)|
os_a: if you're using fat clients, then usb speed is the same as in normal linux, so:
non-ltsp: It's better to direct your questions to the most suitable channel. For example, for questions that are not specific to LTSP, you might try distro-specific channels, such as #ubuntu, #debian, #suse, #fedora etc.
alkisg: Hmm. It seems to me that the distribution kit is not at work here - there was a similar problem on Debian 8 before, now Ubuntu 16.04 lts - the problem is similar. Having some experience with these systems, I can assume that it's not in the distribution
|13:16||antares has left IRC (antares!c1929682@gateway/web/freenode/ip.22.214.171.124, Ping timeout: 260 seconds)|
os_a: ltsp fat clients don't have any code at all for usb drives
Since there's no code, i'm sure it's not a problem with the ltsp codebase
If you're using ltsp *thin* clients, then ltsp has code there, called "ltspfs"
So if you're using ltsp fat clients, then it's not a problem with ltsp, and you should test a local installation to verify that it's not related to ltsp
alkisg: Well thank you. I'll test it.
|13:58||ben_roose has joined IRC (firstname.lastname@example.org)|
|14:00||os_a has left IRC (os_a!c3707416@gateway/web/freenode/ip.126.96.36.199, Ping timeout: 260 seconds)|
|14:27||mikkel has left IRC (email@example.com, Quit: Leaving)|
|14:51||ben_nabiy has left IRC (ben_nabiy!~bennabiy@unaffiliated/bennabiy, Quit: http://www.yellowdeli.com)|
|15:48||Statler has left IRC (Statler!~Georg@p579FEE8F.dip0.t-ipconnect.de, Remote host closed the connection)|
|16:51||Eric5 has left IRC (Eric5firstname.lastname@example.org, Ping timeout: 255 seconds)|
|17:23||vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)|
|17:35||GodFather has left IRC (GodFatheremail@example.com, Ping timeout: 260 seconds)|
|19:15||lucas_ has joined IRC (firstname.lastname@example.org)|
|19:17||lucascastro has left IRC (email@example.com, Ping timeout: 264 seconds)|
|19:20||lucas_ has left IRC (firstname.lastname@example.org, Ping timeout: 248 seconds)|
|19:20||lucascastro has joined IRC (email@example.com)|
|20:38||dgroos has joined IRC (firstname.lastname@example.org)|
|20:42||GodFather has joined IRC (GodFatheremail@example.com)|
In trying to solve client-authentication problem on ltsp-pnp clients I tried the suggestion of booting clients as thin client instead of fat, and try to authenticate. Makes sense, should have worked since I can authenticate AD clients sitting at the ltsp server or ssh-ing into the ltsp server. But doesn’t work at the clients. Any idea?
|20:47||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|
|20:48||lucascastro has left IRC (firstname.lastname@example.org, Remote host closed the connection)|
dgroos: you're able to ssh in when not using ltsp?
@vagrantc sorry, yes, from a laptop on the WAN.
And, I can’t log into the clients, either fat or thin, with local accounts either!
Yet, when I leave (un-join) the ltsp server from the AD domain, I can then successfully log into both the fat and thin clients with a local user!
there's presumably something odd with your PAM stack...
hmmm… gonna check into the log but, which one would be the best to check, auth.log?
dgroos: check the results of "getent passwd" and "getent group" before and after joining the AD domain
vagrantc: will do…
or "geteng passwd USER"
see if there are any obviously weird differences there
… in the log? or just in the results?
that should be the only difference between an LDAP and local login, and depending on how PAM is configured, one might override the other
dgroos: just check the output, that's the only thing above and beyond simply ssh'ing to the machine that LTSP does.
well, it also uses ssh -Y .... and master control sockets ... but i'd be surprised if PAM messed with that
you could also use epoptes to get a root shell on the client, and tail some of the local client logs...
and /etc/passwd and /etc/group, etc.
I do not know about 'root', but I do know about these similar topics: 'ROOT_PASSWORD_HASH'
I do not know about 'shell', but I do know about these similar topics: 'shell-screen', 'gnome-shell'
epoptes: Epoptes is a computer lab administration and monitoring tool. It works on Ubuntu and Debian based labs with LTSP or non-LTSP servers, thin and fat clients, standalone workstations, NX clients etc. More info: http://www.epoptes.org
Error: "epoptes-shell" is not a valid command.
Error: "epoptes-root" is not a valid command.
OK! I’ve got a few things to check, will do and get back (kinda slow at the end of teaching all day ;)
sure, good luck!
test 1: getent passwd LOCAL USER & getent group LOCAL USER returned same results before and after Joining the AD… NOw onto getting onto the external root via epoptes…
|21:45||ben_roose has left IRC (email@example.com, Remote host closed the connection)|
*client root via epoptes “root, locally”
|21:50||ogra_ has left IRC (firstname.lastname@example.org, Ping timeout: 240 seconds)|
|21:50||ogra_ has joined IRC (email@example.com)|
vagrantc: here’s an image of the print out of a “tail -f” of syslog (auth.log remains empty!) https://pasteboard.co/GJtukpc.png
|22:19||GodFather has left IRC (GodFatherfirstname.lastname@example.org, Quit: Ex-Chat)|
vagrantc: alas, I must leave school now for home. I will be trying to do some work on this this weekend remotely via -X and epoptes. Thanks for your ideas!
|22:19||GodFather has joined IRC (GodFatheremail@example.com)|
|22:20||dgroos has left IRC (firstname.lastname@example.org, Quit: dgroos)|
|22:23||GodFather has left IRC (GodFatheremail@example.com, Client Quit)|
|22:23||vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)|
|22:23||GodFather has joined IRC (GodFatherfirstname.lastname@example.org)|
|22:25||GodFather has left IRC (GodFatheremail@example.com, Remote host closed the connection)|
|22:26||GodFather has joined IRC (GodFatherfirstname.lastname@example.org)|
|23:19||pppingme has left IRC (pppingme!~pppingme@unaffiliated/pppingme, Quit: Leaving)|
|23:30||mmarconm has joined IRC (mmarconm!~Marcelo@188.8.131.52)|
|23:32||pppingme has joined IRC (pppingme!~pppingme@unaffiliated/pppingme)|