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


Channel log from 30 March 2008   (all times are UTC)

00:00cpunches has joined #ltsp
00:11makghosh has quit IRC
00:25makghosh has joined #ltsp
00:37maximi89 has quit IRC
00:50the440volttux has quit IRC
01:06Egyptian[Home] has quit IRC
01:07makghosh has quit IRC
01:07Egyptian[Home] has joined #ltsp
01:08rjune has quit IRC
01:12spectra has quit IRC
01:33
<vagrantc>
warren: i probably shouldn't have said anything regarding the selinux thingy. i just don't know enough about it to really know what is proper.
01:39vagrantc has quit IRC
02:21soneyka has quit IRC
02:35deavid has joined #ltsp
03:19captain_magnus has quit IRC
03:20captain_magnus has joined #ltsp
04:10Q-FUNK has joined #ltsp
04:10tux_440volt has joined #ltsp
04:15soneyka has joined #ltsp
04:53subir has joined #ltsp
06:17basanta has joined #ltsp
06:44ogra has quit IRC
06:44ogra has joined #ltsp
06:45basanta has quit IRC
06:48Q-FUNK has quit IRC
06:48Q-FUNK has joined #ltsp
06:49Q-FUNK has quit IRC
07:07rjune has joined #ltsp
07:10spectra has joined #ltsp
07:27spectra has quit IRC
07:33laga has quit IRC
08:14rjune has quit IRC
08:17subir has quit IRC
08:18ogra has quit IRC
08:24rjune has joined #ltsp
08:27petre has joined #ltsp
08:27
<petre>
morning all
08:33tux_440volt has quit IRC
08:43tux_440volt has joined #ltsp
08:57petre has quit IRC
08:57petre has joined #ltsp
09:01vagrantc has joined #ltsp
09:07laprag has joined #ltsp
09:07
<jammcq>
laprag: hey!
09:09
<petre>
is ltsp-vmclient a fedora creation or an ltsp creation?
09:10
<warren>
petre, well, first created on fedora. vagrantc and I intend on making it more general to directly support non-kvm VM's.
09:10
vagrantc, /selinux is a VFS like /proc or /sys, if you are not using selinux then /selinux/enabled wont exist.
09:10
<petre>
it's really cool!--except I can't login via it
09:11
<jammcq>
warren: but, as the last line in a shell script, if the file doesn't exist, the script returns a failure
09:12
as a script returns the return value of the last command in it
09:12
<laprag>
jammcq: ho
09:13
<jammcq>
laprag: where you at these days?
09:13Patina has quit IRC
09:13
<laprag>
just on my way out the door bound for sunny Florida
09:13
<warren>
jammcq, ok I didn't know that, why didn't anyone complain earlier?
09:13Patina has joined #ltsp
09:13
<vagrantc>
warren: i figured as much, but i just don't know enough about how selinux is supposed to work to comment on gvy's comments.
09:14
<jammcq>
warren: shigoran did, on the mailing list
09:14
<warren>
it isn't the last line of the script
09:14
not sure how "done" is treated though
09:14
[ -e /selinux/enforce ] && /sbin/restorecon -R $TFTPDIR &> /dev/null || :
09:14
<jammcq>
dunno, but it should be easy to test
09:14
<warren>
is this better?
09:14
<jammcq>
oooh, combining ANDs and ORs
09:14
ick
09:15
<warren>
|| : is a very standard shell script thing
09:15
<jammcq>
yeah, I use it too
09:15
<wwx>
google earth with x terminal, anybody tried this?
09:15
<vagrantc>
at that point, it should probably just go multi-line.
09:15
<warren>
"if everything previously to this fails, return zero"
09:15
<jammcq>
but not on the same line as &&
09:15
<warren>
vagrantc, the line is still obviously correct
09:16
<vagrantc>
warren: technially yes. stylistically, i think it would be easier to read on multiple lines.
09:16
<warren>
vagrantc, and the reason I use -e instead of -f most everywhere is because I intentionally want to check for file or symlink.
09:16
<vagrantc>
warren: -f handles file the way one would expect.
09:16
<warren>
-f is true on symlink too?
09:17
<vagrantc>
warren: i.e. if the file that the symlink points to is there, it's true, if it's not there, it returns false.
09:17
<warren>
oh
09:17
<vagrantc>
-e also returns true for directories.
09:17
which is often a bad thing.
09:17
<warren>
the bash man page isn't clear
09:17
I used to use -a, which turns out also stands for "ambiguous" =)
09:18
<vagrantc>
heh
09:18
<petre>
brb
09:18makghosh has joined #ltsp
09:18
<vagrantc>
the tricky part is, if you want to test if a file exists to not overwrite, you basically need to do both -f and -d ...
09:18
if you want to be perfect...
09:19
<warren>
I wonder how many people will remember that we have a LTSP meeting in 43 minutes here.
09:19
<vagrantc>
we do?!
09:20dan_young has joined #ltsp
09:20
<warren>
vagrantc, well, fedora LTSP
09:20
vagrantc, training them in using the source repo, editing stuff, building RPMS and testing it
09:21
<vagrantc>
warren: ah, cool.
09:22
<warren>
petre, you here for the meeting too?
09:22
anyone else here?
09:23
dan_young, hey dan
09:24
jammcq, if I don't use || : how do I return true without exiting the loop?
09:24
jammcq, I guess exit 0 after done...
09:25
<jammcq>
yeah, you could always make sure 'exit 0' is the last line
09:25
i've done that, but somehow it seems dirty
09:30
<petre>
I'm back
09:30
warren, yes I am
09:30
here for the meeting
09:31
<warren>
petre, do you have a working install of ltsp5 on fedora?
09:32laprag has quit IRC
09:32
<warren>
petre, (did ltsp-build-client and the setup instructions work?)
09:32
<petre>
well, not quite: I can get the login via ltsp-vmclient
09:33
<warren>
petre, that's likely a network setup proble
09:33
<petre>
but when I try to login I get an error, something about 'this workstation not authorized' or some such
09:33
<warren>
oh
09:33
<petre>
let me try it again...
09:33
<warren>
petre, so you see ldm in ltsp-vmclient?
09:33ivazquez has joined #ltsp
09:33
<petre>
yes, looks great
09:33
<warren>
liar
09:33
it is ugly =)
09:34
<petre>
well, allowing customization of it would be great, but I'm just ticked it comes up atm
09:34
I'm running it on f8, couldn't get f9 beta installed
09:34
<warren>
petre, it is possible that your ltspbr0 wasn't running when you ran ltsp-build-client?
09:34
petre, try ltsp-update-sshkeys then run ltsp-vmclient from scratch again
09:35
<petre>
probably, since the steps in your install notes have bringing up ltspbr0 occurring after ltsp-build-client
09:36
<warren>
petre, do you have wiki editing access?
09:36
<petre>
I just followed the steps blindly, since it's my first time through them
09:36
no, can probably signup for it tho
09:36
<warren>
petre, oh, you can also "chkconfig network on" which will bring up ltspbr0 automatically
09:37
<dan_young>
warren: hey, still doing some daddy duty
09:37
<warren>
k
09:37
<cyberorg>
'this workstation not authorized' is due to missing ssh_known_hosts
09:37
<petre>
cliebow was coming too, wasn't he?
09:38
<warren>
well, we'll see whoever shows up
09:38
I'm going to take a quick shower, brb.
09:38
<petre>
warren, take your laptop w/you, just in case
09:39
cyberorg, does ltsp-update-sshkeys create ssh_known_hosts?
09:39
<cyberorg>
petre, yes
09:40rasmuson_ has joined #ltsp
09:41
<petre>
hm, ltsp-vmclient stops at boot: prompt now, although hitting Enter gets it going again
09:42K_O-Gnom has joined #ltsp
09:43LaVieEstBElla has joined #ltsp
09:49tdiehl has joined #ltsp
09:54ilmarga has joined #ltsp
09:55
<petre>
ltsp-vmclient seems a bit...unstable
09:56
can't alway Ctrl-Alt out of it
09:56
s/alway/always/
09:57
<warren>
petre, what version?
09:57
<petre>
warren, of what? ltsp-vmclient?
09:58
<warren>
petre, kvm
09:58rjune has quit IRC
10:00
<petre>
kvm-63-2.fc8
10:01
<warren>
petre, hm, I never see that mysef.
10:02
<petre>
the login took the ID & PW this time, but then locked up
10:02
well, I should perhaps mention that I'm ssh-ed into the fc8 box and calling ltsp-vmclient from there
10:03
IOW, not logged in at the console and calling it
10:03
<warren>
bingo
10:03
I doubt upstream tests that
10:03
<ilmarga>
Hi, I'm having some problem booting my client with LTSP5. With LTSP 4.2 everything was fine. The problem is the NFS is on a different machine different from the DHCP+TFTP. In 4.2 I was using this syntax " 192.168.10.193:/opt/ltspi386" in my DHCP root-path configuration, but It gave me the nfsmount error. While googling I discovered this syntax isn't supported by LTSP5.
10:03
I added to dnsmasq.conf the option 66 "192.168.10.193" (with ") but it is not working, the client still tries to connect to the DHCP. Is it possible to use another server as NFS server in LTSP5? (I'm usign Debian etch).
10:03
<warren>
it plays weird X grab games.
10:03timborn has joined #ltsp
10:03
<petre>
yeah, that's what it seems like
10:04
<warren>
OK, it is time. Who is here for the LTSP Fedora Development Training?
10:04
<petre>
was scrambling yesterday to get fc8 installed on my laptop here, but couldn't get it done (got partition issues)
10:04* ivazquez is here to listen in
10:04* dan_young is here
10:04
<warren>
It seems that the wiki is broken so I couldn't put training instructions there.
10:04
<petre>
I am
10:04
<timborn>
present
10:05
<petre>
yes, wiki won't let me create a profile
10:05
<warren>
OK has everyone here installed ltsp-server and run ltsp-build-client?
10:05
<petre>
yes
10:06
<warren>
dan_young, ?
10:06
<dan_young>
I'm 768/128k on a non-VT enabled box at home, so not quite there, but I can follow along reasonably well
10:06
<ivazquez>
Not I, but I'll play along at home.
10:06
<warren>
http://fedoraproject.org/wiki/K12Linux/InstallGuide the instructions here somewhat work
10:06
I wasn't able to update them.
10:06
everyone have bzr installed?
10:06
yum install bzr
10:07
https://code.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk
10:07
Here you can conveniently see the history of the ltsp-trunk tree.
10:08
You can see "Download URL: http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk"
10:08
use this command to grab the tree:
10:08
bzr branch http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk
10:09
oh, also install mkdst
10:09
yum install mkdst
10:09* makghosh is here
10:10
<warren>
There is a newer version of mkdst coming, mkdst-0.8
10:10
but the mkdst-0.7 in Fedora 8 and rawhide is OK.
10:10
after you have the ltsp-trunk tree, cd into it
10:11
in a separate terminal you need to have a CVS checkout of the /cvs/pkgs ltsp tree.
10:11
This is the CVS tree used to build the ltsp RPM in Fedora.
10:11* warren finds the checkout instructions for that..
10:12
<warren>
https://fedoraproject.org/wiki/UsingCvs
10:12
CVSROOT=:pserver:anonymous@cvs.fedoraproject.org:/cvs/pkgs
10:12
cvs co <module>
10:12
so you would use:
10:12
cvs co ltsp
10:13
The reason you need both the upstream bzr tree, and Fedora's /cvs/pkgs ltsp module, is you need the ltsp.spec from the CVS tree in order to do your own local RPM test builds.
10:13
<petre>
hold on, gotta get cvs installed...
10:13
<dan_young>
OK, I've got upstream bzr and the Fedora cvs
10:13
<warren>
petre, I'll finish explaining this then wait a bit.
10:13* LaVieEstBElla cliebow is behind..spyware crap on a paying job..
10:13LaVieEstBElla is now known as cliebow
10:14
<cliebow>
daughters..
10:14
<warren>
cliebow, I suppose the meeting log will be sufficient to follow up later.
10:14
<cliebow>
yes..so far i am comfortable
10:14
<petre>
okay, got the fedora stuff
10:14
<warren>
So you have the /cvs/pkgs ltsp checkout in one directory, /path/to/fedora-cvs/ltsp
10:15
and /path/to/ltsp-trunk elsewhere
10:15
cd /path/to/ltsp-trunk
10:15
ln -s /path/to/fedora-cvs/ltsp/devel/ltsp.spec
10:15
So you have a ltsp.spec link in your ltsp-trunk directory.
10:16
everyone here yet?
10:16
I can wait.
10:16* dan_young nods
10:16
<petre>
got 'em both
10:16
<warren>
OK, try:
10:16
mkdst tar
10:16
did it create tarballs?
10:16
<petre>
what should $PWD be?
10:16
<dan_young>
yes
10:17
<petre>
oh, never mind
10:17shishirjha has joined #ltsp
10:17
<warren>
OK, try mkdst rpm
10:17
it should fail for one or moe reasons
10:18
You might be missing BuildRequires, or the tarball doesn't match the version in the spec.
10:18
<petre>
rpmbuild not available
10:18
<warren>
(my ad)
10:18
petre, yum install rpmdevtools
10:18
<dan_young>
error: FIle /tmp/tmp.quuux..../ltsp-5.1.0.tar.bz2: No such file or directory
10:20
<warren>
dan_young, what Version line is in ltsp.spec/
10:20
<dan_young>
5.1.0
10:20
<warren>
ah
10:20shishirjha has left #ltsp
10:20
<warren>
hold a sec, building a new mkdst-0.8 for F-8
10:20
this will really help us here
10:21
Everyone edit ltsp.spec and change 5.1.0 to 5.1.1 to match the tarball
10:21
then try mkdst rpm again
10:22rjune has joined #ltsp
10:22
<warren>
anyone built an RPM, or new rpmbuild error messages?
10:23
<dan_young>
xargs: xargs.c:443: main: Assertion `bc_ctl.arg_max <= (131072-2048)' failed.
10:23
<petre>
I'm getting 'File not found: ltsp.spec' although I just edited it
10:24
<warren>
petre, did you create the symlink?
10:24
<petre>
no, missed that
10:25
<warren>
dan_young, that causes a build failure?
10:25
<dan_young>
yeah
10:25
<warren>
hmm, never seen that one before =)
10:26
http://koji.fedoraproject.org/packages/mkdst/0.8/
10:26
<petre>
I'm missing a bunch of dependencies
10:26
<warren>
Everyone go here and get mkdst-0.8 for your respective distribution.
10:27
petre, yeah, will likely have to yum install a bunch of stuff
10:27
<petre>
doing so now...
10:27* warren gets a drink...
10:27
<warren>
(non-alcoholic =)
10:28
<cliebow>
thought you were pulling a ragnar 8~)
10:28
<petre>
um, it looks like the 1.fc8/ link is going to time out
10:29
<warren>
petre, reload?
10:29
working here
10:29* dan_young got it OK
10:29
<warren>
dan_young, you using F8 or F9?
10:29
<dan_young>
f9
10:29
<petre>
that worked; and my mkdst rpm worked
10:29
<warren>
dan_young, ok, I haven't tested building the rpm on f9... =)
10:30
dan_young, or there might be a new bug on F9....
10:30
<ivazquez>
It's a known bug on F9.
10:30
<warren>
ivazquez, oh?
10:30
ivazquez, thank goodness you're here. =)
10:30
<dan_young>
ah, OK
10:30
<ivazquez>
Update findutils.
10:31
<dan_young>
crap, didn't get latest rawhide, just a sec
10:32
ivazquez, thanks, that works
10:32kushal has joined #ltsp
10:32
<petre>
okay, got new mkdst installed; re-run mkdst rpm?
10:32
even though the last run gave no errors?
10:33
<warren>
yes
10:33
the new mkdst is better
10:34
petre, dan_young: do either of you have any prior experience editing .spec files and building RPMS?
10:34
<dan_young>
yeah
10:34
<petre>
I've re-built a couple rpms, but that was a few years ago
10:35
<warren>
OK please spend a moment exploring the ltsp-trunk source tree
10:35
<makghosh>
mkdst rpm worked perfectly without any errors
10:36
<warren>
note that server/ contains stuff that goes into ltsp-server RPM, and client/ contains stuff for ltsp-client RPM
10:36
ltsp.spec defines exactly what goes where in the RPM
10:36
ltsp.spec is fairly good for training you on RPM spec because it is very explicit
10:36
you see exactly what it does
10:36
because it does everything manually pretty much
10:36kushal has left #ltsp
10:37
<petre>
warren, is this chat being recorded? I won't remember everything you say
10:37
<warren>
petre, yeah, and I will transform this into better docs
10:38
look in ltsp.spec, see all the mkdir and install lines?
10:38
then look at corresponding files in the ltsp-trunk/server and ltsp-trunk/client tree
10:39
Do that for a minute or so
10:39* warren runs away again
10:40spectra has joined #ltsp
10:41tux_440volt has quit IRC
10:41K_O-Gnom has quit IRC
10:42ilmarga has left #ltsp
10:42
<warren>
OK
10:43
before we go further, you must learn about bzr pull, so you can grab changes from upstream.
10:43
is your $PWD ltsp-trunk?
10:43
cd ..
10:43* dan_young nods
10:43* petre also nods
10:43
<warren>
bzr pull ltsp-trunk ltsp-yourname
10:44
ltsp-yourname should be an independent copy of the entire source tree
10:44
oh..
10:44
ops
10:44
<dan_young>
bzr: ERROR: extra argument to command pull: ltsp-dyoung
10:44
<warren>
you might need to use
10:44
<petre>
same as dy
10:44
<warren>
bzr branch ltsp-trunk ltsp-yourname
10:44
<dan_young>
makes more sense
10:45
<warren>
ltsp-yourname will be missing the ltsp.spec symlink, so create it again.
10:45
<makghosh>
same error
10:45
<warren>
makghosh, are you ../ from your ltsp-trunk?
10:45
bzr branch ltsp-trunk ltsp-yourname
10:45* petre gets same error as makghosh
10:45* makghosh checks again
10:45K_O-Gnom has joined #ltsp
10:46* dan_young branched OK
10:46
<petre>
so, we should be right above ltsp-trunk? or in ltsp-trunk?
10:46
<warren>
above
10:46
<petre>
ah
10:46
<warren>
cd ltsp-trunk/../
10:46
<petre>
that works
10:46
<warren>
OK, understand this because this is very important.
10:47
ltsp-trunk is your upstream tree. Never edit any files in there.
10:47
This way you can "cd ltsp-trunk; bzr pull" and it will pull the latest from upstream.
10:48
ltsp-yourname is your copy
10:48
after you have pulled new changes in ltsp-trunk, you can do:
10:48
cd ltsp-yourname; bzr pull ../ltsp-trunk
10:48
understand?
10:48
<petre>
makes sense
10:48* dan_young nods
10:48* makghosh nods
10:48
<warren>
if you symlinked ltsp.spec in ltsp-yourname, you can use mkdst rpm there too.
10:49
ah, here's a neat tool
10:49
yum install bzr-gtk
10:49* vagrantc forgets if append_revisions_only = true is set on all the new repositories
10:49
<warren>
then try "bzr viz" in ltsp-yourname
10:49
vagrantc, if it isn't go ahead
10:50
<vagrantc>
seems like with pack-0.92, it actually even works.
10:50
<warren>
vagrantc, none of these people will have commit access anytime soon, until they have proven that they truly understand how things work and everything else necessary for safety.
10:50
Everyone see bzr viz? pretty cool huh?
10:50
<makghosh>
yeah
10:51
<petre>
hold on, still getting it...
10:51praveer_cool has quit IRC
10:51
<warren>
OK, I can't train you on everything you need to know about bzr. Read the bzr man page to learn more.
10:51praveer_cool has joined #ltsp
10:52
<dan_young>
ooh, shiny
10:52
<warren>
In your own ltsp-yourname tree, if you edit files you can check in changes to your own tree with "bzr ci"
10:52
and read the manpage about "bzr push" so you can push your own tree to a sftp server somewhere, this way you can share your tree with others.
10:53
usig "bzr ci" will only check in changes to your local tree
10:53
You can use "mkdst rpm" to build an RPM of whatever is in the current tree, even if you haven't checked it in.
10:53
This is great if you want to quickly test changes that you made
10:54
simply install the ltsp-server (on the server) or ltsp-client (in the chroot)
10:54
This brings up a new annoyance though.
10:54
If your server is x86_64 and client chroot is i386
10:54
Then you used "mkdst rpm" to build only x86_64 or i386
10:54
Here's what I do:
10:54
yum install mock
10:55
sudo mock -r fedora-8-i386 $THENEWRPMFROMMKDST.src.rpm
10:55
wait a little while...
10:55
then it spits out i386 RPMS
10:56
<cliebow>
ahh..
10:56
<warren>
If I want to upgrade the ltsp-client, then I copy the ltsp-client*.i386.rpm to /opt/ltsp/i386/tmp/
10:56
then chroot into /opt/ltsp/i386 and use rpm -Uvh manually within the chroot.
10:56
mock is slow the first time, but after that it has cached stuff in /var/lib/mock/cache so it is faster the next time.
10:57
IMPORTANT WARNING!!!
10:57
If your host is x86_64, you MUST use this command to chroot into /opt/ltsp/i386
10:57
setarch i386 chroot /opt/ltsp/i386
10:57
if you don't, then some commands like yum will screw up, in the case of yum it will install the wrong arch of RPMS in the chroot effectively destroying it.
10:58
Oh, here's how you safely use yum in the chroot.
10:58
setarch i386 chroot /opt/ltsp/i386
10:58
mount /proc
10:58
yum install FOO
10:58
yum update
10:58
etc.
10:59
Make sure you umount /proc before you exit
10:59
or chroot again later and umount /proc
10:59
<dan_young>
ah, excellent; screwed that up the other day
10:59
<warren>
ANOTHER WARNING
10:59
If you use "umount /proc" be sure you are actually in the chroot
10:59
you can screw up your host if you accidentally unmount /proc
11:00
also be sure that you have unmounted /proc within the chroot before you delete /opt/ltsp/i386 if you want to start fresh.
11:01
<cliebow>
gul darn $%&()_*_ windows pos
11:01
<warren>
We're out of time now.
11:01
I'll take any questions.
11:01
<dan_young>
you can always "umount /var/tmp/imgcreate-Ox1OXX/install_root/proc" from outside the chroot too
11:01
<warren>
dan_young, yeah
11:01
<cliebow>
good start...
11:01
<warren>
dan_young, although that's a different /proc
11:02
<dan_young>
warren: er yeah
11:02
<warren>
dan_young, that is "oh crap, ltsp-build-client failed"
11:02
<dan_young>
warren: :-)
11:02
<warren>
dan_young, after the install I recommend chrooting before mounting and unmounting just to be sure you don't screw with your host.
11:02
dan_young, it also avoids putting garbage into /etc/mtab on the host.
11:02* cliebow cliebow looks forward to crashing thru ltsp-trunk
11:02
<dan_young>
warren: good advice, thx
11:03
<warren>
Oh, one more piece of advice
11:03
your cvs checkout of /cvs/pkgs ltsp module
11:03
You will want to pull updates to ltsp.spec
11:03
because I or somebody else added stuff there
11:03
<cliebow>
k
11:04
<warren>
you could use "cvs up" in that directory
11:04
except you edited ltsp.spec and it might fail
11:04
just delete ltsp.spec and cvs up
11:04
That is all.
11:04
<timborn>
thanks warren
11:04
<warren>
OK, I'll be here until at least 12:30 if you have questions.
11:04
I have one more question for you:
11:04
<dan_young>
warren: thanks
11:04
<makghosh>
warren, cool :)
11:05
<petre>
thank warren
11:05
<warren>
Any particular day/time is better for you folks for a weekly LTSP Fedora meeting?
11:05
<cliebow>
thanks warren
11:05
<makghosh>
warren, thanks a lot :)
11:05
<petre>
early sunday morning is best for me
11:05K_O-Gnom has quit IRC
11:05* makghosh agrees petre
11:05
<cliebow>
if ir is an hour at A time 8-4 edt weekdays at school..i can work around you
11:06
<dan_young>
Pacific working hours are much easier for me; sorry :-(
11:06
<cliebow>
sundays for a bit usually works too
11:06
dan m-f
11:06
?
11:06
<dan_young>
yeah
11:06
<warren>
Sunday at this same timeslot is good for everyone?
11:06
<petre>
sure
11:06
<makghosh>
warren, sure +1
11:06
<dan_young>
I can prob, make it work, earlier might be better, 10 Eastern is 7 am here?
11:07* petre speaks only for himself
11:07
<petre>
yes, /me agrees with dan_young
11:07
<warren>
10 EDT is 1400 UTC?
11:07
<cliebow>
you guys name it..I'll work around..
11:08
er 5 hours
11:08
<warren>
argh
11:08
I get mixed up
11:08
10AM EDT is fine for me
11:08
<ivazquez>
EDT is UTC-4, EST is UTC-5.
11:09
<warren>
Anybody interested in helping me get all these tips onto documentation?
11:09
<dan_young>
I've got a good snapshot of them; can do it.
11:09
where?
11:09
<warren>
dan_young, ok, then we only need a place to PUT the documentation =)
11:09
mm
11:10
they didn't create my trac project yet
11:10
<dan_young>
I was able to edit https://fedorahosted.org/k12ltsp/wiki
11:10
<warren>
dan_young, I'll let the list know when I have a place.
11:10
<cliebow>
k
11:10
<warren>
dan_young, I requested that k12ltsp will be deleted entirely
11:10
dan_young, go ahead and compile it offline for now, I'll try to get k12linux project created myself
11:10
<dan_young>
warren: OK
11:11
<warren>
OK if you have questions ask anytime in #ltsp or on the list.
11:11
https://www.redhat.com/mailman/listinfo/k12linux-devel-list
11:11
I also highly recommend subscribing to the upstream list
11:11
https://lists.sourceforge.net/lists/listinfo/ltsp-developer
11:11
since Fedora is 100% upstream, it is very important to participate there too
11:12Pascal_1 has joined #ltsp
11:12
<warren>
sometimes we have to argue
11:12
=)
11:12
meeting is done
11:12
<makghosh>
warren, yep...i am into those lists :)
11:12* warren works on creating k12linux project.
11:13
<petre>
warren, on http://fedoraproject.org/wiki/K12Linux/InstallGuide, it says ltsp-server-initialize is broken
11:14
is that just on fc9 or all versions?
11:14
<warren>
petre, all
11:15
petre, I just copied it from eharrison's LTSP-4.2 and didn't do any work on it
11:15
petre, some of the plugins are irrelevant, some are wrong, some are missing
11:15
petre, it doesn't handle the new ltspbr0 auto config
11:15
petre, difficult to ask the user which interface they want to permanently use for ltsp too
11:16
<petre>
is that the point of the ltsp bridge interface?
11:16
so they don't have to pick?
11:17
<warren>
petre, could you do me a favor, search google and find the syntax for an ifcfg file to auto add an ethernet device to a bridge.
11:17
<petre>
I'll have a look
11:17makghosh has quit IRC
11:18
<warren>
petre, the point of ltspbr0 is so we can ship an auto-configured ltsp-server, and the ONLY thing the sysadmin has to do is add an interface to the bridge and it will work.
11:20
<petre>
so...the sysadmin would modify /etc/sysconfig/network-scripts/ifcfg-ltspbr0, say?
11:20
<warren>
petre, no, that remains unmodified
11:20
<dan_young>
warren: BRIDGE=ltspbr0 in ifcfg-ethX
11:21
<warren>
petre, /etc/sysconfig/network-scripts/ifcfg-eth1 for example can have a syntax that has no IP, but adds itself to a bridge.
11:21
dan_young, ah
11:21
dan_young, we need that in documentation
11:21
<dan_young>
adding it to my notes
11:22
<warren>
It will be more difficult to configure that in a sane way in ltsp-server-initialize because no sysadmin will do it exactly the same way.
11:22
<dan_young>
warren: yeah I'm envisioning an interactive thing that blinks the link light w/ ethtool
11:23
<warren>
dan_young, that's clever, but does that work with all cards? probabl not.
11:24
<dan_young>
prob not
11:25makghosh has joined #ltsp
11:25praveer_cool has quit IRC
11:26* dan_young has to go; thanks for the cluestick, will have notes up somewhere tomorrow
11:26* makghosh hates being disconnected
11:26
<warren>
dan_young, thanks
11:26
dan_young, probably notes to the list is a good start
11:27
<dan_young>
warren: sounds good
11:27dan_young has quit IRC
11:28Pascal_1 has quit IRC
11:28len71 has joined #ltsp
11:30abadger1991 is now known as abadger1999
11:30cliebow has quit IRC
11:33praveer_cool has joined #ltsp
11:34Pascal_Debian has joined #ltsp
11:36len71 has quit IRC
11:42vagrantc has quit IRC
11:43samar has joined #ltsp
11:45
<warren>
oh nice, git tracks exact file permissions unlike bzr.
11:45* warren kicks bzr.
11:55Pascal_Debian has quit IRC
12:00Q-FUNK has joined #ltsp
12:00
<johnny>
hi
12:05Pascal_1 has joined #ltsp
12:08Pascal_Debian has joined #ltsp
12:09cpunches has quit IRC
12:23makghosh is now known as makghosh|afk
12:24Pascal_Debian has quit IRC
12:26Pascal_1 has quit IRC
12:36samar has quit IRC
12:37praveer_cool has quit IRC
12:41praveer_cool has joined #ltsp
12:55mikkel has joined #ltsp
13:18Q-FUNK has quit IRC
13:23makghosh|afk has quit IRC
13:28tdiehl has quit IRC
13:28deavid has quit IRC
13:28chupacabra has quit IRC
13:32deavid has joined #ltsp
13:42vmlintu has quit IRC
13:42rjune has quit IRC
13:42timborn has quit IRC
13:42petre has quit IRC
13:42gonzaloaf_test has quit IRC
13:42sep has quit IRC
13:42mistik1 has quit IRC
13:42|Paradox| has quit IRC
13:42jbrett has quit IRC
13:42gonzaloaf_work has quit IRC
13:42primeministerp has quit IRC
13:42sutula has quit IRC
13:42Shingoshi has quit IRC
13:42sbalneav has quit IRC
13:42ivazquez has quit IRC
13:42Egyptian[Home] has quit IRC
13:42abadger1999 has quit IRC
13:42r3zon8 has quit IRC
13:42loather-work has quit IRC
13:42oh207 has quit IRC
13:42gu_ has quit IRC
13:42bjorn has quit IRC
13:42Topslack has quit IRC
13:42moquist has quit IRC
13:42mikkel has quit IRC
13:42rasmuson_ has quit IRC
13:42soneyka has quit IRC
13:44ltspbot` has joined #ltsp
13:44captain_magnus has quit IRC
13:44jammcq has quit IRC
13:44RyanRyan52 has quit IRC
13:44F-GT has quit IRC
13:44klausade has quit IRC
13:44dberkholz has quit IRC
13:44ltspbot has quit IRC
13:46captain_magnus has joined #ltsp
13:47bobby_C has joined #ltsp
13:47RyanRyan52 has joined #ltsp
13:49tdiehl has joined #ltsp
13:49chupacabra has joined #ltsp
13:57tux_440volt has joined #ltsp
14:01jammcq has joined #ltsp
14:01klausade has joined #ltsp
14:01F-GT has joined #ltsp
14:09tux_440volt has quit IRC
14:10rasmuson_ has quit IRC
14:18
<johnny>
next version of virtualbox will finally let you use ctrl alt f keys
14:20dberkholz has joined #ltsp
14:22
<johnny>
dberkholz, ok.. openrc seems to work as advertised
14:24
<warren>
johnny, from a menu or something?
14:24
<johnny>
?
14:25
oh the vbox thing lo
14:25
it'll be something like hostkey + alt + f
14:25
i'm nto sure about the menu
14:29
ok.. so my chroot netboots nfs just fine now
14:29
now i handle the tmpfs bind mounts or unionfs..
14:33
<petre>
johnny, does virtualbox offer bridged networking?
14:43
<johnny>
offer?
14:43
you can use it with bridged networking
14:43
i do myself
14:43
ltsp servers won't really work over NAT:)
14:43
you can use internal networking too
14:44
but i'm not
14:54
<petre>
hm, last time I looked at VB I only remember NAT, which I didn't want
14:54
I'll look at it again, probably an oversight on my part
14:55
<johnny>
i've been using it since 1.5.2.. it's been there since then at least
15:01
<petre>
johnny, looks like it defaults to NAT; do I just go in and attach it to, say, my wireless adapter?
15:02
<johnny>
you have to setup briding in your OS
15:02
bridging*
15:02
so whatever you do for that
15:02
<petre>
hm, not sure
15:02
<johnny>
and then you tell it what interface to use.. mine are vbox[0-9]
15:03
there are docs about that on the vbox site
15:04
for some common OSes
15:04
for /etc/network/interfaces for any debian variant
15:04
and /etc/sysconfig for those who use redhat style
15:04
<petre>
it appears I've got some virtual interfaces, probably leftover from a failed vmware installation
15:05
well, I'm trying to run fedora on ubuntu, so I've got a bit of both ;-)
15:06Egyptian[Home] has quit IRC
15:15Egyptian[Home] has joined #ltsp
15:19petre has quit IRC
15:29praveer_cool has quit IRC
15:33J45p3r has joined #ltsp
15:42markvandenborr1 has joined #ltsp
15:42markvandenborr1 has left #ltsp
15:49rjune has quit IRC
16:03bobby_C has quit IRC
16:18mikkel has quit IRC
16:45IRCzito has joined #ltsp
16:47
<IRCzito>
Hi guys, Im try understand, how ltsp5+pulseaudo works, where I can get some info?
16:48
ow, i found something on wiki.ltsp http://developer.novell.com/wiki/index.php/Edgy/HOWTO:_PulseAudio
16:48johnny_ has joined #ltsp
17:03Egyptian[Home1 has joined #ltsp
17:09Egyptian[Home] has quit IRC
17:22cpunches has joined #ltsp
17:27IRCzito has quit IRC
17:29IRCzito has joined #ltsp
17:39
<IRCzito>
someone can sendme actual /opt/ltsp/i386/etc/pulse/default.pa, of ubuntu.
17:41
<dberkholz>
johnny: good to hear
17:42
<johnny_>
what did i say?
17:42
i'm not at home atm
17:43
i should use irssi :(
17:43
i was hoping to run into vagrantc to see how he isn't using unionfs
17:43
since the initfile in the branch forces unionfs
17:44
dberkholz, i got my account enabled for the overlay
17:44
i'll show you my ebuild later tonight
17:44
for ltsp-client
17:44
it doesn't do jetpipe tho
17:44
wasn't sure if we should bother with jetpipe or not
17:45
imo jetpipe should be it's own init script
17:45
but maybe i'm missing something..
17:48deavid has quit IRC
17:58K_O-Gnom has quit IRC
20:25ltspbot has joined #ltsp
20:35
<cliebow>
launchpad.net opens here//
20:40ffhghgf has joined #ltsp
20:40soneyka has quit IRC
20:52ffhghgf has quit IRC
20:52akl has joined #ltsp
21:04cliebow has quit IRC
21:18johnny_ has quit IRC
21:34J45p3r has quit IRC
21:46ffhghgf has joined #ltsp
21:46akl has quit IRC
21:53Egyptian[Home] has joined #ltsp
22:09Egyptian[Home1 has quit IRC
22:22tux_440volt has joined #ltsp
22:56spectra has quit IRC
23:01otavio has quit IRC
23:19subir has joined #ltsp
23:22cpunches has joined #ltsp
23:42tux_440volt has quit IRC
23:59cpunches has quit IRC