IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 2 January 2016   (all times are UTC)

00:00alkisg1 has joined IRC (alkisg1!~alkisg@ubuntu/member/alkisg)
00:00fiesh has left IRC (fiesh!~fiesh@hq.wsoptics.de, Ping timeout: 240 seconds)
00:00PeperPots has left IRC (PeperPots!sid1218@gateway/web/irccloud.com/x-yvbbwsdlgbdqhqaa, Ping timeout: 240 seconds)
00:00spectra_ has left IRC (spectra_!~spectra@63.142.251.150, Ping timeout: 240 seconds)
00:00ltsp has left IRC (ltsp!bot@ltsp.org, Ping timeout: 240 seconds)
00:00alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Ping timeout: 240 seconds)
00:02PeperPots_ is now known as PeperPots
00:05spectra has joined IRC (spectra!~spectra@debian/developer/spectra)
02:13vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
03:26gbaman has left IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com, Remote host closed the connection)
03:27gbaman has joined IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com)
05:17vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 250 seconds)
05:25adrianorg has left IRC (adrianorg!~adrianorg@189.58.235.43.dynamic.adsl.gvt.net.br, Ping timeout: 265 seconds)
05:27adrianorg has joined IRC (adrianorg!~adrianorg@177.18.48.243)
05:30imithcell has joined IRC (imithcell!640e8129@gateway/web/freenode/ip.100.14.129.41)
06:49alkisg1 is now known as alkisg
06:49
<alkisg>
Happy new year to everyone
06:53Ark74 has joined IRC (Ark74!~Luis@177.246.232.49)
07:00
<alkisg>
Maijin: as Hyperbyte said, ask your question and wait for an answer. If you don't ask it first, how can we answer?
07:01
Ark74: if that thing can't pxe boot, it's possible to put the kernel+initrd locally
07:01
Since a couple of months ago, ltsp supports auto-updating a local kernel+initrd copy
07:03
<Ark74>
alkisg, the info i could get from the device, is a NAND flash storage with a arm1176zfj processor
07:03
<alkisg>
Can it boot linux?
07:06
<Ark74>
i really can't boot anything yet, it boots WinCE 6
07:06
so i'm looking, maybe i can flash it with uboot
07:06
<alkisg>
If you can't get it to boot linux, and you need a linux session, then just use rdp/vnc to connect to a server
07:07
How much ram does that have?
07:07
<Ark74>
128MB
07:07
<alkisg>
Is that RAM or DOM (disk)?
07:07teknkik has left IRC (teknkik!tek@kapsi.fi, Ping timeout: 276 seconds)
07:07
<alkisg>
Usually wince devices are so low spec'ed that they're not worth the trouble to make them ltsp clients
07:08
<Ark74>
http://www.sharethinclient.com/products_show_6.html
07:09
<alkisg>
So both RAM and DOM are 128MB...
07:09
<Ark74>
yep
07:10
so, i can use rpd to boot the LTSP session?
07:10
<alkisg>
No, but you can use rdp to connect to the ltsp server
07:10
<Ark74>
*rdp
07:10
<alkisg>
Although that's not related to ltsp of course, it's just rdp
07:10
rdp can be used to connect either to windows pcs, or to linux pcs that have xrdp installed
07:12
<Ark74>
ohh, that's something new, a xrdp and a x over ssh is the same?
07:12
<alkisg>
rdp is a windows protocol
07:12
X is a linux protocol
07:12
xrdp is an rdp server that runs on a linux machine
07:12
So yes it's very different from x over ssh
07:13
<Ark74>
ok, also, you can boot a machine directly to a rdp session, right?
07:13
or can you?
07:13
<alkisg>
rdp is an application like a calculator or an editor or vnc
07:13
You first boot the computer to any OS, then run the rdp application
07:14
In your case, you boot to wince, and run the rdp client from there
07:14
If you want to autorun the rdp client, you can configure that inside wince like all other apps
07:14
<Ark74>
so is like the vnc to gnu/linux, then rdp to windows?
07:15
<alkisg>
There are clients and servers for both vnc and rdp, for all OSes
07:15
<Ark74>
a ltsp server has xrdp installed?
07:15
<alkisg>
So you can rdp from windows to linux, or vnc from windows to windows, etc etc, any combination
07:15
You can install xrdp to any linux distro. No, it's not preinstalled, but you can install it.
07:16
All these things are not related to ltsp. You can install rdp to an ltsp server, or you can install it to a linux machine that doesn't have ltsp, whatever you want.
07:16
<Ark74>
ok, it's just that i read somewhere that rdp is supported on ltsp, or maybe a rdp session login
07:17
<alkisg>
That the opposite of what you want
07:17
That is about booting an ltsp client, and then using the display manager (LDM) to connect via the xfreerdp client to a windows server
07:18
<Ark74>
xDD
07:18
hehehe
07:18
<alkisg>
You don't have an ltsp client in this case, you just want to use the rdp application
07:18
(or the vnc application)
07:18
<Ark74>
ok, thanks
07:19
<alkisg>
Note that the client specs are too low, so you'll get better performance from a 15 year old p4
07:19
You're welcome
07:19
<Ark74>
you mention a really good point, i don't know if it's worth it to mess around and try to flash this thin client
07:19
<alkisg>
You don't need to flash it to use rdp
07:19
It's already installed in wince
07:19
<Ark74>
to get pxe
07:20
<alkisg>
Yup, it's not worth to get uboot etc running on that
07:20
<Ark74>
so it boots directly
07:21
thanks alkisg i get the clear picture now
07:21
<alkisg>
:)
07:21
<Ark74>
\o/!
07:36vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
07:41
<alkisg>
Happy new year vagrantc
07:42NeonLicht has joined IRC (NeonLicht!~NeonLicht@darwin.ugr.es)
07:43
<vagrantc>
alkisg: indeed!
07:43
alkisg: happy new year to the likes of you!
07:43
<alkisg>
Let 2016 bring ltsp6
07:43
<vagrantc>
there is a certain logic there
07:44
introduced ltsp5 in 2005, ltsp6 in 2016... :)
07:44
(although it was muekow in 2005...)
07:45* alkisg would like to hear the story behind the muekow name...
07:45
<vagrantc>
first version i see called ltsp5 wasn't until 2007
07:46
<alkisg>
As for the name MueKow, it was part of an inside joke between sbalneav and myself. Somehow, the name stuck. If the experiment works out, this will likely become LTSP-5.0. -- JimMcQuillan - 28 Feb 2005
07:46
<vagrantc>
right
07:46
<alkisg>
sbalneav: so, what was the inside joke?! :)
07:47* vagrantc vaguely recalls something about "longhorn was already taken"
07:47
<alkisg>
Hehe
07:58ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
08:16teknkik has joined IRC (teknkik!tek@kapsi.fi)
08:36vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
09:01Ark74 has left IRC (Ark74!~Luis@177.246.232.49, Quit: Saliendo)
10:07robb_nl has joined IRC (robb_nl!~robb_nl@ip-80-236-219-29.dsl.scarlet.be)
10:29gil has joined IRC (gil!4f295b50@gateway/web/freenode/ip.79.41.91.80)
13:52
<Maijin>
alkisg: problem I was investigating also in my side^^" When I'll go back on the serv I'll give u more info, I think is more my dhcp config which is wrong :) Will keep u in touch thanks :D
13:52
Hyperbyte: as well
14:13quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Ping timeout: 272 seconds)
14:14quinox has joined IRC (quinox!~quinox@ghost.qtea.nl)
14:35
<alkisg>
Meh. /usr/share/initramfs-tools/hooks/intel_microcode puts GenuineIntel.bin to the initramfs, tailored to the *current system*. That doesn't sound good for booting e.g. amd clients from an intel server...
14:36NeonLicht has left IRC (NeonLicht!~NeonLicht@darwin.ugr.es, Ping timeout: 250 seconds)
14:40
<alkisg>
The whole intel blob is 744740 bytes, quite big to include it in the initramfs by default...
14:41
If needed, we can do it from /etc/default/intel-microcode
14:42
IUCODE_TOOL_SCANCPUS=yes
15:08
<quinox>
https://ghost.qtea.nl/tmp/virtual_ltsp_boot_via_qemu.mp4 booting LTSP via PXE via QEMU works just fine
15:11
it currently boots off our real LTSP server; next steps are to use the auto-login feature of LDM to login+screenshot+shutdown without manual interaction, put the LTSP server itself inside docker or something and get QEMU to boot from the docker image
15:13
once that step is achieved it should be fairly easy to automatically test if <your-OS-choice> can run LTSP
15:15
boot from the docker image --> boot via PXE using the services inside the docker image
15:15
and apparently I'm missing "/etc/ltsp/ntpupdate" inside my client image, I never noticed that error before
15:22
https://ghost.qtea.nl/tmp/qemu-0650.jpeg <-- the error is the 7th line from the bottom... I suppose "/etc/rc.local: 27:" refers to line 27 of rc.local, but that one just contains "exit 0"
15:32vervelak has left IRC (vervelak!~vervelak@139.91.248.88, Ping timeout: 255 seconds)
15:33vervelak has joined IRC (vervelak!~vervelak@139.91.248.88)
15:35gbaman has left IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com, Remote host closed the connection)
15:35gbaman has joined IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com)
18:02
<alkisg>
quinox: I don't think /etc/ltsp/ntpdate exists in LTSP, it sounds like a local thing in your installation
19:54robb_nl has left IRC (robb_nl!~robb_nl@ip-80-236-219-29.dsl.scarlet.be, Ping timeout: 250 seconds)
21:27vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
21:34
<quinox>
might be, although I know we use -s inside /etc/default/openntpdate for that as well
21:35* quinox will track it down somehow
21:42
<quinox>
yeah it's a RCFILE_01, it's surrounded by LOCAL_APPS and we switched to fat clients many years ago already so it's probably an ancient entry
21:44ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
23:35vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)