New answers tagged

0

Not that I know of. You could define the first run in a separate .service file, using [Service] Type=oneshot Then create another .service file that depends on that one, which will be the one that runs regularly.


0

I used the setenv command that ltib prints at the end of building images and the error vanished. It seems that you should instruct system of size of your disk with that command.


0

I assume the other device is the same ip-camera model, with an identically sized HDD/memory component. Then you could use dd to make an image of the whole HDD. Since stuff in dev, proc, sys and other such directories is not on the drive but in virtual memory, you don't need to explicitly copy it, it will be populated at boot. With something like: cat /dev/...


0

mmc0: error -22 whilst initialising SDIO card The mmc could not be initialized for a few reasons: The wrong or no module is loaded for your embedded device. The device tree settings could be wrong for your mmc specs. The hardware bus is not ready to tx/rx data. I get this error on my device when I do not power down correctly. To fix it I do mmcinfo and ...


1

I wrote a comprehensive blog post about Linux network tuning which explains everything about monitoring, tuning, and optimizing the Linux network stack (including the NAPI weight). Take a look. Keep in mind: some drivers do not disable IRQs from the NIC when NAPI starts. They are supposed to, but some simply do not. You can verify this by examining the hard ...


3

Your IP camera is embedded system. This means that it have so little resources available that it cannot even store "fat" bash binary on itself. It's probably has too little RAM too to store it on memory or the operating system inside it is locked down so you will not be able to store bash binary permanently on it. You need to find out how to receive ...


1

You can can transfer files using tftp. With it you can transfer various tools on your device, including another busybox which has vi and other utilities you need in it (check /proc/cpuinfo for the architecture). Should there be no working busybox with vi for your architecture you can try to compile it yourself (preferably statically linked to uClibc) using ...



Top 50 recent answers are included