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


Channel log from 13 June 2012   (all times are UTC)

00:04bengoa has joined IRC (bengoa!~bengoa@2001:1291:229:2:216:cbff:feab:6cc9)
00:08Phantomas has left IRC (Phantomas!~Phantomas@unaffiliated/phantomas, Ping timeout: 246 seconds)
00:11bengoa has left IRC (bengoa!~bengoa@2001:1291:229:2:216:cbff:feab:6cc9, Quit: Leaving.)
00:13dead_inside has left IRC (dead_inside!~dead_insi@76.75.3.174, Quit: Leaving...)
00:18hughessd has left IRC (hughessd!~steve@173-164-117-109-Oregon.hfc.comcastbusiness.net, Quit: gone for some reason)
00:55telex has left IRC (telex!~telex@freeshell.de, Ping timeout: 244 seconds)
00:57Parker955_Away is now known as Parker955
01:00telex has joined IRC (telex!~telex@freeshell.de)
01:01Parker955 is now known as Parker955_Away
01:04monteslu__ has joined IRC (monteslu__!~monteslu@ip68-109-174-213.ph.ph.cox.net)
01:04vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Ping timeout: 252 seconds)
01:07monteslu_ has left IRC (monteslu_!~monteslu@ip68-109-174-213.ph.ph.cox.net, Ping timeout: 245 seconds)
01:14enyc has left IRC (enyc!~enyc@muddle.enyc.org.uk, Ping timeout: 248 seconds)
01:24andygraybeal_ has joined IRC (andygraybeal_!~andy@h98.94.213.151.dynamic.ip.windstream.net)
02:12enyc has joined IRC (enyc!~enyc@muddle.enyc.org.uk)
02:15
<brian418>
hi, anyone have the time or is willing to help a ltsp noob with build-client problem ?
02:36Phantomas has joined IRC (Phantomas!~Phantomas@unaffiliated/phantomas)
02:36adrianorg__ has joined IRC (adrianorg__!~adrianorg@186.213.158.214)
02:39adrianorg_ has left IRC (adrianorg_!~adrianorg@186.215.22.162, Ping timeout: 252 seconds)
02:40Parker955_Away is now known as Parker955
03:08
<muppis>
brian418, just tell the problem and hang around. That way you will get helped more likely.
03:08Parker955 is now known as Parker955_Away
03:09
<brian418>
muppis: thanks for the tip
03:12
getting this error when try to build client after upgrading to 10.04 LTS server: E: Failed getting release file http://archive.ubuntu.com/ubuntu/dists/lucid/Release
03:12
error: LTSP client installation ended abnormally
03:19
<muppis>
As you can see, those are reqular urls, so you can try access them with Firefox or wget to test are those working. If file can be fetched with other application, then just try to rebuild.
03:20
For me that Release file can be found nicely.
03:20
<brian418>
muppis: browser and wget works
03:21
<muppis>
Using any proxy in apt?
03:21
<brian418>
muppis: no prox
03:22
muppis: I went from 6.04 to 8.04 with no probs....then I decided to try and go to 10.04 when it broke
03:24
<muppis>
And apt-get update works at server itself?
03:24
<brian418>
muppis: yes
03:27Phantomas has left IRC (Phantomas!~Phantomas@unaffiliated/phantomas, Read error: Operation timed out)
03:30
<muppis>
By now I can't figure what can cause that.
03:31
<brian418>
muppis: I've been trying to solve this on and off the past month
03:31Phantomas has joined IRC (Phantomas!~Phantomas@unaffiliated/phantomas)
03:33
<muppis>
Personally I use apt-cacher as proxy to ease rebuilding things, but I do lot of testing.
03:34
And need to get to work, so I'll be back in a hour.
03:35
<brian418>
muppis: I'm pretty clear on networking issues but this has gotten to me
03:38
muppis: thanks for your help
03:51staffencasa has left IRC (staffencasa!~staffenca@128.193.8.220, Ping timeout: 250 seconds)
03:52map7 has left IRC (map7!~map7@teksup41.lnk.telstra.net, Read error: Connection reset by peer)
03:53map7 has joined IRC (map7!~map7@teksup41.lnk.telstra.net)
03:58map7 has left IRC (map7!~map7@teksup41.lnk.telstra.net, Ping timeout: 248 seconds)
04:10adrianorg__ has left IRC (adrianorg__!~adrianorg@186.213.158.214, Ping timeout: 246 seconds)
04:10map7 has joined IRC (map7!~map7@165.228.0.35)
04:14brian418 is now known as brian418_away
04:18Phantomas has left IRC (Phantomas!~Phantomas@unaffiliated/phantomas, Ping timeout: 246 seconds)
04:24map7 has left IRC (map7!~map7@165.228.0.35, Ping timeout: 246 seconds)
04:31Phantomas has joined IRC (Phantomas!~Phantomas@unaffiliated/phantomas)
04:36map7 has joined IRC (map7!~map7@teksup41.lnk.telstra.net)
04:40slicknick5181 has joined IRC (slicknick5181!~ubuntu@204.195.131.94)
04:40
<slicknick5181>
having issues getting Local hard drives to mount on clients
04:41
I have edited the lts.conf file to allow internal drives
04:43vagrantc has joined IRC (vagrantc!~vagrant@c-76-115-60-19.hsd1.or.comcast.net)
04:43
<slicknick5181>
anybody on here
04:43vagrantc has left IRC (vagrantc!~vagrant@c-76-115-60-19.hsd1.or.comcast.net, Changing host)
04:43vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
04:44* vagrantc just showed up
04:44
<vagrantc>
!ask
04:44
<ltsp_>
vagrantc: ask: Don't ask to ask a question, simply ask it, and if someone knows the answer, they'll respond. Please hang around for at least 15 minutes after asking a question, as not everybody constantly monitors the channel.
04:44* vagrantc would suggest waiting much more than 15 minutes
04:44
<slicknick5181>
having issues getting Local hard drives to mount on clients I have edited the lts.conf file to allow internal drives
04:45
<vagrantc>
!release
04:45
<ltsp_>
vagrantc: release: please mention the linux distro and release you're using :)
04:46
<slicknick5181>
Hello Vagrantc
04:46* vagrantc waves
04:47
<vagrantc>
slicknick5181: could you paste your lts.conf to, say, a pastebin?
04:48
!pastebin
04:48
<ltsp_>
vagrantc: pastebin: the LTSP pastebin is at http://ltsp.pastebin.com. Please paste all text longer than a line or two to the pastebin, as it helps to reduce traffic in the channel. Don't forget to paste the URL of the text here.
04:48
<vagrantc>
slicknick5181: would also be useful to know what distro and ltsp versions you're running... maybe paste the output of the "ltsp-info" command, too.
04:52slicknick5181 has left IRC (slicknick5181!~ubuntu@204.195.131.94, Read error: Connection reset by peer)
04:54
<vagrantc>
oh well.
04:54slicknick5181 has joined IRC (slicknick5181!~ubuntu@204.195.131.94)
04:54
<slicknick5181>
!pastebin
04:54
<ltsp_>
slicknick5181: pastebin: the LTSP pastebin is at http://ltsp.pastebin.com. Please paste all text longer than a line or two to the pastebin, as it helps to reduce traffic in the channel. Don't forget to paste the URL of the text here.
04:56
<slicknick5181>
actually it's only one line
04:56
LOCALDEV_DENY_INTERNAL_DISKS=false
04:56
<muppis>
Should goto [default] above that to get it working.
04:56
*got
04:57
<slicknick5181>
Hmm I've read all around and no1 else would even answer my question
04:57
Thanks
05:01Phantomas has left IRC (Phantomas!~Phantomas@unaffiliated/phantomas)
05:02
<slicknick5181>
rebooting thin client now
05:04
muppis: You are my HERO!!
05:04
mupis: thank you so much
05:05
<muppis>
No problem.
05:09alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
05:13
<alkisg>
Good morning
05:13
<muppis>
Morning
05:13* muppis yawns.
05:15
<vagrantc>
alkisg: heya
05:16
alkisg: so i can't make up my mind about what the default menu entry should be ... an unversioned kernel? a versioned kernel? just boot the first entry?
05:16
<muppis>
vagrantc, flip a coin.
05:17
<alkisg>
vagrantc: I'd put pxelinux.cfg/ltsp on top, in default, and let it boot the first entry, and just have a commented ontimeout example
05:17
The user can customize the kernels list, so he can bring the one he needs on top even without ontimeout
05:18
<vagrantc>
alkisg: so, the versioned entries need to have the version in the entry ... so i was thinking having ltsp-nfs, ltsp-nbd entries that were the most compatible (i.e. 32-bit only) versioned kernel
05:18
alkisg: i.e. ltsp-nfs-3.2.0 vs. ltsp-nfs-3.3.0 vs. ltsp-nfs
05:19
<alkisg>
vagrantc: I had code in ltsp-pnp which allowed defining a default with only the label prefix, e.g. "DEFAULT=ltsp-nfs" in update-kernels would match the first ltsp-nfs-version label
05:20
But since the user can order the kernels, I don't think it's very useful anymore
05:20
<vagrantc>
alkisg: and implemented ifcpu64 detection, too.
05:21
<alkisg>
...and before feature freeze ;)
05:22
<vagrantc>
alkisg: so you think each feature should be a separate include file? i.e. default ltsp, ifcpu64, ltsp-allkernels ?
05:23
that would allow people to order them however they want...
05:24
alkisg: and how to upgrade from older default files?
05:24
right now i've just implemented a single "ltsp" include file.
05:25
<alkisg>
vagrantc: you'd just overwrite pxelinux.cfg/default, as always... what's to upgrade?
05:26
We didn't support chroot upgrades so far anyway...
05:26
<vagrantc>
alkisg: wait, i thought pxelinux.cfg/default didn't get overwritten, just generated once?
05:27* vagrantc has always supported upgrades
05:27
<vagrantc>
maybe not perfectly, but i've done it numerous times.
05:27
<alkisg>
In the chroot, yes, but it then gets copied in the tftp dir
05:27
The copying part always overrides the tftp files
05:27
...but if you're talking about chroot upgrades, it's a different story, yeah...
05:29
How about sed for something in pxelinux.cfg/default, and if it's the older version, move it to /tmp/deleted-by-ltsp.XXXX/default, and create the new one?
05:30
vagrantc: that one ltsp file you're generating, is it using a submenu?
05:30
<vagrantc>
so, if someone editts /var/lib/tftpboot/ltsp/i386/default ... it will get overwritten when ltsp-update-kernels is run?
05:30
<alkisg>
Yes
05:30
<vagrantc>
i mean, that's how it currently behaves, but i thought we were trying to change that?
05:32* alkisg likes editing the information in its source, (chroot), not its copies (tftp)....
05:33* vagrantc misses the tftp even being separate from the chroot
05:34
<vagrantc>
with lessdisks, i just pointed the tftp server at the chroot ... no need to sync them ... but that required manual configuration of the tftp server.
05:35
<alkisg>
It also requires chmod'ding the kernel on ubuntu, which is readable only by root otherwise
05:35
<vagrantc>
silly ubuntu :)
05:36
<alkisg>
(about editing again) e.g. if TFTP/ltsp/i386/pxelinux.cfg/default has a comment on top of it that it was copied from that chroot and that any changes will be overwritten by ltsp-update-kernels, the sysadmin would know where to edit the file...
05:36slicknick5181 has left IRC (slicknick5181!~ubuntu@204.195.131.94)
05:37
<alkisg>
Or even a pxelinux.cfg/README file would be enough.
05:37
<vagrantc>
ltsp-update-kernels could mark the tftp files read-only ...
05:37
and put notes in the top of each
05:38
<alkisg>
For ltsp-pnp, also, if I update the system kernel and remove the old one and don't run ltsp-update-kernels, then I can't use /boot as my tftp dir
05:38
The clients won't boot (unless we run ltsp-update-kernels from kernel postinst)
05:38
Or is ltsp/update-kernels enough?
05:39
<vagrantc>
update-kernels should be enough if the tftp server is pointing to the right dir
05:39
<alkisg>
Finally, I can't have multiple nbd images without copying their contents to the tftp dir
05:39
(loopback chroots)
05:40
<vagrantc>
sure.
05:40
<alkisg>
With btrfs ahead, I think that will be common enough to support it
05:41* vagrantc just misses simpler times
05:42
<alkisg>
Yeah I get that feeling many times too, even if I'm only using linux for 4 years... but then I remember why fats and localapps etc were invented :-/
05:43bauerski has joined IRC (bauerski!~witekb@frodo.psp.opole.pl)
05:44
<vagrantc>
ok, so my question for the default ... we could default as it does now, essentially an unversioned ltsp, which relies on the symlinks, maybe one for each boot method (and it defaults to the first) ...
05:44* alkisg doesn't like symlinks
05:45* vagrantc neither, mostly
05:45
<alkisg>
Tell me a use case where kernel reordering from update-kernels.conf isn't enough
05:45
<vagrantc>
using LIST_KERNELS_* ?
05:46
<alkisg>
Yup, and ontimeout if he needs an older kernel
05:46
(and BOOT_METHODS ordering)
05:46
<vagrantc>
ontimeout depends on knowing the entries ... i was thinking there should be an "ltsp" entry for the default.
05:47
<alkisg>
If you want a specific older kernel, you'd know its label anyway
05:47
<vagrantc>
or maybe "ltsp-nfs" or "ltsp-nbd"
05:47
<alkisg>
That'd be done with BOOT_METHODS
05:48
If you want nfs first, list it first there
05:48
<vagrantc>
sure.
05:48
<alkisg>
Maybe providing some other, unused by default, pxelinux.cfg/ltsp* files can also be useful, instead of symlinks
05:48
<vagrantc>
hmmmm...
05:48
<alkisg>
The user can include them in his pxelinux.cfg/default manually if he wants to
05:49
ltsp == the default, ltsp-all, ltsp-nfs, ltsp-nbd...
05:49
<vagrantc>
so generate ifcpu64 always, but don't bother including it by default?
05:49
ltsp-ifcpu64 actually would make a reasonable default, too ...
05:50
but it's more tftp downloads each boot
05:50
alkisg: so, what's "ltsp" contain? the first entry from ltsp-all ?
05:50
<alkisg>
Either that, or with an additional ifcpu64 call
05:51
<vagrantc>
or it could be the first entry of LIST_KERNELS="$LIST_KERNELS_32 *"
05:52
<alkisg>
So then with a default ltsp setup but with 686 and 486 kernels, ifcpu64 wouldn't be used to select the correct one, and the user would have to enable it?
05:52
Doesn't sound bad, if ifcpu64 adds an overhead..
05:53
<vagrantc>
it's not a huge overhead, but some.
05:53
<alkisg>
We could also merge files in ltsp-update-kernels. Offer all those ltsp-* variants in the chroot, and ltsp-update-kernels can merge only some of them in the TFTP/pxelinux.cfg/ltsp file
05:54
So basically a chroot would generate entries for all the BOOT_METHODS it supports, while limiting them or ordering them would be an ltsp-update-kernels issue
05:55
<vagrantc>
gets more complicated fast.
05:55
<alkisg>
So in theory I'd have BOOT_METHODS="nfs nbd" in my ltsp-update-kernels.conf, but if I were using an old 10.04 chroot which didn't support NFS, I'd only get NBD
05:56
<vagrantc>
i like keeping ltsp-update-kernels pretty simple/stupid.
05:56
<alkisg>
I do think that NFS vs NBD is a server-side choice though...
05:56
<vagrantc>
true enough.
05:57
<alkisg>
So, the chroot creates ltsp.nbd, ltsp.nfs, in descending kernels version order
05:57
<vagrantc>
the way i implemented it so far was just tweaking the behavior already there to still get most of the functionality we were talking about
05:58
<alkisg>
The server decides that it only supports nbd, so ltsp-update-kernels only uses the first one
05:58
So if in 2 years we also support ... aoe, we won't have aoe entries for older chroots, which is what we want
05:58
<vagrantc>
right
05:59
so create ltsp-foo for each boot method, that contain all the kernel versions?
05:59
<alkisg>
Yes, and merge the ones the server supports into a single ltsp file?
06:00
According to ltsp-update-kernels.conf/BOOT_METHODS ?
06:00
<vagrantc>
that would reduce the number of tftp downloads
06:01
<alkisg>
ltsp-update-kernels does need to be a little smart, at least to update the kernel/initrd path
06:02
So if we're moving away from a simple cp anyways, merging is not too far away
06:02
<vagrantc>
so ltsp-update-kernels ... copies all the files and if ltsp-* exists, do appropriate things. ..
06:03
<alkisg>
Right
06:03
<vagrantc>
if default is all that's there, leave it alone.
06:03
<alkisg>
default won't be changed in any case, will it?
06:03
<vagrantc>
right
06:04
other than maybe making it read-only
06:04
and tweaking comments?
06:04
if we don't want people to edit $tftpdir/ltsp/* we should make it read-only.
06:05
<alkisg>
read only => no, the user might want to test something. Comments...
06:05
<vagrantc>
ok.
06:05
<alkisg>
...won't we be using a master TFTP/pxelinux.cfg/default file?
06:05
or TFTP/ltsp/pxelinux.cfg/default ?
06:05
<vagrantc>
long-run, but i'm just trying to figure out how to get the basics working
06:05
<alkisg>
In that case, the user wouldn't ever have to edit TFTP/ltsp/i386/pxelinux.cfg/default
06:06
As it would basically just include ltsp
06:06
<vagrantc>
would the paths need to be re-written?
06:06
<alkisg>
Hrm. And if we're going there, we might as well have ltsp-update-kernels generate only one master TFTP/pxelinux.cfg/ltsp
06:07
<vagrantc>
right
06:08
so, ltsp-update-kernels doesn't mess with any files in the ltsp/* other than copying them from the tftp dir.
06:09
but i think it should generate $tftp/ltsp/pxelinux* based on those.
06:09
<alkisg>
What if update-kernels only generated a single default file, and ltsp-update-kernels was smart enough to merge it? Then it would work with existing chroots too, their single default file would be included, as ltsp-update-kernels wouldn't recognize the boot method to know if it needs to include it or not
06:09
<vagrantc>
then pxemenus can generate the $tftp/pxelinux* stuff.
06:10
<alkisg>
The user would only edit TFTP/pxelinux.cfg/default, and ltsp-update-kernels would only generate TFTP/pxeilnux.cfg/ltsp from whatever default files are under TFTP/ltsp
06:10
That's only 1 additional tftp download to get the ltsp file
06:11
<vagrantc>
and it can sanely distinguish between i386 and amd64 chroots.
06:12
at that point, the ifcpu code really belongs in ltsp-update-kernels, then.
06:12
ifcpu64 ... not to be confused with ifcpu :)
06:13
<alkisg>
Do we need ifcpu anywhere?
06:13
<vagrantc>
doubtful
06:14
<alkisg>
Also, ltsp default files except the master one could have an "automatically generated, do not edit, configure update-kernels.conf or ltsp-update-kernels.conf or edit the master default" comment
06:15
And they could have special inline comments to help ltsp-update-kernels decide which entries to include or not (boot methods)
06:15
...if it can't be autodetected from the kernel command line
06:18
Let's sum up. update-kernels list all kernels in descending order and generates entries for all boot methods it supports without caring for the order.
06:18
ltsp-update-kernels merges them in a single file, respecting the boot method order from ltsp-update-kernels.conf, while omitting the ones the server doesn't support
06:18
And the default can be set from ontimeout, or we could implement the label matching using the ltsp-pnp code
06:18
Is anything more needed?
06:20
<vagrantc>
that sounds pretty good.
06:20
<alkisg>
I think the boot method can be determined from the kernel command line pretty easily (grep for nbd or nfs), so older chroots would work fine, and inline comments aren't really needed
06:25
Does pxelinux support LABEL foo; goto label bar; ?
06:26
<vagrantc>
not that i know of...
06:26
<alkisg>
If so, we could have ltsp-update-kernels generate some "fake" labels for ltsp-nbd, ltsp-nfs, which would "goto version"
06:26
I think it does... boot xxx
06:26
Let me check
06:26
<knipwim>
http://www.syslinux.org/wiki/index.php/Comboot/menu.c32
06:26
they got a MENU GOTO
06:27
<vagrantc>
oh, there are all sorts of .c32 things
06:27
and you could write one that uses lua if you really wanted to get into it.
06:29
<alkisg>
Btw how can one `bzr push` on behalf of another person?
06:29
I want to push to sch-scripts, with Phantomas showing up as the committer...
06:30
<vagrantc>
bzr --author="Phantomas <phantomas@example.net>" ci
06:30
<alkisg>
ty :)
06:31
<vagrantc>
then you'll show up as the committer
06:31mealstrom has joined IRC (mealstrom!~mealstrom@46.63.71.254)
06:32
<vagrantc>
normally the committer/author are the same thing, but the author gets all the noticeable credit.
06:38* alkisg is pondering whether it's worth it to i18n sch-scripts right from the start, or wait e.g. 1 year until it matures... currently it's half greek, half english...
06:41mealstrom has left IRC (mealstrom!~mealstrom@46.63.71.254, Read error: Connection reset by peer)
06:42xspider has joined IRC (xspider!~sa@linux-bg.eu)
06:51wiki0 has joined IRC (wiki0!51ba0884@gateway/web/freenode/ip.81.186.8.132)
06:51
<vagrantc>
alkisg: well, more on that later. :)
06:51* vagrantc waves
06:51
<alkisg>
bb
06:51
:)
06:51vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
06:57cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Remote host closed the connection)
06:58xspider has left IRC (xspider!~sa@linux-bg.eu, Disconnected by services)
06:58wiki0 has left IRC (wiki0!51ba0884@gateway/web/freenode/ip.81.186.8.132, Quit: Page closed)
06:58xspider has joined IRC (xspider!~sa@46.253.14.205)
07:00
<xspider>
I have a strange problem with K12Linux in EL6. Indefinitely after dolphin/nautilus stops working. They can't be run. Other programs starts like Krusader/Firefox... etc
07:00
no errors..
07:00Mava_ is now known as Mava
07:07cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
07:18jaya has joined IRC (jaya!75d30785@gateway/web/freenode/ip.117.211.7.133)
07:19bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
07:19jaya has left IRC (jaya!75d30785@gateway/web/freenode/ip.117.211.7.133, Client Quit)
07:27loather has left IRC (loather!~khudson@wsip-98-175-250-115.sd.sd.cox.net, Quit: This computer has gone to sleep)
07:34loather has joined IRC (loather!~khudson@wsip-98-175-250-115.sd.sd.cox.net)
07:40loather has left IRC (loather!~khudson@wsip-98-175-250-115.sd.sd.cox.net, Quit: This computer has gone to sleep)
07:40iku_esp has joined IRC (iku_esp!c193130a@gateway/web/freenode/ip.193.147.19.10)
07:42
<iku_esp>
hola alguien habla español?
07:50bauerski has left IRC (bauerski!~witekb@frodo.psp.opole.pl, Quit: Leaving.)
08:03mealstrom has joined IRC (mealstrom!~mealstrom@46.63.71.254)
08:05
<mealstrom>
good morning
08:05
<iku_esp>
hii gm
08:11JesseC has left IRC (JesseC!~JesseCWor@wsip-98-175-20-126.br.br.cox.net, )
08:11
<xspider>
Good morning for you. I'm working from three hours :D
08:12bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 244 seconds)
08:20khildin has joined IRC (khildin!~khildin@ip-83-134-215-206.dsl.scarlet.be)
08:27
<iku_esp>
someone setup kiosk mode?
08:30bauerski has joined IRC (bauerski!~witekb@frodo.psp.opole.pl)
08:36Steve_The_Pirate has joined IRC (Steve_The_Pirate!~Gary@82-68-255-22.dsl.in-addr.zen.co.uk)
08:37map7_ has joined IRC (map7_!~map7@ppp118-209-23-122.lns20.mel4.internode.on.net)
09:08khildin has left IRC (khildin!~khildin@ip-83-134-215-206.dsl.scarlet.be, Remote host closed the connection)
09:09iku_esp has left IRC (iku_esp!c193130a@gateway/web/freenode/ip.193.147.19.10, Ping timeout: 245 seconds)
09:39
<alkisg>
Hyperbyte: did you receive my recent ltsp-discuss mails? I answered before you for ltsp-pnp, and then after you, and yet Peter answered only to you as like if he didn't receive my answers...
09:39
<Hyperbyte>
alkisg, mailing lists are soooooo 1997...
09:40
By the way, I definitely think we need to dump the sourceforge mailing list in favor of our own.
09:40* alkisg completely agrees and he prefers forums instead, but goes with the flow... :(
09:40
<alkisg>
Hyperbyte: why not an SMF forum? I already have one, it works great for support!
09:41
<Hyperbyte>
alkisg, I think mailing lists are more comfortable as well than forums.
09:41
Sorry.
09:41
As for mails received...
09:41
<alkisg>
Really? You go and dig up the sf URL for just pointing someone to a previously answered question?
09:41
And no hierarchy, nothing...
09:41
<Hyperbyte>
Today one about ltsp-pnp nbd, reply to me
09:42
Yesterday one about xfreerdp and Ubuntu 12.04
09:42
<alkisg>
Hmm it looks like my answers take a lot longer to get through than yours
09:42
<Hyperbyte>
And before that a bunch on the 9th of this month, about xfreerdp and 12.04
09:43
<alkisg>
Btw I'm hearing other people preferring mailing lists over forums, so let me ask: were you ever involved in a forum with good structure for e.g. at least a month? Or are you judging by what's happenning on ubuntu forums?
09:43
<Hyperbyte>
alkisg, I have already received your latest reply to my earlier mail though
09:44
Nothing before that though.
09:44
As for forums, I've administrated and moderated several, now only participate in one or two...
09:44
When I arrive at work here, I see mail from mailing lists in my inbox... and during the day I'm informed of new mail that arrives
09:45
If I have to log in to a website to check, it becomes a burden.
09:45
And during the day I have to remember to hit refresh every now and then, but I shouldn't do it too often because then it's costing me too much time...
09:45
<alkisg>
Peter: 11:27, Alkis: 11:36:, Jan: 11:52, Alkis: 11:59, Peter: 12:34
09:46
<Hyperbyte>
Peter: 10:27, Jan: 10:52, Alkis: 10:59, Peter: 11:34
09:46
Never got 11:36.
09:46
Or 10:36 :P
09:56
...
09:56
<alkisg>
Meh stupid mailing lists
09:56* Hyperbyte hugs alkisg
09:57* alkisg would like to burn them along with all their history :D
09:59
<Hyperbyte>
What surprises me, is that no-one has ever coded something that bridges mailing lists and forums
09:59
And combines the best of both worlds.
10:00
I mean, we have mailing lists that are viewable online in threads
10:00
We have forums where you can subcribe to receive e-mail notifications when a new post is made
10:00
...
10:00
Nobody has taken the next step yet...
10:00
Or they have, but nobody noticed. :P
10:03
<alkisg>
They have different features, you can't merge them more than that
10:03
A mailing list can easily be represented in a forum-like fashion, but a forum cannot be represented by a maliing list
10:04
Also many forums support sending an email (not just a notificiation) with any new message
10:04Phantomas has joined IRC (Phantomas!~Phantomas@unaffiliated/phantomas)
10:05
<Hyperbyte>
alkisg, I think you can easily represent a forum in a mail. You just can't provide all of the features.
10:05
<alkisg>
So it really doesn't have any disadvantage over the ML, and I don't know why people keep using them. :P
10:05
<Hyperbyte>
alkisg, it does - you have to surf to a website and login.
10:05
Big disadvantage.
10:06
<alkisg>
Hyperbyte: why? if you have checked the "send me the new forum messages in an email" option?
10:06
There are forums where you can reply to the messages with an email too
10:09
<knipwim>
google wave
10:11
<Hyperbyte>
alkisg, so, make a nice proposal for next meeting. :)
10:17epoptes-user5 has joined IRC (epoptes-user5!298d4f09@gateway/web/freenode/ip.41.141.79.9)
10:23
<elias_a>
knipwim: Is google wave stil in operation?
10:27Phantomas has left IRC (Phantomas!~Phantomas@unaffiliated/phantomas)
10:31dave has joined IRC (dave!0264bb7a@gateway/web/freenode/ip.2.100.187.122)
10:32dave is now known as Guest49753
10:32
<Hyperbyte>
alkisg, I also sent one mail this morning which didn't arrive, by the way
10:32
Just re-sent it... wonder if it will arrive now.
10:32
<Guest49753>
Hi all,
10:32* alkisg decides that burning the MLs isn't enough, we need to torture them first
10:34
<knipwim>
elias_a: hosted by apache now, http://incubator.apache.org/wave/
10:34
<Guest49753>
Hi Alkisg I ahve a couple of question, have you got time to answer them ?
10:35
<alkisg>
Guest49753: a few minutes, what about?
10:38
Guest49753: I'll have to leave in a few minutes, so if you want to ask me something, now it'd be a good time... :)
10:38
<Guest49753>
Is it necessary for all 2 NIC systems to go through the NAT install
10:38
<alkisg>
?
10:38
In what, in LTSP?
10:39
<Guest49753>
Yes
10:39
<Hyperbyte>
I guess it also depends on what you want to use the 2 NICs for.
10:39
<alkisg>
If you have a general LTSP-related question, why not ask in the channel instead of asking specifically me?
10:39
<Hyperbyte>
I have 2 gigabit nics, I bond them for redundancy and for extra bandwith.
10:39
No NAT involved though.
10:39
<Guest49753>
I am surprised that I cannot find any mention of the correct config for 2 Nic systems
10:40
<Hyperbyte>
Guest49753, what is 'correct' and what is not is very subjective.
10:40
In this case, anyways.
10:40
Start by explaining what you actually want your two nics to do.
10:41
<Guest49753>
Oh dear, so how do I decide what the config files should be ?
10:41
<Hyperbyte>
Guest49753, by deciding what you want the nics to do.
10:42
<Guest49753>
One Nic connected to another network via a switch, One Nic to a switch and the LTSP clients
10:42
<Hyperbyte>
Do you want the LTSP clients to be hidden from the rest of the network?
10:42
<Guest49753>
The first nic is to a router on the other network
10:43
<Hyperbyte>
Wait - scratch that - you need NAT anyways.
10:43
<Guest49753>
Yes the LTSP clients will be physically in a room on their own
10:43
<Hyperbyte>
If traffic from the clients goes -through- your server, you need NAT.
10:43
You could do without NAT only if your clients do not need to access the internet themselves.
10:44
For example, when they don't run any applications locally that require internet, and when they synchronize with a local NTP timeserver.
10:44
<alkisg>
(01:43:10 μμ) Hyperbyte: Wait - scratch that - you need NAT anyways. ==> not necessarily, he could just connect all his switches together and have a single subnet, so that ltsp clients directly access the internet
10:44
<Hyperbyte>
alkisg, he just said that that's not his situation.
10:45
<alkisg>
Where did he say it?
10:45
Different rooms doesn't mean different network
10:45
<Hyperbyte>
12:42 <Guest49753> One Nic connected to another network via a switch, One Nic to a switch and the LTSP clients
10:45
<alkisg>
Right, so he'd have to move a cable
10:45
So what?
10:46
<Hyperbyte>
alkisg, you've left out the part about DHCP
10:47
<alkisg>
Guest49753: what I (more or less) mean is that you could have a single NIC LTSP setup where everything would be on the same network and all clients would be able to directly access the internet, if you don't have any reason to hide your clients behind a different subnet
10:47
<Hyperbyte>
I think having the clients and server on a seperate network is a good idea.
10:47
<alkisg>
The DHCP part is easily solved...
10:47
<Guest49753>
Basically I have a 2 Nic server. One NIC for LTSP clients via switch. Another NIC will have to be connected to a switch on a second network where the router is
10:47
<Hyperbyte>
Guest49753, what else is on the second network?
10:47
More LTSP servers? 500 other computers?
10:48
<Guest49753>
About 10 other machines and the router
10:48
<alkisg>
Are you using a 2 NIC setup for security? Or just because that's what you read in some wiki page?
10:48
<Guest49753>
Because of what I read
10:49
<Hyperbyte>
Ah.
10:49
I'm gonna have to agree with alkisg here then.
10:49* alkisg vanishes to pick up kids from school...
10:50yanu has left IRC (yanu!~yanu@lugwv/member/yanu, Read error: Connection reset by peer)
10:50
<Guest49753>
IfThe kids need access to the Internet, so I will go with whatever you suggest
10:50
<Hyperbyte>
Connect your LTSP server with one NIC to the switch, and connect the switch to the main network.
10:50
But wait first.
10:50
The DHCP server on your network - what is it?
10:51
<Guest49753>
I have a summary of what I have and can paste it here if that helps
10:51Trixboxer has joined IRC (Trixboxer!~Trixboxer@115.124.115.71)
10:51
<Hyperbyte>
Never ever paste here please... always use pastebin.
10:51
But right now I'm just curious what your DHCP server is. Is it a router?
10:52
<Guest49753>
The DHCP is NOT router based but is on the servewr according to dhcp.conf
10:52
<Hyperbyte>
Don't you have a DHCP server already in your network?
10:52
Do you configure all IP's manually, or is there some device handing out IP addresses?
10:52Gremble has joined IRC (Gremble!~Ben@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com)
10:53
<Guest49753>
No the machines on the network where the router is all have static ip's
10:53
<Hyperbyte>
And if you attach a machine, and configure it to set the IP address automatically, it doesn't get an IP address from the network?
10:55highvoltage has left IRC (highvoltage!~highvolta@ubuntu/member/highvoltage, Read error: Connection reset by peer)
10:55
<Guest49753>
No since there is no DHCP on the network that has the router
10:55
<Hyperbyte>
If that's the case, then you should just be able to attach server and clients to the switch, and the switch to the main network...
10:55
Then you have a single nic setup, and the LTSP server will be serving DHCP for the network.
10:56
You could then even attach a client to the network in the other room, and log in to LTSP there.
10:56
<Guest49753>
The LTSP side of things works well Machines pick up their ip and you can log on to the ltsp server
10:57
My problem is no Internet and I am really struggling to understand what I need to do with the second NIC to get it
10:58
<Hyperbyte>
Did you read the last three lines I wrote in here?
10:59
If you attach the switch to the main network, and configure DHCP on the server to set nameserver and default gateway to the main network router, you are done.
11:00
If you set it up like I just suggested, you don't need to do -anything- with the second nic.
11:00
<Guest49753>
Yes I understand. Currently the IP addresses are different for the LTSP side and the other network, presumably I bring them into line with the addressing on the router based network.Sorry for typing slowly
11:00
<Hyperbyte>
Yes, you'd have to do that.
11:00highvoltage has joined IRC (highvoltage!~highvolta@ubuntu/member/highvoltage)
11:01yanu has joined IRC (yanu!~yanu@lugwv/member/yanu)
11:01
<Hyperbyte>
Assuming you use 192.168.0.1 .. etc, on the main network, you could use 192.168.0.100 for the LTSP server, and 101-150 for the clients as a range, for example.
11:02
<Guest49753>
OK that is what I shall do. Thank you for your help, I shall do this tomorrow
11:03
<Hyperbyte>
Then I shall wish you luck. :)
11:04
<Guest49753>
Thanks, I shall let you know what happens. :)
11:04
<Hyperbyte>
Do that. :)
11:04
Good luck!
11:07
<Guest49753>
Hyperbyte are you still there ?
11:08Guest49753 has left IRC (Guest49753!0264bb7a@gateway/web/freenode/ip.2.100.187.122, Quit: Page closed)
11:13Gremble has left IRC (Gremble!~Ben@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com, Quit: I Leave)
11:18xspider has left IRC (xspider!~sa@46.253.14.205, Quit: leaving)
11:24
<Hyperbyte>
... sure!
11:24
I'm here. :P
11:31adrianorg__ has joined IRC (adrianorg__!~adrianorg@186.213.158.214)
11:41bieb has joined IRC (bieb!~hbieber@173.226.16.130)
11:53risca has joined IRC (risca!~risca@h87-96-186-215.dynamic.se.alltele.net)
12:02sep has left IRC (sep!~sep@40.211.jostedal.no, Read error: Connection reset by peer)
12:03sep has joined IRC (sep!~sep@40.211.jostedal.no)
12:05Steve_The_Pirate has left IRC (Steve_The_Pirate!~Gary@82-68-255-22.dsl.in-addr.zen.co.uk, Ping timeout: 252 seconds)
12:11mealstrom has left IRC (mealstrom!~mealstrom@46.63.71.254, Read error: Connection reset by peer)
12:14artista_frustrad has joined IRC (artista_frustrad!~fernando@200.247.43.2)
12:17
<alkisg>
!nbd-client
12:17
<ltsp_>
alkisg: Error: "nbd-client" is not a valid command.
12:18
<alkisg>
!learn nbd-client as To try mounting the NBD image from the client initramfs: nbd-client 192.168.67.1 -N /opt/ltsp/i386 /dev/nbd0
12:18
<ltsp_>
alkisg: The operation succeeded.
13:00
<ogra_>
192.168.67.1 ?
13:03monteslu_ has joined IRC (monteslu_!~monteslu@ip68-109-174-213.ph.ph.cox.net)
13:07monteslu__ has left IRC (monteslu__!~monteslu@ip68-109-174-213.ph.ph.cox.net, Ping timeout: 245 seconds)
13:08cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Remote host closed the connection)
13:09brunolambert has joined IRC (brunolambert!blambert@nat/revolutionlinux/x-sqqutswujzclrcif)
13:10cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
13:13map7_ has left IRC (map7_!~map7@ppp118-209-23-122.lns20.mel4.internode.on.net, Ping timeout: 252 seconds)
13:23
<alkisg>
ogra_: yeah, we settled on that one for the internal network, as 192.168.0.x is commonly used so they'd have the same subnet on both NICs and it would cause chaos
13:23
67 = L + T + S + P :)
13:25JesseC has joined IRC (JesseC!JesseCW@wsip-98-175-20-126.br.br.cox.net)
13:36
<highvoltage>
hmm, we didn't discuss changing the default ltsp ip range for edubuntu, which I think we wanted to at some point
13:55
<alkisg>
highvoltage: since we settled on 192.168.67.1, why not use the same for edubuntu too?
13:56
<highvoltage>
alkisg: sounds good
14:12
<ogra_>
a class C network limits you to 254 clients though :P
14:12
well, 253 since the server needs one too
14:13
<alkisg>
True... but I don't worry too much about installations with more than 250 clients, I bet they'd have a sysadmin there :D
14:15
What happens if we decided to use e.g. 10.67/16, and a school uses 10.67.x/24? Problems, right?
14:18
<highvoltage>
in my experience when a school has a /16 they probably have someone already who knows something about networking
14:20dead_inside has joined IRC (dead_inside!~dead_insi@76.75.3.174)
14:20cliebow has joined IRC (cliebow!~cliebow@WatchGuard.ellsworth-hs.ellsworth.k12.me.us)
14:23cliebow has left IRC (cliebow!~cliebow@WatchGuard.ellsworth-hs.ellsworth.k12.me.us, Client Quit)
14:25cliebow has joined IRC (cliebow!~cliebow@watchguard.ellsworth-hs.ellsworth.k12.me.us)
14:27
<alkisg>
highvoltage: in that scenario, the school has /24
14:27
We (LTSP) are using the /16...
14:28
(for the internal NIC)
14:36staffencasa has joined IRC (staffencasa!~staffenca@128.193.8.220)
14:53khildin has joined IRC (khildin!~khildin@h192064.upc-h.chello.nl)
14:58loather has joined IRC (loather!~khudson@wsip-98-175-250-115.sd.sd.cox.net)
15:47risca has left IRC (risca!~risca@h87-96-186-215.dynamic.se.alltele.net, Quit: Lämnar)
15:51F-GT has left IRC (F-GT!~phantom@ppp121-44-97-140.lns20.syd6.internode.on.net, Ping timeout: 244 seconds)
16:46Phantomas has joined IRC (Phantomas!~Phantomas@unaffiliated/phantomas)
17:14khildin has left IRC (khildin!~khildin@h192064.upc-h.chello.nl, Quit: I'm gone, bye bye)
17:22komunista has joined IRC (komunista!~slavko@195.98.5.207)
17:23vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
17:23Parker955_Away has left IRC (Parker955_Away!~parker@74.112.203.151, Ping timeout: 245 seconds)
17:30Parker955_Away has joined IRC (Parker955_Away!~parker@74.112.203.151)
17:38Steve_The_Pirate has joined IRC (Steve_The_Pirate!~Gary@94.175.96.170)
18:02mealstrom has joined IRC (mealstrom!~mealstrom@alfaprime.mail4u.com.ua)
18:32Steve_The_Pirate has left IRC (Steve_The_Pirate!~Gary@94.175.96.170, Remote host closed the connection)
18:50mealstrom has left IRC (mealstrom!~mealstrom@alfaprime.mail4u.com.ua, Quit: Leaving.)
19:11JesseC has left IRC (JesseC!JesseCW@wsip-98-175-20-126.br.br.cox.net, Ping timeout: 248 seconds)
19:11JesseC has joined IRC (JesseC!~JesseCWor@wsip-98-175-20-126.br.br.cox.net)
19:12risca has joined IRC (risca!~risca@90.129.131.40)
19:20JesseC has left IRC (JesseC!~JesseCWor@wsip-98-175-20-126.br.br.cox.net, Ping timeout: 248 seconds)
19:21JesseC has joined IRC (JesseC!JesseCW@wsip-98-175-20-126.br.br.cox.net)
19:28awilliams has left IRC (awilliams!mistik1@unaffiliated/mistik1, Ping timeout: 240 seconds)
19:30awilliams has joined IRC (awilliams!mistik1@unaffiliated/mistik1)
19:39loather has left IRC (loather!~khudson@wsip-98-175-250-115.sd.sd.cox.net, Quit: This computer has gone to sleep)
19:53Trixboxer has left IRC (Trixboxer!~Trixboxer@115.124.115.71, Quit: "Achievement is not the end, its the beginning of new journey !!!")
19:59cliebow has left IRC (cliebow!~cliebow@watchguard.ellsworth-hs.ellsworth.k12.me.us, Remote host closed the connection)
20:05Da-Geek has joined IRC (Da-Geek!~Da-Geek@62.40.45.100)
20:07Phantomas has left IRC (Phantomas!~Phantomas@unaffiliated/phantomas, Ping timeout: 252 seconds)
20:20risca has left IRC (risca!~risca@90.129.131.40, Quit: Lämnar)
20:30bauerski has left IRC (bauerski!~witekb@frodo.psp.opole.pl, Quit: Leaving.)
20:33vmlintu has left IRC (vmlintu!~vmlintu@nblzone-240-143.nblnetworks.fi, Ping timeout: 240 seconds)
20:41bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
20:47brunolambert has left IRC (brunolambert!blambert@nat/revolutionlinux/x-sqqutswujzclrcif, Quit: brunolambert)
20:48bieb has left IRC (bieb!~hbieber@173.226.16.130)
20:53vmlintu has joined IRC (vmlintu!~vmlintu@nblzone-240-143.nblnetworks.fi)
21:30komunista has left IRC (komunista!~slavko@195.98.5.207, Quit: Leaving.)
21:31artista_frustrad has left IRC (artista_frustrad!~fernando@200.247.43.2, Ping timeout: 252 seconds)
21:53alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
22:49Phantomas has joined IRC (Phantomas!~Phantomas@unaffiliated/phantomas)
23:06bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 252 seconds)
23:23dead_inside has left IRC (dead_inside!~dead_insi@76.75.3.174, Quit: Leaving...)
23:28Phantomas has left IRC (Phantomas!~Phantomas@unaffiliated/phantomas)
23:41atamakosi has joined IRC (atamakosi!74c7d396@gateway/web/freenode/ip.116.199.211.150)
23:41
<atamakosi>
hi all, irc virgin here
23:42
i need some help with ltsp
23:42
please
23:44
anyone?
23:46
<vagrantc>
!ask
23:46
<ltsp_>
vagrantc: ask: Don't ask to ask a question, simply ask it, and if someone knows the answer, they'll respond. Please hang around for at least 15 minutes after asking a question, as not everybody constantly monitors the channel.
23:47
<atamakosi>
thanks, I've never used an irc chat before and wasn't sure what the etiquette is
23:47
<vagrantc>
that's fine :)
23:47
<atamakosi>
sorry about that
23:47
so the problem is this
23:47* vagrantc should update the bot to be nicer :)
23:48
<atamakosi>
i've installed ltsp on a virtual ubuntu 12.04 server that was previously setup using ubuntu 11.10 to boot via network into ltsp and open rdesktop
23:48
which would allow my students/users to remote in to our MS terminal server and access docs, profile folders,etc
23:49
now that i've upgraded the system freezes after ltsp splash screen
23:52
removing the lts.conf file allows the thin client to load the ubuntu client so i think it might be an issue with the lts.conf setup for freerdp or freerdp itself
23:56
any advice?