If i disable the automount option in dd-wrt gui, I can manually mount /dev/sda using usbfs and then I see 2 directories 001 and 002, but seems I can't create folder inside them , is there solution for this issue ?:
Code:
root@DD-WRT:/# ls /dev/s*
/dev/sda /dev/sda1 /dev/sda2
root@DD-WRT:/# mount
rootfs on / type rootfs (rw)
/dev/root on / type squashfs (ro,relatime)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
ramfs on /tmp type ramfs (rw,relatime)
none on /dev type tmpfs (rw,relatime,size=512k)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
devpts on /proc/bus/usb type usbfs (rw,relatime)
root@DD-WRT:/# mount -t usbfs /dev/sda/ /mnt
root@DD-WRT:/# mount
rootfs on / type rootfs (rw)
/dev/root on / type squashfs (ro,relatime)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
ramfs on /tmp type ramfs (rw,relatime)
none on /dev type tmpfs (rw,relatime,size=512k)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
devpts on /proc/bus/usb type usbfs (rw,relatime)
/dev/sda/ on /mnt type usbfs (rw,relatime)
root@DD-WRT:/# ls -l /mnt
dr-xr-xr-x 2 root root 0 Jan 1 00:00 001
dr-xr-xr-x 2 root root 0 Jan 1 00:00 002
-r--r--r-- 1 root root 0 Jan 1 00:00 devices
root@DD-WRT:/# chmod -R 777 /mnt/001
root@DD-WRT:/# ls -l /mnt/001
-rwxrwxrwx 1 root root 43 Jan 1 00:00 001
-rwxrwxrwx 1 root root 50 Jan 1 00:00 002
root@DD-WRT:/# cd /mnt/001
root@DD-WRT:/mnt/001# mkdir etc
mkdir: cannot create directory 'etc': Operation not permitted
rootfs on / type rootfs (rw)
/dev/root on / type squashfs (ro,relatime)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
ramfs on /tmp type ramfs (rw,relatime)
none on /dev type tmpfs (rw,relatime,size=512k)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
/dev/sda1 on /tmp/mnt/sda_part1 type ext2 (rw,relatime,errors=continue)
/dev/sda1 on /jffs type ext2 (rw,relatime,errors=continue)
[part deleted;p]
this
Code:
/dev/sda1 on /tmp/mnt/sda_part1 type ext2 (rw,relatime,errors=continue)
is my automount part from the web gui
when i had 3 partitions i had /mnt/sda_part1 2 and 3
rootfs on / type rootfs (rw)
/dev/root on / type squashfs (ro,relatime)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
ramfs on /tmp type ramfs (rw,relatime)
none on /dev type tmpfs (rw,relatime,size=512k)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
/dev/sda1 on /tmp/mnt/sda_part1 type ext2 (rw,relatime,errors=continue)
/dev/sda1 on /jffs type ext2 (rw,relatime,errors=continue)
[part deleted;p]
this
Code:
/dev/sda1 on /tmp/mnt/sda_part1 type ext2 (rw,relatime,errors=continue)
is my automount part from the web gui
when i had 3 partitions i had /mnt/sda_part1 2 and 3
OK, so /dev/sda is NOT mounted.
What release do you use ? I'm thinking about upgrade from 16785 to have this issue fixed and looking for less evilness release
Posted: Wed Jan 04, 2012 12:13 Post subject: ssh public key authentication glitch after opkg install
trumanwu wrote:
gingerbreadassassin wrote:
trumanwu wrote:
do you really need to mount /etc?
it seems my ssh public key is stored in /etc. After run the script to mount /mnt/etc to /etc. my ssh authentication is not working any more. After I removed the startup script, it's working again.
could you please give me some advice on this?
is there any workaround to avoid break my ssh authentication? or I just need to remove the ssh config and then re-config ssh again?
Thank you.
I suffer the same symptoms and would also like to know what to do in this situation. If it's really as simple as not having authentication before applying the script, that'd be awesome.
I guess something affected my authentication files. What I did is remove the key, save, and then add the SSH key again, save. It worked!
Hi,
I just had the same ssh-public-key issue after setting up the opkg. The problem is caused by the
Code:
mount -o bind /mnt/root /tmp/root
command, because this mount hides the files which reside in /tmp/root. Under /tmp/root normally dd-wrt stores the ssh-authentication keys. Now there are two options:
a) re-enter and save the key, as you did
b) script around the issue
Currently I don't know, what dd-wrt additionaly stores in the /tmp/root directory, so I decided to choose option b. I changed the start-script-mount to:
Code:
# copy all files form /mnt/root to /tmp/root, this fixes the .ssh glitch
if [ -f /mnt/move.root2tmp ]; then
if [ -d /mnt/root ]; then
tar -C /mnt/root -cf - . | tar -C /tmp/root -xf -
fi
else
# old mechanism
mount -o bind /mnt/root /tmp/root
fi
To activate the "copy-root" feature just create the /mnt/move.root2tmp file:
Code:
touch /mnt/move.root2tmp
A similar condition could be used for the "/etc" update problem.
Posted: Thu Jan 05, 2012 5:10 Post subject: Confirming a fix for: cant resolve symbol glob64 in lib opkg
For the NetGear WNDR3700.. running build 17210...
I found that by using the libc and opkg packages from release candidate 4 (ie: 10.03.1-rc4) rather than 6 (10.03.1-rc6) fixed the problem with 'opkg: can't resolve symbol 'glob64' in lib 'opkg'.
So step 5 below needs to be modified to use the older .../10.03.1-rc4/... packages.
I just wish I could find the posting in this forum that suggested this workaround. Thanks to whomever.
5. Install the required libraries for the MIPS (big-endian) architecture and OpenWRT's opkg
Posted: Sun Jan 08, 2012 8:47 Post subject: cannot resolve symbol 'glob64'
Hi! Long tread to read through, finally at last someone claims to have found solution to 'glob64' problem. However when I full of hope tried it I got:
root@DD-WRT root $ cd /tmp
root@DD-WRT /tmp $ wget http://downloads.openwrt.org/backfire/10.03.1-rc6/ar71xx
/packages/libc_0.9.30.1-43.29_ar71xx.ipk
Connecting to downloads.openwrt.org (78.24.191.177:80)
libc_0.9.30.1-43.29_ 100% |*******************************| 219k 00:00:00 ETA
root@DD-WRT /tmp $ wget http://downloads.openwrt.org/backfire/10.03.1-rc6/ar71xx
/packages/opkg_576-2_ar71xx.ipk
Connecting to downloads.openwrt.org (78.24.191.177:80)
opkg_576-2_ar71xx.ip 100% |*******************************| 57114 --:--:-- ETA
root@DD-WRT /tmp $ ipkg install libc_0.9.30.1-43.29_ar71xx.ipk opkg_576-2_ar71xx
.ipk
ERROR: File not found: //usr/local/lib/ipkg/lists/whiterussian
You probably want to run `ipkg update'
ERROR: File not found: //usr/local/lib/ipkg/lists/non-free
You probably want to run `ipkg update'
ERROR: File not found: //usr/local/lib/ipkg/lists/backports
You probably want to run `ipkg update'
/bin/ipkg: line 1184: sort: not found
mkdir: cannot create directory '/jffs/tmp/': Read-only file system
root@DD-WRT /tmp $ opkg update
opkg: can't resolve symbol 'glob64' in lib 'opkg'.
root@DD-WRT /tmp $
This is just the beginning of your problems and there will be no help forth-coming from dd-wrt devs. Your immediate problem can be solved by copying ipkg to /tmp and editing the file (ipkg is simply a shell script). Change all instances of 'head -1' to 'head -n1' (there are 5 instances) and executing that file. I hope you compatible with unending frustration! _________________ WRT54G V1.0, build 14853 VINT mini_USB_FTP, USB mod, pixelserv
Buffalo WZR-HP-AG300H build 17461, pixelserve
Buffalo WZR-HP-G300NH, OpenWrt (trunk build 29606), ath9k drivers, pixelserv
Ubiquiti Bullet M2, AirOS
Posted: Tue Jan 24, 2012 18:57 Post subject: On to another ..
Thx King ...
Yup. On to another problems...
Question: How come some of the folks were able to install and run the Optware ? Agreed, I am not an expert in dd-wrt, but I am fairly ok with unix...
The problem message is :
./ipkg install libc_0.9.30.1-43.29_ar71xx.ipk o
pkg_576-2_ar71xx.ipk
ERROR: File not found: //usr/local/lib/ipkg/lists/whiterussian
You probably want to run `ipkg update'
ERROR: File not found: //usr/local/lib/ipkg/lists/non-free
You probably want to run `ipkg update'
ERROR: File not found: //usr/local/lib/ipkg/lists/backports
You probably want to run `ipkg update'
./ipkg: line 1184: sort: not found
tar: invalid option -- z
tar: invalid option -- z
ipkg_install_file: ERROR unpacking control.tar.gz from libc_0.9.30.1-43.29_ar71xx.ipk
Posted: Tue Jan 24, 2012 19:45 Post subject: Re: On to another ..
vijayadik wrote:
Thx King ...
Yup. On to another problems...
Question: How come some of the folks were able to install and run the Optware ? Agreed, I am not an expert in dd-wrt, but I am fairly ok with unix...
Basically, the problems that you are presently experiencing are caused by a dis-functional 'busybox'. I mistakenly in the past had said busybox was broken. I was informed that busybox was not broken, but that the problem was a 'build problem' where some of the busybox configuration parameters had not been set properly during the build process. To me, I really don't see the validity of the distinction... BusyBox still does not function as it should!
Quote:
The problem message is :
./ipkg install libc_0.9.30.1-43.29_ar71xx.ipk o
pkg_576-2_ar71xx.ipk
ERROR: File not found: //usr/local/lib/ipkg/lists/whiterussian
You probably want to run `ipkg update'
ERROR: File not found: //usr/local/lib/ipkg/lists/non-free
You probably want to run `ipkg update'
ERROR: File not found: //usr/local/lib/ipkg/lists/backports
You probably want to run `ipkg update'
./ipkg: line 1184: sort: not found
tar: invalid option -- z
tar: invalid option -- z
ipkg_install_file: ERROR unpacking control.tar.gz from libc_0.9.30.1-43.29_ar71xx.ipk
Again, the current problem is busybox... it has not been configured to support tar -z option (gzip support). You cannot edit around this error. If you do happen to find a way around that error, I assure you, there will be more that are far more serious. You will not find a build of optware packages that is compatible with your dd-wrt build. The toolchains/libraries (mainly UlibC) have become incompatible. If your objective is to run optware and take advantage of the increased memory/storage available newer units, then dd-wrt has become the wrong choice. _________________ WRT54G V1.0, build 14853 VINT mini_USB_FTP, USB mod, pixelserv
Buffalo WZR-HP-AG300H build 17461, pixelserve
Buffalo WZR-HP-G300NH, OpenWrt (trunk build 29606), ath9k drivers, pixelserv
Ubiquiti Bullet M2, AirOS