As shown in the post above, while networking is still up and logged in (over serial port) as 'root':
Code:
[root@[192_168_15_244] root]# mount
rootfs on / type rootfs (rw)
/dev/root on / type ext3 (rw,noatime,nodiratime,barrier=0,data=writeback)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
tmpfs on /dev/shm type tmpfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
tmpfs on /var type tmpfs (rw,relatime,size=0k)
/dev/mmcblk0p3 on /var/local type ext3 (rw,relatime,errors=continue,barrier=0,data=writeback)
fsp on /mnt/us type fuse.fsp (rw,nosuid,nodev,noatime,user_id=0,group_id=0)
/dev/mmcblk0p1 on /cust type ext3 (ro,sync,relatime,barrier=0,data=writeback)
/dev/loop/0 on /mnt/base-us type vfat (rw,noexec,noatime,nodiratime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortn)
That says that both the 'main' file system and the visible USB user storage is both already mounted, to confirm:
Code:
[root@[192_168_15_244] root]# ls /mnt/base-us
diagnostic_logs documents system voice
[root@[192_168_15_244] root]# ls /mnt/us
diagnostic_logs documents system voice
[root@[192_168_15_244] root]# ls /cust
bin dev lib opt sbin tmp var
chroot etc mnt proc sys usr
That will cause some changes, in the past the 'main' file system was not mounted.
For the moment, just make a 'fix-it' mark on your to-do list (or when reading currently posted directions).
= = = =
I need to feed the person - more later today.