On Sun, November 7, 2010 11:30 am, Jeremy Visser wrote:

> Is the root filesystem read/write or read-only? Can you write to it
> anywhere?

Jeremy, thanks

also, any thought where to look for 'built-in' urls for web access

guess not r/w ?:

/ # touch new1
touch: new1: Read-only file system

/ #
/ # ls -al
drwxrwxr-x    1 510      511          2048 Sep 24 08:34 .
drwxrwxr-x    1 510      511          2048 Sep 24 08:34 ..
-rwxr-xr-x    1 510      511         61440 Jan 28  2010 Test.fat
drwxr-xr-x    1 510      511          2048 Jan 28  2010 bin
drwxr-xr-x    1 root     root            0 Jan  1  1970 dev
drwxr-xr-x    1 510      511          2048 Jan 28  2010 etc
drwxr-xr-x    1 510      511          2048 Jan 28  2010 lib
lrwxrwxrwx    1 510      511            11 Sep 24 08:34 linuxrc ->
bin/busybox
drw-rw-rw-    1 root     root         2048 Nov  7  2010 lost+found
drwxr-xr-x    1 510      511          2048 Jan 28  2010 mnt
dr-xr-xr-x   81 root     root            0 Nov  7  2010 proc
drwxr-xr-x    1 510      511          2048 Jan 28  2010 sbin
drwxr-xr-x   11 root     root            0 Nov  7  2010 sys
drwxr-xr-x   13 root     root            0 Nov  7 03:49 tmp
drwxr-xr-x    1 510      511          2048 Jan 28  2010 tmp_orig
drwxr-xr-x    1 510      511          2048 Jan 28  2010 usr
lrwxrwxrwx    1 510      511             4 Sep 24 08:34 var -> tmp/
-rwxr-xr-x    1 510      511       4919683 Jan 28  2010 vmlinux
/ #

/ # df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                98.0M     98.0M         0 100% /
/dev/mtdblock/2          40.0M      1.3M     38.7M   3% /usr/local/etc
/dev/rd/0                40.0k     40.0k         0 100% /mnt/rd
/dev/scsi/host0/bus0/target0/lun0/part1    144.6G     33.3G    111.3G  23%
/tmp/hdd/volumes/HDD1
/dev/scsi/host0/bus0/target0/lun0/part3      4.0G    266.0k      4.0G   0%
/tmp/hdd/livepause
/dev/scsi/host0/bus0/target0/lun0/part4    151.9M     34.5M    109.5M  24%
/tmp/hdd/root
/ #

/ # chroot
BusyBox v1.1.3 (2009.12.18-04:22+0000) multi-call binary

Usage: chroot NEWROOT [COMMAND...]

Run COMMAND with root directory set to NEWROOT.



> If you can write somewhere and have plenty of storage (>300MB), I'd
> start by creating a Debian chroot. Use debootstrap, tell it you want mips,
> and upload it to the device.
>
> Of course, it doesn't look like the telnet interface you have supports
> chroot, so you will need to fish out busybox-static from Debian (the mips
> version, of course), and go from there.
>
>> and, lm-sensors to control fan speed, if possible ?
>
> If the hardware supports it, then possibly, but I believe the kernel
> also needs support. I don't know whether the device's kernel is in ROM or
> not.
>
> If the kernel doesn't support it, you'll likely need to grab the source
> from the manufacturer's website. (Although you may be waiting a long time.
> NetComm didn't publish the source to one of their routers on their
> site, and said they only send it on a CD for $10 postage. Fortunately after
> >60 days they decided to upload the source to their FTP site
> instead.)
>


-- 
Voytek

-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Reply via email to