Revision [30051]

Last edited on 2014-04-10 14:48:57 by darkcity
Additions:
~On start-up these file-systems are super-imposed upon each other so that they appear merged. Additional files and alterations are written to the Puppy Save File (if within the Linux directory structure). The directory structure viewed in a [[FileManagers file manager]] or listed by a [[TerminalEmulator terminal emulator]] is actually **contained within** these compressed files.
Deletions:
~On start-up these file-systems are super-imposed upon each other so that they appear merged. Additional files and alterations are written to the Puppy Save File (if within the Linux directory structure). The directory structure viewed in a [[FileManagers file manager]] or listed by a [[TerminalEmulater terminal emulator]] is actually **contained within** these compressed files.


Revision [30050]

Edited on 2014-04-10 14:33:11 by darkcity [~When first run: ~~- the Puppy Linux initializes t]
Additions:
~~- the Puppy Linux initializes the layered file system starting with the [[BaseSFS]] (also known as ""PupSfs""). This is a [[SquashFS Sfs file]] containing Linux file system and directory structure ([[RootFS]]) The file is either accessed from the disk or loaded into RAM (read only) eg. lupu_528.sfs
Deletions:
~~- the Puppy Linux loads the [[BaseSFS]] (also known as ""PupSfs"") a [[SquashFS Sfs file]] containing Linux file system and directory structure ([[RootFS]]) (read only) eg. lupu_528.sfs


Revision [29123]

Edited on 2013-10-07 10:35:43 by darkcity [~When first run: ~~- the Puppy Linux initializes t]
Additions:
==Also on the Wiki==
~[[HowtoAddSFStoFullInstall How to Add SFS to Full Installation]]
~[[PupMode]]
==Related Webpages==
~[[http://puppylinux.com/development/howpuppyworks.html Detailed Explained of How Puppy Installs (puppylinux.com)]]
Deletions:
==Also see==
[[HowtoAddSFStoFullInstall How to Add SFS to Full Installation]]


Revision [28618]

Edited on 2013-08-24 17:33:58 by darkcity [revise text]
Additions:
~This page explains the differences between [[Frugal]] and [[InstallationFullHDD Full]] installation.
Deletions:
~This page explains the differences between [[InstallationFrugal Frugal]] and [[InstallationFullHDD Full]] installation.


Revision [28617]

Edited on 2013-08-24 17:31:14 by darkcity [revise text]
Additions:
~In a **Full installation** the system files ([[RootFS|Linux directory structure]]) takes up a whole [[WikiPedia:Disk_partitioning drive partition]]. The contents from Puppy Linux's BaseSFS are extracted to the linux directory structure. All subsequent software installations, file edits and additions are made directly to the partition's file system. The directory structure is stored as it appears in the [[FileManagers file manager]] or listed by a [[TerminalEmulator terminal emulator]].
~In a **Frugal** installation the system files ([[RootFS|Linux directory structure]]) are compressed into a couple of file (technically filesystems within a file):
Deletions:
~In a **Full installation** the system files ([RootFS|Linux directory structure]) takes up a whole [[WikiPedia:Disk_partitioning drive partition]]. The contents from Puppy Linux's BaseSFS are extracted to the linux directory structure. All subsequent software installations, file edits and additions are made directly to the partition's file system. The directory structure is stored as it appears in the [[FileManagers file manager]] or listed by a [[TerminalEmulator terminal emulator]].
~In a **Frugal** installation the system files ([RootFS|Linux directory structure]) are compressed into a couple of file (technically filesystems within a file):


Revision [28616]

Edited on 2013-08-24 17:30:48 by darkcity [revise text]
Additions:
~This page explains the differences between [[InstallationFrugal Frugal]] and [[InstallationFullHDD Full]] installation.
~In a **Full installation** the system files ([RootFS|Linux directory structure]) takes up a whole [[WikiPedia:Disk_partitioning drive partition]]. The contents from Puppy Linux's BaseSFS are extracted to the linux directory structure. All subsequent software installations, file edits and additions are made directly to the partition's file system. The directory structure is stored as it appears in the [[FileManagers file manager]] or listed by a [[TerminalEmulator terminal emulator]].
~In a **Frugal** installation the system files ([RootFS|Linux directory structure]) are compressed into a couple of file (technically filesystems within a file):
---
~When first run:
~~- the Puppy Linux loads the [[BaseSFS]] (also known as ""PupSfs"") a [[SquashFS Sfs file]] containing Linux file system and directory structure ([[RootFS]]) (read only) eg. lupu_528.sfs
---
~Additional files:
~~- the Puppy [[SaveFile 'save file']] containing settings, additional software, modifications etc. (read/write) eg. lupusave-mysave.2fs
~~- additional software [[SquashFS Sfs files]] (read only) eg. Gimp_2.7.3_528.sfs
---
~On start-up these file-systems are super-imposed upon each other so that they appear merged. Additional files and alterations are written to the Puppy Save File (if within the Linux directory structure). The directory structure viewed in a [[FileManagers file manager]] or listed by a [[TerminalEmulater terminal emulator]] is actually **contained within** these compressed files.
---
~For more information see [[http://puppylinux.com/development/howpuppyworks.html How Puppy works]].
Deletions:
This page explains the differences between [[InstallationFrugal Frugal]] and [[InstallationFullHDD Full]] installation.
In a **Full installation** the linux directory structure takes up a whole [[WikiPedia:Disk_partitioning drive partition]]. The contents from Puppy Linux's BaseSFS are extracted to the linux directory structure. All subsequent software installations, file edits and additions are made directly to the partition's file system. The directory structure is stored as it appears in the [[FileManagers file manager]] or listed by a [[TerminalEmulator terminal emulator]].
A frugal installation involves using compressed 'filesystem-within-a-file/s' without expanding them. These files are,
When first run:
~- the Puppy Linux loads the [[BaseSFS]] (also known as ""PupSfs"") a [[SquashFS Sfs file]] containing Linux file system and directory structure ([[RootFS]]) (read only) eg. lupu_528.sfs
Additional files:
~- the Puppy [[SaveFile 'save file']] containing settings, additional software, modifications etc. (read/write) eg. lupusave-mysave.2fs
~- additional software [[SquashFS Sfs files]] (read only) eg. Gimp_2.7.3_528.sfs
On start-up these file-systems are super-imposed upon each other so that they appear merged. Additional files and alterations are written to the Puppy Save File (if within the Linux directory structure). The directory structure viewed in a [[FileManagers file manager]] or listed by a [[TerminalEmulater terminal emulator]] is actually **contained within** these compressed files.
For more information see [[http://puppylinux.com/development/howpuppyworks.html How Puppy works]].


Revision [24396]

Edited on 2012-10-12 13:10:08 by darkcity ['filesystem-within-a-file/s]
Additions:
A frugal installation involves using compressed 'filesystem-within-a-file/s' without expanding them. These files are,
Deletions:
A frugal installation involves using compressed file/s without expanding them. These files are,


Revision [20733]

Edited on 2012-02-24 07:14:46 by darkcity [improve text]
Additions:
In a **Full installation** the linux directory structure takes up a whole [[WikiPedia:Disk_partitioning drive partition]]. The contents from Puppy Linux's BaseSFS are extracted to the linux directory structure. All subsequent software installations, file edits and additions are made directly to the partition's file system. The directory structure is stored as it appears in the [[FileManagers file manager]] or listed by a [[TerminalEmulator terminal emulator]].
On start-up these file-systems are super-imposed upon each other so that they appear merged. Additional files and alterations are written to the Puppy Save File (if within the Linux directory structure). The directory structure viewed in a [[FileManagers file manager]] or listed by a [[TerminalEmulater terminal emulator]] is actually **contained within** these compressed files.
Deletions:
In a **Full installation** the linux directory structure takes up a whole [[WikiPedia:Disk_partitioning drive partition]]. The contents from Puppy Linux's BaseSFS are extracted to the linux directory structure. All subsequent software installations, file edits and additions are made directly to the partition's file system. The directory structure is stored as viewed as it appears in a [[FileWindow file window]] or listed by a [[TerminalEmulator terminal emulator]].
On start-up these file-systems are super-imposed upon each other so that they appear merged. Additional files and alterations are written to the Puppy Save File (if within the Linux directory structure). The directory structure viewed in a [[FileWindow file window]] or listed by a [[TerminalEmulater terminal emulator]] is actually **contained within** these compressed files.


Revision [20732]

Edited on 2012-02-24 07:12:36 by darkcity [improve text full install]
Additions:
In a **Full installation** the linux directory structure takes up a whole [[WikiPedia:Disk_partitioning drive partition]]. The contents from Puppy Linux's BaseSFS are extracted to the linux directory structure. All subsequent software installations, file edits and additions are made directly to the partition's file system. The directory structure is stored as viewed as it appears in a [[FileWindow file window]] or listed by a [[TerminalEmulator terminal emulator]].
Deletions:
Full installation involves extracting the linux directory structure from Puppy linux's BaseSFS to a drive [[WikiPedia:Disk_partitioning partition]] with a chosen [[FileSystem file system]]. All subsequent software installations, file edits and additions are saved in this file system. The directory structure is stored as viewed in a [[FileWindow file window]] or listed by a [[TerminalEmulator terminal emulator]].


Revision [20442]

Edited on 2012-02-04 05:27:38 by darkcity [pup save file]
Additions:
|=|[[SaveFile Pup SaveFile]] || No, directly accesses [[RootFS]] || Yes, saved directly to disk|| Yes, in RAM (saved to disk on request/reboot)||
Deletions:
|=|[[SaveFile Pup SaveFile]] || No, directly access [[RootFS]] || Yes, saved directly to disk|| Yes, in RAM (saved to disk on request/reboot)||


Revision [20441]

Edited on 2012-02-04 05:27:03 by darkcity [pup save info]
Additions:
|=|[[SaveFile Pup SaveFile]] || No, directly access [[RootFS]] || Yes, saved directly to disk|| Yes, in RAM (saved to disk on request/reboot)||
Deletions:
|=|[[SaveFile Pup SaveFile]] || No, directly access [[RootFS]] || Yes, saved directly to disk|| Yes, in RAM (saved to disk on request/reboot)||


Revision [20440]

Edited on 2012-02-04 05:26:36 by darkcity [pup save file]
Additions:
On start-up these file-systems are super-imposed upon each other so that they appear merged. Additional files and alterations are written to the Puppy Save File (if within the Linux directory structure). The directory structure viewed in a [[FileWindow file window]] or listed by a [[TerminalEmulater terminal emulator]] is actually **contained within** these compressed files.
For more information see [[http://puppylinux.com/development/howpuppyworks.html How Puppy works]].
|=|Installation Protection ||[[RootFS]] writable with root user access||BaseSfs Read only ||BaseSfs Read only||
|=|[[SaveFile Pup SaveFile]] || No, directly access [[RootFS]] || Yes, saved directly to disk|| Yes, in RAM (saved to disk on request/reboot)||
Deletions:
On start-up these file-systems are super-imposed upon each other so that they appear merged. Additional files and alterations are written to the Puppy Save File (if within the Linux directory structure). The directory structure viewed in a [[FileWindow file window]] or listed by a [[TerminalEmulater terminal emulator]] is actually **contented within** these compressed files.
|=|Installation Protection ||Whole linux structure writable with root access||BaseSfs Read only ||BaseSfs Read only||


Revision [20214]

Edited on 2012-01-08 15:51:38 by darkcity [pup save file]
Additions:
~- the Puppy Linux loads the [[BaseSFS]] (also known as ""PupSfs"") a [[SquashFS Sfs file]] containing Linux file system and directory structure ([[RootFS]]) (read only) eg. lupu_528.sfs
Deletions:
~- the Puppy Linux loads the [[BaseSFS]] (also known as PupSfs) a [[SquashFS Sfs file]] containing Linux file system and directory structure ([[RootFS]]) (read only) eg. lupu_528.sfs


Revision [20213]

Edited on 2012-01-08 15:51:21 by darkcity [pup save file]
Additions:
~- the Puppy Linux loads the [[BaseSFS]] (also known as PupSfs) a [[SquashFS Sfs file]] containing Linux file system and directory structure ([[RootFS]]) (read only) eg. lupu_528.sfs
Deletions:
~- the Puppy Linux loads the BaseSFS a [[SquashFS Sfs file]] containing Linux file system and directory structure (read only) eg. lupu_528.sfs


Revision [19556]

Edited on 2011-11-16 10:09:25 by darkcity [[SquashFS SFS]] files||Harder||Easy ||Easy||]
Additions:
|=|Load/Unload [[SquashFS SFS]] files||Harder||Easy ||Easy||
==Also see==
[[HowtoAddSFStoFullInstall How to Add SFS to Full Installation]]


Revision [19264]

Edited on 2011-10-30 10:51:18 by darkcity [FAT, NTFS, Linux Type ||]
Additions:
|=|Installation file system || Linux Type ||FAT, NTFS, Linux Type || FAT, NTFS, Linux Type ||
Deletions:
|=|Installation file system || FAT, NTFS, Linux Type || Linux Type|| Linux Type ||


Revision [19260]

Edited on 2011-10-30 09:45:06 by darkcity [Linux Type|| Linux Type ||]
Additions:
|=|Installation file system || FAT, NTFS, Linux Type || Linux Type|| Linux Type ||
Deletions:
|=|Installation file system || Linux Type|| Linux Type ||FAT, NTFS, Linux Type ||


Revision [19259]

Edited on 2011-10-30 09:43:58 by darkcity [|=|Speed || Medium||Likely to be slower|| Faster|]
Additions:
|=||=|Full|=|Frugal (not in RAM)|=|Frugal (copied to RAM)|=|
|=|Drive partition required||Yes||No||No||
|=|Installation directory || Requires a drive [[WikiPedia:Disk_partitioning partition]]|| Almost any directory || Almost any directory ||
|=|Speed || Medium||Likely to be slower|| Faster||
|=|Installation file system || Linux Type|| Linux Type ||FAT, NTFS, Linux Type ||
|=|Installation Protection ||Whole linux structure writable with root access||BaseSfs Read only ||BaseSfs Read only||
Deletions:
|=||=|Frugal|=|Full|=|
|=|Drive partition required||No||Yes||
|=|Installation directory || Almost any directory || Requires a drive [[WikiPedia:Disk_partitioning partition]]||
|=|Installation file system || FAT, NTFS, Linux Type || Linux Type ||
|=|BaseSfs protection || Read only || No baseSfs, whole linux structure Writable with root access||
|=|Speed if BaseSfs copied to RAM ||(needs sufficient RAM) Faster||No baseSfs, slower||
|=|Speed if BaseSfs NOT copied to RAM||Likely to be slower||Likely to be faster||


Revision [19258]

Edited on 2011-10-30 09:36:44 by darkcity [|=|Speed || Medium||Likely to be slower|| Faster|]
Additions:
|=|Speed if BaseSfs NOT copied to RAM||Likely to be slower||Likely to be faster||
Deletions:
|=|Speed BaseSfs NOT copied to RAM||Likely to be slower||Likely to be faster||


Revision [19257]

Edited on 2011-10-30 09:36:24 by darkcity [|=|Speed || Medium||Likely to be slower|| Faster|]
Additions:
|=|Speed if BaseSfs copied to RAM ||(needs sufficient RAM) Faster||No baseSfs, slower||
Deletions:
|=|Speed BaseSfs copied to RAM (needs sufficient RAM)||Faster||No baseSfs, slower||


Revision [19256]

Edited on 2011-10-30 09:34:20 by darkcity [basesfs]
Additions:
Full installation involves extracting the linux directory structure from Puppy linux's BaseSFS to a drive [[WikiPedia:Disk_partitioning partition]] with a chosen [[FileSystem file system]]. All subsequent software installations, file edits and additions are saved in this file system. The directory structure is stored as viewed in a [[FileWindow file window]] or listed by a [[TerminalEmulator terminal emulator]].
A frugal installation involves using compressed file/s without expanding them. These files are,
~- the Puppy Linux loads the BaseSFS a [[SquashFS Sfs file]] containing Linux file system and directory structure (read only) eg. lupu_528.sfs
~- the Puppy [[SaveFile 'save file']] containing settings, additional software, modifications etc. (read/write) eg. lupusave-mysave.2fs
~- additional software [[SquashFS Sfs files]] (read only) eg. Gimp_2.7.3_528.sfs
Deletions:
Full installation involves extracting the linux directory structure from Puppy linux's base [[SquashFS Sfs file]] to a drive [[WikiPedia:Disk_partitioning partition]] with a chosen [[FileSystem file system]]. All subsequent software installations, file edits and additions are saved in this file system. The directory structure is stored as viewed in a [[FileWindow file window]] or listed by a [[TerminalEmulater terminal emulator]].
A frugal installation involves using compressed file/s directly (also, vmlinuz are initrd.gz used) These files are,
~- the Puppy Linux loads the BaseSFS (a [[SquashFS Sfs file]] containing Linux file system and directory structure (read only))
~- the Puppy [[SaveFile 'save file']] containing additional software and files and modifications (read/write)
~- additional software [[SquashFS Sfs files]] (read only)


Revision [19255]

Edited on 2011-10-30 09:29:29 by darkcity [basesfs]
Additions:
~- the Puppy Linux loads the BaseSFS (a [[SquashFS Sfs file]] containing Linux file system and directory structure (read only))
|=|BaseSfs protection || Read only || No baseSfs, whole linux structure Writable with root access||
|=|Speed BaseSfs copied to RAM (needs sufficient RAM)||Faster||No baseSfs, slower||
|=|Speed BaseSfs NOT copied to RAM||Likely to be slower||Likely to be faster||
Deletions:
~- the Puppy Linux base [[SquashFS Sfs file]] containing Linux file system and directory structure (read only)
|=|Base file protection || Read only || No base-file, whole linux structure Writable with root access||
|=|Base Sfs copied to RAM ||Yes (if sufficient RAM) faster|| slower||
|=|Base not copied to RAM||Can be slower||N/A base never copied to RAM||


Revision [19249]

Edited on 2011-10-30 09:12:43 by darkcity [basesfs]
Additions:
|=|Base file protection || Read only || No base-file, whole linux structure Writable with root access||
Deletions:
|=|Base file protection || Read only || Writable ||


Revision [17510]

Edited on 2011-08-17 12:37:53 by darkcity [basesfs]
Additions:
[[HomePage]] > [[ComponentHowTo Components and HowTos]] > [[InstallationIndex Install]]
Deletions:
[[HomePage]] > [[HowToIndex HowTo]] > [[InstallationIndex Install]]


Revision [17042]

Edited on 2011-07-21 11:38:40 by darkcity [basesfs]
Additions:
A frugal installation involves using compressed file/s directly (also, vmlinuz are initrd.gz used) These files are,
Deletions:
A frugal installation involves using compressed file/s directly. These files are,


Revision [17018]

Edited on 2011-07-20 14:54:07 by darkcity [basesfs]
Additions:
|=|Base file protection || Read only || Writable ||
|=|Base Sfs copied to RAM ||Yes (if sufficient RAM) faster|| slower||
|=|Base not copied to RAM||Can be slower||N/A base never copied to RAM||
Deletions:
|=|Core file protection || Read only || Writable ||
|=|Speed increased by copy to RAM ||Yes (if sufficient RAM)||No||
|=|Slower on low RAM computer||Possibly||No||


Revision [17017]

Edited on 2011-07-20 14:50:24 by darkcity [basesfs]
Additions:
|=|Installation directory || Almost any directory || Requires a drive [[WikiPedia:Disk_partitioning partition]]||
Deletions:
|=|Installation directory || Almost any directory || Requires a drive [[partition]] ||


Revision [17016]

Edited on 2011-07-20 14:49:58 by darkcity [basesfs]
Additions:
Full installation involves extracting the linux directory structure from Puppy linux's base [[SquashFS Sfs file]] to a drive [[WikiPedia:Disk_partitioning partition]] with a chosen [[FileSystem file system]]. All subsequent software installations, file edits and additions are saved in this file system. The directory structure is stored as viewed in a [[FileWindow file window]] or listed by a [[TerminalEmulater terminal emulator]].
Deletions:
Full installation involves extracting the linux directory structure from Puppy linux's base [[SquashFS Sfs file]] to a drive [[partition]] with a chosen [[FileSystem file system]]. All subsequent software installations, file edits and additions are saved in this file system. The directory structure is stored as viewed in a [[FileWindow file window]] or listed by a [[TerminalEmulater terminal emulator]].


Revision [16989]

Edited on 2011-07-20 14:08:56 by darkcity [basesfs]
Additions:
On start-up these file-systems are super-imposed upon each other so that they appear merged. Additional files and alterations are written to the Puppy Save File (if within the Linux directory structure). The directory structure viewed in a [[FileWindow file window]] or listed by a [[TerminalEmulater terminal emulator]] is actually **contented within** these compressed files.
Deletions:
Upon start-up these file-systems are super-imposed upon each other so that they appear merged. Additional user files that are written to the written to the Puppy Save File, if within the Linux directory structure. The dictionary structure as viewed in a [[FileWindow file window]] or listed by a [[TerminalEmulater terminal emulator]] is actually contented within these compressed files.


Revision [16988]

Edited on 2011-07-20 14:06:26 by darkcity [basesfs]
Additions:
Full installation involves extracting the linux directory structure from Puppy linux's base [[SquashFS Sfs file]] to a drive [[partition]] with a chosen [[FileSystem file system]]. All subsequent software installations, file edits and additions are saved in this file system. The directory structure is stored as viewed in a [[FileWindow file window]] or listed by a [[TerminalEmulater terminal emulator]].
Deletions:
Full installation involves extracting the linux directory structure from Puppy linux's base [[SquashFS Sfs file]] to a drive [[partition]] with a chosen [[FileSystem file system]]. All subsequent software installations, file edits and additions are saved in this file system. The dictionary structure is stored as viewed in a [[FileWindow file window]] or listed by a [[TerminalEmulater terminal emulator]].


Revision [16981]

Edited on 2011-07-20 13:57:33 by darkcity [basesfs]
Additions:
|=|Speed increased by copy to RAM ||Yes (if sufficient RAM)||No||
|=|Slower on low RAM computer||Possibly||No||
Deletions:
|=|Base file copied to RAM (increases speed)||Yes (if sufficient RAM)||No||
|=|May be slower if computer doesn't have much RAM||Yes||No||


Revision [16980]

Edited on 2011-07-20 13:55:16 by darkcity [basesfs]
Additions:
====Frugal or Full Installation====
This page explains the differences between [[InstallationFrugal Frugal]] and [[InstallationFullHDD Full]] installation.
==Full Installation==
Full installation involves extracting the linux directory structure from Puppy linux's base [[SquashFS Sfs file]] to a drive [[partition]] with a chosen [[FileSystem file system]]. All subsequent software installations, file edits and additions are saved in this file system. The dictionary structure is stored as viewed in a [[FileWindow file window]] or listed by a [[TerminalEmulater terminal emulator]].
==Frugal Installation==
A frugal installation involves using compressed file/s directly. These files are,
When first run:
~- the Puppy Linux base [[SquashFS Sfs file]] containing Linux file system and directory structure (read only)
Additional files:
~- the Puppy [[SaveFile 'save file']] containing additional software and files and modifications (read/write)
~- additional software [[SquashFS Sfs files]] (read only)
Upon start-up these file-systems are super-imposed upon each other so that they appear merged. Additional user files that are written to the written to the Puppy Save File, if within the Linux directory structure. The dictionary structure as viewed in a [[FileWindow file window]] or listed by a [[TerminalEmulater terminal emulator]] is actually contented within these compressed files.
==Comparsion==
|=||=|Frugal|=|Full|=|
|=|Drive partition required||No||Yes||
|=|Installation directory || Almost any directory || Requires a drive [[partition]] ||
|=|Installation file system || FAT, NTFS, Linux Type || Linux Type ||
|=|Core file protection || Read only || Writable ||
|=|Base file copied to RAM (increases speed)||Yes (if sufficient RAM)||No||
|=|May be slower if computer doesn't have much RAM||Yes||No||
Deletions:
====Complete Installation Guide====
1) [[http://puppylinux.com/ Learn more about Puppy]]
2) Acquire the container file (either ISO or ZIP) of a [[http://puppylinuxnews.org/releases/ recent Puppy release]]
3) Choose how to use Puppy with your machine with MinimumSystemRequirements:
<<Using Puppy from a **[[InstallationFrugal flash memory drive]]**
Using Puppy from a **[[InstallationFullHDD hard disk drive]]**
Using Puppy from an **[[LiveDVD optical disc drive]]**
Using Puppy from a **[[http://puppylinux.org/wikka/PXELINUX network server drive]]**<<
===Appendix 1 - The container file===
Puppy essentially consists of three compressed files:
- //vmlinuz//
- //initrd.gz//
- //*.sfs// (where the nature of * is determined by the Puppy version)
N.B. Some Puppy versions make use of an additional file: //z*.sfs//
These files are usually distributed in a container file in either ISO or ZIP format. It is this one file that one has to acquire so as to be able to make use of Puppy.
===Appendix 2 - Co-existing with another operating system===
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 [[http://murga-linux.com/puppy/viewtopic.php?p=483349#483349 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) (see Appendix 3)
One can place a frugal install within a pre-existing Windows installation. The save file, although itself is a Linux file-system, may reside on a FAT or NTFS 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.
===Appendix 3 - The start-up process===
Upon starting, the computer needs to select one of its partitions from which to load an operating system. This requires specific boot code to be located at a special location ([[http://www.pcguide.com/ref/hdd/file/structMBR-c.html Master Boot Record]]) on the boot drive. This program eventually transfers control to the Linux boot-loader system file, e.g. //ldlinux.sys// or //grldr//.
So, if the existing operating system is to be kept, one has to choose which operating system is to be the primary one to initiate the boot process:
- either, the //existing// operating system (e.g. Windows)
- or, the //new// operating system (i.e. Puppy)
If Windows is chosen it will need to be modified so that it presents a start-up menu that includes Puppy as one of the available options. These changes have to be made from inside Windows and not from within Puppy. There is an on-line [[http://www.icpug.org.uk/national/linnwin/step00-linnwin.htm tutorial]] called the ""Lin'N'Win"" Project, that will achieve this.
Is Puppy to be used to boot-up the computer? This will involve installing ""GRUBforDOS"" from within Puppy, which will make Windows available as an option from the GRUB boot menu. However, this will only work if Puppy has been installed into its own partition. And the partition must be formatted using a Linux-compatible file system such as EXT4.
The Puppy Universal Installer (P.U.I.) does not install GRUB to a F.A.T. or N.T.F.S. partition because then it assumes that the partition contains Windows (error message "This partition is not Linux"). Instead, the boot-loader may be installed to the M.B.R.. To return to a Windows-only setup in the future simply run the //fixmbr// command.
===Appendix 4 - Using an appropriate file-system===
When Puppy is to be installed to its own partition it may be formatted with the file-system of choice.
EXT4 is the recommended file-system.
F.A.T. formatting would enable an external drive, e.g. U.S.B. flash memory drive, for file sharing with the Microsoft Windows operating system. It is not suitable for installing Puppy Linux onto since such a file-system does not permit the use of symbolic links. Also it does not support files with sizes greater than 4GB.
N.T.F.S. formatting permits the use of symbolic links and file sizes greater than 4GB. However, there are problems with its usage and so it is not recommended.
The formatting can be performed on an unmounted partition using a LiveDVD or [[installationfrugal LiveUSB]] and going to:
//Menu > System > GParted > Partition > Format to//
===Appendix 5 - Frugal and Full Installations===
When one performs a full installation, all of the data from the core Puppy files are extracted (decompressed) and deposited as a Linux file-system onto one's chosen partition. Therefore, a full installation involves __one file-system__. Any subsequent software application installations, or file edits, are appended to this file-system so that the total number of files and folders gradually increases with time.
A frugal installation involves __two distinct file-systems__:
- the Linux file-system, consisting of a compressed, read-only single file
- the "save file" or "pupsave file" consisting of a decompressed, read/write single file
Upon start-up these two file-systems are super-imposed upon each other so that they appear merged. One has, in effect, a full installation whilst Puppy is running, but all that one actually sees on the physical partition are those two files. Any additional user files that are written to the operating system are written to the save file.
The main advantages of a frugal installation is that one always boot with pristine copies of the core Puppy files. If the install gets corrupted it is just a matter of restoring the single save file from a backup copy.
The save file is of a fixed size but it may be increased if more space is required. However it is simpler to just store or move data outside of the save file, which is recommended. For example these software packages are installed outside the save file: [[seamonkey]], [[libreoffice]]
Frugal installations can be made almost anywhere. It may even be placed inside a full installation of Puppy or another Linux distribution. Or one may have multiple frugal installations in the same partition. When using older machines it is recommended to compare both frugal and full installations to determine which functions better.
Windows Vista may become corrupted if a user tries to shrink the Windows partition using Linux tools. A safer procedure is to use Vista's own Disk Management tool, then create the new partitions using Linux. If one wants to keep Vista as the primary boot-loader, look at Easy BCD [[http://neosmart.net/wiki/display/EBCD/EasyBCD+Documentation+Home;jsessionid=4CDEDEBD199D7577A170EDA271A0B04A
here]].
A frugal installation may be performed on a Windows FAT or NTFS partition without requiring to re-partition it; operates faster in high-R.A.M. computers; and is easier to upgrade. However, if one has fast, newer disks and plenty of R.A.M., frugal loses its speed advantage. On a P3-1GHz machine with 1GB of RAM and UDMA5 hard disks, there is no material performance difference between a frugal install and a full H.D.D install, provided the full install is on a reiserfs partition. On a P3-800 laptop with only a UDMA2 hard disk, there is a great deal of difference. If you have enough RAM to hold Puppy, e.g. 256MB, then the frugal install is the only way to go.
To be able to dual-boot Puppy alongside Windows without re-partitioning or re-formatting: perform a [[InstallationFrugal frugal Puppy installation]].
For a full installation the conventional Linux file system is directly placed onto the partition. A full installation runs faster on low-RAM computers.
On a full hard disk install, the //vmlinuz// file is usually at /boot, and executables are located at /usr/bin. On a frugal install //vmlinuz// is outside of pup_save.2fs somewhere on the "real" file system. executable files within frugal installations are also are /usr/bin, but /usr/bin itself is not directly on the disk but rather is at /initrd/pup_rw which in reality is pup_save.2fs on the disk's "real" file-system, "union'ed" into the overall Linux / directory tree in pup_xxx.sfs.
Another thing frugal installations do is copy the pup_xxx.sfs file into R.A.M. if there is a sufficient amount, causing applications to start slightly faster. If the computer does not have sufficient R.A.M., it will instead mount the pup_xxx.sfs file from the HDD.
In the case that a frugal installation's save file is on a flash memory drive, Puppy stores its file changes within R.A.M., and only copies them to the save file on the drive periodically (or when one clicks the "save" icon or shut down). This is to cut down on writes to the drive to extend it's life. This behavior does not happen on non-flash media (if it does you probably forgot to set the pmedia=satahd parameter when using a SATA drive).
Puppy can boot from a non-primary partition. Or you can have the PUI write GRUB's stage1 to a floppy boot disk. Or you can do the frugal installation manually and use a [[http://www.murga-linux.com/puppy/viewtopic.php?t=16950 boot CD]] to launch it. In that case, one could even put Puppy in a logical FAT partition which would be shared with Windows.


Revision [16979]

The oldest known version of this page was created on 2011-07-20 12:48:30 by darkcity [basesfs]
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki