Author |
Message |
Stripe
Joined: 23 Jun 2010 Posts: 658 Location: In a field. England
|
Posted: Fri 26 Nov 2010, 05:42 Post subject:
|
|
Hi sc0ttman
Heres my grub4dos entry;
title 214-X5 (sda2/puppy214)
find --set-root --ignore-floppies /puppy214/initrd.gz
kernel /puppy214/vmlinuz pmedia=atahd psubdir=puppy214 root=/dev/ram0
initrd /puppy214/initrd.gz
Hope this helps
Stripe
|
Back to top
|
|
 |
shinobar

Joined: 28 May 2009 Posts: 2664 Location: Japan
|
Posted: Fri 26 Nov 2010, 06:38 Post subject:
|
|
Thanks bigpup, sc0tman and stripe.
Stripe wrote: | title 214-X5 (sda2/puppy214)
find --set-root --ignore-floppies /puppy214/initrd.gz
kernel /puppy214/vmlinuz pmedia=atahd psubdir=puppy214 root=/dev/ram0
initrd /puppy214/initrd.gz |
I will write about 'root=/dev/ram0' option on the document regarding the classic pup.
_________________ Downloads for Puppy Linux http://shino.pos.to/linux/downloads.html
|
Back to top
|
|
 |
shinobar

Joined: 28 May 2009 Posts: 2664 Location: Japan
|
Posted: Sat 27 Nov 2010, 03:40 Post subject:
Grub4DosConfig v1.6.3 Subject description: Updated 27 November 2010 |
|
Updated Grub4DosConfig v1.6.3. See the top of this topic.
CHANGES:
- Manage the issue USB flash devices treated by the 'BootFlash' corrupts with Grub4DosConfig. (Thanks to smokey01)
But anyway, re-format the USB device using gparted before using Grub4DosConfig (back up the data before).
1. Delete all the partition
2. Rewrite the partition table (Device >> Create Partition Table)
3. Create partitions and format.
- Chainload PBR.
Grub4DosConfig v1.6.3 gives menu items chainload the Partition Boot Records, like '(sda2:PBR)'.
It does not always mean you can boot up from the partiton.
There may be cases boot flag is on but the boot loader is not there.
These items may be redundant because the OS is already listed up on the leading items.
You can remove it from the menu after you are sure you can boot up the OS with another entry.
- New Puppy simple filename support.(Thanks to artifus and ICPUG)
- Classic Pup support, maybe not perfect.(Thanks to Stripe)
- Tool tips.(Thanks to sc0ttman)
- New icon. (Thanks to big_bass)
Thanks to all, and awaiting your report.
_________________ Downloads for Puppy Linux http://shino.pos.to/linux/downloads.html
|
Back to top
|
|
 |
shinobar

Joined: 28 May 2009 Posts: 2664 Location: Japan
|
Posted: Sat 27 Nov 2010, 03:46 Post subject:
Sector size check Subject description: by Grub4DosConfig v1.6.3 |
|
shinobar wrote: | Manage the issue USB flash devices treated by the 'BootFlash' corrupts with Grub4DosConfig. (Thanks to smokey01) |
Th Grub4DosConfig v1.6.3 checks the sector size, and gives error message like this:
It occures only when you once treat the USB by the 'BootFlash' and then you re-format it with ext4 partition.
Because fat32 case, the Grub4DosConfig v1.6.3 escapes the issue by using smaller boot loader.
Anyway, I recommend to re-format the USB device using gparted before using Grub4DosConfig (back up the data before).
1. Delete all the partition
2. Rewrite the partition table (Device >> Create Partition Table)
3. Create partitions and format.
_________________ Downloads for Puppy Linux http://shino.pos.to/linux/downloads.html
|
Back to top
|
|
 |
noryb009
Joined: 20 Mar 2010 Posts: 592
|
Posted: Sat 27 Nov 2010, 08:39 Post subject:
|
|
Can you change "after escaping all the data" to "after backing up all the data"?
|
Back to top
|
|
 |
shinobar

Joined: 28 May 2009 Posts: 2664 Location: Japan
|
Posted: Sat 27 Nov 2010, 08:56 Post subject:
backing up |
|
noryb009 wrote: | Can you change "after escaping all the data" to "after backing up all the data"? |
Thanks. Maybe next release
_________________ Downloads for Puppy Linux http://shino.pos.to/linux/downloads.html
|
Back to top
|
|
 |
nooby
Joined: 29 Jun 2008 Posts: 10548 Location: SwedenEurope
|
Posted: Sat 27 Nov 2010, 09:05 Post subject:
|
|
Shinobar, have patience with a perennial Newbie now.
I want to have a USB mem stick that I can use as a rescue thing on my and others computers.
But when I make the usb then it look for OS on the particular machine one make it on.
Suppose I make it on the Acer D250 then it list all the puppies I have on that one and it makes a menu.lst to be able to boot on that one.
All good but then I want to rescue the Packard Bell or the HP/Compaq computer.
So one would need some kind of script that would give a choice to include the new computer under its name and brand? A kind of menu.lst that was changed the order of the entries so the older entries for AcerD250 was pushed further down and those for the current Packard Bell that one use at the moment comes fist choices and then when one use it on the next computer then the OS for that one comes up first?
Maybe very unrealistic request for further versions update?
Maybe one could start all over with grub4dosconfig on each computer and create nested menu.lst files that had names or numbers for each computer one test it on?
_________________ I use Google Search on Puppy Forum
not an ideal solution though
|
Back to top
|
|
 |
shinobar

Joined: 28 May 2009 Posts: 2664 Location: Japan
|
Posted: Sat 27 Nov 2010, 09:21 Post subject:
nested menu |
|
nooby wrote: | Maybe one could start all over with grub4dosconfig on each computer and create nested menu.lst files that had names or numbers for each computer one test it on? |
Nice idea, nooby You can do it manually editing the menu.lst.
- You make a menu.lst for the 1st computer running grub4dosconfig on the 1st computer.
- You go to the 2nd computer and run grub4dosconfig on the 2nd computer.
Made new menu.lst for the 2nd PC. This time, the menu list for the old 1st PC is automatically backed up with a name menu-xxxx-xx-xx-xxxxxx.lst. (you can rename it, say 'menu-1st.lst'.
- Add next entry in the menu.lst of the new 2nd:
Code: | title Next menu for the 1st PC
configfile /menu-xxxx-xx-xx-xxxxxx.lst
commandline |
_________________ Downloads for Puppy Linux http://shino.pos.to/linux/downloads.html
Last edited by shinobar on Sat 27 Nov 2010, 09:42; edited 3 times in total
|
Back to top
|
|
 |
shinobar

Joined: 28 May 2009 Posts: 2664 Location: Japan
|
Posted: Sat 27 Nov 2010, 09:36 Post subject:
root=/dev/ram0 option |
|
For Classic Pup support, i add 'root=/dev/ram0' option in the grub4dosconfig v1.6.3.
But it may not proper...
What version of Puppy require 'root=/dev/ram0' option to boot up?
I am confused seeing the Barry's document:
http://www.puppylinux.com/hard-puppy.htm
_________________ Downloads for Puppy Linux http://shino.pos.to/linux/downloads.html
|
Back to top
|
|
 |
nooby
Joined: 29 Jun 2008 Posts: 10548 Location: SwedenEurope
|
Posted: Sat 27 Nov 2010, 09:36 Post subject:
|
|
Cool and when one boot how does the one chose among them?
I guess one have to manually go into geany or some other editor and add entries from each back upped menu.lst then?
Could not the script notice that one are on a new computer by knowing this is another MAC address.
Then it ask. Do you want me to add the OS on this new machine to the menu.lst or do you want me to back up the old menu.lst by giving it a back up number and treat this new machine as the one you exclusively want to use from now on?
Does that add too much to the simplicity?
_________________ I use Google Search on Puppy Forum
not an ideal solution though
|
Back to top
|
|
 |
nooby
Joined: 29 Jun 2008 Posts: 10548 Location: SwedenEurope
|
Posted: Sat 27 Nov 2010, 10:19 Post subject:
|
|
Shinobar I know nothign about such but puppy search I found this one.
root=/dev/ram0
http://www.murga-linux.com/puppy/viewtopic.php?p=165550#165550
Quote: | You don't need 'root=/dev/ram0 ramdisk_size=16384' -- the kernel in Dingo will just ignore the root=/dev/ram0 |
Thread title is "Boot Puppy on the Asus eeepc"
in case that explain something?
when are that ram= used then?
_________________ I use Google Search on Puppy Forum
not an ideal solution though
|
Back to top
|
|
 |
rcrsn51

Joined: 05 Sep 2006 Posts: 11889 Location: Stratford, Ontario
|
Posted: Sat 27 Nov 2010, 14:02 Post subject:
Re: root=/dev/ram0 option |
|
shinobar wrote: | What version of Puppy require 'root=/dev/ram0' option to boot up? |
Only Puppy 2.xx. Starting with Puppy 3, that option was eliminated.
|
Back to top
|
|
 |
Stripe
Joined: 23 Jun 2010 Posts: 658 Location: In a field. England
|
Posted: Sat 27 Nov 2010, 14:36 Post subject:
|
|
Hi shinobar
Grub4dos is working with frugal installs of 214 on hard drive and on usb stick as well
Cheers
Stripe
|
Back to top
|
|
 |
shinobar

Joined: 28 May 2009 Posts: 2664 Location: Japan
|
Posted: Sat 27 Nov 2010, 18:54 Post subject:
Re: root=/dev/ram0 option |
|
rcrsn51 wrote: | Only Puppy 2.xx. Starting with Puppy 3, that option was eliminated. |
Thanks nooby, rcrsn51 and Stripe.
I had a mistake. add the root=/dev/ram0 to both Puppy 2.x and 3.x.
@ Puppy 3.x users:
Remove the root=/dev/ram0 opton from the menu.lst entry.
_________________ Downloads for Puppy Linux http://shino.pos.to/linux/downloads.html
|
Back to top
|
|
 |
BarryK
Puppy Master

Joined: 09 May 2005 Posts: 8526 Location: Perth, Western Australia
|
Posted: Sun 28 Nov 2010, 18:35 Post subject:
Re: root=/dev/ram0 option |
|
shinobar wrote: | For Classic Pup support, i add 'root=/dev/ram0' option in the grub4dosconfig v1.6.3.
But it may not proper...
What version of Puppy require 'root=/dev/ram0' option to boot up?
I am confused seeing the Barry's document:
http://www.puppylinux.com/hard-puppy.htm |
Puppies prior to 3.0 used a ramdisk at bootup, from 3.0 onwards they used a "initramfs" -- a ramfs (ram filesystem) in memory to hold the initrd.gz contents.
Note, a ramdisk is a simulated disk drive in RAM, with a normal filesystem in it -- Puppy created a ext2 f.s.
From 3.0 onwards, if you do have "root=/dev/ram0" it just gets ignored. But, better not to have it as it will confuse people wondering why it is there.
_________________ http://bkhome.org/news/
|
Back to top
|
|
 |
|