Are there simple line-powered MP3 recorders?

[Joel Koltner]

Phil,

"Phil Hobbs" <pcdhSpamMeSenseless@electrooptical.net> wrote in message
news:491265C6.3070901@electrooptical.net...

I have much worse problems with Windows in this regard. In Linux, I can
always say 'sudo' and do whatever I need to, whereas the Windows security
model is complicated and (to me) almost entirely opaque.

I work around this problem by having a small batch file that just starts a
Windows command prompt running as administrator, using the freeware program
"cpau" (http://www.joeware.net/freetools/tools/cpau/index.htm). (It prompts
from a password, spits out an error if CPAU doesn't like it, otherwise fires
up the command prompt with a solid red background to remind me that I should
think twice before typing in del *.*).

---Joel

 

[Phil Hobbs]

Joel Koltner wrote:

Phil,

"Phil Hobbs" <pcdhSpamMeSenseless@electrooptical.net> wrote in message
news:491265C6.3070901@electrooptical.net...
I have much worse problems with Windows in this regard. In Linux, I can
always say 'sudo' and do whatever I need to, whereas the Windows security
model is complicated and (to me) almost entirely opaque.

I work around this problem by having a small batch file that just starts a
Windows command prompt running as administrator, using the freeware program
"cpau" (http://www.joeware.net/freetools/tools/cpau/index.htm). (It prompts
from a password, spits out an error if CPAU doesn't like it, otherwise fires
up the command prompt with a solid red background to remind me that I should
think twice before typing in del *.*).

---Joel


That looks interesting. However, there are things in a Windows system

that even the administrator can't touch. Try deleting a file called
'LPT1' for instance. Or creating a directory with Cygwin and trying to
delete it from the Windows command line.

I like computers that do what they're bloody well told.

Cheers,

Phil Hobbs

 

[JosephKK]

On Thu, 06 Nov 2008 16:30:09 -0500, Phil Hobbs
<pcdhSpamMeSenseless@electrooptical.net> wrote:

Joel Koltner wrote:
Phil,

"Phil Hobbs" <pcdhSpamMeSenseless@electrooptical.net> wrote in message
news:491265C6.3070901@electrooptical.net...
I have much worse problems with Windows in this regard. In Linux, I can
always say 'sudo' and do whatever I need to, whereas the Windows security
model is complicated and (to me) almost entirely opaque.

I work around this problem by having a small batch file that just starts a
Windows command prompt running as administrator, using the freeware program
"cpau" (http://www.joeware.net/freetools/tools/cpau/index.htm). (It prompts
from a password, spits out an error if CPAU doesn't like it, otherwise fires
up the command prompt with a solid red background to remind me that I should
think twice before typing in del *.*).

---Joel


That looks interesting. However, there are things in a Windows system
that even the administrator can't touch. Try deleting a file called
'LPT1' for instance. Or creating a directory with Cygwin and trying to
delete it from the Windows command line.

I like computers that do what they're bloody well told.

Cheers,

Phil Hobbs

Me too. That is why i use Linux. Of course understanding how to set
up the permissions is part of the issue.

 

[Joerg]

JosephKK wrote:

On Tue, 04 Nov 2008 16:05:29 -0800, Joerg
notthisjoergsch@removethispacbell.net> wrote:

Rich Grise wrote:
On Tue, 04 Nov 2008 12:52:14 -0800, Joerg wrote:
Joel Koltner wrote:
"Joerg" <notthisjoergsch@removethispacbell.net> wrote in message
news:lS0Qk.3807$hc1.2980@flpi150.ffdc.sbc.com...
Well, we just ordered a top-of-the-line Marantz recorder. Even easier:
Plug it in, turn it on, press "REC" -> works.
When can we expect to hear the results of the new recorder on the web
site?


A few weeks maybe. Some wiring will have to be re-done and I as well as
our IT pro must to do that after work. Also, the old rack needs to be
re-built and so on. Not exactly a piece of cake.
Maybe not, but think of the satisfaction you'll get from a job well done.



This is at church so we aren't after worldly recognition or self-pride

So where did the money come from for the top of the line Marantz?

Like everything else there, free-will donations. Some items are bought
and then donated directly, such as a very nice grand piano. In that case
the donor wished to remain anonymous which is very common in Lutheran
congregations. Even after he or she passes away nobody will be told.

--
Regards, Joerg

http://www.analogconsultants.com/

"gmail" domain blocked because of excessive spam.
Use another domain or send PM.

 

[Joerg]

Phil Hobbs wrote:

Joerg wrote:
Joel Koltner wrote:
"Joerg" <notthisjoergsch@removethispacbell.net> wrote in message
news:LLrQk.6961$be.6214@nlpi061.nbdc.sbc.com...
So, now I did try KiCad and I must say I like it a lot.

Cool, thanks for the update/review.

Someone even wrote a converter for Eagle schematics but that blew up
on me.


Another upside is it's Windows-based so you don't have that dreaded
"you are not authorized to write to this folder" behavior of Linux.
Meaning I can place my libs where they belong, in the lib directory.

I have much worse problems with Windows in this regard. In Linux, I can
always say 'sudo' and do whatever I need to, whereas the Windows
security model is complicated and (to me) almost entirely opaque.
Unix-style OSes are good at doing what they're told--they know that root
is The Boss.

I've learned about bash and sudo by now. But with CAD systems this
really gets in the way. Libraries whether supplied with the SW,
acquired, or self-created all ought to be under the same "Lib"
subdirectory. In Linux you cannot do that. You could theoretically copy
them all into /home/phil/geda/lib but then you cannot start the program
from the usual GUI interface anymore. Because it would then not see
those libraries. Honestly, that doesn't make much sense to me.

--
Regards, Joerg

http://www.analogconsultants.com/

"gmail" domain blocked because of excessive spam.
Use another domain or send PM.

 

[Joerg]

Joel Koltner wrote:

"Joerg" <notthisjoergsch@removethispacbell.net> wrote in message
news:m0tQk.3071$8_3.2418@flpi147.ffdc.sbc.com...
Another upside is it's Windows-based so you don't have that dreaded "you are
not authorized to write to this folder" behavior of Linux.

Hey, go join a big company and you can have that problem on Windows too.

Meaning I can place my libs where they belong, in the lib directory.

T'is one reason I never joined a big company

You probably know this, but the Linux philosophy is that you place all "your
own" stuff somewhere in your home directory (e.g., ~joerg) where you do have
full read/write/execute permissions by default... and they figure that if
you're trying to do something "system wide" (e.g., make a /lib), you should
spend the time to "chmod" the result to set the read/write permissions as the
the "system administrator" -- you! -- prefers.

As far as I found out so far (and I may be wrong here) that change does
not stick. A half hour later you open a file from the GUI and decide you
need a new model for a super gizmo mux chip. Then bam, "You do not have
permission to write ...".

The file system is something I seriously do not like about Linux. I just
do not like to be second-guessed by some software. Other than that it
seems a pretty nice OS so far.

I'll try that again if I have my custom libs converted. Problem is: Every
schematic editor names files *.sch. So it's hard to decipher which file was
from which CAD system. Only if you go by date, and even then sometimes not
because you may have to massage an old file with the old CAD.

Agreed, that is a bit of a pain. If you open up the files in a text editor
(possibly set to binary mode), is it readily obvious where each file came
from? If so, it wouldn't be too difficult to write a small script to loop
through the files, take a look inside, and then rename them as, e.g.,
*.eagle_sch or *.kicad_sch or whatever.

Oh, I can do that by hand. But many of those files are on customer
servers now and I often have to deal with them there. Else you could
just auto-open them all and mod according to where no error window pops up.

SI-Metrix names schematics something like *.sxsh (more-than-three-letters
extension), but unfortunately the old DOS three-letter limitation seems like
it's never going to go away with most software.

Yep, DOS has had the most profound effect on personal computing.

--
Regards, Joerg

http://www.analogconsultants.com/

"gmail" domain blocked because of excessive spam.
Use another domain or send PM.

 

[Joerg]

JosephKK wrote:

On Tue, 04 Nov 2008 12:54:10 -0800, Joerg
notthisjoergsch@removethispacbell.net> wrote:

Jan Panteltje wrote:
On a sunny day (Tue, 04 Nov 2008 10:52:56 -0800) it happened Joerg
notthisjoergsch@removethispacbell.net> wrote in
lS0Qk.3807$hc1.2980@flpi150.ffdc.sbc.com>:

This is becoming the obvious embedded RTLinux PC project. Select your
PC104 form factor stuff, stir in the right Linux stuff and boom, it
just works.

Well, we just ordered a top-of-the-line Marantz recorder. Even easier:
Plug it in, turn it on, press "REC" -> works.
Yes, but where is the challenge?

Right now I don't need any more challenges

Besides a few client projects I am trying to migrate to gEDA. Got it
running but the symbol editing turns out to be a real bear. Plus
learning all the Linux-speak.

You are in exactly the right place to help me. I have yet to get gEDA
running enough to even begin schematic entry. How did you do it? On
what underlying variant? Oh hell, you can read headers, talk to me.

Well, first I made the decision that I will absolutely not have a dual
boot system because that all but kills productivity. So I got Sun
VirtualBox. Then I downloaded Ubuntu, installed it as a virtual machine
on this new VirtualBox. Installing applications such as gschem and PCB
Designer is a breeze in Linux. You go to a package manager (I used
Synaptics) look around what's there and check the boxes of the stuff you
want. Then click install and have a coffee. After that I was in business.

Then, while drawing some mock schematics I found out the limitations in
gEDA and they are so serious for an analog guy like me that I will
probably select KiCad as my next CAD system. But that decision isn't
final just yet. Mostly the issues have to do with things like explicit
power symbols and designator re-numbering. Yeah, there are workarounds
for some of these issues but most require to close the schematic, go to
the terminal, do stuff on the command line, then re-open gschem, re-load
the schematic. So things that take five seconds with my current CAD now
take minutes. Other issues seem to only be fixable if I use what SW pros
call a "fork". I just learned that from the gEDA NG, it means you would
now be using a version that will not necessarily remain compatible with
the main program that almost everyone else is using. That isn't quite
what I had in mind for a new CAD system.

The plus side of gEDA is a stellar support and help, and friendly people
in the newsgroup. Also lots of helper applications. And when you look
for one in the package manager just scrolling through all that Linux SW
out there can make you drool. There is a ton of good stuff.

BTW, once you get it loaded open up someone elses schematic and play
around in it. For me that is usually the best way to learn the ropes.

--
Regards, Joerg

http://www.analogconsultants.com/

"gmail" domain blocked because of excessive spam.
Use another domain or send PM.

 

[Jan Panteltje]

On a sunny day (Fri, 07 Nov 2008 15:23:32 -0800) it happened Joerg
<notthisjoergsch@removethispacbell.net> wrote in
<w24Rk.5018$D32.3407@flpi146.ffdc.sbc.com>:

I've learned about bash and sudo by now. But with CAD systems this
really gets in the way. Libraries whether supplied with the SW,
acquired, or self-created all ought to be under the same "Lib"
subdirectory. In Linux you cannot do that. You could theoretically copy
them all into /home/phil/geda/lib but then you cannot start the program
from the usual GUI interface anymore. Because it would then not see
those libraries. Honestly, that doesn't make much sense to me.

I am not sure, but I think that is not correct.
man chown

for example if there is a user joerg, then, as root you can do:

mkdir mylibs

ls -ld mylibs
drwxr-xr-x 2 root root 48 2008-11-08 00:42 mylibs/

Change the owner, and group now you program should see it:
chown joerg:joerg mylibs
drwxr-xr-x 2 joerg joerg 48 2008-11-08 00:42 mylibs/

That directory can be anywhere.

Or
chown joerg:users
drwxr-xr-x 2 joerg users 48 2008-11-08 00:42 mylibs/

 

[Joerg]

JosephKK wrote:

On Tue, 04 Nov 2008 10:52:56 -0800, Joerg
notthisjoergsch@removethispacbell.net> wrote:

JosephKK wrote:
On Mon, 27 Oct 2008 09:26:29 -0700, Joerg
notthisjoergsch@removethispacbell.net> wrote:

Charlie E. wrote:
On Sun, 26 Oct 2008 14:31:21 -0700, Joerg
notthisjoergsch@removethispacbell.net> wrote:

For our church we are looking for mains-powered (no batteries) MP3
recorders that can record up to 1.5hrs, preferably onto a USB stick. As
simple as possible, like on/off, record, stop.

I have looked around the web and only found gear from Roland which had
mixing functions and stuff that makes it too complicated, or Intempo
which is more geared towards recording from radio channels and would
probably need some hack to connect to our mixer. If this costs a few
hundred Dollars that's ok but it cannot be complicated with teeny LCD
screens and menus. In essence I'd have to be able to call someone and
say "Turns this dark gray gizmo in the left corner on and hit the red
record button", not explain a lengthy menu tree where they need a
magnifier just to see it.

IOW what we need is a cassette recorder sans cassettes, that records
onto USB. Any ideas?
Jeorge,
We used a pro gear Tascam recorder for our last project, but it used
compact flash, not USB flash, and is in the $900 range. I like your
idea, though, and would like to buy it as well. Maybe it is time to
design one!

Do you remember the Tascam model? Flash isn't ideal but a lot better
than CD or having to plug the whole device into a PC. That is because a
church member does the spooling onto the web from home and would then
have to drive back to church to return the unit.
This is becoming the obvious embedded RTLinux PC project. Select your
PC104 form factor stuff, stir in the right Linux stuff and boom, it
just works.

Well, we just ordered a top-of-the-line Marantz recorder. Even easier:
Plug it in, turn it on, press "REC" -> works.

And i had thought that Marantz had gone out of business long ago.
Maybe this is a "logo / brand name" resurrection.

It could be, but a serious audio professional from Germany recommended
three models and this was one of them. For a church the fact that it can
be completely configured from remote and that you can download
recordings the same way is a huge upside. Certainly in our case because
our IT guru lives way out in the boonies.

--
Regards, Joerg

http://www.analogconsultants.com/

"gmail" domain blocked because of excessive spam.
Use another domain or send PM.

 

[Joerg]

Jan Panteltje wrote:

On a sunny day (Fri, 07 Nov 2008 15:23:32 -0800) it happened Joerg
notthisjoergsch@removethispacbell.net> wrote in
w24Rk.5018$D32.3407@flpi146.ffdc.sbc.com>:

I've learned about bash and sudo by now. But with CAD systems this
really gets in the way. Libraries whether supplied with the SW,
acquired, or self-created all ought to be under the same "Lib"
subdirectory. In Linux you cannot do that. You could theoretically copy
them all into /home/phil/geda/lib but then you cannot start the program
from the usual GUI interface anymore. Because it would then not see
those libraries. Honestly, that doesn't make much sense to me.

I am not sure, but I think that is not correct.
man chown

for example if there is a user joerg, then, as root you can do:

mkdir mylibs

ls -ld mylibs
drwxr-xr-x 2 root root 48 2008-11-08 00:42 mylibs/

Change the owner, and group now you program should see it:
chown joerg:joerg mylibs
drwxr-xr-x 2 joerg joerg 48 2008-11-08 00:42 mylibs/

That directory can be anywhere.

Or
chown joerg:users
drwxr-xr-x 2 joerg users 48 2008-11-08 00:42 mylibs/

Anywhere, as in anywhere but root. At least that's what people told me.
This means you now need to start stuff like gschem from the new
directory where the libs are, by command line. Because it will otherwise
not see its gafrc and thus not load your libraries.

This is so much easier in Windows SW. You don't need to do anything,
just start to create your own libraries and remain disciplined enough
not to mess with original libraries. I've had that discipline for over
20 years now

--
Regards, Joerg

http://www.analogconsultants.com/

"gmail" domain blocked because of excessive spam.
Use another domain or send PM.

 

[Jan Panteltje]

On a sunny day (Fri, 07 Nov 2008 15:53:41 -0800) it happened Joerg
<notthisjoergsch@removethispacbell.net> wrote in
<my4Rk.8480$Ws1.3503@nlpi064.nbdc.sbc.com>:

Anywhere, as in anywhere but root. At least that's what people told me.
This means you now need to start stuff like gschem from the new
directory where the libs are, by command line. Because it will otherwise
not see its gafrc and thus not load your libraries.

Script, put this in /usr/local/sbin/mygschem

cd whereveritis
gschem


make it executable:
chmod +x /usr/local/sbin/mygschem

now link your GUI or whatever so the icon starts
mygschem

That is how I run all the win stuff like swcad


grml: ~ # cat /usr/local/sbin/swcad
cd "/root/.wine/drive_c/Program Files/LTC/SwCADIII/"
wine scad3.exe
grml: ~ #


So all I have to to is type swcad.
You could add an icon too, but I mostly use rxvt (sort of an xterm).

You may need to add 'sudo' before those commands.

Anyways I am always root
Some people are scared of that...

 

[Joerg]

Jan Panteltje wrote:

On a sunny day (Fri, 07 Nov 2008 15:53:41 -0800) it happened Joerg
notthisjoergsch@removethispacbell.net> wrote in
my4Rk.8480$Ws1.3503@nlpi064.nbdc.sbc.com>:

Anywhere, as in anywhere but root. At least that's what people told me.
This means you now need to start stuff like gschem from the new
directory where the libs are, by command line. Because it will otherwise
not see its gafrc and thus not load your libraries.

Script, put this in /usr/local/sbin/mygschem

cd whereveritis
gschem


make it executable:
chmod +x /usr/local/sbin/mygschem

now link your GUI or whatever so the icon starts
mygschem

Ok, yes, I could make a GUI icon. So far I've always started aps from
the "Applications" Pulldown Menu in Ubuntu.

That is how I run all the win stuff like swcad


grml: ~ # cat /usr/local/sbin/swcad
cd "/root/.wine/drive_c/Program Files/LTC/SwCADIII/"
wine scad3.exe
grml: ~ #


So all I have to to is type swcad.
You could add an icon too, but I mostly use rxvt (sort of an xterm).

You may need to add 'sudo' before those commands.

That's just the thing. Often Linux decides to not let me do stuff unless
sudo is issued. I like things to happen right now, pronto. Well, that's
how we are in America ;-)

Anyways I am always root
Some people are scared of that...

How can you make yourself "always root"? That would solve a lot of problems.

--
Regards, Joerg

http://www.analogconsultants.com/

"gmail" domain blocked because of excessive spam.
Use another domain or send PM.

 

[Phil Hobbs]

Joerg wrote:

Phil Hobbs wrote:
Joerg wrote:
Joel Koltner wrote:
"Joerg" <notthisjoergsch@removethispacbell.net> wrote in message
news:LLrQk.6961$be.6214@nlpi061.nbdc.sbc.com...
So, now I did try KiCad and I must say I like it a lot.

Cool, thanks for the update/review.

Someone even wrote a converter for Eagle schematics but that blew
up on me.


Another upside is it's Windows-based so you don't have that dreaded
"you are not authorized to write to this folder" behavior of Linux.
Meaning I can place my libs where they belong, in the lib directory.

I have much worse problems with Windows in this regard. In Linux, I
can always say 'sudo' and do whatever I need to, whereas the Windows
security model is complicated and (to me) almost entirely opaque.
Unix-style OSes are good at doing what they're told--they know that
root is The Boss.


I've learned about bash and sudo by now. But with CAD systems this
really gets in the way. Libraries whether supplied with the SW,
acquired, or self-created all ought to be under the same "Lib"
subdirectory. In Linux you cannot do that. You could theoretically copy
them all into /home/phil/geda/lib but then you cannot start the program
from the usual GUI interface anymore. Because it would then not see
those libraries. Honestly, that doesn't make much sense to me.

You mean shared libraries (.so) or component libraries?

The usual methods are to make symbolic links from wherever the library
is really to the /usr/lib directory (or someplace similar, e.g.
/usr/local/lib), to use the LD_LIBRARY_PATH environment variable (works
like PATH in Windows or LIBPATH in OS/2). There's another method that's
cleaner but I can never remember.

Cheers,

Phil Hobbs

 

[Jasen Betts]

On 2008-11-07, Joerg <notthisjoergsch@removethispacbell.net> wrote:

I've learned about bash and sudo by now. But with CAD systems this
really gets in the way. Libraries whether supplied with the SW,
acquired, or self-created all ought to be under the same "Lib"
subdirectory.

why? that seems like a really bad idea.

In Linux you cannot do that.

sure you can, I can think of atleast three different ways...

run the app with elevated permissions
change the ownership if the lib dir
use a unification filesystem (this works a little like addpath did in dos)

You could theoretically copy

them all into /home/phil/geda/lib but then you cannot start the program
from the usual GUI interface anymore.

most applications allow a personal configuration file where you can
specify that sort of stuff, most GUIs also allow you to make custom
launchers and/or custom menus

Because it would then not see

those libraries. Honestly, that doesn't make much sense to me.

--

Bye.
Jasen

 

[Frank Buss]

Joerg wrote:

How can you make yourself "always root"? That would solve a lot of problems.

You shouldn't do this. But I login as root, too, because I'm developing
Linux drivers, adjusting system files all the time etc., so it is easier
not to sudo all the time.

For KDE, which I like more than Gnome, because it feels more like Windows,
you can configure KDM: change AllowRootLogin in kdmrc. I think for Gnome it
is very easy, too: http://www.google.de/search?hl=de&q=gdm+root+login

--
Frank Buss, fb@frank-buss.de
http://www.frank-buss.de, http://www.it4-systems.de

 

[Joerg]

Frank Buss wrote:

Joerg wrote:

How can you make yourself "always root"? That would solve a lot of problems.

You shouldn't do this. But I login as root, too, because I'm developing
Linux drivers, adjusting system files all the time etc., so it is easier
not to sudo all the time.

With Linux it seems you almost have to because the directory system is a
bit messy. IMHO it is, for example, not a good idea at all to have CAD
linraries split into two directories in very different places.

For KDE, which I like more than Gnome, because it feels more like Windows,
you can configure KDM: change AllowRootLogin in kdmrc. I think for Gnome it
is very easy, too: http://www.google.de/search?hl=de&q=gdm+root+login

Thanks! That ought to fix it. But my Linux is a bit on hold right now
because I found gEDA not to suit my needs as well as KiCad seems to do.
But whether gschem or KiCad I have to say that both are quite reliable.
I really gave both a run lately and none crashed, not once. I can't even
count anymore how often I have crashed OrCad.

--
Regards, Joerg

http://www.analogconsultants.com/

"gmail" domain blocked because of excessive spam.
Use another domain or send PM.

 

[Joerg]

Phil Hobbs wrote:

Joerg wrote:
Phil Hobbs wrote:
Joerg wrote:
Joel Koltner wrote:
"Joerg" <notthisjoergsch@removethispacbell.net> wrote in message
news:LLrQk.6961$be.6214@nlpi061.nbdc.sbc.com...
So, now I did try KiCad and I must say I like it a lot.

Cool, thanks for the update/review.

Someone even wrote a converter for Eagle schematics but that blew
up on me.


Another upside is it's Windows-based so you don't have that dreaded
"you are not authorized to write to this folder" behavior of Linux.
Meaning I can place my libs where they belong, in the lib directory.

I have much worse problems with Windows in this regard. In Linux, I
can always say 'sudo' and do whatever I need to, whereas the Windows
security model is complicated and (to me) almost entirely opaque.
Unix-style OSes are good at doing what they're told--they know that
root is The Boss.


I've learned about bash and sudo by now. But with CAD systems this
really gets in the way. Libraries whether supplied with the SW,
acquired, or self-created all ought to be under the same "Lib"
subdirectory. In Linux you cannot do that. You could theoretically
copy them all into /home/phil/geda/lib but then you cannot start the
program from the usual GUI interface anymore. Because it would then
not see those libraries. Honestly, that doesn't make much sense to me.

You mean shared libraries (.so) or component libraries?

The component libraries.

The usual methods are to make symbolic links from wherever the library
is really to the /usr/lib directory (or someplace similar, e.g.
/usr/local/lib), to use the LD_LIBRARY_PATH environment variable (works
like PATH in Windows or LIBPATH in OS/2). There's another method that's
cleaner but I can never remember.

Ok, I'll have to look into that some more but the folks from the Linux
caucus have said that you can only store non-root and then must
"hand-crank" the app from there. Although Frank just posted a method to
boot as root, then I could write into the real directoey for libraries
just like I did the last 20 years or so. But anyhow, now I finally found
a CAD software that suits me better and it's Windows-based. So I'll take
a sabbatical from Linux

--
Regards, Joerg

http://www.analogconsultants.com/

"gmail" domain blocked because of excessive spam.
Use another domain or send PM.

 

[Joerg]

Jasen Betts wrote:

On 2008-11-07, Joerg <notthisjoergsch@removethispacbell.net> wrote:

I've learned about bash and sudo by now. But with CAD systems this
really gets in the way. Libraries whether supplied with the SW,
acquired, or self-created all ought to be under the same "Lib"
subdirectory.

why? that seems like a really bad idea.

That is how most CAD systems work. I've done that for >20 years now,
with various CAD systems, works like a champ. To me it makes no sense to
have some library parts in the den and some others in a storage locker
at the other side of town.

In Linux you cannot do that.

sure you can, I can think of atleast three different ways...

run the app with elevated permissions
change the ownership if the lib dir
use a unification filesystem (this works a little like addpath did in dos)

Seems I still have to learn. And obviously also not believe all the
tutorials I've read because they said there is no other way but to store
under /home/..., add a gafrc there and start the app from there as well.
Meaning command line. But meantime I have come across several tutorials
in other areas of Linux and virtual machines that were plain wrong. So I
became careful.

You could theoretically copy
them all into /home/phil/geda/lib but then you cannot start the program
from the usual GUI interface anymore.

most applications allow a personal configuration file where you can
specify that sort of stuff, most GUIs also allow you to make custom
launchers and/or custom menus

Not gEDA. If you don't start it from the directory where the custom
library parts are it will not allow you to use such parts because it
fails to see your gafrc file in there.

This is one of the reasons I am testing KiCad now. It has IMHO a more
clear directory structure.

Because it would then not see
those libraries. Honestly, that doesn't make much sense to me.

--
Regards, Joerg

http://www.analogconsultants.com/

"gmail" domain blocked because of excessive spam.
Use another domain or send PM.

 

[Rich Grise]

On Fri, 07 Nov 2008 15:53:41 -0800, Joerg wrote:

This is so much easier in Windows SW. You don't need to do anything, just
start to create your own libraries and remain disciplined enough not to
mess with original libraries. I've had that discipline for over 20 years
now

"Discipline, comrades, iron discipline."
--- George Orwell, "Animal Farm".

But really. To install from source, run configure, then make, then log
out, log in as root, Chdir to the source, run install, then log out and
log in as yourself. It should work then - the installer should make it
available on your GUI menu(s).

And if it's a Redmond^H^H^H^HHat RPM or a Slack package, all you have to
do is run its installer. (in Slackware, that would be installpkg.)

Have Fun!
Rich

 

[Joerg]

Rich Grise wrote:

On Fri, 07 Nov 2008 15:53:41 -0800, Joerg wrote:
This is so much easier in Windows SW. You don't need to do anything, just
start to create your own libraries and remain disciplined enough not to
mess with original libraries. I've had that discipline for over 20 years
now

"Discipline, comrades, iron discipline."
--- George Orwell, "Animal Farm".

But really. To install from source, run configure, then make, then log
out, log in as root, Chdir to the source, run install, then log out and
log in as yourself. It should work then - the installer should make it
available on your GUI menu(s).

Make? You mean re-compile it all? That wouldn't quite be my cuppa tea ;-)

And if it's a Redmond^H^H^H^HHat RPM or a Slack package, all you have to
do is run its installer. (in Slackware, that would be installpkg.)

It's Ubuntu.

--
Regards, Joerg

http://www.analogconsultants.com/

"gmail" domain blocked because of excessive spam.
Use another domain or send PM.