It's a shame you think there are "parallel port zealots". The parallel
port is just one of the interfaces that linuxcnc supports. Still a quite
viable as an entry level interface or a "quick & dirty" one. A lot of us
have gone with the various motion cards from MESA.
And Murphy', Law....no that's an ancient law thought up by the Bards &
Druids of old. Twas used to describe a particularly bad battle of the
clan Murchadh against the Danes. I would take this with a dram of whisky
as it may or may not be true*.*
A modified Slackware build script to produce a Slackware-type package
was really helpful when building a LFS & BLFS system.
On 5/3/20 5:00 am, Rafael Skodlar wrote:
On 2020-02-19 00:11, Robert Murphy wrote:
On 19/2/20 5:47 pm, Rafael Skodlar wrote:
On 2020-02-17 04:49, Les Newell wrote:
One issue jumps to mind that is different. The tiny shop I have
doesn't have room for a Keyboard, Mouse and Display by the lathe. I
currently have a nice work triangle set up for the lathe toolbench
and tool cabinet. It would require a lot of work to change that at
a cost of space lost somewhere else.
Monitor on the wall behind the lathe? Support arm bolted to the wall
for the keyboard? If you wanted these things you'd make room. As you
don't want them you won't make the room. I'm not saying that's a bad
thing. We just have different requirements.
..... snip
/opt/linuxcnc-v2.8/bin
/opt/linuxcnc-v2.8/etc
/opt/linuxcnc-v2.8/lib
/opt/linuxcnc-v2.8/man
/opt/linuxcnc-v2.8/log
Latest release would be:
/opt/linuxcnc -> link to /opt/linuxcnc-v2.8.
Your path to LinuxCNC binaries or scripts would always be
/opt/linuxcnc/bin etc.
Dunno why you are calling that the "Slackware Method" and I've been
running a 24/7 Slackware server for years. Never in all my years I have
seen that method used in Slackware or mentioned in the docs. Actually I
can't recall any official Slackware packages installing into /opt and
linking as you say. Have you used Slackware ?
That's the first one I used. Before Yggdrasil, Redhat, Mandrake,
Xandros, and Debian.
Don't take everything so literally. I was just giving an example for
files locations. Ubuntu uses /srv a lot. Put application wherever you
want, /usr/local for what I care. What I wanted to point out is
simplicity in managing multiple versions of some application or service.
https://www.slackbook.org/html/package-management.html
"Packages are built to be extracted in the root directory" which makes
it easier to put them under chrooted directory.
"Apparently many people in the Linux community think that a packager
manager must by definition include dependency checking. Well, that
simply isn't the case, as Slackware most certainly does not."
that means it won't mess with other packages (dependencies) as many
_standard package utilities_ do. Sometimes that's good, other times
it's not.
You obviously did not read this:
http://www.slackware.com/config/packages.php
"Slackware's packaging system uses ordinary compressed tar files."
and that's what I was reffering to. Read the docs before you tell
somebody else !!!
Puppy Linux and Salix use a "Plug in" file system for apps. But usually
a squashfs file system that can be loaded on boot.
If you read the Linuxcnc docs you'd be aware of a Run In Place install.
Which is the recommended method before a full upgrade.
I'm beginning to think you don't know too much about Linuxcnc and are
trying a push it something that suits your needs or business model.
Is that a Murphy law? I'm glad to see you know everything and how
things should be. I observe trends in the industry and point them out
to parallel port zealots. Opening discussion for software architecture
is not automatic _business model_.
As a sysadmin I've seen volumes of good and bad software that's hard
to maintain or fix in some cases. I'm not saying LinuxCNC is this or
that. It's great what people have done with it so far. A lot of work
is ahead since Python 2.7 reached it's end of life.
Since you know so much, tell me what's going on here:
file emc2-dev/src/emc/motion/teleop-notes has a reference to
http://jmkasunich.com/pics/emc2-motion-dataflow.pdf
How many more such things are there?
Now go learn about hard and soft links, PATH, and chroot in Unix.
Why not do your own crowd funding, fork Linuxcnc and pay for someone to
break it up and rearrange it to suit your needs.
That's because I don't have more money than you do.
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
