Re: Solaris 9 x86 on a heterogenous domain - domain cannot be ascertained
From: S. Anthony Sequeira (tony_at_sequeira.com)
Date: 06/22/04
- Next message: S. Anthony Sequeira: "Re: Solaris 9 x86 on a heterogenous domain - domain cannot be ascertained"
- Previous message: slrn: "Re: getting solaris 9 for intel, Help needed !?"
- In reply to: Juhan Leemet: "Re: Solaris 9 x86 on a heterogenous domain - domain cannot be ascertained"
- Next in thread: S. Anthony Sequeira: "Re: Solaris 9 x86 on a heterogenous domain - domain cannot be ascertained"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 21 Jun 2004 23:07:58 +0100
On Mon, 21 Jun 2004 02:52:36 -0200, Juhan Leemet penned:
> Putting dns in there will solve only the host naming problem. I wonder if
> that is enough for the OP, or whether he will also (eventually? soon?)
> need other network lookup services? I would still recommend setting up nis
> (or nisplus, or ldap, if you're more ambitious). This can be used to
> align uid,gid over all machines in his domain, to ensure that nfs
> (permissions) work right. It can also provide automounter maps, etc.
It's a small home network. FreeBSD, Gentoo and Debian Servers. Linux Win
XP Home and LFS (2) clients. DNS works fine, except for this part of the
system. I do not wish to start playing with NIS(+)/LDAP or the like until
the system has stabilised.
>
> BTW, it seems to me this is really hard slogging, but maybe someone is
> trying to do it laboriously, by hand, to learn how it is all assembled.
> Personally, I have found that it all gets setup automagically by
> choosing the right networking options during the initial install, or by
> executing sys-unconfig (to redefine the networking stuff, or none). But
> then, I have already setup a working Solaris NIS server, to which the
This is probably what is lacking, a Solaris master network server of some
kind. I have a spare machine, and decided to see what Solaris could do
for me. Believe me it has been a hard slog. I have reinstalled many
times, used sys-unconfig many times too. I have several issues which are
easier solved using Linux or FreeBSD, but I'm not about to let an OS beat
me.
> installation process can refer, and determine a number of things
> required for the networking configuration. Perhaps setting up nis might
> be a good idea?
See above.
> How big is the domain? Only 2 machines? Several machines? Will it grow?
See above. I don't see it growing appreciably, OTOH I may just win the
lottery ;)
> I've also started doing my (re)installs using jumpstart. After
screwing
> up the courage (seems daunting at first?) it turns out to be so easy,
> and you don't have to do the CD shuffle. I let it fall back to console
> interaction.
>
> After beating one's head against a wall, it feels good to stop.
>
> p.s. In Solaris9 there is a /etc/nsswitch.dns template file already
> defined. If dns is really all you want, then just copy that template to
> /etc/nsswitch.conf, which IIRC would be done for you if you had selected
> the appropriate installation options.
See my previous posting. The problem is that DNS is good enough for most
other things just not the Solaris Management Console.
Cheers.
-- Tony Experience is directly proportional to the cost of the equipment ruined.
- Next message: S. Anthony Sequeira: "Re: Solaris 9 x86 on a heterogenous domain - domain cannot be ascertained"
- Previous message: slrn: "Re: getting solaris 9 for intel, Help needed !?"
- In reply to: Juhan Leemet: "Re: Solaris 9 x86 on a heterogenous domain - domain cannot be ascertained"
- Next in thread: S. Anthony Sequeira: "Re: Solaris 9 x86 on a heterogenous domain - domain cannot be ascertained"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
