On a new 11.0 system that was installed with just defaults, many of the yast
configuration tools were not present, at least under network services.
Included were http, nfs server, nfs client. Going to software management,
I installed apache2, nfs server, and nfs client. Still no configuration
tools. I had to go back to software management and then manually install
the configuration tools.

Shouldn't these be auto-included as a depency? Or present on any minimal
instll?

John

On 2008-07-14, John Bowling <johnlb2002@cox.net> wrote:
> On a new 11.0 system that was installed with just defaults, many of the yast
> configuration tools were not present, at least under network services.
> Included were http, nfs server, nfs client. Going to software management,
> I installed apache2, nfs server, and nfs client. Still no configuration
> tools. I had to go back to software management and then manually install
> the configuration tools.
>
> Shouldn't these be auto-included as a depency? Or present on any minimal
> instll?
>

YaST >Software > Search >yast2this and yast2that and so on...


Vahis
--
Training new things here:
http://waxborg.servepics.com/gallery/v/helsinki/
"The only thing more expensive than training is the lack of it"
Henry Ford

John Bowling wrote:

> On a new 11.0 system that was installed with just defaults, many of the
> yast configuration tools were not present, at least under network
> services.

Hi John,
Almost same problem here - even if all relevant YaST modules seem to be
installed, no way to configure network cards. Thankfully, eth1 was
autoconfigured. Any hints?

My System Intel Core2 Duo with SuSE 11.0 x_64

Hendric
--
Hendric Stattmann, Mödling, Austria. Registered Linux User #178879
For e-mail contact, please use <hendric.stattmann.yyyy-mm@kabsi.at>

John Bowling wrote:
> Shouldn't these be auto-included as a depency? Or present on any minimal
> instll?

No.

houghi
--
You are about to enter another dimension, a dimension not only of
sight and sound but of mind. A journey into a wondrous land of
imagination. Next stop, Usenet!

Hendric Stattmann wrote:

> Almost same problem here - even if all relevant YaST modules seem to be
> installed, no way to configure network cards. Thankfully, eth1 was
> autoconfigured. Any hints?

Got it! Now everything put together in Network Devices -> Network Settings
Looks like its time for a break...

[SOT]
General first impression of 11.0_x64 vs 10.3_i386: very quick install,
significantly faster overall, YaST scanner setup messed up (will file bug
report as soon as I can trace the cause), flash working, but regularly
crashing (like before).
[/SOT]

Greetings,
Hendric
--
Hendric Stattmann, Mödling, Austria. Registered Linux User #178879
For e-mail contact, please use <hendric.stattmann.yyyy-mm@kabsi.at>

Hendric Stattmann wrote:
> Almost same problem here - even if all relevant YaST modules seem to be
> installed, no way to configure network cards. Thankfully, eth1 was
> autoconfigured. Any hints?

YaST, Network Devices, Network Settings. This will do the same as being
root and doing `yast2 lan`

houghi
--
You are about to enter another dimension, a dimension not only of
sight and sound but of mind. A journey into a wondrous land of
imagination. Next stop, Usenet!

houghi <houghi@houghi.org.invalid> wrote:
>John Bowling wrote:
>> Shouldn't these be auto-included as a depency? Or present on any minimal
>> instll?

>No.

Again I disagree. When the ability to use the network is loaded,
the Yast tools to manage it should be as well. And if I recall
correctly, they were in my case.

When I loaded Apache2, I got the Yast management module loaded
alng with it. Same with the mail server.

--
--- Paul J. Gans

John Bowling wrote:

> On a new 11.0 system that was installed with just defaults, many of the
> yast configuration tools were not present, at least under network
> services.
> Included were http, nfs server, nfs client. Going to software management,
> I installed apache2, nfs server, and nfs client. Still no configuration
> tools. I had to go back to software management and then manually install
> the configuration tools.
>
> Shouldn't these be auto-included as a depency? Or present on any minimal
> instll?
>
> John

Go in yast and manage software then search by repos then search for yast and
install the network services module
--
Michael S. Dunsavage

Paul J Gans wrote:
> houghi <houghi@houghi.org.invalid> wrote:
>>John Bowling wrote:
>>> Shouldn't these be auto-included as a depency? Or present on any minimal
>>> instll?
>
>>No.
>
> Again I disagree. When the ability to use the network is loaded,
> the Yast tools to manage it should be as well. And if I recall
> correctly, they were in my case.
>
> When I loaded Apache2, I got the Yast management module loaded
> alng with it. Same with the mail server.

Ok, I select all the YaST things anyway. I just thought that John
Bowling was correct and I just followed what he said without
verification.

houghi
--
> Beware of he who would deny you access to information, <
> for in his heart he dreams himself your master. <
> Commissioner Pravin Lal: "U.N. Declaration of Rights" <

On Tue, 15 Jul 2008, Paul J Gans wrote:-

<snip>

>Again I disagree. When the ability to use the network is loaded,
>the Yast tools to manage it should be as well. And if I recall
>correctly, they were in my case.

It all depends on how you go about picking the packages that provide the
various network services. If you pick the individual packages, you're
not going to get the unnecessary and fake dependencies[0] where a
package "depends" on the YaST module.

>When I loaded Apache2, I got the Yast management module loaded
>alng with it. Same with the mail server.

But did you select the individual Apache2 packages, or did you pick the
"Web and LAMP" pattern? You only get the YaST admin module by default if
install it by selecting the pattern. If you don't pick the pattern, you
don't automatically get the module.


[0] And yes they would be fake dependencies. While they may be useful
and make things easier while maintaining a configuration, they aren't
required to either configure or use the package.

Regards,
David Bolt

--
www.davjam.org/lifetype/ www.distributed.net: OGR@100Mnodes, RC5-72@15Mkeys
SUSE 10.1 32 | | openSUSE 10.3 32bit | openSUSE 11.0 32bit
| openSUSE 10.2 64bit | openSUSE 10.3 64bit | openSUSE 11.0 64bit
RISC OS 3.6 | TOS 4.02 | openSUSE 10.3 PPC | RISC OS 3.11