So,
Let's go ahead and tackle this. There have been a handful of methods
suggested for handling multiple interfaces in SystemImager in the past.
Has anybody stumbled upon what they think is a "ringer"?
-Brian
Sean Dague wrote:
>On Sun, Mar 27, 2005 at 10:07:14AM -0800, [EMAIL PROTECTED] wrote:
>
>
>> sub write_sc_command {
>> my ( $out, $ip_assignment_method ) = @_;
>>+
>>+ # Configure the network device used to contact the image-server -AR-
>>+ print $out "[ -z \$DEVICE ] && DEVICE=eth0\n";
>>+
>> my $sc_excludes_to = "/etc/systemimager/systemconfig.local.exclude";
>> my $sc_cmd = "chroot /a/ systemconfigurator
>> --excludesto=$sc_excludes_to";
>> if ($ip_assignment_method eq "replicant") {
>>@@ -1595,7 +1599,7 @@
>> print $out "\n";
>>
>> print $out "[INTERFACE0]\n";
>>- print $out "DEVICE = eth0\n";
>>+ print $out "DEVICE = \$DEVICE\n";
>>
>>
>
>I don't think you should change this last portion. There are a lot of users
>that make assumptions on [INTERFACE0] ending up to be eth0 (including the
>OSCAR folks) and changing that to be the install interface will break
>some other things.
>
>The right thing is doing multiple interfaces through SystemImager. So while
>shutting down $DEVICE is definitely a good thing, setting up $DEVICE by
>default with SystemConfigurator is a change in behavior that is going to
>break some people.
>
> -Sean
>
>
>
--
------------------------------------------------------
Brian Elliott Finley Mobile: 630.631.6621
gpg --keyserver wwwkeys.pgp.net --recv-keys 10F8EE52
------------------------------------------------------
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Sisuite-devel mailing list
Sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
