Perhaps a real expert can correct me if I'm wrong here, but I don't think it creates a real filesystem. What was the 'failed' error message? We can take a look at some of the optware-bootstrap.sh code:
optware-bootstrap-manual.sh - bootstrap in WebOS Internals - Gitorious
So we can see lines like:
Code:
mkdir -p /var/opt
mkdir -p /opt
mount -o bind /var/opt /opt
echo '/var/opt /opt bind defaults,bind 0 0' >> /etc/fstab
So it seems to be creating those directories /var/opt and /opt and then using the "bind" option in mount.
mount(8): mount file system - Linux man page
It appears that the script is using /var/opt as if it were a filesystem and mounting (using bind option) to mount point /opt so even though it is mounting, there is no new 'filesystem' mounted. Later on in the script we can see some mkfs commands, but these appear to be for running in an emulator.
If you want to check in Novaterm or a file browser, then we can check if there are those directories /var/opt and /opt existing and if that entry for /opt exists in /etc/fstab.
For example in Novaterm.
Code:
# ls -l /opt
# ls -l /var/opt
# grep opt /etc/fstab
# mount | grep opt
So if those directories /var/opt and /opt don't exist and no lines in fstab for mounting /opt then nothing to worry about. Even if those directories /var/opt and /opt exist I'm not sure if there can be any real harm.
