[nas-2000] Re: extending the capabilities with linux from drive?

  • From: philipp Wehrheim <flipstar@xxxxxxx>
  • To: nas-2000@xxxxxxxxxxxxx
  • Date: Sun, 08 Jul 2007 19:44:41 +0200

Hi Felix,

Felix Mellmann wrote:
> Hey guys!
> I have now tinky running on my NAS1000, a lot of thanks to those, who made 
> that piece of work! But I'd like to go one step forward, how amazing would it 
> be, if we could get the NAS device to boot from the hdd (having a bash, 
> apache, php or even a midnight commander ;) ?!
What stops you from creating all the bins and put them into ipk's?
> I thought about the following: keep RedBoot (of course), keep the kernel and 
> the rest but tell the kernel, that the root device is /dev/hda(x).
> "rdev" on the kernel image from /dev/mtd1 tells the current used device - 
> 0x1a02, that means 0x1a for the major and 0x02 for the minor number, but 
> /dev/mtd2 (where the boot image resists) has 0x5a02, so there is a bit 
> missing .. booting from /dev/hda1 would lead into the root device 0x0301.
It is even easier all you have to do is (if you don't mind to read some
bits from flash) edit the /etc/rc script and "pivot_root" chroot or what
ever to your hd.
> I think with the original kernel image saved on my pc, and not modifing 
> RedBoot, it should be safe, trying it.
> Buuut, i have another problem, does anyone know, how to tell the kernel, that 
> it should use the serial port as its console? Furthermore, is the serial port 
> usable under linux as well? cat /proc/tty/drivers just outputs /dev/ttySL0 as 
> a serial interface ..
Yes the Port can be used under linux and you can make yourself a serial
adapter see:http://flipstar.net/myfaq ... this way you can easily follow
the bootup etc. The kernel is called with (cat /proc/cmdline)
root=/dev/ram0 rw console=ttySL0,19200 initrd=0x0800000,16M

I don't really see the benefits of booting strait from hd since there is
some flash that uses very little power and makes no noise. And after the
start (that is what tinky does) you can read additional code and stuff
from the hd /system/overlay.

The next tinky version will be allot more modular so the flashing with
every new version should go away.
If you are interested in joining the development feel invited since this
 is currently (I hate to say that) a one man show :-(


> thanks a lot in advance,
> Felix

Other related posts: