Patrick Shanahan wrote:

* Joseph Loo [05-05-08 22:46]:

...

I have Suse 10.1. It turns out that my wireless went down. I tried to do a ifconfig ath0 down followed by an up. It did not restart the network. If I do

/etc/init.d/network restart

, will this restart the network? Will this apply to 10.3?

yes, but... better and the openSUSE way: rcnetwork restart (as root)

akulkis@kulkis:~> file /sbin/rcnetwork /sbin/rcnetwork: symbolic link to `/etc/init.d/network' -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Joe Sloan wrote:

Sam Clemens wrote:

...

Patrick Shanahan wrote:

...

* Joseph Loo [05-05-08 22:46]:

...

I have Suse 10.1. It turns out that my wireless went down. I tried to do a ifconfig ath0 down followed by an up. It did not restart the network. If I do

/etc/init.d/network restart

, will this restart the network? Will this apply to 10.3?

yes, but... better and the openSUSE way: rcnetwork restart (as root)

akulkis@kulkis:~> file /sbin/rcnetwork /sbin/rcnetwork: symbolic link to `/etc/init.d/network'

The difference (and suse gets points for this) is that "rcnetwork" is in the path. So, I can type "rcne<tab> restart" instead of the clumsy "/etc/init.d/network restart"

However... /etc/init.d/network restart works on ANY *n*x platform except BSD -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Joe Sloan wrote:

Sam Clemens wrote:

...

Joe Sloan wrote:

...

Sam Clemens wrote:

...

Patrick Shanahan wrote:

...

* Joseph Loo [05-05-08 22:46]:

...

I have Suse 10.1. It turns out that my wireless went down. I tried to do a ifconfig ath0 down followed by an up. It did not restart the network. If I do

/etc/init.d/network restart

, will this restart the network? Will this apply to 10.3?

yes, but... better and the openSUSE way: rcnetwork restart (as root)

akulkis@kulkis:~> file /sbin/rcnetwork /sbin/rcnetwork: symbolic link to `/etc/init.d/network'

The difference (and suse gets points for this) is that "rcnetwork" is in the path. So, I can type "rcne<tab> restart" instead of the clumsy "/etc/init.d/network restart"

However...

/etc/init.d/network restart works on ANY *n*x platform except BSD

Right, so if I'm stuck having to write cross platform scripts, I'll use the clunky "one size fits all" method. But in shell sessions on the machines I admin, which are all suse, I'm gonna go ahead and enjoy the benefits...

I guess if you have the luxury of being in a purse SuSE environment, that's great. But most admins live in a multi-flavor world...and so it pays to know what works on Solaris and HP-UX as much as SuSE. Otherwise, you spend a lot of time trying to remember which customization is for which platform. Lowest common denominator...although ugly, works most everywhere.

Joe

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, 2008-05-05 at 23:44 -0400, Sam Clemens wrote:

However...

/etc/init.d/network restart works on ANY *n*x platform except BSD

In case you come across those BSD things (to put it mildly) one can do something like: ln -s /usr/local/etc/rc.d/network /etc/rc.d/network (I alway forget where free puts its scripts and data, as they don't give a damn about fsh) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tue, May 6, 2008 at 4:40 PM, Sam Clemens wrote:

The fractured and shattered BSD community has everything but destroyed, through pride and arrogance, what was Bill Joy's baby and what USED TO BE (past tense!) the premier *nix platform :-(

There was a time when BSD was not only relevant, but *the* platform where all of the important development was happening. Now we have three camps, each headed up by a glory-hound, and each of whom refuses to even *work* with anyone....which is why BSD is all but irrelevent now.

Being late to the BSD party, I've only used NetBSD some many years ago, and FreeBSD today (mostly for grins in a Vmware machine). Other than those problems caused by Vmware, (vmware drivers for dynamic resizing of desktop in the virtual machine) I found FreeBSD 7 (x86_64) with KDE to be the best out of the box installation for browsing windows networks (and samba) of any nix I've tried. Its utterly fast, faster than windows itself, and and faster and way more reliable than OpenSuse 10.3 at this task. Not that this is a major point, but it is interesting that this works so well and Kubuntu and Opensuse have problems in this regard. -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Randall R Schulz wrote:

On Monday 05 May 2008 20:16, Sam Clemens wrote:

...

...

akulkis@kulkis:~> file /sbin/rcnetwork /sbin/rcnetwork: symbolic link to `/etc/init.d/network'

You're slippin', dude!

Oh well.

RRS

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

John Andersen wrote:

On Mon, May 5, 2008 at 8:15 PM, Sam Clemens wrote:

...

Joseph Loo wrote:

...

I have Suse 10.1. It turns out that my wireless went down. I tried to do a ifconfig ath0 down followed by an up. It did not restart the network. If I do

/etc/init.d/network restart

will this restart the network?

Why wouldn't it?

Why? I can think of a couple reasons" If the wireless were managed by knetworkmanager for example? Or if ath0 was not set to start on boot for another example.

Thanks for answering my Q.

Surely a more helpful answer "Why wouldn't it" was possible.

In general, answers are not followed by a question mark. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org