John Desmond wrote: > > --- "Michael D. Schleif" <[EMAIL PROTECTED]> wrote: > > > > John Desmond wrote: > > > > > > --- "Michael D. Schleif" <[EMAIL PROTECTED]> wrote:
[ snip ] > > I believe that (additional) ramdisks are created > > *after* root.lrp is > > unrolled; but, *before* anything goes into /var/log > > or /tmp. > > But how does LRP know to install ramdisk.lrp and > execute the included bootup file before any of the > other .lrp's that depend on it? *I* didn't tell it to! I don't know about sequence and race conditions; but, without ramdisk/ramlog.lrp, /var/log will be empty on bootup -- until up comes the network and stuff happens and logs are created. Same goes for /tmp . . . > Which brings up another question that's been nagging > at me ever since I installed ramdisk.lrp to put > /var/log on it's own: why do I need ramdisk.lrp, > anyway? The whole LRP-thing is operating out of a ram > drive! Can't a second ramdrive be specified in > /etc/fstab mounted at /var/log? Is it a different kind > of ramdrive? Anybody know? If your logs go crazy and expand they can consume the entire filesystem on which they reside. If you have only ram0, that is the filesystem that will fill up. If ram0 fills up, then the operating system *cannot* operate, because to do something new, it needs memory in which to do it. Placing /var/log on ram1 gives your logfiles limited space in which to expand. Even if ram1 fills up, the operating system can continue to operate . . . -- Best Regards, mds mds resource 888.250.3987 Dare to fix things before they break . . . Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
