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


Channel log from 13 March 2016   (all times are UTC)

04:43vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 240 seconds)
07:02Freejack has left IRC (Freejack!~Freejack@unaffiliated/freejack, Remote host closed the connection)
07:02Freejack has joined IRC (Freejack!~Freejack@unaffiliated/freejack)
07:18fuzzmew has joined IRC (fuzzmew!~fuzzmew@71.216.56.79)
07:25
<fuzzmew>
i have a disibility so please forgive i dont get my point across or ask right questions. if i post in future. u might have to ask me a olot of questions too.
07:32fnurl has left IRC (fnurl!3d3edc4a@gateway/web/cgi-irc/kiwiirc.com/ip.61.62.220.74, Quit: http://www.kiwiirc.com/ - A hand crafted IRC client)
07:33
<gehidore>
no worries...
07:33
at least from me
07:34fnurl has joined IRC (fnurl!3cf8605f@gateway/web/cgi-irc/kiwiirc.com/ip.60.248.96.95)
07:41
<fuzzmew>
thank you
07:42vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
07:43
<gehidore>
so in what way are you using ltsp?
07:49
<fuzzmew>
i just want to make it so my brother and me can share the new 8 core amd machine with Mint on it 17.3
07:50
Using maybe intel atom board as thin client
07:50
2 thin clients is all we need
07:53vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
07:53
<gehidore>
very nice
07:54
I was just discussing with alkisg what affordable thin clients were out there and I just ordered this: http://www.newegg.com/Product/Product.aspx?Item=N82E16813157616
07:58
<fuzzmew>
I wonder if an intel atom with 4Gb of ram would be powerful enough?
07:59
I thought of getting one, if I cood ever get it to bood that is
07:59
<gehidore>
well if you're doing thin client nearly any machine would work
08:00
alkisg's suggestion is to run the cpu past cpubenchmark.net and compare the postmark value
08:01
which opened my eyes as I was looking at arm and atom soc's and found they weren't as quality as the one I linked to
08:03
<fuzzmew>
how come nothing boots though? I typed in all the things the tutorials told me to, and never boots. I don't understand
08:04
for now I am just using an old laptop with pxe boot. its all I have for now
08:04
Not possible with mint eh?
08:05
<gehidore>
I was making it work with archlinux so I would think mint would work
08:06
have you checked the pxe server with telnet?
08:06
or whatever the manual suggests for testing, it's been a while since I've actually diagnosed any issues
08:07
<fuzzmew>
i dont know how to do that.
08:07
<gehidore>
lemme see if I can find it
08:07
<fuzzmew>
Ok
08:07ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
08:07
<fuzzmew>
many thanks
08:09
<gehidore>
are you sure the laptop supports pxe?
08:11
<fuzzmew>
pretty sure, it says pxe boot when it comes up
08:11
so I asume it means that unless i miss something
08:11
<gehidore>
excellent
08:11
does it do anything at that point or just fail to find a pxe server to hook into?
08:12
<fuzzmew>
pxe 2.0 (build 082) or something like that
08:12
it says soemething like tftp..... then it poops
08:13
<gehidore>
ok I recal having a similar issue lemme look up the logs
08:13
<fuzzmew>
many thanks
08:14
<gehidore>
http://irclogs.ltsp.org/?d=2015-07-02
08:14
scroll down to 19:40
08:18
now I want that SOC machine here yesterday so I can be playing with LTSP in person again
08:18
so many projects... so little time
08:24
<fuzzmew>
oh so dhcp is broken.
08:25
<gehidore>
that could be the case
08:25
worth investigating the same way that alkisg had me do back then
08:33
<fuzzmew>
If i cood write programmes I would make an automatic config one to set it all up
08:38Hyperbyt1 has joined IRC (Hyperbyt1!jan@middelkoop.cc)
08:38Hyperbyte has left IRC (Hyperbyte!jan@middelkoop.cc, Ping timeout: 246 seconds)
08:38Marqin has left IRC (Marqin!~marqin@spiramirabilis.net, Ping timeout: 246 seconds)
08:38Marqin has joined IRC (Marqin!~marqin@spiramirabilis.net)
08:39sutula has left IRC (sutula!~sutula@207-118-160-27.dyn.centurytel.net, Ping timeout: 246 seconds)
08:39sutula has joined IRC (sutula!~sutula@207-118-160-27.dyn.centurytel.net)
08:41
<gehidore>
that would be nice wouldn't it?
08:41
and not a bad idea for future reference... /me adds this to his notes
08:41
<fuzzmew>
yes. i wish i cood do it.
08:42
<gehidore>
with a little practice I'm sure you could
08:42
<fuzzmew>
i think in my case it would be alot, i need help with those things, can't do it myself.
08:43
<gehidore>
perhaps... only you can say for sure
08:43
<fuzzmew>
yes it wood take someone to train me to programme.
08:45
i can crash test though hehe
08:45
i used to send coredumps and backtrace stuff to the develepers of "gaim" an aol instant messenger closne
08:46
to help the guys out when i cood
08:46
<gehidore>
I remember gaim
08:46
before I gave up on anything that wasn't skype or hangouts... now I don't even use skype
08:46
<fuzzmew>
i would do all kinds of crasy stuff to it to make it crash then send them the results. they appreciated it.
08:47
i still use skype sometimes. i cant type for crap. heh
08:47
i do better with phone. or I just copy and paste. maybe change an IP in the configs
08:48
<gehidore>
quality developers appreciate patient alpha / beta testers who can back their findings with trace and dumps
08:50
<fuzzmew>
if i know i can help with something , a programme i'd like to see bettered, I sure will. I just sent them the coredump or back trace and said "umm, what does this mean"? and they'd say "oh crap! I totally missed that thanks!" and theyd give me a little rundown on what happend. then theyd ask me to test the new re-compile
08:53
or I'd run across a web page that had a little software experiment "my crappy experiment" or something and test it , not even knowing what it supposed to do ack! :) just curious about some programmes. make it crash and ask them what it means.
08:54
I love how Linux has come as far as it has, used to be I had to have someone show me what to type in to make the sound even work back in the late 1990s
08:55
I tried to make windows work for me and I just cannot use it, I think it is more for gaming and maybe office work, but it does not do what I need it to do, so I went with linux and mac OS. Mostly linux now.
08:56
<gehidore>
cheers fuzzmew it's 0200 I should sleep
08:57
<fuzzmew>
oh ok, yes, i probably should as well. goodnight and good luck with things
08:57fuzzmew has left IRC (fuzzmew!~fuzzmew@71.216.56.79, Quit: Leaving)
09:34krimtsev has joined IRC (krimtsev!c1c02418@gateway/web/freenode/ip.193.192.36.24)
09:35
<krimtsev>
hallo
09:36
guys, what hardware is necessary for the ltsp clients?
09:42
<quinox>
something with a network port
09:44
<krimtsev>
:D
09:45
<quinox>
if your clients aren't "beefy" hardware wise you can run them as thin clients, meaning the server does most of the work
09:45
if your clients are "beefy" you could run them as fat clients, meaning they do most of the work themselves
09:46
we buy the cheapest parts for clients which are still more than enough to run them in fat client mode
09:48
<krimtsev>
intel 420 + 2GB RAM normal?
09:49
now we have windows server 2008 r2 on this hardware
09:49
thinkstation
09:50
<quinox>
'work_alkisg: lauri, if your client specs are good enough (e.g. 1000+ cpubenchmark, 1000+ MB RAM) you could use them as ltsp fat clients instead'
09:51
http://www.cpubenchmark.net/cpu.php?cpu=Intel+Celeron+420+%40+1.60GHz says it gets a cpubenchmark of 450
09:51
so fat clients might not be the best, but thin clients should be no problem unless you have a slow LAN
09:52
<krimtsev>
i found on ltsp wiki
09:52
If you have slower clients, in the range of 233 MHz to 533 MHz, you may be able to use them, if you're willing to reduce the security of your thin client network
09:52
@quinox ty :D
09:54krimtsev has left IRC (krimtsev!c1c02418@gateway/web/freenode/ip.193.192.36.24)
10:25adrianorg has left IRC (adrianorg!~adrianorg@201.22.230.235, Ping timeout: 260 seconds)
10:27adrianorg has joined IRC (adrianorg!~adrianorg@189.58.230.246.dynamic.adsl.gvt.net.br)
15:24robb_nl has joined IRC (robb_nl!~robb_nl@62.235.16.45)
15:34robb_nl has left IRC (robb_nl!~robb_nl@62.235.16.45, Ping timeout: 250 seconds)
16:28vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
16:29
<vagrantc>
sbalneav: so, regarding lightdm-webkit*-greeter ... would you like to be the primary maintainer, and me just be a sponsor?
16:30
<sbalneav>
vagrantc: Say the antergos developers
16:30
<vagrantc>
?
16:30
sbalneav: or rather, i mean in debian
16:30
<sbalneav>
Oh, ok, sure.
16:33
vagrantc: You are awesome, as per usual
16:39
<vagrantc>
sbalneav: i've just build-tested them ... haven't actually tried them yet
16:44
<sbalneav>
Simple theme should work.
17:40danny_ has joined IRC (danny_!73f15dd9@gateway/web/freenode/ip.115.241.93.217)
17:40
<danny_>
hello
17:41danny_ has left IRC (danny_!73f15dd9@gateway/web/freenode/ip.115.241.93.217, Client Quit)
17:43
<vagrantc>
sbalneav: ok, so now i've gone as far as to install lightdm-webkit-greeter ... how do i enable it?
18:10
sbalneav: looks like lightdm-webkit-greeter and lightdm-webkit2-greeter have some file conflicts...
18:12
sbalneav: they both ship files in /usr/share/lightdm-webkit/
18:13
probably trivially patchable to install in /usr/share/lightdm-webkit2/
18:13
it's just the theme files ...
18:15
i guess, this gets back to the question of weather it's worth shipping both or not
18:33
sbalneav: i tried configuring greeter-session=lightdm-webkit-greeter and greeter-session=lightdm-wekbit2-greeter ... but lgithdm fails to start
18:48
<sbalneav>
Hm
18:49
ok lets check this
18:50
have you got a /usr/share/xgreeters/lightdm-webkit2-greeter.desktop?
18:50
<vagrantc>
believe so
18:51* vagrantc boots the machine and checks
18:53
<vagrantc>
sbalneav: hah! wekbit != webkit
18:54
<sbalneav>
hahaha
18:55
I can be the maintainer for lightdm-wekbit2-greeter too, if that helps ;)
18:56
<vagrantc>
even spelling it right still fails
18:56
[+0.01s] DEBUG: Seat seat0: Failed to find session configuration lightdm-webkit2-greeter
18:57
<sbalneav>
one sec...
18:58
<vagrantc>
ok, i had webkit-2greeter installed ... now putting in the actually installed greeter seems to work.
18:59
<sbalneav>
ah, ok
18:59
So it's popping up?
18:59
<vagrantc>
yeah
18:59
<sbalneav>
cool
18:59
<vagrantc>
and restarting lightdm when webkit2-greeter is only partially installed also results in problems for some reason... :)
19:00
that could just be my packaging mistake ... i excluded the .la file in the hopes that it would work without it
19:06
nope, those are in both packages.
19:09
<sbalneav>
Are you seeing the theme come up?
19:09* vagrantc wonders if it's defaulting to the theme that i patched out
19:09
<sbalneav>
Check what the config file says
19:09
/etc/lightdm/lightdm-webkit2-greeter.conf
19:09
<vagrantc>
ding ding ding
19:10
<sbalneav>
Of course, for debian, you want to get it tied into the /etc/alternatives system
19:10
lightdm-greeter
19:10
/etc/alternatives/lightdm-greeter
19:11
<vagrantc>
ok, now it displays
19:11
ah, ok, there's already an alternative ... cool.
19:12
and i can even log in!
19:13
those simple themes sure are simple!
19:16
<sbalneav>
That was the plan. "The simplest theme that a) shows off the capability of webkit2-greeter and b) properly implements a login with all messages"
19:17
<vagrantc>
hrm. so now i guess i should try with libpam-sshauth?
19:17
<sbalneav>
sure. should work
19:22* vagrantc digs memory of how to configure that out
19:24
<vagrantc>
simple greeter pulls no punches when you hit the shutdown button
19:24
<gehidore>
very true
19:24
shut down my server the other day by mistake :P
19:24
<vagrantc>
none of this "are you sure?" "other peopel are logged in, please proove you're an authority and more important"
19:27
<gehidore>
hal9000 at its finest
19:33
<vagrantc>
whoah... "ltsp-update-image /" without --cleanup sure spits out lots of complaints
19:34
<gehidore>
:|
19:47robb_nl has joined IRC (robb_nl!~robb_nl@ip-80-236-223-85.dsl.scarlet.be)
20:01
<vagrantc>
wow. isc-dhcp-server in debian stretch is broken in so many ways.
20:01
it really is time to default to dnsmasq.
20:05
sbalneav: well, it seems lightdm with libpam-sshauth is working ... still need to update the ltsp-pam hooks to work with stretch.
20:07
<sbalneav>
cool
20:08
<vagrantc>
well, "working" in that it authenticates ... but lightdm fails to log in.
20:08* vagrantc should try without all the extra hooks.
20:13
<vagrantc>
yup, works as a kiosk with a local homedir
20:14
oh wow...
20:14
sbalneav: so, if i type in "root", it logs in as root without asking for a password
20:14* vagrantc suspects pam_permit is a bit too permissive
20:15
<sbalneav>
yeah, that's a problem with your pam config :D
20:15
<vagrantc>
ok.
20:16
sbalneav: my config is based on your examples :P
20:17
sbalneav: if i take out pam_permit, it fails to log in at all.
20:17
<sbalneav>
OK, there's a problem with my pam config :D
20:18
hahaha
20:19
<vagrantc>
sbalneav: so ... how to configure pam_sshauth ?
20:19
this basically works quite well for a kiosk session
20:20frederickjh has joined IRC (frederickjh!~frederick@84-74-197-237.dclient.hispeed.ch)
20:20
<sbalneav>
I'd have to look... I'll take a look tonight... I'm dealing with another problem at the moment... hell, for all I know, it's a bug in libpam_sshauth
20:24
<frederickjh>
Hi! Its been awhile since I setup a LTSP server. I just set one up using ltsp-pnp My clients make it to the login but the desktop never loads. I can switch to a terminal and ssh in fine. syslog is showing the message "nbd_server: Disconnect request received." Anyone have any ideas on how to troubleshoot this?
20:25
<vagrantc>
frederickjh: the nbd message is just ldm checking for an updated inmage
20:25
frederickjh: most likely
20:25
frederickjh: look at the user's ~/.xsession-errors file
20:25
<frederickjh>
On the server or client?
20:25
<vagrantc>
frederickjh: what's the default desktop? might try using an alterate desktop
20:25
frederickjh: should be the same, unless something's broken.
20:26
<frederickjh>
Unity
20:26
<vagrantc>
not sure if unity works with LTSP...
20:27
<frederickjh>
Last line of ~/.xsession-errors reads: "open: Permission denied"
20:27
<vagrantc>
sbalneav: ok, thanks so far, lightdm-webkit*-greeter looks pretty cool.
20:28
<frederickjh>
line before that says: init: update-notifier-crash (/var/crash/_usr_lib_virtualbox_VirtualBox.0.crash) main process (1990) terminated with status 127"
20:28
<vagrantc>
frederickjh: ~/.xsession-errors is pretty verbose ... but it might reveal something
20:28
<sbalneav>
vagrantc: Good! Glad you like it!
20:28
<frederickjh>
I am running the client in Virtualbox but a real client does the same thing.
20:28* vagrantc is really itching to make some progress towards LTSP6
20:29
<vagrantc>
frederickjh: try a different desktop environment
20:37ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 276 seconds)
20:38ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
20:49robb_nl has left IRC (robb_nl!~robb_nl@ip-80-236-223-85.dsl.scarlet.be, Quit: I'm gone, bye bye)
20:56Hyperbyt1 is now known as Hyperbyte
21:06ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
21:12MCMXI has joined IRC (MCMXI!~kvirc@v-74-91-112-62.unman-vds.internap-atlanta.nfoservers.com)
21:29
<frederickjh>
Ok, I managed to track down the problem. I it is related to the permissions on /tmp on the client. They were 755 but needed to be 777. I found this in an IRC log from this channel. The permissions in the build directory /opt/ltsp/build-i386 for /tmp are correct. Any ideas on how to fix this in the image?
21:30
http://irclogs.ltsp.org/?d=2012-05-12 is the link to the irc log I mentioned.
21:30
<vagrantc>
what version of ubuntu?
21:30
<frederickjh>
14.04.4
21:31
<vagrantc>
!ppa
21:31
<ltsp>
I do not know about 'ppa', but I do know about these similar topics: 'sbalneav-ppa', 'greek-schools-ppa'
21:32
<vagrantc>
!greek-schools-ppa
21:32
<ltsp>
greek-schools-ppa: https://launchpad.net/~ts.sch.gr/+archive/ppa/ supports LTS Ubuntu releases with newer LTSP versions, bug fixes etc
21:32
<vagrantc>
i'm not sure if that's an LTSP problem, or an ubuntu problem ... but the greek-schools-ppa miight fix it if it was in LTSP
21:32
LTSP maintenance in ubuntu suffered a bit the last year or so
21:32
<frederickjh>
I have the greek school ppa install.
21:33
<vagrantc>
ltsp-info
21:33
!paste | echo frederickjh
21:33
<ltsp>
frederickjh paste: try !pastebot
21:33
<vagrantc>
!pastebin | echo frederickjh
21:33
<ltsp>
frederickjh 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.
21:34
<frederickjh>
I did the ltsp-pnp using the package from: deb http://archive.amxa.ch/ubuntu trusty main
21:34
That installs the greek schools ppa
21:36
<vagrantc>
wait, build directory?
21:36
that doesn't sound like ltsp-pnp at all.
21:36
frederickjh: how do you build the client image?
21:37
frederickjh: please paste the output from ltsp-info to a pastebin
21:40
<frederickjh>
http://pastebin.com/x8EFZ5iX ltps-info output
21:40
Maybe I am using the wrong name.
21:40
I am new to ltsp-pnp
21:41
My last build of a ltsp server was on 10.04. Than is what I am trying to replace now with a new server.
21:43
The directory that I was referring to is /opt/ltsp/build-i386/tmp/ It has 777 permissions.
21:43
<vagrantc>
ltsp-pnp is a simpler way to manage LTSP
21:43
!ltsp-pnp | echo frederickjh
21:43
<ltsp>
frederickjh ltsp-pnp: ltsp-pnp is an alternative (upstream) method to maintain LTSP installations for thin and fat clients that doesn't involve chroots: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
21:44
<vagrantc>
frederickjh: looks like you have the ppa installed only on the server
21:44
frederickjh: you also need to install it in the chroot
21:44
<frederickjh>
However doing Ctrl-Alt-F2 where I have a root shell setup and checking the permissions of /tmp shows they are 755
21:45
<vagrantc>
although it would probably be easier to do it using ltsp-pnp
21:45
<frederickjh>
Now you have me confused. My understanding is there is no chroot in ltsp-pnp
21:45
<vagrantc>
frederickjh: yes, because you're running the old version of ltsp on the clients.
21:45
frederickjh: yes, but i think you're running the chroot's version, not the ltsp-pnp bui.d.
21:45
<frederickjh>
Old version where did you see that?
21:46
<vagrantc>
frederickjh: the output of ltsp-info
21:46
on a terminal on tty2(ctrl-alt-f2), what version does "dpkg -l ltsp-client-core" ?
21:46
<frederickjh>
Why would I have an old version? This is a fresh install. I followed the instructions found here: https://github.com/basilstotz/ltsp-pnp
21:49
<vagrantc>
frederickjh: i have no idea what basilstotz does, you should report bugs to that. it's not part of LTSP.
21:49
<frederickjh>
5.5.5~r2703+p1238+2015
21:49
<vagrantc>
frederickjh: from a booted client?
21:49
<frederickjh>
Yes
21:49
from the root shell
21:50
<vagrantc>
ok, so you've got /opt/ltsp/build-i386 for no useful reason.
21:50
<frederickjh>
I maybe made it by mistake
21:50
<vagrantc>
a red herring... was hoping it was as simple as that
21:50
<frederickjh>
The ltsp-pnp pagkage has a build option. It maybe something that was left over.
21:50
from old development.
21:51
I was not sure when I got set back to the login each time after login in if the problem was with the image or ssh keys or what.
21:53
<vagrantc>
that looks like the project you used to install it, which is notably not "LTSP-PNP" as it is used by the LTSP project, might have some sort of network authentication or soemthing?
21:53
frederickjh: it seems to be a part of a larger project
21:58
frederickjh: or if you want to try to keep using that, file bugs in the issue tracker https://github.com/basilstotz/ltsp-pnp for that project.
21:59
<frederickjh>
So where is the "other" ltsp-pnp install located at?
21:59
Or how do you set it up? Are there instructions some where online?
22:00
<vagrantc>
!ltsp-pnp | echo frederickjh
22:00
<ltsp>
frederickjh ltsp-pnp: ltsp-pnp is an alternative (upstream) method to maintain LTSP installations for thin and fat clients that doesn't involve chroots: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
22:02
<frederickjh>
Ok, I was to that page and then a page in German here: https://wiki.ubuntuusers.de/LTSP/LTSP-PNP_mit_Fat_Clients/
22:03
There are bash scripts at the bottom of that page to setup ltsp-pnp and to update the ltsp system images
22:04
<vagrantc>
all you need to update the images is a single command.
22:06
frederickjh: no clue what LTSP-install.sh actually does.
22:07
<frederickjh>
One other question, the files in /opt/ltsp/build-i386, there not needed, are they with ltsp-pnp?
22:07
<vagrantc>
it just seems like an additional part that can go wrong
22:07
frederickjh: not needed at all for ltsp-pnp, not.
22:07
frederickjh: maybe they were added to support i386 clients on an amd64 server?
22:08
frederickjh: but the recommended way to do that is to run the i386 OS on the amd64 server.
22:08
don't loose too much with a PAE kernel installed.
22:09
<frederickjh>
No, I don't think so. I think I created them trying to fix this problem. Server is a 64 bit machine but I have 32 bit clients so I installed 32bit OS so I could use ltsp-pnp
22:12simonlnu has joined IRC (simonlnu!~eric@malsum.org)
22:12simonlnu has left IRC (simonlnu!~eric@malsum.org)
22:13SOUL_OF_r00T has joined IRC (SOUL_OF_r00T!~leonardo@unaffiliated/soul-of-r00t/x-4421326)
22:13
<SOUL_OF_r00T>
hello guys my settings appear ok i am trying debian ltsp, anya can help me? the client box no mount root fs
22:13
?
22:15
i have tryed nfs mount from other boxes and it's ok
22:16
the message on client is no init found
22:16
any tip for me?
22:17
<frederickjh>
vagrantc I just checked the update launcher and it is running the clone process in the /etc/init.d/ltsp-pnp that was installed. It is not calling the build function. I will file a issue on github and see what happens. Thanks again for your time and help!
22:33
Sorry SOUL_OF_r00T, I don't think I can help you there.
22:35
<SOUL_OF_r00T>
here is the irc channel over ltsp is it?
22:35
why not help me?
22:36
<frederickjh>
vagrantc, I just checked the /etc/init.d/ltsp-pnp script when it is run with the launcher which runs it with the clone option it also first goes through an init function that sets it up the first time then does not run. So it looks like the build option is never run by the launcher.
22:37
SOUL I would help you if I could. I am not really sure what exactly you are talking about. with root fs
22:37
Do you mean the host file system?
22:37
<SOUL_OF_r00T>
my root / partition is not mounted on ltsp clients
22:37
<frederickjh>
Can the clients not not access their /home/user directory?
22:38
Do you have anything useful in the log?
22:38
<SOUL_OF_r00T>
only one screen with boot: and no default ui configuration directive found
22:38
<frederickjh>
/var/log/syslog
22:42
<SOUL_OF_r00T>
http://pastebin.com/52SrMh05
22:42
the system not found some files
22:43
i follow the official how to
22:43
i have a litle knownledge but is confused
22:44
<frederickjh>
let me have a look at the pastebin
22:45
Ok what you pasted is from the bootup when it is trying to find an image to boot from.
22:46
<SOUL_OF_r00T>
yeap
22:46
<frederickjh>
It tries the most specific and then tries less specific names for the images to boot.
22:46
Does it stop there and go no further?
22:47
<SOUL_OF_r00T>
i have corrected
22:47
i try again
22:47
very thanks
22:47
<frederickjh>
OK, I look
22:47
<gehidore>
moin
22:48
<frederickjh>
Do you have a new pastebin url? The old one is the same here.
22:49
<SOUL_OF_r00T>
the error now is can't execute test no such file or directory on client box
22:51
<frederickjh>
I do not understand.
22:51
Does it boot to the login screen?
22:52
<SOUL_OF_r00T>
no
22:52
<frederickjh>
Maybe a photo of the screen then post it on a photo sharing site like photobucket so I can see what you are looking at.
22:57
Does your client machine have a 64 bit CPU?
22:58
<SOUL_OF_r00T>
yeh all boxes amd64
23:02Tatanka has joined IRC (Tatanka!~tim@revue.vtk.be)
23:06
<SOUL_OF_r00T>
work
23:07
very thanks
23:07
<frederickjh>
what?
23:07
Did you get it to work?
23:07
Did it boot?
23:08
<SOUL_OF_r00T>
yeap
23:08
boot
23:08
logon screen
23:08
xfree
23:08
all work
23:09
<frederickjh>
Good! Not sure what I did to help, but I am glad you got it up and running.
23:09
<SOUL_OF_r00T>
my dhcp runs o n freebsd box i have made some experiences in settings on it and now all works fine
23:09
<frederickjh>
OK, I am working on a problem of my own.
23:10
For some reason the permissions on the /tmp folder on the client have the wrong permissions.
23:10
This cause the xsession to be denied starting.
23:11
I can change the permissions but after a reboot the permissions are wrong again.
23:11
<gehidore>
http://www.newegg.com/Product/Product.aspx?Item=N82E16813157595 wonder if one could use those puny mini-pci ssd in that...
23:24frederickjh has left IRC (frederickjh!~frederick@84-74-197-237.dclient.hispeed.ch)