Puppy linux �������� ��������

Puppy linux �������� ��������

Puppy Linux is a unique family of Linux distributions meant for the home-user computers. It was originally created by Barry Kauler in 2003.

Puppy Linux advantage

1. Ready to use → all tools for common daily computing usage already included.
2. Ease of use → grandpa-friendly certified ™
3. Relatively small size → 300 MB or less.
4. Fast and versatile.
5. Customisable within minutes → remasters.
6. Different flavours → optimised to support older computers, newer computers.
7. Variety → hundreds of derivatives (“puplets”), one of which will surely meet your needs.

If one of these things interest you, read on.

Yes, but what does it look and feel like?

First thing first

Puppy Linux is not a single Linux distribution like Debian. Puppy Linux is also not a Linux distribution with multiple flavours, like Ubuntu (with its variants of Ubuntu, Kubuntu, Xubuntu, etc) though it also comes in flavours.

Puppy Linux is a collection of multiple Linux distributions, built on the same shared principles, built using the same set of tools, built on top of a unique set of puppy specific applications and configurations and generally speaking provide consistent behaviours and features, no matter which flavours you choose.

There are generally three broad categories of Puppy Linux distributions:

official Puppy Linux distributions → maintained by Puppy Linux team, usually targeted for general purpose, and generally built using Puppy Linux system builder (called Woof-CE).

woof-built Puppy Linux distributions → developed to suit specific needs and appearances, also targeted for general purpose, and built using Puppy Linux system builder (called Woof-CE) with some additional or modified packages.

unofficial derivatives (“puplets”) → are usually remasters (or remasters of remasters), made and maintained by Puppy Linux enthusiasts, usually targeted for specific purposes.

Why not try it? Download now! (Official distributions)

Get the ISO, burn it to a CD/DVD using your favorite CD/DVD burner, or flash it using dd (Windows version) to your USB flash drive, or visit our download page for more comprehensive information.

Compatibility *	Architecture	Latest Version	Download link
Ubuntu Focal 64	x86_64 64-bit	FossaPup64 9.5	Main — Mirror — Checksum
Raspbian Buster	armhf 32-bit	Raspup 8.2.1	Main — Mirror — Checksum
Ubuntu Bionic	x86 32-bit	BionicPup32 8.0	Main — Mirror — Checksum
Ubuntu Bionic 64	x86_64 64-bit	BionicPup64 8.0	Main — Mirror — Checksum
Ubuntu Xenial	x86 32-bit	XenialPup 7.5	Main — Mirror — Checksum
Ubuntu Xenial 64	x86_64 64-bit	XenialPup64 7.5	Main — Mirror — Checksum
Slackware 14.2	x86 32-bit	Slacko Puppy 7.0	Main — Mirror — Checksum
Slackware64 14.2	x86_64 64-bit	Slacko64 Puppy 7.0	Main — Mirror — Checksum
Slackware 14.1	x86 32-bit	Slacko Puppy 6.3.2	Main — Mirror — Checksum
Slackware64 14.1	x86_64 64-bit	Slacko64 Puppy 6.3.2	Main — Mirror — Checksum
Ubuntu Trusty	x86 32-bit	Tahrpup 6.0.5	Main — Mirror — Checksum
Ubuntu Trusty 64	x86_64 64-bit	Tahrpup64 6.0.5	Main — Mirror — Checksum

* Compatibility: A Puppylinux distribution can also be built and assembled using packages and components from another Linux distribution called in Puppy the “binary compatible” distribution. The choice of a binary compatible distribution determines the availability of additional packages, among other things.

Questions?

It has been said that the best experience of Puppy Linux is not from the software itself, but from the community that gathers around it. Whatever you have in mind — praises, curses, questions, suggestions, or just plain chit-chat, we welcome you to join us at Puppy Linux Discussion Forum or just check the discussions for the latest puppylinux woof builds.

Источник

Puppy linux �������� ��������

Puppy Linux as of November 2015 supports both x86 and x86_64 CPU architectures. Generally, these are manufactured by Intel and AMD and some smaller companies such as VIA and earlier on Cyrix.

Puppy will not (likely) run on an old 486, or even an old PI. A PII will struggle with a modern Puppy. Some later PIII and Athlon machines should cope.

If you are finding it tough deciding which Puppy to download for your machine read on.

Technically speaking, any Intel 8086 processor is x86! This includes the old 286, 386 and 486 series however it wasn’t until the 386 that “32 bit” registers came into effect.

We often refer to “32 bit” or “64 bit”. Generally when we refer to “x86” we are talking about “32 bit”. A 32 bit operating system will run on an x86 or an x86_64 processor but a 64 bit operating system will not run on an x86 processor. If you are unsure what type of processor you have a 32 bit Puppy is a safe bet and once running there are various ways to determine the architecture of your processor.

Here is a simple test we have devised if you are running Linux:

grep -o -w -q ‘lm’ /proc/cpuinfo && echo «64 bit» || echo «32 bit»

That test will return 64 bit if your processor is capable or 32 bit otherwise.

To PAE or not to PAE ; That is the question!

PAE (Physical Address Extension) is a patch to the Linux Kernel. Normally, a 32 bit operating system is limited to “seeing” 4 GB of RAM. When a kernel is configured there is an option to enable higher memory. This switches on the PAE patch and subsequently the operating system is capable of “seeing” up to 64 GB of RAM, however, any one process is still restricted to using up to 4 GB of RAM.

Some 32 bit processors have not got PAE capability set in their instructions. It is a limited few but a notable one is the Intel Centrino with 400MHz FSB. Some quite old processors do not support PAE too.

A similar check to the 64 bit test above can be performed to determine your processors PAE capabily:

grep -o -w -q ‘pae’ /proc/cpuinfo && echo «PAE Supported» || echo «PAE Unsupported»

This will return PAE Supported if your processor supports PAE; PAE Unsupported if your processor does not.

If you have less than 4GB of RAM there isn’t much point in using a PAE enabled operating system, however in most cases it will work fine anyway.

i386, i486, i586 and i686

Briefly, these architectures correspond with the following CPUs:

i386 – Intel 386 and AMD 386 CPUs

i486 – Intel 486 and AMD 486

i586 – The First Intel Pentiums MMX, AMD-K5

i686 – Pentium Pro, AMD-K6

Since around 2009 Puppy’s kernels have been compiled with Pentium Pro support making the operating system “i686”. Most software is compiled i686 as well.

x86_64

x86_64 is just x86 with 64 bit addressing capability. This gives the operating system access to 64 GB of RAM natively.

AMD were the first to come up with a 64 bit processor with their “Opteron” line in 2003. In 2004 Intel released its first 64 bit processor “Nocona”.

AMD Opteron, Athlon X2 and later are 64 bit processors

Intel’s Pentium 4 Prescott gained 64 bit support in 2004. Pentium D and later are 64 bit processors with the exception of some Atom processors (“Diamondville” and some others).

x86_64, ia64, amd64 ; I’ve seen all these, what’s up with that?

Firstly, x86_64 and _amd64 are one and the same. Maybe it’s because AMD got there first that “amd64” caught on.

ia64 is a completely different instruction set for Intel Itanium processors which Puppy does not support.

arm processors are likely to be found in embedded systems such as routers, TVs, appliances and mobile phones.

There are many different arm architectures and not all are compatible; armel, armhf, armv6l, armv7l, even 64 bit aarch64 or arm64.

Puppy now has support for armhf on the Raspberry Pi family of computers, from pi zero and the original pi 1 to the latest pi 4. See the Old Puppy Forum for more details.

BIOS and UEFI

BIOS (Basic Input/Output System) based computers have been around for a long time. Most people familiar with computers have been into the BIOS setup at some point to change a setting such as boot device order or the system time.

UEFI (Unified Extensible Firmware Interface) is a standard and is (however much a pain it is) necessary to help address the limitation of BIOS/MBR systems limit of support for hard disks above 2 TB. MBR can not work on large disks. It is fairly inexpensive these days to replace your current harddisk with a 4 TB or even 6 TB.

My MAC has EFI; is that the same as UEFI?

UEFI and Puppy

At the time of writing, Puppy does not support UEFI. However, most Windows™ computers come with “legacy Bios” which you can enter to enable booting a Puppy boot media (optical or USB). Secure Boot must be turned off and you must make sure that the computer has fully shut down and not in a hibernated state.

Puppy does intend to support UEFI in the near future.

Conclusion

Hopefully the above information has helped you out with your decision. If not, please consider this: The only stupid question is the one that isn’t asked! Feel free to “ask away” on the Puppy Linux Discussion Forum.

Источник

Puppy linux �������� ��������

See: Official Pup build recipes at Woof-CE on GITHUB

Name	Description	More Info
FossaPup64	UbuntuLTS20.04 compatible Official Pup (64bit)	Fossapup64 Forum Page
BionicPup32	UbuntuLTS18.04 compatible Official Pup (32bit)	BionicPup32 Forum Page
BionicPup64	UbuntuLTS18.04 compatible Official Pup (64bit)	Bionicpup64 Forum Page
XenialPup	UbuntuLTS16.04 compatible Official Pup (32bit)	Xenialpup Forum Page
XenialPup64	UbuntuLTS16.04 compatible Official Pup (64bit)	Xenialpup64 Forum Page
Tahrpup	UbuntuLTS14.04 compatible Official Pup (32bit)	Tahrpup Forum Page
Tahrpup64	UbuntuLTS14.04 compatible Official Pup (64bit)	Tahrpup64 Forum Page
ScPup	SlackwareCurrent compatible Pup (32 & 64bit)	ScPup Forum Page
Slacko14.2	Slackware14.2 compatible Pup (32 & 64bit)	Slacko14.2 Forum Page
Slacko14.1	Slackware14.1 compatible Official Pup (32 & 64bit)	Slacko Website
LxPupSc	SlackwareCurrent Pup with LXDE (32 & 64bit)	LxPupSc Forum Page
FocalPup32	UbuntuLTS20.04+Debian Pup (UPupFF+D) (32 bit)	FocalPup32 Forum Page
DPupStretch	DebianStretch compatible Pup (32bit)	DPupStretch Forum Page

Download Sites

All the “official” Puppies since version 2 are hosted at Ibiblio.

Ibiblio also hosts the puppy specific packages (pet) used to build puppies as well as squashfs files (sfs) with kernels, kernel sources, large applications and application frameworks.

The Ibiblio puppylinux directory is mirrored by several sites world-wide.

The NLUUG and the UoC mirrors in Europe and the AARNET and the Internode mirrors in Australia are known to update regularly and are usually faster than Ibiblio.

Mirrors may take up to a day to incorporate changes in Ibiblio.

Источник

Puppy linux �������� ��������

The fact is that you do not need to install Puppy Linux at all! You can simply download and burn it to an optical disc (CD, DVD, CD±RW, DVD±RW) or dd it to an USB drive and boot it live.

Burning an Optical disc or preparing a USB Drive

Optical

In any Linux, once you have downloaded the ISO image and verified its authenticity by checking its md5sum you can burn it to a DVD or a CD using any Linux optical burning tool. Just make sure you burn it as an image and not data otherwise it will not be bootable.

In Windows we recommend Imageburn (direct link to download) to burn the image to a CD or DVD.

All Linux versions come with a tool name dd. Our ISO images since 2013 come as iso hybrid images so they can be transferred directly to the USB drive using dd. Don’t attempt this with older puppy versions unless you know what you are doing. Here is a simple tutorial on using dd to make a bootable USB drive. Be very careful with your target drive name!

There is a Windows version of dd available on this site.

There is also a graphical tool for Windows called Win32 Disk Imager. A download is available from this page.

Booting

Depending on whether you have optical or USB media you may have to go into your computer’s BIOS Setup program to adjust the boot order of devices. You want to give your optical or USB ports priority over the harddrive.

Once you have your boot media and computer set up just insert the boot media and switch on your computer. You will see a couple of text screens go past and hopefully you will boot to a shiny new desktop with a quick setup screen followed by a welcome screen.

When you are finished you can decide to save the session or not! Not saving the session does not leave a trace of the operating system as Puppy runs entirely in RAM and as soon as the computer is powered off the RAM is flushed. This is ideal from a security perspective for internet banking or other sensitive financial transactions performed over the internet.

Saving the session can be achieved in a number of ways:

You can save the session to a harddrive or an USB drive in a vfat, ntfs or linux [1] partition. This will save all your settings to what is known as a pupsave [2] file or folder. When you boot off the same media next time the pupsave will be found and all your files and settings will be as you left them.

If you booted off of optical media you can save the session and all settings back to that same optical disc.

So you want to install Puppy

Naturally you can actually install Puppy if you wish. Once you boot Puppy and are happy with what you see it is time to open the Puppy Installer from Setup in the main menu. There are 3 main types of install; frugal, USB and traditional full install.

1. Frugal install (Recommended)

This type of install copies the main puppy files from the boot media (either optical or USB) to your harddrive. Firstly, you are presented with some information about your system and what partitions you have available. If you don’t have a suitable partition then you can use the included graphical partition manager GParted to shrink and move partitions as necessary to created a partition for your installation. Once this is done you are prompted for the location of your boot media files (either an iso image, optical media or just the files themselves) and once confirmed these are copied to a folder in your chosen partition. A bootloader is then installed and once finished you can reboot into your new system.

This will be a pristine system that requires you to save your session at shut down if you want to keep your settings. Once saving the session is complete, a pupsave file or folder is created. On you next boot your files and settings will be exactly as you left them at last shutdown.

2. USB Install (Recommended)

This type of install copies the main puppy files from the boot media (either optical or USB) to your chosen USB drive. Firstly, you should insert the USB drive that you want to use for installation. Again using the graphical partition manager GParted you need to make sure that there is a suitable partition on the USB drive. This can be formatted to fat32 Windows™ style filesystem (good for portability if you want to use the drive as storage to be used between Linux and Windows™) or one of the supported Linux filesystems. (Note: not all Puppies support the f2fs filesystem. The installer is intelligent enough to know this.) Again, you are prompted for the location of your boot media files (either an iso image, optical media or just the files themselves) and once confirmed these are copied to a folder in your chosen USB drive. A bootloader is then installed and once finished you can reboot into your new system. This can be booted on any computer you like! This is also a type of frugal installation.

Again, this will be a pristine system that requires you to save your session at shut down if you want to keep your settings. Once saving the session is complete, a pupsave file or folder is created. On you next boot your files and settings will be exactly as you left them at last shutdown.

3. Full Install

This is a traditonal Linux install to its own dedicated partition. If you don’t have a suitable partition then you can use the included graphical partition manager GParted to shrink and move partitions as necessary to created a partition for your installation. You must use a Linux filesystem. Once this is done you are prompted for the location of your boot media files (either an iso image, optical media or just the files themselves) and once confirmed these are expanded in your chosen partition. A bootloader is then installed and once finished you can reboot into your new system.

Once booted this will act like any other Linux installation.

Using Puppy

Puppy is famous for its ease of use. The desktop layout is traditional with a task bar at the bottom (or top) and icons on the desktop. Anyone coming from Windows™, Mac OSX™ or another Linux such as Ubuntu, Fedora or Arch will have little issue getting used to it. The interface is a typical WIMP style (Windows, Icons, Menus and a Pointing device).

While puppy comes with almost everything you need to write, calculate, enjoy videos and music, create artwork, work with your digital camera, and more there invariably comes a time when you need an an extra piece of software. Extra software comes in the form of pet packages which can be installed through the Puppy Package Manager or by downloading from a trusted source and simply clicking on the package. Puppy also has the capability of installing deb, rpm and tgz/txz packages from Debian family, Red Hat family and Slackware family of Linux operating systems.

The way Puppy is designed, if you use a frugal type install, software can be installed as an sfs (Squash File System) package. This is the preferred method to install very large packages such as LibreOffice. In fact the Puppy development environment, including the GNU Compiler Collection (GCC) and development libraries and headers, is shipped as an sfs; a separate download to the main ISO image. There is a tool call SFS Load which makes installing these packages a one step process. The sfs packages do not work on a full install.

Once you have been using Puppy for a little while you may want to try a remaster (see FAQ). This saves the state of your current installed system (minus some the personal stuff) to a burnable ISO image. This enables you to have your system setup and ready to go if you have several computers or you can share your remaster as a puplet with the community.

However you decide to install (or not) Puppy Linux, we hope you enjoy using it for years to come!

Notes

While we recommend frugal or USB installations the choice is entirely yours.

[1] Some common Linux filesystems that Puppy supports are ext2, ext3, ext4, f2fs. Windows™ filesystems supported are fat16, fat32 and ntfs.

[2] A pupsave file is a file that contains a linux filesystem. It can be stored on any supported partition. It is a fixed size and can be as small as 32MB and as large as 4GB (on fat32) and even larger on other filesystems. The pupsave file can be enlarged later on, but the challenge is to keep your system trim and clean by regularly deleting browser cache, cleaning up any stray files and storing other stuff outside the save file.

A pupsave folder can only be created on a linux filesystem. This allows you to store as much as your partition can hold.

Источник