Full Installer to USB flash drives

[bigpup]

Full install to USB drive

Puppy runs better and faster as a frugal install to a USB device.
However, this is Linux and Linux is about options, even if they are something you normally should not do.

Thanks to Scooby for this code.

Here is a script that can do a full install to a USB flash drive and probably a USB hard drive.
This script runs from a terminal.

As base gist:
It's at https://gist.github.com/suedi/8897880a873d68ea05f5
Copy and paste into Geany
Save as... puppy_full_installer
Give execute permission
In a terminal enter: sh puppy_full_installer

As a zip file:
https://gist.github.com/suedi/8897880a8 ... 68abc1.zip
Unzip
Give execute permission
In a terminal enter: sh puppy_full_installer

It runs from a terminal and is very basic.
Easy to use.
Just answer some simple questions and input the correct information that is asked.

To make USB storage device bootable.
Install a boot loader to the USB drive and make the boot menu entry look similar to this one for a USB flash drive full install.
Example:
(USB flash drive sdb1)
Boot menu entry for Grub4dos boot loader.

Code: Select all

title Slacko Puppy 6.3.0 (sdb1/boot)
  uuid 1b94bf9f-2c37-4152-a564-52eefa24c3d3
  kernel /boot/vmlinuz root=/dev/sdb1 rootwait

About using a Puppy full install on a USB flash drive
It opens programs slower.
Selecting stuff in a program, runs slower, if that selection requires reading data from the flash drive.
It writes more often to the flash drive, than a normal frugal installed Puppy..
Probably all of this slowness is caused by:
1. The read speed of the flash drive and the USB connection.
Mine is USB 2.
2. A full install does not load much into memory on boot-up.
Only the basic Puppy operating system is in memory.

[scsijon]

Is there any chance bigpup of having scooby add a section that checks size of source against required vacent space on device and erroring with a message if there is not enough? That's one thing that's always bugged me!

Other than that, from a quich scan, I think it's a nice script, I'll try it on a test system this weekend.

[april]

Just trying this .
For your perusal I list what I got -Ill take it all off in a day or two when you have had a chance to see it .
Precise 5.7.1
Reckon us stupids need a bit more info. I didn't get a bootable drive

Code: Select all

puppy_full_installer
# puppy_full_installer
bash: puppy_full_installer: command not found
# ./puppy_full_installer
bash: ./puppy_full_installer: Permission denied
# ./puppy_full_installer
I assume you have formatted the drive to ext(2,3,4)
I'm not babysitting so if it isn't do it now!
Is it? (y or n + [Enter/Return])
y
Assuming you are not stupid...
OK, remember.. I'm not responsible here...
Proceeding...

Insert your drive and mount it.
Then tell me the target drive partition (eg: sdc1, sdd1 etc)
GET IT RIGHT!
what is the drive partition?
sdc1
Seems sane..
Ok, /mnt/sdc1 exists. Good.

Now we need some source files
either mount a CD/DVD or an ISO file
THEN, tell me the mount point path
EXAMPLE: /mnt/sr0 or /mnt/+mnt+sda5+iso+tahr64-6.0.3.9.iso
An easy way to do that is enter the mounted folder and type 'pwd' in a terminal
Type the source mount point path.
 /mnt/sr0
Seems sane..

Install from /mnt/sr0 to /mnt/sdc1
Press y + [Enter/Return] to continue
y
---------------------------------------------------------------
cp: cannot stat `/mnt/sr0/vmlinuz': No such file or directory
ls: cannot access /mnt/sr0/*.sfs: No such file or directory
mv: cannot stat `/mnt/sdc1/vmlinuz': No such file or directory
losetup-FULL: failed to setup loop device: Is a directory
mount: /dev/loop2: can't read superblock
cp: cannot create directory `/mnt/sdc1/lib/modules/3.9.11/': No such file or directory
WARNING: Couldn't open directory /mnt/sdc1/lib/modules/3.9.11: No such file or directory
FATAL: Could not open /mnt/sdc1/lib/modules/3.9.11/modules.dep.temp for writing: No such file or directory
./puppy_full_installer: line 130: /mnt/sdc1/etc/rc.d/PUPSTATE: No such file or directory
./puppy_full_installer: line 131: /mnt/sdc1/etc/rc.d/PUPSTATE: No such file or directory
cp: cannot create special file `/mnt/sdc1/dev/': No such file or directory
cp: cannot create special file `/mnt/sdc1/dev/': No such file or directory
chroot: can't execute '/etc/rc.d/rc.update': No such file or directory
mv: cannot stat `/mnt/sdc1/etc/fstab': No such file or directory
./puppy_full_installer: line 164: /mnt/sdc1/etc/fstab: No such file or directory
./puppy_full_installer: line 165: /mnt/sdc1/etc/fstab: No such file or directory
./puppy_full_installer: line 166: /mnt/sdc1/etc/fstab: No such file or directory
./puppy_full_installer: line 167: /mnt/sdc1/etc/fstab: No such file or directory
./puppy_full_installer: line 168: /mnt/sdc1/etc/fstab: No such file or directory
umount: can't umount /mnt/sdc1/srcmntpt: Invalid argument
---------------------------------------------------------------

Hopefully we're done ...

Do not forget if your target is a USB drive then add "rootwait"
in the Options textbox in grub4dos-config window with title:

"Grub4DosConfig - List of detected operating systems"

It is essential for a successful boot.

now run grub4dos-config to make it bootable.
#  grub4dos-config
bash: grub4dos-config: command not found
# grub4dos-config
bash: grub4dos-config: command not found
# ./puppy_full_installer
I assume you have formatted the drive to ext(2,3,4)
I'm not babysitting so if it isn't do it now!
Is it? (y or n + [Enter/Return])
y
Assuming you are not stupid...
OK, remember.. I'm not responsible here...
Proceeding...

Insert your drive and mount it.
Then tell me the target drive partition (eg: sdc1, sdd1 etc)
GET IT RIGHT!
what is the drive partition?
sdc1    
Seems sane..
Ok, /mnt/sdc1 exists. Good.

Now we need some source files
either mount a CD/DVD or an ISO file
THEN, tell me the mount point path
EXAMPLE: /mnt/sr0 or /mnt/+mnt+sda5+iso+tahr64-6.0.3.9.iso
An easy way to do that is enter the mounted folder and type 'pwd' in a terminal
Type the source mount point path.
sr0
Not sane! try again
Type the source mount point path.
/mnt/sr0
Seems sane..

Install from /mnt/sr0 to /mnt/sdc1
Press y + [Enter/Return] to continue
y
---------------------------------------------------------------

Decompressing: /mnt/sr0/puppy_precise_5.7.1.sfs
To target: /mnt/sdc1

please have patience.

Parallel unsquashfs: Using 2 processors
15759 inodes (18306 blocks) to write

[===========================================================|] 18306/18306 100%
created 12545 files
created 2145 directories
created 2878 symlinks
created 336 devices
created 0 fifos
mv: cannot move `/mnt/sdc1/vmlinuz' to `/mnt/sdc1/boot/': Not a directory
Upgrading Precise Puppy to version 5.7.1...
Updating w.m. menus...
Updating boot and shutdown system scripts...
Executing depmod, to update module files...
find: warning: you have specified the -noleaf option after a non-option argument -path, but options are not positional (-noleaf affects tests specified before it as well as those specified after it).  Please specify options before other arguments.

Updating /etc/networkmodules...
Adding i2400m-usb
Adding iwlwifi
Adding rndis_wlan

Took a big chunk out here 


Adding hso
Adding atl2
Adding prism2_usb
gtk-update-icon-cache: Cache file created successfully.
Error opening file for reading: No such file or directory
Error opening file for reading: No such file or directory
Error opening file for reading: No such file or directory
Files being translated:
 /etc/rc.d/functions4puppy4
 /etc/rc.d/rc.sysinit
 /etc/rc.d/rc.update
 /etc/rc.d/rc.country
 /usr/local/petget/0setup
Files being translated:
 /root/Choices/ROX-Filer/PuppyPin
 /root/.jwmrc-tray
Generating /root/.icewm/menu...
Generating /root/.jwmrc...
---------------------------------------------------------------

Hopefully we're done ...

Do not forget if your target is a USB drive then add "rootwait"
in the Options textbox in grub4dos-config window with title:

"Grub4DosConfig - List of detected operating systems"

It is essential for a successful boot.

now run grub4dos-config to make it bootable.
# 

[bigpup]

april,

Thanks for your post.
Do not remove it. It is information to consider and needs to stay posted.

Looking at your results. I think your flash drive had file system errors.
Try it again after a repartition and format.
Only have it partitioned in one single partition.
I used ext2 format on my USB flash drive.

I assume you tried to use a Precise 5.7.1 live CD/DVD to get the Precise 5.7.1 data from.
I am not totally sure Scooby coded this to do that.
I think you need to actually mount a Puppy version iso file.
The iso file could be on a CD/DVD.
I did the install from a mounted Slacko 6.3.0.iso file that was on my hard drive.
It worked for me.

Also, the part of your post about upgrading/updating Precise 5.7.1 seems really wrong to be happening. Not sure what that is about. Not part of what this script should be doing.

Grub4dos bootloader does need to be installed to the USB flash drive.
In your example sdc1.
When you run Grub4dos config, choose to install to sdc1 and search only the USB flash drive.

The usb drive identified as sdc1 could cause problems if you boot the computer with it and the computer is seeing it now as sdb1 or something else.
The Grub4dos boot info, on the drive, will be looking for sdc1 for data.
This boot menu entry controls this:
My usb flash is seen as sdb1

Code: Select all

 kernel /boot/vmlinuz root=/dev/sdb1 rootwait

Here is what my flash drive looks like. (Libreoffice.sfs is a file I downloaded not part of the install)

[bigpup]

scsijon,

I am not sure if Scooby wants to work on or improve this script.
Lets see what he says about your request.

He may want to talk bad about me, because I posted this before I got his permission to do so.

If this topic suddenly, is not here anymore, you now know why

I hope Scooby allows it to stay.

[Scooby]

scsijon,

I am not sure if Scooby wants to work on or improve this script.
Lets see what he says about your request.

Problem is "improvement" does not carry the same meaning for you and me.

As for free space checking I will not work on adding it.

Anyone else wanting to do so are free to do it.
They have any questions about the code I will help.

He may want to talk bad about me, because I posted this before I got his permission to do so.

If this topic suddenly, is not here anymore, you now know why

I hope Scooby allows it to stay.

I'll allow it if the archive ready for download is updated to the latest version
https://gist.github.com/suedi/8897880a8 ... 0fd08d.zip

Maybe you should just give base gist so user will always grab the
latest versions themselves?

It's at https://gist.github.com/suedi/8897880a873d68ea05f5

I have changed only comments at the start reflecting
origins of the script. ( +Grub4DosConfig in message and
a possible fix of april's vmlinuz issue)

Man this almost wants me to do a greetings scroller like back in
the commodore64 days, with piss-off greetings and all


I want to ask you all why you feel there is a need for a pet for this?
It is one file. easier to just DL and run.

Or do you want it searchable in packagemanager?

[Scooby]

@april

Code: Select all

puppy_full_installer
# puppy_full_installer
bash: puppy_full_installer: command not found
# ./puppy_full_installer
bash: ./puppy_full_installer: Permission denied
# ./puppy_full_installer

Maybe this is why a pet is needed then again april did get it to run
in the end

Code: Select all

Now we need some source files
either mount a CD/DVD or an ISO file
THEN, tell me the mount point path
EXAMPLE: /mnt/sr0 or /mnt/+mnt+sda5+iso+tahr64-6.0.3.9.iso
An easy way to do that is enter the mounted folder and type 'pwd' in a terminal 
Type the source mount point path.
 /mnt/sr0
Seems sane..

Install from /mnt/sr0 to /mnt/sdc1
Press y + [Enter/Return] to continue
y
---------------------------------------------------------------
cp: cannot stat `/mnt/sr0/vmlinuz': No such file or directory
ls: cannot access /mnt/sr0/*.sfs: No such file or directory
mv: cannot stat `/mnt/sdc1/vmlinuz': No such file or directory
losetup-FULL: failed to setup loop device: Is a directory
mount: /dev/loop2: can't read superblock
cp: cannot create directory `/mnt/sdc1/lib/modules/3.9.11/': No such file or directory
WARNING: Couldn't open directory /mnt/sdc1/lib/modules/3.9.11: No such file or directory
FATAL: Could not open /mnt/sdc1/lib/modules/3.9.11/modules.dep.temp for writing: No such file or directory
./puppy_full_installer: line 130: /mnt/sdc1/etc/rc.d/PUPSTATE: No such file or directory
./puppy_full_installer: line 131: /mnt/sdc1/etc/rc.d/PUPSTATE: No such file or directory
cp: cannot create special file `/mnt/sdc1/dev/': No such file or directory
cp: cannot create special file `/mnt/sdc1/dev/': No such file or directory
chroot: can't execute '/etc/rc.d/rc.update': No such file or directory
mv: cannot stat `/mnt/sdc1/etc/fstab': No such file or directory
./puppy_full_installer: line 164: /mnt/sdc1/etc/fstab: No such file or directory
./puppy_full_installer: line 165: /mnt/sdc1/etc/fstab: No such file or directory
./puppy_full_installer: line 166: /mnt/sdc1/etc/fstab: No such file or directory
./puppy_full_installer: line 167: /mnt/sdc1/etc/fstab: No such file or directory
./puppy_full_installer: line 168: /mnt/sdc1/etc/fstab: No such file or directory
umount: can't umount /mnt/sdc1/srcmntpt: Invalid argument
---------------------------------------------------------------

In this run what did you have mounted on /mnt/sr0?

The script urges you to
"either mount a CD/DVD or an ISO file"

Did you mount a valid ISO on /mnt/sr0?

Code: Select all

Hopefully we're done ...

Do not forget if your target is a USB drive then add "rootwait"
in the Options textbox in grub4dos-config window with title:

"Grub4DosConfig - List of detected operating systems"

It is essential for a successful boot.

now run grub4dos-config to make it bootable.
#  grub4dos-config
bash: grub4dos-config: command not found
# grub4dos-config
bash: grub4dos-config: command not found

How do you run grub4dos-config from the commandline
is it Grub4DosConfig?

I will definately change the message since it is clearly misdirecting

Code: Select all

...
mv: cannot move `/mnt/sdc1/vmlinuz' to `/mnt/sdc1/boot/': Not a directory

Some sort of bug here
Will research...




Cannot really say what the error message of Grub4dosConfig is all about.
what I can say is that the script puppy_full_installer does not touch
partition tables.

[Scooby]

Tralllalllalla Why can I not delete this extra superfluous post

[april]

Maybe this is why a pet is needed then again april did get it to run
in the end

........I could have hidden it but sometimes I am just a bit slow especially when I have no coffee. Ran out and am travelling south in boat so grumpy too

In this run what did you have mounted on /mnt/sr0?

The script urges you to
"either mount a CD/DVD or an ISO file"

..........CD with Precise 5.7.1 files on it see pic

how do you run "grub4dos-config"

..from menu

[starhawk]

Irony is fun sometimes...

http://murga-linux.com/puppy/viewtopic.php?t=106066

Nothing sinister, I promise. Just an observation.

[bigpup]

starhawk,

That is where this script was originally made.
I posted it here to move it out of the section of the forum that is for discussion of programing in general.

Did you ever get it to work for you?

I feel this is cutting edge for Puppy.
Doing full installs to USB flash drives, has never been supported by Puppy installers.
Well, Quirky did do it, but it is not official Puppy.

[bigpup]

Scooby,

I updated the first post.

Thanks!!

If you change this script and tell us you did it. I will update the first post.

I want to ask you all why you feel there is a need for a pet for this?
It is one file. easier to just DL and run.

Just easier for people to download and run as a pet.
Some people have problems understanding this:
Download.
Unzip
Give execute permission
In a terminal enter: sh puppy_full_installer

[Scooby]

Code: Select all

...
now run grub4dos-config to make it bootable.
#  grub4dos-config
bash: grub4dos-config: command not found
# grub4dos-config
bash: grub4dos-config: command not found

Downloaded grub4dos-0.4.4.v1.9.2.pet and checked that the executable is
/usr/sbin/grub4dosconfig

I think /usr/sbin is in PATH on puppy right?

I updated puppy_full_installer message of to reflect the correct name of the executable to avoid the situation above


bigpup can you please update link in first post to

https://gist.github.com/suedi/8897880a8 ... 86aea4.zip

[april]

OK Thank you very much for your efforts .
I assume now I must gparted my USB to remove partitions first . I'll do that in a sec. Here is terminal output with a couple of errors I spotted just in case you want to see .

Code: Select all

# ls
puppy_full_installer
# puppy_full_installer
bash: puppy_full_installer: command not found
# sh puppy_full_installer
I assume you have formatted the drive to ext(2,3,4)
I'm not babysitting so if it isn't do it now!
Is it? (y or n + [Enter/Return])
y
Assuming you are not stupid...
OK, remember.. I'm not responsible here...
Proceeding...

Insert your drive and mount it.
Then tell me the target drive partition (eg: sdc1, sdd1 etc)
GET IT RIGHT!
what is the drive partition?
sdd1
Seems sane..
Ok, /mnt/sdd1 exists. Good.

Now we need some source files
either mount a CD/DVD or an ISO file
THEN, tell me the mount point path
EXAMPLE: /mnt/sr0 or /mnt/+mnt+sda5+iso+tahr64-6.0.3.9.iso
An easy way to do that is enter the mounted folder and type 'pwd' in a terminal
Type the source mount point path.
/mnt/sr0
Seems sane..

Install from /mnt/sr0 to /mnt/sdd1
Press y + [Enter/Return] to continue
y
---------------------------------------------------------------

Decompressing: /mnt/sr0/puppy_precise_5.7.1.sfs
To target: /mnt/sdd1

please have patience.

Parallel unsquashfs: Using 2 processors
15759 inodes (18306 blocks) to write

[===========================================================\] 18306/18306 100%
created 12545 files
created 2145 directories
created 2878 symlinks
created 336 devices
created 0 fifos
Upgrading Precise Puppy to version 5.7.1...
Updating w.m. menus...
Updating boot and shutdown system scripts...
Executing depmod, to update module files...
find: warning: you have specified the -noleaf option after a non-option argument -path, but options are not positional (-noleaf affects tests specified before it as well as those specified after it).  Please specify options before other arguments.

Updating /etc/networkmodules...
Adding i2400m-usb
Adding iwlwifi
Adding rndis_wlan

Took a big chunk out here


Adding int51x1
Adding qmi_wwan
Adding hso
Adding atl2
Adding prism2_usb
gtk-update-icon-cache: Cache file created successfully.
Error opening file for reading: No such file or directory
Error opening file for reading: No such file or directory
Error opening file for reading: No such file or directory
Files being translated:
 /etc/rc.d/functions4puppy4
 /etc/rc.d/rc.sysinit
 /etc/rc.d/rc.update
 /etc/rc.d/rc.country
 /usr/local/petget/0setup
Files being translated:
 /root/Choices/ROX-Filer/PuppyPin
 /root/.jwmrc-tray
Generating /root/.icewm/menu...
Generating /root/.jwmrc...
---------------------------------------------------------------

Hopefully we're done ...

Do not forget if your target is a USB drive then add "rootwait"
in the Options textbox in grub4dos-config window with title:

"Grub4DosConfig - List of detected operating systems"

It is essential for a successful boot.

now run grub4dosconfig to make it bootable.
# grub4dosconfig
root: PROBEDISK ERROR: MOUNTED UNPLUGGED sdc1
/usr/sbin/grub4dosconfig: line 691: 14022 Terminated              $GTKDIALOG -p DIALOG -c &>/dev/null
Sectors/Track is expected 63. But the drive: 'sdd' seems Sectors/Track= \nThe Grub4DosConfig does not support this drive. Remove all the partitions on the drive (after backing up all the data) and rewrite the partition tabe with Gparted.
# 

[april]

Success ! A booting USB stick

I started again and reformatted the USB stick but I cannot get an option that lets me format it as sdc. Rather I can only make sdc1 so that's what I did and I added the boot flag later too .

I did not understand where to put the "rootwait" command as I could not find an options box? Actually I found this now where "ro" appears on the first GUI page. I assume you delete the "ro"

Here is the output from this session . let me know and I'll remove the long posts when you are ready.

Code: Select all

# sh puppy_full_installer
I assume you have formatted the drive to ext(2,3,4)
I'm not babysitting so if it isn't do it now!
Is it? (y or n + [Enter/Return])
y
Assuming you are not stupid...
OK, remember.. I'm not responsible here...
Proceeding...

Insert your drive and mount it.
Then tell me the target drive partition (eg: sdc1, sdd1 etc)
GET IT RIGHT!
what is the drive partition?
sdc1
Seems sane..
Ok, /mnt/sdc1 exists. Good.

Now we need some source files
either mount a CD/DVD or an ISO file
THEN, tell me the mount point path
EXAMPLE: /mnt/sr0 or /mnt/+mnt+sda5+iso+tahr64-6.0.3.9.iso
An easy way to do that is enter the mounted folder and type 'pwd' in a terminal
Type the source mount point path.
/mnt/sr0
Seems sane..

Install from /mnt/sr0 to /mnt/sdc1
Press y + [Enter/Return] to continue
y
---------------------------------------------------------------

Decompressing: /mnt/sr0/puppy_precise_5.7.1.sfs
To target: /mnt/sdc1

please have patience.

Parallel unsquashfs: Using 2 processors
15759 inodes (18306 blocks) to write

[===========================================================\] 18306/18306 100%
created 12545 files
created 2145 directories
created 2878 symlinks
created 336 devices
created 0 fifos
Upgrading Precise Puppy to version 5.7.1...
Updating w.m. menus...
Updating boot and shutdown system scripts...
Executing depmod, to update module files...
find: warning: you have specified the -noleaf option after a non-option argument -path, but options are not positional (-noleaf affects tests specified before it as well as those specified after it).  Please specify options before other arguments.

Updating /etc/networkmodules...
Adding i2400m-usb
Adding sfc
Adding hamachi
Adding yellowfin

Took a big chunk out here

Adding hostap_cs
Adding hostap_pci
Adding iwlwifi
Adding atl2
Adding prism2_usb
gtk-update-icon-cache: Cache file created successfully.
Error opening file for reading: No such file or directory
Error opening file for reading: No such file or directory
Error opening file for reading: No such file or directory
Files being translated:
 /etc/rc.d/functions4puppy4
 /etc/rc.d/rc.sysinit
 /etc/rc.d/rc.update
 /etc/rc.d/rc.country
 /usr/local/petget/0setup
Files being translated:
 /root/Choices/ROX-Filer/PuppyPin
 /root/.jwmrc-tray
Generating /root/.icewm/menu...
Generating /root/.jwmrc...
---------------------------------------------------------------

Hopefully we're done ...

Do not forget if your target is a USB drive then add "rootwait"
in the Options textbox in grub4dos-config window with title:

"Grub4DosConfig - List of detected operating systems"

It is essential for a successful boot.

now run grub4dosconfig to make it bootable.
# grub4dosconfig
/usr/sbin/grub4dosconfig: line 691: 29920 Terminated              $GTKDIALOG -p DIALOG -c &>/dev/null
Boot flag not found on sdc.\nSome BIOS does not boot from the drive which has no boot flag. Click 'Cancel' here and set the boot flag by using GParted or something. But you can proceed installing grub4dos first.
find: File system loop detected; `/mnt/sdc1/lib/i386-linux-gnu' is part of the same file system loop as `/mnt/sdc1/lib'.
find: `/mnt/sdc1/run/tmp': Too many levels of symbolic links
find: `/mnt/sdc1/tmp/tmp': Too many levels of symbolic links
find: File system loop detected; `/mnt/sdc1/lib/i386-linux-gnu' is part of the same file system loop as `/mnt/sdc1/lib'.
find: `/mnt/sdc1/run/tmp': Too many levels of symbolic links
find: `/mnt/sdc1/tmp/tmp': Too many levels of symbolic links
find: File system loop detected; `/initrd/mnt/dev_save/lib/i386-linux-gnu' is part of the same file system loop as `/initrd/mnt/dev_save/lib'.
find: File system loop detected; `/initrd/mnt/dev_save/lib/i386-linux-gnu' is part of the same file system loop as `/initrd/mnt/dev_save/lib'.
0:1:2
/usr/sbin/grub4dosconfig: line 1285: 31123 Terminated              $GTKDIALOG -p DIALOG -c &>/dev/null
/usr/sbin/grub4dosconfig: line 1986: 31884 Terminated              $GTKDIALOG -p DIALOG -c &>/dev/null

[starhawk]

starhawk,

That is where this script was originally made.
I posted it here to move it out of the section of the forum that is for discussion of programing in general.

Did you ever get it to work for you?

I feel this is cutting edge for Puppy.
Doing full installs to USB flash drives, has never been supported by Puppy installers.
Well, Quirky did do it, but it is not official Puppy.

That post was directed primarily at april, who does not seem to like me after she (?) was rude to me and I returned fire. Sorry for the confusion.

I did not get it working, yet -- as posted in the other topic, to which I linked -- I'm having what I believe are hardware troubles. The machine will boot from USB but not from an SD card in an adapter via its internal IDE header. I've replaced the adapter, and am in the process of replacing the system itself entirely -- see my most recent post in the other topic, please -- and the card on its own reads fine. If all else fails, I'll replace the card itself -- but since it's a 64gb SD card, it isn't exactly cheap for me (I'm sadly in the income bracket where $15 is kind of a large expenditure), so I'm trying to avoid that if I can.

TBH I'm starting to wonder if there's something in the air around here that fouls chipsets -- that is one of three or four machines, now, that will not properly boot! Very strange...

Well, to be completely fair -- with this particular box, when I took the heatsink off to replace the thermal transfer material underneath, some months ago, I managed to accidentally knock off a tiny surface-mount "passive" (resistor or capacitor) that... well... does something. (The clearance between parts and spring-pins on this thing is INSANE. Way too small.) Threw the part away, as it was in such shape that there was no rescuing it. I've not had any real trouble with it other than (a) stubbornness with openchrome and (b) now it suddenly won't boot, so for a long time I wrote that missing component off as harmless. (In my experience, something like that tends either to have an immediate, severe effect, or be completely harmless forever.) Now, though, I'm beginning to reconsider that conclusion...

[bigpup]

I did not understand where to put the "rootwait" command as I could not find an options box? Actually I found this now where "ro" appears on the first GUI page. I assume you delete the "ro"

You found the correct place to enter the option.
Yes I would delete the "ro" and only have "rootwait" as the added option.

I actually used "ro" and "rootwait" as the added options and Puppy ran even slower.
I edited the Grub4dos boot menu entry and removed the "ro".
It ran much faster without the "ro" option. Just use "rootwait" as the only added option.

[Scooby]

Success ! A booting USB stick

Good news, How would you rate the difficulty of this script? Intermediate?

I did not understand where to put the "rootwait" command as I could not find an options box? Actually I found this now where "ro" appears on the first GUI page. I assume you delete the "ro"

In your opinion could this be communicated in a better way?
How to make it more clear?

I did replace "ro" with "rootwait rw" don't really know the difference
though "rootwait" is essential

Here is the output from this session . let me know and I'll remove the long posts when you are ready.
...

No need to remove, please keep them for reference


Seems like it worked out OK


If keeping it as a terminal script, is there anyway you think that
will make it easier to understand

I don't mean this

Code: Select all

# puppy_full_installer
bash: puppy_full_installer: command not found
# sh puppy_full_installer 

This would be solved by putting script in .pet and place it in /bin
that is in PATH

then you could run it with

Code: Select all

# puppy_full_installer

[bigpup]

I started again and reformatted the USB stick but I cannot get an option that lets me format it as sdc. Rather I can only make sdc1 so that's what I did and I added the boot flag later too .

You did it correctly.
In your system the USB flash drive is seen as sdc.
Any partitions on it are identified as sdc1, sdc2, sdc3, etc.....
That is normal identification.

Any drive has to have:
At least one partition.
That partition has to be formatted.
Data is written to the partition.

[april]

No I think you have it thanks Scooby.
As with everything with computers reading the post carefully is the main bit
cheers