![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Updates and Perplexities
Jul. 29th, 2006 10:36 amLooks like the partition and boot record weirdness has indeed been solved. I had some Fedora Core 5 CDs on hand so that's what I installed. grub installed in the MBR without complaint. I am happy about that; the trials of the past week haven't been in vain. Finally I can have my dual boot to Windows and Linux on this machine again! Sadly though, every silver lining has a cloud with the potential for thunderstorms.
I use a Syslink NSLU2 as a file server. I was a little perplexed when it locked up while I was trying to access it to move a few things over to my new FC5 install. After getting it back up and ensuring it was working fine I got back to getting FC5 set up with my favorite applications. Then later I tried to access it from FC5 again and, lo and behold, the file server crashed again.
This is the first time I've ever had this problem, even with an earlier version of Fedora. I've been accessing the NSLU2 from a machine running FC 4 for a while with no problems. I've yet to determine what FC5 is doing that boggles the NSLU2 or why the NSLU2 is so sensitive to whatever it is. At this point I suspect some sort of protocol mismatch or something along those lines. For the time being it's clear that the NSLU2 and FC5 don't play well together.
I use a Syslink NSLU2 as a file server. I was a little perplexed when it locked up while I was trying to access it to move a few things over to my new FC5 install. After getting it back up and ensuring it was working fine I got back to getting FC5 set up with my favorite applications. Then later I tried to access it from FC5 again and, lo and behold, the file server crashed again.
This is the first time I've ever had this problem, even with an earlier version of Fedora. I've been accessing the NSLU2 from a machine running FC 4 for a while with no problems. I've yet to determine what FC5 is doing that boggles the NSLU2 or why the NSLU2 is so sensitive to whatever it is. At this point I suspect some sort of protocol mismatch or something along those lines. For the time being it's clear that the NSLU2 and FC5 don't play well together.
