Greyhound is a Puppy derivative (or puplet) but there is nothing to download--nothing except the information on this page. Information has a much smaller bandwidth than an ISO. What I mean is that these are the instructions to turn a regular Puppy into a Greyhound. They are easy to try and they are easy to undo if you don't like them.
I have always admired BarryK's decision to make Puppy a single-user operating system that ran as root. I am sure he took some grief for that, as many of us probably have, because that violates a rule of Linux Orthodoxy; that Linux is a multi-user operating system. But, gee-whiz, what does my ancient p3 need with a multi-user OS. I would rather have the simplcity and convenience of running as root. So, all I have done in training my Greyhound is to ask some more questions about what is really necessary and what is not--because by eliminating what is not necessary I can get a return in quickness and speed.
Here are the Instructions. I hope you will read the explanation below if you don't already know each of these programs. Start Pprocess (Menu: System: Pprocess) and Kill whichever of these processes you choose. I kill them all. If you don't like the result, just reboot and you are back to normal with no harm done (on the basis of my knowledge and testing--don't do anything you are not comfortable with).
Code: Select all
/sbin/udevd -daemon
syslog m -0
klogd
/bin/sh /sbin/pup_event_frontend_d
absvolume -bg #DCDAD5
xload -nolable -bg #888888 -fg red -hl white
freememapplet
asapm - 4
blinky-bg #DCDAD5
/usr/bin/inotifywait -e modify --format % /tmp/pup_e
Explanation.
First, I don't think the logs are necessary. I test programs and try to adapt them to Puppy and I almost never use the logs; in day to day usage, I never need them. If I need them I can turn them back on. Surely a server or a corporate network need the logs; I don't.
Similarly, I don't need xload, blinky, freememapplet, the battery monitor, or the volume control ( the volume control is a close call, but I can start it easily from the menu). If or when I need any of these they are easy to start, but 99% of the time I would rather have the memory and cpu cycles they take up. I do want the clock, but someone else might not.
Finally, the tough one. I have been watching BarryK's progress in creating a leaner, faster subsitute for hal and dbus. Once upon a time aI had made a lean and quick Arch linux system and then I put dbus and hal (which basically automount things as far as I can see). It was a noticable and shocking slowdown! I haven't liked them since or seen any need for them. But they are a superstitition; some programs won't even start without them though they don't really need them. So I was happy to see Barry try to replace them. But I realize now that I don't really need his pup_event system either. I can start Pmount whenever I need to mount something and it even thoughtfully opens a rox window after mounting. I can easily see that some people might be more comfortable with automounting in a transition from Windows.
I must say that I have tried and enjoyed numerous puplets but I do not remember any of them being quicker and more responsive than BarryK's original--he sets a high standard. The puplets add different personalities to Puppy, which is great fun because Puppy is such a wonderful basis for customization. Perhaps some of the other puplets could add some greyhound training too
Extra. You can download the Greyhound (which my wife and daughter insist is a Whippet) and make it your wallpaper by putting it into /usr/share/backgrounds and running Menu: Desktop: Wallpaper Setter.
http://www.diddywahdiddy.net/Puppy400/silver.jpg
If you want to make Greyhound permanent, then the xload, freememapplet, asapm, blinky, (and clock) are in .jwmrc-tray in your home /root) folder--just comment them out with a # at the beginning of each line.
pup_event_frontend_d and absvolume are in /root/.xinitrc and I comment them out the same way.
udevd, klogd, and syslog are somewhere you can find but I don't think udevd should be commented out--it has to run for hardware detection, but it can be stopped once X and your window manager are running. I write a little script named greyhound.sh that I put into /root/startup--so it runs when jwm starts--don't forget to change the permissions with Rox Right-Click on greyhound.sh Permissions
killall -9 klogd
killall -9 syslogd
killall -9 udevd
Finally--will anyone really read this far I personally would be appreciative if instead of making pets for me, people would sometimes write instructions. Don't get me wrong, I appreciate the pets, but I would also like to know how to do it myself. Thank you.