Saluki, Puppy Remastered
I compiled 2.6.34 and messed around with compcache yesterday. It became obvious that it's going to work better for a full install or in cases where the SFS file is not in RAM. Trying to compress the SFS is just a waste of CPU cycles. I wonder if there is a way to tell the kernel to try not to swap out the SFS.
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
I wonder if it would matter if it was an initramfs instead...
I've been thinking that since everything does get loaded into ram, it would be nice to be able to use XIP (execute in place) to save ram, but the closest things to squashfs is cramfs which is old and aufs which seems like too much work. I don't know if either one would work with aufs or unionfs.
I've been thinking that since everything does get loaded into ram, it would be nice to be able to use XIP (execute in place) to save ram, but the closest things to squashfs is cramfs which is old and aufs which seems like too much work. I don't know if either one would work with aufs or unionfs.
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].
What about axfs? http://en.wikipedia.org/wiki/AXFS It seems to be designed with that in mind. Maybe it's vaporware...
You are talking above my head so I probably should not interfere...but I cant help it...
If initrd.gz could be both initrd.gz and main.sfs - one could put all the startup stuff there (finding savefiles, mounting, sfs-additions, drivers-load etc.) and let the further customization happen via pets in save-file or sfs-additions. So core is one core and the rest is add ons...
Boot normal via initrd.gz afterwards mount initrd.gz as main.sfs and go from there...
If initrd.gz could be both initrd.gz and main.sfs - one could put all the startup stuff there (finding savefiles, mounting, sfs-additions, drivers-load etc.) and let the further customization happen via pets in save-file or sfs-additions. So core is one core and the rest is add ons...
Boot normal via initrd.gz afterwards mount initrd.gz as main.sfs and go from there...
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
oops thats what I meant - typo - not aufs ... I'm not sure how one would properly do the profiling run ... it seems that it would be a good option if it could directly map the memory in the initramfs rather than reloading an executed program to more ram and then mapping itjemimah wrote:What about axfs? http://en.wikipedia.org/wiki/AXFS It seems to be designed with that in mind. Maybe it's vaporware...
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].
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
I think I get what you are saying, similar to your copy method in the pupngo init. You have some great snippets that should definitely be looked at for size reductiongoingnuts wrote:Boot normal via initrd.gz afterwards mount initrd.gz as main.sfs and go from there...
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].
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
I subscribe to the pcmanfm mail list - gvfs is planned to be switched to straight gio ... so it will be usable even by rox ... it always seems to be 3 months out
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].
Yeah, I saw this about a year ago. But, as I remember, there was a problem with its use. It was old even I started to test with it.Mobeus wrote:gcmartin
... vtpup posted this on getting the samba .pet to work in Puppy 4. It's samba 3.0.26 and is described as SMB/CIFS fileserver and client. Is this one broken? Too old?
Just curious
Mobeus
All major distros have moved to the 3.5+ versions. If we use a version we would well be served to use a current stable version so that qny questions we have could be answered by SAMBA if needed.
See your PM.
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
Here's the deal with using 3.0.37 instead of a later version.
It has more sane dependencies
The build system is slightly less convoluted
It is smaller
It performs 99% of needed tasks
It is compatible with existing frontends
It is more stable
...default setting are really bad though
4.X would-be a legitimate replacement but:
Build tree is bad in a whole different way
Many new dependencies
Unstable
... default settings are better though
Why can't they just make a single libsamba that contains all their libs?
It has more sane dependencies
The build system is slightly less convoluted
It is smaller
It performs 99% of needed tasks
It is compatible with existing frontends
It is more stable
...default setting are really bad though
4.X would-be a legitimate replacement but:
Build tree is bad in a whole different way
Many new dependencies
Unstable
... default settings are better though
Why can't they just make a single libsamba that contains all their libs?
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].
For anyone considering Samba3......
http://www.samba.org/samba/docs/man/Samba-Guide/
Also consider virtual samba
http://www.linux.org/docs/ldp/howto/Vir ... TO-10.html
http://www.vmware.com/support/ws45/doc/ ... ba_ws.html
and Common Internet File System
http://linux-cifs.samba.org/
Some admin tips
http://www.prodevtips.com/2009/02/10/be ... and-samba/
Aitch
http://www.samba.org/samba/docs/man/Samba-Guide/
Also consider virtual samba
http://www.linux.org/docs/ldp/howto/Vir ... TO-10.html
http://www.vmware.com/support/ws45/doc/ ... ba_ws.html
and Common Internet File System
http://linux-cifs.samba.org/
Some admin tips
http://www.prodevtips.com/2009/02/10/be ... and-samba/
Aitch
samba
is rcrsn51's howto on samba
http://murga-linux.com/puppy/viewtopic.php?t=60204
a contribution to the discussion?
http://murga-linux.com/puppy/viewtopic.php?t=60204
a contribution to the discussion?
I've been thinking about how to handle collaboration for this project and I came across TikiWiki today. It's apparently extremely flexible, user friendly, and should be easy to administer.
It supports a lot of neat project management stuff like task lists, bug trackers, plus chat, RSS, forums, and pretty much everything else you can think of.
http://info.tiki.org/Tiki+Feature+Checklist?bl=y
http://doc.tiki.org/Features
Thoughts?
It supports a lot of neat project management stuff like task lists, bug trackers, plus chat, RSS, forums, and pretty much everything else you can think of.
http://info.tiki.org/Tiki+Feature+Checklist?bl=y
http://doc.tiki.org/Features
Thoughts?
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
In the early days of Puppy, if the forum or wiki became slow Barry would create a new service (yes he did everything) This often meant a great deal of work. However any service was created at the point at which it became needed. It is how Puppy started and shows some of the Barryk's unique capabilities.
As Puppy grew some services for example the forum, became others kind provision. Another example, we had a great wiki within the Drupal CMS for a while. The PHP programming developer left for Debian and has never been heard of again. Is Debian some sort of Black Hole? The PHP code was considered too complex and time consuming to support.
Raffy had to revive the old wiki format, transfer what we could and also create a separate CMS. We lost our previous CMS and wiki to one centralizing mistake. It could have worked and many people invested heavily in its content, hosting and development.
So one developer (that's you Jemimah) controlling the communication infrastructure and being in charge of development does not allow for much organic flexibility. However Puppy is not a horse designed by a committee (aka a camel)
Another thing to be aware of, many Puppy forums, wikis etc have been set up. Most fail because setting up a structure is the easy part. It is content and community that draws people. For example the IRC is now being overseen and is a fun place to be for many regulars including some developers.
Content was being added to the Drupal CMS as it had support from Raffy, Coolpup, Warren and many other Puppys. The wiki was suspended as its content was now in the Drupal CMS. The structure did not draw people from where they were - it never does. It was the content providers filling the structure, that provided the draw. it was too dependent on one PHP programmer. There was talk of a revival but nothing has happened that I know of.
The following comments are very focused and I apologize if they sound harsh as I value the potential of Saluki and fully support your efforts
You have one thread, a tiny wiki page, several developers getting bored (one is already talking of dropping out) and no ISO.
What is the minimum base hardware we developing for?
Which kernel are we using?
What are we bootstrapping from?
When will an ISO and devx to start compiling apps and testing be available?
Tiki Wiki is fine.
We have a wiki, we have a forum, we have a blog - actually we don't have a blog - a Saluki joint blog will be good idea. I'll join for the ranting component.
I hope that is taken as helpful thoughts and experience. I am sorry if it is of no value . . .
As Puppy grew some services for example the forum, became others kind provision. Another example, we had a great wiki within the Drupal CMS for a while. The PHP programming developer left for Debian and has never been heard of again. Is Debian some sort of Black Hole? The PHP code was considered too complex and time consuming to support.
Raffy had to revive the old wiki format, transfer what we could and also create a separate CMS. We lost our previous CMS and wiki to one centralizing mistake. It could have worked and many people invested heavily in its content, hosting and development.
So one developer (that's you Jemimah) controlling the communication infrastructure and being in charge of development does not allow for much organic flexibility. However Puppy is not a horse designed by a committee (aka a camel)
Another thing to be aware of, many Puppy forums, wikis etc have been set up. Most fail because setting up a structure is the easy part. It is content and community that draws people. For example the IRC is now being overseen and is a fun place to be for many regulars including some developers.
Content was being added to the Drupal CMS as it had support from Raffy, Coolpup, Warren and many other Puppys. The wiki was suspended as its content was now in the Drupal CMS. The structure did not draw people from where they were - it never does. It was the content providers filling the structure, that provided the draw. it was too dependent on one PHP programmer. There was talk of a revival but nothing has happened that I know of.
The following comments are very focused and I apologize if they sound harsh as I value the potential of Saluki and fully support your efforts
You have one thread, a tiny wiki page, several developers getting bored (one is already talking of dropping out) and no ISO.
What is the minimum base hardware we developing for?
Which kernel are we using?
What are we bootstrapping from?
When will an ISO and devx to start compiling apps and testing be available?
Tiki Wiki is fine.
We have a wiki, we have a forum, we have a blog - actually we don't have a blog - a Saluki joint blog will be good idea. I'll join for the ranting component.
I hope that is taken as helpful thoughts and experience. I am sorry if it is of no value . . .
hosts
Ah, now I recall tuxfamily.org and launcpad.net - both are very good project hosts. Of course, googlecode is still there.jemimah wrote:I've been thinking about how to handle collaboration for this project..
Thoughts?
Puppy user since Oct 2004. Want FreeOffice? [url=http://puppylinux.info/topic/freeoffice-2012-sfs]Get the sfs (English only)[/url].
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
I thought the blog was a good idea and created one here
http://puppysaluki.posterous.com/
Stripe and 8bit as you are founder testers send me a PM (personal message) with an email address and you can join the blog posters
or try out the comments section . . .
Hope that is a good idea
We is Saluki
We has Blog and wiki
http://puppysaluki.posterous.com/
Stripe and 8bit as you are founder testers send me a PM (personal message) with an email address and you can join the blog posters
or try out the comments section . . .
Hope that is a good idea
We is Saluki
We has Blog and wiki
My intention is not to replace existing services. I am not planning for it to be a Wiki even.
The idea is to create a collaboration platform for the contributers. The only people that would necessarily use it are me, Technosaurus, Big_Bass, Ttuuxxx, and anyone else that wants to contribute. When the project is over, the site would be decommissioned. (So I guess it's you guys' opinion I actually want).
The major reason not to use a hosted solution, like google code, is flexibility. I can probably make something more user friendly and useful. Features could be added as we need them. All the developers can have full administrative access.
The point of picking Tiki, would be that all of this could be done without writing any code.
Even if it ends up that I am the only content contributor, I'd probably still create something like this for my own book keeping. 200 page forum threads are not exactly an ideal way to organize information.
The idea is to create a collaboration platform for the contributers. The only people that would necessarily use it are me, Technosaurus, Big_Bass, Ttuuxxx, and anyone else that wants to contribute. When the project is over, the site would be decommissioned. (So I guess it's you guys' opinion I actually want).
The major reason not to use a hosted solution, like google code, is flexibility. I can probably make something more user friendly and useful. Features could be added as we need them. All the developers can have full administrative access.
The point of picking Tiki, would be that all of this could be done without writing any code.
Even if it ends up that I am the only content contributor, I'd probably still create something like this for my own book keeping. 200 page forum threads are not exactly an ideal way to organize information.
Collaboration
Even though I am not on your team, just a note that "may" reduce your workload consideratbly.
I have used Google for collaboration projects over the past 3 years. I have found it to be an excellent method for a "closed" project team. Nothing to invent or maintain, and simply works to the team's advantage.
Of course, Lotus Notes is the premire for projects as well. And contains everything any project can imagine.
Google Docs, is by far, the most advanced of public tools for it has some extensive privacy protection built in.
So that you can focus on your project and not on your tool(s) or its maintenance in collaboration is the ONLY reason I'm suggesting this to you.
I have no aspirations, I am not a trumpeter of Google, and I only mention this to help. If it helps, use it.
I have used Google for collaboration projects over the past 3 years. I have found it to be an excellent method for a "closed" project team. Nothing to invent or maintain, and simply works to the team's advantage.
Of course, Lotus Notes is the premire for projects as well. And contains everything any project can imagine.
Google Docs, is by far, the most advanced of public tools for it has some extensive privacy protection built in.
So that you can focus on your project and not on your tool(s) or its maintenance in collaboration is the ONLY reason I'm suggesting this to you.
I have no aspirations, I am not a trumpeter of Google, and I only mention this to help. If it helps, use it.
I've seen some gui's posted that do that, but using "adduser" is simple. I posted a build script for sudo-1.7.4 in utilities.chrismt wrote:I wish Puppy 6 will have multiple users account support so that it will become a widely accepted linux distro for anyone like what Ubuntu is now.
http://murga-linux.com/puppy/viewtopic.php?t=60258