All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Olszewski <ray@comarre.com>
To: linux-newbie@vger.kernel.org
Subject: Re: Sequence of events at boot
Date: Thu, 12 Oct 2006 08:54:33 -0700	[thread overview]
Message-ID: <452E6539.4090902@comarre.com> (raw)
In-Reply-To: <4b0d6e0d0610112357n67e2ca1fxe317a07fff725793@mail.gmail.com>

OK. Jim, I don't use Fedora, but there are a few basic thoughts that 
might help anyway.

1. That the line you quote ends with "Done" makes me suspect that it is 
not the problem. As Joy notes below, it probably is the next script that 
is hanging, not this one. (I can't tell from what you write below, but 
does the cursor advance to the next line after "Done"?)

2. I believe FC4 keeps its init scripts in /etc/init.d . Have you grep'd 
"jstarrc" in that directory? More basically, have you grep'd "jstar"? 
For this kind of problem grep'ing is better than "looking".

3. I'm not sure where RC4 puts its runlevel symlinks (the links to init 
scripts that Debian and its derivatives put in places like /etc/rc4.d), 
  but I'd suggest you find that location (actually there will be two of 
them, one for the single-user scripts, another for the actual runlevel 
scripts -- on a stock Debian system, they are /etc/rcS.d and /etc/rc4.d) 
and use the numbering it provides to deduce which script is involved.

4. Not to quibble, but your problem is not a boot failure; it is an init 
failure. What happens after the (apparent) hang? Do you always give up 
and reboot? How long do you wait (try at least 5 minutes, if you haven't 
already ... it may be some wacky DNS thing, and they normally time out 
after 3 minutes)? Does hitting ^C have any effect? Since you say "I've 
looked at every config, init, and rc file and directory I can think of", 
you must have *some* way of getting past this stoppage. What is it?

joy merwin monteiro wrote:
> it must be finding jstarrc _somewhere_, otherwise it
> would have complained. did you try setting the default
> runlevel to someother value( like 1) and booting ?
> it may not be about processing jstarrc, but something
> after that. you never know.
> 
> all bootup scripts should be in /etc/init.d/
> try grepping for jstarrc there. you can probably
> see what is getting executed after 'processing jstarrc'.
> 
> On 10/12/06, Jim Reimer <jdr@wa5rrh.us> wrote:
> 
>> As of today, my FC4 machine is not booting.  The last thing on the 
>> screen during boot is
>>
>> Processing `etc/joe/jstarrc`...Done
>>
>> jstar is the default editor on the system, and the "Processing" line 
>> on the screen follows
>> lm_sensors, automount, nifd, and mDNSResponder.  Also, curiously, it 
>> says twice that it's
>> processing the jstarrc file.
>>
>> Can't find where jstarrc is run during boot, so I have no idea what 
>> should be happening
>> next.  I've looked at every config, init, and rc file and directory I 
>> can think of, and
>> I'm drawing a blank.
>>
>> Where do I look?
>>
>> -- 
>> -jdr-
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2006-10-12 15:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-12  2:56 Sequence of events at boot Jim Reimer
2006-10-12  6:57 ` joy merwin monteiro
2006-10-12 15:54   ` Ray Olszewski [this message]
     [not found]     ` <52946266531.20061012171413@wa5rrh.us>
     [not found]       ` <452EC95D.6050807@comarre.com>
2006-10-12 23:47         ` Sequence of events at init (was boot) - fixed (sort of) Jim Reimer
2006-10-13  0:12           ` Ray Olszewski
2006-10-13 13:11             ` Hal
2006-10-13 16:15               ` Ray Olszewski

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=452E6539.4090902@comarre.com \
    --to=ray@comarre.com \
    --cc=linux-newbie@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.