Mailinglist Archive: opensuse (5130 mails)

< Previous Next >
Re: [SLE] Permanant bridge
  • From: Sunny <sloncho@xxxxxxxxx>
  • Date: Thu, 18 May 2006 09:25:59 -0500
  • Message-id: <e7eeb230605180725q54855c09ta5d866bb90d76566@xxxxxxxxxxxxxx>
On 5/18/06, Peter Van Lone <petervl@xxxxxxxxx> wrote:
On 5/18/06, Per Jessen <per@xxxxxxxxxxxx> wrote:

> Uh, rerun the brctl commands at boot-time? Bascially insert the proper
> script into your startup sequence or add them to the standard SUSE
> network-startup.

lol! (following is a 'mini-thread-hijaak' ...)

Per, you make that sound so simple! I am struggling to make sense of
how to simply "insert the proper script into your startup sequence".

It seems there are a bunch of directories where a script COULD go ...
is there a good HOW TO anywhere on SUSE startup? One of the things I'm
finding with linux is that each and every procedure has SO MANY
options/things you can do, and the docs all go into ALL of the
options, that it is simply over-whelming to figure out how to do
simple things. I would LOVE a simple HOW TO on SUSE startup
procedures/commands/scripts. Something short of 50 pages that could
help me to organize my understanding of the architecture ...

When is it OK to just put startup commands into /etc/init.d/boot.local?

Which rc#.d location is the correct one? /etc/init.d/rc#.d? Or, /etc/rc.d/rc#.d?

To create a script in /etc/init.d/rc3.d, do I just give it a K# or S#
name, and then type in whatever commands are used to start the
program? Or, is there a syntax that has to be followed?

What is the role of /etc/sysconfig?

Is there a procedure for integrating a startup routine with the YAST
runlevel editor?

I'm not sure that boot.local is good for you, as it runs before any
runlevel is entered, i.e. before network is started. At least this is
my understanding. Although running my firewall script (build with
fwbuilder) works OK from boot.local, so maybe I'm wrong.

Anyway - the proper way is to make a copy of /etc/init.d/skeleton
script to a new name (again in init.d) and modify it to make it run
after network is up, etc. The script is well documented, so you should
be able to figure it out. After you are ready with your script you can
use either chkconfig to set the right runlevels, or you can use
Yast/System/Runlevel editor to enable it. This will create the proper
K and S links in the right rc directories.

Cheers

--
--
Svetoslav Milenov (Sunny)

Windows is a 32-bit extension to a 16-bit graphical shell for an 8-bit
operating system originally coded for a 4-bit microprocessor by a
2-bit company that can't stand 1 bit of competition.

< Previous Next >
Follow Ups