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


Channel log from 8 April 2015   (all times are UTC)

00:12gdi2k has joined IRC (gdi2k!~gdi2k@49.151.77.1)
00:12lei_ has joined IRC (lei_!bb0cff7e@gateway/web/freenode/ip.187.12.255.126)
00:12
<lei_>
oi
00:12lei_ has left IRC (lei_!bb0cff7e@gateway/web/freenode/ip.187.12.255.126, Client Quit)
00:29MarconM has joined IRC (MarconM!~Marcelo@201-25-75-23.cbace702.dsl.brasiltelecom.net.br)
00:29MarconM has joined IRC (MarconM!~Marcelo@unaffiliated/marconm)
02:02Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 265 seconds)
02:07Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
02:37gbaman_ has left IRC (gbaman_!~gbaman@host81-148-184-31.in-addr.btopenworld.com, Remote host closed the connection)
03:08sutula has left IRC (sutula!~sutula@207-118-178-73.dyn.centurytel.net, Ping timeout: 272 seconds)
03:09sutula has joined IRC (sutula!~sutula@207-118-178-73.dyn.centurytel.net)
03:57telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
03:58telex has joined IRC (telex!teletype@freeshell.de)
04:02bojan has joined IRC (bojan!75d82b84@gateway/web/freenode/ip.117.216.43.132)
04:03
<bojan>
Can anybody please help me suddenly all my ps/2 mouse is not working in all my client computers but USB is working good
04:13
<MarconM>
use usb -D
04:13
=D
04:18
<vagrantc>
bojan: what distro and release?
04:18
bojan: did it happen after updating the kernel or something?
04:19* vagrantc could easily see ps/2 support getting dropped by accident
04:20bojan has left IRC (bojan!75d82b84@gateway/web/freenode/ip.117.216.43.132, Ping timeout: 246 seconds)
04:20MarconM has left IRC (MarconM!~Marcelo@unaffiliated/marconm, Ping timeout: 240 seconds)
04:21H3suS has joined IRC (H3suS!~Marcelo@177-2-93-250.3g.brasiltelecom.net.br)
04:21
<H3suS>
!ltsp-pnp
04:21
<ltsp>
ltsp-pnp: ltsp-pnp is an alternative (upstream) method to maintain LTSP installations for thin and fat clients that doesn't involve chroots: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
04:23bojan has joined IRC (bojan!75d0d2f2@gateway/web/freenode/ip.117.208.210.242)
04:23
<bojan>
MarconM:But it worked good so far...from today it is making problem
04:23
vagrantc:Yes
04:24
please somebody help me...Office hours started
04:25
vagrantc:Its ubuntu 12.04 alternate amd64
04:27
<vagrantc>
bojan: this is a new install, or an upgraded install?
04:30
<bojan>
vagrantc:i have already installed and its worked good
04:31
vagrantc:i just updated my chroot with apt-get update and then ltsp-update-image
04:35
when i done update chroot i got this following error "http://paste.ubuntu.com/10769909/"
04:37
<vagrantc>
bojan: did you use ltsp-chroot to get into that shell?
04:38
bojan: try with: ltsp-chroot --mount-all apt-get -f install
04:39
<bojan>
vagrantc:I have just mount /proc to /opt/ltsp/amd64/proc and then apt-get install -f its installed now correctly without any error in chroot
04:39
<vagrantc>
my wild guess is the kernel you're booting and the kernel in the image are mismatched due to a partial upgrade...
04:40
<bojan>
vagrantc:What can i do now??
04:40
<vagrantc>
finish the upgrade you started?
04:40
<bojan>
yes its finished
04:40
<vagrantc>
bojan: try with: ltsp-chroot --mount-all apt-get upgrade
04:40
<bojan>
what will happen if i give this command
04:40
??
04:41
<vagrantc>
it will mount several of the filesystems (such as proc) chroot into your chroot, and inside your chroot run apt-get upgrade
04:41
<H3suS>
vagrantc: about the bug with lxde session
04:41
do u know ho to fix
04:41
<vagrantc>
H3suS: i don't really know anything about it
04:41
<H3suS>
vagrantc: thanks sorry about to ask again
04:42
<bojan>
vagrantc:The upgrade has done well once i mount /proc now i am updating the image for booting...Let me check whether the mouse is working good after this updation
04:42
vagrantc:Am little confused that what is location of lts.conf??
04:43
<vagrantc>
bojan: on ubuntu it should be /var/lib/tftpboot/ltsp/CHROOT_NAME/lts.conf
04:43
although, depending on your setup, it may try /var/lib/tftpboot/ltsp/i386/lts.conf no matter what your chroot is.
04:44
there's also /opt/ltsp/*/etc/lts.conf ... but you usually don't want to edit that directly, otherwise you have to update your images after every change.
04:44
<bojan>
vagrantc:It was in that location only but after my update i lost my lts.conf file
04:44
vagrantc:Then how should i update
04:44
<vagrantc>
bojan: i don't know what you mean?
04:44
bojan: do you *need* and lts.conf?
04:45
<bojan>
lts.conf is need right??
04:45
<vagrantc>
only if the defaults don't work
04:45
<bojan>
so ps/2 mouse is default right??
04:45
<vagrantc>
unless there's a bug in the version of ltsp you're using ... i do recall something from a long time ago...
04:46
bojan: you shouldn't need to specify ps/2 in lts.conf
04:46
bojan: like i said, you probably had a partial upgrade and mismatched versions so the modules weren't present to support some peripherals.
04:47
bojan: it was working before the updates?
04:47
<bojan>
vagrantc:yes it worked good before the update
04:47
vagrantc:what will be final solution??
04:48
<vagrantc>
bojan: depends on what's really wrong ...
04:48
bojan: it's unclear to me that you've really finished the upgrade properly, or updated your image, or updated the tftp directories
04:49
bojan: but once the upgrade is done: ltsp-update-image ; ltsp-update-kernels
04:49
or maybe ltsp-update-image && ltsp-update-kernels
04:49
(the extra call to ltsp-update-kernels might not be needed, but shouldn't cause any problems)
04:54
<bojan>
vagrantc:It is working good now
04:54
thank you so much
04:55
vagrantc:one more doubt that i have configured nfs in LTSP server and want some authentication for that like NIS,LDAP,,<What will be better and will works good with LTSP
04:55
??
05:14zChris has left IRC (zChris!~zChris@h-36-243.a204.priv.bahnhof.se)
05:39
<vagrantc>
bojan: you're using NFS home dirs? or NFS for the LTSP root?
05:39
bojan: or NFS for something else?
05:39
bojan: i've never actually set up NFS with authentication... i always use unauthenticated NFS... almost exclusively read-only.
05:40MarconM has joined IRC (MarconM!~Marcelo@unaffiliated/marconm)
05:43H3suS has left IRC (H3suS!~Marcelo@177-2-93-250.3g.brasiltelecom.net.br, Ping timeout: 252 seconds)
05:57bojan has left IRC (bojan!75d0d2f2@gateway/web/freenode/ip.117.208.210.242, Ping timeout: 246 seconds)
06:02MarconM has left IRC (MarconM!~Marcelo@unaffiliated/marconm, Quit: Leaving)
06:11gbaman has joined IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com)
06:18gbaman has left IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com, Ping timeout: 250 seconds)
07:03vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
07:08FrozenZia has left IRC (FrozenZia!pbrown@evo.paivola.fi, Ping timeout: 272 seconds)
08:03andygraybeal has left IRC (andygraybeal!~andy@h36.21.30.71.dynamic.ip.windstream.net, Ping timeout: 272 seconds)
08:09andygraybeal has joined IRC (andygraybeal!~andy@h36.21.30.71.dynamic.ip.windstream.net)
09:43bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
09:52gbaman has joined IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com)
09:57gbaman has left IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com, Ping timeout: 265 seconds)
10:28ricotz has joined IRC (ricotz!~rico@p5B2AA3C1.dip0.t-ipconnect.de)
10:28ricotz has joined IRC (ricotz!~rico@ubuntu/member/ricotz)
11:06ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 252 seconds)
11:08ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
11:15vinod_ has joined IRC (vinod_!3b5bc151@gateway/web/freenode/ip.59.91.193.81)
11:15
<vinod_>
hello
11:16
i just installed edubuntu 14.04 lts with LTSP
11:16
it is working
11:17
but when i restart client then getting error. like soket error
11:17
after restart server is again working good
11:18
can u help me about this type of problem what i am facing
11:24Faith has joined IRC (Faith!~paty@unaffiliated/faith)
11:31vinod_ has left IRC (vinod_!3b5bc151@gateway/web/freenode/ip.59.91.193.81)
11:50gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
11:55gvy has left IRC (gvy!~mike@altlinux/developer/mike, Ping timeout: 256 seconds)
12:05bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 264 seconds)
12:06gbaman has joined IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com)
12:09gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
12:11gbaman_ has joined IRC (gbaman_!~gbaman@host81-148-184-31.in-addr.btopenworld.com)
12:13telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
12:14telex has joined IRC (telex!teletype@freeshell.de)
12:15gbaman has left IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com, Ping timeout: 276 seconds)
12:16gbaman_ has left IRC (gbaman_!~gbaman@host81-148-184-31.in-addr.btopenworld.com, Ping timeout: 252 seconds)
12:19Jane_ has joined IRC (Jane_!02dcaabf@gateway/web/freenode/ip.2.220.170.191)
12:22
<Jane_>
hi I have just tried to set up Pinet and get as far as the login screen. at this point i am unable to input username as the mouse and keyboard don't appear to work. I have tried the RPi stand alone using a different SD card and the mouse and keyboard work. Can you advise what is happening?
12:42MarconM has joined IRC (MarconM!~Marcelo@189.74.151.215)
12:42MarconM has joined IRC (MarconM!~Marcelo@unaffiliated/marconm)
12:44
<MarconM>
!ping
12:44
<ltsp>
pong
12:44
<MarconM>
morning
12:55Jane_ has left IRC (Jane_!02dcaabf@gateway/web/freenode/ip.2.220.170.191, Ping timeout: 246 seconds)
13:03khildin has joined IRC (khildin!~khildin@ip-213-49-87-196.dsl.scarlet.be)
13:07AlexPortable has joined IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-qiqyyvdwmdqrkykt)
13:09Jane_ has joined IRC (Jane_!02dcaabf@gateway/web/freenode/ip.2.220.170.191)
13:11
<Jane_>
hi I have just tried to set up Pinet and get as far as the login screen. at this point i am unable to input username as the mouse and keyboard don't appear to work. I have tried the RPi stand alone using a different SD card and the mouse and keyboard work. Can you advise what is happening?
13:14ldr has joined IRC (ldr!555b42f9@gateway/web/freenode/ip.85.91.66.249)
13:14
<ldr>
hello
13:14
I have a probably pretty basic question but haven't found any clue in documentation
13:15
I have to ltsp servers installed, let's say ltsp1 and ltsp2
13:15
and several thin clients, some of them using ltsp1 and others using ltsp2
13:16
what I want to know is how thin clients knows what ltsp server to boot up
13:18
my knowledge of boot process is when a thinkclient turns on it sends a DHCPDISCOVER and the dhcp service in the server answers
13:19
but it is a matter of the first server to answer is the server the thinclient chooses to request an image to boot from?
13:21m_ has joined IRC (m_!d906b893@gateway/web/freenode/ip.217.6.184.147)
13:25m_ has left IRC (m_!d906b893@gateway/web/freenode/ip.217.6.184.147, Ping timeout: 246 seconds)
13:25Jane_ has left IRC (Jane_!02dcaabf@gateway/web/freenode/ip.2.220.170.191, Ping timeout: 246 seconds)
13:57asmok has joined IRC (asmok!3e4ee4b0@gateway/web/freenode/ip.62.78.228.176)
13:58asmok has left IRC (asmok!3e4ee4b0@gateway/web/freenode/ip.62.78.228.176)
15:06gbaman has joined IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com)
15:16bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
15:19khildin has left IRC (khildin!~khildin@ip-213-49-87-196.dsl.scarlet.be, Ping timeout: 256 seconds)
15:29SeuMadruga has joined IRC (SeuMadruga!~Marcelo@191.222.241.216)
15:30uXus has left IRC (uXus!~uXus@217.77.222.72, Quit: ail bi bek)
15:30
<SeuMadruga>
i installed lubuntu 14.04 i386, i having problem with log in ... when i try to log ... reboo the thin client
15:30
how can i fix this
15:32uXus has joined IRC (uXus!~uXus@217.77.222.72)
15:48
<SeuMadruga>
!ltsp-pnp | echo SeuMadruga
15:48
<ltsp>
SeuMadruga ltsp-pnp: ltsp-pnp is an alternative (upstream) method to maintain LTSP installations for thin and fat clients that doesn't involve chroots: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
16:17vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
16:31ltsp_fan has joined IRC (ltsp_fan!69e2509b@gateway/web/freenode/ip.105.226.80.155)
16:33
<SeuMadruga>
Γειά σου
16:34
<ltsp_fan>
hi everyone, thanks for offering to help: I have two unrelated problems: 1) I'm running Debian Testing, the clients boot succesfully but have a green tinge to the desktop 2) how do I enable nbd client root mounting and disable nfs
16:37
<vagrantc>
ltsp_fan: just how green are we talking? what video cards?
16:38
ltsp_fan: switching to NBD isn't too difficult... some of the steps are described here: https://wiki.debian.org/LTSP/Howto
16:39SeuMadruga has left IRC (SeuMadruga!~Marcelo@191.222.241.216, Read error: Connection reset by peer)
16:39
<vagrantc>
ltsp_fan: although it's documenting how to use the LTSP-PNP method, rather than chroots ... the concepts are the same.
16:42
ltsp_fan: you'll need to edit update-kernels.conf in the chroot, ltsp-chroot dpkg-reconfigure linux-image-x.y.x, ltsp-update-image /opt/ltsp/XXX, ltsp-config nbd-server, service nbd-server restart
16:43
ltsp_fan: i often configure my environments to enable either, and have a boot menu to select between them
16:45
<ltsp_fan>
thanks so much, yes I read https://wiki.debian.org/LTSP/Howto but wasn't sure how much applied because I have a different server to client environment
16:45
from speaking to alksig a couple of a months ago nbd is the preferred choice, why still give an option?
16:45
<vagrantc>
ltsp_fan: main thing to change is BOOT_METHODS
16:46
<ltsp_fan>
whats IPAPPEND=3 for?
16:46
<vagrantc>
NBD is much ess resilient
16:47
IPAPPEND re-uses the initial DHCP request made via PXE rather than making a second request via initramfs
16:47
should be safe to use
16:47
<ltsp_fan>
cool let me try this now
16:49
<vagrantc>
ltsp_fan: NBD can't handle brief server disconnects as well as NFS, in my experience ... which makes it less stable. it is much faster, and by and large works fine. i also find having to run ltsp-update-image after every change can result in confusion where the chroot is updated but the client is running an older image...
16:49
a good compromise is NFS+squashfs images
16:50
has most of the speed benefits of NBD, but is as reliable as NFS
16:50
still the image vs. chroot confusion potential
16:51
some of it may be my own bias in developing LTSP in that I do a lot of testing and so consistancy of state comes up a lot more often :)
16:52
but it's now fairly easy to switch back and forth between them
16:54* vagrantc still resents the confusion over lts.conf in tftp vs. in the chroot that was implemented to work with NBD
16:56
<vagrantc>
for jessie+1 we may have to switch away from NFS, as aufs is no longer in recent kernels, and mainline overlayfs isn't compatible with using NFS as a layer
16:56
(though works fine with NFS+squashfs images)
17:15andygraybeal has left IRC (andygraybeal!~andy@h36.21.30.71.dynamic.ip.windstream.net, Ping timeout: 250 seconds)
17:18
<ltsp_fan>
ok i've started following your instructions. I really value these other comments which plan to ask you about further, but in the mean time I'm at the chroot stage and a question occured to me:
17:18
when I dpkg-reconfigure
17:19
after I've chrooted
17:20
<vagrantc>
i'd recommend using "ltsp-chroot" rather than running from a chrooted shell
17:20
<ltsp_fan>
the howto recommends I use uname -r to determine the kernel
17:20
but that returns the server kernel, no?
17:20
<vagrantc>
yes, and with ltsp-pnp, that's always going to be the same
17:20
(well, mostly)
17:20
<ltsp_fan>
what's the difference between ltsp-root and chroot
17:20
<vagrantc>
but with a chroot, you may have a different version
17:21
ltsp-chroot sets a few variables to prevent daemons from spawning inside the chroot, and also can be used to automatically mount some things (such as /proc) which may be necessary for some packages to install/upgrade
17:21
it also automatically figures out which chroot to use
17:22
<ltsp_fan>
ok thanks that helps a lot
17:22
<MarconM>
vagrantc: so its recommended use ltsp-chroot
17:22
?
17:22
<ltsp_fan>
but my uname -r still says:
17:22
<vagrantc>
MarconM: with ltsp chroots, yes.
17:22
ltsp_fan: your "uname -r" is not relevent to what kernel to reconfigure in the chroot
17:22
<ltsp_fan>
3.14-2-amd64
17:22
<MarconM>
vagrantc: when the client load .. i try to log on tty
17:23
user and pass dont works
17:23
<vagrantc>
MarconM: yes, there are no users configured on the ltsp client by default.
17:23
<MarconM>
vagrantc: i am using ltsp-pnp
17:23
<vagrantc>
ltsp_fan: but it does sound like you're running a very old kernel
17:24
MarconM: there are no users in the client image.
17:24
MarconM: LDM creates them at login time.
17:24
<MarconM>
how i fix that
17:24
<vagrantc>
why do you need to?
17:24
<MarconM>
confuse
17:24
do i need to create or add users to ltsp-pnp ?
17:24
<ltsp_fan>
so how do I determine what kernel to reconfigure?
17:25
<vagrantc>
MarconM: you create the users on the server. they authenticate against the server. there are normally no users configured for console login, only through LDM.
17:26
ltsp_fan: ltsp-chroot dpkg -l 'linux-image-*'
17:26
<MarconM>
ok
17:26
<vagrantc>
ltsp_fan: you just need to do that after changing update-kernels.conf ... in future kernel updates it will happen automatically
17:26
<MarconM>
but on ldm ... i try to log in and nothing happend
17:27
just reboot
17:27
<vagrantc>
sounds like you have some other problem.
17:27
<MarconM>
yes
17:27
i think this is a bug on lxde or ltsp-pnp
17:27
<vagrantc>
MarconM: try setting SCREEN_02=shell and SCREEN_07=ldm in lts.conf
17:27
<MarconM>
alsing help me to fix
17:27
ok
17:27
<vagrantc>
that will give you a root sheel on tty2 to debug with
17:32
<MarconM>
vagrantc: on lts.conf can i specific wich machine by MAC address will log in with user1 user2 and pass too
17:32
?
17:33
<vagrantc>
MarconM: yes.
17:33
though the simplest thing is to set up ltsp1 through ltsp255
17:34
and just use the defaults
17:34
e.g. 192.168.67.20 -> ltsp20 or 192.168.67.150 -> ltsp150
17:35
most of them will probably never be used, but it's easier than configuring all of them in lts.conf
17:49bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Quit: Goin' down hard)
17:55gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: ~)
18:04andygraybeal has joined IRC (andygraybeal!~andy@h66.61.188.173.dynamic.ip.windstream.net)
18:17telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
18:18Jane_ has joined IRC (Jane_!02dcaabf@gateway/web/freenode/ip.2.220.170.191)
18:18telex has joined IRC (telex!teletype@freeshell.de)
18:19andygraybeal has left IRC (andygraybeal!~andy@h66.61.188.173.dynamic.ip.windstream.net, Read error: Connection reset by peer)
18:22Jane_ has left IRC (Jane_!02dcaabf@gateway/web/freenode/ip.2.220.170.191)
18:32MarconM has left IRC (MarconM!~Marcelo@unaffiliated/marconm, Ping timeout: 246 seconds)
18:32championofcyrodi has left IRC (championofcyrodi!~cott@50-205-35-98-static.hfc.comcastbusiness.net, Remote host closed the connection)
18:33MarconM has joined IRC (MarconM!~Marcelo@189.74.151.215)
18:33MarconM has joined IRC (MarconM!~Marcelo@unaffiliated/marconm)
18:38championofcyrodi has joined IRC (championofcyrodi!~cott@50-205-35-98-static.hfc.comcastbusiness.net)
18:39jane_ has joined IRC (jane_!02dcaabf@gateway/web/freenode/ip.2.220.170.191)
18:56jane_ has left IRC (jane_!02dcaabf@gateway/web/freenode/ip.2.220.170.191, Ping timeout: 246 seconds)
19:10
<ltsp_fan>
hi I'm back, thanks for the help so far
19:10
vagrantc: I think I completed all the steps but I can't seem to boot
19:11
when you said the kernel was old, I tried to fix that by installing 686-pae kernel in the chroot
19:11
is that the right way?
19:12gbaman has left IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com, Remote host closed the connection)
19:12gbaman has joined IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com)
19:13
<Faith>
hey, vagrantc, you said you have a menu boot for images, how did you do?
19:13
<vagrantc>
ltsp_fan: well, jessie currently uses a 3.16 kernel, you mentioned 3.14
19:13
<ltsp_fan>
I also get this error when reconfigure the kernel: cat: /proc/cmdline: No such file or directory
19:14
<vagrantc>
ltsp_fan: that should be fine
19:14
Faith: edit update-kernels.conf ... there should be commented out entries for menu
19:15
Faith: either in /opt/ltsp/*/etc/ltsp/update-kernels.conf or /etc/ltsp/update-kernels.conf if using ltsp-pnp methods.
19:15
<Faith>
vagrantc, it does only work with ltsp-pnp? I use nbd
19:16
<ltsp_fan>
I did a fresh install of jessie, why would the server have a 3.14 kernel? How do I fix it?
19:16
<vagrantc>
Faith: no, the location of the file you edit changes if you're using chroots or ltsp-pnp
19:17
<Faith>
vagrantc, ahh ok, tks :)
19:17
<vagrantc>
ltsp_fan: maybe you used ancient install media?
19:17
ltsp_fan: apt-get upgrade should fix it...
19:19
<ltsp_fan>
ah, you're right I assumed testing was Jessie, but yes, I did then do apt-get upgrade with the jessie repos
19:21
oh ok i forgot to run apt-get dist-upgrade
19:22
<vagrantc>
testing has been jessie for quite some time, though at the end of the month will transition to stable :)
19:22gbaman has left IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com, Remote host closed the connection)
19:23gbaman has joined IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com)
19:26
<ltsp_fan>
ok so back to getting nbd to work, the client says: chroot can't access test
19:26
did I miss a step?
19:27AlexPortable has left IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-qiqyyvdwmdqrkykt, Quit: Connection closed for inactivity)
19:31
<ltsp_fan>
got to go for now, I hope to continue tomorrow, thanks
19:31ltsp_fan has left IRC (ltsp_fan!69e2509b@gateway/web/freenode/ip.105.226.80.155, Quit: Page closed)
20:22Faith has left IRC (Faith!~paty@unaffiliated/faith, Quit: Saindo)
20:52MarconM has left IRC (MarconM!~Marcelo@unaffiliated/marconm, Quit: Leaving)
20:53hatcha has joined IRC (hatcha!c820f7ca@gateway/web/freenode/ip.200.32.247.202)
20:53
<hatcha>
hey
20:55
am new to ltsp. now can i get my thin client to boot to rdp login?
20:55gbaman has joined IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com)
20:55
<vagrantc>
use SCREEN_07=xfreerdp in lts.conf and RDP_OPTIONS and RDP_SERVER
20:56
i haven't used it myself beyond testing, so good luck
20:58
gbaman: heya! just got an rpi2 today
21:00khildin has joined IRC (khildin!~khildin@ip-213-49-87-196.dsl.scarlet.be)
21:00
<vagrantc>
will give it a whirl with ltsp using debian armhf soonish!
21:01hatcha has left IRC (hatcha!c820f7ca@gateway/web/freenode/ip.200.32.247.202, Quit: Page closed)
21:04gbaman has left IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com, Ping timeout: 245 seconds)
21:28ricotz has left IRC (ricotz!~rico@ubuntu/member/ricotz, Quit: Ex-Chat)
21:52khildin has left IRC (khildin!~khildin@ip-213-49-87-196.dsl.scarlet.be, Remote host closed the connection)
22:01gbaman has joined IRC (gbaman!~gbaman@host81-148-184-31.in-addr.btopenworld.com)
22:02
<gbaman>
vagrantc: cool. They are really nice, the speed difference is very noticeable, especially when doing stuff like web browsing
22:03
<vagrantc>
the pi i have is the 256MB model, so i suspect it will be *really* noticeable
22:03
<gbaman>
ah..
22:03
yeah..
22:04
just a tad..
22:04
Plus, it can hit PiNet login screen in under 30 seconds :)
22:04
<vagrantc>
heh
22:05
<gbaman>
Vs the the older Pis which take about 55-60 seconds
22:05
Have already had a few schools comment who got some that it is faster than their normal Windows machines :)
22:07
<vagrantc>
gbaman: there's nothing really ubuntu-specific with pinet, is there? it would be feasible to install on a debian server?
22:07
<gbaman>
Erm..
22:08
It uses $SUDO_USER a lot, which I don't believe Debian has
22:08
It will complain if you try and install it on Debian
22:08
<vagrantc>
huh
22:08
<gbaman>
$SUDO_USER, as in the user than ran the script with sudo
22:08
One of the reasons I stopped supporting both was Debian didn't seem to set it
22:09
Best bet is Ubuntu 14.04
22:09
As everything will "just work"
22:09
<vagrantc>
SUDO_USER seems to be there on Debian 8
22:09
jessie
22:09
<gbaman>
Oh?
22:09
Then other than that, don't see any reason why not? But don't install it on a machine you intend to use for anything else!
22:10
Never wrote an uninstaller as no one ever really needed one
22:10
<vagrantc>
was thinking about trying it out using a virtual machine
22:10
<gbaman>
Yeah, will work fine
22:10
<vagrantc>
since i've heard so much about it... :)
22:10
<gbaman>
I even have a virtualbox guide :) http://pinet.org.uk/articles/installation/virtualbox.html
22:11
If you are doing a vm though, I will still recommend Ubuntu
22:11
Is the one I have tested and know everything works with
22:11
Ubuntu 14.04 desktop
22:11
<vagrantc>
would you accept debianization bug reports? :)
22:11
<gbaman>
:)
22:11
Maybe
22:11
Keep in mind the target audience though
22:11
teachers
22:12
And as much as I love Debian, Ubuntu is more beginner friendly
22:12
But I accept pull requests! https://github.com/PiNet/PiNet
22:12* vagrantc doesn't believe "teachers" == "beginners"
22:13
<gbaman>
Oh trust me... Most are
22:13
Especially with Linux
22:13
<vagrantc>
that's like saying teenagers aren't good with computers because they don't have experience or old people aren't good with computers because they're set in their ways
22:14
i guess i tend to run into teachers running LTSP on debian :)
22:14
<gbaman>
But, you need to be very careful not to scare them off
22:14
PiNet is targeted at being extremely simple
22:14
As you will see
22:14
<vagrantc>
i tend to only support people who clearly know what they want
22:15
<gbaman>
These teachers want a system for user accounts usually, for the Pis
22:15
But haven't a clue of any of the insides of how to do it
22:15
<vagrantc>
but anyways... maybe i'll finally get around to installing this stuff
22:15
<gbaman>
:)
22:18
Well do let me know what you think (and if anything should be changed)
22:18
and feel free to try and break stuff :)
22:18
<vagrantc>
it's a single-network card setup?
22:18
<gbaman>
Yeah
22:19
Most schools just repurpose an old desktop machine
22:19
<vagrantc>
sure
22:19
<gbaman>
So asking them to buy another network card for it is pushing it
22:19
<vagrantc>
single-nic setups have a lot of advantages
22:19
<gbaman>
The biggest being simplicity in my opinion
22:20
<vagrantc>
what with fat clients and all ... the main advantage of a two-nic setup was to isolate the thin client network which didn't need internet access ... but now with localapps and fatclients that requires NAT ugliness.
22:20
so single-nic makes a lot of sense
22:21* vagrantc waves
22:21vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
23:58adrianorg has left IRC (adrianorg!~adrianorg@177.204.151.58.dynamic.adsl.gvt.net.br, Ping timeout: 265 seconds)