READ-ONLY Archive
https://oldforum.puppylinux.com/
I think the way to do it rather than as part of the intial iso is to do a science/math service pack for puppylinux.greengeek wrote:Yikes!! This link says the iso is 2GB ! Surely there can't be a puppy fat enough to run that can there??TyroBGinner wrote:I am requesting the current version of TeX, but certainly no one should break their neck trying to provide it - the TeX Live iso serves its purpose pretty well.
I like this approach too, having an almost empty menu and then populating it with whatever you need/want from PPM after.nic007 wrote:I think a standard barebones puppy (32 and 64 bit) should be issued with necessary drivers, networking, printing intact. Then we need a dedicated repository for applications ie. Pets, sfs's, etc. which will all work with this standard issue (the necessary libs included). This will make things easier and give the user freedom of choice.
why hasnt anyone made a pup yet specifically for running woof-ce?Sailor Enceladus wrote:I like this approach too
Mike Walsh just posted re a similar program here:Rattlehead wrote:. What F.lux and other programs of its kind do (and the physical screen filters too), is eliminating the blue light component from the light beam.
To add to this approach, users should be encouraged to rather use sfs-addons instead of installing stuff and/or doing remasters which is unnecessary. Keep it simple.Sailor Enceladus wrote:I like this approach too, having an almost empty menu and then populating it with whatever you need/want from PPM after.nic007 wrote:I think a standard barebones puppy (32 and 64 bit) should be issued with necessary drivers, networking, printing intact. Then we need a dedicated repository for applications ie. Pets, sfs's, etc. which will all work with this standard issue (the necessary libs included). This will make things easier and give the user freedom of choice.
I think that in most cases SFS are preferable. However, I have noticed that when you are using large amounts of ram, sfs might get pushed partly into the swap partition. As a consequence, perhaps it makes sence to have for instance one browser installed as a pet, and have the rest as sfs files which can be easily unloaded or re-loaded if needed.nic007 wrote:To add to this approach, users should be encouraged to rather use sfs-addons instead of installing stuff and/or doing remasters which is unnecessary. Keep it simple.Sailor Enceladus wrote:I like this approach too, having an almost empty menu and then populating it with whatever you need/want from PPM after.nic007 wrote:I think a standard barebones puppy (32 and 64 bit) should be issued with necessary drivers, networking, printing intact. Then we need a dedicated repository for applications ie. Pets, sfs's, etc. which will all work with this standard issue (the necessary libs included). This will make things easier and give the user freedom of choice.
If you have lots of RAM you do not need a swap partition or a swap file. Generally, sfs's are not loaded into RAM but when you use the application part of it will reside in RAM or swap . If you add SFS's to a zdrv, it will load fully into RAM if you have enough RAM.s243a wrote:I think that in most cases SFS are preferable. However, I have noticed that when you are using large amounts of ram, sfs might get pushed partly into the swap partition. As a consequence, perhaps it makes sence to have for instance one browser installed as a pet, and have the rest as sfs files which can be easily unloaded or re-loaded if needed.nic007 wrote:To add to this approach, users should be encouraged to rather use sfs-addons instead of installing stuff and/or doing remasters which is unnecessary. Keep it simple.Sailor Enceladus wrote: I like this approach too, having an almost empty menu and then populating it with whatever you need/want from PPM after.
Interesting idea. Where does it create it?rufwoof wrote:Detect when memory is getting low (as per Fred's script) and ...
dd if=/dev/zero of=swapfile bs=1024k count=1024
mkswap swapfile
swapon swapfile
type thing (that creates and activates a 1GB swapfile)
In that example ... in the current directorygreengeek wrote:Interesting idea. Where does it create it?rufwoof wrote:Detect when memory is getting low (as per Fred's script) and ...
dd if=/dev/zero of=swapfile bs=1024k count=1024
mkswap swapfile
swapon swapfile
type thing (that creates and activates a 1GB swapfile)
Code: Select all
cd
mkdir -p sda2
mount /dev/sda2 sda2
cd sda2
if [ ! -f swapfile ]; then
dd if=/dev/zero of=swapfile bs=1024k count=1024
mkswap swapfile
swapon swapfile
filearnhow2code wrote:why hasnt anyone made a pup yet specifically for running woof-ce?Sailor Enceladus wrote:I like this approach too
Code: Select all
"To keep the suicide rate low among developers."
If you think the above is the right answer, hit Enter now.
If you think the right answer should be:
"To keep the hair-pulling rate low among developers",
type any printable key and press Enter.a couple suggestions:rufwoof wrote:Detect when memory is getting low (as per Fred's script) and ...
dd if=/dev/zero of=swapfile bs=1024k count=1024
mkswap swapfile
swapon swapfile
Do you mean making pie from scratch or buying ready-made cooked pie? I can't even make Kraft Dinner!musher0 wrote:Simple as pie.
Poor thing! You must be just skin and bones, eh?!Sailor Enceladus wrote:Do you mean making pie from scratch or buying ready-made cooked pie? I can't even make Kraft Dinner!musher0 wrote:Simple as pie.
Thanks Flash - I hadn't seen mushers tree thread so i have now added that to my watchlist. If we are lucky don570 may come up with a rightclick menu for tree (if not already incorporated in one of his rightclick menus...).Flash wrote:I'd like to see tree incorporated into ROX-filer's right-click menu. At least, how about a .pet that does that?