How to strip FossaPup64 ? make it smaller (Solved)
Hi
How to strip FossaPup64 ? make it smaller
i want to remove everything except mpv Media player
Discussion, talk and tips
https://forum.puppylinux.com/
Hi
How to strip FossaPup64 ? make it smaller
i want to remove everything except mpv Media player
Hello,
please, study the release notes to Fossapup64. It is possible to deactivate the adrv...sfs module which contains most of apps and then you will have bare bones system.
viewtopic.php?f=146&t=820
I assume that your install is frugal. If you boot Fossapup64 without "adrv....sfs" module, there will be minimum of applications so you can add what you need. Just go to your install folder and rename it (if it doesn't begin "adrv" it will not be loaded by booting).
You may regret not having a lot of what is in Fossapup64 9.5
After you actually try using some of those programs.
You may learn to like them.
All they do is take up a little space.
Some of those programs, are specifically coded to how Puppy works.
Try using a standard Linux program, to do what they do, and Puppy may no longer work.
See you ask for a smaller version and already need to add a program to it.
This info you may need to know:
viewtopic.php?f=156&t=1819
@Feek Thanks i will study that topic.
@bigpup I know when i need other app I just boot from regular FossaPup64.
The thing is.
Will not using the adrv.sfs remove too much?
There may be something in the adrv.sfs that is needed to run MPV Player.
Only way to know is try it.
We the users are also the testers.
I am wondering why you really want to do this?
Is about 200MB of programs really a big deal?
Do not want to see all that stuff in the menu?
You can fix that easily and have the menu show what you want.
Are you real low on memory?
Maybe if we know for sure exactly why.
We may know something better to do.
Puppy is easy to run in some very strange ways.
@bigpup i do that for learning, fun & curiosity
few years ago i tested ASTRUMI linux less than 50mb desktop with many app, also SLiTAZ and even TinyCore.
what i want is a puppy linux with only mpv media player.
The man wants what he wants. Can't force him to change his mind. He also doesn't sound like a total noob, either; SliTaz & TinyCore aren't exactly known for being 'straight-forward' or 'easy' at the best of times. TinyCore, especially, pre-supposes you already possess a certain degree of Linux system knowledge.
Perhaps running a bare-bones Puppy with nothing but MPV is one of those "strange ways"..!
Mike.
Sometimes one does just cause one can In the days of yore I wrote DOS based routers that resided on a 360k floppy and would just reboot in the event of a power failure and just keep going. Finally replaced then with Coyote Linux ones, also floppy resident.
Much more recently I stripped FossaPup64, chosen for the relatively modern libraries. Kept the main SFS as is for maintainability, ditched the adrv, no fdrv needed for my hardware, and piecewise added exactly what I wanted into a ydrv, initially carrying LXDE and PcManFM. Worked so well I continued the process to make it a 'savefile less' install with all the network setup, look'n'feel, etc. in the ydrv. It runs portable un-googled chromium as the browser well and remembers nothing on shutdown. Not everybodies cup of tea but serves a purpose and was fun.
So did you try not using the adrv.sfs and installing MPV player?
If yes and it works.
Is that what you wanted or even smaller?
Maybe using the remove builtin packages to remove what you do not want.
Be very careful!!! Remove the wrong thing and it breaks Fossapup64.
Only remove stuff that has a menu entry, unless you fully understand, what a listed item is.
Then do a remaster of what you end up with.
Your own version of a Fossapup64 9.5.iso
yes i did remove adrv_ then download latest mpv media player
and yes it work but it is still big
I'm sure there are many stuff i can remove... still testing
Unfortunately, the days of achieving a re-mastered Puppy with exactly what you want @ somewhere around the 100MB-120/30MB mark are LONG gone.....
The distros Puppy is built from have become much, much bigger.....and as bigpup says, there's a limit to just how much you CAN remove whilst still retaining functionality.
(*shrug*)
Mike.
Packaged in the ISO is an adrv.sfs which contains many applications. When adjacent to the pupyy_xxx.sfs it will automatically be used on bootup. Start by removing it; or moving out of the frugal puppy's folder.
The problem with applications built into an adrv is that they can not be removed using Menu>Setup>Remove Builtins. [To remove applications form an adrv.sfs or ydrv.sfs, you have to mount that file, copy its contents into a folder, manually remove all files relating to that application from the folder, then dir2sfs the folder, giving the resulting sfs the name of the 'old' adrv/ydrv.sfs]*.
Applications included in the puppy_version_version_number.sfs --e.g., puppy_fossapup64_9.5.sfs-- can be removed with Menu>Setup>Remove Builtins. I recommend that before doing so you download two applications and convert them to SFSes so that they can be loaded and used without having to install them:
radky's listdd-2.1.pet -- used to determine whether your system lacks any dependencies required by a desired application. https://ubuntu.pkgs.org/20.04/ubuntu-un ... 4.deb.html will tell you what dependencies mpv has if you are running Ubuntu Focal Fossa. But you won't be and your Puppy base may lack files built into Ubuntu's OS.
jpep's gnewpet-6.5.pet, from viewtopic.php?p=18174#p18174. gnewpet does what its OP says "Finds current files for an installed Pet, and makes a new version in /tmp. Leave "new version" box blank for straight duplication, or edit to update name. Batch mode builds multiple pets."
If you have any doubt that removal of a builtin may break something, gnewpet will enable its re-installation.
Additionally, if mpv was included in fossapup64's adrv, you can save a lot of work by first booting up using the adrv, then running gnewpet to 'capture' its files as a pet. Then boot without the adrv and install the pet.
You know, of course, that 'remove builtins' doesn't actually remove anything. It write a white-out so that links to the application's files will not be followed and the application appears not to be present. But it's still, actually in the puppy_version_number.sfs. To really get rid of it you have to remaster.
Don't hesitate to ask if you have any further questions.
=-=-=-
If removing applications from an adrv or ydrv seems at first glance to be a PITA, that's because it is. 666philb had a good reason for making extensive use of an adrv: a 'stripped version' of fossapup64 for those who, perhaps having a computer with limited resources, want it and a 'fleshed-out' version for the rest of us. But, IMHO, locating anything an an adrv/yrdv which someone may not want creates problems; perhaps not while using a SaveFile/Folder --whose instructions will have priority-- but when converting that SaveFile/Folder to your own adrv/ydrv or on remastering.
@mikeslr you hit the nail!
that's exactly the info i need
What about fdrv_ and zdrv_
if i remove zdrv_ a basic system boots to desktop and keyboard work but my mouse no
if i remove fdrv_ a basic system boots to desktop but i have no wi-fi so no internet
is there similar tool like gnewpet & listdd for fimware ?
In all honesty, if you want to remove basic, essential files like the zdrv & adrv yet still have support for just your hardware, there is but one option; and that is to compile your own kernel, setting JUST the flags that you, personally need.....and nothing else.
There is no other way round it, really. From what I understand, the Woof-CE 'kernel-kit' will let you do this. Learning the 'recipe' you need - there's a multitude of 'flags' that have to be either 'set' or 'unset' at compile time - that's where experience comes in to the mix.
An alternative suggestion? Take a look at Gentoo or Linux-from-scratch (aka LFS). Both of these will allow you to build a system, literally from the ground-up, optimised for your specific hardware, and no other. I can promise you one thing; by the time you get finished (and some people take years to achieve what they want), you will have a ground-up, intimate knowledge of the workings of a Linux OS in a way few others have.
Mike.