Using ssh from BusyBox, I cannot remove symlinks: after rebooting the device, symlinks re-appear. ls -la shows that symlinks have been removed, but after rebooting device they re-appear again.Those symlinks already existed beforehand, created at installing the firmware.$ rm uw_cert.cerI tried to remove uw_cert.cer and uw_key_prv.bin, but it reappears after reboot. The other files can be removed without problem.<root@fwre:/nvram/1/security> ls -latotal 5drwxr-xr-x    3 root     0                0 Jan  1 00:00 .drwxr-xr-x    5 root     0                0 Jan  1 00:05 ..-rwxrwxrwx    1 root     0              905 Jan  1 00:06 cm_cert.cerdrwxr-xr-x    2 root     0                0 Jan  1 00:00 downloadlrwxrwxrwx    1 root     0               25 Jan  1 00:00 uw_cert.cer -> /nvram/fw/bpi/uw_cert.cerlrwxrwxrwx    1 root     0               28 Jan  1 00:00 uw_key_prv.bin -> /nvram/fw/bpi/uw_key_prv.bin-rwxrwxrwx    1 root     0             1052 Jan  1 00:06 mfg_cert.cer-rwxrwxrwx    1 root     0              140 Jan  1 00:02 mfg_key_pub.binlrwxrwxrwx    1 root     0               37 Jan  1 00:00 root_pub_key.bin -> /etc/docsis/security/root_pub_key.binmount output:<root@fware:/var/tmp> mountrootfs on / type rootfs (rw)/dev/root on / type squashfs (ro)proc on /proc type proc (rw)ramfs on /var type ramfs (rw)sysfs on /sys type sysfs (rw)tmpfs on /dev type tmpfs (rw)devpts on /dev/pts type devpts (rw)/dev/mtdblock4 on /nvram type jffs2 (rw)EDIT:df /nvram/1/securityFilesystem           1K-blocks      Used Available Use% Mounted on/dev/mtdblock4             320       256        64  80% /nvramcat /proc/mountsrootfs / rootfs rw 0 0/dev/root / squashfs ro 0 0proc /proc proc rw 0 0ramfs /var ramfs rw 0 0sysfs /sys sysfs rw 0 0tmpfs /dev tmpfs rw 0 0devpts /dev/pts devpts rw 0 0/dev/mtdblock4 /nvram jffs2 rw 0 0
Canot remove symlinks: after reboot, symlinks re-appear
linux;shell;ssh;embedded;busybox
the filesystem you are trying to remove symlink from is probably an initramfs which is loaded on ram at boot, so the one you are modifying is the ram copy of the initial ram disk, which is discarded at shutdown.If you want to modify the ramdisk file, you need additional information. Which bootloader are you using? From which device? Can you access the kernel file and the ramdisk? Which kernel command line do you have? (use cat /proc/cmdline to discover)?I found this page that explains how to put a ramdisk image on a u-boot device. However I couldn't find a way to download the original ramdisk to your computer, so that you can edit.Please be careful that if you provide an invalid ramdisk your system could become unbootable. I don't know much about that specific architecture, so I can't suggest you a proven safe strategy. You would have your best chances if you ask another question about how to modify the initial ramdisk for a U-boot embedded modem (in this question you asked about symlinks so people who know about u-boot would probably overlook this completely)