The OTA will work and will replace the modified firmware. All of the additional packages that were installed, and files that have been created outside of the official directories, will remain on the external disk but the official firmware has no hooks into it to start things up so they will become dormant. Once someone patches the new firmware again, you can load that and should be exactly back to where you were.However (sorry if this has been answered before), I have a very basic question: what will happen if/when Humax transmits an OTA update?
Plug in a USB stick in the front or rear port. When you then select USB from Media the virtual drive will be listed as a USB device also.Also, should I be able to view my media stored in my virtual drive on the box? I can see the virtual drive when I select copy but then cannot view the drive on my box afterwards. I can see the virtual drive over FTP and samba but not on the box.
humax# service Name Installed Autostart Running ---- --------- --------- ------- mediatomb Yes No No dropbear Yes Yes Yes transmission Yes Yes Yes samba Yes No No cifs Yes No No mongoose Yes Yes Yes humax# service stop transmission Stopping transmission... Done. humax# service auto transmission Disabling auto-start for transmission
login as: zero Authenticating with public key "dave" Passphrase for key "dave": -sh: ulimit: line 6: error setting limit (Invalid argument) humax#
humax# cat /etc/profile # ~/.bashrc: executed by bash(1) for non-login interactive shells. export PATH=/mod/bin:/mod/usr/bin:/mod/bin/busybox:/bin:/sbin export LD_LIBRARY_PATH=/mod/lib:/lib:/usr/lib ulimit -S -c 100000000 umask 077 # If running interactively, then: if [ -n "$PS1" ]; then hst=`hostname` [ "$hst" = '(none)' ] && hst=humax export PS1="$hst# " export USER=`id -un` export LOGNAME=$USER export HOME=/mod fi if [ -f /mod/etc/termtype ]; then export TERM=`cat /mod/etc/termtype` else # Reasonable failsafe export TERM=vt100 fi for f in /mod/etc/profile/*; do [ -f "$f" ] || continue . "$f" done