from discussion here appears pinet close want do, except not pi's boot option collection of windows pc labs. valuable hear experience reasoning behind approach taken pinet , trade off between alternative approaches.
in past i've experimented mounting squashfs image of live boot disk on network. live boot uses aufs, unionfs or overlayfs obtain read-write file system placing writable overlay in ram. however, not practical machines limited memory. similar issue has overcome pinet, i'm hoping benefit knowledge.
i'm wondering, writable overlay pinet in ram or mounted on server? swapping network swap out ram disk?
there thousands of computers on campus, though 40 or 50 ever simultaneously used linux. pinet-like system include enough security/encryption work on campus area network? pinet server need configured each client, or can server create swap , writable overlays on as-needed basis. also, how prevent 2 pi's mounting same network swap mistake or intent?
in past i've experimented mounting squashfs image of live boot disk on network. live boot uses aufs, unionfs or overlayfs obtain read-write file system placing writable overlay in ram. however, not practical machines limited memory. similar issue has overcome pinet, i'm hoping benefit knowledge.
i'm wondering, writable overlay pinet in ram or mounted on server? swapping network swap out ram disk?
there thousands of computers on campus, though 40 or 50 ever simultaneously used linux. pinet-like system include enough security/encryption work on campus area network? pinet server need configured each client, or can server create swap , writable overlays on as-needed basis. also, how prevent 2 pi's mounting same network swap mistake or intent?
raspberrypi
Comments
Post a Comment