Re: [PATCH] kernel.spec: no more files in /boot

2015-05-08 Thread Don Zickus
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 ja...@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
 environments.

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).

Cheers,
Don
___
kernel mailing list
kernel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/kernel

Re: [PATCH] kernel.spec: no more files in /boot

2015-05-08 Thread Reindl Harald


Am 08.05.2015 um 16:51 schrieb Don Zickus:

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 ja...@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
environments.


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. :-)


invalid argumentation because if you follow that statement you could say 
throw away all computers at all


but to keep on topic: copy the kernel files to the system partition 
perverts the recent improvement of kernel-core / kernel-modules



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.


interesting things?

boot don't need to be interesting
it needs to be relieable and the sepearte /boot makes it so

otherwise some dist-upgrades over the years would have been impossible 
and yes i maintain some dozen production machines installed in 2008 with 
Fedora 9 now running Fedora 21 without re-install



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)


UsrMove was long ago

___
kernel mailing list
kernel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/kernel

Re: [PATCH] kernel.spec: no more files in /boot

2015-05-08 Thread Josh Boyer
On May 8, 2015 11:38 AM, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl
wrote:

 On Thu, May 07, 2015 at 10:08:56PM -0400, Matthew Miller wrote:
  On Thu, May 07, 2015 at 04:29:11PM -0500, Ian Pilcher wrote:
   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
   environments.
 
  They don't have a separate boot, fwiw.
 What about amending the patch to use

cp --reflink=auto ...

 ?

The kernel-install tool is what would need to be patched. It is what is
doing the copying at install time.  Doing it in the spec is pointless as
we're mucking around in the build root not the actual system.

josh
___
kernel mailing list
kernel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/kernel