At a listener's suggestion, we describe three new solutions that try to answer the age-old question, 'Why can Linux distributions not agree on how to install and application?' We describe Snap, AppImage and FlatPak.
Episode 333 Time Stamps 00:00 Going Linux #333 One Installation File - Many Linux Distributions 00:15 Introduction 00:47 New Book: Using Ubuntu MATE and Its Applications 01:42 Why can Linux distributions not agree on how to install and application? 03:59 Snaps: Intro 05:31 FlatPaks: Intro 06:14 AppImages: Intro 07:02 Snap 08:58 AppImage 11:06 FlatPak 11:55 More details and how to create packages 12:07 Which should I use? 13:57 goinglinux.com, [email protected], +1-904-468-7889, @goinglinux, feedback, listen, subscribe 14:54 End 337 episodes available. A new episode about every 15 days averaging 38 mins duration.
Puppy Linux Xenialpup 7.5 Barry Kauler (original) Larry Short, Mick Amadio and Puppy community (current) OS family Working state Current Source model Primarily Initial release 0.1 / 18 June 2003; 14 years ago ( 2003-06-18) 7.5 (XenialPup) / 4 December 2017; 31 days ago ( 2017-12-04) 17.11+9 (possibly version 8.X.X) RC (ArtfulPup) / December 27, 2017; 8 days ago ( 2017-12-27) Marketing target Live CD, Netbooks, older systems and general use Puppy Package Manager Platforms, type Default / + and various others Official website Puppy Linux is an and that focuses on and minimal. The entire system can be run from with current versions generally taking up about 210 MB, allowing the boot medium to be removed after the has started. Applications such as, and are included, along with a choice of lightweight web browsers and a utility for downloading other packages. The distribution was originally developed by Barry Kauler and other members of the community, until Kauler retired in 2013. The tool can build a Puppy Linux distribution from the binary packages of other Linux distributions.
Puppy Linux 7.5 Xenialpup Version Release Date Puppy 0 18 June 2003 Puppy 1 29 March 2005 Puppy 2 1 June 2006 Puppy 3 2 October 2007 Puppy 4 5 May 2008 Puppy 5 15 May 2010 Puppy 6 26 October 2014 Puppy 7 4 December 2017 Puppy 0 is the initial release of Puppy Linux. It has no unionfs, extreme minimal persistence support, and has no package manager or ability to install applications Puppy 1 series will run comfortably on very dated hardware, such as a Pentium computer with at least 32 MB RAM. For newer systems, the USB keydrive version might be better (although if USB device booting is not directly supported in the, the Puppy floppy boot disk can be used to kick-start it). It is possible to run Puppy Linux with /. It is also possible, if the BIOS does not support booting from USB drive, to boot from the CD and keep user state on a USB keydrive; this will be saved on shutdown and read from the USB device on bootup. Puppy 2 uses the Mozilla-based SeaMonkey as its (primarily a and e-mail client).
Puppy 3 features Slackware 12 compatibility. This is accomplished by the inclusion of almost all the dependencies needed for the installation of Slackware packages.
However, Puppy Linux is not a. Puppy 4 is built from scratch using the T2 SDE and no longer features native Slackware 12 compatibility in order to reduce the size and include newer package versions than that found in 3. To compensate for this, an optional 'compatibility collection' of packages was created that restores some of the lost compatibility. Puppy 4.2 features changes to the user interface and backend, upgraded packages, language and character support, new in-house software and optimizations, while still keeping the size under 100 MB. Puppy 5 is based on a project called Woof which is designed to assemble a Puppy Linux distribution from the packages of other Linux distributions. Woof includes some binaries and software derived from, T2 SDE, or repositories.
Puppy 5 came with a stripped down version of the browser to be used for reading help files and a choice of web browsers to be installed, including, Internet Suite, and. Puppy 6 is built from Trusty Tahr packages, has binary compatibility with Ubuntu 14.04 and access to the Ubuntu package repositories. Tahrpup is built from the woof-CE build system, forked from Barry Kauler's Woof late last year after he announced his retirement from Puppy development. It is built from the latest testing branch, incorporates all the latest woof-CE features and is released in PAE and noPAE ISOs, with the option to switch kernels.
Puppy 7 is built from Ubuntu 16.04 Xenial Xerus packages, has binary compatibility with and access to the Ubuntu package repositories. Tahrpup is built from the woof-CE build system, forked from Barry Kauler's Woof.
It is built from the latest testing branch, incorporates all the latest woof-CE features and is released in PAE and noPAE ISOs, with the option to switch kernels. It has a new, a new kernel update for greater hardware compatibility, redesign Puppy Package Manager, some bugfixes and base packages inclusion into the woof structure. Features Puppy Linux is a complete operating system bundled with a collection of applications suited to general use tasks. It can be used as a, a demonstration system that leaves the previous installation unaltered, as an accommodation for a system with a blank or missing hard drive, or for using modern software on legacy computers. Puppy's compact size allows it to boot from any media that the computer can support. Icofx keygen 2.3.1. It can function as a for or other mediums, a, an internal, an, a or LS-120/240, through, and through a floppy that chainloads the data from other storage media. It has also been ported to ARM and can run on a single board computer such as the.
Puppy Linux features built-in tools which can be used to create bootable USB drives, create new Puppy CDs, or remaster a new live CD with different packages. It also uses a sophisticated write-caching system with the purpose of extending the life of live USB flash drives. Puppy Linux includes the ability to use a normal persistent updating environment on a write-once multisession CD/DVD that does not require a rewritable disc; this is a unique feature that sets it apart from other Linux distributions. While other distributions offer versions of their operating systems, none offer a similar feature. It works particularly well with DVDs due in part to the larger space available than a CD.
– Puppy's bootloader does not mount hard drives or connect to the network automatically. This ensures that a bug or even unknowingly incompatible software won't corrupt the contents of such devices. Puppy Linux offers a session save on shutdown.
Since Puppy Linux fundamentally runs in RAM, any files and configurations made or changed in a session would disappear otherwise. This feature enables the user to either save the contents to a writable storage medium, or write the file system to the same CD containing Puppy, if 'multisession' was used to create the booted CD and if the disc drive supports burning.
This applies to CD-Rs as well as CD-RWs and DVDs. It is also possible to save all files to an external hard drive, USB stick, or even a floppy disk instead of the root file system. Puppy can also be installed to a hard disk. User interface. Desktop with one of multiple integrated themes with XMMS a multimedia player, mtPaint a painting program for creating pixel art and manipulating digital photos and mplayer running, plus an opened text file under Puppy Linux 2.15 CE Viz (with default WM: IceWM) The default in most Puppy releases is. Packages of the desktop, and are also available via Puppy's PetGet package (application) management system (see below). Some derivative distributions, called puplets, come with default window managers other than JWM.
When the operating system boots, everything in the Puppy package uncompresses into a RAM area, the '. The PC needs to have at least 128 MB of RAM (with no more than 8 MB shared video) for all of Puppy to load into the ramdisk. However, it is possible for it to run on a PC with only about 48 MB of RAM because part of the system can be kept on the hard drive, or less effectively, left on the CD. Puppy is fairly full-featured for a system that runs entirely in a ramdisk, when booted as Live system or from a 'frugal' installation. However, Puppy also supports the 'full' installation mode, which enables Puppy to run from a hard drive partition, without a ramdisk. Clipse albums. Applications were chosen that met various constraints, size in particular. Because one of the aims of the distribution is to be extremely easy to set up, there are many that guide the user through a wide variety of common tasks.
Package and distribution management. Puppy Package Manager showing Slackware 14 indic fonts package Puppy Linux's package manager, Puppy Package Manager, installs packages in PET (Puppy Enhanced Tarball) format by default but it also accepts packages from other distros (such as, and packages) or by using third-party tools to convert packages from other distros to PET packages. Puppy Package Manager can also trim the software bloat of a package to reduce the disk space used.
Building the distribution On earlier releases of Puppy Linux, Puppy Unleashed was used to create Puppy. It consists of more than 500 packages that are put together according to the user's needs.
However, on later versions starting with Puppy Linux version 5.0, it was replaced by Woof. It is an advanced tool for creating Puppy installations. It requires an Internet connection and some knowledge of Linux to use. It is able to download the binary source packages from another and process them into Puppy Linux packages by just defining the name of that Linux distro.
It is equipped with a simpler version control named Bones on earlier releases but on later versions of woof, Fossil version control is used. Puppy also comes with a remastering tool that takes a 'snapshot' of the current system and lets the user create a live CD from it, and an additional remastering tool that is able to remove installed components. Puppy Linux uses the T2 SDE build scripts to build the base binary packages. Official variants Because of the relative ease with which the Woof tool and the remaster tool can be used to build variants of Puppy Linux, there are many variants available. Variants of Puppy Linux are known as puplets. After Barry Kauler reduced his involvement with the Puppy Project, he designed two new distributions within the same Puppy Linux family, Quirky and Wary.
Quirky - An embedded, less-stable distro with all files contained in an built into the kernel. It has simple module loading management but fewer drivers are included. It used for experimental purposes Racy - A variant of puppy optimized for newer PCs. Wary - A Puppy variant targeted at users with old hardware. It uses an older Linux kernel, which has long-term support and the newest applications. Easy - A puppy variant which init script is completely rewritten and it uses originally developed application containers aside the conventional package management.
Reception reviewer Rober Storey concluded about Puppy 5.2.5 in April 2011: 'A lot of people like Puppy — it's in the top 10 of the DistroWatch page-hit ranking. I enjoy Puppy too, and it's what I run exclusively on my netbook. Maybe the only thing wrong with Puppy is that users' expectations tend to exceed the developer's intentions.' In a detailed review of Puppy Linux in May 2011 Howard Fosdick of OS News addressed the root user issue, 'In theory this could be a problem — but in practice it presents no downside. I've never heard of a single Puppy user suffering a problem due to this.'
Fosdick concluded 'I like Puppy because it's the lightest Linux distro I've found that is still suitable for end users. Install it on an old P-III or P-IV computer and your family or friends will use it just as effectively for common tasks as any expensive new machine.' In December 2011 Jesse Smith, writing in DistroWatch, reviewed Puppy 5.3.0 Slacko Puppy.
He praised its simplicity, flexibility and clear explanations, while noting the limitations of running as root. He concluded 'I would also like to see an option added during the boot process which would give the user the choice of running in unprivileged mode as opposed to running as root. Always being the administrator has its advantages for convenience, but it means that the user is always one careless click away from deleting their files and one exploit away from a compromised operating system. As a live CD it's hard to beat Puppy Linux for both performance and functional software. It has minimal hardware requirements and is very flexible.
It's a great distro as long as you don't push it too far out of its niche.' In December 2011 Howard Fosdick reviewed the versions of Puppy Linux then available.
He concluded, 'Puppy's diversity and flexibility make it a great community-driven system for computer enthusiasts, hobbyists, and tinkerers. They also make for a somewhat disorderly world. You might have to read a bit to figure out which Puppy release or Puplet is for you. Puppy's online documentation is extensive but can be confusing. It's not always clear which docs pertain to which releases.
Most users rely on the active, friendly forum for support.' He also noted 'Those of us who enjoy computers sometimes forget that many view them with disdain.
What's wrong with it now? Why do I have to buy a new one every four years?
Why on earth do they change the interface in every release? Can't it just work? Puppy is a great solution for these folks. It's up-to-date, free, and easy to use.
And now, it supports free applications from the Ubuntu, Slackware, or Puppy repositories. Now that's user-friendly.' Retrieved 2012-05-06. Retrieved 2017-02-20. Retrieved 4 January 2018.
Fosdick, Howard (October 8, 2007). Archived from on January 16, 2013.
Retrieved August 19, 2016. Kauler, Barry (2008). Archived from on December 11, 2015. Retrieved July 13, 2016. Kauler, Barry. Retrieved 2013-08-04. DistroWatch Weekly.
November 14, 2005. Retrieved 2016-08-19. Retrieved 26 August 2016.
Retrieved 2016-08-16. Kauler, Barry. Archived from on November 8, 2007. Kauler, Barry. Kauler, Barry. ^ Kauler, Barry. Kauler, Barry.
Archived from on 3 January 2010. Retrieved 6 April 2011. Kauler, Barry (9 February 2009). Puppy developer pages. Retrieved 2009-02-13. Puppy Linux (May 2016). Retrieved May 14, 2016.
Puppy Linux (May 2016). Retrieved May 14, 2016.
Kauler, Barry (May 2013). Retrieved May 14, 2016. Kauler, Barry. Retrieved 2017-12-10. May 29, 2013. Retrieved August 12, 2013. Archived from on October 13, 2008.
Retrieved August 19, 2016. Puppy Linux Wiki. Retrieved August 19, 2016. Kauler, Barry (September 9, 2006). From the original on August 19, 2016.
Retrieved August 19, 2016. Archived from on 2010-08-14. Eckstein, Keith (July 2010). Archived from on July 11, 2010. Retrieved 9 July 2010.
Archived from on 2008-06-21. Retrieved 2008-08-02. Kauler, Barry (October 2009). Retrieved 23 January 2011. Barry Kauler (March 2010). Barry Kauler (March 2010). Retrieved 2012-04-12.
Kauler, Barry. Retrieved 26 August 2016.
Kauler, Barry. Retrieved 21 March 2017. Storey, Robert (April 2011). Retrieved 23 April 2011. Fosdick, Howard (May 2011). Retrieved 17 May 2011. Smith, Jesse (12 December 2011).
Puppy Linux Package Manager
Retrieved 12 December 2011. Fosdick, Howard (17 December 2011). Retrieved 17 December 2011. External links Wikimedia Commons has media related to. Wikibooks has more on the topic of:.
Puppy Linux Discussion Forum:: View topic - How to install.deb.rpm.tar.gz.tar etc? Puppy Linux Discussion Forum Puppy HOME page: 'THE' alternative forum: The time now is Sat 06 Jan 2018, 11:06 All times are UTC - 4 » » Moderators:,:: Page 1 of 2 21 Posts Goto page: 1, Author Message figetelfibets Joined: 10 May 2008 Posts: 18 Posted: Sat 10 May 2008, 19:34 Post subject: How to install.deb.rpm.tar.gz.tar etc?
I was wondering about some post that I read today that would have me believe that you can install apps besides the common.pup like.deb.rpm.tar.gz.tar etc using some software tool like Alien, unrpmfull or undeb. I would like to ask if this is true and what works best? I also would like to try to get Wine and K3b working. WhoDo Joined: 11 Jul 2006 Posts: 4440 Location: Lake Macquarie NSW Australia Posted: Sat 10 May 2008, 19:41 Post subject: Re: Installers? Subject description:.deb.rpm.tar.gz.tar etc figetelfibets wrote: I was wondering about some post that I read today that would have me believe that you ca install apps besides the common.pup like.deb.rpm.tar.gz.tar etc using some software tool like Alien, unrpmfull or undeb. I would like to ask if this is true and what works best?
I also would like to try to get Wine and K3b working. Yes it is true. What works best? That depends. On the app, your puppy version, dependencies involved, etc. Alien isn't particularly useful in puppy, but unrpmfull (contains undeb) and undeb are useful for installing binaries in puppy. Wine is already available as a dotpet package for most puppy versions.
K3b will only work if you first use the KDE.sfs add-on package. That's a lot of bloat for one program. You might find that Pburn is just as good and a whole lot smaller and easier on your storage space and ram. Hope that helps. Actions speak louder than words.
And they usually work when words don't! SIP:[email protected]; [email protected] Lobster Official Crustacean Joined: 04 May 2005 Posts: 15235 Location: Paradox Realm Posted: Sat 10 May 2008, 20:58 Post subject: Dingo Wine figetelfibets Joined: 10 May 2008 Posts: 18 Posted: Sat 10 May 2008, 21:31 Post subject: the best location to download is because I noticed that the link is dead which is the one on that site.
I got dependencies. File /usr/lib/wine/wldap32.dll.so has these missing library files: libldapr-2.3.so.0 File /usr/lib/wine/gphoto2.ds.so has these missing library files: libgphoto2.so.2 libgphoto2port.so.0 File /usr/lib/wine/wineesd.drv.so has these missing library files: libesd.so.0 I used to use a Distro that could fix that itself so I don't know where to get the files or anything. I already have KDE fore the added tools but it is KDELite. I would like to know how to use unrpmfull and undeb. Thanks in advanced and thanks fore WinePup. O and I guess I cant have click able links yet. (Thanks fixed) Last edited by figetelfibets on Sun 11 May 2008, 00:19; edited 1 time in total Bruce B Joined: 18 May 2005 Posts: 11488 Location: The Peoples Republic of California Posted: Sat 10 May 2008, 23:37 Post subject: This should work, as a direct link, so don't click it if you don't want to start a download.
WhoDo Joined: 11 Jul 2006 Posts: 4440 Location: Lake Macquarie NSW Australia Posted: Sat 10 May 2008, 23:48 Post subject: figetelfibets wrote: the best location to download is /urlO and I guess I cant have click able links yet. All you need to do is get the tag right. You have a '/' in front of the leading url tag which is a close url tag. It should go 'url url goes here /url' Actions speak louder than words. And they usually work when words don't!
SIP:[email protected]; [email protected] figetelfibets Joined: 10 May 2008 Posts: 18 Posted: Sun 11 May 2008, 00:21 Post subject: Thanks see above on links. I got the right one and was only noting that its better to look in then use the link on that old site but yes works fore now. Muggins Joined: 20 Jan 2006 Posts: 6734 Location: hobart Posted: Sun 11 May 2008, 01:32 Post subject: Quote: I would like to know how to use unrpmfull and undeb. Ttuxxx has an unrpm.pet. Both unrpm & undeb extract their respective archives from the commandline. If you want the linux RollsRoyce archiver, which will handle both rpm & deb, you might consider installing Pkag's peazip.pet. Figetelfibets Joined: 10 May 2008 Posts: 18 Posted: Sun 11 May 2008, 01:48 Post subject: Thanks I will give it a try.
Now about the dependence thing? Muggins Joined: 20 Jan 2006 Posts: 6734 Location: hobart Posted: Sun 11 May 2008, 02:01 Post subject: Quote: Now about the dependence thing? Figetelfibets, did you search the forum for libldapr-2.3.so.0? Figetelfibets Joined: 10 May 2008 Posts: 18 Posted: Tue 13 May 2008, 18:12 Post subject: I found the thing now I would like to know do I save the needed lib to the perspective folder mentioned in the list of dependencies something like /usr/lib/wine?
I haven't messed with much yet so be kind if I sound a bit new/dumb. Vanchutr Joined: 05 Aug 2006 Posts: 438 Posted: Tue 13 May 2008, 22:41 Post subject: k3b and Puppy 4.00 k3b works good in Puppy 4.00 1. Install cdrdao 2.
Install k3b version 1.0.4 3. Supply some libs (In rxvt use command k3b to check lib) 4. Now we can use k3b in Puppy 4.00 Please give your comments. Thanks muggins Joined: 20 Jan 2006 Posts: 6734 Location: hobart Posted: Tue 13 May 2008, 23:25 Post subject: Quote: I haven't messed with much yet so be kind if I sound a bit new/dumb No worries! After a few weeks messing with puppy you'll be up to speed & a bona-fide puppy pro. Actually the file you really need to download is. The other file is a symlink to this real library file.
Save this file to /usr/lib directory. Then you just need to create a symlink. Open a console terminal, ( Menu-Utility-Rxvt), and enter the following: Code: ln -s /usr/lib/libldapr-2.3.so.0.2.15 /usr/lib/libldapr-2.3.so.0 Then, while you've still got the terminal open, type wine, and if any errors are generated let us know.
Figetelfibets Joined: 10 May 2008 Posts: 18 Posted: Thu 15 May 2008, 17:01 Post subject: bash: syntax error near unexpected token `in'??I did what you asked?? I know I probably typed something incorrectly. I will probably get it right.
Puppy Linux Installation and Usage The fact is that you do not need to install Puppy Linux at all! You can simply 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 to burn the image to a CD or DVD.
USB 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 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. There is also a graphical tool for Windows called Win32 Disk Imager.
A download is available from. 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 partition.
This will save all your settings to what is known as a pupsave 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. 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. 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. 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 ). 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. Some common Linux filesystems that Puppy supports are ext2, ext3, ext4, f2fs. Windows™ filesystems supported are fat16, fat32 and ntfs. 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.
Debianization is a coined term for Puppy more Debian like, or fully installing & enabling Debian versions of DPKG and apt-get on puppy. I don't have any specific reason for doing this, other than research and trying to build puppy up to a Debian distro. I have encountered many problems along the way, so if you find one that is not addressed in here, please visit and post about it. The actual success of 'debianizing' puppy may vary, and I only cover the basic procedure. DO NOT try this on a puppy save that you want to keep, or if you do actually want to try this on a valuable puppy save, then BACK IT UP.
You have been warned. At the time I had written this article, puppy 4 was the latest stable distribution. Afaik puppy has since then split off into several distributions using different sources.
If you are going through this tutorial for fun, then I'd recommend that you get the latest puppy 4 distribution, which is 4.31 if I'm not mistaken. Otherwise, proceed at your own risk. Download links on the. I find it kind of silly that debian has no list whatsoever of required packages to get a bare system running.
Here's a list of packages that I have needed while Debianizing my system. Required packages may differ, or I may have forgotten to add one. Go ahead and add it yourself, you'll be benefiting the whole community;) (To edit, add /edit to the URL bar in your address.
Speaking of silly.AHEM wikka AHEM.) Package name Download link Comments libgcc1 libc6 dpkg Perl-base Debconf Debconf-english, or Debconf-i18n libpam-runtime libpam0g Bash libncurses5 Base-files awk (gAwk) For this, we'll use gAwk, since Awk is actually a virtual package. Base-passwd passwd You will need to do lots of editing in the /etc/shadow file to get this package fully working. Debianutils Solves that darn missing tempfile command! Libpam-modules libdb4.6 login Heh. Very cryptic error message from libuuid before I found out that this package was needed:P Of course, according to Debian devs, 'This packages comes standard with all debian systems, so we shouldn't have to make it required.' Libblkid1 mount initscripts e2fsprogs e2fslibs libcomerr2 libss2 lsb-base sed ncurses-bin sysvinit-utils sysvinit Once you technically correctly install it, it will give you an error saying 'init: timeout opening/writing control channel /dev/initctl'.
I'm assuming that this is because we haven't yet rebooted the computer since starting our debianization, and I'm also assuming that this is no cause for alarm. At least dpkg didn't say so. Go to see my flow chart. You'll want to follow it from right to left. The packages most-right are the ones you'll want to install first, then move up and to the left.
Starting at the very beginning here, I'm assuming that you have just downloaded the puppy ISO from I myself will be installing it into a blank hard drive in my PC, but whether you are doing the same or installing in a Virtual Machine, the step process is similar. NOTE: I know that installing puppy to the hard drive defeats the general purpose of puppy, but as far as my knowledge of how puppy works goes, it will be the only way for this to work.
Install/Boot puppy. Click on install on the desktop 4II. Click on the 'Run the puppy package manager' button 4III. Search for dpkg and install the first and only result that comes up. After that you will never have to go through step 4a again.
Now all you have to type is dpkg-deb -x.deb file. Ensure that you are in the root of your hard drive, since the files in the.deb archive mirror that of the root of your hard drive. Search for and download DPKG for lenny on debian's package site, then run dpkg-deb -x /dpkg.deb (Assuming you saved it as dpkg.deb when you downloaded it.) 4d. Now type dpkg to ensure it installed correctly. You may now install the other packages. This can be done by dpkg -i (packagename). Unlike the previous command, these packages do not have to be at the root of your hard drive, since dpkg will automatically install them as so.
Eventually you will reach a point where libc6 and libgcc1 will loop-depend on each other, meaning that one asks the other to be installed first, so you will want to run dpkg -i -force-all libgcc1.deb. This should automatically install libgcc1 and libc6. However, when it tries to install libc6, busybox will interrupt saying init is the parent of all processes.
Cool story, brah. Navigate to /var/lib/dpkg/info and edit libc6.postinst. Go to line 367, and comment out all lines from that to line 371. That portion should like this when you are finished.
#if '$(stat -c%d/%i /)' = '$(stat -Lc%d/%i /proc/1/root 2/dev/null)' ; then # the devicenumber/inode pair of / is the same as that of /sbin/init's # root, so we're.not. in a chroot #(init u; sleep 1) #fi 5c. Save and close the file, then run dpkg -configure libc6. It should finish, then at that point you will want to run dpkg -i libgcc1.deb one more time to make sure it is installed as well. After installing libselinux1, you may now install coreutils.Wait? Errors relating to a directory with perl in it!? No one said we needed perl!
Go ahead and download/install perl-base, then try again. Perl depends on dpkg?
Ok, let's have dpkg install its self then. (download and install dpkg, with dpkg.). Dpkg will then ask for coreutils, which was indirectly asking for perl-base, which was in turn asking for dpkg. So now dpkg -i -force-all perl-base.deb. Coreutils will then whine for a backup file, so create a blank file at /var/backups/infodir.bak. This will require creating the backups directory first.
NOW you can run/install coreutils. After that, and just to be safe, dpkg -i dpkg.deb too, to prevent any further confusion. (Which will require downloading and installing lzma first, and any of its dependencies as well. But heck, maybe it(they) will be useful in the future.) 8.
Now we can get to work. Navigate to, and save the package to the root again. Don't forget to get the debian-archive-keyring package, as well as any dependencies that follow, since apt will want them before you install it. Install the dependencies, then install apt. Type apt-get to see what comes out, and if it's something other than 'Command not found', congratulations! You're past the worst part of this.
Now we need to create the sources.list file. Someone has made an excellent site for this particular task, It supports multiple debian releases as well as different branches, too. I will include a perfectly working sample below. Create the sources.list file in the path /etc/apt/, and add the following to it. Type apt-get update. You should see lots of links pop up, then the prompt come back. (NOTE: This may take a minute.
Let it do its thing.) 14. You are now debianized by my definition. Take care in downloading possibly system-modifying packages, especially ones that change the way linux boots up. Puppy has it's own special way of booting up, so changing that could stop you from getting back to your puppy. Do not restart or shutdown your computer at any point during the above procedure.
I have not tested the stability of a booting system after the installation of any one package, thus doing so your self could leave you unbootable. Problem: When attempting to run apt-get, you get an error reading 'E: Unable to determine a suitable packaging system type'. Cause: DPKG is not installed.
Solution: Visit the debian package site, and download+extract the dpkg package. Problem: When attempting to do any command (update, install, remove, etc.) with apt-get, you get an error saying 'Cannot open file /var/lib/dpkg/status - open.
Basicall saying that it cannot find the file named 'status'. Cause: We simply have not install DPKG all of the way. Solution: No worries, this is an easy solution. Simply navigate to /var/lib/dpkg, and create a blank file named 'status'. Problem: When booting, it says Starting up., then init: applet not found. The kernel panicks.
Cause: Your busybox binary file has been overwritten, with what seems like a debian version. Boot up puppy in mode.
Access /bin, (and not in your broken hard drive, but the ramdrive.) 3. Find busybox, and copy it to the /bin folder in your broken hard drive. If there are differences in file sizes, you are on the right track. Overwrite it, reboot, enjoy. If there is no difference in file size, then there is something else wrong. Sorry, but I wouldn't know what else. Problem: While installing a package, you get a console error reading; 'tempfile: command not found.'
Cause: Generally occurs while configuring base-passwd, and debianutils is not installed. Solution: You must install the debianutils package. See the Required Packages section for a link.
Problem: While installing a package, you get an error saying; '/usr/lib/libxml2.so.2: undefined symbol: gzopen64' Cause: I've seen it only occur in one package. (Can't think of it right now.) Happens because of an outdated zlib installation. Download the zlib1g package from Debian. Extract it's contents, retaining the file/folder structure, to your root.
Try installing the package again. NOTE: Some people have reported that it is necessary to run the command 'ldconfig' after doing this. If your package gives the same error after trying steps 1-3, then run the command. NOTE2: zlib is necessary for all programs to function on puppy. If it gets removed or corrupted, no programs will work, so make sure you have a backup and/or the updated package already extracted. Problem: When booting, an error repeatedly comes up saying something about an /etc/tty0 directory missing.
Cause: This is linked to installing a certain debian package. Solution: I currently have no direct solution for this. If you have a Live CD, try chrooting into the system and installing any terminal-related package.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |