Re: lsmod path hardcoded in v4l/Makefile

2009-07-28 Thread Trent Piepho
On Mon, 27 Jul 2009, Mauro Carvalho Chehab wrote: > Em Tue, 21 Jul 2009 09:14:36 +0200 > Matthias Schwarzott escreveu: > It is not a good idea to run as root. Most people compile everything > with a normal user and then use "sudo" command to install/remove/insert > modules. Unfortunately, dependin

Re: lsmod path hardcoded in v4l/Makefile

2009-07-27 Thread Mauro Carvalho Chehab
Em Tue, 21 Jul 2009 09:14:36 +0200 Matthias Schwarzott escreveu: > Hi Mauro! > > is there any reason to not pull this besides time? Time is one reason, however, there's another: It is not a good idea to run as root. Most people compile everything with a normal user and then use "sudo" comman

Re: lsmod path hardcoded in v4l/Makefile

2009-07-21 Thread Matthias Schwarzott
On Dienstag, 23. Juni 2009, Trent Piepho wrote: > On Tue, 23 Jun 2009, Matthias Schwarzott wrote: > > > On Mon, 2009-06-22 at 16:36 +0200, Matthias Schwarzott wrote: > > > > It seems the path to lsmod tool is hardcoded in the Makefile for > > > > out-of-tree building of v4l-dvb. > > > > Shouldn't $

Re: lsmod path hardcoded in v4l/Makefile

2009-06-23 Thread Trent Piepho
On Tue, 23 Jun 2009, Matthias Schwarzott wrote: > > On Mon, 2009-06-22 at 16:36 +0200, Matthias Schwarzott wrote: > > > It seems the path to lsmod tool is hardcoded in the Makefile for > > > out-of-tree building of v4l-dvb. > > > Shouldn't $PATH of root be considered safe? Else the distro or the sy

Re: lsmod path hardcoded in v4l/Makefile

2009-06-23 Thread Matthias Schwarzott
On Dienstag, 23. Juni 2009, Theodore Kilgore wrote: > On Mon, 22 Jun 2009, Andy Walls wrote: > > On Mon, 2009-06-22 at 16:36 +0200, Matthias Schwarzott wrote: > >> Hi list! > >> > >> It seems the path to lsmod tool is hardcoded in the Makefile for > >> out-of-tree building of v4l-dvb. > >> Now at l

Re: lsmod path hardcoded in v4l/Makefile

2009-06-23 Thread Matthias Schwarzott
On Dienstag, 23. Juni 2009, Trent Piepho wrote: > On Mon, 22 Jun 2009, Andy Walls wrote: > > On Mon, 2009-06-22 at 16:36 +0200, Matthias Schwarzott wrote: > > > Hi list! > > > > > > It seems the path to lsmod tool is hardcoded in the Makefile for > > > out-of-tree building of v4l-dvb. > > > Now at

Re: lsmod path hardcoded in v4l/Makefile

2009-06-23 Thread Matthias Schwarzott
On Dienstag, 23. Juni 2009, Andy Walls wrote: > On Mon, 2009-06-22 at 16:36 +0200, Matthias Schwarzott wrote: > > Hi list! > > > > It seems the path to lsmod tool is hardcoded in the Makefile for > > out-of-tree building of v4l-dvb. > > Now at least gentoo has moved lsmod from /sbin to /bin. > > Ad

Re: lsmod path hardcoded in v4l/Makefile

2009-06-22 Thread Theodore Kilgore
On Mon, 22 Jun 2009, Andy Walls wrote: On Mon, 2009-06-22 at 16:36 +0200, Matthias Schwarzott wrote: Hi list! It seems the path to lsmod tool is hardcoded in the Makefile for out-of-tree building of v4l-dvb. Now at least gentoo has moved lsmod from /sbin to /bin. Sorry, but is it considere

Re: lsmod path hardcoded in v4l/Makefile

2009-06-22 Thread Trent Piepho
On Mon, 22 Jun 2009, Andy Walls wrote: > On Mon, 2009-06-22 at 16:36 +0200, Matthias Schwarzott wrote: > > Hi list! > > > > It seems the path to lsmod tool is hardcoded in the Makefile for out-of-tree > > building of v4l-dvb. > > Now at least gentoo has moved lsmod from /sbin to /bin. Won't your p

Re: lsmod path hardcoded in v4l/Makefile

2009-06-22 Thread Andy Walls
On Mon, 2009-06-22 at 16:36 +0200, Matthias Schwarzott wrote: > Hi list! > > It seems the path to lsmod tool is hardcoded in the Makefile for out-of-tree > building of v4l-dvb. > Now at least gentoo has moved lsmod from /sbin to /bin. > Additionally it is bad style (or at least I am told so), to

lsmod path hardcoded in v4l/Makefile

2009-06-22 Thread Matthias Schwarzott
Hi list! It seems the path to lsmod tool is hardcoded in the Makefile for out-of-tree building of v4l-dvb. Now at least gentoo has moved lsmod from /sbin to /bin. Additionally it is bad style (or at least I am told so), to not rely on $PATH but hardcode pathes for tools that should be in $PATH.