Puppy 4.4 CE - Phase 1: pet tests

Message

rexterd · #121 Post by **rexterd** » Sun 11 Oct 2009, 13:22

Is 4.4 using aufs as its default filesystem? Please include mounting sfs file on the fly. Just some few lines needed to be added to init script. Thank you.

technosaurus · #122 Post by **technosaurus** » Sun 11 Oct 2009, 15:58

jrb has sent me a pet that allows dynamic loading in 4.3+ (there is already a puplet available)

Lobster · #123 Post by **Lobster** » Sun 11 Oct 2009, 16:12

Those who have offered to help with 4.4
I suggest they download and test 4.3.1 release candidate
http://www.puppylinux.com/blog/?viewDetailed=01161
4.3.1 will be the base for 4.4
Let us get it as good a base as possible

You could also become familiar with the google bug reporting system technosaurus has set up.

I was exploring the bug reporter this morning, trying out the wiki - could not edit the wiki but was able to add a link to our existing wiki page
from the front page

gyro · #124 Post by **gyro** » Sun 11 Oct 2009, 19:24

Now that my pup-430 frugal install mounts the aufs stack with pup-430.sfs and zp430305.sfs at the bottom, I've discovered something a bit odd. There seems to be some firefox 2.0.0.7 stuff in devx_430 /opt/mozilla.org/.

This may have caused problems with my real firefox, which is included in my-apps-sfs4.sfs. When I mount devx_430.sfs above my-apps-sfs4.sfs, firefox does strange things. But if I mount my-apps-sf4.sfs above devx_430.sfs, firefox is ok. (My fixed init also mounts them in the order that I specify them in BootManager, rather than alphabetical as it did before.)

So we might have to be careful that no existing sfs files contain rubbish that used to be hidden by pup-430.sfs.

Does devx_430.sfs contain any unnecessary left over's?

gyro

shinobar · #125 Post by **shinobar** » Wed 14 Oct 2009, 03:10

Graphical menu on boot up is easy thanks to Grub4Dos.
atatched the screen shot of Puppy 4.30 Japanese edition.
the menu has followed options:

nomal boot
boot with most safe options
boot with pfix=ram option
pfix=fsck
and boot up menus of Windows if they are installed

technosaurus · #126 Post by **technosaurus** » Wed 14 Oct 2009, 04:22

@ gyro the firefox directory in /opt is there to compile plugins etc... the layers only should affect things in the same directory... the only thing that I see could be an issue would be SVG images from the .la file in plugins... is that the issue? ... sorry "strange things" is difficult to interpret

technosaurus · #127 Post by **technosaurus** » Wed 14 Oct 2009, 04:26

Shinobar - I have recently completely removed my windows install to make room for more compiling so can't test that very well. Is it installed via windows (unetbootin etc...) or from their installer?

or libnss* in /usr/lib?

shinobar · #128 Post by **shinobar** » Wed 14 Oct 2009, 06:18

technosaurus wrote: Is it installed via windows (unetbootin etc...) or from their installer?

tnx for interest.

grab4dos can be installed via windows if you take some steps by hand.
but the screen shot is boot from 4.30JP live CD.
grub4dos itself is on the web. it is well documented.

grub4dos installer is enbeded in the 4.30JP and easy to use, or you can experience it by installing grub4dos-0.4.4-v1.1.peton the original puppy any version of 4.x.

technosaurus · #129 Post by **technosaurus** » Wed 14 Oct 2009, 07:04

thanks shinobar - i'll have to confiscate my wife's PC and play with it a bit

shinobar · #130 Post by **shinobar** » Wed 14 Oct 2009, 14:32

hi, gyro, great!
i implimented your both codes aginst the init script of 4.30JP.
it works fine with our modified bootmanager, reading sfs in subsidiary directories, say '/mnt/home/puppy/*.sfs'.
your codes are cool solusion.
wasted loop devices - suggesed fix
init_patched_pupsfs_zpsfs_last

atatched /usr/sbin/bootmanager extracted from 4.30JP. it reads sfs in subsidiary directories, and i18n'ed.

tnx

gyro · #131 Post by **gyro** » Wed 14 Oct 2009, 14:54

technosaurus wrote:@ gyro the firefox directory in /opt is there to compile plugins etc...

why firefox-2.0.0.7?

technosaurus wrote: sorry "strange things" is difficult to interpret

Yes, but I'm not worried about the "strange things" because I simply mount the sfs that contains firefox above the devx sfs. Problems go away.

What I am concerned about is a warning, I guess.
"fixing" the unionfs stack so that it is:
1) rw layer, pupsave
2) sfs files in order specified in BootManager
3) pup-xxx.sfs
4) zpxxxxxx.sfs
may unearth some problems that have always been "covered" by pup-xxx.sfs in the past.

I have "fixed" my "init" so it does setup the unionfs in the order outlined above, and then found this "problem".
(I checked the unionfs order in /sys/fs/aufs/si_xxxxxxxx/)

("strange things" was that after each reboot firefox never found /root/.mozilla/firefox/xxxxxxxx.default, and so generated a new one.)

gyro

dio444 · #132 Post by **dio444** » Wed 14 Oct 2009, 20:10

I guess I'd fallen behind on my reading duties, so some of this is really old.

1) I REALLY want gnumeric in the "base" liveCD. The proposed solution (splitting out as many apps as reasonably possible into seperate autoloading sfs) seems perfect to me. I really love the idea of a base pup_xxx.sfs that's ~50mb....

And still getting full functionality from a live cd, especially if you can blacklist sfs files with a boot parameter (or during normal boot but I prefer boot parameter).

2) If I understood correctly, and all addon sfs files will be loaded from psubdir, I'm a happy man. See: http://murga-linux.com/puppy/viewtopic.php?t=47064 The "issue" raised about putting them there causing wasted space from sfs duplication holds no water. Symlinks work.

3) I'm not great at self-direction, and I'm not really some great guru. It'd probably be best if I kept my nose out of the key stuff, but if you toss me a specific package or two you'd like me to compile/package recent versions for, to take some of your load off, I'd be most happy to put all my free time into it

Tom

gyro · #133 Post by **gyro** » Fri 16 Oct 2009, 17:39

dio444 wrote:The "issue" raised about putting them there causing wasted space from sfs duplication holds no water. Symlinks work.

Not on all the filesystems that Puppy can boot from. e.g. vfat or ntfs.

gyro

technosaurus · #134 Post by **technosaurus** » Fri 16 Oct 2009, 17:48

Thanks Tom, I recall trying the symlink method in a previous version and had difficulty making it work across directories (don't remember exactly - its been a while) as for compiling new packages, since you are a gnumeric fan, that would be a good one to play with. I can post my notes as far as new vs. old dependencies and various dependencies that should be compiled statically. One thing is libspreadsheet - I don't know if any other program uses it in Puppy (maybe we could try gnomedb?)... so that should be statically compiled into the executable if its the case - same goes for goffice and a couple others (basically anything you need to compile from source because it is missing) --enable-static --disable-shared should do it (I know it seems counterintuitive, but for a single executable it is actually smaller and faster that way)

panzerpuppy · #135 Post by **panzerpuppy** » Sat 17 Oct 2009, 14:22

Puppy 4.3.1 is out. Now we have a solid base for 4.4 (CE)

raffy · #136 Post by **raffy** » Sun 18 Oct 2009, 01:25

Some of my own notes after testing 4.3.1:

1. Use of 4.3.1 and sfs4 OOo 3.1.1 - it's terribly slow in my 800 mhz system compared to using OOo 3.x in older builds like BoxPup 4.13 (based on Woof-ized/updated 4.12 using post-4.20 packages).

2. Use of autonomous HD-resident applications. I've been using Opera residing on hard disk with static libs, and I can switch Puppy versions and run Opera without problems. What's good about it is that my bookmarks and history are preserved in the Opera directory.

The implications:

a. Let us try making large applications hard-disk resident (they can also reside in flash drives) which can then be used across Puppy versions (am confident that I can use my Opera setup from Puppy 2.12 onwards). This way, we can focus on a small core Puppy with the most basic programs. (Puppy is not meant to be implemented anyway as one take-it-or-leave-it bundle.)

b. Implement OpenOffice the way Opera can now be installed, ie, full install to hard/flash drive, but useful across Puppy/Linux versions.

Hope that makes sense, especially given the sfs4 vs sfs3.x incompatibilities.

Addition: Can we try using a name for version 4.4, as searching is a pain without it. Say a name that starts with goo, as we are using googlecode for the first time. Goopy?

panzerpuppy · #137 Post by **panzerpuppy** » Sun 18 Oct 2009, 03:00

xpad (the sticky notes app) has been updated to v4.0.

Superpup says: compile the latest version and include it in Puppy 4.4 CE

raffy · #138 Post by **raffy** » Sun 18 Oct 2009, 03:43

Here is a good additional wishlist:
http://murga-linux.com/puppy/viewtopic.php?t=47908

BTW, am posting here 'coz I can't find the other "wish list" thread for 4.4. Sorry, am on the run.

technosaurus · #139 Post by **technosaurus** » Sun 18 Oct 2009, 04:12

xpad-4.0-i486|xpad|4.0-i486||Desktop|100K|pet_packages-4|xpad-4.0-i486.pet||Jot down notes for later|puppy|4|official|

James C · #140 Post by **James C** » Sun 18 Oct 2009, 04:50

Xpad is one neat little pet. Works fine in 4.31 final.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Puppy 4.4 CE - Phase 1: pet tests

firefox in devx_430?

Graphical boot menu

Re: Grub4dos

sfs order and ...

reordering loading order of sfs files in unionfs stack

Behind on my reading duties.

Re: Behind on my reading duties.

notes from testing

wishlist