Aras Vaichas schrieb: > Rob Landley wrote: >> Ok, I think you've just exhausted the "volunteer help from open source >> developers" category. If you want "professional", you're welcome pay one of >> our consulting rates, and we'll fix your problem as soon as the check clears. >> >> (Be careful what you ask for...) >> > I just don't get why you guys are being so harsh. The example from > Wolfgang's website told me to: > > ~ # mount -t jffs2 /dev/mtdblock5 /new-root > ~ # cd /new-root/ > /new-root # pivot_root . old-root > ~ # umount /old-root/proc > ~ # chroot . kill -QUIT 1 > > All I asked was why this didn't work when I ran it from within > /etc/init/rcS. I later found out that the problem was that inittab > wasn't being reloaded when I called "kill -1 1". I honestly thought it > was a Busybox specific issue otherwise I wouldn't have posted. > > If there is another Busybox mailing list for system integrators and > implementors, then please refer me to it and I will go there instead. > > But getting all 133t and calling people n00bs isn't the way to win > friends and influence people. You'll just piss them off, and some of > those people (like myself) occasionally find bugs in your code, submit > patches and contribute to these great open source projects. >
Hi Aras, it seems no one is understanding each other. What Denys wants is 1. .config ,so he can build your busybox binary 2. a /etc/inittab and all scripts that are needed to create the problem 3. a README that contain anything about your buildchain like version of linuxkernel, gcc, libc, etc The purpose is to rebuild exactly your environment (that shows the bug) so he can see for himself and compare with a healthy one. hope that helps, wh _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
