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


Channel log from 16 October 2009   (all times are UTC)

00:02Sarten-X has joined #ltsp
00:17Sarten-X has quit IRC
00:27Sarten-X has joined #ltsp
00:41cyberorg has quit IRC
00:43cyberorg has joined #ltsp
00:59alkisg_work has joined #ltsp
01:05Sarten-X has quit IRC
01:16Sarten-X has joined #ltsp
01:26Sarten-X has quit IRC
01:36Sarten-X has joined #ltsp
01:52alkisg_work has quit IRC
02:12alkisg has joined #ltsp
02:24din_os has joined #ltsp
02:55bobby_C has joined #ltsp
03:18chupacabra has quit IRC
04:00garymc has joined #ltsp
04:09Selveste1___ has joined #ltsp
04:10avlis has joined #LTSP
04:18jhutchins_lt has quit IRC
04:28jhutchins_lt has joined #ltsp
04:36alkisg has quit IRC
04:50din_os has quit IRC
05:01sene has joined #ltsp
05:24alkisg has joined #ltsp
05:49alexqwesa has quit IRC
05:56alexqwesa has joined #ltsp
06:02kusznir_ has quit IRC
06:05alkisg has quit IRC
06:12alexqwesa has quit IRC
06:13kusznir_ has joined #ltsp
06:16pmatulis has joined #ltsp
06:18alkisg has joined #ltsp
06:29bobbyC has joined #ltsp
06:29bobby_C has quit IRC
06:48alexqwesa has joined #ltsp
06:54sene has quit IRC
06:57jammcq has quit IRC
07:34rjune has quit IRC
07:54johnny has left #ltsp
08:03alkisg has quit IRC
08:07cliebow has joined #ltsp
08:08pmatulis has quit IRC
08:15pmatulis has joined #ltsp
08:28pmatulis_ has joined #ltsp
08:33dro has joined #ltsp
08:35pmatulis has quit IRC
08:48alkisg has joined #ltsp
09:07jhutchins_lt has quit IRC
09:21rjune has joined #ltsp
09:28
<Appiah>
I made a profile that has the menu with only the software that's gonna be used
09:28
and all users have been created
09:29
now I want to change that menu , is there a easy way to change this on the users or should I just replace all ~/.config/ (script)
09:36
<_UsUrPeR_>
appiah: is that with sabayon?
09:37avlis has quit IRC
09:37
<Appiah>
nope
09:37
wish I could use sabayon but it just crashes
09:38
<_UsUrPeR_>
ok, well if you've removed the System Menus, you can still get to the "main menu" program by using terminal or alt+F2
09:38
from there, run alacarte
09:38
<alkisg>
Appiah: it doesn't crash for me if I use sbalneav's ppa..
09:38
<Appiah>
alkisg: good to know :)
09:38
<_UsUrPeR_>
alkisg speaks the truth
09:38
<alkisg>
Appiah: also, is that change for *all* users?
09:38
If so, I think you can modify the default menus...
09:39
<Appiah>
it's locked down for changes
09:39
users have no access to launch gnome-terminal or xterm
09:40
what's fixed in the PPA that has not made it into the Jaunty repo?
09:40
<_UsUrPeR_>
Appiah: ssh -X into the server and run alacarte from there? :)
09:40jammcq has joined #ltsp
09:40
<jammcq>
good morning my friends
09:40
<alkisg>
Appiah: many critical (=crashing) bugs... :)
09:40
<Appiah>
_UsUrPeR_: what are we talking about right now?
09:41
<sbalneav>
Appiah: have you tried the sabayon packages in my ppa?
09:41
<Appiah>
no never heard of it sbalneav
09:41
until now
09:41
<_UsUrPeR_>
I am assuming you made changes to the desktop of your users which disallows changes to the menu. Is that the case?
09:41GodFather has joined #ltsp
09:41
<Appiah>
_UsUrPeR_: correct
09:42
if I run alacarte on the server ,it will effect all users , is that what you're saying?
09:42
<sbalneav>
https://edge.launchpad.net/~sbalneav/+ppa-packages
09:42
<_UsUrPeR_>
no, it will affect a single user
09:42
but you can copy the gconf after it's created I believe
09:42
<Appiah>
_UsUrPeR_: ye but I have already made my changes :)
09:43
sbalneav: I'll check it out in my lab
09:43
proper working tools *yummy*
09:50Kicer86 has joined #ltsp
09:50
<Appiah>
oh alacarte is what I've been using
09:51
not as familiar with all the gnome names as I thought I was >_>
09:52
<_UsUrPeR_>
Appiah: yeah :)
09:52
that's the one
09:53
<Appiah>
well for now I'll just replace all users application.menu file
09:56garymc has quit IRC
10:10alkisg has quit IRC
10:11Selveste1___ has quit IRC
10:19vagrantc has joined #ltsp
10:26cliebow has quit IRC
10:28evilx has joined #LTSP
10:33Sarten-X has quit IRC
10:35johnny has joined #ltsp
10:35johnny is now known as Guest69355
10:40Sarten-X has joined #ltsp
10:43makghosh has joined #ltsp
10:48Guest69355 has left #ltsp
10:55jhutchins_lt has joined #ltsp
11:17staffencasa has joined #ltsp
11:18vagrantc_ has joined #ltsp
11:25alkisg has joined #ltsp
11:27fotanus has joined #ltsp
11:33vagrantc has quit IRC
11:57cpnogueira has joined #ltsp
12:03chupacabra has joined #ltsp
12:12
<vagrantc_>
jammcq, sbalneav, Ryan52, stgraber, ogra: does this look like a reasonable patch to y'all: http://bugs.debian.org/550989
12:12talntid has quit IRC
12:13
<vagrantc_>
or the makings of a workable patch
12:14
<ogra>
looks ok to me
12:15
<vagrantc_>
i wonder if it also catches hostname and ip matching...
12:15
<ogra>
but i dont know much about the guts of getltscfg ... it always just worked so i never had to touch it
12:15chupacabra has quit IRC
12:15
<vagrantc_>
yeah, same here.
12:15
<ogra>
jim or scott should be best to comment on it
12:15* vagrantc_ wonders what the _GNU_SOURCE define is about
12:16
<ogra>
some headers behave differently with it set
12:16* ogra needs to go afk again
12:17
<vagrantc_>
i guess i could apply it to my next debian upload to test it out, and then upstream if it works ok.
12:19alkisg has quit IRC
12:30johnny has joined #ltsp
12:30johnny is now known as Guest51035
12:35alkisg has joined #ltsp
12:38dro has quit IRC
12:44
<stgraber>
vagrantc_: I agree with the idea but I can't say that the code will just work by looking at it. I don't know getltscfg well enough for that. Testing it to make sure we don't break anything would be good.
12:44
<vagrantc_>
stgraber: sure.
12:48tstafford has quit IRC
12:49bobbyC has quit IRC
12:50tstafford has joined #ltsp
12:59bobby_C has joined #ltsp
13:01tstafford has quit IRC
13:02chupacabra has joined #ltsp
13:03tstafford has joined #ltsp
13:13Sarten-X has quit IRC
13:15Selveste1___ has joined #ltsp
13:28Sarten-X has joined #ltsp
13:35
<vagrantc_>
well, the pattern matching from getltscfg seems to work for me...
13:36
<jammcq>
vagrantc_: i'm looking at the patch now. I tried to do this about 6 or 7 years ago
13:37
<vagrantc_>
cool :)
13:38
<jammcq>
I never knew there was a fnmatch() function
13:39
i'm impressed with how little code had to be added
13:41
<vagrantc_>
my manual tests on the commandline using -n ip and -n mac seemed to work fine.
13:41
<jammcq>
it needs to be document that this is "glob" matching not "regex" matching.
13:41
for this purpose, glob matching is perfect
14:12Lns has joined #ltsp
14:24
<rjune>
!j
14:24
<ltspbot>
rjune: "j" is jammcq!!!!!!!!!!!!!!!!!!!!!!!
14:32rjune has quit IRC
14:38rjune has joined #ltsp
14:45garymc has joined #ltsp
14:50cg_uira has joined #ltsp
14:54ajohnson has quit IRC
14:56Guest51035 has left #ltsp
14:56Guest51035 has joined #ltsp
15:02talntid has joined #ltsp
15:02
<talntid>
anyone here have any trouble with some ltsp clients surfing the web super fast, and some being really slow?
15:02
same internal website
15:05
<Lns>
talntid: same client hardware and switch to ltsp server?
15:07
<talntid>
yes
15:07
everything is identical
15:09
<Lns>
doesn't make sense to me
15:09
<talntid>
me either :\
15:09
<Lns>
heh
15:09pmatulis_ has quit IRC
15:09
<talntid>
its all exact. heh
15:09
<Lns>
could it be something more up the chain than the clients? (like your proxy/router/etc) ?
15:10
<talntid>
well, i'm not using a proxy...
15:10
router is identical, and on nearly-stock settings..
15:10
i have a xen machine, ltsp1...
15:10
and another one called www1
15:11
most clients on ltsp1 can hit the website on www1 instantly
15:11
.. but not some of 'em
15:12
<Lns>
so this is all through xen?
15:12Kicer86 has quit IRC
15:14garymc has quit IRC
15:17
<talntid>
yes, Lns :)
15:21chrisinajar has quit IRC
15:22vmlintu has joined #ltsp
15:23chrisinajar has joined #ltsp
15:25
<vagrantc_>
talntid: consistantly the same clients?
15:26
<talntid>
yes
15:26
one is currently going on right now
15:27
i'm pinging, tracerouting, etc..
15:27
it takes like.. 60 seconds to refresh a page...
15:27
on the browser
15:27
other clients, it's instant
15:27
<Lns>
talntid: are you ltsp clients virtualized as well?
15:27
<talntid>
no
15:27
just the server they are on
15:27
<Lns>
k
15:28
is there anything in common with these slow clients besides the fact that they're slow?
15:29
and/or the users logged on?
15:39
<alkisg>
talntid: you could start benchmarking... e.g. first try iperf or netperf to verify that it isn't some low level problem, then try firefox with an ip address instead of a dns name, etc etc...
15:40
<talntid>
tried firefox with ip...
15:40
tried a different account even.. logged in as an account that works well at another client
15:41
and i am VNC'd to that client perfectly
15:41
<Lns>
talntid: is it consistent that the hardware takes 60sec. to refresh, or sparatic?
15:42
<talntid>
consistant
15:42
<Lns>
what about bootup time? still real slow comparitively?
15:42
(sp)
15:42
<talntid>
nope, boots fine..
15:42davidj has joined #ltsp
15:42
<talntid>
and everything else runs fine
15:42
apps load quickly.. etc..
15:42
<Lns>
"everything else" besides firefox?
15:42
<talntid>
right, but firefox is identical to all the other clients
15:42
<Lns>
yeah
15:43
<talntid>
and if i login to the trouble client with a login that works perfect on another client, it works fine.
15:43
<Lns>
so it's user-specific.
15:43
now we're getting somewhere
15:44
what about logging in with a 'trouble' login on a previously OK client? is it slow?
15:45
<talntid>
i asked him to go login and see...
15:46
so when he's done with his next call, he'll check
15:48
<Lns>
talntid: are these thin client sessions or fat client sessions or firefox localapps..?
15:49rjune has quit IRC
15:49
<talntid>
not fatcliewnt
15:49
firefox runs on the server
15:49
i'd like to try making it run as a localapp... heh
15:51
<vagrantc_>
if
15:52
<Lns>
talntid: you could try renaming their ~/.mozilla folder and see if it helps, maybe something is corrupted, though it sounds like something more low level than that
15:53
<talntid>
Lns: I created a completely new profile, and had them login to it on the problem client
15:53
still slow
15:53
so, seems like a connectivity issue to me somehow...
15:54
bad ethernet maybe...? but i am connected to vnc flawlessly
15:54
<Lns>
so new users are slow, "normal slow users" are slow, but users that work ok on other clients are ok on slow clients?
15:55
<talntid>
no
15:55
on the problem clients, it doesn't matter what user logs in...
15:55
its still slow
15:55
on non-problem clients, it's fine.
15:55
<alkisg>
(11:42:57 μμ) talntid: and if i login to the trouble client with a login that works perfect on another client, it works fine.
15:56
<talntid>
yeah, i havn't been able to reproduce that.
15:56
sorry
15:56
<alkisg>
ok
15:56
<talntid>
i just tried 2 logins
15:56
it seems that the problem clients are just problem clients...
15:56cpnogueira has left #ltsp
15:56
<talntid>
they're gonna have something in common
15:57
<alkisg>
talntid: but they do boot fast, and you can vnc (to? from?) them fast?
15:57
<Guest51035>
hardware?
15:58
<talntid>
correct, alkisg
15:58
Guest51035: Wyse V00L thin client
15:58
800mhz, 512mb ram
15:58
<Guest51035>
are they all that same model?
15:58
<talntid>
yep
15:58Guest51035 is now known as johnny
15:59
<johnny>
then it must be the network?
15:59
<talntid>
i think so
15:59
it's just odd i can vnc it perfectly
15:59
<vagrantc_>
talntid: have you tried switching the cables and ethernet ports on a "good" and "bad" client?
16:00
<talntid>
nah, everything is cut to length
16:00
hard to swap them like that
16:00
<vagrantc_>
swap thin clients?
16:00
<talntid>
problem persists
16:00
<alkisg>
talntid: and the problem is while the page loads? I mean, after it loads, you can scroll the page quickly?
16:00
<talntid>
yes, alkisg, correct
16:01
vagrantc_: replaced client with brand new unit
16:01
<alkisg>
Do you have a dns server around?
16:01
<talntid>
yes
16:01
i run my own dns
16:01
<alkisg>
Maybe some reverse lookup problem or something?
16:01
<vagrantc_>
but if they're logging into the same server...
16:01
<talntid>
it should affect every client then
16:02
traceroute comes up quickly, as does mtr and ping..
16:02shawnp0wers has joined #ltsp
16:02
<alkisg>
Maybe you have dns entries for half of the ltsp clients, I don't know...
16:02
<talntid>
negative.. everything is the same
16:02
25 clients
16:03
<vagrantc_>
analize the network traffic with wireshark, maybe?
16:03
<talntid>
what would i look for?
16:03
<vagrantc_>
differences between a working client and a not working one? :P
16:03
<talntid>
right, but the non working ones work, just slower on web browsing only
16:04
<vagrantc_>
you're going to have to cast the net wide, as there isn't much to go on
16:04
<talntid>
yeah
16:04
<vagrantc_>
so, as best you can, isolate it down to a non-working client ... see if it does anything repetative when it's not working right ... and then try with a working client.
16:04
<alkisg>
talntid: try to minimize the traffic (i.e. have only 1 non-working client try to access the server) and see or upload the dumps....
16:05* vagrantc_ just DoS'ed vagrantc_ with too many layers of bridging.
16:05
<alkisg>
heh
16:06
vagrantc_, I wonder what happens with that new getltscfg patch, when one client matches several sections...
16:06
Only the first one is used?
16:11alkisg has quit IRC
16:13
<Lns>
talntid: what about pinging a DNS name that isn't cached from the trouble clients? does it timeout?
16:13
or take a long time to resolve?
16:14
<talntid>
i don't know of any ?
16:14
just a random name?
16:14
<Lns>
well something like www.cisco.com or something
16:14japerry has quit IRC
16:14
<Lns>
something you'd browse to but isn't cached by your dns server
16:15
<talntid>
k
16:15
instant
16:16
<Lns>
and browsing to external sites is the same as your intranet site (slow)?
16:19Egyptian[Home] has quit IRC
16:20Egyptian[Home] has joined #ltsp
16:21
<talntid>
yes, Lns
16:21
<Lns>
is it the same with another browser, say epiphany?
16:22
<vagrantc_>
alkisg: the same as before: the first one defined in lts.conf is used.
16:22
<Lns>
so weird...certain clients only with http traffic are slow.
16:22
<talntid>
yes, and lynx
16:22
<Lns>
talntid: do you have QOS running anywhere?
16:22
what is your router?
16:22
<talntid>
those clients do NOT have any proxy enviro vars set either
16:22
no qos
16:23
using dell powerconnect switches
16:23
linksys rv086 router
16:23
<vagrantc_>
talntid: can you plug on of the machines directly into the server with a crossover cable?
16:24
<talntid>
no
16:24
<vagrantc_>
reduce the variables to the smallest possible set.
16:24
<talntid>
the server does not have any open ethernet ports
16:25
<vagrantc_>
talntid: i mean for testing; just unplug the current one that goes to the LTSP network.
16:25
<talntid>
i could, yes...
16:25
<vagrantc_>
might be worth a shot.
16:27
<talntid>
i'll try it when everyone leaves
16:30mikedavisong has joined #ltsp
16:31
<mikedavisong>
hi guys
16:31
can anybody help me on how to setup k12ltsp to allow administrators to read/write to users home directories
16:31
thanks
16:32fotanus has quit IRC
16:34
<kusznir_>
Hi all: I've been trying to get my ubuntu-based ltsp distro to do two things that I haven't managed to yet. The first is to run dual-screened on a DevonIT dual-head thin client, and the second is to get it to connect to other, non-ltsp servers.
16:34
<Lns>
mikedavisong: dunno about k12ltsp but ACLs might be a good option
16:34
that's what i use
16:35map7 has quit IRC
16:35
<mikedavisong>
is there a tutorial i can use on the web? i am new to linux
16:35
<johnny>
mikedavisong, put them in wheel and sudo ?
16:35
<kusznir_>
To the first, I've googled a fair bit, but basically all I get is stuff about making your own custom X config file and overriding all the automatic stuff. I'm still learning LTSP5, but used to use LTSP 4.2, and when I ran that, it was a simple 2-3 lines I added to the lts.conf file to enable dual-head.
16:35
Is there something like that for ltsp5?
16:35
<Lns>
mikedavisong: get ready to learn about linux filesystem permissions =)
16:35
<mikedavisong>
great!
16:35
<kusznir_>
(BTW: part of this seemed to require logging into the thin client with a shell so I can take a look around and try different x options, etc. How do I do that? I have shells running, but I can't seem to get a username/password setup that will let me in)
16:36
<Lns>
mikedavisong: https://help.ubuntu.com/community/UbuntuLTSP/ACLSupport
16:36
(should be portable across distros)
16:36
<johnny>
kusznir_, set SCREEN_02=shell
16:36
just like in ltsp4
16:36
iirc
16:37
kusznir_, read lts-parameters.txt.gz
16:37
<kusznir_>
johnny: already done. I get a nice login: prompt, for which I can't get past. I tried adding a password for root in /etc/shadow on the ltsp server's chroot, then reran the make image command, rebooted the thin client, but still couldn't get in.
16:37lucascoala has quit IRC
16:37
<johnny>
no.. there sholdn't be a promt
16:37
<kusznir_>
johnny: as I can't get into the thin client, I can't see why its not letting me in....
16:37
<mikedavisong>
lns: i think i saw this when i googled for it
16:37
<johnny>
it should be a shell
16:37
<mikedavisong>
lns: is there a gui tool for acl's?
16:37
<kusznir_>
Hmm...Ok, I'll try it again.
16:37
<johnny>
i mean.. no login prompt
16:38
kusznir_, the other idea is to set the password in the chroot and then rebuild it
16:38
<Lns>
mikedavisong: google for eiciel
16:38
<johnny>
then you can login that way
16:38* Lns likes that people have already found some of his vids on yt =)
16:38
<mikedavisong>
lns: i tried the commands on the ubuntu help but couldnt get pass the 1st step to confirm if acl is installed or not
16:39
<kusznir_>
johnny: that's what I was hoping for, but so far all I've gotten so far is login prompts from the shell screen command. Also, I tried setting the password in the chroot (at least, for root), and it still wouldn't let me in. (I set the password by copying my password from the server's /etc/shadow for my account, and pasting that into the root's /etc/shadow password field)
16:39
<mikedavisong>
i am using k12ltsp
16:40
<Lns>
mikedavisong: well.. it's going to be difficult for you to manage the permissions if you don't know how to use the package manager for your dist...no offense at all..maybe the best bet would be to just use the root account for making changes to users' homedirs (although that is a very insecure solution)
16:40
mikedavisong: for redhat based dists try 'rpm -qa | grep acl'
16:41
<mikedavisong>
it says i have these libacl-2.2.47-3.fc10.i386
16:41
acl-2.2.47-3.fc10.i386
16:41
installed
16:42
lns: i am trying to install eiciel right now
16:42
<Lns>
k
16:43
<mikedavisong>
lns: i am running eiciel right now and i tried to open a user directory
16:43enmi has quit IRC
16:44
<mikedavisong>
however, all i can see in the ACL is that only the user and "users" and "others"
16:44
<johnny>
kusznir_, did you rebuild the chroot?
16:45
i don't know if they use nbd or not..
16:45
<mikedavisong>
lns: how can i add a user into allow list?
16:45
<johnny>
next time.. just chroot in
16:45
and set it
16:45artista_frustrad has quit IRC
16:46
<mikedavisong>
lns: it shows possible participants but they are all greyed out
16:46artista_frustrad has joined #ltsp
16:46
<Lns>
mikedavisong: i'm not too familiar with eiciel, i always use the shell
16:47
might wanna check the docs...did it ask you for root/your pw when starting eiciel?
16:47
<mikedavisong>
no
16:47
<Lns>
maybe you're not running it as a privileged user
16:47
so it won't let you set perms
16:47
<mikedavisong>
let me try that again
16:48
lns: it does ask for it
16:49
lns: if i use the shell, what is the simplest way of allowing user1 to access user2's home directory?
16:49
do i login as root first?
16:52
<vagrantc_>
probably better to set up a separate directory that certain groups can read/write to, and give all the appropriate users access to that.
16:52
giving people read/write access to each other's home directories has some bad consequences
16:53
<mikedavisong>
vagrantc_: i tried that but the supervisors want to be able to save some files into their subordinates' directories
16:54
<lfaraone>
mikedavisong: then you want to make the supers part of the subs group, and "chmod g+rw" the directories you want
16:54
mikedavisong: (assuming that the subs group owns the files you want)
16:54
*directories you want
16:55
<mikedavisong>
lfaraone: but would that enable the users to see the supers' directory?
16:55
<lfaraone>
mikedavisong: No.
16:55
if you're not chmodding the super's dir, that is.
16:55
<mikedavisong>
lfaraone: how about other subs' individual directories? would they be able to see each other's directories?
16:56
<lfaraone>
mikedavisong: you might want to read through the unix permissions model. As long as subs are not part of other subs group, and the files are not world readable, they won't have r/w access.
16:58
<mikedavisong>
lfaraone: sorry about this, i am so new to linux.
16:59
lfaraone:can you give me an example of how to use chmod g+rw?
16:59
<lfaraone>
mikedavisong: perfectly alright, just something you should get up to speed on :)
16:59
<mikedavisong>
lfaraone: yeah. just dont have that much time to read up on it
16:59Sarten-X has quit IRC
17:00
<lfaraone>
mikedavisong: well, for the full explanation rum "man chmod", but essentially "chmod g+rw DIRECTORY". If you want that to apply recursively to all files and subdirectories in DIRECTORY, do "chmod -R g+rw DIRECTORY"
17:01
mikedavisong: that command will probably have to be run either as the sub's user or as root. by the way, "g" stands for 'group', and "+rw" means "add read and write privileges".
17:01
<mikedavisong>
lfaraone: do i do this while i am logged in as the supervisor and navigate into the directory i want to "open up"?
17:01
oh.
17:01F-GT has quit IRC
17:02
<mikedavisong>
lfaraone: but how do i define which "group" would have that priviledge?
17:03
<lfaraone>
mikedavisong: well, you can create a "supervisors" group, add all the supers to it, and change the group on the directory with "chgrp GROUPNAME DIRECTORY". (use -R as before if you want it to be recursive)
17:04
<mikedavisong>
lfaraone: ok, let me try that
17:06
lfaraone: I tried it and i get this message
17:06
[root@localhost /]# chgrp -R Administrators home
17:06
chgrp: cannot access `home/mikeo/.gvfs': Permission denied
17:06
<lfaraone>
mikedavisong: you can safely ignore that, .gvfs is not something you want to access.
17:07
<mikedavisong>
ok
17:07
<lfaraone>
mikedavisong: that's a GNOME "virtual file system" folder, which allows legacy programs to access mounted remote shares etc
17:07
<Lns>
the bad thing about this is that newly created files/dirs won't have the group assignment unless you have group sticky bit (iirc)
17:08
<mikedavisong>
lfaraone: i tried to access the home directories using Nautilus but still could not get through. it tells me i have no permission to view the files yet
17:09
lns: how do i do the group sticky bit (iirc)?
17:09
<vagrantc_>
mikedavisong: don't forget to set the global umask.
17:09
<Lns>
mikedavisong: you really, really, really should read up on *nix permissions before doing stuff like this...its going to be much quicker than trial/error..jmho
17:10jammcq has quit IRC
17:10
<lfaraone>
mikedavisong: are you a member of the group?
17:10
<vagrantc_>
mikedavisong: what you're trying to do is not impossible, but it's very tricky to do well.
17:10
<Lns>
you don't want to go changing perms recursively like that unless you know what you're doing.
17:10
<mikedavisong>
lns: yeah i guess so...
17:10F-GT has joined #ltsp
17:10
<lfaraone>
mikedavisong: if you just added yourself, you'd have to log out and back in.
17:10
<mikedavisong>
i could fxxk up the system pretty bad by doing this
17:10
<Lns>
yes. yes you could. ;)
17:10
<lfaraone>
mikedavisong: or worse, enable a security hole.
17:11
<vagrantc_>
or both!
17:11
<mikedavisong>
ha!
17:11
<Lns>
hehe
17:11* lfaraone will be back, good luck.
17:11
<Lns>
mikedavisong: try http://www.perlfect.com/articles/chmod.shtml
17:11
<mikedavisong>
kewl
17:12
<Lns>
seems fairly well laid out
17:12
<mikedavisong>
i will read up on this first and play with it on a test system
17:12
so i dont get fired for bringing down the system
17:12
=P
17:12
thanks guys
17:13
<Lns>
:) good idea! hehe
17:14
<mikedavisong>
lns: is the chmod part of the ACL?
17:14shawnp0wers has quit IRC
17:14
<mikedavisong>
lns: just to make sure i dont get confused
17:15
<Lns>
mikedavisong: ACLs go beyond standard unix permission theory - but they all share the ideas and practices
17:15
they're separate from chmod (they use 'setfacl' command)
17:15
<mikedavisong>
lns: okie. so which one is a better option? chmod or acl?
17:15
<Lns>
they accomplish the same general goals though.
17:16
<mikedavisong>
lns: i mean easier to manage and implement
17:16pmatulis has joined #ltsp
17:16
<Lns>
standard perms will always be *easier* to manage, but they have their limitations (which ACL takes care of).
17:16
<mikedavisong>
got it
17:16
thanks. have a nice weekend
17:16
<Lns>
you too, good luck!
17:16
<mikedavisong>
thanks
17:17mikedavisong has quit IRC
17:24bobby_C has quit IRC
17:38Lns has quit IRC
17:38Sarten-X has joined #ltsp
17:41
<kusznir_>
Ok, making some progress...and some steps backward.
17:41
It seems that now for some reason the image that is getting created has some sort of problem...my thin client shows /etc/resolv.conf as being present, but whenever I try and use it (cat /etc/resolv.conf), I get an Input/Output error.
17:42
/etc/resolv.conf is perfectly readable and correct on the host machine.
17:42
err... "on the host machine" == in the chroot.
17:42
I also made some other changes to files there and they are in the nbd image.
17:43
I've re-made the image several times, but all without any success. Any suggestions?
17:50cg_uira has quit IRC
17:50
<kusznir_>
And with respect to my first original question, it appears that when I use an IP address for my alternate host, ldm exits with "assertion GTK_IS_WIDGET(child) failed.
17:51GodFather has quit IRC
18:10
<johnny>
try ubuntu or debian? :)
18:24tstafford has quit IRC
18:27tstafford has joined #ltsp
18:32jontheisguy has joined #ltsp
18:32jontheisguy has left #ltsp
19:22zamba has quit IRC
19:24cliebow has joined #ltsp
19:30Selveste1___ has quit IRC
19:41cliebow has quit IRC
19:41Sarten-X has quit IRC
20:13Egghead has joined #ltsp
20:22vagrantc_ has quit IRC
20:32Sarten-X has joined #ltsp
20:33Topslakr has quit IRC
20:35Topslakr has joined #ltsp
21:13try2free has joined #ltsp
21:17primeministerp has quit IRC
21:22try2free has left #ltsp
21:26LaserJock has joined #ltsp
21:28japerry has joined #ltsp
22:01ogra has quit IRC
22:02ogra has joined #ltsp
22:38lucascoala has joined #ltsp
22:43makghosh has quit IRC
22:49Egghead has quit IRC
22:56LaserJock has quit IRC
23:01pmatulis has quit IRC
23:07alkisg has joined #ltsp
23:28yanu has quit IRC
23:31yanu has joined #ltsp