5 ms·
> With the merged /usr directory we can offer a read-only export of the vendor supplied OS to the network, which will contain almost the entire operating system
by dietrichepp 4y ago
> With the merged /usr directory we can offer a read-only export of the vendor supplied OS to the network, which will contain almost the entire operating system resources.
Back in 2005 or 2006, I made a Linux that exported the filesystem this way, and it worked by mounting / as a network volume. This worked by doing a particular dance with "pivot_root" at the beginning and a union mount with a tmpfs volume. We used it to play LAN games in the computer lab. Because the network booting Linux didn't touch the local hard drive, you could clean up after yourself just by shutting down the machines. It was also nice and fast, because the machines all had gigabit ethernet and the file server was serving from cache most of the time. It ended up being noticeably better than running off local hard disk... this was the era before SSDs took over, obviously.
- colechristensen 4y agoYeah mounting large amounts the filesystem read only over the network was a pretty common thing to do in large environments.
- hinkley 4y agoI got a couple extensions on homework assignments in college on account of the entire computer lab being dead because Solaris and NFS getting into a cage match with each other. The admins had to restart things Apollo 13 style.
- froh 4y agoit was.also used to share /usr in a large number of virtual guests. large as in thousands of guests, for example "your personal web server with root account and perl/php" running on a s390x mainframe.