I'm still testing on a couple machines, and it is going well so far with my previous savefile and a few minor adjustments. I noticed that the wpa-gui tray icon only has one option left on a right click. I think I will miss the quick access to disconnect, reconnect, and scan. Can they be added back?

We had a discussion about removing those items from the right-click menu. We decided to eliminate items that don't apply to both the Wireless and the Wired tab. So, those three had to go.

Quote:

I had been running with a small initrd, achieved by use of the installer, but that option was not there in the new version. Did I miss something? I know that the script to split it exists, but that seems like so much more effort that the automation that was there before.

Something new I've started to encounter is the inability to terminate or kill a process. Most recently it was with Opera - in fact it may have been Opera in every case. I also could not shutdown or reboot. Resorted to REISUB in the end.

I guessing there are any number of reasons why this delay might be happening. Since changing the gpu driver. I had enabled 'Hardware Acceleration' in Opera. I've now disabled it to see if that is the cause.

Hard to tell. It could be an Opera bug - they have had that sort of issues in the past. If you want to study opera's view of your GPU, including hw acceleration status and quirks, open page opera://gpu.
Another possibility is faulty hardware. With Fatdog64-710 I had a bad USB hub once that completely locked my system because a connected disk couldn't be dismounted. REISUB was the only way out._________________Fatdog64-800|+Packages|Kodi|Findnrun|+forum|gtkmenuplus

Hard to tell. It could be an Opera bug - they have had that sort of issues in the past. If you want to study opera's view of your GPU, including hw acceleration status and quirks, open page opera://gpu.
Another possibility is faulty hardware. With Fatdog64-710 I had a bad USB hub once that completely locked my system because a connected disk couldn't be dismounted. REISUB was the only way out.

Thanks for the thoughts step. I think the cause could well be a usb stick I've had connected. I have noticed it's presence even would affect BIOS loading - with it's removal fixing the problem.

Just want to say that I have been lurking on this topic. I downloaded the Fatdog 720 beta and set up a frugal install on my primary machine with a separate hard disk directory and boot option over a week ago. Also installed the latest Firefox (57.0.2). No significant problems, once I got audio set up.

This already looks stable enough for my modest purposes. I'll move my main system when the actual release comes out.

Just want to say that I have been lurking on this topic. I downloaded the Fatdog 720 beta and set up a frugal install on my primary machine with a separate hard disk directory and boot option over a week ago. Also installed the latest Firefox (57.0.2). No significant problems, once I got audio set up.

This already looks stable enough for my modest purposes. I'll move my main system when the actual release comes out.

Thank for testing. It won't be long.

@polekat: perhaps it has experience bitrot. We'll look at it.
EDIT: flowblade 1.2 was a test release that was accidentally released. It never worked. I've pushed flowblade-1.0 that does work, to the repo._________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.

@ step
I've attached a screenshot from the test laptop. No checkbox, but the desktop computer (where I don't need it) has one. They were both installed from the same CD. I've reinstalled 720 a couple times, with no change.

Using the 710 savefile, my cursor changes from my preferred redglass to the system default when I change from user root to user spot, i.e. when I cross into a browser or e-mail window. With a new 720 savefile, I don't have that. With the 710 savefile, it generally works, but with a few little glitches along the way. I'll have to redo a lot of settings.

I've attached a screenshot from the test laptop. No checkbox, but the desktop computer (where I don't need it) has one. They were both installed from the same CD. I've reinstalled 720 a couple times, with no change.

What's the size of your /tmp? (Running "df -h /tmp" on a terminal will tell you that). The installer will only show "small initrd" checkbox if you have at least 1000M in /tmp. That implies about 2G of RAM.
If your machine has less, the installer won't show the checkbox.

Quote:

Using the 710 savefile, my cursor changes from my preferred redglass to the system default when I change from user root to user spot, i.e. when I cross into a browser or e-mail window.

Assuming you use the fatdog-set-cursor to do that, it seems to be a bug to me. I'll check it out.

Quote:

With a new 720 savefile, I don't have that. With the 710 savefile, it generally works, but with a few little glitches along the way. I'll have to redo a lot of settings.

Well, our official position is we don't support it. In reality, it will usually work most of the time, but it may fail in some corner cases, in an obscure or unexpected ways, because how things changed between versions. If you know what to do, using the old savefile is not a problem. If you **don't** know what to do, it's better to use new savefile rather than spending hours troubleshooting. That is reasoning for the official position.

_____________________

Anyway, most of the time the problem is because:
a) newer Fatdog includes library that used to be in the repo; and the built-in version is newer that the one installed in the savefile.
b) newer Fatdog has new configuration options, which didn't exist previously, and because you have changed the config file, that config file is now "baked" in the savefile and obscures the new one from the savefile.
c) Directories re-created as symlink (or vice versa) between different versions.
Solution for all of the above is simple: uninstall the offending library (a) and remove the white outs (fatdog-clean-whiteouts) to expose the built-in library; and (b) delete the old config file / directory / symlink from the savefile and do "aufs_reval" to expose the new config file from the basesfs. Of course, for this to work, you need to know the library and the config file which needs to changed. Generally not easy. The less you have customised your savefile/savedir, the greater sucsess you have, but who doesn't customise or install anything in their savefile/savedir?
Which is way we always say "Fatdog does not update from previous versions"._________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.

Continue to be impressed by FD720 which I use mainly as liveCD.
Notwithstanding:
a) can it be FULLy installed in the usual sense of deconstructed?
b) like many recent distros RTL8201CL NIC driver is absent. This was an extremely common chip a few years ago. [Suspect the kernel?] Anybody out there that can mould a simple .pet installer for those of us less well endowed, please?
c)can't get a picture, hdmi, on any of my Samsung TVs, old or new, not VESA, FB, modesetting, w.h.y. - most recent ones have dispensed with the vga input, too!

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