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.
Puppy - Which programs do you need/want?
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.
-
- Posts: 1543
- Joined: Mon 22 Feb 2016, 19:43
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.
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.
http://www.murga-linux.com/puppy/viewto ... 322#919322
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.
Fred has a couple of features in DebianDog64 to extend the amount of ram allocated to changes being recorded in memory space, and to flag up (pop up message) when that memory is getting low. A nice extension to that would be to allocate swap file space ... somewhat dynamically. Most of the time swap might be idle/unused, but comes in handy to keep the system running when heavily loaded, such as video rendering in memory space.
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)
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)
I was just showing a example. My sda2 is a large ext3 format that I store data on so if I intend to render a largish video or whatever intensive activity, as more usually I don't have a swap partition/file active I usually create/activate a swapfile in the root of that sda2 partition before doing that activity. Something like :
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
fi
learnhow2code 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.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
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
1. i think puppy already automounts swap on boot. i think thats fine, that probably saves more trouble than it causes. its a very puppy-like thing to do.
2. if the user has a partition mounted rw with 1g free, go ahead and create the swapfile.
3. if the user does not have a partition mounted rw with 1g free, popup a window and offer a choice of partitions to create a file on-- include the options:
* no, i will take my chances with low ram
* i dont know, just pick whatever is best
automounting a unmounted partition to create a new swapfile seems like a good way to cause trouble. consider that the pupsave isnt created without a prompt, and follow that example.
About the swap file:
-- older Puppies created a 256 Mb swap file on first boot if neither swap
partition nor swap file were detected on the disk. Maybe do a test with
newish Puppies to confirm or infirm that.
If the new Puppies still do it, then we don't need to waste any energy!
Flash has kindly made sticky my set of ready-made swap files
and pup-save files here. Basically, choose the size of
your swap file, download it, unzip it and use.
Simple as pie.
Rule of thumb:
-- if you have over 2 Gb's of RAM, 500 Mb of swap file is enough.
-- if you have less, get the file with +/- 2.5 times your amount of RAM.
Final consideration -- A swap file is always a stop-gap measure. It will
prevent your computer from freezing if all your RAM gets filled up, but
using it always seriously s-s-l-l-o-o-w-w-s-s down your machine.
To minimize the possibility of this slow down -- and of resorting to using
the swap file in the first place--, if you know program X is a RAM guzzler,
quit from all other programs before you run program X. (And keep your
fingers crossed!)
BFN.
-- older Puppies created a 256 Mb swap file on first boot if neither swap
partition nor swap file were detected on the disk. Maybe do a test with
newish Puppies to confirm or infirm that.
If the new Puppies still do it, then we don't need to waste any energy!
Flash has kindly made sticky my set of ready-made swap files
and pup-save files here. Basically, choose the size of
your swap file, download it, unzip it and use.
Simple as pie.
Rule of thumb:
-- if you have over 2 Gb's of RAM, 500 Mb of swap file is enough.
-- if you have less, get the file with +/- 2.5 times your amount of RAM.
Final consideration -- A swap file is always a stop-gap measure. It will
prevent your computer from freezing if all your RAM gets filled up, but
using it always seriously s-s-l-l-o-o-w-w-s-s down your machine.
To minimize the possibility of this slow down -- and of resorting to using
the swap file in the first place--, if you know program X is a RAM guzzler,
quit from all other programs before you run program X. (And keep your
fingers crossed!)
BFN.
Last edited by musher0 on Fri 26 Aug 2016, 21:52, edited 1 time in total.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
-
- Posts: 1543
- Joined: Mon 22 Feb 2016, 19:43
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.
I mean: simple as eating a piece of already cooked blueberry or apple or
cherry or lemon or meringue pie, put on the table in front of you by a
friendly waitress in a lovely little china plate decorated with some flowery
pattern, with a fork.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
video playing and management of collections.
Puppy has too much choice in some sections (graphics) and not enough in others (video playing and management of collections). It's a pity some Puppies have to use again Gxine to be able to play DVDs.
These apps are no longer tested before release. As users (thousands still use their computers to play CDs or DVDs, mostly children before going to bed).
CD burning is used by our colleagues, even by famous Puppy makers.
With Mistfire, we hardly found an application able to play DVDs..
These apps are no longer tested before release. As users (thousands still use their computers to play CDs or DVDs, mostly children before going to bed).
CD burning is used by our colleagues, even by famous Puppy makers.
With Mistfire, we hardly found an application able to play DVDs..
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?
What version of Puppy would you be wanting a pet for?