On Sat, Dec 16, 2017 at 01:06:16PM -0500, Temlakos wrote: > On 12/16/2017 10:13 AM, fred roller wrote: > > [snip] > > | I now ask the community for some suggestions. > > > > I have done this type of set up on my systems before so what its worth I > > will share how I installed and where applicable, why. > > > > | First, for partitioning: > > | > > | 1. Should I even try to accept /automatic/ partitioning when the > > installer gets to that point? > > No. In custom choose the 120 GB drive and auto choices may be fine but > > mine was to mount /boot, /swap, /tmp, and /. For reasons related to HDD > > and rpm's that was the order; for SDD not so much. The second drive I > > mounted on /Crypt [or some other name you want]. > > What do you recommend as the sizes of partitions /boot and /tmp? Obviously > "/" will take up "all the rest." /swap will take up 16 GB. I used 50 GB for > /boot. But I never broke out /tmp as a separate partition. overkill. I've seen mny recommend 1GB for /boot. I usually do 2-4GB. Just looked at 3 systems, highest /boot usage was < 350MB. If no separate /tmp, it can autofs to 50% of swap. You can have swap on multiple drives. Thus either greater total swap or more space on 120 drive for / or /tmp. lost+found should be empty. It is used by fsck program to reattach orphaned files it finds (files with an allocated inode and data blocks but no directory entry). If found fsck attaches them in l+f named "#<inode number>". Root can then examine them and move or remove. l+f is created as part of file system formatting. -- Jon H. LaBadie jonfu@xxxxxxxxxx _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
