On Tue, Jul 25, 2006 at 06:10:23PM +0200, Eduard Bloch wrote:
I disagree. You compare a 11kB utility (sysctl) with a new 132kB
package.
You are comparing two completly different things. If we are to
actually compare the size of tools actually *needed*:
-rwxr-xr-x 1 root root 1554 2006-05-12
#include hallo.h
* Riku Voipio [Wed, Jul 26 2006, 12:18:54PM]:
On Tue, Jul 25, 2006 at 06:10:23PM +0200, Eduard Bloch wrote:
I disagree. You compare a 11kB utility (sysctl) with a new 132kB
package.
You are comparing two completly different things. If we are to
actually compare the size
#include hallo.h
* Otavio Salvador [Mon, Jul 24 2006, 09:26:58PM]:
IMO it is much easier to find functionality like this if it is already
present on the system than if you have to search for it. And it seems to
me basic enough that it warrants inclusion in base, especially as
Eduard Bloch [EMAIL PROTECTED] writes:
#include hallo.h
* Otavio Salvador [Mon, Jul 24 2006, 09:26:58PM]:
IMO it is much easier to find functionality like this if it is already
present on the system than if you have to search for it. And it seems to
me basic enough that it warrants
On Jul 25, Frans Pop [EMAIL PROTECTED] wrote:
My main rationale is that its init script offers offers a fairly clean and
obvious way for users to set values in /sys at boot time. (Without the
need for them to hack a local init script.)
echo looks clean and obvious to me as well, and does not
On Jul 25, Otavio Salvador [EMAIL PROTECTED] wrote:
I agree that we already have equivalent functionality for /proc values
so makes sense to have it in too.
No, wishing a feature-complete set of configuration file for aestethical
reasons is not enough to move more stuff to base.
--
ciao,
On Tuesday 25 July 2006 21:16, Marco d'Itri wrote:
echo looks clean and obvious to me as well, and does not require 180 KB
of new packages.
Why do you choose to completely ignore the option (that was mentioned at
least twice) to move the init script part to a separate or existing base
On Jul 25, Frans Pop [EMAIL PROTECTED] wrote:
Why do you choose to completely ignore the option (that was mentioned at
least twice) to move the init script part to a separate or existing base
package? That would make the addition to base only a few KB.
*If* this really added only a few KB
#include hallo.h
* Otavio Salvador [Tue, Jul 25 2006, 02:23:16PM]:
Well then we might work reducing the code size but at least am I
talking about functionality and that's important in my POV.
Important for whom exactly? I do not have this package installed here
and I never missed it. Now I
[EMAIL PROTECTED] (Marco d'Itri) writes:
On Jul 25, Otavio Salvador [EMAIL PROTECTED] wrote:
I agree that we already have equivalent functionality for /proc values
so makes sense to have it in too.
No, wishing a feature-complete set of configuration file for aestethical
reasons is not
Em Ter, 2006-07-25 às 02:04 +0200, Frans Pop escreveu:
My main rationale is that its init script offers offers a fairly clean and
obvious way for users to set values in /sys at boot time. (Without the
need for them to hack a local init script.)
It's far away from actually being installed by
On Jul 25, Otavio Salvador [EMAIL PROTECTED] wrote:
No, wishing a feature-complete set of configuration file for aestethical
reasons is not enough to move more stuff to base.
So let's remove setctl from base.
There is no such package. But if you think that some of the packages
currently in
On Tuesday 25 July 2006 01:42, Marco d'Itri wrote:
Which packages actually use it, and why?
What can it do that echo $VALUE /sys$DEVPATH/attribute and similar
commands cannot do?
What is the point of having an abstraction layer for a published and
already widely used API?
I object to
Frans Pop [EMAIL PROTECTED] writes:
On Tuesday 25 July 2006 01:42, Marco d'Itri wrote:
Which packages actually use it, and why?
What can it do that echo $VALUE /sys$DEVPATH/attribute and similar
commands cannot do?
What is the point of having an abstraction layer for a published and
Package: base
Severity: wishlist
As 2.6 will be the default kernel for Etch and /sys is playing an
increasingly important role in system configuration, I was wondering if
it does not make sense to add sysfsutils to base and thus install it by
default on new systems.
It can be used for example to
15 matches
Mail list logo
