On Tue, Oct 18, 2011 at 4:13 PM, Steven S. Critchfield wrote: > Net booting is nothing special if your netcard supports it. > > Trouble with a local cache would be how would you know > when the central image changed? Essentially, if you cached > a local copy and are not the only one accessing the > filesystem, you do not know when the remote file changed.
Sure it is. You just need to check the mtime of the file on the server, verifying it against the cached mtime of the file when it was last retrieved (or last saved to the server). > Normal cache and swap would handle most of the > problems you would have. Most used apps would be cached > the same as if it had been a local filesystem. Given time and > memory starvation, it will cycle out until needed again. That covers it for a normal boot cycle, but upon reboot, swap would be wiped, and you'd have to start over again. I see a certain beauty in the design of that Sun system. Given how cheap disks are nowadays, and the danger of a central point of failure, however, I don't see a particularly great reason to reimplement it. -Tilghman -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en
