Bug#562205: closed by Ben Hutchings <ben@decadent.org.uk> (Bug#562205: fixed in linux-2.6 2.6.32-3)
On 27/12/2009 10:20, Martin Michlmayr wrote:
You like crying over spilt milk, don't you?
Probably as you like breaking other hardware inadvertently...
We support a lot of NAS
devices and I cannot test every single change on every device.
You should. You cannot rely on every single users having a serial console!
Installing a serial console:
1) requires hardware knowledge that many people do not have (including
me as a friend did the mechanical and soldering for me),
2) Voids the warranty,
If you are reading the Dlink DNS323 wiki, yo know that many people are
rather unhappy with the support dlink provides for official firmware.
You cannot expect having all theses people installing a serial cable.
I assure you that the debian instable code is much better than the
original dlink ones (except the always flashing blue led that really
annoys me...)
The
DNS-323 is very low priority for me. If you want to volunteer testing
kernels on this machine, you're welcome.
You know the rule: "if it ain't broke don't fix it" especially if you do
not know if kexec works or if loading the flash driver as a module after
boot will indeed give back access to the mtd devices...
If you change something on embedded devices with no software only
recovery options, you should rather waste a bit time to test your
change. Anyway, security problem (the main driver for rushing 32 I
guess) are unlikely to affect that much people on theses devices.
I'll send you a uKernel and uRamdisk in about 7-10 days and then you
can follow
http://www.cyrius.com/debian/orion/d-link/dns-323/recovery.html
Ok thanks. Happy holliday and happy new year then.
-- eric
Reply to: