Arch Puppy ;)

What features/apps/bugfixes needed in a future Puppy
Post Reply
Message
Author
Gnuxo
Posts: 365
Joined: Thu 09 Feb 2012, 19:01

Arch Puppy ;)

#1 Post by Gnuxo »

I am no developer and I'm no expert but I do know one thing. Every time Puppy releases a new version, I have to reburn it and risk losing my data.

Now, I don't mind backing things up but after talking to some people online, I became firmly convinced that if someone would take Arch linux as a base for Puppy and use that minimal rolling environment to create a semi-rolling pup, it would be amazing.

Arch's speedy nature combined with Puppy's awesome .pet infrastructure and lightweight apps. Any new updates to the distro are just added as an update without the need to reburn anything.

And of course the best reason of all, the ability to install Arch packages. Though considering how cross platform .pets are, I could just as easily install lucid .pets and just have the system auto update whenever necessary.

I know that this is difficult to pull off but it is awesome none the less. No one may even take this idea but I know that I just had to put it out there. You know that you've thought about an Arch Puppy too. You've just never considered saying anything about it.

Well, I've said it. And now that that pandora's box is opened, we'll see what happens.

amigo
Posts: 2629
Joined: Mon 02 Apr 2007, 06:52

#2 Post by amigo »

"awesome .pet infrastructure" -Hehe -you're joking, right? Using arch as a base has been mentioned and proposed here before, though.

Gnuxo
Posts: 365
Joined: Thu 09 Feb 2012, 19:01

#3 Post by Gnuxo »

Well...it's just my opinion. I think it's awesome. I mean I'm able to install lucid 525 pets on slacko and the slackware .txz files as well.

Actually when installing the newest Seamonkey on Slacko, it said that I can install Slackware or Arch packages?

That got my hopes up but I haven't been able to install Arch packages. :/

Anyway, sorry if I sounded dumb.

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#4 Post by nooby »

Every time Puppy releases a new version, I have to reburn it and risk losing my data.
I get curious on this thing. You reburn on a RW DVD then?
Or you do frugal install on a USB flash memory and name
that to reburn it instead of naming it add a frugal installed OS
to the one that is already there?

Or do you burn your internal HD? I have some 6 different Linux
frugal installs on my HD. No need to burn any of them.

Do you refer to full install and you wipe it all clean and do a new
full install?

Or maybe you refer to the save file that it can be loaded by the new
puppy and that way being not compatible can get unusable and so on?

You can make a directory named Backup-of-Puppy-save-files
and then place copies of the savefiles there naming them by
version and date like Lupu528-090212, Slacko5321-090212, and so on

No need to loose a backup at all.

Sorry my poor reading skills can have totally missed the point.
I use Google Search on Puppy Forum
not an ideal solution though

Gnuxo
Posts: 365
Joined: Thu 09 Feb 2012, 19:01

#5 Post by Gnuxo »

I usually make save files. I've had save files break while updating versions of puppy. For instance when I was transitioning from lucid 520 to 525, during boot it gave me the option to transition my save file. I said yes, transition.

The save file was corrupted and became unusable.

I lost all my data and applications.

Frugal installs would be no different. Because it's the save file that has all the data and if your risk breaking your save file by upgrading then it seems unfair to me.

which is why I thought that having a rolling or semi rolling infrastructure could fix that. Because then you can upgrade easily and keep support for the save file.

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#6 Post by nooby »

Now I get it better. Sorry my poor grasp of English messed my head up :)
when I was transitioning from lucid 520 to 525, during boot it gave me the option to transition my save file. I said yes, transition.

The save file was corrupted and became unusable.

I lost all my data and applications.
Yes that is why some Devs remind us to never use the save file
instead to write

puppy pfix=ram and then when we have a new pupsave file go back to
pfix=fsck so it get repaired.

Others can explain it better than what I can. I barely get things going.

But wanted to understand what you talked about.

Puppy is seldom made for upgrading the way other linux os are.

Sure sometimes it just works but at other times there are dependencies
that spell trouble.

Some of us has started to use SFS instead. Many of these can be reused
and one place them outside of puppysave and that way one can reuse
them on the fly when needed. I installed Opera browser that way
so whenever I test a new puppy I can always call up Opera without
needing to install it. Makes the pupsave much smaller too if many programs
is not added but still are available when in need.

Sorry me so wordy. I have promised to not post answers due to me too confusing and low quality but got curious on your use of the word burning.

No big deal at all. I leave you now in better hands so they can help you out
I use Google Search on Puppy Forum
not an ideal solution though

Post Reply