Thank you for the Sun Fire v240 support
  Home FAQ Contact Sign in
 
Advanced search
MATCHING GROUPS



more...
POPULAR GROUPS

more...

found 3 articles for 0.013 sec
Re: Thank you for the Sun Fire v240 support!     

Group: linux.debian.ports.sparc · Group Profile · Search for Thank you for the Sun Fire v240 support in linux.debian.ports.sparc
Author: Martin
Date: May 9, 2007 07:30

... <snip> On a similar note, we are considering getting a Sun Fire T1000 system. I have read...about the press with Ubuntu/Canonical + Sun - but was wondering if anyone ...the T1000, When talking to a Sun rep. they said the next ... which distro's would be supported; the rep I spoke to ... it" in to Etch, Kernel support for the T1 was added ... should stick with a sun fire V240 or if the T1000 ...
Show full article (1.19Kb) · Show article thread
Thank you for the Sun Fire v240 support!     

Group: linux.debian.ports.sparc · Group Profile · Search for Thank you for the Sun Fire v240 support in linux.debian.ports.sparc
Author: Matt Weatherford
Date: Apr 30, 2007 11:10

...Etch 4.0r0 on my Sun Fire v240 - which went without a hitch...only sticking point was that the v240 eth0 as labeled on the ..., we are considering getting a Sun Fire T1000 system. I have ... the press with Ubuntu/Canonical + Sun - but was wondering if anyone ...I should stick with a sun fire V240 or if the T1000 ... under debian Etch sparc64 SMP Thanks, Matt -- Matt Weatherford Computing Core ...
Show full article (1.34Kb)
Re: Thank you for the Sun Fire v240 support!     

Group: linux.debian.ports.sparc · Group Profile · Search for Thank you for the Sun Fire v240 support in linux.debian.ports.sparc
Author: Josip Rodin
Date: May 3, 2007 00:30

On Mon, Apr 30, 2007 at 11:02:12AM -0700, Matt Weatherford wrote: well, the only sticking point was that the v240 eth0 as labeled on the back of the machine wasnt the real eth0... it turned out I need to plug in to eth2 to get the Debian version of eth0.. an extremely minor annoyance. With three reports so far, I guess we could add this to the release notes :) Or maybe file a bug ...
Show full article (0.78Kb) · Show article thread