Main page
[00:11] Faithful1 (n=Faithful@ns.linuxterminal.com) left irc: Client Quit
[00:11] Faithful (n=Faithful@ns.linuxterminal.com) joined #ltsp.
[01:02] japerry (n=japerry@drupal.org/user/45640/view) left irc:
[01:09] alkisg (n=alkisg@ubuntu/member/alkisg) joined #ltsp.
[01:23] alkisg (n=alkisg@ubuntu/member/alkisg) left irc: "Leaving."
[03:00] bobby_C (n=bobby@85-124-22-227.teleworker.xdsl-line.inode.at) joined #ltsp.
[03:08] mikkel (n=mikkel@84-238-113-66.u.parknet.dk) joined #ltsp.
[03:21] bobby_C (n=bobby@85-124-22-227.teleworker.xdsl-line.inode.at) left irc: "Goin' down hard"
[03:49] rhodan_ (n=quassel@73-108.107-92.cust.bluewin.ch) joined #ltsp.
[04:02] rhodan (n=quassel@253-92.107-92.cust.bluewin.ch) left irc: Read error: 110 (Connection timed out)
[04:05] hersonls (n=hersonls@187.40.76.49) joined #ltsp.
[04:11] hersonls (n=hersonls@187.40.76.49) left irc: Remote closed the connection
[04:17] hersonls (n=hersonls@187.40.76.49) joined #ltsp.
[04:18] sene (n=sene@unaffiliated/sene) joined #ltsp.
[05:16] Faithful (n=Faithful@ns.linuxterminal.com) left irc: Read error: 113 (No route to host)
[05:19] Faithful (n=Faithful@ns.linuxterminal.com) joined #ltsp.
[05:47] alkisg (n=alkisg@ubuntu/member/alkisg) joined #ltsp.
[05:56] alkisg (n=alkisg@ubuntu/member/alkisg) left irc: "Leaving."
[06:15] pmatulis (n=peter@mail.papamike.ca) joined #ltsp.
[06:33] xet7 (n=xet7@e83-245-139-63.elisa-laajakaista.fi) joined #ltsp.
[07:04] johnny (i=spectrum@franklin.localmomentum.net) left #ltsp.
[07:05] johnny (i=spectrum@franklin.localmomentum.net) joined #ltsp.
[07:26] vvinet (n=vince@modemcable045.251-20-96.mc.videotron.ca) joined #ltsp.
[07:42] yanu (n=yanu@lugwv/member/yanu) left irc: "leaving"
[07:42] yanu (n=yanu@d54C5F090.access.telenet.be) joined #ltsp.
[07:44] yanu (n=yanu@lugwv/member/yanu) left irc: Client Quit
[07:44] yanu (n=yanu@d54C5F090.access.telenet.be) joined #ltsp.
[07:56] hersonls (n=hersonls@187.40.76.49) left irc: Remote closed the connection
[08:00] barzog (n=Miranda@vulture2-nat-44.telecom.by) joined #ltsp.
[08:01] [barzog] hello. I've have following problems on gentoo amd64:
[08:01] [barzog] albatros2 stages # rm -rf /opt/ltsp/amd64/ && ltsp-build-client --dist Gentoo
[08:01] [barzog] --stage-uri file://opt/ltsp/stages/stage3-amd64-20100121.tar.bz2
[08:01] [barzog] --quickstart-verbose
[08:01] [barzog] Default Quickstart profile: /etc/ltsp/quickstart/profile.qs
[08:01] [barzog] Installing into: /opt/ltsp/amd64
[08:01] [barzog] * Sanity checking config
[08:01] [barzog] * you must specify a stage_uri
[08:01] [barzog] * kernel_sources not set...assuming gentoo-sources
[08:01] [barzog] * logging_daemon not set...assuming syslog-ng
[08:01] [barzog] * Sanity checking partition config for amd64
[08:01] [barzog] * bootloader not set...assuming grub
[08:01] [barzog] error: LTSP client installation ended abnormally
[08:01] [barzog] and ideas?
[08:12] Egyptian[Home] (n=Egyptian@62.117.46.179) left irc: Remote closed the connection
[08:16] Egyptian[Home] (n=Egyptian@62.117.46.179) joined #ltsp.
[08:23] [ogra] barzog, why make you use --dist Gentoo there ?
[08:23] [ogra] drop that
[08:24] [elmo40] ;)
[08:24] [elmo40] drop that...
[08:24] [barzog] tried. nothing changes:(
[08:25] [ogra] well Gentoo is surely not a debian or ubuntu release :) (--dist specifies the release and i dont think anyone ever ported the option to gentoo)
[08:26] [ogra] file: is missing a third slash
[08:26] [ogra] should be file:///
[08:26] [ogra] (first two are the protocol, third is /
[08:26] [ogra] )
[08:28] [ogra] if that still doesnt work you need to wait for knipwim or johnny, they are gentoo guys
[08:30] [barzog] nothing changes with third slash. ok, anyway thanks for directions. will wait....
[08:32] [ogra] " you must specify a stage_uri" is surely a pointer i would take a look at :)
[08:34] [barzog] I've also specified it in /etc/ltsp/ltsp-build-client.conf: STAGE_URI=file:///opt/ltsp/stages/stage3-amd64-20100121.tar.bz2
[08:34] [barzog] nothing changes. with --stage_uri it complains unknown key "--stage_uri"
[08:38] [ogra] are you sure in ltsp-build-client.conf file:// is needed ?
[08:38] [ogra] or are you sure file:/// is needed at all ?
[08:38] [ogra] also have a look at ltsp-build-client --extra-help it should tell you more details about options
[08:38] [barzog] it shown in http://en.gentoo-wiki.com/wiki/LTSP#Client_Install
[08:40] Faithful1 (n=Faithful@ns.linuxterminal.com) joined #ltsp.
[08:50] Faithful (n=Faithful@ns.linuxterminal.com) left irc: Read error: 110 (Connection timed out)
[08:56] vvinet (n=vince@modemcable045.251-20-96.mc.videotron.ca) left irc: Read error: 104 (Connection reset by peer)
[08:58] Nick change: rhodan_ -> rhodan
[09:52] alkisg (n=alkisg@ubuntu/member/alkisg) joined #ltsp.
[10:16] vvinet (n=vince@74.57.151.125) joined #ltsp.
[10:42] pem725 (n=pem725@129.174.65.247) left irc: "Leaving"
[10:48] [johnny] barzog, things have changed i think.. knipwim just did something with stage_uri to make it act differently
[10:48] [johnny] barzog, do you really have amd64 thin clients? :)
[10:51] [elmo40] johnny: can you buy anything else? if it is new hardware it will more then likely be 64-bit.
[10:51] litlebuda (n=litle@169.191.108.93.rev.vodafone.pt) joined #ltsp.
[10:53] [johnny] sure.. just depends on if you have new hardware..
[10:55] vvinet (n=vince@74.57.151.125) left irc: Read error: 110 (Connection timed out)
[10:58] [elmo40] if a company is going to implement an LTSP (bank, library, PR firm...) would they make a request for random hardware ? I would want every terminal to be the same. One profile ;) Unless you can find a stack of identical machines on eBay those companies will purchase brand new.
[10:59] [johnny] i don't know anything about banks..
[10:59] [johnny] didn't see anything about using banks..
[10:59] [johnny] are you the same person?
[11:02] [elmo40] check my IP. I am not.
[11:02] [elmo40] plus, I use Debian ;)
[11:04] [johnny] then why are you responding..
[11:04] [johnny] i was asking him
[11:04] [johnny] he iddn't indicate using it for a bank..
[11:08] artista_frustrad (n=artista_@201-25-168-216.ctame704.dsl.brasiltelecom.net.br) joined #ltsp.
[11:15] johnny (i=spectrum@franklin.localmomentum.net) left #ltsp.
[11:16] johnny (i=spectrum@franklin.localmomentum.net) joined #ltsp.
[11:28] [elmo40] johnny: it was an example. bank, library, other corporate type places.
[12:01] pmatulis (n=peter@mail.papamike.ca) left irc: Read error: 110 (Connection timed out)
[12:21] pmatulis (n=peter@mail.papamike.ca) joined #ltsp.
[12:52] Kicer86 (n=kicer@host-5db0eeee.sileman.net.pl) joined #ltsp.
[13:01] ogra (n=ogra@ubuntu/member/ogra) left irc: Read error: 104 (Connection reset by peer)
[13:01] ogra (n=ogra@ubuntu/member/ogra) joined #ltsp.
[13:05] bobby_C (n=bobby@85-124-22-227.teleworker.xdsl-line.inode.at) joined #ltsp.
[13:20] johnny (i=spectrum@franklin.localmomentum.net) left #ltsp.
[13:20] johnny (i=spectrum@franklin.localmomentum.net) joined #ltsp.
[13:23] [alincoln] anyone else playing with lucid? as of this morning ltsp-build-client dies due to unmet dependencies, and I can't tell if it's because of the repo state or because I did something to break it.
[13:25] [alkisg] alincoln: what's the exact error message?
[13:26] mikkel (n=mikkel@84-238-113-66.u.parknet.dk) left irc: "Leaving"
[13:26] [alincoln] alkisg: er, shut down the VM already. it was apt complaining about unmet dependencies for dbus, ltsp-client, and something else. sorry i didn't keep the message.
[13:27] [alkisg] I don't think there's been any updates in lucid ltsp this week...
[13:27] [alkisg] How did you call ltsp-build-client?
[13:28] [alincoln] plain old 'ltsp-build-client --arch i386'
[13:29] [alincoln] at one point i had stgraber's ppa in there, and i wanted to try moving back to the lucid package. so i had purged ltsp-server, ltspfs, and ldm-server on the server and installed the lucid packages. but i would still expect ltsp-build-client to do the right thing...?
[13:31] [alkisg] One way to do that would be (1) remove stgraber's ppa (2) remove ltsp (3) apt-get update (4) install ltsp... If you did that, sure, it should work fine...
[13:32] [alincoln] yep, that's what i tried
[13:35] [alkisg] alincoln: I did a lot of ltsp-build-client tests this week, none of them broke.
[13:35] [alkisg] So it must be something wrong about stgraber's ppa (didn't use it) or your setup
[13:35] [alincoln] alkisg: ok. i probably broke something :) i'll just get a new one going, no worries.
[13:35] [alkisg] If you try again, do keep the whole logs/messages etc
[13:35] [alincoln] will do
[13:36] [alkisg] And, a new version is coming out soonish, with lots of new stufff
[13:36] [alincoln] cool.
[13:39] sebas891 (n=sebas@201.255.36.155) joined #ltsp.
[14:07] vagrantc (n=vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net) joined #ltsp.
[14:20] [stgraber] alincoln: my PPA is a snapshot of what will be uploaded in Lucid, I don't currently have any dependency change in there so if you are using up to date lucid, the same should happen with current's lucid ltsp
[14:20] [alincoln] stgraber: ok, thanks. i didn't suspect the ppa. i imagine i did something stupid :D
[14:21] [stgraber] that or someone broke a dependency in lucid itself, it's a dev release so that happens quite often
[14:21] [stgraber] in most case, just wait 2-3 hours and try again ;) Also, always use archive.ubuntu.com and not some local mirror
[14:22] [stgraber] it may take up to a day for mirrors to update, that's not a problem for a stable release but it's for dev release
[14:22] [alkisg] stgraber: is it time for 5.2? \o/
[14:22] litlebuda (n=litle@169.191.108.93.rev.vodafone.pt) left irc: Read error: 110 (Connection timed out)
[14:22] litlebuda (n=litle@169.191.108.93.rev.vodafone.pt) joined #ltsp.
[14:23] [stgraber] alkisg: I'll be doing some tests on current trunk probably today or tomorrow and if I don't find anything broken, I'll tag that as 5.1.99
[14:23] [stgraber] nbd-proxy is stable and a lot faster than last week though it's still adding a 30% or so overhead which I'll get fixed last week for 5.2
[14:23] [alkisg] Yey :)
[14:23] [stgraber] s/last/next/ of course
[14:24] [alkisg] Some teachers here want to test the fat clients plugin asap, so I'll tell them to test 5.1.99 - that way we'll have more input for a stable 5.2 ;)
[14:27] [stgraber] sounds good
[14:28] [stgraber] vagrantc: In some of the diffs Launchpad sent me I noticed we are playing with IFS to get the right result from while/for loops but didn't restore the IFS after the loop, was that done on purpose ?
[14:29] [stgraber] vagrantc: usually "unset IFS" is causing some weird issues and that's why we save it as OLDIFS and the restore it after the loop
[14:29] pmatulis (n=peter@mail.papamike.ca) left irc: Read error: 60 (Operation timed out)
[14:29] [vagrantc] stgraber: i may have missed it in the initial commits, but everything should end with unset IFS ; test -n "$OLDIFS" && IFS="$OLDIFS"
[14:30] [vagrantc] i found a few cases that were inconsistant that i fixed in code i didn't even use
[14:30] [vagrantc] stgraber: so you're saying "unset IFS" shouldn't be used at all?
[14:31] [stgraber] well, if you do unset + restore the OLDIFS, that's fine, I thought I saw a case where we only unset it but never restore the old one
[14:32] [vagrantc] stgraber: i'm fairly certain i fixed those by the end of my flurry of commits
[14:32] [vagrantc] stgraber: and a few extra ones for good measure
[14:33] [stgraber] vagrantc: ok, I just found one in another file that you didn't touch, so I guess that was just me not parsing LP's diff correctly in my head ;)
[14:33] [stgraber] thanks for all the cleaning up
[14:34] [vagrantc] stgraber: there should be noticeable speed improvements on login when localapps is enabled now
[14:34] [vagrantc] still kind of slow, at least with debian+nfs ... but i think even NBD setups will notice
[14:34] [stgraber] did you do some tests with weird group names ? In the past we had some issues with "Domain Admins" as group that'd make that script fail and end up with no groups at all
[14:35] [vagrantc] stgraber: i didn't test it ... i don't really have a means to do so
[14:35] [vagrantc] stgraber: but i'm fairly certain it should work even with spaces and whatnot.
[14:35] [vagrantc] in shell, case is king.
[14:37] [stgraber] vagrantc: I'll try to do some tests here later today, I really hope the new code handles it correctly as we had to do a lot of hack in the past (and probably adding a lot of overhead with these)
[14:37] [vagrantc] stgraber: it's all quoted pattern matching, so it should be fine.
[14:37] [stgraber] cool, btw, how are we doing with translations ?
[14:38] [vagrantc] i think there are only 4 slightly out of date, and 1 way out of date
[14:38] [vagrantc] stgraber: today's the "deadline" i gave, of course we'd keep accepting updates :)
[14:54] Kicer86 (n=kicer@host-5db0eeee.sileman.net.pl) left irc: Client Quit
[15:09] cyberorg (n=cyberorg@opensuse/member/Cyberorg) left irc: Read error: 110 (Connection timed out)
[15:13] [highvoltage] hi stgraber
[15:15] [alkisg] Here's a way to *correctly* restore IFS: http://ltsp.pastebin.com/m10b9a7bc
[15:15] [alkisg] (i.e. unset it if it was initially unset)
[15:17] [stgraber] hey highvoltage
[15:23] ltspbot (n=supybot@S010600902754713b.wp.shawcable.net) left irc: Read error: 60 (Operation timed out)
[15:31] [vagrantc] alkisg: is there really a difference between IFS="" and IFS being unset?
[15:31] [alkisg] vagrantc: I've no idea.
[15:31] [alkisg] But then why bother unsetting it?
[15:32] [vagrantc] i guess: test -n "$OLDIFS" && IFS="$OLDIFS" || IFS=""
[15:32] [vagrantc] should also work...
[15:32] [alkisg] I _imagine_ that some shell could consider "null" = "there's no delimiter" and "unset"="use the default delimiter" - but that's just my imagination...
[15:32] [vagrantc] i guess if a variable was previously exported, it would be better not to unset it.
[15:33] [alkisg] In that case, we should get rid of those "unset IFS" instructions...
[15:34] [vagrantc] yeah, the unset IFS maybe would be better to change to IFS=""
[15:34] [alkisg] Or just IFS="$OLDIFS"
[15:34] [vagrantc] though really, i wonder if a couple functions would resolve this better.
[15:34] [vagrantc] since it's a lot of duplicate code.
[15:35] [vagrantc] it's all very short code...
[15:35] [vagrantc] but still, prone to many implementations
[15:35] [stgraber] wouldn't IFS="" mean no delimiter at all where "unset IFS" would be the shell's default delimiter
[15:35] [alkisg] OLDIFS="$IFS" and IFS="$OLDIFS" should be enough, unless there's distinction between empty and unset.
[15:35] [stgraber] that might be quite a difference
[15:35] [alkisg] stgraber: in that case, the current code is broken
[15:36] [alkisg] (and much other code in /usr/bin/*)
[15:36] sbalneav (n=sbalneav@S010600902754713b.wp.shawcable.net) left irc: Read error: 110 (Connection timed out)
[15:36] [vagrantc] stgraber: i think the shell treats "" the same as no value set.
[15:36] [alkisg] That's why I pasted the example code to correctly restore IFS in pastebin...
[15:36] [vagrantc] alkisg: looks like the initial setting of OLDIFS in your example is broken
[15:37] [stgraber] alkisg: yeah, I think that what's in your pastebin is the best way to make sure we have exactly the same after using a modified IFS than we had before
[15:37] [alkisg] vagrantc: why? no quotes?
[15:38] [vagrantc] i guess i just wasn't familiar with the OLDIFS=${IFS-IFS_was_unset} syntax
[15:38] *** alkisg used `man sh` and tried to find _any_ way to differentiate between unset/empty, and that was the only thing he came up with.
[15:38] [stgraber] vagrantc: that's just the magic making a variable contain the value of another but only if it's set, if not it then contains what's after the -
[15:39] [stgraber] vagrantc: we use that quite a lot in ltsp-build-client plugins IIRC
[15:39] [vagrantc] stgraber: what we use in the plugins has a differnet syntax
[15:39] [alkisg] stgraber: we usually use ${var:-subst}, not ${var-subst}
[15:39] [vagrantc] subtle, but different
[15:39] [alkisg] A colon makes the difference
[15:39] [vagrantc] yeah
[15:40] [stgraber] ah, right
[15:40] [vagrantc] alkisg: i don't seem to get anything when IFS is set.
[15:41] [vagrantc] alkisg: OLDIFS just ends up empty, even though IFS contains something.
[15:41] [alkisg] vagrantc: I'm getting a visible enter
[15:41] [alkisg] '
[15:41] Last message repeated 1 time(s).
back next →
1 2
up
Generated by logs2html module for eggdrop v.2.3.4
Find latest version at http://sourceforge.net/projects/logs2html or http://shmupsik.osetia.org