9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] some #s
Date: Wed,  4 Jun 2003 12:46:17 -0400	[thread overview]
Message-ID: <bf799d38bfa154dc56338da2b2e4e150@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0306032215140.6478-100000@maxroach.lanl.gov>

On Wed Jun  4 00:22:20 EDT 2003, rminnich@lanl.gov wrote:
> ...
> Some timing for same hardware with 9load/plan 9:
>
> 0->10 seconds: 9load is up and has loaded the plan 9 kernel over ether
> 10-20 seconds: no real output from plan 9
> 20-30 seconds (or so): until I get the 'boot from [il]' prompt
> ...

i just tried some boots without a plan9.ini (9load tweaked to probe
suitable ether devices, but no other changes). the machine is a standard
asus k7m motherboard with a floppy and 2 ether cards, no other
peripherals:

 it takes 20s from power on to get 9load off the floppy, probe for peripherals
 and get to the 'boot from: ' prompt;
 it takes 3s after typing 'ether0!/386/9pccpu' to the above prompt to get the
 kernel over the ether and get the 'root is from (il, tcp)[il]: ' prompt.

perhaps the kernel is poking some other peripherals on your system (e.g. things
that look like discs) to create the delay you see after the kernel is loaded?


  parent reply	other threads:[~2003-06-04 16:46 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-04  4:21 ron minnich
2003-06-04  4:45 ` andrey mirtchovski
2003-06-04 14:31   ` ron minnich
2003-06-04 11:27 ` C H Forsyth
2003-06-04 14:39   ` ron minnich
2003-06-04 15:39     ` andrey mirtchovski
2003-06-04 21:20     ` northern snowfall
2003-06-04 23:06       ` [9fans] " Jim Choate
2003-06-05  0:24         ` northern snowfall
2003-06-05  3:20           ` Dan Cross
2003-06-05 11:33             ` Jim Choate
2003-06-05 22:41               ` Dan Cross
2003-06-05 23:06                 ` Jim Choate
2003-06-06  0:25                   ` David Presotto
2003-06-06  1:08                     ` Dan Cross
2003-06-06  1:19                       ` David Presotto
2003-06-06  3:58                         ` northern snowfall
2003-06-06  3:41                           ` ron minnich
2003-06-06 11:36                             ` Jim Choate
2003-06-06  4:04                           ` northern snowfall
2003-06-06 12:01                         ` Jim Choate
2003-06-06 12:02                           ` David Presotto
2003-06-06  1:21                       ` boyd, rounin
2003-06-06  2:24                       ` Russ Cox
2003-06-06  3:15                         ` Dan Cross
2003-06-06  4:17                           ` northern snowfall
2003-06-06  3:33                             ` Dan Cross
2003-06-06  4:45                               ` northern snowfall
2003-06-06  5:46                                 ` Dan Cross
2003-06-06  9:48                                   ` northern snowfall
2003-06-06  3:51                             ` boyd, rounin
2003-06-06 15:45                     ` Jack Johnson
2003-06-05  3:20       ` [9fans] " ron minnich
2003-06-04 16:46 ` jmk [this message]
2003-06-04 22:38   ` ron minnich

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=bf799d38bfa154dc56338da2b2e4e150@plan9.bell-labs.com \
    --to=jmk@plan9.bell-labs.com \
    --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).