Droopy first appeared in the MGM cartoon Dumb-Hounded, released by MGM on March 20, 1943 which is considered one of Avery's best works by animation scholars. Droopy's first scene is when he saunters into view, looks at the audience, and declares "hello all you happy people...you know what? I'm the hero."

Before I have heard about Puppy I was a SLAX fan, why? because it was live & modular, and with .mo modules it was easy to customize and experiment different softwares.When I descovered puppy , became my favourite distro, never went back to SLAX.I think is very good that puppy will become Slackware compatible. Even Vector linux returns to gslapt to catch precompiled binaries. So I suppose That new puppy will be very flexible in getting pet/pup and tgz(slackware) binaries, I hope it will include the posibility on mounting .mo (SLAX) sfs files too (by ROX & Boot Manager). For an experimented user is straitforward to get and compile software from source package, sometimes in smaller softwares with few dependencies it works for me too, but I had to admit I prefer to get it in working precompiled binaries, so extending pupy to be slackware binary compatible is wonderful.Even more easy for an newbie is workink with .sfs (puppy) and .mo (SLAX) modules! Is like working with 'bricks' : you copied it and is ready for testing, if it fit your need you keep it, if not you drop it (simply delete it).This is an wonderful philosophy.It worth to be extended.Frugal install on HDD is prefered against normal install for this too.The price for these flexibility (mounting more than 3 sfs modules) is performance /speed & memory, so puppy limit it for 3 modules, and SLAX doesn't limit it (I presume it can mount up to 255 modules...).An compromise solution could be to raise the limit of 3 to say 7-9 sfs modules in BOOT MAnager & issue-ing an warning of performance drop for using more than 3 modules in daily use, encouraging users to use more .sfs & .mo modules only for testing purpose, and after that better pack this extra modules in one custom sfs file for daily use.The idea is to move custom software packages instaled (with compilation from source, or binaries PUP/PET or tgz ) from inside puppy.2fs in an separate custom_only_software.sfs file.In these way puppy.2fs will remain an container for personal work, data ,PC setup information only, and stable personal custom used software will be an separete module like devx.sfs or open office.sfs.These philosophy should encourage users instead of creating different puplet distros , to better make custom.sfs modules that work with base puppy and behave like their distro.It also could be an reasonable solution for discussion about puppy size: is too big 100mbyte or not! Puppy could be split in 2 files (2 stage puppy) :
An basic puppy file with small size that run seamlessly in old hardware in memory, and extended (second) puppy file with all application of standard puppy not fitting in the basic file.
...sorry if I was too long...

It wasn't too long, but it does help if you break things up into shorter chunks. Otherwise, when my eyes get to the end of a line and they do a "carriage return", I have trouble finding the correct line to start reading from again._________________Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

Sounds great that 2.20 is coming out. Will be interesting to see what it is like. Sounds like some new thinking and ideas. Thank goodness AU is ahead of on the time line so "Tomorrow" will be here quicker for the rest of us.
Rambling thoughts:
Could of called it "high voltage" since it reminds me of 220 volts. Would be cool to hear Droopy say something like "hello folks" instead of the familiar "bark bark" when it opens the first time. Also "Happy Feet" makes me think of Linux penguins._________________Penguin, the OTHER white meat.

This booted OK but failed to load any modules in the zdrv file. There were entries in bootsysinit.log for
loading ipw2200
loading eepro

but lsmod showed that they had not been loaded and I trying to load them manually failed with "not found" I think.

There was no entry in /etc/rc.d/PUPSTATE for zdrv, I presume this is the caused of the failed module loading.

After creating a pup_save and rebooting the modules were loaded automatically

On a minor note Atol failed to launch a terminal even though the settings showed rxvt as the program that should be invoked.

Be aware that the routine that searches for a pup_save is now more thorough and asks less questions(than 2.16 at least). It found my only pup_save on another partition and booted using it without asking me. If you have 2 you get a choice._________________Will
contribute: community website, screenshots, puplets, wiki, rssLast edited by HairyWill on Mon 03 Sep 2007, 14:14; edited 2 times in total

Loaded "puppy pfix=ram" and os came up. I have an Epia ml6000eag (VIA) motherboard w/512mb ram. The os did not recognize my sound or network eth0 and eth1. Tried to load zd1211rw and wouldn't load. Tried to load ndiswrapper for the windows drivers and would not load. Tried the new ICW pet and it failed also. Exited without saving.

The previous versions 2.14-2.17.1 work without any problems. Also, when I went back to using 2.17.1 it would not network properly and after about 25 minutes of trying different ways to get the network working failed, I had to reload 2.17.1

First off, it really does boot slow. Second, it will not recognize either the built-in ethernet or my wireless PC card. I could not manually load the drivers either. The drivers in question are the eepro100 and the orinoco_cs driver. Since I only brought my laptop with me to the dorm, I have no other computer upon which to test. I really wanted to try out the new SeaMonkey. The lack of spell-check was really my main complaint against the old versions.

This problem existed for the orinoco_cs driver in some older versions, and I would fix it by installing it from a DotPup. I hope this is fixed before the final release because I don't want to go back to that.

If I read Barry's blog correctly, 2.20 is reverting to the old kernel. Since that is the kernel for the Puppy versions with which the orinoco driver had this problem before, I wonder if the kernel is to blame. Then again, the eeepro driver never had a problem with the old kernel, so maybe it is something else._________________Be brave that God may help thee, speak the truth even if it leads to death, and safeguard the helpless. - A knight's oathLast edited by SirDuncan on Mon 03 Sep 2007, 17:37; edited 1 time in total

If I read Barry's blog correctly, 2.20 is reverting to the old kernel. Since that is the kernel for the Puppy versions with which the orinoco driver had this problem before, I wonder if the kernel is to blame. Then again, the eeepro driver never had a problem with the old kernel, so maybe it is something else.

No, the 2.20alpha has the latest, 2.6.21.5 kernel. I have a future plan to *also* release a 2.20 with the older kernel.

First off, it really does boot slow. Second, it will not recognize either the built-in ethernet or my wireless PC card.

Tried it on my Dell Dimension:

A. Did not detect my network card 2.17.1 did
B. Did not offer a usb printer option 2.17.1 did
C. Did not detect my sound card 2.17.1 did
D. Did not find any legacy sound drivers (did't need to with 2.17.1)
E. Could not use vmware to create appliance as worked with 2.17.1

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum