pUPnGO 2012
-
- Posts: 1885
- Joined: Tue 05 Jun 2012, 12:17
- Location: Wisconsin USA
-
- Posts: 1885
- Joined: Tue 05 Jun 2012, 12:17
- Location: Wisconsin USA
The idea I had, was my vision of a modular puppy distro.
There will be:
-different kernel options
-different base tool chains
-different desktop options
while having a big online repo and having some unity no matter what modules you have loaded. I want this to be distro that will benefit all (whether want to use on a P3 system, Atom netbook, or on some thousand core gaming system), there will be something for everyone.
There will be:
-different kernel options
-different base tool chains
-different desktop options
while having a big online repo and having some unity no matter what modules you have loaded. I want this to be distro that will benefit all (whether want to use on a P3 system, Atom netbook, or on some thousand core gaming system), there will be something for everyone.
....
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
It is possible, not too difficult and has been done (mostly via zdrv.sfs), but dont expect all apps from other distros to work with other kernel versions, they dont all build packages against a lowest common denominator ... Fyi If you build packages against Linux 2.32, glibc-2.6ish and gtk2.12 (and corresponding dependencies) they are pretty likely to work on other distros... Basically build against the oldest version that will build it if you can. There are other considerations like stack smashing, etc... Someone really should post a portability howto wiki somewhere for other builders.
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].
I have not tried any of the two so cant advise here. You are sure pupngo is a healthy starting point? (I'm not)...bark_bark_bark wrote:Hello, I have a really ludicrous idea about a puppy derivative. I need to know, how can I get the current code in the woof build system into the original pUPnGo. Also how to a compile a glibc from scratch?
Maybe Debian or some other large distro already close to target?
-
- Posts: 1885
- Joined: Tue 05 Jun 2012, 12:17
- Location: Wisconsin USA
-
- Posts: 1885
- Joined: Tue 05 Jun 2012, 12:17
- Location: Wisconsin USA
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
Here is the low down. Since pupngo's multicall binaries were statically built against a kernel older than any major distro uses, they can be used with all of them.
Now, some stuff (not much) will need to use the distro version like squash tools where newer versions are now in the vanilla kernel and stable but were only patches in the older kernels and are incompatible.
Now, some stuff (not much) will need to use the distro version like squash tools where newer versions are now in the vanilla kernel and stable but were only patches in the older kernels and are incompatible.
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].
Iguleder has recently started working on a similar sort of concept here:bark_bark_bark wrote:Well, I kind of wanted to use a tiny base.
http://www.murga-linux.com/puppy/viewto ... 427#724427
Sounds like it runs the sfs addons in a sandboxed environment which is quite a nice idea.
Oh, I wondered why you where doing so muchwork to a very old base, I kept waiting for something newer... Now it makes sense, except that I do not see any newer roll outs, are they being uploaded somewhere?technosaurus wrote:Here is the low down. Since pupngo's multicall binaries were statically built against a kernel older than any major distro uses, they can be used with all of them.
Now, some stuff (not much) will need to use the distro version like squash tools where newer versions are now in the vanilla kernel and stable but were only patches in the older kernels and are incompatible.
greengeek: Thanks for the link - will be exiting to follow Iguleders work. Remind me slightly of booting xwoaf, basic linux or tinycore via sfs in pupngo
Ted Dog: The possibilities for posting new variants of pupngo are huge but for the moment my ideas for posting other than what would be considered remasters are not present.
Other developers much more skilled than I deliver small basis with package managers to build up custom systems. Atm the static linked principle seems the most unique pupngo feature still not handled by most other puplets. So I cruise around, collect apps that potentially add functionality/variability to a possible future pupngo - but at the same time can be used today in a broad range of puppy versions (and beyond..).
Ted Dog: The possibilities for posting new variants of pupngo are huge but for the moment my ideas for posting other than what would be considered remasters are not present.
Other developers much more skilled than I deliver small basis with package managers to build up custom systems. Atm the static linked principle seems the most unique pupngo feature still not handled by most other puplets. So I cruise around, collect apps that potentially add functionality/variability to a possible future pupngo - but at the same time can be used today in a broad range of puppy versions (and beyond..).
How did you capture those vids? They are very clear.goingnuts wrote:Remind me slightly of booting xwoaf, basic linux or tinycore via sfs in pupngo
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
I posted some light weight xpm tango icons here
over 200 icons each in both 32x32(gz compressed to 49kb) and 16x16(gz compressed to 27kb) versions
I did a some tricks to ensure that they shared an indexed color palette of 64 colors to help with compression and manually edited them to make them look decent. Even without compression they are significantly smaller than the RGBA icons included in the default Tango package.
I like the responsiveness of jwm with only xpm enabled (especially when the file system is already compressed - indexed xpm is smaller and faster)
over 200 icons each in both 32x32(gz compressed to 49kb) and 16x16(gz compressed to 27kb) versions
I did a some tricks to ensure that they shared an indexed color palette of 64 colors to help with compression and manually edited them to make them look decent. Even without compression they are significantly smaller than the RGBA icons included in the default Tango package.
I like the responsiveness of jwm with only xpm enabled (especially when the file system is already compressed - indexed xpm is smaller and faster)
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].
- Iguleder
- Posts: 2026
- Joined: Tue 11 Aug 2009, 09:36
- Location: Israel, somewhere in the beautiful desert
- Contact:
goingnuts, I wrote a udev replacement you could use. It relies on devtmpfs (i.e doesn't create device nodes), but mdev can compensate for that.
It's a small, single-process solution for loading kernel modules, without support for firmware loading or libudev. Is it useful for pupngo?
EDIT: opened a thread.
It's a small, single-process solution for loading kernel modules, without support for firmware loading or libudev. Is it useful for pupngo?
EDIT: opened a thread.
- Attachments
-
- devd.png
- devd in action
- (39.91 KiB) Downloaded 690 times
[url=http://dimakrasner.com/]My homepage[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]
I've been trying to remaster a Turbopup variant using pup431 for the remaster but no success. I assumed that 431 would be ok for remastering a 420 based pup.technosaurus wrote:I typically do my dev work in wary for broader compatibility, dir2sfs is squash version dependent though so for pupngo, I would use a 4.1.x derivative like akita.
Now I look back at your comment I realise that I previously thought that both pupngo and turbopup were based on pup 420 (although I see now you pointed out here that pupngo is 412 based...).
Is pupngo definitely based on 412 rather than 420?
Would you expect 431 to have trouble remastering a 412 based pup or 420 based pup?
Should I use Akita to remaster turbopup rather than using 431?
cheers!
Use Woofy, sc0ttman's remaster tool. But remember with TurboPup -- it's built like a Formula 1 car -- it's *dang* fast, but it's not very rugged, and when it breaks, it breaks spectacularly.
I tried to get TurboPup to remaster cleanly with Woofy about four or five times and I wound up with one badly broken Puppy every single time.
I wish you luck in your endeavors -- and I think you'll need plenty of it!
I tried to get TurboPup to remaster cleanly with Woofy about four or five times and I wound up with one badly broken Puppy every single time.
I wish you luck in your endeavors -- and I think you'll need plenty of it!