eth_up command not found

hosler · 09-20-2006, 11:51 AM

I see this error multiple times when I boot up. It comes from the inet1 script. Does this script need to run for me to use the network? Right now all I use is iwconfig and dhclient to connect to the internet. Also, does ldconfig have to execute every bootup? It takes a while.

Alien Bob · 09-20-2006, 12:22 PM

What release of Slackware are you running?

Quote:

eth_up command not found

The "eth_up" function is no longer used in Slackware 10.2 and onwards. My guess is that you installed some other (non-Slackware) software packages (like, I remember an old version of Dropline Gnome did this) that incorrectly patches the rc.inet1 file.

The rc.inet1 file initializes the network, and it can do so too for your wireless card if you want. But if you work with iwconfig and dhclient and find that sufficient, then you don't need rc.inet1 I guess.

And no, ldconfig does not need to run on every boot. If it takes to long to start, comment it out of the boot script. Make sure you run ldconfig by hand then, each time you install new software.

Eric

Tinkster · 09-20-2006, 12:34 PM

Hmmm ... none of the rc.inet1 scripts I have access to mention an eth_up
What did you do to yours? :}
[edit]
That's what you get when you start editing and go away

[/edit]

Cheers,
Tink

raska · 09-20-2006, 12:35 PM

Just to complement Alien Bob's post, the ldconfig command is called from the /etc/rc.d/rc.M script.
I personally prefer to add an ampersand (&) at the end of the command so it runs albeit on background and the boot up process doesn't last too much (around the 25 - 30 secs mark)

zborgerd · 09-20-2006, 01:44 PM

Quote:

Originally Posted by Alien Bob

What release of Slackware are you running?

The "eth_up" function is no longer used in Slackware 10.2 and onwards. My guess is that you installed some other (non-Slackware) software packages (like, I remember an old version of Dropline Gnome did this) that incorrectly patches the rc.inet1 file.

The rc.inet1 file initializes the network, and it can do so too for your wireless card if you want. But if you work with iwconfig and dhclient and find that sufficient, then you don't need rc.inet1 I guess.

And no, ldconfig does not need to run on every boot. If it takes to long to start, comment it out of the boot script. Make sure you run ldconfig by hand then, each time you install new software.

Eric

That's very likely. GNOME's system-tools-backends was doing this erroneously on Slackware. I thought that we patched it in Dropline so that it wouldn't keep doing this, but it may have been forgotten. I'll investigate it.

If you are using another GNOME desktop for Slackware, then they may not have patched it.

hosler · 09-20-2006, 02:39 PM

i use dropline. thanks guys.

zborgerd · 09-20-2006, 02:53 PM

Quote:

Originally Posted by hosler

i use dropline. thanks guys.

Which version? I'm still looking into it. Doesn't appear that it was patched out.

Alien Bob · 09-20-2006, 03:11 PM

Quote:

Originally Posted by zborgerd

Which version? I'm still looking into it. Doesn't appear that it was patched out.

Zborgerd, you found it was caused by a Gnome network configuration tool, in this old thread: http://www.linuxquestions.org/questi...46#post2067846.
Don't know if it is something you Dropline guys should patch, or pass on to the upstream developers, but it seems neither has been done up to now.

Cheers, Eric