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 uncommented. Putting more and more stuff into busybox
would just make the situation worse and more frustrating,

The usual way of development is:

(1) Planning the work to do (the step we are discussing here)

(2) Code hacking (what I will do next)

(3) Preliminary Testing (also mine job)

(4) Offer access to those who like (for further testing)

(5) fixing complains

(6) putting into main stream (or accessible by the rest)

Right? So what is your complain?


sorry. I really do not want busybox to follow the systemd way.

Who told you, I'm trying to go that way. My intention is to overcome the
mdev problems, and allow those who like to use the netlink interface. I
dislike encoding any fixed functionality in a binary, and don't force
anybody to use possible extensions.

Laurent poked me to more clarity, which would mean to split early
initialization from mdev operation, with the cave eat of a slight change in init scripts (may be one more command or some extra command parameter, could be done automatic, but than different functionalities in applet - may be more discussion required on that). Beside that, it's shall be up to the system maintainer, to chose which device management mechanism to use (BB shall provide the tools for that, small modular tools, bound together by admin - no big monolithic).


On the positive side of systemd, they at least have far more resource
than what Denys can offer, at least in my opinion, so ...

You are talking about development resources? Here they are! I'm willing to do that job, not asking for someone else doing the work.

I'm asking about, which preferences other people have, so I'm able to get the right decisions, before I start hacking code ... so what's wrong?

--
Harald

_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox

Reply via email to