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 ��������� �������

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 ��������� �������

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 ��������� �������

Woof-CE is a collection of build scripts that will automatically build a Puppy Linux distribution from scratch. It is versatile and very flexible. To build a Puppy, Woof can use puppy-specific, self-compiled packages (pets) and packages from another distribution called the “binary compatible” distribution (e.g. Ubuntu, Slackware) or it can use only self-compiled packages. It supports multiple architectures (x86, x86_64 and arm).

Puppy Linux Woof-CE is the official build system for making a Puppy Linux distribution, going forward. If it is not built from Woof-CE, it is not a Puppy.

The name

Woof-CE stands for Woof Community Edition. The name Woof itself is chosen because … well, what’s more appropriate then a sound of a dog’s bark to indicate a presence of a new distribution, if the distribution’s name itself is Puppy? ☺

Building Puppy from Woof-CE.

There are a few prerequisites to building a woof-CE based Puppy:

a modern Puppy; one built from woof-CE is best.

the devx sfs module must be loaded. It contains some essentials like the git program.

a partition with no less than 10 GB of free space with a Linux filesystem

1. Make a local clone of Woof-CE repository:

git clone https://github.com/puppylinux-woof-CE/woof-CE.git

1. Once downloaded you will have the latest code of woof-CE. Change into the cloned repository directory:

Run the script merge2out and choose the host arch.

This script merges woof-arch, woof-code and woof-distro, to ../woof-out_*.

woof-arch: architecture-dependent (x86, arm) files, mostly binary executables. woof-code: the core of Woof. Mostly scripts. woof-distro: distro-configuration (Debian, Slackware, etc.) files. kernel-kit: puppy-kernel build script and configuration files

Important: the host architecture is distinct from the target architecture. The host is the machine you are running Woof on, the target is the machine in which the Puppy that you build is going to run. Typically, you will build on a x86 machine, and the target may be x86 or arm.

1 arm 2 x86 3 x86_64 Type number of host architecture: 2 …ok, x86

Choose target arch.

Choose the binary compatible distro for your Puppy.

Choose the version of the binary compatible distro.

If you are happy, it’s just a matter of reading the prompts and selecting [Enter] and in a matter of moments you will have a new woof tree set up to build your shiny new Puppy.

Change into your new woof-out* directory.

Now run the following commands in order, waiting for each to complete! (This can take a long time! Especially on first run when all packages need to be downloaded

around 600MB of packages.)

./0setup ./1download ./2createpackages ./3builddistro-Z

If all goes well, you will have a nice new ISO image in the woof-out_x86_x86_slackware_14.1/woof-output* directory.

Note: At the time of writing not all distro choices are tested working. Known working distros are Slackware 14.1 (Slacko), Ubuntu Trusty Tahr (Tahrpup) and Trisquel Belenos (Librepup).

Contributing

Woof-CE is kept on github.com. Everybody is welcome to download and use it to build a Puppy, or even fork it.

But if you want your modifications to be included and used for future puppies, they must be merged back to the original Woof-CE repository. To merge that, you need to send a patch or better yet a pull request to the Woof-CE repository.

The Woof-CE members will then consider your request and merge them if they feel that your changes are beneficial for everyone. If your patch is not accepted, don’t feel bad. Often it is just a little changes you need to apply before resubmitting the request again. Even if the rejection is final, be glad to know the puppy you build with your changes is now unique — no other puppy will work like it because it’s the only one that has your unique changes.

Источник