On Sat, 2010-02-20 at 13:13 +0100, edgar.sol...@web.de wrote: > >> > >> well, How about one big additional storage package then? Additionally > >> enabling swapon and blkid from busybox? > >> This also makes it easier to maintain. There is enough stuff already in > >> base files. > > > > One or two packages is the solution we'll be going for, with swapon and > > blkid enabled in busybox. This makes things a whole lot easier in terms > > of the code as well as the packaging. > > This is very close to your current packaging. You probably want to make > these changes yourself?
Working on it now. > I'm making that an optional feature. But the recommended way for most > > users is to boot a normal jffs2-based session (which is also the > > fallback in case of problems mounting the external rootfs) and use the > > scripts I will be writing, to initialize the rootfs, and then reboot > > into the rootfs. > > > > How about a fs label "openwrt-root-ext2"? The fs suffix can tell what fs > the block device is, and does not have to be ext2. > Also the user obviously has to name the fs, what he wouldn't do if he > didn't want the device to be an openwrt-root, so he can be explained. The biggest problem isn't being able to boot with a predefined rootfs, but making sure it has the right files for the image that's just been flashed (for instance). At some point preparing the filesystem has to be done, and it has to be loaded with the right binaries for the image that will be booting. This is trickier than it sounds if you want to be safe about it. > "If a device with a partition named 'openwrt-root-<fs>' (e.g. > openwrt-root-ext2) is found during boot, openwrt will try to changeroot > into it." > > Something like that. Certainly a label or uuid is possible, but the problem isn't convincing OpenWRT to boot into a rootfs, but making sure the rootfs has the appropriate binaries. That's why even if I use something like this for the autoconfigured rootfs (that basically does with a usb rootfs what now happens with jffs), it won't be the default - Not wiping at the wrong time and only on a flash is trickier than it sounds. > And one other thing. Why don't you put extroot in > buildroot/package/block-extroot. It seems pretty core to me :) and this > way the connection to block-mount is more obvious. Hmmmm....depends on what the core devs say...I did it as a package because I have commit rights to the packages but not core OpenWRT. > Nice work, ede Thank you. Regards, Daniel -- And that's my crabbing done for the day. Got it out of the way early, now I have the rest of the afternoon to sniff fragrant tea-roses or strangle cute bunnies or something. -- Michael Devore GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C http://gnupg.org The C Shore (Daniel Dickinson's Website) http://cshore.is-a-geek.com
signature.asc
Description: This is a digitally signed message part
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
