From: Hans-Werner Hilse <hilse@web.de>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] init Id "s0" respawning too fast: disabled for 5 minutes
Date: Wed, 5 Apr 2006 16:12:02 +0200 [thread overview]
Message-ID: <20060405161202.b77f0337.hilse@web.de> (raw)
In-Reply-To: <B31C4776605A3840B544482E1A94C5C93AEC90@eagle.birds>
Hi,
On Wed, 5 Apr 2006 15:58:57 +0200 "Jean Blignaut" <jean@megaweb.biz>
wrote:
> On Wed, 5 Apr 2006 15:01:53 +0200 "Jean Blignaut" <jean@megaweb.biz>
> wrote:
>
> >> ----nope just tried still get the "respawning too fast" error even
> >> with the s0 line commented out---
>
> > Does the error claim that it's still the "s0" line? If so, you must
> > have make a mistake when commenting it out like editing the
> > wrong /etc/inittab or similar (initrd regeneration, etc.pp.).
>
> No mistake as far is I can tell after checking the /etc/inittab on the
> booted gnap virtual machine I decided to try changing runlevels from
> 3 to 4 and back again this seems to have worked cause I havn't seen
> the message since [...]
well, a reboot, changing runlevels or at least a "telinit q" is
necessary to make init aware of the changed inittab. I didn't mention
this before...
> -- this leads me to believe that some thing else is
> enabling the s0 tty, something that ignores inittab
> As a matter of interest: the I/O error hasn't shown up in the logs
> since I first commented out s0 line in inittab
OK, then it worked. But please note that the "s0" is the name of the
inittab entry (read "man inittab") and doesn't per se specificate a
device. That's done in another place and the correct device name is
ttyS0 (capital "S"). The line could have a totally different name.
Anyway, the inittab issue seems to be gone for you, that was just a
clarification. All that seem to be left is your firewall problem
(doesn't seem to be embedded-specific, so you might want to ask on
-security or -user).
> I'll have to test and see what works and what doesn't don't know too
> much about the inner workings of shorewall and my knowledge of
> iptables matching is -slim-
Sorry, I can't help here as I'm not using any firewall builders. But
you should disable lines that e.g. specify that only certain
applications are allowed to access the net (that would probably be
command matching).
As a side note: You *did* compile full netfilter support into your
kernel, didn't you?
-hwh
--
gentoo-embedded@gentoo.org mailing list
next prev parent reply other threads:[~2006-04-05 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 13:58 [gentoo-embedded] init Id "s0" respawning too fast: disabled for 5 minutes Jean Blignaut
2006-04-05 14:12 ` Hans-Werner Hilse [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-05 14:47 Jean Blignaut
2006-04-05 14:52 ` Hans-Werner Hilse
2006-04-05 14:30 Jean Blignaut
2006-04-05 13:35 Jean Blignaut
2006-04-05 13:01 Jean Blignaut
2006-04-05 13:43 ` Hans-Werner Hilse
2006-04-05 12:13 Jean Blignaut
2006-04-05 12:42 ` Hans-Werner Hilse
2006-04-05 12:56 ` Hanni Ali
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=20060405161202.b77f0337.hilse@web.de \
--to=hilse@web.de \
--cc=gentoo-embedded@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox