\etc\sysconfig\network\ symbolic link

OS: Suse 9.0 [2.4.21-215-default] [grub] [kde 3.1]

Sitchy-ation:::
have different networks my laptop has to connect to
at different times [home, work location 1,
work location 2, etc]

Trying to use a symbolic link for 'ifcfg-eth0'.

right now I have mutliple ifcfg-type files named:::

eth0.dhcp used for dhcp [default work/home]
eth0.C.1 static for 192.168.1.x network
eth0.A.1 static for lab testing 1.1.1.x network
eth0.C.16 used for work 16.x net [no dhcp]

so, I have a sym link set for ifcfg-eth0-->eth0.dhcp

UPON BOOTUP the sym link is not seen/paid attention to;
and the network interface does not come up.

However, after bootup, I can 'ifup eth0' and the link
comes up fine [no matter which file I have the sym link
pointing to].

What is the reason that the bootup scripts won't see
the sym link?

Is there a way to 'automate' this via grub on boot by passing param? [really
don't prefer this...but...]

Thanks,
TroyC




----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---

sure enough grub was the option:::
http://www.kplug.org/lmbp/

courtesy of google
http://www.google.com/search?hl=en&l...g-eth0+symboli
+link&btnG=Search

I wrote:

> OS: Suse 9.0 [2.4.21-215-default] [grub] [kde 3.1]
>
> Sitchy-ation:::
> have different networks my laptop has to connect to
> at different times [home, work location 1,
> work location 2, etc]
>
> Trying to use a symbolic link for 'ifcfg-eth0'.
>
> right now I have mutliple ifcfg-type files named:::
>
> eth0.dhcp used for dhcp [default work/home]
> eth0.C.1 static for 192.168.1.x network
> eth0.A.1 static for lab testing 1.1.1.x network
> eth0.C.16 used for work 16.x net [no dhcp]
>
> so, I have a sym link set for ifcfg-eth0-->eth0.dhcp
>
> UPON BOOTUP the sym link is not seen/paid attention to;
> and the network interface does not come up.
>
> However, after bootup, I can 'ifup eth0' and the link
> comes up fine [no matter which file I have the sym link
> pointing to].
>
> What is the reason that the bootup scripts won't see
> the sym link?
>
> Is there a way to 'automate' this via grub on boot by passing param?
> [really don't prefer this...but...]
>
> Thanks,
> TroyC
>
>
>
>
> ----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet
> News==---- http://www.newsfeed.com The #1 Newsgroup Service in the World!
> >100,000 Newsgroups ---= 19 East/West-Coast Specialized Servers - Total
> Privacy via Encryption =---

--
---------
No bits were hurt during this transmission.


----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---

Hi,

it should also work with your original approach.
But using boot profiles is far more comfortable i guess.

Sorry, i don't remeber the network script name that is used to
set up net devices (somewhere in /etc/init.d/), but i've looked
over it some time ago.
There were some restrictions which files are loaded so
some were simply left out. This might apply to symlinks,
but i'm not sure.
Check the script and i think you could change it to
handle the link file ifcfg-eth0 correctly.

Ciao

Ralf