Hi,
I am currently working on a sbc6000x board with linux 2.6.24 and Busybox
1.4.2.
I want to use the Telnet deamon on the board but everytime i try to connect
from my other computer (ubuntu) the connection close (by foreign host).
I already tried to modify the hosts.allow to allow the all connect
On 11.03.2015 17:24, Laurent Bercot wrote:
On 11/03/2015 17:10, Harald Becker wrote:
And what is wrong with a long lived daemon?
Ok, what I see is brain damaged developers writing big monolithic
long lived daemons, which suck up tons of memory and / or cpu power
:( ...
... this is not what I u
When I try to visit https://bugs.busybox.net , I see:
-
Software error:
Can't connect to the database.
Error: Can't connect to MySQL server on 'db1.osuosl.org' (110)
Is your database installed and up and running?
Do you have the correct username and password selected in localconfig?
For h
Interrupts ... no trouble, everybody agree you need only one unblocked
interrupt source, but never ask for the detail which one ... :)
Hi Laurent !
I'm sorry if I came across as dismissive or strongly opposed to the
idea.
It was not my intent. My intent, as always, is to try and make sure
Hi Natanael !
Hi Isaac !
Looks like you misunderstand my approach for the mdev changes ... ok,
may be I explained it the wrong way, so lets go one step back and start
with a wider view:
IMO Busybox is a set of tools, which allow to setup a working system
environment. How this setup is done,
On Wed, Mar 11, 2015 at 3:47 PM, Isaac Dunham wrote:
> On Wed, Mar 11, 2015 at 10:21:26AM +0100, walter harms wrote:
>>
>>
>> Am 11.03.2015 06:35, schrieb Isaac Dunham:
>> > +0 bytes disabled, +56 enabled when DESKTOP is enabled (glibc/i386):
>> > function
On 11/03/2015 15:56, Harald Becker wrote:
And one point to state clearly: I do not want to go the way to fork a
project (that is the worst expected), but I'm at a point, I like /
need to have Busybox to allow for some additional or modified
solutions to fit my preferences
I don't understand th
On Thu, 12 Mar 2015 00:15:52 +0100
Harald Becker wrote:
> Hi Michael !
>
> On 11.03.2015 22:44, Michael Conrad wrote:
> > I'm interested in this thread, but there is too much to read. Can you
> > explain your reason in one concise paragraph?
>
> One paragraph is a bit to short, my English suck
On Wed, 11 Mar 2015 14:30:13 +0100
Harald Becker wrote:
> Hi Natanael !
> Hi Isaac !
>
> Looks like you misunderstand my approach for the mdev changes ... ok,
> may be I explained it the wrong way, so lets go one step back and start
> with a wider view:
>
> IMO Busybox is a set of tools, whic
On Wed, Mar 11, 2015 at 7:02 PM, Harald Becker wrote:
> On 11.03.2015 16:21, Laurent Bercot wrote:
>>
>> I don't understand that binary choice... You can work on your own
>> project without forking Busybox. You can use both Busybox and your
>> own project on your systems. Busybox is a set of tools
On 11/03/2015 19:02, Harald Becker wrote:
It is neither a knowledge nor any technical problem, it is preference:
I want to have *one* statical binary in the minimal system, and being
able to run a full system setup with this (system) binary (or call it
tool set). All I need then is the binary, so
Hi,
I am Trying to install busybox on an Embedded arm system. Sadly this one
can't use sudo/make/apt-get so i can't directly install the busybox on it.
I have cross-compiled the busybox for my system but since this is on a
computer and not the target system i wanted to "make install" in a custom
d
On 3/12/2015 6:58 AM, Alexis Guilloteau wrote:
I am Trying to install busybox on an Embedded arm system. Sadly this one
can't use sudo/make/apt-get so i can't directly install the busybox on it.
I have cross-compiled the busybox for my system but since this is on a
computer and not the target sys
On Wed, Mar 11, 2015 at 5:10 PM, Harald Becker wrote:
> On 11.03.2015 16:34, Laurent Bercot wrote:
>>
>> On 11/03/2015 14:02, Denys Vlasenko wrote:
>>>
>>> But that nldev process will exist for all time, right? That's not
>>> elegant.
>>> Ideally, this respawning logic should be in the kernel.
>>
On Thu, 12 Mar 2015 13:10:20 +0100
Denys Vlasenko wrote:
> On Wed, Mar 11, 2015 at 5:10 PM, Harald Becker wrote:
> > On 11.03.2015 16:34, Laurent Bercot wrote:
> >>
> >> On 11/03/2015 14:02, Denys Vlasenko wrote:
> >>>
> >>> But that nldev process will exist for all time, right? That's not
> >>>
On 12/03/2015 13:10, Denys Vlasenko wrote:
I find it suboptimal to have, say, a hotplug daemon lingering
in the system five hours after the last hotplug event happened.
On most systems, it will be swapped away in that case. (Whereas
if the logic is in the kernel, that memory cannot be swapped.
Hi Denys !
On 12.03.2015 13:10, Denys Vlasenko wrote:
I find it suboptimal to have, say, a hotplug daemon lingering
in the system five hours after the last hotplug event happened.
IMO that highly depend on the complexity and resource constrains of the
daemon. For a big resource eating daemon
On Tue, Mar 3, 2015 at 2:13 PM, Laszlo Papp wrote:
> Denys, any feedback about this bugfix?
It is whitespace damaged.
>> +char *cp, *line;
>> +if (!name && member) {
>> +struct group* g;
>> +if ((g = getgrent())) {
Read the file using getgtent?
The rest o
Hi Isaac !
On 12.03.2015 02:05, Isaac Dunham wrote:
I just don't think you're quite thinking through exactly what this means.
In which sense? Let me know, what I got wrong. I'm a human, making mistakes,
not a perfect machine.
It seems like you want to force everyone who uses mdev to use a mul
Hi,
I have modified nldev[1] to instead of just executing mdev on kernel
events it will forward the event to a helper program via pipe. If
helper program exits (normally due to timeout), it will respawn it as
needed.
netlink listener code that needs to be in memory all the time:
http://git.alpine
I have this error message after the kernel initialisation after compiling
and transfering the /bin /sbin and /user of busybox 1.23.1 on a arm linux
2.6.24.
Is busybox doing something in the initialisation of the kernel or after ?
Because when i reload my system with its former root (with an older v
Issac,
Thanks for your reply. Yes, I am a bit familiar with Linux, been doing
work with it for 10+ years, from kernel hacking old 2.4/2.6 kernels up to
building entire systems (but using 3rd party tools, like. . . Yucto. . . :(
)
No, Init is NOT copied to the RFS, as far as I can tell, the RFS
Hi !
To Michael:
Don't be confused, Natanael provided an alternative version to achieve
the initial device file system setup (which isn't bad, but may have it's
cons for some people on small resource constrained systems of the
embedded world). So I left it out for clarity ... but still may be
On Thu, Mar 12, 2015 at 04:40:45PM +0100, Alexis Guilloteau wrote:
> I have this error message after the kernel initialisation after compiling
> and transfering the /bin /sbin and /user of busybox 1.23.1 on a arm linux
> 2.6.24.
> Is busybox doing something in the initialisation of the kernel or af
Hi Natanael !
> I assume that you are talking about named pipes (aka fifos)
http://en.wikipedia.org/wiki/Named_pipe
Ack, fifo device in the Linux / Unix world.
Why do you need a hotplug helper spawned by kernel when you have a
netlink listener? The entire idea with netlink listener is to avo
On 12/03/2015 16:19, Natanael Copa wrote:
netlink listener code that needs to be in memory all the time:
http://git.alpinelinux.org/cgit/ncopa/nldev/tree/nldev.c
A few comments:
- disableoom(): it's a generic operation for any daemon you don't
want to have killed, so you can factorize it: yo
On Thu, Mar 5, 2015 at 2:16 PM, Laszlo Papp wrote:
> This is not at all what I am referring to. I am not talking about how
> it ought to work. I am talking about it should be _documented_ how it
> works.
You proposed to add the following to --help:
+//usage: "\nIf no peer is defined,
Hi Laszlo !
So why don't you write such a binary wrapping busybox then and other
things? I think KISS principle still ought to be alive these days.
Not to mention, Denys already cannot cope with the maintenance the
way that it would be ideal. For instance, some of my IMHO serious
bugfixes are un
On Thu, Mar 12, 2015 at 6:00 PM, Harald Becker wrote:
> Hi Laszlo !
>
>> So why don't you write such a binary wrapping busybox then and other
>> things? I think KISS principle still ought to be alive these days.
>> Not to mention, Denys already cannot cope with the maintenance the
>> way that it w
On Thu, Mar 12, 2015 at 04:04:41PM +0100, Harald Becker wrote:
> Hi Isaac !
>
> On 12.03.2015 02:05, Isaac Dunham wrote:
> >>>I just don't think you're quite thinking through exactly what this means.
> >>In which sense? Let me know, what I got wrong. I'm a human, making mistakes,
> >>not a perfect
On 12/03/2015 18:26, Isaac Dunham wrote:
[1] The format proposed by Laurent uses \0 as an "line" terminator;
I think it might be better to use something that's more readily
generated by standard scripting tools from uevent files, which would
make it possible to use cat or env to feed the mdev par
On Thu, Mar 12, 2015 at 11:51:28AM -0400, Stephen Beckwith wrote:
> Isaac,
>Thanks for your reply. Yes, I am a bit familiar with Linux, been doing
> work with it for 10+ years, from kernel hacking old 2.4/2.6 kernels up to
> building entire systems (but using 3rd party tools, like. . . Yucto.
you can try init=/bin/sh
2015-03-12 19:17 GMT+03:00, Phil Sutter :
> On Thu, Mar 12, 2015 at 04:40:45PM +0100, Alexis Guilloteau wrote:
>> I have this error message after the kernel initialisation after compiling
>> and transfering the /bin /sbin and /user of busybox 1.23.1 on a arm linux
>> 2.6.2
The question I was asking was only about this:
On 3/12/2015 12:04 PM, Harald Becker wrote:
but that one will only work when you either use the kernel hotplug
helper mechanism, or the netlink approach. You drop out those who
can't / doesn't want to use either.
...which I really do think could
http://git.alpinelinux.org/cgit/ncopa/nldev/tree/nldev-handler.c
- child(): the parent is blocking as long as the child is running -
this is not safe if a user registers a bad-behaved helper. The
parent should be able to kill the child after a timeout.
- line 76: especially since you're block
Hi Laurent !
> Out of curiosity: what are, to you, the benefits of this approach ?
What are the benefits of preferences? ... good question!? ;)
Does it actually save you noticeable amounts of RAM ?
May be a few bytes ... noticeable? what is your level to noticeable
here? ... otherwise I
Hi Natanael !
My point is that a long lived daemon that stays there 5 hours after
the last hotplug event is currently unavoidable unless you are ok
with one fork/exec for every event.
Why not logical splitting the function?
- one listener which is gathering data, and forward sanitized message
On 12.03.2015 13:45, Laurent Bercot wrote:
If your system doesn't have swap, then it's probably some embedded
box and you likely won't hotplug many things, so you can use
Natanael's approach: use an event listening daemon for the coldplug,
then kill it and register a /proc/sys/kernel/hotplug he
ACK ... but what do you think about e.g. tcpsvd (accepting incoming
tcp connections), or netlink reader?
tcpsvd is precisely a super-server. That's where I would draw the line.
A netlink reader probably has its place.
But really, I have my own super-servers and my own netlink reader, so
I h
On 12/03/2015 20:07, Harald Becker wrote:
Don't you risk resource problems for hotplug handler processes, when
the system is under such pressure?
No and that's my point. If you don't have swap, it's likely that
your box is embedded and you won't spend your life plugging and
unplugging USB stic
On 12.03.2015 18:12, Laszlo Papp wrote:
It is nice that you are trying to help and I certainly appreciate it,
but why cannot you simply do that job nicely outside busybox where
*you* have to be responsible for that project? It would be an explicit
way of enforcing KISS and not putting more burden
On 12.03.2015 19:38, Michael Conrad wrote:
On 3/12/2015 12:04 PM, Harald Becker wrote:
but that one will only work when you either use the kernel hotplug
helper mechanism, or the netlink approach. You drop out those who
can't / doesn't want to use either.
...which I really do think could be an
Thank you very much for constructive feedback.
Most of the code is from nldev which I didn't write. I simply moved the
child() function that fork/exec mdev to a separate helper.
I suppose I should rename it to something else than nldev. Maybe
netlinkd? nlevd?
The intention is that the helper sho
On 12.03.2015 20:57, Laurent Bercot wrote:
On 12/03/2015 20:07, Harald Becker wrote:
Don't you risk resource problems for hotplug handler processes, when
the system is under such pressure?
No and that's my point. If you don't have swap, it's likely that
your box is embedded and you won't spe
Hi Natanael,
I prefer finishing planning and creating a functional complete
structure, before hacking code, so I do not see any benefits, to dig
into your code at the moment, don't see any question that could be
answered this way, at least at the moment.
So my question to this:
What is the
On 03/12/2015 04:32 PM, Harald Becker wrote:
On 12.03.2015 19:38, Michael Conrad wrote:
On 3/12/2015 12:04 PM, Harald Becker wrote:
but that one will only work when you either use the kernel hotplug
helper mechanism, or the netlink approach. You drop out those who
can't / doesn't want to use ei
46 matches
Mail list logo
