> | > |Well, from my expirience I can say that actually you can use > |/boot, swap and /. Three partitions is enough. The more partitions > |you create, the less flexible your system is. > > That depends. If you want to secure your system by having a read-only /etc > and /sbin, but you must have a rw /tmp and /var, then you've got to have > separate partitions. In this case, more partitions = more flexibility.
Well, looks like we use the word flexibility in a different way. That's not a surprise for me since English is my second language. You can make /etc and /sbin read-only, but what's the reason? 1. Isn't just setting proper access writes is enough to protect /etc and /sbin? And what makes it good these filesystems are already more or less protected after installation, so you don't have to do anything about it. 2. Aren't it a little bit annoying to remount your /etc and /sbin each time your want to reconfigure your system or install something new (possibly rebooting your system)? And I think you have to remount /etc quite often. Besides what happens if user decides to change his password? ------------------------------------------------------- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.openprojects.net
