Page 18 of 20
Posted: Sun 22 Nov 2015, 21:32
by B.K. Johnson
grr_argh wrote:
Replace Seamonkey as the default browser with either Firedog or Chromium. I understand the desire to keep the Seamonkey suite as it offers a lot of applications in a compact size, but there are better alternatives out there
I use Seamonkey and Firefox. You give the benefits as
a lot of applications in a compact size. You advocate Firedog or Chromium (neither of which I have used) but you give no reasons for your advocacy of them or name the "
better alternatives out there". I've got an open mind; convince me to at least try one, both or anything else. While doing so, factor in the additional "weight" for an HTML editor to replace Composer in seamonkey. You know puppy's virtue of size, don't you?
Posted: Sun 22 Nov 2015, 22:39
by 6502coder
grr_argh wrote:* Same with the text editors (four of them!).
WYSIWYG document prep, programming, and writing are three completely different tasks, so having at least three different kinds of "text editors" is justified.
Posted: Sun 29 Nov 2015, 00:55
by eric52
I know it's old-fashioned, but I still use Puppy on DVD. It is slower than a pen drive, which I also use, but it is also far less expensive. I promote Puppy by providing a DVD with an OS configured appropriately to the particular needs of the recipient. Because SFS files don't load right from a DVD, I need to configure on a PET basis. New users don't want to hear instructions about loading SFS files after booting, and the dialogue screens are misleading and negative. Anyhow, Puppy seems to be moving away from the optical disk platform. I believe this is unfortunate, because I don't think any other OS devised robust persistence on a disk, and that makes the feature something of a hallmark. So I wish for a working SFS on disk or more PETS in future development, despite the backwardness of the technology.
Posted: Sun 29 Nov 2015, 06:44
by greengeek
eric52 wrote:Anyhow, Puppy seems to be moving away from the optical disk platform. I believe this is unfortunate, because I don't think any other OS devised robust persistence on a disk, and that makes the feature something of a hallmark. So I wish for a working SFS on disk or more PETS in future development, despite the backwardness of the technology.
I quite agree. Optical media can also be extremely valuable from the perspective of avoiding malware (if not using the persistence anyway). What could be better than a remastered pup on CD or DVD, loading extra pets as required - it gives excellent reliability, reproducibility and certainty of operation.
Posted: Sun 29 Nov 2015, 07:14
by 01micko
sfs loading *is* supposed to work from save back to CD/DVD installs. They are supposed to be saved at '/' but I think that is wrong. I might look into this a bit further. Maybe Ted Dog knows the magic, as he is the original writer of the 'save session to optical' routine.
Posted: Sun 29 Nov 2015, 07:47
by eric52
Thanks, 01micko. SFS files do load, get "saved" at / live and work fine once, at least on Tahrpup +. Boot Manager won't accommodate until a disk save. If you do that and set up BM, it fails to load SFS on boot and delivers an error message. You can do it manually by ignoring error/save messages, but that's awkward and inappropriate for a glowing intro to Puppy. I'll contact Ted Dog to see if he has any applicable magic.
Posted: Sun 29 Nov 2015, 18:42
by unicorn316386
Hi eric52,
What is the message you get when you try to load SFS? I think if it is only one folder deep in DVD, it should work (ie. /mnt/home/puppydir). Otherwise, it will have a prompt where you can just select "No Copy" and it will work (I think). I have never booted from CD/DVD though, and am curious if any of this isn't true for that setup. This is how it works for me on HDD in Slacko 6.3.
Posted: Sun 29 Nov 2015, 20:23
by eric52
unicorn316386 - It's been months since I've bothered with SFS on DVD. As I recollect, it protests that it isn't there (/), then that it's already loaded (ignore), then suggests that you make another copy (no), then it works. SFS load/unload is flawless on hard drive (frugal/full) and depends on the setup with pen drive. I think memory serves right. I got everything working in July and haven't messed with it since. Except for the cluttered bits and pieces, it's a useful basement, man-cave system. Considering it's all from the dump, the price was right. I use multi-cores upstairs with Windows for my wife and disks for me.
Posted: Mon 18 Apr 2016, 13:29
by nubc
I request a Virtual Keyboard for Slacko, backwards compatible to Slacko 5.5, called from menu tree, desktop icon, or taskbar quick launch. Likely candidate for implementation includes
xvkbd keyboard.
If you want to keep Puppy Linux an OS for everybody.
Posted: Tue 23 Aug 2016, 08:57
by Pelo
Nice idea to ask people what they would like. Then devs will try to make it real.
At work things were going that way.. Software was chosen depending on what was requested by customer.
Keep FFmpeg included, so many apps are based on it. that is my wish. And no linux to type in terminal, because English needed, but Linux knowledge too.
If you want to keep Puppy Linux an OS for everybody.
Re: rc.shutdown suggestion
Posted: Mon 29 Aug 2016, 23:32
by dagreen
Pick wrote:My case is probably not unique. I am running from a USB stick with a swap file on a HD. Because my devices are static I put a mount statement for the swap file device in rc.local followed by a swapon /mnt/hxx1/pup.swp statement. Cool. Now I have an automatic swapfile brought up at startup. I could build an desktop link to a script to swapoff and umount (Actually I did this) but then I'd have to remember to pop that button before hitting reboot or shutdown.
If I read it correctly, rc.shutdown does a universal umount as it's last act but if the swapfile is still "on" I get a disk error complaining about the partition table when trying to restart..apparently has no consequence but I get nervous when I see HD error messages about partition tables.
The code to find an existing swapfile and swapoff it, would seem to be a relative easy addition right before the busybox umount statement in rc.shutdown. (I guess this presumes there is an easy way to find the *.swp file location) That way if a swap file were inadvertently left on at shutdown it would get turned off before the swap device was unmounted or more probably actually not unmounted before power off.
In my case since I know the location of my pup.swp swapfile I just hard coded a swapoff for that file into rc.shutdown and viola fixed. Not elegant but it works.
agree hahaha
Posted: Tue 30 Aug 2016, 00:14
by nic007
eric52 wrote:unicorn316386 - It's been months since I've bothered with SFS on DVD. As I recollect, it protests that it isn't there (/), then that it's already loaded (ignore), then suggests that you make another copy (no), then it works. SFS load/unload is flawless on hard drive (frugal/full) and depends on the setup with pen drive. I think memory serves right. I got everything working in July and haven't messed with it since. Except for the cluttered bits and pieces, it's a useful basement, man-cave system. Considering it's all from the dump, the price was right. I use multi-cores upstairs with Windows for my wife and disks for me.
Merge your sfs-sddons into the zdrv, adrv or even the base sfs.
Re: rc.shutdown suggestion
Posted: Tue 30 Aug 2016, 15:09
by Sailor Enceladus
dagreen wrote:Pick wrote:My case is probably not unique. I am running from a USB stick with a swap file on a HD. Because my devices are static I put a mount statement for the swap file device in rc.local followed by a swapon /mnt/hxx1/pup.swp statement. Cool. Now I have an automatic swapfile brought up at startup. I could build an desktop link to a script to swapoff and umount (Actually I did this) but then I'd have to remember to pop that button before hitting reboot or shutdown.
If I read it correctly, rc.shutdown does a universal umount as it's last act but if the swapfile is still "on" I get a disk error complaining about the partition table when trying to restart..apparently has no consequence but I get nervous when I see HD error messages about partition tables.
The code to find an existing swapfile and swapoff it, would seem to be a relative easy addition right before the busybox umount statement in rc.shutdown. (I guess this presumes there is an easy way to find the *.swp file location) That way if a swap file were inadvertently left on at shutdown it would get turned off before the swap device was unmounted or more probably actually not unmounted before power off.
In my case since I know the location of my pup.swp swapfile I just hard coded a swapoff for that file into rc.shutdown and viola fixed. Not elegant but it works.
agree hahaha
Can't you just make a swap partition with Gparted? Sounds like the post you quoted is really old and obsolete.
firefox needs default adblocker
Posted: Fri 02 Sep 2016, 04:23
by boof
I'm somewhat aged, an it takes a while to remember that I need to install one after a new install. I know it bloats, but an anti banner and popup add on is essential these days.
Re: firefox needs default adblocker
Posted: Fri 02 Sep 2016, 04:39
by Sailor Enceladus
boof wrote:I'm somewhat aged, an it takes a while to remember that I need to install one after a new install. I know it bloats, but an anti banner and popup add on is essential these days.
There is one at least in Slacko, in Menu -> Internet -> Pup-Advert Blocker. Handy tool for sure.
Posted: Wed 11 Jan 2017, 11:33
by amj
I would like to suggest a small expansion of the JWM configuration manager.
There are currently six options, the one I miss is the opportunity to change, via a GUI, the fonts that JWM uses.
I'm an English speaker an use an EN locale, but I also have large numbers of files with non-latin names.
Whenever I install a Puppy/Quirky system, I install a unicode font and then edit /root/.jwm/jwmrc-theme in order to change the font for Window style, Task List style and Popup style so that my non-latin file names will display correctly in JWM windows and on the panel.
As a Puppy newbie in 2009 I had no trouble installing a unicode font and getting a correct display of non-latin file names throughout Puppy - except for JWM. I put up with gibberish on window headers and the panel for a long time before finally hunting down the configuration file I needed to hack to fix the problem.
Posted: Wed 11 Jan 2017, 15:55
by LazY Puppy
Changes made into /root/.jwm/jwmrc-theme will disappear next time when changing the JWM theme.
Better find out what's the original of /root/.jwm/jwmrc-theme (to be found in /root/.jwm/themes) and doing the changes in original theme file (also).
I think this may be also the cause why there' isn't a option to change fonts from within JWM configuration manager, as there could be different ways used to set the font related to the theme definition file in /root/.jwm/themes?
X Precise 64?
Posted: Thu 09 Mar 2017, 21:10
by steff99
Hi How about X- precise 64?
X -precise was the easiest possible puppy to use. it would run almost anything, had a frisbee connection manager, and was so simple to use, I could use it with my eyes closed.
Precise is amazing, in fact puppy is amazing. it fills the huge gap in the OS market very well, especially for people with older machines, people who transport their OS around the world, and people who like to run in ram.
the problem is that ram is becoming very easy to come by.
most people have 16gb of ram and even that is starting to increase.
puppy fills the void for slower machines, but what about the faster, powerful machines?
I download fatdog 64 recently but I ran into a torrent of problems trying to install 64 bit apps. fatdog made a good attempt at it, but I simply could find all the apps in the repo, and I ended up trying to run slacko 14.1 versions, with limited results.
fatdog, - or anydog, particularly precise with an xfce desktop and thunar manager would be a very powerful but simple OS to use.
and the 64bit version would allow people to copy and paste large file into ram much more easily.
X86
Posted: Wed 12 Apr 2017, 00:37
by Wildman69
My Hardware is old yet reliable and I can not afford a new 64 bit computer.
I am unable to boot the new "uefi" ISOs.
So Please do not leave out Folks like me.
I don't want to go back to "WinBlows".
My System:
PC Manufacturer: Compaq-Presario
Product Name: GN578AA-ABA SR5233WM
Motherboard Vendor: ASUSTeK Computer INC.
Product Name: Lancaster8
BIOS Vendor: American Megatrends Inc.
Version: 5.19
Release Date: 03/04/2008
Intel(R) Pentium(R) D CPU 2.80GHz
Max Speed: 2800 MHz
Current Speed of Core 0:2800 MHz, 1:2800 MHz
Frequency governor : ondemand
Freq. scaling driver : acpi-cpufreq
Total RAM: 3028 MB
Linux Kernel: 4.9.13 (i686)
Kernel Version: #1 SMP PREEMPT Thu Mar 9 09:27:40 GMT 2017
PAE Enabled: No
Distro: wildman69pup 7.0.6
Window Manager: JWM v2.3.5
Thank You.
HAND
Posted: Wed 12 Apr 2017, 05:04
by Robert123
Hi Wildman.
Have you looked at this still being developed.
https://archive.org/details/s57-2017b