Re: [Emc-developers] Questions about hard coded paths at "./configure" time

[Steffen Möller via Emc-developers]

> Gesendet: Freitag, 25. April 2025 um 14:46
> Von: "andy pugh" <bodge...@gmail.com>
> An: "EMC developers" <emc-developers@lists.sourceforge.net>
> Betreff: Re: [Emc-developers] Questions about hard coded paths at 
> "./configure" time
>
> On Fri, 25 Apr 2025 at 13:13, Bertho Stultiens <l...@vagrearg.org> wrote:
> 
> > And it isn't even used consistently throughout the code base.
> 
> From a parallel conversation:
> 
> "I was thinking about this more and I probably can kind of guess what
> was going on.
> 
> There is usage of lsmod and modprobe and those are "root" binaries. I
> suspect they were trying to ensure the right path to the root binaries
> could be found. This was then copied for other utilities like grep.
> 
> Modern distros should have PATH set correctly for users to be able to
> find binaries. This was an issue on weird non-linux platforms but Linux
> should have been ok even then, certainly now.
> 
> I'd think it could all be simplified."
> 
> I suspect that lsmod and modprobe are only relevant to RTAI builds,
> and I doubt that the Yocto build would ever use RTAI.

The exact specification of paths gives some extra security. For instance you 
can have loads of fun with somethign along

echo "#!/bin/rm -r /" > python3
chmod +x !$
export PATH=.:$PATH

You kind of want to know exactly what is executed, especially while training 
some small horde of giggling teenagers and giving too much attention to the 
metal, turning your back to your keyboard.

But yes, I also want things to be simple.

Steffen




_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers