Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Hello,
I've just had my dns-323 in the end of last week, and i'm trying to bypass its limitations..
I've followed the wiki to enable telnet and try to play around with scripts, but i'm really uncomfortable with the
idea of the HDD not being properly unmounted when starting the telnet daemon from the HDD.
Here's what i've tried, modifying the fun_plug and starttelnet.sh from the telnet howto:
- the fun_plug creates a /tmp/lnx_bin directory
- the fun_plug copies the utelnetd, busybox3 and starttelnet.sh to the /tmp/lnx_bin
- the fun_plug lauch the starttelnet.sh
- the starttelnet.sh make the symbolic link /tmp/lnx_bin/sh pointing the the /tmp/lnx_bin/busybox3
- the starttelnet.sh launch the utelnetd daemon using the /tmp/lnx_bin/sh
The telnet starts from the /tmp/lnx_bin directory and works fine.
Looking at the dmesg after several reboots, it seems that the HDD still properly umounted, and there's no
other warning.
Do you think it could be a clean solution for enabling telnet, without installing a custom firmware ?
I think the limit of this kind of solutions (copying the daemon to the ramdisk) would be the size
of the ramdisk. (about 900k still available after the installation of the utelnetd and busybox in the /tmp directory)
To have more space to play around with custom daemons, i was thinking of copying only the usb_storage.ko
to the ramdisk, launch it from there, and then start the custom daemons from an usb key permanently connected
to the dns-323. This way, the only device which would have a unclean umount is the usb key, and the HDD
containing the precious data will still safe and have clean umounts.
Does it seems a way to go ?
(sorry if this kind of solution was already discussed before, i'm new here and i haven't read every topics yet)
Offline
nagrom wrote:
Looking at the dmesg after several reboots, it seems that the HDD still properly umounted, and there's no
other warning.
couldn't this refer to the disk not being checked (look into e2fsck) since the last time that the drive was not cleanly unmounted?
nagrom wrote:
to the ramdisk, launch it from there, and then start the custom daemons from an usb key permanently connected
to the dns-323. This way, the only device which would have a unclean umount is the usb key, and the HDD
containing the precious data will still safe and have clean umounts.
Does it seems a way to go ?
Lots of us here do it this way. Look into ffp (0.5) - see the wiki, it comes with a telnetd and a sshd. Get it setup as you want then copy to your usb key, then run off the key. There are lots of posts here on how to do it, search for ffp and .bootstrap on this forum.
to check your drive(s) look up fsck from fonz (this is just one way of doing it).
Offline