RE: RFC: Alternate patch to have true new-style rc.d scripts inports (without touching localpkg)

From: Rob MacGregor (freebsd.macgregor_at_blueyonder.co.uk)
Date: 07/31/04

  • Next message: FreeBSD Tinderbox: "[current tinderbox] failure on i386/i386" 
    To: <current@freebsd.org>
Date: Sat, 31 Jul 2004 11:19:57 +0100

    > -----Original Message-----
    > From: Oliver Eikemeier [mailto:eikemeier@fillmore-labs.com]
    >
    > Nope, only two kinds of scripts will be run: old-style scripts with a
    > `.sh' extension, and new-style rc.d scripts without extension. So you
    > should not run into an trouble with scripts renamed to `.old' or
    > `.disabled', except when you got into the habit to *remove* the
    > extension to disable the scripts.

    Ok, I'm confused (but then I haven't had my coffee yet).

    You're saying that any script ending in .sh is assumed to be an old style one
    and processed that way. You're also saying that anything else is assumed to
    be a new style script, correct?

    However, then you say that renaming scripts (new or old?) will be fine, as
    long as you rename them to .old or .disabled - anything else will still be run
    as if it's a new style script?

    I just want to ensure that I don't get bit by this when it goes live :) 

    -- 
 Rob | Oh my God! They killed init! You bastards! 
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
  • Next message: FreeBSD Tinderbox: "[current tinderbox] failure on i386/i386"