Tiny Core Base > CorePlus

Use of external boot loaders with CorePlus frugal install on hard drive

(1/2) > >>

Len E.:
My computers are generally set up in multi-boot fashion with Windows
and several Linux distros installed.  I frequently rely on a Ubuntu
derivative to manage a boot partition,  and an associated boot list
from which to select the distro of interest.  This boot list approach
doesn't seem to work for Tiny Core, but fortunately there are other
alternatives.

I've found that, provided CorePlus is installed in a primary disk partition,
not a logical partition which is part of an extended partition, the PLop
boot loader, or Super Grub Version 2.02s3, running from a CD, will
boot up CorePlus directly after a simple frugal install with no problem.

(PLop can only access the first 3 partitions per hard drive).
(Super Grub Version 2.02s3 is not the latest version; last April 1, I
 encountered hacker-installed April Fool's Day nuisance messages
 with later versions).

If CorePlus is installed in a logical partition, a boot loader must be
installed with it.   I found a "how-to" procedure from 2009 on the
web, and have applied it specifically to my current situation, as
described in the attached file, grubinstall.txt.

Hopefully, this is of some interest .................

Len E.

Len E.:
Some details  I forgot to include in the initial post:

-The initial frugal intall was from a bootable USB created
 from the .iso with unetbootin.
-The usb device is sdd1
-The target hard drive partition is sda7
-The boot loader install takes place immediately after the
  frugal install, with the usb still mounted.

Len E.

mocore:

--- Quote from: Len E. on November 28, 2017, 04:49:04 PM --- I frequently rely on a Ubuntu
derivative to manage a boot partition,  and an associated boot list
from which to select the distro of interest.  This boot list approach
doesn't seem to work for Tiny Core, but fortunately there are other
alternatives.

--- End quote ---

Hi i read your post but i do not understand
 ..what is "this boot list approach" ( perhaps some scripts that create automagically a boot cfg ? )
..and how or why do it "not seem to work for Tiny Core"   ???

polikuo:
Hi Len E.
I don't use GRUB that much, but I'm pretty sure you can use an existing bootable grub partition to boot TC.
Just copy core.gz (corepure64.gz) and vmlinuz (vmlinuz64) to your grub partition.
Edit your grub.cfg and you should be good to go.

For instance, let's say your bootable partition is /dev/sda1.

--- Code: ---tc@box:~$ cp core.gz vmlinuz /mnt/sda1/boot
tc@box:~$ vi /mnt/sda1/boot/grub/grub.cfg

--- End code ---

--- Quote ---### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
menuentry 'TinyCore' {
   set root="(hd0,msdos1)"
   linux /boot/vmlinuz tce=UUID="82349d6b-6363-41ec-99a8-1238649cba45"
   initrd /boot/core.gz
}
### END /etc/grub.d/40_custom ###

--- End quote ---
For UUID:

--- Code: ---tc@box:~$ blkid -s UUID /dev/sda7
/dev/sda7: UUID="82349d6b-6363-41ec-99a8-1238649cba45"

--- End code ---

coreplayer2:

--- Quote from: polikuo on November 28, 2017, 10:22:26 PM ---Hi Len E.
I don't use GRUB that much, but I'm pretty sure you can use an existing bootable grub partition to boot TC.
Just copy core.gz (corepure64.gz) and vmlinuz (vmlinuz64) to your grub partition.
Edit your grub.cfg and you should be good to go.

--- End quote ---
Exactly, add only the menu entry for the new system to the config file.     

It's always good to see folks roll up their sleeves and get their hands dirty, but It's really easy..    Folks seem to make this more difficult than it needs to be..

Note:  Super Grub is more of a recovery disk and not really necessary,  grub2 extension is in the repo if you wish to update grub files or reinstall if you insist,  just follow the information in the extension info files.

 8)

Navigation

[0] Message Index

[#] Next page