grub boot manager
grub boot manager
getting 1.02 to work fine using my cdrom as a boot, but i wanted to install it to my harddrive to boot without a cdrom. i dont have the expenses to buy a new cdrom. i dont see the grub boot manager when i begin loading puppy, i just see a big puppy logo, and the files loading when i turn on my machine.
the user/password problems seems to be solved in 1.02, not sure why or how, but it is now working, great thanks.
help with harddrive install?
the user/password problems seems to be solved in 1.02, not sure why or how, but it is now working, great thanks.
help with harddrive install?
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
Yes.
Puppy has two options on the HD install. Option 2 will allow a boot from HD whilst option 1 still requires a floppy boot disk.
Option 2 will also set up the Grub boot loader which allows the booting from HD just like Windows (a pre-Puppy Operating System and retirement system for Bill Gates)
Hope that answers your question
Puppy has two options on the HD install. Option 2 will allow a boot from HD whilst option 1 still requires a floppy boot disk.
Option 2 will also set up the Grub boot loader which allows the booting from HD just like Windows (a pre-Puppy Operating System and retirement system for Bill Gates)
Hope that answers your question
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
When working on 1.0.2, I focussed my attention on Option 2 installation, and I don't think that I even tested Option 1.
Note, due to the size of the new kernel, there is no longer an autoexec.bat file, as there is no room for command.com on the floppy.
config.sys is used instead to directly launch tiny.exe (the boot loader), totally bypassing command.com.
So, Option 1 is not using Grub at all.
Probably this whole situation will be done away with, now that we have Grub, and we will use Grub to create a boot floppy -- so not need a dos and tiny.exe system at all.
Note, due to the size of the new kernel, there is no longer an autoexec.bat file, as there is no room for command.com on the floppy.
config.sys is used instead to directly launch tiny.exe (the boot loader), totally bypassing command.com.
So, Option 1 is not using Grub at all.
Probably this whole situation will be done away with, now that we have Grub, and we will use Grub to create a boot floppy -- so not need a dos and tiny.exe system at all.
Using GRUB to make a boot flopppy
Very interesting for me. I didn't know grub can create a floppy disk.BarryK wrote: Probably this whole situation will be done away with, now that we have Grub, and we will use Grub to create a boot floppy -- so not need a dos and tiny.exe system at all.
I'm glad you choose to use grub over lilo. Wonder if it would be good to make a grub section on the forum.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: Using GRUB to make a boot flopppy
This is a new area for me also.Bruce B wrote:Very interesting for me. I didn't know grub can create a floppy disk.BarryK wrote: Probably this whole situation will be done away with, now that we have Grub, and we will use Grub to create a boot floppy -- so not need a dos and tiny.exe system at all.
I'm glad you choose to use grub over lilo. Wonder if it would be good to make a grub section on the forum.
Grubconfig has option of creating a boot floppy, so I tried it, it worked -- but at the time I didn't follow through and find out just what got put onto the floppy.
I intend to come back to it for a closer scrutiny.
I'll do some R&D
I justed searched Google for +grub +floppy - there is a lot out there on the subject.
I'll try and save you a little time by doing some preliminary work and post what I learned, links and etc.
I'll try and save you a little time by doing some preliminary work and post what I learned, links and etc.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Yes, but I think Grubconfig has done it all for us.
Just need to execute Grubconfig from the install scripts.
-- I already made a slight modification to Grubconfig, it accepts a partiton on the commandline,
grub /dev/hda2
which makes it that much easier.
...and there is a menu option in Grubconfig to create a Grub boot floppy, as well as install grub to h.d.
Just need to execute Grubconfig from the install scripts.
-- I already made a slight modification to Grubconfig, it accepts a partiton on the commandline,
grub /dev/hda2
which makes it that much easier.
...and there is a menu option in Grubconfig to create a Grub boot floppy, as well as install grub to h.d.
Last edited by BarryK on Mon 23 May 2005, 00:45, edited 1 time in total.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Bruce B,
If you want to, or anyone else, you could try the install-to-hard-drive script Option-2 and at the end where it calls Grubconfig and you choose the "automatic install" menu option, I think it does ask if you want to create a boot floppy -- find out how that works.
If it does, maybe we would have to call Grubconfig twice, first time to install Grub to h.d., second time to install to floppy. Both would be optional -- or rather it would have to at least one of them, or both.
If you want to, or anyone else, you could try the install-to-hard-drive script Option-2 and at the end where it calls Grubconfig and you choose the "automatic install" menu option, I think it does ask if you want to create a boot floppy -- find out how that works.
If it does, maybe we would have to call Grubconfig twice, first time to install Grub to h.d., second time to install to floppy. Both would be optional -- or rather it would have to at least one of them, or both.
I'd edit the existing menu.lst
If it were me and I already had GRUB installed, I'd choose not to let Puppy install GRUB. Just edit your existing menu.lst file to boot the new Puppy.babbs wrote:I currently have grub running with selections for my Windows drive and my FC3 drive (with multiple kernel choices that I need to clean up). If I do an Option 2 install with grub, will it add to my current grub.conf file or will it replace it?
Example below:
Indent where appropriate. Change pup size and locations for your system
# for type 1 install
title Puppy version 1.0.2
rootnoverify (hd0,4)
kernel /vmlinuz root=/dev/ram PFILE=pup001-none-131072 PHOME=hda5
initrd /image.gz
# for a type 2 install (I think the initrd line is correct, but can't verify now right now)
title Puppy Linux (hda7)
kernel (hd0,6)/boot/vmlinuz root=/dev/hda7
Last edited by Bruce B on Tue 31 May 2005, 08:42, edited 2 times in total.
I'm thinking that I missed something... I did a type 2 install to the first partition in the first hard drive (Windoz is now all gone) with a manual insertion of Puppy into the grub.conf file. When I select Puppy from the grub boot menu, I get an "Error 15 File Not Found".
Here is my grub.conf:
Does it look like I missed anything?
Here is my grub.conf:
Code: Select all
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd1,0)
# kernel /vmlinuz-version ro root=/dev/hdc2
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd1,0)/grub/splash.xpm.gz
hiddenmenu
password --md5 {Removed}
title Fedora Core (2.6.11-1.14_FC3)
root (hd1,0)
kernel /vmlinuz-2.6.11-1.14_FC3 ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.11-1.14_FC3.img
title Puppy Linux v1.0.2
rootnoverify (hd0,0)
kernel /vmlinuz root=/dev/ram0 PFILE=pup001-none-262144 PHOME=hda1
initrd /image.gz
Last edited by babbs on Wed 01 Jun 2005, 05:58, edited 2 times in total.
Comparing our menu.lst commands
Comparing our GRUB commands
----------------------------
MINE
title Puppy Linux HD
kernel (hd0,6)/boot/vmlinuz root=/dev/hda7
YOURS
title Puppy Linux v1.0.2
rootnoverify (hd0,0)
kernel /vmlinuz root=/dev/ram0 PFILE=pup001-none-262144 PHOME=hda1
initrd /image.gz
PUPPY version 1.0.2 default type 2 instruction example for you
title Linux (on /dev/hda7)
root (hd0,6)
kernel /boot/vmlinuz root=/dev/hda7 ro vga=normal
------------------------
MY COMMENTS:
It looks to me as if you have instructions to boot a type 1 install but your post said you did a type 2 install. I think this is the problem.
I think you should follow the example from Puppy's default rather than my example.
----------------------------
MINE
title Puppy Linux HD
kernel (hd0,6)/boot/vmlinuz root=/dev/hda7
YOURS
title Puppy Linux v1.0.2
rootnoverify (hd0,0)
kernel /vmlinuz root=/dev/ram0 PFILE=pup001-none-262144 PHOME=hda1
initrd /image.gz
PUPPY version 1.0.2 default type 2 instruction example for you
title Linux (on /dev/hda7)
root (hd0,6)
kernel /boot/vmlinuz root=/dev/hda7 ro vga=normal
------------------------
MY COMMENTS:
It looks to me as if you have instructions to boot a type 1 install but your post said you did a type 2 install. I think this is the problem.
I think you should follow the example from Puppy's default rather than my example.