<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span></span></div><div><br></div> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;" class="ms__id44824"> </div><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;" dir="ltr" class="ms__id44824"> <font size="2" face="Arial"> <div style="margin: 5px 0px; padding: 0px; border: 1px solid rgb(204, 204, 204); height: 0px; line-height: 0; font-size: 0px;" class="hr" contentEditable="false" readonly="true"></div> <b><span style="font-weight: bold;">From:</span></b> David L. Anselmi <anselmi@anselmi.us><br> <b><span style="font-weight: bold;">To:</span></b> mike havlicek <mhavlicek1@yahoo.com>; CLUE's mailing list <clue@cluedenver.org> <br> <b><span
style="font-weight: bold;">Sent:</span></b> Monday, March 12, 2012 11:52 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [clue] revisiting boot partition and LVM + grub<br> </font> </div><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;" class="ms__id44824"> ===============================================================================================<br>
> This leads me to a question of defeating my purpose (separate /boot disk area within lvm so as to<br>> be able to resize when an update involving the kernel is possibly going to go over available<br>> space and I am not yet sure what backup kernel(s) I am ready to remove)<br><br>I've never had a good reason to use a separate boot partition. Others have told me 2:<br><br>Using the same (probably custom built) kernel with several distros. So all distros share the same /boot. If you're using stock kernel packages that seems error prone and with initramfs I'm not sure how possible it is these days. Regardless, I've never wanted to do it.<br><br>Putting root on a partition that can't be booted from (e.g., using grub with LVM). I used LILO to boot off LVM until grub2 could handle it. Today I don't have any reason to do this.</div><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"
class="ms__id44824"> </div><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;" class="ms__id44824">Thanks for the input. It makes me re-think in terms of forest through the trees. I have primarily been fixed in /dev/sdx1=/boot from</div><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;" class="ms__id44824">the old grub "requirement". At the moment I am also a little fixed in my filesystem based backup/restore method</div><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;" class="ms__id44824">where I reduce the size of each on a partition/filesystem basis and not cluttering up something relatively static with something I</div><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;" class="ms__id44824">might mess up... Not really the case here as I am only slightly curious about seeing what happens say when I build a
v3 kernel</div><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;" class="ms__id44824">on a vanilla rhel6 based distro... I am not planning on multi-distro boot access... Hmmm<var id="yui-ie-cursor"></var><br>===================================================================================<br>> I think the Ubuntu 8.04 LTS USB stick should work which is what I intend to modify, but I still<br>> kinda wonder about the update issues surrounding the kernel once the grub version is<br>> changed...<br><br>With grub2 a grub update should cause it to be reinstalled on your boot device. A kernel or initrd update should cause the config to be rebuilt. If your distro doesn't get that right, get one that does (obsolete distros aside).</div><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;" class="ms__id44824"> </div><div style="font-family: times new roman, new york, times,
serif; font-size: 12pt;" class="ms__id44824">This sounds sane. I'll probably check to see that I am not double grubbed in my software inventory to be safe (at least in my mind 8^)<br><br>> Oh, I have also found various fdisk representations e.g. starting block and DOS compatibility<br>> mode between versions available on installation media and my favorite systemrescueCD to be a bit<br>> confusing particularly when choosing the start so as to install the grub on a HDD.<br>=================================================================<br>How big is your core.img? It has to fit between the MBR and the first partition.</div><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;" class="ms__id44824"><br>I'll have to look at that.</div><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;" class="ms__id44824"><br>Dave<br><br><br><br> -Mike (Whoops .. if my mail partition comes
out a bit screwy)</div> </div> </div></body></html>