Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Pages: 1
hi,
i just installed ffp 0.5 on my dns-321. i wanted to be able to use cleanboot, so i installed version 2.0.5 and started the shell script. now when i type in reboot or shutdown, i get these messages:
-sh: reboot: not found
-sh: shutdown: not found
am i doing something wrong?
thanks in advance
Offline
you're doing better than I did with cleanboot on my 321.
It locked me out and I had to do some odd gymnastics with ftp and ftp site commands to get back in.
I believe that cleanboot renames or removes a few builtins and replaces them with it's own script. I think
it is something like do_reboot. If I recall, there is a readme that explains the expected behavior.
Offline
what i'm thinking at this point is that cleanboot for the dns-323 isn't compatible with the 321... don't know if anyone has been successful in installing cleanboot on the 321. if anyone has any advice on how to do this, that would be great.
even though i can't type in reboot or shutdown, if i do busybox reboot, it will do the reboot the old (bad) way...
any help is much appreciated.
thanks
Last edited by fahrennheit451 (2009-05-12 05:22:36)
Offline
for information, i tried to install it on a DNS-313 a few days ago, i had the same errors !
It seems it is not compatible on DNS-313 too !
Offline
I'd be curious if this script
http://dns323.kood.org/forum/viewtopic. … 201#p29201
would work. It works on my 323 and on my 321. I'm not sure if anyone else has tried it.
If you want to use the maintenance mode,
you will need to have utelnetd installed in the place where the script is looking. shutdown and reboot shouldn't require it.
You will want to copy the script to /sbin before you run it, otherwise the disk it lives on wont unmount.
Offline
talkingRock
i copied your script to /sbin and tested reboot and shutdown, both of which worked (don't know if everything umounted correctly, but the unit rebooted and shut down with the appropriate command).
i want to try the maintenance part of your script, but i don't understand exactly where i should get utelnetd from, and where i should put it... as far as i can tell, i'm supposed to put it in /local/bin/utelnetd...
is this correct?
thanks so much for your help!
Offline
farennheit451,
Thanks for giving the script a try!
I'm really curious whether the umounts worked, but that's easier to tell with the maintenance mode.
Yes, the way the script is written right now depends on my directory structure.
You will want to put utelnetd into /local/bin, or somewhere else and change the variable.
The easiest way to get utelnetd is from the telnet how-to on this site.
http://dns323.kood.org/_media/howto:ute … ache=cache
This should get you a tarball with a bunch of stuff including utelnetd.
The other thing you will need to really do anything is an account which has root privileges and has /bin/sh as its shell and a home directory on the ramdisk. On my box, this user is "toor". This will make that happen.
adduser toor
usermod -u 0 -g 0 -o -s /bin/sh -d /root toor
When you put the machine into the maintenance level, you should have to log back in using telnet. Once the machine accepts your username and password, you will have to type the magic number:
5784468
in order to get a shell prompt.
Let me know how it goes.
Once I get a few folks to try it, I'll can package the whole mess into its own tarball so that it's more usable.
Offline
talkingRock
i've made a few modifications to my fun_plug to copy your cleanboot.sh as well as utelnetd to the appropriate places at each boot.
i also realized that we need to run store-passwd.sh to make sure user toor remains in place after reboot.
once i did this, i was able to run sh cleanboot.sh maintenance... which forced a umount, and a disconnection from ssh (expected).
then i was able to login via telnet using toor, and am currently running e2fsck!
thanks so much for your wonderful scripts... hope this solves my cleanbooting needs.
Offline
Great! I'm glad it's working for you.
What you did is the way I actually run it.
It just seemed easier to package it so that it can be run without changes to fun_plug, but that is the easiest way to do it since that way you don't have to worry about start_utelnetd failing.
Yes, I forgot to tell you about the store-passwd.sh, but you are correct.
I'll let you know if I make any enhancements.
Fonz had the idea of creating a second ramdisk and copying some more advanced tools over to it for a higher powered maintenance mode. "badblocks" "debugfs" "dumpfs" and a few others would almost certainly be needed in case any real problem were found. The "parted" tools, ... would be nice. With my current setup, it shouldn't be too hard to setup an "extendedMaintenance" level which would do exactly that. Something like that is my next step on this if I get some time.
Currently, I'm ok without that feature since I run ffp from /dev/sda4 and duplicate it onto /dev/sdb4 for backup. After I fsck /dev/sda4, I remount it ro, and then I have a full toolset for the other partitions, which is where the real data live anyhow.
Thanks again for giving it a try and I'm glad that it seems to be working.
Offline
Pages: 1