Fatdog64-610 testing 20 Nov 2012 (finished)
Here is a potential issue with geany, but I suspect that it would also happen with other Puppies.
In Fatdog, you are logged in as the root user. But it sounds like you are accessing a Mint file that is owned by a non-root user.
If geany is creating temporary files in the Mint filesystem that are also owned by root, they could very well be causing problems, even if you never wrote the actual file back into Mint.
I have seen similar problems with geany when opening a network share. I also have an install of Ubuntu on a flash drive. I once browsed its filesystem from Puppy and managed to corrupt it.
As a test, try using leafpad instead. However, if you change the file and save it back, you will probably have the same problem with corruption.
In Fatdog, you are logged in as the root user. But it sounds like you are accessing a Mint file that is owned by a non-root user.
If geany is creating temporary files in the Mint filesystem that are also owned by root, they could very well be causing problems, even if you never wrote the actual file back into Mint.
I have seen similar problems with geany when opening a network share. I also have an install of Ubuntu on a flash drive. I once browsed its filesystem from Puppy and managed to corrupt it.
As a test, try using leafpad instead. However, if you change the file and save it back, you will probably have the same problem with corruption.
I often use VirtualBox to test other or new distributions. The problem is loading external files in to the distribution. What I tried last night was to run pure-ftpd on the host and gFTP on the client. Only one problem, no pure-ftp in Fatdog or the repository.
You can get a copy here and it works fine.
http://www.smokey01.com/software/Fatdog ... 9-fd64.pet
You can get a copy here and it works fine.
http://www.smokey01.com/software/Fatdog ... 9-fd64.pet
spandey, I have absolutely no idea what caused the corruption. But you can test easily whether geany (or any other tools) changes stuff behind your back.
This is how I would do it. I would assume you are using the RAM layer (if you don't use RAM layer, change references to /aufs/pup_rw to /aufs/pup_save instead).
1. Open a file that exists in the base ISO, but you haven't touched yet, for example: /usr/share/doc/Xdialog.htm
2. Open the corresponding folder of that file in rox, ie "rox /aufs/pup_rw/usr/share/doc"
3. See if there is any Xdialog.htm in that dialog.
4. Close geany.
5. Refresh rox folder, see if Xdialog.htm shows up there.
6. Nothing? That means geany doesn't change anything. If you see a new Xdialog.htm file created there, ok - geany have changed stuff.
You can easily use experiment to verify this: instead of geany, use chmod or chown --- and you will definitely see a new copy created. That is just what the layering system is all about.
smokey01, pure-FTP isn't in the repo because it is already in the base ISO. You can turn it on through Services Manager in Control Panel.
cheers!
This is how I would do it. I would assume you are using the RAM layer (if you don't use RAM layer, change references to /aufs/pup_rw to /aufs/pup_save instead).
1. Open a file that exists in the base ISO, but you haven't touched yet, for example: /usr/share/doc/Xdialog.htm
2. Open the corresponding folder of that file in rox, ie "rox /aufs/pup_rw/usr/share/doc"
3. See if there is any Xdialog.htm in that dialog.
4. Close geany.
5. Refresh rox folder, see if Xdialog.htm shows up there.
6. Nothing? That means geany doesn't change anything. If you see a new Xdialog.htm file created there, ok - geany have changed stuff.
You can easily use experiment to verify this: instead of geany, use chmod or chown --- and you will definitely see a new copy created. That is just what the layering system is all about.
smokey01, pure-FTP isn't in the repo because it is already in the base ISO. You can turn it on through Services Manager in Control Panel.
cheers!
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Hi JamesBond.
Thanks for your response. As you are witnessing some to the frustrations you exhibit. The primary issues that some of us have experienced is that much of the technology that comes with FATDOG is so new and different that we are having problems getting on-board based upon our past experiences with PUPs in Puppyland. And, in some cases, FATDOG offers technology which sharply contrast with past distros we use. So, sometimes what is happening is that we either "think" things are missing, broken, or mis-implemented as we are un-aware that new appraoches have been put in place. FATDOG is awsome, but it's also NEW!
But, we are trying and this is why we follow this distro. We're trying ...
Here to help
Thanks for your response. As you are witnessing some to the frustrations you exhibit. The primary issues that some of us have experienced is that much of the technology that comes with FATDOG is so new and different that we are having problems getting on-board based upon our past experiences with PUPs in Puppyland. And, in some cases, FATDOG offers technology which sharply contrast with past distros we use. So, sometimes what is happening is that we either "think" things are missing, broken, or mis-implemented as we are un-aware that new appraoches have been put in place. FATDOG is awsome, but it's also NEW!
But, we are trying and this is why we follow this distro. We're trying ...
Here to help
Hardinfo
Hardinfo
I continue to applaud what the FATDOG team has done with HARDINFO. They provide this tool such that it shows the distro name and when the "Computer" (top line of Hardinfo) is click provides a snapshot. This version of HARDINFO put in by Kirk several years ago in not present in any 32bit distro to date. I find his advancements with HARDINFO in FATDOG of great value for this system utility.
Issue Reporting
The Computer page of the on-screen report does NOT show RAM. Where on the Summary page RAM (and used RAM) is shown. It does NOT affect operations of the tool or the integrity of data in the report, but someone may want to review and address.
(HARDINFO findings are shown below)
Here to help
I continue to applaud what the FATDOG team has done with HARDINFO. They provide this tool such that it shows the distro name and when the "Computer" (top line of Hardinfo) is click provides a snapshot. This version of HARDINFO put in by Kirk several years ago in not present in any 32bit distro to date. I find his advancements with HARDINFO in FATDOG of great value for this system utility.
Issue Reporting
The Computer page of the on-screen report does NOT show RAM. Where on the Summary page RAM (and used RAM) is shown. It does NOT affect operations of the tool or the integrity of data in the report, but someone may want to review and address.
(HARDINFO findings are shown below)
Here to help
610 Final is released here: http://murga-linux.com/puppy/viewtopic.php?t=82611. Thank you for everyone for testing it.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
ibiblio is giving 403 Forbidden for yours and one (only) of BK's releases this morning. BK and others have been complaining of ibiblio congestion this last fortnight, but problems may have been building for longer. Anyone offering mirrors?
OK - got a valid connection a bit later, so need to keep trying.
There was a slight hiccup on FD-Firefox - started d/l as Fluppy13 but seems OK now.
OK - got a valid connection a bit later, so need to keep trying.
There was a slight hiccup on FD-Firefox - started d/l as Fluppy13 but seems OK now.