On Thu, May 07, 2015 at 04:29:11PM -0500, Ian Pilcher wrote:
On 05/06/2015 02:00 PM, Josh Boyer wrote:
>On Wed, May 6, 2015 at 2:53 PM, Jarod Wilson <jarod(a)redhat.com> wrote:
>>One other thought: what happens when /boot is on the same file system as
>>/usr and/or /lib? Does the file get unnecessarily copied, or is it
>>hardlinked or _____?
>Copied as far as I know. Yes it's slightly inefficient, but worrying
>about that case (which isn't default at all) seems kind of pointless.
Hmm. If don't know off the top of my head if Fedora cloud images have a
separate /boot or not, but disk space is a big concern in such
You could also argue simplifying package maintenance and sysadmin stuff is a
big concern for throw away cloud images. ;-) With a change like this you
could almost throw away /boot and regenerate it on the fly. :-)
As I stated in another thread, it is hard to know what interesting things
you could do with this approach if you don't play around with it.
Maybe if you detect /boot is on the same partition as /usr you go completely
nuts and symlink the kernel images to the /usr/lib/modules ones (or maybe
just /lib if /lib/modules hasn't moved to /usr/lib/modules yet).