Revision [27217]

This is an old revision of InstallationFrugal made by coolpup on 2013-04-17 04:39:49.

 

HomePage >
Components and HowTos > Installation

How to manually make a frugal Puppy Linux 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. Let that desired partition be known as the target
partition since one is aiming to install to it. That partition may be
located on: a flash memory drive
(often erroneously referred to as a memory stick)
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. The minimum, nominal storage capacity for a
flash memory drive is 256MB.

WARNING: If the target partition contains any important
files Unknown action; the action name must not contain special characters., because they will be destroyed whenever the target
partition is formatted.






IMPORTANT: Unknown action; the action name must not contain special characters. to work on, via the
command-line interface:
lsblk







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

Step 1 - PARTITIONING
partition structure on the target drive bzip2, grep, parted, tar device X (WARNING - access to all
existing files on the target device will be lost):
/usr/sbin/parted 
/dev/sdX mklabel gpt && /usr/sbin/parted -l
X (where set 1 defines partition 1 of device X to be the boot
partition):
/usr/sbin/parted -a opt /dev/sdX mkpart primary ext4 8 
100% set 1 boot on && /usr/sbin/parted /dev/sdX disk_set 
pmbr_boot on && /usr/sbin/parted /dev/sdX set 1 legacy_boot on 
print


Step 2 - FORMATTING
file-system structure on the target drive of the target device X (WARNING - all
data on the target partition will be over-written (destroyed)): e2fsprogs}:
/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
dosfstools}:
mkdosfs -v -n 
PUPPY -F 16 /dev/sdXY


Step 3 - BOOT-LOADER INSTALLATION
the boot-loader SYSLINUX files for one's use; it does not replace any of the existing boot-loader
files which one's actual operating system makes use of for booting
(starting-up) itself (sample file for flash
memory drives only) on the target device by copying it to
/boot/syslinux (this file will need editing if more than one Puppy
version has been installed; the
pkeys parameter will
need to be configured for one's geographical location) partition directory sdXY/boot:
/bin/mount /dev/sdXY /mnt/sdXY && /bin/mkdir -p /mnt/sdXY/boot
 && /sbin/extlinux -i --stupid /mnt/sdXY/boot

Step 4 - SYSTEM INSTALLATION
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) personal storage (pupsave) file which must be chosen if personal
settings and configuration are to be saved.



Appendix 1 - Installation to any external device, from within Microsoft Windows
syslinux
.zip file to the C drive, i.e. C:\syslinux the target drive bootable: (where X is the drive letter for the target
drive or partition)
syslinux.exe -m -a X:
7-zip, (it is important that the original file names be kept) all those with the extensions .sfs syslinux.cfg (for flash
memory drives only} and place it on the target device
Appendix 2 - Installation to any Microsoft Windows partition and using GRUBforDOS as boot-loader
Microsoft Windows resides)
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:
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

Appendix 4 - Absent internal H.D.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

Appendix 5 - Using GRUBforDOS bootloader for all common file-systems
Grub4DosConfig
bootlace.com --time-out=0 /dev/sdX
grldr by placing it on the
target device existing one, by using Grub4DosConfig: Menu > System > Grub4Dos



Categories
CategoryInstallation
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki