Other Help Topics :: preserve ssh cert and user base across boots?



Quote (bjhbjh @ June 23 2008,14:21)
Quote
The cheatcode "noeject"


How do I invoke that at a reboot?

How do I invoke that at an ssh session reboot?

Or was this a joke ? I don't see 'noeject' in the DSL Wiki list of cheat  codes.

I need something that will persist across reboots so I don't have to  remember to do it if I reboot remotely a year from now.

Thanks,

Brian H.

Just because it's not in the wiki (yet) does not mean it is not used/true.

For a reboot, you would have to enter it in again at the boot menu, within the 30 second timeout, or it will use the default options, which does not include "noeject".

Same thing for an ssh session reboot.

Or, you can always launch with the cheatcode "frugal", which also skips the cd ejection at the end (Along with alot of other things)
As the wiki is user-maintained, it tends to be out of sync (a lot unfortunately). Some cheatcodes have never been mentioned anywhere near here, but can be found when adventuring deep in DSL ;)

It's no joke, it works. You can also edit your bootloader config file to include it among the other bootcodes.
Quote
For a reboot, you would have to enter it in again at the boot menu, within the 30 second timeout, or it will use the default options, which does not include "noeject".

Same thing for an ssh session reboot.


Ok, I seem to be missing something here. Please bear with me if I am being stupid.

If I am at a remote ssh session, perhaps miles away, and I call for a reboot, how do I enter the 'noeject' cheatcode at the local boot menu ?

Or perhaps I didn't make my intent clear from the outset. I want to make this thing come back to life, as configured, un attended in the event of either a local power interruption or a user invoked reboot from an ssh remote session.

So far I can do all this EXCEPT that the cd ejects and waits for someone to put it back in when the system is rebooted remotely.

How can I stop this from happening that does not require local console user intervention?

Thanks,

Brian H.
I have this kind of setup with my server, and there are several ways of going about it.  But if you are wanting to run the cd as a live cd (no frugal or regular install) then the easiest thing to do is to do a remaster and alter the /boot/isolinux/isolinux.cfg file to default boot with your preferences.
Quote (bjhbjh @ June 24 2008,12:12)
Quote
For a reboot, you would have to enter it in again at the boot menu, within the 30 second timeout, or it will use the default options, which does not include "noeject".

Same thing for an ssh session reboot.


Ok, I seem to be missing something here. Please bear with me if I am being stupid.

If I am at a remote ssh session, perhaps miles away, and I call for a reboot, how do I enter the 'noeject' cheatcode at the local boot menu ?

Or perhaps I didn't make my intent clear from the outset. I want to make this thing come back to life, as configured, un attended in the event of either a local power interruption or a user invoked reboot from an ssh remote session.

So far I can do all this EXCEPT that the cd ejects and waits for someone to put it back in when the system is rebooted remotely.

How can I stop this from happening that does not require local console user intervention?

Thanks,

Brian H.

Aside from remastering like Jason suggested, you can also install to a flash drive, which would get rid of the ejecting problem, allow for easier (imho) changes to the default boot settings, and some extra storage space.


But, as a side note, all my computers have, without fail, forced closed the cd drive if it is open on boot/reboot.

Or is your problem really about the "Remove cd and press enter to finish rebooting/shutting down" message (Which afaik, wasn't required on reboot, only on shutdown, but I've been on a usb boot for so long I've forgotten.)
Next Page...
original here.