(old)Puppy Linux Discussion Forum

greengeek wrote:Maybe the 'foreign' portion of the PPM could be nothing more than an sfs - so that it allows the foreign package to be run in a nondestructive way, then discarded at next boot if unsuccessful. Sort of like a "static_package_on_the_fly"

Things other than sfs and {2,3,4}fs files can be unioned. For instance you could install all Debian Wheezy packages to /mnt/sda1/wheezy and union it to / ... likewise for any variant of any distro.

technosaurus wrote: For instance you could install all Debian Wheezy packages to /mnt/sda1/wheezy and union it to / ... likewise for any variant of any distro.

If that process was used - how easy would it be to "un-union" or unload or disconnect those packages if they started to show an undesirable effect and the user wanted to get rid of them? I was thinking that an sfs was easier to disconnect (unload) but is an sfs really no different to the unioning you have described?

An SFS is a file system image. You can make a file system image using any file system you like. Any of them can be used any of the ways normal file systems are used -including adding them to a union mount -either as read-only or as read-write if the file system permits that(SFS, cramfs, and cromfs do not).

amigo wrote:An SFS is a file system image. You can make a file system image using any file system you like. Any of them can be used any of the ways normal file systems are used -including adding them to a union mount -either as read-only or as read-write if the file system permits that(SFS, cramfs, and cromfs do not).

For file systems that are read only, having a writable layer above them makes it look to the user like a write can be done. Making a utility that can make a new SFS from the old with the changes can be added as a "rebootish" option so that the user can do it on demand.

I want everyone to understand that I am NOT a Linux distro/application developer. But, over the years, I have heard and understand rationales presented for compressed filesystems as well as use of SFSs as well as unioning and other ideas and implementations.

One of the things that is constantly thrown onto the table is the notion of install packages "trashing" a running system.

Here's my problem
Excepting for the often times when a newer distro is released and where a user tries to use/install the new distro to the PC using the old distro's older save-file(s), I have not witnessed any general user complaints of installing package(s) that locks or crashes their Puppy distro system.

Questions

• Even though its a conceivable occurrence, are package installation crashes happening?
• And if so, at what scale?
• Does the current package system really need a re-architecture?
• Should or will any new approach be simple for new and experienced users to extend PUPPY with subsystems and application should a user desire?

Curious

Sure.
Don't bundle stuff together.
Get dependencies straight.
Package each binary and library separately.
Separate architecture independent resources.
The package manager should warn if an uninstall will affect other packages.

Debian, for one, has strict rules about this.
Puppy, on the other hand has played fast and loose.

Side note: Puppy went about half a decade without a proper uninstaller. It took <10min for me to write one in ~10 lines including reverse dependency checks (I actually wrote it as a 1-liner at first). The current method is bad for multiuser though since installed packages go to /root/.packages/... instead of /var/...

Hello everybody at the community:

I'm interested in being a supporter or tester or puppy linux CE

I'm spaniard, so I can help with some translations

Feel free to mail / post me

HAVE A NICE DAY U ALL

Hello pp4mnklinux.

Thanks for the offer, but for all intents and purposes, this Community
Edition of Puppy -- although quite good at the time -- has faded away. If
you look at the first post of this thread, you will see that it was started in
the Fall of 2013. Time runs fast in our Puppy environment.

I'm not discouraging you, quite the contrary. Perhaps browse around the
forum some more and find an active / recent Puppy you'd like to test
out / improve / translate.

Of course, "iguleder" and the members of the woof-CE team are always
looking for "personnel", Puppy-testers as well as Puppy-makers.
http://murga-linux.com/puppy/viewtopic.php?t=101174
But be fore-warned: woof-CE is a tall order. The woof-CE github project is
where the new Puppies are being crafted, so, to contribute / collaborate,
you have to know your Linux and your Puppy through and through.

On the other hand, you may have noticed that the forum has a Spanish
section. I believe that a good forum member to contact about its needs
would be "nilsonmorales". He's pretty much abreast of what's going on
with Spanish and Latino Puppies. (E.g. the "pupjibaro" series, but there
are others. In general, these Puppies rock, and in particular their graphic
aspect is always remarkable!)

Welcome to the kennels, my friend, and good luck!

Bye for now.

musher0

Hello @pp4mnklinux. In addition to what @Musher0 shares, you would, also, want to get in touch with @L18L. Send him a PM or post him here with your desire to contribute your language skills. Expect to receive advice and/or instructions.

Hello all.

Anybody knows if wanderer is still around?

BFN.

musher0 wrote:Anybody knows if wanderer is still around?

Hey, musher0.

Last post would appear to have been on the 30 Jan this year; previous one to that was mid-November....

Your guess is as good as anybody's.


Mike.

hi all

yes I'm still here
just reading and playing with stuff

thanks for noticing

I'm always amazed and inspired by the puppy community

thanks everyone

wanderer

Ah. So there's the man!!!

Hi, wanderer!

What are you up to these days? Any Puppy ideas?

BFN.

hi musher0

what I'm playing with now is the minimal modular pupngo tinycore thing.
which is a very puppy type concept (simple small modifiable extend-able). I think it would be useful and interesting to the puppy community especially to non gurus like me to have something that is small and simple enough to learn and build upon so we can build a system from the ground up using only the parts we want. Anyway its a lot of fun.

By the way how are you doing and what are you up to ?

wanderer

Great idea!

As for me, I'm fine, thanks.

These days, I'm trying not be too much of a nuisance to jopejp2424 and his brand
new pupjibaro-jessie-beta!

BFN.

jibaros are barbarians who speak english, never Her Majesty citizen will use a barbarian Puppy. Furthermore learn their language.
Don't break the apartheid, musher0 . El puppito va a jugar futbol,
Puppito is the baby of Mam Puppy and papa Perrito Toutou (france) is far from all that..

There are other tools to remasterize than woof CE, tools for users, and tools which works perfectly. Switch the kernels for brand new computeurs, and things are done.Nothing new apart the kernel, and the ugly SVG icons...
Woof CE products series, derivatives (no personal touch). Woof Ce is a factory.

musher0

I followed your link
great work

wanderer

wanderer wrote:musher0

I followed your link
great work

wanderer

Thanks.

Most of the credit goes to josejp2424, of course. He's the one who managed to
create a viable "Jessie Puppy" using the Woof-CE process. I helped by finding and
providing some missing libs.

It's very likely that I'll use his pupjibaro-Jessie as a basis to continue work on
"The Pooch".

BFN.

musher0

your pooch and pupjibaro will be synergistic
great way to go
kill 2 birds with 1 stone
woof-ce is a great system
but you must be a brave and clever man to use it

congrats

wanderer

wanderer wrote:musher0

your pooch and pupjibaro will be synergistic
great way to go
kill 2 birds with 1 stone
woof-ce is a great system
but you must be a brave and clever man to use it

congrats

wanderer

Hi wanderer.

Yeah, synergy. Why not?

Thanks for the "congrats", but I'll enjoy them more
when the birds are in the oven!

BFN.