Dear all,
Quickie Q here:
I have to add a DTU in a remote office on a different subnet to the
sunray server.
A Cisco router will hand out the DHCP information. I think that it will
have to hand out an IP(s) for the DTU to know how to download new
firmware and authenticate to the Sun Ray serv
You're right, my apologies.
[EMAIL PROTECTED] wrote:
On Wed, 01 Mar 2006 14:25:36 -0800
Craig Bender <[EMAIL PROTECTED]> wrote:
How can that be a srss bug. hostname.* files are for hostnames only.
Sun documentation states that /etc/hostname.* file can have either an IP
address or a name as
[EMAIL PROTECTED] wrote:
Sun documentation states that /etc/hostname.* file can have either an IP
address or a name associated with that interface. If SRSS cannot cope with IP
addresses, it's a bug.
True particulary if you are going to do some advanced network
setup like IPMP
-
It also can't cope with hostname.domain or in my case IPMP entries.
Been complaining about that since 1.3.
We really need to get that fixed ;-)
We should all open bug reports at the same time so maybe it will get
patched.
Thanks,
-Steve
On Mar 1, 2006, at 2:27 PM, [EMAIL PROTECTED
I had a list of procs that are critical to the sunray running, but
that was back in 2.x days
Does anyone have a list of the process names that should always be
running on your host?
Thanks,
-Steve
___
SunRay-Users mailing list
SunRay-Users
On Wed, 01 Mar 2006 14:25:36 -0800
Craig Bender <[EMAIL PROTECTED]> wrote:
> How can that be a srss bug. hostname.* files are for hostnames only.
Sun documentation states that /etc/hostname.* file can have either an IP
address or a name associated with that interface. If SRSS cannot cope with I
How can that be a srss bug. hostname.* files are for hostnames only.
[EMAIL PROTECTED] wrote:
On Wed, 01 Mar 2006 15:33:17 -0500
Brad Lackey <[EMAIL PROTECTED]> wrote:
This error usually means that utadm is not
able to find the server's public interface.
Double check your /etc/hostname.* and
On Wed, 01 Mar 2006 15:33:17 -0500
Brad Lackey <[EMAIL PROTECTED]> wrote:
> This error usually means that utadm is not
> able to find the server's public interface.
>
> Double check your /etc/hostname.* and /etc/hosts entries.
OK, the problem was my /etc/hostname.qfe0 contained the actual IP add
This error usually means that utadm is not
able to find the server's public interface.
Double check your /etc/hostname.* and /etc/hosts entries.
BTW, Is your Sun Ray server the router on that subnet as well? If not
then you need to input the correct router.
Brad
[EMAIL PROTECTED] wrote:
"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
On Wed, 01 Mar 2006 19:25:14 +
[EMAIL PROTECTED] wrote:
> The original poster needs to sit down and figure out how he's going
> to arrange for the Sun Ray to get onto the network and be put into
> contact with its server. Chapter 7 of the SRSS Admin Guide goes
> into great detail on the var
The utadm -A will turn on DHCP options only for the SunRay specific stuff.
Or as Craig suggested, you could modify your isc-dhcpd configuration.
-Bill
[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
wher
"Brad Lackey" <[EMAIL PROTECTED]> wrote:
> You need to do a utadm -A subnet
You only need to do that if you want the Sun Ray server to provide
DHCP data to the Sun Ray. Otherwise 'utadm -L on' is sufficient.
> No you shouldn't need to touch the Xservers files.
Right, SRSS will manage the Xserve
Actually it configures vendor class options in DHCP, but not addresses,
subnet, etc.
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 M
Nope... you're right... I missed that in quickly reading your post...
Like Craig Said, Option 49 is probably your quickest bet... Point it to
you SRSS server, and you'll be off and running.
This won't facilitate any automatic firmware upgrading/etc, but it will
get the up and running.
Once y
"Jimmy Fox" <[EMAIL PROTECTED]> wrote:
> First, how does [the X11 XVideo extension] work?
Like any other X extension it expands the set of requests that
the X server understands. Applications that know about the
extension can detect its presence and can use the additional
requests it provides.
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
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.
Brad
[EMAIL PROTECTED] wrote:
You need to tell the Sun Rays where to go. Are there routers in between
the Sun Ray and the Sun Ray Server? What you've done so far is only
going to work if they are on the same segment and the Sun Ray will
exhaust other methods and find it via broadcast.
If you want a quick way, put an arra
Hi, could anyone please give me some hints on how to configure Sun Ray Server
Software.
I'm trying to set it up on shared LAN. I installed the software, then rebooted
the server, then ran 'utconfig', followed by 'utadm -L on' and then
'utrestart'. I'm not using Sun dhcpd, but instead isc-dhcpd i
Sun Ray users sign up here (SGD/Tarantella users too!)
http://www.frappr.com/sunraysgd
___
SunRay-Users mailing list
SunRay-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sunray-users
I have used the logitech mx310 with no problems.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED]
> Sent: Wednesday, March 01, 2006 9:05 AM
> To: sunray-users@filibeto.org
> Subject: Re: [SunRay-Users] USB mouse
>
>
> On Wed, 01 Mar 2
All of the mice I've tried work but with some of the wheel mice the
wheel isn't recognized. I haven't been able to get any of the extra
buttons on the 'many buttoned' mice to work
Logitech LX7 wireless works, scroller works
Logitech MX500 works, scroller works
Microsoft Trackball explorer works
On Wed, 01 Mar 2006 07:55:12 -0800
Craig Bender <[EMAIL PROTECTED]> wrote:
> Most USB Keyboards and mice work just fine. Just plug it in a give it a
> shot.
Well I'd have to buy one first to give it a shot :-) But everyone says it
should work, so it's good news.
Most any USB mouse has worked for me. I prefer a scroll mouse.
> Hi, I have Sun USB keyboard for Sun Ray, but no mouse. Will any USB mouse
> work, or does it have to be from Sun?
> ___
> SunRay-Users mailing list
> SunRay-Users@filibeto.org
> http://w
Any HID compliant USB mouse should work just fine... Some newer mince
are only recognized with the 3.1 firmware.
Brad
[EMAIL PROTECTED] wrote:
Hi, I have Sun USB keyboard for Sun Ray, but no mouse. Will any USB mouse work,
or does it have to be from Sun?
__
Most USB Keyboards and mice work just fine. Just plug it in a give it a
shot.
[EMAIL PROTECTED] wrote:
Hi, I have Sun USB keyboard for Sun Ray, but no mouse. Will any USB mouse work,
or does it have to be from Sun?
___
SunRay-Users mailing list
SunR
Hi, I have Sun USB keyboard for Sun Ray, but no mouse. Will any USB mouse work,
or does it have to be from Sun?
___
SunRay-Users mailing list
SunRay-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sunray-users
28 matches
Mail list logo
