Hi all,
Having read your replies, I think, the best option is NOT to change
netman's backend as suggested by Tobias Hunger. This means, I will
heed the advice of Rainer Weikusat, KatolaZ and Hendrik Boom.
Regarding the advice from aitor_czr, I wish to thank aitor,
notwithstanding I will not need
On Tue, Sep 08, 2015 at 11:53:33PM +0100, KatolaZ wrote:
> On Tue, Sep 08, 2015 at 09:40:12PM +0200, Edward Bartolo wrote:
> > Hi all,
> >
> > I think, a simple way to avoid the backend having to call external
> > programs like ifup and ifdown, is to use code belonging to these
> > programs as it
On Tue, Sep 08, 2015 at 09:40:12PM +0200, Edward Bartolo wrote:
> Hi all,
>
> I think, a simple way to avoid the backend having to call external
> programs like ifup and ifdown, is to use code belonging to these
> programs as it they were functions. This means, their code would be
> used like this
Hi Edward,
Don't change the name of the main funtion. In order to distinguish
between ifup and ifdown, you can use one of the arguments, for example
argv[1] (the first one *int argc* is the number of arguments in the
command line (+1) included itself) .
Aitor.
El 08/09/15 a las 21:40, Edwar
Edward Bartolo writes:
> Actually, you can do away with using a root SUID for backend as that
> was initially how netman was designed. However, there were complaints
> that I was adding an extra dependency which simply was a dependency on
> sudo being installed. Moreover, my initial proposal that
Hi all,
I think, a simple way to avoid the backend having to call external
programs like ifup and ifdown, is to use code belonging to these
programs as it they were functions. This means, their code would be
used like this:
Suppose int main(int argc, char * argv[]) is the main function for
ifup.
Quote: << Maybe you could get away with setting only one capability on
the back end instead of handing it full root privileges. Maybe there
is a group that has special privileges to run the necessary binaries?
Then you could sgid your back end to that group id, severely limiting
the damage any expl
Actually, you can do away with using a root SUID for backend as that
was initially how netman was designed. However, there were complaints
that I was adding an extra dependency which simply was a dependency on
sudo being installed. Moreover, my initial proposal that worked, used
sudo in a way to on
Hi,
since from yesterday, there is no ktorrent in repository.
--
Alessandro Sangiorgi
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
In the second script, i forgot adding $line3 in the path to 'find', so i
rectify:
** SCRIPT1:
#!/bin/sh
find ./DEBIAN -name "*.dsc" -exec ./script2 {} \;
exit 0
** END OF THE SCRIPT1
** SCRIPT2:
#!/bin/sh
line1=${1%/*}
line2=${line1#*/}
line3=${line2#*/}
if [ -d ./DEVUAN/$li
Hi all,
Take the case two mirrors, a complete Debian mirror in DEBIAN folder,
and the merged packages in DEVUAN folder, containing both their
corresponding /dists/ and /pool/. The following scripts build the /dist/
and /pool/ from the content of them, giving priority to Devuan. The
script1 ca
11 matches
Mail list logo
