hello
I just installed Quirky 7.0.4.1 April to my hard drive and it seems to be pretty good. But... I can't seem to find any tool to configure grub
C
grub in Quirky 7.0.4.1
grub4dos supports grub as well. Look for a file named menu.lst at the top
of your hard drive.
If you are running an Ubuntu computer they use a different procedure
---> edit /boot/grub/grub.cfg (you are not supposed to edit this file but you can)
https://help.ubuntu.com/community/Grub2
_______________________________________
of your hard drive.
If you are running an Ubuntu computer they use a different procedure
---> edit /boot/grub/grub.cfg (you are not supposed to edit this file but you can)
https://help.ubuntu.com/community/Grub2
_______________________________________
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
Don,
You need to warn people that any changes they make to grub.cfg will disappear the next time that system runs update-grub.
Editing the 40_custom file in /etc/grub.d, and making it executable, will create a new menu entry in a way that will survive update-grub. If you want to put the entry at the top of the menu, you can change 40_custom to 7_custom.
Here's the file I used to boot Quirky on another system using grub2: The code at the beginning is typically found in 40_custom. Your uuid will be different, and you will have to run update-grub from a root console within that system after creating this file.
I don't like the added complexity of this approach, which requires a working Linux environment to run the script that builds grub.cfg. This presents problems when you are trying to recover a damaged system. However, this is the approach you will find in many popular distributions which can deal with a UEFI BIOS. You can use these distributions to install a bootloader, if your Puppy system fails to install one you can use.
You need to warn people that any changes they make to grub.cfg will disappear the next time that system runs update-grub.
Editing the 40_custom file in /etc/grub.d, and making it executable, will create a new menu entry in a way that will survive update-grub. If you want to put the entry at the top of the menu, you can change 40_custom to 7_custom.
Here's the file I used to boot Quirky on another system using grub2:
Code: Select all
#!/bin/sh
exec tail -n +3 $0
# 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 "Quirky April64 7.0.4.1 frugal in sda2 dir april64-7.0.4.1"{
set root='(hd0,2)'
search --no-floppy --fs-uuid --set c02f47ec-bc89-4742-af5e-97f54efa5769
linux /april64-7.0.4.1/vmlinuz
initrd /april64-7.0.4.1/initrd.q
}
I don't like the added complexity of this approach, which requires a working Linux environment to run the script that builds grub.cfg. This presents problems when you are trying to recover a damaged system. However, this is the approach you will find in many popular distributions which can deal with a UEFI BIOS. You can use these distributions to install a bootloader, if your Puppy system fails to install one you can use.
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
I wrote a tutorial
http://murga-linux.com/puppy/viewtopic.php?t=90516
Make sure you use a CD to burn plop if you are using an old computer
because of the problem of booting DVDs in old computers.
...but it is possible to just copy files to your hard disk. Carefully read instructions at plop site.
_____________________________________________________________
http://murga-linux.com/puppy/viewtopic.php?t=90516
Make sure you use a CD to burn plop if you are using an old computer
because of the problem of booting DVDs in old computers.
...but it is possible to just copy files to your hard disk. Carefully read instructions at plop site.
_____________________________________________________________