On Fri, Sep 30, 2005 at 03:11:29PM +0200, Guus Sliepen wrote:
> On Thu, May 12, 2005 at 03:27:58PM -0700, Jean Tourrilhes wrote:
>
> > The problem with calling ifscheme directly is that it
> > reconfigures the interface, which would make the boot slower. On the
> > other hand, setting the file /etc/network/scheme *before* any network
> > driver is loaded (i.e. before /etc/init.d/networking and
> > /etc/init.d/hotplug) would make sure that when the interface is
> > initially configured, it is with the right scheme.
> >
> > Maybe you could try a boot script like this and report :
> > -------------------------------------
> > #!/bin/sh
> >
> > PATH=/sbin:/bin
> >
> > test -x /sbin/ifscheme || exit 0
> >
> > # No boot time scheme assigned
> > if [ -z "$SCHEME" ]; then
> > exit 0;
> > fi
> >
> > # Set default scheme using boot value
> > echo "$SCHEME" >/etc/network/scheme
> > -------------------------------------
> >
> > Guus : how do you want to manage to boot-script issue ?
>
> I can implement that init script without problems (I haven't heard any
> reports like you though). However, there is some discussion ongoing
> about writing stuff to /etc and about writing stuff during boot time. I
> think you should move /etc/network/scheme to /etc/network/run/scheme.
Done in ifscheme 1.5. I tested, but as 'run' is a symlink on
'.', that doesn't count...
> Met vriendelijke groet / with kind regards,
> Guus Sliepen <[EMAIL PROTECTED]>
Jean
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
