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


Channel log from 17 September 2012   (all times are UTC)

01:24Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 245 seconds)
01:29mbjzralrrii has joined IRC (mbjzralrrii!~iamparado@c-71-57-196-26.hsd1.va.comcast.net)
01:32|Paradox| has left IRC (|Paradox|!~iamparado@c-71-57-196-26.hsd1.va.comcast.net, Ping timeout: 244 seconds)
01:32mbjzralrrii is now known as |Paradox|
01:50Lns has joined IRC (Lns!~Lns@173-16-218-84.client.mchsi.com)
01:50Lns has joined IRC (Lns!~Lns@pdpc/supporter/professional/lns)
02:16ltspuser_26 has joined IRC (ltspuser_26!bd3c67f3@gateway/web/freenode/ip.189.60.103.243)
02:17
<ltspuser_26>
Hi! I have a very simple question: Do the $99 thin clients from HP work with LTSP?
02:23ltspuser_26 has left IRC (ltspuser_26!bd3c67f3@gateway/web/freenode/ip.189.60.103.243, Ping timeout: 245 seconds)
02:30ltspuser_01 has joined IRC (ltspuser_01!bd3c67f3@gateway/web/freenode/ip.189.60.103.243)
02:31
<ltspuser_01>
I have a beginer question: Does LTSP work with the $99 thin clients from HP ?
02:31
<highvoltage>
hi ltspuser_01
02:31
what a co-incidince, there was another user called ltspuser_26 earlier with the exact same question.
02:31
do you have a link with the specs?
02:32
<ltspuser_01>
Yes, I have.
02:32
http://h10010.www1.hp.com/wwpc/us/en/sm/WF06a/12454-12454-321959-338927-5112717-5171156.html?dnr=1
02:32
The faile session was my client that crashed ...
02:44
<highvoltage>
hmm, it says 1x vga but not what type
02:44
it has RJ-45 but it doesn't say it has pxe (I guess it could be assumed thatit has)
02:47
heh, the pdf goes into detail about its mounting brackets, etc but no juicy details
02:47
<stgraber>
those are zero-clients, not thin clients
02:48
<highvoltage>
ah so they're like those n-computing machines?
02:48
<stgraber>
zero-clients are a bit weird in the sense that it's mostly proprietary technology and they vary from full fledge thin clients with custom software all the way to something that's roughly a board with an ethernet port, vga and USB but no CPU
02:48
<highvoltage>
ah right.
02:49
<stgraber>
those t200 look like those later kind of clients, where it's roughly something like displaylink but over ethernet
02:50
they apparently require a matching "server": http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/12454-12454-321959-338927-5112717-5096586.html?dnr=1
02:50
where they then refer to these clients as "seats", so a similar terminology as displaylink based hardware
02:50
so short answer, if I'm right, no, those won't work with LTSP and can't ever work with it
02:56
<ltspuser_01>
but the DO work with Userful distribution: http://www.userful.com
02:58
I guessa better link is: http://www.userful.com/products/userful-multiseat-linux
03:05alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
03:15Pecker has joined IRC (Pecker!~irc@67-61-36-10.cpe.cableone.net)
03:19Parker955 is now known as Parker955_Away
03:21Pecker has left IRC (Pecker!~irc@67-61-36-10.cpe.cableone.net, Ping timeout: 240 seconds)
03:41ry has left IRC (ry!~ry@static-71-183-64-28.nycmny.fios.verizon.net, Read error: Connection reset by peer)
03:42ltspuser_01 has left IRC (ltspuser_01!bd3c67f3@gateway/web/freenode/ip.189.60.103.243, Ping timeout: 245 seconds)
04:26alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
05:39ricotz has joined IRC (ricotz!~rico@unaffiliated/ricotz)
05:53alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
06:13
<alkisg>
!socat
06:13
<ltsp>
socat: One way to share a console with a remote person is: [local pc] forward port 5500, run: socat tcp-listen:5500,keepalive=1 stdio,raw,echo=0 [remote pc] socat tcp:server:5500 SYSTEM:"{ sleep 1; xterm -e screen -xRR ra$$; } & exec screen -S ra$$",pty,stderr
06:14Bootless has joined IRC (Bootless!~AnDyLap@sarkomand-201-219-aps.cronon.net)
06:23Lns has left IRC (Lns!~Lns@pdpc/supporter/professional/lns, Ping timeout: 240 seconds)
06:29gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
06:49dobber has joined IRC (dobber!~dobber@213.169.45.222)
07:22
<alkisg>
!nbd-client
07:22
<ltsp>
nbd-client: To try mounting the NBD image from the client initramfs: nbd-client 192.168.67.1 -N /opt/ltsp/i386 /dev/nbd0
07:28F-GT has joined IRC (F-GT!~phantom@ppp121-44-5-171.lns20.syd6.internode.on.net)
08:02bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
08:04ricotz has left IRC (ricotz!~rico@unaffiliated/ricotz, Quit: Ex-Chat)
08:21fossala has joined IRC (fossala!~fossala@host-92-17-244-94.as13285.net)
08:21
<fossala>
Is there a way of changing volume on ltsp thin clients without using the gnome/xfce volume controls?
08:21
I'm using a window manager that doesn't provide that (i3).
08:24
<ogra_>
pavucontrol might help
08:26mealstrom has joined IRC (mealstrom!~mealstrom@46.63.71.254)
08:27
<fossala>
Worked, thanks.
08:37khildin has joined IRC (khildin!~khildin@ip-80-236-222-240.dsl.scarlet.be)
08:59bauerski has joined IRC (bauerski!~witekb@frodo.psp.opole.pl)
09:41Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
10:11Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
11:00ltspuser_66 has joined IRC (ltspuser_66!c122cd02@gateway/web/freenode/ip.193.34.205.2)
11:00
<ltspuser_66>
hello
11:05Gremble has joined IRC (Gremble!~Ben@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com)
11:09Gremble has left IRC (Gremble!~Ben@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com, Client Quit)
11:14khildin_ has joined IRC (khildin_!~khildin@ip-80-236-222-107.dsl.scarlet.be)
11:17khildin has left IRC (khildin!~khildin@ip-80-236-222-240.dsl.scarlet.be, Ping timeout: 252 seconds)
11:43xet7 has left IRC (xet7!~xet7@a91-156-248-33.elisa-laajakaista.fi, Quit: Lähdössä)
11:57Parker955_Away is now known as Parker955
12:02Parker955 is now known as Parker955_Away
12:12brunolambert has joined IRC (brunolambert!blambert@nat/revolutionlinux/x-tkgscfazofnceeop)
12:23mgariepy has joined IRC (mgariepy!mgariepy@ubuntu/member/mgariepy)
12:27Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
12:28alkisg1 has joined IRC (alkisg1!~alkisg@ubuntu/member/alkisg)
13:04[GuS] has joined IRC ([GuS]!~MysT@unaffiliated/gus/x-663402)
13:15JesseC has joined IRC (JesseC!~JesseCWor@wsip-98-175-20-126.br.br.cox.net)
13:24bauerski has left IRC (bauerski!~witekb@frodo.psp.opole.pl, Quit: Leaving.)
13:50artista-frustrad has joined IRC (artista-frustrad!~fernando@189.125.205.147)
14:08xJustTheTip has joined IRC (xJustTheTip!~xJustTheT@50-192-155-18-static.hfc.comcastbusiness.net)
14:09roasted has joined IRC (roasted!32c80ada@gateway/web/freenode/ip.50.200.10.218)
14:09
<roasted>
hello!
14:10
<xJustTheTip>
hi everyone
14:10ltspuser_66 has left IRC (ltspuser_66!c122cd02@gateway/web/freenode/ip.193.34.205.2, Ping timeout: 245 seconds)
14:11
<xJustTheTip>
has anyone been successful getting ltsp running on raspberry pi? NOT berryterminal
14:12ricotz has joined IRC (ricotz!~rico@unaffiliated/ricotz)
14:13
<roasted>
xJustTheTip: I haven't tried that.
14:13
In fact I have two rasp pi's I have yet to unbox.
14:14
Between a wedding in 3 weeks and a blasted home renovation my tinker time has been approx nothing.
14:14
<xJustTheTip>
we're wanting to use them as thin clients to just run RDP to connect to a windows terminal server
14:14
<roasted>
Anybody out there running XFCE on their LTSP terminals? I'm having trouble digging up info on how to switch it over... like, what EXACT syntax to use in the lts.conf
14:14
<xJustTheTip>
I have it working for i386, I just was curious if anyone has done it for ARM
14:18sideffect has left IRC (sideffect!sideffect@gateway/shell/bshellz.net/x-jixdnwnohaeyjnll, Remote host closed the connection)
14:21artista-frustrad has left IRC (artista-frustrad!~fernando@189.125.205.147, Ping timeout: 264 seconds)
14:21artista-frustrad has joined IRC (artista-frustrad!~fernando@189.125.205.147)
14:21dead_inside has joined IRC (dead_inside!~dead_insi@76.75.3.174)
14:22TedHughes1 has joined IRC (TedHughes1!~stuartian@cpc9-burn8-2-0-cust51.10-1.cable.virginmedia.com)
14:24
<TedHughes1>
Hi I am using LTSP on ubuntu 12.04 through Zentyal and if I look at the logs ltsp-build-client updates all the kernels and tftboot dirs for all images even though I specify --arch
14:25
I think its an LTSP script more than zentyal is this correct ?
14:26sideffect has joined IRC (sideffect!sideffect@gateway/shell/bshellz.net/x-ttbjgnfkfmqxymhz)
14:29bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 244 seconds)
14:40staffencasa has joined IRC (staffencasa!~staffenca@8-220.ptpg.oregonstate.edu)
14:42Bootless has left IRC (Bootless!~AnDyLap@sarkomand-201-219-aps.cronon.net, Read error: Connection reset by peer)
14:50Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 252 seconds)
15:00TedHughes has joined IRC (TedHughes!~stuartian@cpc9-burn8-2-0-cust51.10-1.cable.virginmedia.com)
15:01F-GT has left IRC (F-GT!~phantom@ppp121-44-5-171.lns20.syd6.internode.on.net, Ping timeout: 240 seconds)
15:03TedHughes1 has left IRC (TedHughes1!~stuartian@cpc9-burn8-2-0-cust51.10-1.cable.virginmedia.com, Ping timeout: 240 seconds)
15:04Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
15:07Parker955_Away is now known as Parker955
15:07TedHughes has left IRC (TedHughes!~stuartian@cpc9-burn8-2-0-cust51.10-1.cable.virginmedia.com)
15:20Lns has joined IRC (Lns!~Lns@173-16-218-84.client.mchsi.com)
15:20Lns has joined IRC (Lns!~Lns@pdpc/supporter/professional/lns)
15:24dobber has left IRC (dobber!~dobber@213.169.45.222, Remote host closed the connection)
15:29Parker955 is now known as Parker955_Away
15:56alkisg1 has left IRC (alkisg1!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
16:01dgeary2 has joined IRC (dgeary2!~david@114.73.104.51)
16:02dgeary2 has left IRC (dgeary2!~david@114.73.104.51, Client Quit)
16:08dead_inside has left IRC (dead_inside!~dead_insi@76.75.3.174, Quit: Leaving...)
16:10dead_inside has joined IRC (dead_inside!~dead_insi@76.75.3.174)
16:19vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
16:56gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)
17:09risca has joined IRC (risca!~risca@h240n6-n-a31.ias.bredband.telia.com)
18:22cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 260 seconds)
18:23alkisg1 has joined IRC (alkisg1!~alkisg@ubuntu/member/alkisg)
18:41ltspuser_44 has joined IRC (ltspuser_44!bd3c67f3@gateway/web/freenode/ip.189.60.103.243)
18:45
<ltspuser_44>
I can't seem to be able to find a list of thin clients supported by LTSP ? Is there one ?
18:47
<vagrantc>
not really
18:47
any x86 based processor that can PXE boot should be reasonably well supported if it has enough ram
18:48
at least 128MB, though 256MB+ would be better.
18:49
<||cw>
ltspuser_44: generally for x86 pc's. embedded thin clients don't need ltsp support, just linux
18:50
<ltspuser_44>
HP has a long list of hardware, some named thin clients, some named "smart zero clients" and some named "zero clients". They all PXE and the all have decent memory. Do all of them work with LTSP?
18:51
<||cw>
it's not that simple.
18:52
<vagrantc>
a lot of the HP thin clients could in theory work with LTSP, but come with their own OS on flash that replicates some of the functionality of LTSP ...
18:52
<||cw>
ltps is basically just a way to maintain an x86 or xmd64 chroot for the client systems to boot on, and some scripts to wrap it all up and make it easy to manage
18:52
anything x86 based will work.
18:52
<vagrantc>
if you can get it to boot to something other than the built-in OS
18:53
<||cw>
anything arm based can be made to work, but will take some extra work outside of normal ltsp operation
18:53
is it technically possible/feasible to have an arm chroot?
18:54
or even just a build arm image, made using qemu or something, that can be nbd'd to an arm system?
18:55
<vagrantc>
yes
18:55
<ltspuser_44>
So LTSP works with PC's only ? Not with ready-sold thin clients ?
18:55
<vagrantc>
at least on debian, installing qemu-user-static and binfmt-support makes arm work out of the box
18:56
ltspuser_44: it works with thin clients, but it depends on how the manufacturer made the thin client
18:56
ltspuser_44: there's no exact specification on what "thin client" is.
18:56
<||cw>
been playing with arm stuff recently, but not thin clients, nas's
18:58
<vagrantc>
i've gotten the arm baased HP t5325 to work as an LTSP client with some hackery
18:58
and to a lesser extent, the genesi efikamx smarttop
18:59
but i wouldn't recommend using an arm-based thin-client for your first LTSP setup. :)
18:59
<||cw>
butting my head with one issue, mounted the nas's ext3 rootfs on my desktop, and even if i change nothing, the nas won't boot it again.
18:59
think I'm going to have to break down and solder on the serial pads to get a console there
19:05
<ltspuser_44>
So it is mostly for PC's then ?
19:06bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
19:08
<vagrantc>
ltspuser_44: you can use any computer that supports network booting.
19:08
ltspuser_44: it would be easiest if you used x86 based thin clients, since those are best tested.
19:09
<ltspuser_44>
Can you give me the name of one ? I have not bought any yet.
19:09
<vagrantc>
ltspuser_44: but the term "thin client" doesn't necessarily mean much, so weather or not somethinng is marketed as a thin client will work with LTSP... it not immediately obvious
19:09
ltspuser_44: disklessworkstations.com
19:10
<ltspuser_44>
Yup ... but those are very expensive! $250 each. The ones from HP cost only $20 on eBay!
19:10
<vagrantc>
most thin clients will probably work, but it may require changing the default boot devices ... which may very greatly in how difficult it is.
19:11
if they're so cheap, buy one and try it out?
19:11
also, i'd recommend avoiding the ebox2300 models- they don't work well with modern versions of LTSP
19:11
which are marketed under a few different names
19:12
<||cw>
I've had some luck using these http://www.wdlsystems.com/modperl/view_services.cgi?r=detail&prod_num=1EB3MXM&aisle_id=1313
19:12Parker955_Away is now known as Parker955
19:12
<||cw>
you have to build your own kernel for them though since distros don't seem to be including the nic drivers by default
19:12
maybe just compiling the nic driver and rebuilding initrd would work
19:13
<vagrantc>
that sounds like a lot of hassle
19:13
<||cw>
they arne't particularly fast though, the via 500Mhz ones I have feel faster
19:14
but they're $100 more
19:15
vagrantc: yeah. I haven't deployed them as pxe boots because of it.
19:15
<vagrantc>
the ebox-3300 series isn't too bad
19:15
<||cw>
I only have 2, one's running XP, the other is linux installed to CF card and using usb wifi
19:15
that's the first one, or I copy the wrong link?
19:16
yeah, 330
19:16
4500 is the via based one
19:17
vagrantc: do you know what distros have the 3300's nic driver by default?
19:18
I've found ubuntu is a no go on them from 12.04+, they've dropped 586 support
19:19
<vagrantc>
||cw: worked with debian
19:20
<||cw>
stable or testing?
19:20robbie has joined IRC (robbie!~rob@CPE-60-231-21-101.qld.bigpond.net.au)
19:20
<vagrantc>
either, as of a few months ago
19:21
<||cw>
noted, will have to try it sometime.
19:21robbie has left IRC (robbie!~rob@CPE-60-231-21-101.qld.bigpond.net.au)
19:21
<||cw>
ubuntu's turning into a bitch to use with ltsp unless you're on proper 686+
19:22robbie has joined IRC (robbie!~rob@CPE-60-231-21-101.qld.bigpond.net.au)
19:22
<vagrantc>
so i hear
19:23
were they even dropping support for non-pae 686?
19:23
<||cw>
it's not pae that's the issue
19:23
the 3300's are 586, not 686, and that's the issue
19:24ricotz has left IRC (ricotz!~rico@unaffiliated/ricotz, Quit: Ex-Chat)
19:24* alkisg1 is thinking more every day about packaging a debian or even altlinux very thin chroot...
19:25
<alkisg1>
sudo apt-get install really-thin-client-that-support-586-and-32-mb-ram :P
19:25
<||cw>
I don't recall if the VIA Eden;s are 686 or not, having tried 12.04 on one yet
19:25robbie has left IRC (robbie!~rob@CPE-60-231-21-101.qld.bigpond.net.au, Client Quit)
19:26
<||cw>
I'd settle with a ppa with such a kernel that meets the with linux-image req
19:27
or some similar req to get patches and dist-upgrades
19:27
and then you'd be my hero
19:29
<vagrantc>
it's not just the kernel anymore
19:29
the whole OS is built without support
19:29ltspuser_44 has left IRC (ltspuser_44!bd3c67f3@gateway/web/freenode/ip.189.60.103.243, Ping timeout: 245 seconds)
19:29
<vagrantc>
alkisg1: we talked about auto-building such a chroot in the past...
19:30
<||cw>
:(
19:30
<alkisg1>
True, and since I'm getting more and more problems with non-pae and non-686 clients... I'm starting to think about it more :)
19:31
<vagrantc>
i should just go ahead and set up such a thing...
19:31
i've got a spare server sitting on the intertubes not doing much
19:31* vagrantc was just about to explore backporting wheezy's ltsp packages to squeeze
19:58alkisg1 has left IRC (alkisg1!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
21:00ltsp has joined IRC (ltsp!bot@ltsp.org)
21:03
<vagrantc>
[TiZ]: you may need to specify a .desktop file instead of a path to a binary ...
21:04
end-users and upstream LTSP has been mangling how LDM_SESSION works for the past couple years, so it's hard to know what the right thing to do is for any arbitrary version
21:04
<[TiZ]>
Possibly. I do have a working image now, so I'll try muppis's instructions to see if the file's being accessed.
21:04
Like... to make sure the /var lts.conf is even being loaded.
21:05
<vagrantc>
right
21:05
simplest way is to put SCREEN_07=shell in there, and it should drop you to a shell instead of loading up a graphical session
21:06
in the lts.conf from tftp
21:07
<muppis>
Yes, more simplier than what I suggested.
21:07
<[TiZ]>
Alright, well, let's give that a try.
21:08
<muppis>
But you still remove lts.conf from chroot to make sure.
21:08
+need
21:08
<[TiZ]>
Man, I should have just made a complete barebones fat client image instead of letting it stuff all of unity into the stupid thing... I'm only 1/4 of the way done.
21:09
<vagrantc>
no need to remove it from the chroot ... if it doesn't drop you to a shell, you know it isn't working...
21:09
<[TiZ]>
No shell. Unity.
21:09
<muppis>
vagrantc, but which one overrules the other one?
21:10roasted has left IRC (roasted!32c80ada@gateway/web/freenode/ip.50.200.10.218, Ping timeout: 245 seconds)
21:10
<vagrantc>
the tftp file should replace the one in the chroot on boot... so if it's not respecting the one from tftp, it's not working correctly.
21:10
so your problem is with the tftp transfer.
21:10
or at least, near it
21:10
<[TiZ]>
Okay... so what are my next steps?
21:12
<vagrantc>
i'd edit /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default and add a break=init line to the boot options
21:12
you probably will also need to disable the splash screen ... no idea how to do that these days ...
21:14
<muppis>
From same file, remove words quiet and splash
21:14
<vagrantc>
oh, the tftp fetching might be from usr/share/ltsp/init-ltsp.d ...
21:18
<muppis>
Hmm?
21:18
<[TiZ]>
Well, break=init took me to a shell... what should I do from there?
21:19
<vagrantc>
i'm not sure where the tftp fetch is on 12.04 ...
21:19* vagrantc develops on debian
21:19
<vagrantc>
look in /root/etc/lts.conf
21:25ltsp has joined IRC (ltsp!bot@ltsp.org)
21:25
<vagrantc>
or at least, it should be.
21:25
<[TiZ]>
I see. When I boot, $filename is just "pxelinux.0".
21:26
It doesn't have any kind of path like the lts.conf fetching script says it does.
21:26brunolambert has left IRC (brunolambert!blambert@nat/revolutionlinux/x-tkgscfazofnceeop, Quit: brunolambert)
21:27
<||cw>
if your tftp server config has a base path set, then $filename should not have a path, or should have a path relative to the base dir
21:28
pxelinux.0 is normally in the root of the tftp
21:28
<muppis>
Even this gets interesting I still need catch some sleep. Nights.
21:28
<vagrantc>
in a typical ltsp setup, it should be /ltsp/i386/pxelinux.0
21:29
<[TiZ]>
And I'm assuming s/i386/amd64 on 64-bit.
21:29* vagrantc has always thought the way it fetches the lts.conf from tftp was messed up
21:29
<vagrantc>
sure
21:29
<[TiZ]>
Well... I'm just gonna edit the script and make it do what I want. And then rebuild. *again.*
21:32
<||cw>
if you're using tftpd-hpa, the base is defined in /etc/default/tftpd-hpa
21:33
<[TiZ]>
Hmm... my boss was the one who actually set up the LTSP server, and delegated the session set up to me. And he appears to have changed TFTP_DIRECTORY to /var/lib/tftpboot/ltsp/amd64.
21:33
Somehow I get the sense that it's not supposed to be that.
21:34
<||cw>
so if the default base is /var/lib/tftpboot/, your DHCP server will need to send ltsp/i386/pxelinux.0 or ltsp/amd64/pxelinux.0 as the filename
21:34
<vagrantc>
no
21:34
<||cw>
ah, so then your "pxelinux.0" is correct
21:34
<[TiZ]>
Ah ha! I know why he changed it.
21:34
<vagrantc>
there's no good reason to do it that way, though.
21:34
<||cw>
well, setting the base like that means you can only boot x64 clients
21:35
<[TiZ]>
There's another PXE server set up here, and its boot path is simply pxelinux.0 as well.
21:35
<||cw>
same here, but you can still make it work
21:36
basically, you copy the kernels to the other tftp server and set configs for the clients there
21:36
that's the easiest
21:37
after a kernel update, copy /var/lib/tftpboot/ltsp to the root of the other tftp
21:38
everything else works the same, keeping the ltsp/arch/* filenames
21:39
<[TiZ]>
If I can avoid having to derp around with the included scripts, that's better than hacking things around just to suit my boss's incorrect configuration.
21:39
<||cw>
you'll need add nbdroot=x.x.x.x:2000 to the kenrl append line though
21:40
<[TiZ]>
Ah, I have a shell. So that did it, then. I had to reconfigure the tftp server and dhcp server.
21:54
And now I have to figure out how to make it start the user x session...
21:55
<vagrantc>
you can't isolate these onto their own network?
21:55
<[TiZ]>
What?
21:55
<vagrantc>
it seems like a bad idea to have multiple PXE servers on a single network ... if you could set up a separate network for the LTSP clients, you could avoid a lot of headache
21:56
if that's a feasible option
21:56
the recommended LTSP server setup involves a server with two network cards- one for internet access, and another for the LTSP network
21:57
but it requires an isolated network dedicated to LTSP
21:57
<[TiZ]>
I don't know much about the network infrastructure here... but there is a default boot server hostname and bootfile name configured, and then for the LTSP clients, those get overridden.
21:57
It doesn't seem like particularly much headache to have reconfigured it.
21:58
<vagrantc>
the existing network boot setup isn't actually in use?
21:58
<[TiZ]>
It's more headache trying to get this X session crap working. All I want LDM to run is ~/.xsession.
21:59
In this building, by default, network boot takes you to a server where you can access miscellaneous tools like ghostcast.
21:59khildin_ has left IRC (khildin_!~khildin@ip-80-236-222-107.dsl.scarlet.be, Quit: I'm gone, bye bye)
22:00
<vagrantc>
it should run ~/.xsession by default...
22:00
unless you try to set LDM_SESSION
22:00
or ubuntu's done something messed up with default session handling.
22:00
<[TiZ]>
I think they have done something messed up with default session handling.
22:04
I don't normally have any particular hate for Unity.
22:05
But now I completely detest it because I can't make it go the hell away!!!
22:07
<vagrantc>
alkisg: hrm. the versioned dependencies on newer nbd are makking ltsp hard to backport :(
22:07
alkisg: nbd was fairly easy to backport a few versions ago, but no longer.
22:07
<[TiZ]>
Well... thank you all for the help with the lts.conf. I have to go do other stuff now. Take care.
22:08
<vagrantc>
good luck
22:08
<[TiZ]>
Thanks.
22:08[TiZ] has left IRC ([TiZ]!~TiZ@192.122.237.253, Quit: Leaving)
22:15dead_inside has left IRC (dead_inside!~dead_insi@76.75.3.174, Quit: Leaving...)
22:27bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Read error: Operation timed out)
22:47Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 268 seconds)
23:26cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
23:51adrianorg__ has left IRC (adrianorg__!~adrianorg@177.18.49.77, Read error: Connection reset by peer)
23:52adrianorg__ has joined IRC (adrianorg__!~adrianorg@177.18.101.98)
23:53monteslu_ has joined IRC (monteslu_!~monteslu@ip68-109-174-213.ph.ph.cox.net)
23:53ecolinux has joined IRC (ecolinux!~ecolinux@5.79.121.78.rev.sfr.net)
23:54
<ecolinux>
hello
23:56
i try to make a package ltsp-archlinux for archlinux but docs is not really .....
23:56
;)
23:56monteslu has left IRC (monteslu!~monteslu@ip68-109-174-213.ph.ph.cox.net, Ping timeout: 240 seconds)