Puppy Community Register
-
- Posts: 36
- Joined: Fri 09 May 2008, 19:03
Marblemike - Level 2 I guess.
I'm relatively new to puppy (I've been convinced by my short stay), did the puppy unleashed thing to make a puplet for use in an embedded system, have never made a pet or sfs file, but figure that since I can program in C, pascal, delphi, basic, a little assembler, a little C++, Matlab / Octave and just lately VHDL - I deserve a 2. I mainly do hardware though, and when I develop its generally for external hardware like DSP's and micro's.
I'm relatively new to puppy (I've been convinced by my short stay), did the puppy unleashed thing to make a puplet for use in an embedded system, have never made a pet or sfs file, but figure that since I can program in C, pascal, delphi, basic, a little assembler, a little C++, Matlab / Octave and just lately VHDL - I deserve a 2. I mainly do hardware though, and when I develop its generally for external hardware like DSP's and micro's.
Hi interesting concept in self awareness
In puppy terms I'd like to be a zero, since my knowledge of anything codified is aaaarrrrggghhhh
.....but I do pull PCs to pieces quite often, been a puppy forum user more than a puppy user, due to the remaining w2k os, and I do a fair amount of research, trying to help similar uninformed individuals, as I'm a bit of a ferret
You'll find me splattered all over the forums, I think, as a result
No point putting my irc up here, I don't use it often enough - pm me
Aitch
In puppy terms I'd like to be a zero, since my knowledge of anything codified is aaaarrrrggghhhh
.....but I do pull PCs to pieces quite often, been a puppy forum user more than a puppy user, due to the remaining w2k os, and I do a fair amount of research, trying to help similar uninformed individuals, as I'm a bit of a ferret
You'll find me splattered all over the forums, I think, as a result
No point putting my irc up here, I don't use it often enough - pm me
Aitch
- Attachments
-
- calm.gif
- (54.83 KiB) Downloaded 1748 times
-
- Posts: 355
- Joined: Tue 19 Aug 2008, 21:12
- Location: Los Angeles, CA.
- Contact:
Puppy Community Register
I'm an avid puppy user and spread as much puppy (puplets/derivative) around via torrents as possible. (linuxtracker.org/tuxdistro.com and mininova.org)
I also build computers from used and new parts for family use.
A level 1 seems to fit well.
I also build computers from used and new parts for family use.
A level 1 seems to fit well.
see level 3 guys
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
Puppy user since Oct 2004. Want FreeOffice? [url=http://puppylinux.info/topic/freeoffice-2012-sfs]Get the sfs (English only)[/url].
- Béèm
- Posts: 11763
- Joined: Wed 22 Nov 2006, 00:47
- Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
Aitch, is this one of your repair methods also?
- Attachments
-
- fix pc.gif
- (14 KiB) Downloaded 2356 times
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
- Béèm
- Posts: 11763
- Joined: Wed 22 Nov 2006, 00:47
- Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
And in case you want to rebuild, this is an example of computer technology.
- Attachments
-
- computer.gif
- (14.63 KiB) Downloaded 1362 times
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
2+
Some scripting (pwget and prototype for psip)
Trying to learn Genie
http://www.murga-linux.com/puppy/viewto ... 314#283314
Some scripting (pwget and prototype for psip)
Trying to learn Genie
http://www.murga-linux.com/puppy/viewto ... 314#283314
Last edited by Lobster on Sun 03 May 2009, 05:40, edited 2 times in total.
- darrelljon
- Posts: 551
- Joined: Sun 08 Apr 2007, 11:10
- Contact:
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!
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!
John Hechtman / www.zenarrow.com / jhecht@ix.netcom.com
"Computer help in NYC" / 917 628 0192 - cell / 212 586 4633 - landline
"Computer help in NYC" / 917 628 0192 - cell / 212 586 4633 - landline
- mysticmarks
- Posts: 159
- Joined: Tue 27 Feb 2007, 01:56
- Location: California
- Contact:
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.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!
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.
- ttuuxxx
- Posts: 11171
- Joined: Sat 05 May 2007, 10:00
- Location: Ontario Canada,Sydney Australia
- Contact:
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?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!
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
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)