On 06/21/2014 12:46 AM, Andrey Borzenkov wrote:
В Sat, 21 Jun 2014 01:20:41 +0200 "Carlos E. R." <robin.listas@telefonica.net> пишет:
On 2014-06-20 22:34, Tony Alfrey wrote:
If I just define a bootable /boot partition and / partition, will the installer know what to put in each?
Of course.
However, you do not need a boot partition, except on some specific situations - and you have not described any of those being your case (some types of RAID, LVM...)-
Having separate /boot with simple filesystem like ext2 is more robust. I have seen cases when grub failed to read ext4 after unclean shutdown because it does not use journal replay.
+1 Perhaps in the days of 10M disks allocating a 'big enough but not too big' partition for /boot (and others) was problematic. Now Resource management isn't as much of an issue, no need to be parsimonious. Stability and reliability is everything in a production system. Yes, I've experimented with 'all one file system' with an early iteration of BtrFS. It was great until ... That early of version had a hiccup. I replaced it with one that had a small (200M) /boot and a slightly later version of BtrFS. Paranoia (or diligence) aside, tat later version of BtrFS was solid. But experimentation is one thing. I have BtrFS as the / file system on another machine with no problems. But I'd still advise a /boot on ext2 -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org