Ian said...
> Because, after the Kernel, you don't get a lot of Linux software into > 512Kilobytes :-) > (DoC Millenium (32pin) houses 8 Megabytes, FYI) and then added... > The biggest drama with booting to a Linux OS on a HDD is that not all of > the boards under LinuxBIOS have their IDE hardware initialized properly > (since quite a few people here run solely from the DoC in the BIOS > socket) -- the upshot of this is that you can have a running multiuser > system in 3seconds, but no harddrive(s) to play with ;-) Polite cough, since I'm probably about to ask a dumbass question. I don't know the detailed pros and cons of IDE flash vs. DoC, I've tried to divine the details from the past correspondence of this list. Do the problems apply to solid state IDE? e.g. <http://www.web-tronics.com/webtronics/ideflasdison.html>. It's not clear to me whether the problems are due to the spin-up time of the hardware or other IDE initialisation details. One advantage of IDE over DoC is that it's trivial to initialise on any hardware. I probably wouldn't want to change the kernel and minimal root that often, but I might want to update other software frequently. So one might have a kernel+root in a DoC, and then an application on an IDE drive. Boot/install mechanisms recently became a much hotter topic here, and by coincidence, a colleague has just taken delivery of a Sis630 based Asus Terminator micro-tower diskless system for just under �200 ex VAT (it was a "Today Only" from scan.co.uk, if anyone's interested). So, I'm hoping that we might start looking at LinuxBIOS in the near future. :) If the 630 support described at <http://www.acl.lanl.gov/linuxbios/news/index.html> is still correct, I need NO special DoC socket on my mainboard, yes? Even to flash it? -- Peter Lister, Sychron Inc. - 1-866-SYCHRON Intelligent Infrastructure - www.sychron.com
