Sourceforge currently shows that iso size is 86.1 mb, but real size is 82.1 mb, I don't know why they give false information. If you want me to add linux-firmware (4mb) in main iso, then we must remove something, not 4mb but whole 6mb to make iso under 80mb again. Plan is: first I will move libraries mentioned here http://murga-linux.com/puppy/viewtopic.php?p=675849#675849 to archdev sfs; then completely remove pacmanxg - that program is good, but anyone can install it later; remove yaourt with 3 dependencies. Packer will return but will be in archdev, it is logical because you anyway need archdev to compile. If you want to help, see if you can find some unnecessary stuff inside /initrd/pup_ro2 - this command might help (shows 20 largest files in folder):

Code:

du -sh * | grep M | sort -n -r | head -n 20

Goal is to remove 6MB, current state: moved libs to archdev -600KB, pacmanxg and yourt - 1.6MB.

This may be minor, but I just installed Gimp using the terminal "pacman -S gimp" -- well, that increased my personal save file from 90MB to about 260MB, but Gimp didn't appear in the Graphics Menu. So, I used PacmanXG4 to reinstall Gimp and it appeared in the menu then, plus my personal save file increased about 7MB (menu entry?). Who knows, but this is pretty cool...!!

Sourceforge currently shows that iso size is 86.1 mb, but real size is 82.1 mb, I don't know why they give false information. If you want me to add linux-firmware (4mb) in main iso, then we must remove something, not 4mb but whole 6mb to make iso under 80mb again. Plan is: first I will move libraries mentioned here http://murga-linux.com/puppy/viewtopic.php?p=675849#675849 to archdev sfs; then completely remove pacmanxg - that program is good, but anyone can install it later; remove yaourt with 3 dependencies. Packer will return but will be in archdev, it is logical because you anyway need archdev to compile. If you want to help, see if you can find some unnecessary stuff inside /initrd/pup_ro2 - this command might help (shows 20 largest files in folder):

Code:

du -sh * | grep M | sort -n -r | head -n 20

Goal is to remove 6MB, current state: moved libs to archdev -600KB, pacmanxg and yourt - 1.6MB.

well when u have to pick between an arm and a leg....i think having the leg is more beneficial. so rather than stripping the system out to that extent.....it's probably better overall to leave the linux-firmware as an sfs file.

dennis-slacko531: If some applications don't appear in menu you could try to remove /root/.cache/menus folder, that will force menu to recreate. For installing larger applications maybe it's better to use makesfs script, that way space in savefile will not be used.

Anyone tested Pwireless, I can't add Frisbee because it's not using system dhcpcd, wpa_supplicant..., and needs older system libraries like readline.so.5 (included is readline.so.6).

yaf-splash should not be mandatory, it only shows notifications, but ok will add Xdialog, it's 30kb.
Now I will try to recompile cups, same version 1.6.1, but without dependencies krb -1.5 mb and avahi -500kb. This folder /usr/share/i18n compressed is 3mb, something could be removed from there, .. but what...
EDIT: it's finished - cups package size is 6.7mb, converted was 6.9mb, plus I removed 5 dependencies of that old cups package, combined size 2.1mb.

Sourceforge currently shows that iso size is 86.1 mb, but real size is 82.1 mb, I don't know why they give false information. If you want me to add linux-firmware (4mb) in main iso, then we must remove something, not 4mb but whole 6mb to make iso under 80mb again.

Is the 80MB limit imposed by someone (sourceforge?) or is just a number that you are aiming for so will be an "80MB OS"?
If it is so will load in RAM, the ISO size limit is half of the available RAM. So 128MB for a 256MB machine.

Making the final decision you may want to consider functionality.
If the idea is that the base can be just used to build the system of your preference through pacman, then the wider possible hardware compatibility should be in the base. ie, video, audio, network, printing and peripherals drivers. So the machine will be adequately functional to build your system by just downloading packages.
If you can not make you hardware going OOTB, you just do not bother any further, particularly with a bare bones OS.

In any case keep in mind that these "build it yourself" pupplets may have a considerably more limited audience/user base. The Saluki/Carolina/lina-lite developers may provide some info. Also Tinycore vs Puppy is an equivalent similar comparison._________________== Here is how to solve yourLinux problems fast ==

My idea is, as written is first post, to give full control to the end user - if someone want to install his own specific programs then he would just download main iso, and if he thinks that is too hard or lacks experience he will also download archapps sfs, then connect to the internet and start to explore. How to use pacman is explained in documentation with examples, everyone can make use of it. I first installed Arch Linux using net-install cd image. When installation finished I had OS without any application, not even graphical server, so had to use console browser called links to search on archwiki for informations, and finally got to work, after some 3 hours. That is what I would call bare bones OS, not ArchPup. And 80MB limit was invented today to add some "challenge to this game".

My idea is, as written is first post, to give full control to the end user - if someone want to install his own specific programs then he would just download main iso, and if he thinks that is too hard or lacks experience he will also download archapps sfs, then connect to the internet and start to explore. How to use pacman is explained in documentation with examples, everyone can make use of it. I first installed Arch Linux using net-install cd image. When installation finished I had OS without any application, not even graphical server, so had to use console browser called links to search on archwiki for informations, and finally got to work, after some 3 hours. That is what I would call bare bones OS, not ArchPup. And 80MB limit was invented today to add some "challenge to this game".

that's sounds good. but if that's the case, why not add openbox, tint2, urxvt, and the other gui apps to openapps.sfs, and just let the main.sfs boot to a tty prompt.

i think that would be an excellent way of doing it. and have some more premade .sfs's for the users to download. the light one with openbox, tint2, etc. the medium with apps like xfce, xfce-terminal, etc. and a big one with like kde or something.

i think a layout like that would b unmatched. and it would appeal to super uber geeks, intermediates, and beginners. and would also be the best distro for new computers, or old ones.

it would also free up that 4mb, to put the linux-firmware in the main.sfs.

Notifications are very useful when connecting by wifi as they show the progress of the connection - if yaf-splash is a link to gtkdialog-splash in normal puppies cannot it be included as a link to the arch equivalent???

@stifiling
I would like something like that. My idea would be to include you those extra puppy apps that make up for not having a full Desktop Environment (but usually only require gtkdialog) in an SFS. People going for KDE/Gnome would have less need for this.

---
I've tested pns-tool in 12.12 and it works very well. Is there a way to make it save the choices made?

To create the /interface file, wlan0 must have been created prior to the Frisbee startup code (in init.d??) being run - that's why the wifi driver needs to be loaded earlier in the boot sequence - .start is too late - which can be achieved by editing the addlist in /etc/rc.d/MODULESCONFIG

I think there must be lots of module loading stuff missing from archpup that has been worked on for many years in trad puppies - rerwin is the current guru who knows most about this side of things.

Cheers
PeeBeeLast edited by peebee on Mon 07 Jan 2013, 10:04; edited 1 time in total

MD5 matches, verified the data when burning a cd, used unetbootin,
other live media are booting fine, even copied the .sfs to the root
of each partition. Is there a mystery command to run at the prompt?

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum