Fedora 12 updates or Fedora 13?

[Lamar Owen]

Just a ping to see how this was coming along.

[Hans Witvliet]

On Mon, 2010-07-12 at 17:14 -0400, Lamar Owen wrote:
pong

[Dennis Gilmore]

On Monday, July 12, 2010 04:14:58 pm Lamar Owen wrote:
>  Just a ping to see how this was coming along.
>  _______________________________________________
>  sparc mailing list
>  sparc(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/sparc 
We hit a bug in qemu that
corrupted the /mnt/koji filesystem.  I need to spend 
some time to piece it all back together. ive just not yet found that time.

Dennis

[xmechanic]

On 7/12/2010 4:44 PM, Dennis Gilmore wrote:
>  We hit a bug in qemu that corrupted the /mnt/koji filesystem.  I need
> to spend
>  some time to piece it all back together. ive just not yet found that time.
>
>  Dennis
>     
>  _______________________________________________
>  sparc mailing list
>  sparc(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/sparc
>      
Not sure what kind of luck/stability others have been having, but it 
seems whenever I try to do any updates
on my 280R, it ends up with missing dependencies and ultimately breaking 
something to the point of not being
able to boot the machine again.  It's working fairly well now after the 
3rd install with KDE instead of Gnome
for the VNC desktop. Reboots are still iffy, but after a couple of trys, 
it will eventually load and everything
(i.e. httpd, php, mysql, vsftp, samba, SSH, and KDE via VNC server) are 
all working. Maybe Fedora 13 will
clear up the boot issues and make it a bit more stable?

Dave Land
This message originated from Land Computer Service at 65.113.122.252

[Lamar Owen]

On Jul 12, 2010, at 6:44 PM, Dennis Gilmore wrote:

>  On Monday, July 12, 2010 04:14:58 pm Lamar Owen wrote:
> > Just a ping to see how this was coming along.
>  We hit a bug in qemu that corrupted the /mnt/koji filesystem.  I  
>  need to spend
>  some time to piece it all back together. ive just not yet found that  
>  time. 
Bummer.  I know what you mean about finding time, or rather the lack  
of it.

Just knowing this helps somewhat.  Thus far, our Blade 1000 has been  
up for, uh:
[root@sb1k-1 ~]# uptime
  21:40:09 up 58 days,  2:35,  1 user,  load average: 0.00, 0.00, 0.00
[root@sb1k-1 ~]# uname -a
Linux sb1k-1.pari.edu 2.6.32.10-90.fc12.sparc64 #1 SMP Thu Apr 15  
13:30:40 CDT 2010 sparc64 sparc64 sparc64 GNU/Linux
[root@sb1k-1 ~]#

The E6500 is down at the moment; until it's somewhat more stable,  
especially on boot, it's not worth the power consumption to keep it  
up.  But it's available for a build host should the need arise.