From: Ray Olszewski <ray@comarre.com>
To: linux-newbie@vger.kernel.org
Subject: Re: Sequence of events at init (was boot) - fixed (sort of)
Date: Thu, 12 Oct 2006 17:12:01 -0700 [thread overview]
Message-ID: <452ED9D1.3010002@comarre.com> (raw)
In-Reply-To: <100951833359.20061012184700@wa5rrh.us>
Jim Reimer wrote:
> I added a bit to /etc/profile a couple of days ago to set the EDITOR
> environment variable to /usr/bin/jstar.... that was the problem. I
> don't know WHY that should be a problem, but removing is has cured
> the malady. (Now - how do I use jstar as the default editor?)
You don't ... since it apparently is not functional as the systemwide
default editor. (If you figure out the problem ... my prior, off-list
message to you offered some advice as to how ... then you may be able to
use jstar this way.) I don't use jstar or its ancestor joe, but the
Debian package for joe describes it as WordStar-like. That means -- at
least in its jstar configuration -- it is a fullscreen editor using
(probably) nsurses, and it may not function properly when called
non-interactively, say, as any bash script might.
That's all just a guess. The only way to know the specifics of the
problem is to find the init script that is invoking the editor ... I
believe bash uses the built-in command "edit" to invoke EDITOR, so check
the init scripts for that.
But do you need it as the systemwide default? You could add an EDITOR=
line to specific users' /home/[userid]/.profile or ./.bashrc
directories. Don't try this with root, though, or you may recreate the
problem you just fixed.
>
> Ray Olszewski wrote:
>
> <snip>
>
>>Why are you running mDNSResponder? Try disabling it from runlevel S
>>(just remove the symlink to its init script in /etc/rcS.d, or change the
>>starting S to NOT) and see if it helps. You may have to disable nifd as
>>well, since it appears to require nDNSRresponder.
>
>
> I guess I'm running it because it got installed with everything else
> when I installed FC4.... I'm still weeding out things I don't need -
> the problem is knowing what those things are.
>
>
>>Final thought ... what did you change recently? If this behavior is new,
>>it probably results from your having made some change since the last
>>successful boot/init.
>
>
> See above.
>
> I'm back in business. Thanks.
>
-
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
next prev parent reply other threads:[~2006-10-13 0:12 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
[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 [this message]
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=452ED9D1.3010002@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.