Re: Reinstalling debian on n2100

2008-04-20 Thread Martin Michlmayr
* Andrew Haswell [EMAIL PROTECTED] [2008-04-16 23:46]:
 How do i go about reinstalling? do i need to revert to the thecus rom or can
 i reinstall debian another way?

You can flash the installer directly from withing Debian without
installing the original Thecus firmware.  Just follow
http://www.cyrius.com/debian/iop/n2100/deinstall.html but use the
debian-installer .bin file instead of the one from Thecus.

 I have a 10GB raid1 root partition and the rest are data partitions
 so i would like to know if i can reinstall whilst keeping my data
 safe.

You can do that when you skip the guided partitioner.
-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



2 Disks (by label/UUID)

2008-04-20 Thread Stuart Read
Hello,

I was preparing to add a second harddisk to my NSLU2, and since
previous messages on this list referenced a boot order problem with
this, I followed the directions on the wiki (and some previous
messages on this list).

I have two questions:

1) Why does the troubleshooting page on the wiki say that the UUID
method there is no good when that's the method suggested on this list
by Martin M. et al?

2) After updating the flash, the NSLU2 failed to boot (orange LED) so
I had to restore my old fstab and flash to get it booting again. Is
there a step besides updating fstab, creating a new initramfs, and
flashing it?
 I noticed that in /etc/initramfs-tools/conf.d there is a file named
resume which references /dev/sda5 (which is the swap). Could this be
the problem?

Let me know if there's more info required. I'm running a (mostly
up-to-date) lenny system.
-Stuart


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Puzzling difference between debian-arm and debian-i386 re growisofs

2008-04-20 Thread Rick Thomas


On Apr 18, 2008, at 1:14 PM, Barry Tennison wrote:



So I think it's definitely in the genisoimage -M code, and COULD BE  
an endian issue there.




For what it proves, if anything, I tried to recreate the bug


cd somewhere safe
mkdir tmp1
touch tmp1/nullfile-with-long-name
genisoimage -R tmp1/ RR-arm-1.iso
# note: this succeeds, and then RR-arm-1.iso will loop-mount perfectly
#  well with Rock Ridge active, so nullfile-with-long-name shows with
#  the right name
genisoimage -M RR-arm-1.iso -C 0,0 -R tmp1/ RR-arm-2.iso



on a PowerMac G3 running Etch, and had no errors at all.  So simple  
endian-ness bugs seem less likely.  Complex bugs (endian or  
otherwise) are still possible, of course.


Enjoy!

Rick


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]