(old)Puppy Linux Discussion Forum

There is a T2 discussion recently started by Barry, so you will find all true developers there (level 3 up): http://murga-linux.com/puppy/viewtopic.php?t=32972

Aitch, is this one of your repair methods also?

Thanks Béèm

It is now, .... mmm, much better

Aitch

And in case you want to rebuild, this is an example of computer technology.

@Beem

Lol, if you loaded up Windows on that system, you'd certainly need the plunger aka "debugger" due to the bloatware!

level 1 to level 2
still impressed of puppy's power and use puppy as a one aond only os on my computer

2+
Some scripting (pwget and prototype for psip)

Trying to learn Genie
http://www.murga-linux.com/puppy/viewto ... 314#283314

Level 1
Wannabe Level 2/3

Level 1
new to linux & love with Puppy Linux

I am "out here".

Best wishes to you all. I'll spout off when I feel I can help a bit or relate.

Most likely I could be listed as a "tester" at least.

Hi

Puppy n00bie - but very enthusiastic and willing to learn

Most appropriate for me is probably - Level 1 - low level

Happy to help anyway I can.

best regards - Ray

John Hechtman - contact through forum, or direct email.

I'd call myself sort of a level 2. I've used Puppy for a long time, along with other Linux distros. I'm a pro computer tech by trade, and service both Windows and Macintosh 'puters.

Not a programmer, not a developer, but what I AM is a very skilled technical writer. Just had a book published on wiring audio recording studios. Check out: http://www.amazon.com/Audio-Wiring-Guid ... 0240520068

So I'd like to volunteer to help with documentation. One of the biggest stumbling blocks for all the Linux distros I've worked with (maybe 12-15) is that they either have almost no documentation, or really scanty documentation, or else the docs presuppose a level of knowledge and expertise that may/may not exist in a new - or even intermediate - end user.

I'd like to make the following a steadfast rule for all Puppy documentation; when you describe a process, ALWAYS give EVERY step! Every single mother-lovin' one of them, no matter how obvious, or self-evident you think they are. What is self-evident to YOU may NOT be to the next person to read the docs...

If you don't want to spell out a procedure in your docs, you MUST provide a link to it, so someone who does not know that step can find the missing puzzle piece, and then come back to your docs quickly...

If everyone who works on Puppy documentation abides by this simple, logical rule Puppy documentation will very soon outshine the docs for almost any other available distro!

I cam be reached at jhecht@ix.netcom.com

Thanks!

jhecht wrote:John Hechtman - contact through forum, or direct email.

I'd like to make the following a steadfast rule for all Puppy documentation; when you describe a process, ALWAYS give EVERY step! Every single mother-lovin' one of them, no matter how obvious, or self-evident you think they are. What is self-evident to YOU may NOT be to the next person to read the docs...

If you don't want to spell out a procedure in your docs, you MUST provide a link to it, so someone who does not know that step can find the missing puzzle piece, and then come back to your docs quickly...

If everyone who works on Puppy documentation abides by this simple, logical rule Puppy documentation will very soon outshine the docs for almost any other available distro!

Thanks!

Excellent. If you're serious, The Wiki would be an excellent contribution to this project as it stands at the moment. It needs refinement for your reasoning reguarding new users.

I would also like to know if you would be able to correlate with a level 3 to produce a cloud diagram of the squash file system overlay of puppy with links to the updated wiki [which of course you having redesigned sorted/created the appropriate documentation for. ].

Ideally, a new start page for puppy that will be an attractive/interactive diagram of a layered union file system and linked to man pages essentially providing lesson 1 for the new user, and allowing them access to level 2 very quickly. This is essential in maintaining a user base.

It would be a big undertaking, but would correct some long standing side work that has become a stone in the shoe.

Excellent post mystic

jhecht wrote:John Hechtman - contact through forum, or direct email.

I'd call myself sort of a level 2. I've used Puppy for a long time, along with other Linux distros. I'm a pro computer tech by trade, and service both Windows and Macintosh 'puters.

Not a programmer, not a developer, but what I AM is a very skilled technical writer. Just had a book published on wiring audio recording studios. Check out: http://www.amazon.com/Audio-Wiring-Guid ... 0240520068

So I'd like to volunteer to help with documentation. One of the biggest stumbling blocks for all the Linux distros I've worked with (maybe 12-15) is that they either have almost no documentation, or really scanty documentation, or else the docs presuppose a level of knowledge and expertise that may/may not exist in a new - or even intermediate - end user.

I'd like to make the following a steadfast rule for all Puppy documentation; when you describe a process, ALWAYS give EVERY step! Every single mother-lovin' one of them, no matter how obvious, or self-evident you think they are. What is self-evident to YOU may NOT be to the next person to read the docs...

If you don't want to spell out a procedure in your docs, you MUST provide a link to it, so someone who does not know that step can find the missing puzzle piece, and then come back to your docs quickly...

If everyone who works on Puppy documentation abides by this simple, logical rule Puppy documentation will very soon outshine the docs for almost any other available distro!

I cam be reached at jhecht@ix.netcom.com

Thanks!

or another idea is,,, Muggins posted a little program that can record your screen as you do things, If someone would say record how to make a pet package, you could translate that video into text format, and maybe pause it and take screen shots and then we'll have a real nice documentation. How does that sound?
Not really implying that it has to be you, just an idea, to simplify things, some people have problems putting actions into words, Ever see the movie "Lost in Translation?" great movie
ttuuxxx

[/quote]
or another idea is,,, Muggins posted a little program that can record your screen as you do things, If someone would say record how to make a pet package, you could translate that video into text format, and maybe pause it and take screen shots and then we'll have a real nice documentation. How does that sound?
ttuuxxx[/quote]

This is actually a part of the whole process I was speaking of. Links would bring you to those explainations and videos based off of the main page. I totally agree. However, I would note that this would require additional work by the Level 3, as he/she would be doing all of the video of his/her work. BUT, we could use a new volunteer to do post video editing and isolation of screenshots for use. So we need a video pro.

Now would be an excellent time for input and volunteers. If we have the people then you (jhecht) should pm those people and start a new thread that will begin the process.

We are all leaders AND followers. Lets keep the ball rolling folks!

mysticmarks wrote:

jhecht wrote:John Hechtman - contact through forum, or direct email.

I'd like to make the following a steadfast rule for all Puppy documentation; when you describe a process, ALWAYS give EVERY step! Every single mother-lovin' one of them, no matter how obvious, or self-evident you think they are. What is self-evident to YOU may NOT be to the next person to read the docs...

If you don't want to spell out a procedure in your docs, you MUST provide a link to it, so someone who does not know that step can find the missing puzzle piece, and then come back to your docs quickly...

If everyone who works on Puppy documentation abides by this simple, logical rule Puppy documentation will very soon outshine the docs for almost any other available distro!

Thanks!

Excellent. If you're serious, The Wiki would be an excellent contribution to this project as it stands at the moment. It needs refinement for your reasoning reguarding new users.

I would also like to know if you would be able to correlate with a level 3 to produce a cloud diagram of the squash file system overlay of puppy with links to the updated wiki [which of course you having redesigned sorted/created the appropriate documentation for. ].

Ideally, a new start page for puppy that will be an attractive/interactive diagram of a layered union file system and linked to man pages essentially providing lesson 1 for the new user, and allowing them access to level 2 very quickly. This is essential in maintaining a user base.

It would be a big undertaking, but would correct some long standing side work that has become a stone in the shoe.

MM - it's a lovely idea, but I fear you are asking me to commit to more time than I can give - and also more expertise - I have never edited a Wiki...

What I was thinking about was more along the lines of a book, or series of articles about using Puppy. I am appending a how-to I wrote to this post, about creating a dual-booting Puppy/Win XP 'puter, and a second how-to, about restoring the GUI, if your Puppy drops to commandline.

There are some issues here that need to be addressed. The Puppy Documentation Project has a lot of good info - including some of my contributions.

But procedures vary according to what vintage Puppy you're working with, and there are often good reasons for choosing an older build over the latest one. For example, when installing Puppy on older computers. I've found v2.15 CE to be more compatible with older hardware than newer builds - likely due to the older kernel.

The PDP is not currently (AFAIK) set up to reference docs by build number. So I propose that the info in the PDP be categorized by build. That way when you look at a doc, you know what version of Puppy it was written for. This is a pretty simple task, and would GREATLY enhance the usability of the existing documentation.

That said, my own idea was sort of "The Puppy Book" - and I would gladly interface with a level 3 Puppian, or Lucifer himself to do it (grin).

Here's a rough idea of possible chapters/contents. Add/remove/slice/dice, and cook 'til done.

*What is/why use Puppy?
*Using Puppy as a live CD, including write back to CD in multisession
*Installing Puppy as a standalone OS to older computers
*Installing Puppy as a standalone OS to newer computers
*Installing Puppy as a dual booting OS to older computers
*Installing Puppy as a dual booting OS to newer computers
*Installing Puppy to other media - e.g. flash drives
*Using Puppy 1 - how to navigate in Puppy and configure connections
*Using Puppy 2 - how to set up printers & other peripherals (i-Pods)
*Using Puppy 3 - networking with other computers
*Using Puppy 4 - adding programs and remastering Puppy

This list is by no means complete, but it would be a darn good start if such a compilation was made. If it was structured as a book, rather than a Wiki, it might be salable - which could benefit both the authors AND the Puppy Linux Foundation/Barry Kauler. I, for one, would gladly tithe a generous portion of any profits I made to ensure the continuation of Puppy after Barry 'retires'...

ttuuxxx wrote: or another idea is,,, Muggins posted a little program that can record your screen as you do things, If someone would say record how to make a pet package, you could translate that video into text format, and maybe pause it and take screen shots and then we'll have a real nice documentation. How does that sound?
Not really implying that it has to be you, just an idea, to simplify things, some people have problems putting actions into words, Ever see the movie "Lost in Translation?" great movie
ttuuxxx

Would you please provide a link for the program Muggins uploaded? It sounds very useful!

And with no disrespect, ttuuxxx, this is exactly the mindset I'm trying to change - if you post about the fact that there's a cool program, that does xyz, you need to put a link for that program in the original posting!

This makes it easy for readers to find it, and spares you annoying comments like mine (grin). I don't want a movie review, I want the cool proggie, and I want it now. It's a way of thinking...

jhecht

John, 1st I support your comment to ttuuxxx about the links, so also have to admit not being so supportive of your links in your posts, which I feel are a bit spammy for a forum
However, I know you are trying to grow you're business, I just feel there are better ways, OK
Link here:-
http://www.murga-linux.com/puppy/viewtopic.php?t=33674

As you will see, you got some support

I've sent you a pm with some ideas re this, HTH

Aitch

Aitch wrote:jhecht

John, 1st I support your comment to ttuuxxx about the links, so also have to admit not being so supportive of your links in your posts, which I feel are a bit spammy for a forum
However, I know you are trying to grow you're business, I just feel there are better ways, OK
Link here:-
http://www.murga-linux.com/puppy/viewtopic.php?t=33674

As you will see, you got some support

I've sent you a pm with some ideas re this, HTH

Aitch

Aitch - please read my reply at:
http://www.murga-linux.com/puppy/viewto ... 557#235557

I got your PM - thanks! I'll check out your suggestions as time permits.

Regarding my links - I assume you mean the ones in my signature? There's my main email and website - I think those are very plain vanilla.

Then there's my description of what I do, and my service phone number. They are there to inform people that I am available to help them, and provide a quick means to contact me.

FWIW, I have been using the same Sig here for years, and you are the only one who has ever questioned it - and that includes the forum moderators...

I judge signatures by the size/length, as well as content. Mine is designed to let people know who I am, what I do, and how to reach me in the smallest amount of space - thus not clogging up the forum with trivia.

Look at cb88's signature - which takes up far more space then mine - yet you don't object to his... If you like, I could lay it out horizontally rather than vertically. Would that be better for you?