Re: eagle-lin64-7.5.0.run, won't

On Sun, Jan 17, 2016 at 05:19:34PM -0500, Gene Heskett wrote: > > I hadn't thought of that. My bad. OTOH, although no one has come thru > the router except to view my web page, do I really want to do that in > the event they do get thru? That could make their raising a little hell > just

Re: eagle-lin64-7.5.0.run, won't

On Tuesday 19 January 2016 09:59:23 Chris Bannister wrote: > On Sun, Jan 17, 2016 at 05:19:34PM -0500, Gene Heskett wrote: > > I hadn't thought of that. My bad. OTOH, although no one has come thru > > the router except to view my web page, do I really want to do that in > > the event they do get

Re: eagle-lin64-7.5.0.run, won't

On Tue, Jan 19, 2016 at 11:38:11AM +, Lisi Reisz wrote: On Tuesday 19 January 2016 09:59:23 Chris Bannister wrote: On Sun, Jan 17, 2016 at 05:19:34PM -0500, Gene Heskett wrote: > I hadn't thought of that. My bad. OTOH, although no one has come thru > the router except to view my web page,

Re: eagle-lin64-7.5.0.run, won't

On 1/19/16, Chris Bannister wrote: > On Sun, Jan 17, 2016 at 05:19:34PM -0500, Gene Heskett wrote: >> >> I hadn't thought of that. My bad. OTOH, although no one has come thru >> the router except to view my web page, do I really want to do that in >> the event they do

Re: eagle-lin64-7.5.0.run, won't

On Tuesday 19 January 2016 07:54:30 Cindy-Sue Causey wrote: > On 1/19/16, Chris Bannister wrote: > > On Sun, Jan 17, 2016 at 05:19:34PM -0500, Gene Heskett wrote: > >> I hadn't thought of that. My bad. OTOH, although no one has come > >> thru the router except to

Re: eagle-lin64-7.5.0.run, won't

On Tuesday 19 January 2016 08:00:12 Darac Marjal wrote: > On Tue, Jan 19, 2016 at 11:38:11AM +, Lisi Reisz wrote: > >On Tuesday 19 January 2016 09:59:23 Chris Bannister wrote: > >> On Sun, Jan 17, 2016 at 05:19:34PM -0500, Gene Heskett wrote: > >> > I hadn't thought of that. My bad. OTOH,

Re: eagle-lin64-7.5.0.run, won't

On Tue, Jan 19, 2016 at 11:38:11AM +, Lisi Reisz wrote: > On Tuesday 19 January 2016 09:59:23 Chris Bannister wrote: > > On Sun, Jan 17, 2016 at 05:19:34PM -0500, Gene Heskett wrote: > > > I hadn't thought of that. My bad. OTOH, although no one has come thru > > > the router except to view my

Re: eagle-lin64-7.5.0.run, won't

On Sunday 17 January 2016 22:19:34 Gene Heskett wrote: > On Sunday 17 January 2016 09:14:33 Chris Bannister wrote: > > I think you'll find the 'tail' command is in your path, in this > > instance. > > tail is the program, not the argument.  The argument of course is the > list of options between

Re: eagle-lin64-7.5.0.run, won't

On Sunday 17 January 2016 09:46:36 Joe wrote: > On Sat, 16 Jan 2016 20:28:50 -0500 > > Gene Heskett wrote: > > Bugs in the gcode exporter are my main beefs. In the gcode output > > for bottom.ngc, with spot drilling enabled, it outputs a line for > > each of the holes, but

Re: eagle-lin64-7.5.0.run, won't

On Sunday 17 January 2016 22:21:38 Gene Heskett wrote: > On Sunday 17 January 2016 09:46:36 Joe wrote: > > On Sat, 16 Jan 2016 20:28:50 -0500 > > > > Gene Heskett wrote: > > > Bugs in the gcode exporter are my main beefs. In the gcode output > > > for bottom.ngc, with spot

Re: eagle-lin64-7.5.0.run, won't

On Sunday 17 January 2016 09:14:33 Chris Bannister wrote: > On Sat, Jan 16, 2016 at 12:28:32PM -0500, Gene Heskett wrote: > > On Saturday 16 January 2016 10:57:55 Curt wrote: > > > On 2016-01-16, Gene Heskett wrote: > > > >> So its full path is

Re: eagle-lin64-7.5.0.run, won't

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Jan 16, 2016 at 09:45:58AM -0700, Brandon Vincent wrote: > On Sat, Jan 16, 2016 at 9:42 AM, Curt wrote: > > Thank you for your time. Just another misapprehension I've been laboring > > under these many years. > > I actually

Re: eagle-lin64-7.5.0.run, won't

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, Jan 16, 2016 at 10:42:25PM +, Lisi Reisz wrote: > On Saturday 16 January 2016 17:28:32 Gene Heskett wrote: > > somebody forgot to tell my mostly wheezy system. > [snip] > > this system with many years of cruft accumulated. > > And it

Re: eagle-lin64-7.5.0.run, won't

On Sunday 17 January 2016 12:33:40 to...@tuxteam.de wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Sat, Jan 16, 2016 at 10:42:25PM +, Lisi Reisz wrote: > > On Saturday 16 January 2016 17:28:32 Gene Heskett wrote: > > > somebody forgot to tell my mostly wheezy system. > > > >

Re: eagle-lin64-7.5.0.run, won't

On Sat, Jan 16, 2016 at 12:28:32PM -0500, Gene Heskett wrote: > On Saturday 16 January 2016 10:57:55 Curt wrote: > > > On 2016-01-16, Gene Heskett wrote: > > >> So its full path is /home/gene/eagle-7.5.0/bin/eagle, not > > >> /bin/eagle? > > >> > > >> Lisi > > > > > > I was

Re: eagle-lin64-7.5.0.run, won't

On Sat, 16 Jan 2016 20:28:50 -0500 Gene Heskett wrote: > > > Bugs in the gcode exporter are my main beefs. In the gcode output for > bottom.ngc, with spot drilling enabled, it outputs a line for each of > the holes, but fills the first 6 of those lines with X0 Y0, so

Re: eagle-lin64-7.5.0.run, won't

On Saturday 16 January 2016 06:06:48 Gene Heskett wrote: > > > shows in that shells env report, but it can't find its executable > > > with both hands, prefering to give me a > > > gene@coyote:~/eagle-7.5.0$ bin/eagle > > > bash: bin/eagle: No such file or directory > > > > > > Clues? I'm confused

Re: eagle-lin64-7.5.0.run, won't

On Sat, Jan 16, 2016 at 3:49 AM, Gene Heskett wrote: > I was cd'd to /home/gene/eagle-7.5.0 and the command issued was > bin/eagle, which is perfectly legal syntax. Gene, Could you post the output of ldd /home/gene/eagle-7.5.0 for us to see? Brandon Vincent

Re: eagle-lin64-7.5.0.run, won't

On Saturday 16 January 2016 05:05:22 Lisi Reisz wrote: > On Saturday 16 January 2016 06:06:48 Gene Heskett wrote: > > > > shows in that shells env report, but it can't find its > > > > executable with both hands, prefering to give me a > > > > gene@coyote:~/eagle-7.5.0$ bin/eagle > > > > bash:

Re: eagle-lin64-7.5.0.run, won't

On Saturday 16 January 2016 19:41:45 Joe wrote: > On Sat, 16 Jan 2016 12:13:14 -0500 > > Gene Heskett wrote: > > But as I said in a PM, its moot, gEDA has come to the rescue. > > > > Now, if ALL the gEDA suite was brought up to date, the repo versions > > are positively

Re: eagle-lin64-7.5.0.run, won't

On Saturday 16 January 2016 17:42:25 Lisi Reisz wrote: > On Saturday 16 January 2016 17:28:32 Gene Heskett wrote: > > somebody forgot to tell my mostly wheezy system. > > [snip] > > > this system with many years of cruft accumulated. > > And it doesn't run like an entirely Wheezy system with no

Re: eagle-lin64-7.5.0.run, won't

On Sat 16 Jan 2016 at 12:28:32 (-0500), Gene Heskett wrote: > On Saturday 16 January 2016 10:57:55 Curt wrote: > > > On 2016-01-16, Gene Heskett wrote: > > >> So its full path is /home/gene/eagle-7.5.0/bin/eagle, not > > >> /bin/eagle? > > >> > > >> Lisi > > > > > > I was

Re: eagle-lin64-7.5.0.run, won't

On 2016-01-16, Brandon Vincent wrote: > On Sat, Jan 16, 2016 at 9:14 AM, Curt wrote: >> I don't see what you're referring to in there. > > Eagle installs itself into your home directory under a folder called > "eagle-7.5.0". Inside this folder is the "bin"

Re: eagle-lin64-7.5.0.run, won't

On 2016-01-16, Brandon Vincent wrote: > On Sat, Jan 16, 2016 at 8:57 AM, Curt wrote: >> Not if bin is not in your path it isn't. > > You should probably read [1]. > > It is legal syntax. > [1] http://mywiki.wooledge.org/BashFAQ/028 I don't see what

Re: eagle-lin64-7.5.0.run, won't

On Sat, Jan 16, 2016 at 8:57 AM, Curt wrote: > Not if bin is not in your path it isn't. You should probably read [1]. It is legal syntax. [1] http://mywiki.wooledge.org/BashFAQ/028 Brandon Vincent

Re: eagle-lin64-7.5.0.run, won't

On Sat, Jan 16, 2016 at 9:14 AM, Curt wrote: > I don't see what you're referring to in there. Eagle installs itself into your home directory under a folder called "eagle-7.5.0". Inside this folder is the "bin" folder in which the Eagle executable is stored. If you are in the

Re: eagle-lin64-7.5.0.run, won't

On Saturday 16 January 2016 17:28:32 Gene Heskett wrote: > somebody forgot to tell my mostly wheezy system. [snip] > this system with many years of cruft accumulated. And it doesn't run like an entirely Wheezy system with no cruft. Now there's a surprise! Lisi

Re: eagle-lin64-7.5.0.run, won't

On Sat, 16 Jan 2016 12:13:14 -0500 Gene Heskett wrote: > > But as I said in a PM, its moot, gEDA has come to the rescue. > > Now, if ALL the gEDA suite was brought up to date, the repo versions > are positively ancient, I think it would have been easier. I was able > to

Re: eagle-lin64-7.5.0.run, won't

On Sunday 17 January 2016 01:11:04 Gene Heskett wrote: > FWIW I just reinstalled apt and all its kinfolks, no change, so I > installed adept, which didn't work, stuck in refresh forever, except it > wasn't, the file menu was still active, but several attempts to manage > the repos were ignored,

Re: eagle-lin64-7.5.0.run, won't

On Saturday 16 January 2016 22:22:34 David Wright wrote: > On Sat 16 Jan 2016 at 12:28:32 (-0500), Gene Heskett wrote: > > On Saturday 16 January 2016 10:57:55 Curt wrote: > > > On 2016-01-16, Gene Heskett wrote: > > > >> So its full path is

Re: eagle-lin64-7.5.0.run, won't

On 2016-01-16, Gene Heskett wrote: >> >> So its full path is /home/gene/eagle-7.5.0/bin/eagle, not /bin/eagle? >> >> Lisi > > I was cd'd to /home/gene/eagle-7.5.0 and the command issued was > bin/eagle, which is perfectly legal syntax. Not if bin is not in your path it

Re: eagle-lin64-7.5.0.run, won't

On Sat, Jan 16, 2016 at 9:42 AM, Curt wrote: > Thank you for your time. Just another misapprehension I've been laboring > under these many years. I actually linked to the wrong article. I've never been able to find actual Bash documentation that states this. It just has always

Re: eagle-lin64-7.5.0.run, won't

On Saturday 16 January 2016 08:06:25 Brandon Vincent wrote: > On Sat, Jan 16, 2016 at 3:49 AM, Gene Heskett wrote: > > I was cd'd to /home/gene/eagle-7.5.0 and the command issued was > > bin/eagle, which is perfectly legal syntax. > > Gene, > > Could you post the output of

Re: eagle-lin64-7.5.0.run, won't

On Saturday 16 January 2016 10:57:55 Curt wrote: > On 2016-01-16, Gene Heskett wrote: > >> So its full path is /home/gene/eagle-7.5.0/bin/eagle, not > >> /bin/eagle? > >> > >> Lisi > > > > I was cd'd to /home/gene/eagle-7.5.0 and the command issued was > > bin/eagle, which

Re: eagle-lin64-7.5.0.run, won't

On Saturday 16 January 2016 11:45:58 Brandon Vincent wrote: > On Sat, Jan 16, 2016 at 9:42 AM, Curt wrote: > > Thank you for your time. Just another misapprehension I've been > > laboring under these many years. > > I actually linked to the wrong article. I've never been able to

Re: eagle-lin64-7.5.0.run, won't

On Friday 15 January 2016 23:35:53 Chris Bannister wrote: > On Thu, Jan 14, 2016 at 06:37:49PM -0500, Gene Heskett wrote: > > Greetings all; > > > > Since the gEDA kit in the repo's seems to be rather broken, I > > thought I'd give eagle another chance, so I downloaded, from the > > cadsoft site,

Re: eagle-lin64-7.5.0.run, won't

On Thu, Jan 14, 2016 at 06:37:49PM -0500, Gene Heskett wrote: > Greetings all; > > Since the gEDA kit in the repo's seems to be rather broken, I thought I'd > give eagle another chance, so I downloaded, from the cadsoft site, the > latest 64 bit linux installer, but can't find a help file, and

Re: eagle-lin64-7.5.0.run, won't

On Thursday 14 January 2016 19:38:34 Brandon Vincent wrote: > On Thu, Jan 14, 2016 at 4:37 PM, Gene Heskett wrote: > > Has anyone else had any luck, running it after convincing the > > installer where you wanted it installed? > > I just tried installing Eagle manually and

Re: eagle-lin64-7.5.0.run, won't

On Thu, Jan 14, 2016 at 4:37 PM, Gene Heskett wrote: > Has anyone else had any luck, running it after convincing the installer > where you wanted it installed? I just tried installing Eagle manually and had no problems on a clean install of Debian 8. Is your Debian install

eagle-lin64-7.5.0.run, won't

Greetings all; Since the gEDA kit in the repo's seems to be rather broken, I thought I'd give eagle another chance, so I downloaded, from the cadsoft site, the latest 64 bit linux installer, but can't find a help file, and obviously I am not training my monkeys correctly. Has anyone else had

Re: eagle-lin64-7.5.0.run, won't

On Friday 15 January 2016 00:06:51 Anders Andersson wrote: > On Fri, Jan 15, 2016 at 12:37 AM, Gene Heskett wrote: > > Since the gEDA kit in the repo's seems to be rather broken, I > > thought I'd give eagle another chance > > While I had no problems using Eagle on 64-bit

Re: eagle-lin64-7.5.0.run, won't

On Fri, Jan 15, 2016 at 12:37 AM, Gene Heskett wrote: > Since the gEDA kit in the repo's seems to be rather broken, I thought I'd > give eagle another chance While I had no problems using Eagle on 64-bit Debian, I did not like running closed software. A couple of months ago