PBG4 emphasizes an excellent point: devices sold as SSDs are much much better at wear management than devices sold as USB sticks. To which I would add that even if you find a USB stick that works well, the probability is extremely high that just when you get comfortable with it, the manufacturer will change the firmware/controller/flash vendor, and new versions will behave differently (and usuallby Malc - Debian
Although this is only a minor point, the reason that your (U-Boot) netconsole appears to halt at "Starting kernel" is that at that point U-Boot is done, and with it the netconsole functionality. The next stage is the ksyslog output from the kernel, which will go to a memory buffer. However, the Debian standard initramfs allows the Linux "netconsole" functionality, which wiby Malc - uBoot
One interesting point to note: at least some of these devices (e.g. the Pogoplug V4) have SLC NAND: the part in the Pogo4 is a Hynix HY27UF081G2M, which offers an endurance of 100,000 program/erase cycles, which is much more than almost all commercial USB sticks. So if you had, say, the 112MB of filesystem on a Pogo4 and chose to use that with a UBIFS filesystem, you would have a device to whiby Malc - Debian
Bodhi, I'm interested in trying to get some kind of union filesystem working, and would prefer to build on your kernels rather than from scratch! Would I be right in thinking that you are taking the upstream (kernel.org) kernel, applying the patches (that you include in the distribution), building according to the config file (also included)? This is all a bit new to me, although Iby Malc - Debian
After a couple of years of prevarication, I have finally got around to producing a U-Boot for the Pogo V4 that I'm vaguely happy with. It is similar to the ALARM version, in that it is based on the stock 1.1.4 sources, but it goes a little further. Background and Philosophy What I want is a U-Boot that will reliably load Debian and support the SATA interface in that environment. Thiby Malc - uBoot