root partition move

[Aviss,Tyler]

Quite often the kernel loads with inital RAMdisk (initrd) in memory  
prior to the OS base. The unitrd has basic stuff like modules/ 
components for SATA/RAID/interfaces/etc needed to actually get Linux  
up to the point of mounting root

(sent from my phone, so please excuse the typos)

On 28-Jul-09, at 6:45 PM, Rajinder Yadav <devguy.ca-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote:

> On Tue, Jul 28, 2009 at 8:24 PM, Aviss,Tyler<tjaviss-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote:
>> Hey Rajinder,
>>
>> Have you ever tried compiling a kernel? You could probably get away  
>> with
>> actually having a shared /boot between Linuxes, and common kernel.  
>> If you
>> just separate partitions for each OS that should work well enough.
>
> I compiled a kernel in the past a long time ago, back in college when
> I learned Slackware from a friend who showed me how to install it
> using floppies. I am currently (slowly) going through Linux from
> Scratch. I am at the point where I need to chroot and build my system
> along with the kernel in Ernest. So that will give me the opportunity
> to look at building the kernel more closely.
>
>> You may even be able to use a Ubuntu kernel in RedHat. My main  
>> concern would
>> be the initrd's. With a self compiled kernel you could likely  
>> compile all
>> drivers necessary for booting in and not need an unitrd at all.
>
> I guess I could try to build a new kernel for my current Kubuntu
> install, since I've already backed up the image there is no fear of
> messing things up.
>
> When you say initrd's / unitrs are you speaking about the
> start-up/shut-down scripts that need to be run? Not sure I follow, I
> am still a quasi-newbie =)
>
>> On 28-Jul-09, at 12:51 PM, Rajinder Yadav <devguy.ca-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org>  
>> wrote:
>>
>>> On Tue, Jul 28, 2009 at 1:29 PM, Lennart
>>> Sorensen<lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org> wrote:
>>>>
>>>> On Tue, Jul 28, 2009 at 01:04:12PM -0400, S P Arif Sahari Wibowo  
>>>> wrote:
>>>>>
>>>>> Sharing /boot works too. Just may need more understanding on  
>>>>> grub and
>>>>> booting mechanism. That said, I do agree that chain-loading may be
>>>>> easier.
>>>>
>>>> Chain loading means you can allow each linux to automatically  
>>>> manage
>>>> grub.
>>>> Sharing /boot means you can forget about having them automatically
>>>> managed.
>>>
>>> Is there a how-to on on chaining, would it be found in the GRUB
>>> how-to, if there is one? I would like to install fedora 11 when they
>>> get their mirror update issues worked out, and want to make sure I  
>>> am
>>> not sharing the /boot partition between different distros.
>>>
>>>> Of course I must admit I have never installed multiple linuxes on
>>>> one system.  I can't see any use.  If I want to play around and  
>>>> try out
>>>> a distribution I will use a virtual machine.  I just never reboot  
>>>> so
>>>> why would I want to have two systems to maintain where somethings  
>>>> work
>>>> in one and some things in the other.  Just not useful to me.
>>>>
>>>> --
>>>> Len Sorensen
>>>> --
>>>> The Toronto Linux Users Group.      Meetings: http://gtalug.org/
>>>> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
>>>> How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists
>>>>
>>> --
>>> Kind Regards,
>>> Rajinder Yadav
>>> --
> --
> The Toronto Linux Users Group.      Meetings: http://gtalug.org/
> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
> How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists