Scooby wrote:...
Alternative 2 - the second easiest way
This did not work for me with the instructions as given (at least if I understood them correctly). I did find a slightly different way to do things.
I was working from a terminal window running in Ubuntu 12.10, though the exact flavour of Linux should not matter, Puppy does tend to mount filesystems differently to most larger flavours of Linux (*)
2. ...
where sdxx is exchanged for your label
and -I is i and not the L character.
Firstly: a typo: there must not be a space between the - and the F.
Here I was not quite sure what you meant by "label". To Linux users usually (*) means a human readable name for the disk whereas sdxx looks like a Linux disk identifier.
If sdxx is a label, the syntax on many Linux distros (*) is /dev/disk/by-label/sdxx
If sdxx is a partition (eg sdc1) then /dev/sdc1 is the more usual form (*), and /mnt/sdc1 is specific to Puppy's way of doing things.
So I used /dev/sdc1 here instead of /mnt/sdc1
Thinking of labels, you might actually want a label on this partition: this is how you do that:
Code: Select all
mkdosfs -F 32 -n easy2boot -I /dev/sdxx
Then when you look at the drive in Windows and in most (*) Linux versions it will show as easy2boot
3. Make USB drive bootable with Grub4Dos.
where y is exchanged for the number of the partion you want to install the bootloader on(most commonly 1
and sdxx is exchanged for your label
Here I typed --floppy=1 /dev/sdc1. That appeared to work at the time, but at the end of the process the bios failed to find the bootsector.
Referring back to the grub4dos manual, this is because your form of the command installs to the *Partition* MBR, and the BIOS looks at the *disk* MBR. (+)
So I changed the command to refer to the disk, and bootlace then complained that the --floppy option is illegal
So I left that out, and the version of this that worked for me was as follows:
where sdx is the disk not the partition (for example sdc not sdc1)
Having done that, I followed the remaining instructions as given and it booted nicely. After setting up the wifi, the first thing I did from my *new* *working* Puppy was to post this.
River~~
edit to add footnotes
(*) In this post, "Linux usually" and "most Linux" means the mainstream distros like Debian, SuSE, Fedora, Red Hat, Ubuntu; and in contrast to how Puppy does things.
Anyone swapping in either direction between "most Linux" and "Puppy" has some learning to do. Most of these differences arise from BarryK's efforts to reduce bloat.
(+) Looking back, I wonder if my mistake was simpler - did I check that the "boot" flag was set on that partition? I'm not going to go back and test that now I have got a bootable Puppy