Back
[01:12:58] <skunkworks> jepler:
http://emc2-buildbot.colorado.edu/buildbot/builders/hardy-i386-trunkish-realtime-rip/builds/21/steps/get-dmesg/logs/stdio
[01:13:06] <skunkworks> get rid of the -admin
[01:13:30] <skunkworks> http://emc2-buildbot.colorado.edu/buildbot/builders/hardy-amd64-trunkish-realtime-rip/builds/6/steps/get-dmesg/logs/stdio
[01:15:44] <jepler> skunkworks: thanks for the top
[01:15:45] <jepler> tip
[01:18:31] <skunkworks> no problem. sure I learned it on here.. anything worth while I learn on this channel :)
[01:56:07] <skunkworks> peter wallace is a very nice person. I could not imagine getting support like that from any other company.
[01:58:22] <cliff> cliff is now known as cblack
[03:33:20] <KimK> * KimK hopes cradek and crew(?) get something to eat before everything closes.
[18:06:40] <logger_1> * logger_1 is logging
[18:07:19] <SWPLinux> take two, they're small
[18:07:19] <skunkworks> SWPLinux: thank you!
[18:07:19] <skunkworks> SWPLinux: thank you!
[18:07:19] <SWPLinux> take two, they're small
[18:07:25] <skunkworks> heh
[18:07:25] <skunkworks> heh
[18:11:18] <psha> SWPLinux: every line will go to two file or will be logged twice in one file? :)
[18:11:18] <psha> SWPLinux: every line will go to two file or will be logged twice in one file? :)
[18:11:41] <skunkworks> logger_dev: bookmark
[18:11:41] <skunkworks> Just this once .. here's the log:
http://www.linuxcnc.org/irc/irc.freenode.net:6667/emcdevel/2010-11-16.txt
[18:11:41] <skunkworks> logger_dev: bookmark
[18:11:41] <logger_dev> Just this once .. here's the log:
http://www.linuxcnc.org/irc/irc.freenode.net:6667/emcdevel/2010-11-16.txt
[18:11:53] <skunkworks> logger_1: bookmark
[18:11:53] <skunkworks> logger_1: bookmark
[18:11:53] <skunkworks> Just this once .. here's the log:
http://www.linuxcnc.org/irc/irc.freenode.net:6667/emcdevel/2010-11-16.txt
[18:11:53] <logger_1> Just this once .. here's the log:
http://www.linuxcnc.org/irc/irc.freenode.net:6667/emcdevel/2010-11-16.txt
[18:12:28] <skunkworks> looks like it might double.
[18:12:28] <skunkworks> looks like it might double.
[18:12:31] <psha> nice )
[18:12:31] <psha> nice )
[18:12:53] <SWPLinux> well. that is teh sukc then, isn't it?
[18:12:54] <SWPLinux> well. that is teh sukc then, isn't it?
[18:12:54] <psha> fault tolerance in action :)
[18:12:54] <psha> fault tolerance in action :)
[18:13:37] <logger_1> * logger_1 is logging
[18:13:53] <SWPLinux> jepler, help! :)
[18:13:53] <SWPLinux> jepler, help! :)
[18:14:07] <SWPLinux> how in the heck do you start only one logger now?
[18:14:07] <SWPLinux> how in the heck do you start only one logger now?
[18:14:15] <SWPLinux> (or really kill one you don't want)
[18:14:15] <SWPLinux> (or really kill one you don't want)
[18:15:16] <psha> hope they don't start producing loggerkids
[18:15:17] <psha> hope they don't start producing loggerkids
[18:15:50] <logger_dev> logger_dev is now known as 17SAAFZ6W
[18:15:50] <logger_dev> logger_dev is now known as 92AABK7SB
[18:15:54] <17SAAFZ6W> * 17SAAFZ6W is logging
[18:15:54] <92AABK7SB> * 92AABK7SB is logging
[18:15:55] <logger_dev> * logger_dev is logging
[18:15:55] <logger_dev> * logger_dev is logging
[18:16:07] <SWPLinux> glargh
[18:16:07] <SWPLinux> glargh
[18:16:07] <SWPLinux> glargh
[18:17:36] <psha> three now!
[18:17:37] <psha> three now!
[18:17:37] <psha> three now!
[18:17:52] <psha> don't touch! don't touch anything! :)))
[18:17:52] <psha> don't touch! don't touch anything! :)))
[18:17:52] <psha> don't touch! don't touch anything! :)))
[18:17:58] <psha> * psha hiding under table
[18:17:59] <psha> * psha hiding under table
[18:17:59] <psha> * psha hiding under table
[18:18:19] <SWPLinux> well, I know how to get it back to one, I think
[18:18:20] <SWPLinux> well, I know how to get it back to one, I think
[18:18:20] <SWPLinux> well, I know how to get it back to one, I think
[18:18:34] <psha> psha is now known as logger_4
[18:18:34] <psha> psha is now known as logger_4
[18:18:34] <psha> psha is now known as logger_4
[18:18:45] <logger_4> * logger_4 is logging
[18:18:45] <logger_4> * logger_4 is logging
[18:18:45] <logger_4> * logger_4 is logging
[18:19:11] <logger_5> * logger_5 is logging
[18:19:27] <logger_6> * logger_6 is logging
[18:19:27] <logger_6> * logger_6 is logging
[18:19:33] <SWPLinux> or not
[18:19:33] <SWPLinux> or not
[18:19:33] <SWPLinux> or not
[18:19:37] <skunkworks> SWPLinux: sorry...
[18:19:37] <skunkworks> SWPLinux: sorry...
[18:19:37] <skunkworks> SWPLinux: sorry...
[18:19:41] <SWPLinux> wtf++
[18:19:41] <SWPLinux> wtf++
[18:19:41] <SWPLinux> wtf++
[18:19:50] <logger_4> * logger_4 is logging too
[18:19:50] <logger_4> * logger_4 is logging too
[18:19:50] <logger_4> * logger_4 is logging too
[18:20:01] <SWPLinux> well, I hope I can get it back to something relatively reasonable before boarding the plane :)
[18:20:01] <SWPLinux> well, I hope I can get it back to something relatively reasonable before boarding the plane :)
[18:20:01] <SWPLinux> well, I hope I can get it back to something relatively reasonable before boarding the plane :)
[18:20:02] <micges> hehe cool ;P
[18:20:02] <micges> hehe cool ;P
[18:20:02] <micges> hehe cool ;P
[18:20:35] <logger_2> * logger_2 is logging
[18:20:36] <logger_5> * logger_5 is logging
[18:20:36] <logger_5> * logger_5 is logging
[18:24:14] <skunkworks> yay!
[18:24:22] <SWPLinux> phew!
[18:24:54] <SWPLinux> but it won't attempt to restart now (which may not have been working anyway)
[18:25:50] <logger_4> * logger_4 is not logging
[18:25:52] <logger_4> logger_4 is now known as psha
[18:25:55] <SWPLinux> prick :)
[18:26:22] <psha> that was atmega's idea :)
[18:26:37] <skunkworks> question on web hosting - do you guys follow a template for setup a on site webserver that will be visable to the web?
[18:27:00] <psha> skunkworks: template?
[18:27:02] <SWPLinux> ?
[18:27:05] <skunkworks> guide
[18:27:30] <psha> do you have computer visible from outside or need to find hosting?
[18:27:35] <SWPLinux> I don't. I write a tiny bit of text like "Check back soon!" and leave it there for 10 years
[18:27:42] <skunkworks> heh
[18:28:04] <skunkworks> I want to setup a 'on site' web server
[18:28:07] <SWPLinux> there are a load of templates available though
[18:28:18] <skunkworks> Just worried about security
[18:28:19] <SWPLinux> do you mean an internal web server?
[18:28:33] <psha> skunkworks: do you need dynamic contents?
[18:28:35] <SWPLinux> (like one that people at the company use but not really others)
[18:28:45] <psha> tons cool buggy php scripts
[18:29:02] <SWPLinux> or are you talking about one you can carry somewhere (like EMC fest) and stick stuff on it?
[18:29:06] <SWPLinux> or something else?
[18:29:44] <skunkworks> it will be used internally and externally
[18:30:09] <SWPLinux> ok, either way
[18:30:19] <skunkworks> we would get another static ip and use
[18:30:19] <SWPLinux> google is probably a friend here :)
[18:30:22] <psha> then deside what kind of content will be hosting
[18:30:23] <skunkworks> I suppose
[18:30:28] <SWPLinux> (web site template)
[18:31:09] <skunkworks> people do it all the time ;)
[18:31:49] <archivist> I self host here
[18:32:04] <SWPLinux> one thing to think about is whether you'll want to have mostly static content or a fair amount of dynamic content (news updates, etc)
[18:32:59] <skunkworks> archivist: no major issues?
[18:33:11] <SWPLinux> in either case, you'll likely want some sort of content management system, but you can use a much simpler one if it's mostly static
[18:33:12] <archivist> no not really
[18:33:14] <skunkworks> SWPLinux: we are purchasing some software that will be run on it.
[18:33:25] <SWPLinux> what? what does that mean?
[18:33:32] <archivist> purhase!!! use apache etc
[18:33:52] <SWPLinux> yeah. if you're buying it, I'd be really concerned about security
[18:33:54] <skunkworks> some catalog type software
[18:33:55] <SWPLinux> :)
[18:33:57] <skunkworks> heh
[18:34:17] <SWPLinux> do you expect to expand that to online ordering at some point?
[18:34:25] <archivist> there are plenty open source ones about too
[18:34:39] <archivist> of varying quality :(
[18:34:40] <skunkworks> yes - and costing
[18:34:45] <skunkworks> *estimating
[18:35:01] <SWPLinux> hmmm
[18:35:19] <SWPLinux> in that case it gets more complex. luckily, I don't know how much more complex :)
[18:35:39] <archivist> I did an online costing thing for a company, can be a money sink
[18:35:52] <skunkworks> yeh - When I had asked what was needed for hosting - they said linux and sql
[18:35:59] <psha> skunkworks: if you are buying something then check it's requirments
[18:36:00] <skunkworks> that is it . linux and sql
[18:36:02] <skunkworks> ;)
[18:36:19] <psha> so install distro you are common with and sql, that's it :)
[18:36:54] <skunkworks> anyhoo - of to do more research.
[18:36:56] <archivist> can even run on your cnc box while you are machining
[18:36:57] <skunkworks> :)
[18:37:08] <SWPLinux> and draw plans with a robot :)
[18:37:47] <skunkworks> heh
[18:38:12] <SWPLinux> ok, time to board. see you later
[18:38:29] <psha> skunkworks: on most distros installing lighttpd, nginx, apache, mysql, ... is just typing 'hey computer, get me this!'
[18:39:39] <psha> most distros ship pretty equal versions of everything (with minor diffirencies)
[18:39:47] <archivist> biggest problems I see for self hosting are a secondary dns, and uplink speed of the adsl line
[18:39:49] <psha> so don't expect something difficult :)
[18:40:40] <psha> stable uplink is real problem...
[18:40:49] <archivist> you wont need fast serving because the uplink data rate
[18:40:59] <archivist> * archivist is pretty stable
[18:41:14] <KimK> So far the best line from Wichita is, "...my robot is right-handed...(cradek)"
[18:41:38] <archivist> skunkworks, expected hits per day?
[18:41:39] <skunkworks> yeah - that is really why we want to host locally. (if we actually get it working - it will do a lot of proccesses internally) so if the internet is down - we cannot be down.
[18:41:50] <skunkworks> archivist: not many at first.
[18:43:06] <alex_joni> KimK: haha
[18:43:07] <archivist> skunkworks, google has a feeding frenzy on mine now and again it handles 12k per day which would be regarded as a low hit rate
[18:43:30] <alex_joni> hmm.. wonder what that was that SWPadnos mentioned
[18:43:52] <alex_joni> "There was one change needed in genserkins, which took less than an hour to
[18:43:53] <alex_joni> figure out."
[22:55:51] <jepler> SWPadnos: ise 12 webpack still excludes xc3s2000.
[22:56:40] <jepler> * jepler fails to find a nice way to test the ise version number
[22:57:15] <jepler> I have determined that it's in ise11+ that the "-r" (disable register ordering) flag was removed, or at least infer it from
http://www.xilinx.com/support/documentation/sw_manuals/xilinx11/ise_r_properties_conversion.htm#styler-id1.1.1.16.5.7.4.3.1
[23:42:12] <jthornton> I'm getting john@zotac:~/emc2-dev$ git push
[23:42:13] <jthornton> fatal: The remote end hung up unexpectedly
[23:42:36] <jthornton> I've checked to be sure I have .ssh and the related files and have git configured
[23:42:52] <jthornton> this is a new computer :/
[23:43:08] <jthornton> * jthornton wonders what I'm missing
[23:43:47] <andypugh> I think I have a special talent. I am getting null pointer exceptions in .comp
[23:43:53] <jepler> 'ssh git.linuxcnc.org' and see what it does. if it says "fatal: what do you think I am? A shell?" then everything's OK.
[23:44:38] <jepler> but if it's a new machine it may say that it doesn't recognize git.linuxcnc.org's public key (in which case, accept it and try your push again), or it might reject you or ask for a password (in which case, look to a misconfiguration in your ~/.ssh)
[23:44:43] <jthornton> ok
[23:44:55] <jepler> so do that and let me know what you learn
[23:45:41] <jepler> andypugh: you're not the only one who writes bugs, you know
[23:45:44] <jthornton> ssh git.linuxcnc.org resulted in Password:
[23:45:48] <jepler> you should know, you've used emc and had a chance to chew on my bugs :-/
[23:46:43] <andypugh> I am guessing that I am using a pin that I haven't created in this personality.
[23:46:54] <jepler> jthornton: OK, pastebin 'ls -l ~/.ssh', let's look at whether the permissions are right
[23:47:14] <jepler> actually, 'ls -al ~/.ssh'
[23:47:24] <jepler> let's make sure of the permissions on the .ssh directory itself are right to
[23:47:25] <jepler> +o
[23:47:56] <jepler> I'm assuming that when you said you set up .ssh, you mean that you copied everything from some other machine?
[23:48:08] <jthornton> http://pastebin.ca/1993944
[23:48:17] <jthornton> yes from my plasma
[23:49:00] <jthornton> I just created the .ssh directory but didn't change any permissions
[23:49:15] <jepler> make sure the directory can be accessed only by your user: chmod -R go-rwx ~/.ssh
[23:50:56] <jthornton> ok, I still get remote end hung up unexpectedly trying to push
[23:51:06] <jepler> did it change what 'ssh git.linuxcnc.org' did?
[23:51:42] <jthornton> yes
[23:51:49] <jepler> OK, then we're one step closer.
[23:51:59] <jthornton> but it wants a password
[23:52:00] <jepler> when and how did you make this git clone?
[23:52:07] <andypugh> Is there a way to force a kernel module to quit? Like an industrial-strength halrun -U
[23:52:23] <jepler> jthornton: urrrrrr
[23:52:29] <jthornton> a few days ago
[23:52:35] <jthornton> following the wiki
[23:52:42] <jepler> jthornton: you said earlier that 'ssh git.linuxcnc.org' resulted in Password:
[23:52:45] <jepler> then you told me it changed
[23:52:54] <jepler> is it still asking you for a password?
[23:53:18] <jthornton> this time it asked me if I wanted to add linuxorg to known hosts then asked for a password
[23:53:57] <jepler> is your ssh private key protected by a password?
[23:54:05] <jthornton> I created it with git clone ssh://
[email protected]/git/emc2.git emc2-dev
[23:54:13] <jthornton> not that I know of
[23:54:33] <jepler> is your linux login name the same as your name on git.linuxcnc.org? maybe you need to 'ssh
[email protected]' for my ssh test to be valid.
[23:54:52] <jthornton> no it is different
[23:55:09] <jepler> OK, then try that ssh instead: ssh
[email protected]
[23:55:48] <jthornton> PTY allocation request failed on channel 0
[23:55:49] <jthornton> fatal: What do you think I am? A shell?
[23:55:51] <jthornton> Connection to git.linuxcnc.org closed.
[23:55:59] <jepler> ok
[23:56:08] <jepler> git.linuxcnc.org at least knows who you are now
[23:56:29] <jepler> in the terminal, got your emc2-dev directory, and: git config remote.origin.url
[23:56:32] <jepler> what's that print?
[23:57:01] <jthornton> git://git.linuxcnc.org/git/emc2.git
[23:57:23] <jepler> OK, that is the url for non-push access
[23:57:40] <jepler> git config remote.origin.url ssh://
[email protected]/git/emc2.git
[23:57:47] <jepler> then try your push again
[23:58:20] <jthornton> ok, it is working
[23:58:25] <jepler> jthornton: by the way, I had a suggestion from a user during the fest
[23:58:32] <jthornton> was the problem that I used a different log in name
[23:58:46] <jthornton> on this computer
[23:59:04] <jepler> in the table of contents there are often abbreviations like "pyVCP". It would be nice if the acronym was expanded in the table of contents
[23:59:06] <CIA-2> EMC: 03jthornton 07master * r74fcfbe4b3f6 10/src/hal/components/time.comp: converts seconds to hrs, min, seconds
[23:59:46] <jthornton> ! [rejected] v2.4_branch -> v2.4_branch (non-fast-forward)
[23:59:48] <jthornton> error: failed to push some refs to 'ssh://
[email protected]/git/emc2.git'
[23:59:49] <jepler> .. the difficulty is coming up with a short phrase that will help the user understand what a pyvcp or halui is