: S 0 1 6
>>>
>>> in the LSB. Now as I understand it, by the script definition, there
>>> should be links in /etc/rcS.d to the scripts in /etc/init.d with
>>> names like K20ncidd.init, and so forth. Per the output of
>>> update-rc.d, however, thes
Sven Joachim wrote:
> On 2011-11-24 17:51 +0100, lrhorer wrote:
>
>> Arno Schuring wrote:
>>
>>> lrhorer (lrho...@satx.rr.com on 2011-11-24 03:38 -0600):
OK, so here's the deal. I compiled and installed ncid on one of my
Debian servers Everything seems to be working just fine. There'
Dmitriy Matrosov wrote:
> 2011/11/24 Arno Schuring :
>> lrhorer (lrho...@satx.rr.com on 2011-11-24 03:38 -0600):
>>> OK, so here's the deal. I compiled and installed ncid on one of my
>>> Debian servers Everything seems to be working just fine. There's
>>> one small item, though. When I took t
ate-rc.d, it gave me a warning saying "stop runlevel arguments (0
>> 1 6) do not match LSB Default-Stop values (S 0 1 6)". When I looked
>> at the scripts, they have the line
>>
>> # Default-Stop: S 0 1 6
>>
>> in the LSB. Now as I understand it,
On 2011-11-24 17:51 +0100, lrhorer wrote:
> Arno Schuring wrote:
>
>> lrhorer (lrho...@satx.rr.com on 2011-11-24 03:38 -0600):
>>> OK, so here's the deal. I compiled and installed ncid on one of my
>>> Debian servers Everything seems to be working just fine. There's
>>> one small item, though.
Arno Schuring wrote:
> lrhorer (lrho...@satx.rr.com on 2011-11-24 03:38 -0600):
>> OK, so here's the deal. I compiled and installed ncid on one of my
>> Debian servers Everything seems to be working just fine. There's
>> one small item, though. When I took the init scripts and ran
>> update-rc
2011/11/24 Arno Schuring :
> lrhorer (lrho...@satx.rr.com on 2011-11-24 03:38 -0600):
>> OK, so here's the deal. I compiled and installed ncid on one of my
>> Debian servers Everything seems to be working just fine. There's
>> one small item, though. When I took the init scripts and ran
>> upda
lrhorer (lrho...@satx.rr.com on 2011-11-24 03:38 -0600):
> OK, so here's the deal. I compiled and installed ncid on one of my
> Debian servers Everything seems to be working just fine. There's
> one small item, though. When I took the init scripts and ran
> update-rc.d, it gave me a warning sa
p runlevel arguments (0 1 6) do not
> match LSB Default-Stop values (S 0 1 6)". When I looked at the scripts,
> they have the line
>
> # Default-Stop: S 0 1 6
>
> in the LSB. Now as I understand it, by the script definition, there
> should be links in /etc/
not
match LSB Default-Stop values (S 0 1 6)". When I looked at the scripts,
they have the line
# Default-Stop: S 0 1 6
in the LSB. Now as I understand it, by the script definition, there
should be links in /etc/rcS.d to the scripts in /etc/init.d with names
like K20ncidd.init, and so fo
Grzegorz wrote:
> 'S' means " Single user mode (not to be switched to directly)"
You're right, but I thought it would start in single user mode (S) and
then move up to 1, 2, ...
Probably that was my misconception.
Felipe.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubs
my script in rcS.d would be enough, but it
just didn't run at initialization time. Then I discovered the utility
sysvconfig which told me that my script was disabled! Asking it to
enable it made links appear in each of rc*.d, and now it is being ran
at
initialization time okay.
hi,
i
script in rcS.d would be enough, but it
just didn't run at initialization time. Then I discovered the utility
sysvconfig which told me that my script was disabled! Asking it to
enable it made links appear in each of rc*.d, and now it is being ran
at
initialization time okay.
So now I h
On 09/23/2006 05:22 PM, Marc wrote:
Hi there,
I have a feeling that I have a problem with the sysinit scripts (rcS.d)
I put additional modules to be loaded (e.g. ip_nat_ftp) into
/etc/modules, however they are not loaded when the system boots.
I have executed /etc/rcS.d/S20module-init-tools
Hi there,
I have a feeling that I have a problem with the sysinit scripts (rcS.d)
I put additional modules to be loaded (e.g. ip_nat_ftp) into
/etc/modules, however they are not loaded when the system boots.
I have executed /etc/rcS.d/S20module-init-tools manually, which does
what it should. Now I
Hi there,
I have a feeling that I have a problem with the sysinit scripts (rcS.d)
I put additional modules to be loaded (e.g. ip_nat_ftp) into
/etc/modules, however they are not loaded when the system boots.
I have executed /etc/rcS.d/S20module-init-tools manually, which does
what it should. Now I
Hi there,
I have a feeling that I have a problem with the sysinit scripts (rcS.d)
I put additional modules to be loaded (e.g. ip_nat_ftp) into
/etc/modules, however they are not loaded when the system boots.
I have executed /etc/rcS.d/S20module-init-tools manually, which does
what it should. Now I
Well, i've been at this off and on today. Not much dice
to recap, I'm trying to use dhcp-client-identifier on a live cd
(eventually) so I can additional settings when they boot (without
affecting their normal setup while not on the livecd).
If someone else has invented this wheel, let me kn
I think I've found a lead to answer my question.
http://lists.netisland.net/archives/plug/plug-2005-02/msg00210.html
I'll have to try, and follow up later.
Chow.
I'd like to roll my own livecd (anything debian proper, or debian like
will do). The one piece of my puzzle I'm still puzzled about is
allowing the cd to make a dhcp request I can distinguish as coming
from the livecd. Based on that, I'd also like to offer an init script
(gpg signature thereof m
berto's .config file was useful, but it differs
exceedingly little from my own. Further investigation suggests that
the problem lies in the /etc/init.d/network and /etc/init.d/networking
scripts run within rcS.d. The kernel is looking for something it
cannot find, apparently.
I'm
21 matches
Mail list logo
