9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9 boots 9
Date: Thu, 25 Sep 2003 19:09:08 -0400	[thread overview]
Message-ID: <2d77323e9c6e9eda78cc814ec01658bf@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0309251304300.5512-100000@maxroach.lanl.gov>

[-- Attachment #1: Type: text/plain, Size: 66 bytes --]

I'm happy with it given rsc's observation of the redundant reboot.

[-- Attachment #2: Type: message/rfc822, Size: 2857 bytes --]

From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: [9fans] 9 boots 9
Date: Thu, 25 Sep 2003 13:21:40 -0600 (MDT)
Message-ID: <Pine.LNX.4.44.0309251304300.5512-100000@maxroach.lanl.gov>


I mentioned that it would be nice to have /dev/rebootfile to load a file,
then do kfscmd halt, so we would have a really clean shutdown/reboot
scenario.

It was pointed out that adding another file to #s is hardly a good idea.

So, could we add another command to /dev/reboot?

Currently we have two commands for /dev/reboot
reboot
and
reboot filename

could we add

rebootfile filename

e.g. you could then do this:

echo 'rebootfile /386/test' > /dev/reboot
disk/kfscmd sync
disk/kfscmd halt
echo reboot > /dev/reboot

Is this acceptable?

ron




  parent reply	other threads:[~2003-09-25 23:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-25 19:21 ron minnich
2003-09-25 20:53 ` Russ Cox
2003-09-25 23:09 ` David Presotto [this message]
2003-09-25 23:56   ` boyd, rounin
2003-09-26  0:01     ` Charles Forsyth
2003-09-26  2:07       ` Lyndon Nerenberg
2003-09-26  2:11         ` boyd, rounin
2003-09-26  2:17           ` Lyndon Nerenberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2d77323e9c6e9eda78cc814ec01658bf@plan9.bell-labs.com \
    --to=presotto@closedmind.org \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).