How to make a GNU/Linux frugal installation with copy-to-R.A.M. mode system: PuppyLinux

Revision [26640]

This is an old revision of InstallationFrugal made by coolpup on 2013-03-16 07:44:07.

HomePage > ComponentHowTo Components and HowTos > InstallationIndex Installation

How to manually make a frugal Puppy installation

A frugal Puppy installation is performed by extracting the contents of the container file (either ISO or ZIP) to normally one, i.e. the same, directory residing optimally on an EXT4 formatted partition. Let that desired partition be known as the target partition since one is aiming to install to it. That partition may be located on:

either an external device, e.g. U.S.B. flash memory drive (U.F.D.) (often erroneously referred to as a memory stick) or some other flash memory device

or, an internal device, usually a hard disk drive (H.D.D.)

Therefore, the target device is the device which contains the partition that one aims to install to, such as an external flash memory drive or an internal hard disk drive. Such a device must have a partition with a minimum storage capacity of 256MB.

WARNING: If the target partition contains any important files copy them elsewhere if required, because they will be destroyed when the target partition is formatted.

The following procedure assumes that one is running Puppy Linux. However, the same procedure is followed with any running Linux distribution. If one is running Microsoft Windows go to Appendix 1 below.

Step 1 - Installing a boot-loader to the target device

determine the correct device name of the target device to work on, via the command-line interface:
```
fdisk -l && probedisk2
```

1A. Using SYSLINUX for EXT4 file-systems

install a recent version of SYSLINUX

rename any existing directory at /dev/sdX/boot/syslinux:
```
mv /dev/sdX/boot/syslinux /dev/sdX/boot/syslinux.old
```

create a new /dev/sdX/boot/syslinux directory:
```
cp -afpru /usr/lib/syslinux /dev/sdX/boot/
```

install the boot code to the M.B.R. of the target device X:

/bin/dd bs=446 conv=notrunc count=1 if=/usr/lib/syslinux/mbr.bin of=/dev/sdX

install the boot system file ldlinux.sys to the target partition directory sdXY/boot, ensuring that it is mounted first:
```
/bin/mount /dev/sdXY /mnt/sdXY && /bin/mkdir -p /mnt/sdXY/boot && /sbin/extlinux -i --stupid /mnt/sdXY/boot
```

place the boot configuration file syslinux.cfg on the target device at /boot (this file will need editing if more than one Puppy version has been installed)

follow the additional instructions in Appendix 3 at LiveDVD

if there is already an existing Puppy installation re-boot the computer with the flash memory device connected; if there is no existing Puppy installation then either both steps 2 and 3 or just step 3 (if any existing file-system is to be retained) must be performed before re-booting the computer with the flash memory device connected

1B. Using SYSLINUX for FAT32 file-systems

install a recent version of SYSLINUX

rename any existing directory at /sdX/boot/syslinux:

mv /dev/sdX/boot/syslinux /dev/sdX/boot/syslinux.old

create a new /dev/sdX/boot/syslinux directory:
```
cp -afpru /usr/lib/syslinux /dev/sdX/boot/
```

install the boot code to the M.B.R. of the target device X:

/bin/dd bs=446 conv=notrunc count=1 if=/usr/lib/syslinux/mbr.bin of=/dev/sdX

install the boot system file ldlinux.sys to the target partition directory sdXY/boot:
```
/bin/mkdir -p /mnt/sdXY/boot && /usr/bin/syslinux -i -s /dev/sdXY/boot
```

place the boot configuration file syslinux.cfg on the target device at /boot (this will need editing if more than one Puppy version has been installed)

follow the additional instructions in Appendix 3 at LiveDVD

if there is already an existing Puppy installation re-boot the computer with the flash memory device connected; if there is no existing Puppy installation then either both steps 2 and 3 or just step 3 (if any existing file-system is to be retained) must be performed before re-booting the computer with the flash memory device connected

1C. Using GRUBforDOS for all common file-systems

install the latest available version of helper program Grub4DosConfig

install the boot code to the M.B.R. of the target device X:
```
bootlace.com --time-out=0 /dev/sdX
```

install the boot system file grldr by placing it on the target device

install the boot configuration file menu.lst, or update an existing one, by using Grub4DosConfig: Menu > System > Grub4Dos

follow the additional instructions in Appendix 3 at LiveDVD

if there is already an existing Puppy installation re-boot the computer with the flash memory device connected; if there is no existing Puppy installation then either both steps 2 and 3 or just step 3 (if any existing file-system is to be retained) must be performed before re-booting the computer with the flash memory device connected

Step 2 - Creating a partition and file-system on the target device

install the latest available versions of bzip2, e2fsprogs, grep, parted and tar

determine the correct device name of the target device to work on, via the command-line interface:
```
fdisk -l && probedisk2
```

ensure to dismount the target device X:
```
umount /dev/sdX
```

(optional) create a new partition table (disklabel) on the target device X (WARNING - access to all existing files on the target device will be lost):
```
/usr/sbin/parted /dev/sdX mklabel msdos && /usr/sbin/parted -l print
```

(optional) create a partition(s) or, delete or resize an existing one on the target device X: Menu > System > GParted > Partition:

/usr/sbin/parted /dev/sdX mkpart primary ext4 0% 100% && /usr/sbin/parted /dev/sdX print && /usr/sbin/parted /dev/sdX align-check opt 1

(optional) create the required file-system (formatting) on the partition(s) of the target device X (WARNING - all data on the target partition will be over-written (destroyed)): Menu > System > GParted > Partition > Format to

select EXT4 for all partitions if possible {fastest file-system for flash memory devices}

/sbin/mkfs.ext4 -b 4096 -m 0 -L PUPPY -O extents,uninit_bg,dir_index,filetype,has_journal,sparse_super -E stride=4,stripe-width=256 /dev/sdXY

then optionally select FAT32 for another partition for sharing the device with non-Linux devices {requires dosfstools}
```
/usr/sbin/mkdosfs -v -n PUPPY -F 32 /dev/sdXY
```

ensure the boot flag status of the device is set to on via Menu > System > GParted > Partition > Manage Flags > boot or via the command-line interface, e.g for partition 1 of device X
```
/usr/sbin/parted /dev/sdX set 1 boot on
```

Step 3 - Installing Puppy to the target device

mount the target device

mount the Puppy ISO (or ZIP) file by clicking on it

copy from the ISO (or ZIP) directory to the target device either all the files, or, just these essential ones: vmlinuz, initrd.gz, and all those with the extension .sfs (if more than one Puppy version is to be installed ensure that they are each contained within their own directory)

Step 4 - Creating the storage file

When shutting down for the first time there will be the option to create a personal storage (pupsave) file which must be chosen if personal settings and configuration are to be kept.

Appendix 1 - Installation to any external device, from within Microsoft Windows

Format the drive or partition to FAT32

Download and extract the latest syslinux .zip file to the C drive, i.e. C:\syslinux

Then go to directory C:\syslinux\win32\:
```
cd C:\syslinux\win32\
```

Then, with administrator privileges, run the syslinux command to make the target drive bootable: (where X is the drive letter for the target drive or partition)
```
syslinux.exe -m -a X:
```

Open the Puppy ISO (or ZIP) file to view its contents, using e.g. 7-zip, (it is important that the original file names be kept)

Copy to the target device the files: vmlinuz, initrd.gz, and all those with the extensions .sfs

Download this sample boot-loader configuration file syslinux.cfg and place it on the target device

Re-boot the computer with the flash memory device connected

Appendix 2 - Installation to any Microsoft Windows partition and using GRUBforDOS as boot-loader

Installing the boot-loader to the internal hard disk drive (where Microsoft Windows resides)
http://www.icpug.org.uk/national/linnwin/step1-xp.htm
http://puppy.b0x.me/lin-n-win
Installing the boot-loader to an external drive
http://shino.pos.to/linux/lupq/puppydualboot.html

When making an installation to an internal H.D.D. with an existing operating system, one has the option to either allow that operating system to remain or be removed. Only remove the existing operating system if the computer is more than 3 years old since most computer manufacturers cease to provide new B.I.O.S. versions after that time. If the intention is to remove the existing operating system, regardless of computer age, then ensure to check for and install any B.I.O.S. updates first.

If the Puppy files are to be appended, by making a frugal installation only of Puppy, then this would involve one of the following:

either making a new partition for Puppy (not recommended)

or, using an existing partition for Puppy (recommended)

One can place a frugal installation within a pre-existing Windows installation. The save file, although itself is comprised of a Linux file-system, may reside on a F.A.T. or N.T.F.S. partition; which is why a frugal installation is also called a "co-exist" installation. A full hard disk drive installation on a F.A.T. partition is not possible because F.A.T. partitions do not support Linux symbolic links.

There is an option to install from within Microsoft Windows using the relevant file from here: http://www.mediafire.com/?5ah0d0rzcz5cc

Appendix 3 - How to run Puppy Linux from a flash memory drive on any computer already running

QEMUpuppy

Appendix 4 - Absent internal H.D.D.

Older Puppy versions will not boot from U.F.D. if the internal H.D.D. has been removed:

Posted on 23 Apr 2011, 22:54 by perthie
USB Install Issue?
I notice that you still haven't commented on this issue. A machine missing an internal hard drive can no longer be booted from a flash drive. The new search procedure fails to find the sfs file on the flash drive.
Posted on 24 Apr 2011, 8:20 by BarryK
Re no boot usb
I have written it down in my to-do list.

http://bkhome.org/blog/?viewDetailed=02231