"Craig Bender" <[EMAIL PROTECTED]> wrote:
> Actually it configures vendor class options in DHCP, but not 
> addresses, subnet, etc.

'utadm -A' will do all of that, if you tell it to.  '-A' can do
almost everything that '-a' can do.  The distinction is that '-a'
tells SRSS that you're configuring a dedicated Sun Ray interconnect
while '-A' tells it that you're configuring a subnet on your shared
intranet.  The tiny divergences in behaviour between '-a' and '-A'
all stem from that distinction.  Those divergences include:

  * '-a' wants an interface name because it wants to ensure that
    the interconnect really does meet the requirement of being 
    directly attached to this machine.  '-A' just wants a subnet
    number, it doesn't care about interfaces because it knows that
    the subnet may not be directly attached, it understands that 
    the subnet will be reachable through the magic of IP routing.

  * '-a' will let you specify a netmask because the interconnect
    is a local concern.  Maybe you're doing something that clashes
    with an enterprise-wide (eg NIS) netmask setting but that's OK 
    because the interconnect is private and doesn't have to match 
    any enterprise-wide settings.  '-A' won't let you override a 
    netmask locally because it knows that the rules for this subnet
    should be consistent across the intranet, and giving this host
    its own unique notion of this subnet's netmask is bad juju.  
    Of course you can trick '-A' by vi'ing /etc/netmasks yourself,
    but '-A' will not abet you in that kind of tomfoolery.

  * '-A' has the side effect of performing '-L on'

Those are the big ones.  I've probably missed a couple.

Brad (assuming you read this far without being driven into sleep):
what's missing from the Admin Guide discussion, other than a properly 
integrated explanation of the DNS/TFTP changes introduced in 3.1?

OttoM.
__
ottomeister

Disclaimer: These are my opinions.  I do not speak for my employer.


> But you don't need that (it's a good idea for a variety of reasons 
> though), -L on is typically fine.  But you need to tell the Sun Ray 
> how to get there.  Try option 49.
> 
> [EMAIL PROTECTED] wrote:
> > On Wed, 01 Mar 2006 13:59:27 -0500
> > Brad Lackey <[EMAIL PROTECTED]> wrote:
> >
> >> You need to do a utadm -A subnet
> >>
> >> where subnet is the subnet of the interface of the SRSS server 
> >> on which the Sun Rays are going to connect.
> >>
> >> utadm -A 192.168.0.0
> >>
> >> It will do all of the configuration for you...
> >>
> >> No you shouldn't need to touch the Xservers files.
> >>
> >
> > Well 'utadm- A' would configure dhcp service and turn on lan 
> > connections. I'm not using Sun dhcpd, instead I'm using 
> > isc-dhcpd, this is why I ran 'utadm -L on' instead. Or did I get 
> > this completely wrong?
> > _______________________________________________
> > SunRay-Users mailing list
> > [email protected]
> > http://www.filibeto.org/mailman/listinfo/sunray-users
> _______________________________________________
> SunRay-Users mailing list
> [email protected]
> http://www.filibeto.org/mailman/listinfo/sunray-users

>


-- 
___________________________________________________
Play 100s of games for FREE! http://games.mail.com/

_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

Reply via email to