Fatdog64-710 Final [4 Dec 2016]
-
- Posts: 152
- Joined: Tue 06 Oct 2015, 14:10
- Location: on the inter-planet train
First of all, thanks to the dev team for this great distro. I've been using Fatdog since version 630.
I have one second hand cheap PC with 4GB RAM. It used to dual boot win7 and Fatdog happily. Recently I boot into Fatdog and edited a sfs file with editsfs utility. At first it is successful, but when the size of sfs file grow to about 350 MB, editsfs failed without any error message.
After comparing the same operation in BarryK's SLAQ64, I suspect the failed editsfs(with 350MB file ) in Fatdog may be caused by insufficient memory. On observation, with physical RAM of 4GB, only 2GB seem to be available for editsfs in Fatdog. Running editsfs in Slaq64, it seem that about 4.2 GB can be used by editsfs.
Is this a limitation of Fatdog ? But Barryk seems to be too busy to maintain older version of Quirky/Slaq. Will future release of Fatdog taking this into consideration ?
Thanks again
I have one second hand cheap PC with 4GB RAM. It used to dual boot win7 and Fatdog happily. Recently I boot into Fatdog and edited a sfs file with editsfs utility. At first it is successful, but when the size of sfs file grow to about 350 MB, editsfs failed without any error message.
After comparing the same operation in BarryK's SLAQ64, I suspect the failed editsfs(with 350MB file ) in Fatdog may be caused by insufficient memory. On observation, with physical RAM of 4GB, only 2GB seem to be available for editsfs in Fatdog. Running editsfs in Slaq64, it seem that about 4.2 GB can be used by editsfs.
Is this a limitation of Fatdog ? But Barryk seems to be too busy to maintain older version of Quirky/Slaq. Will future release of Fatdog taking this into consideration ?
Thanks again
@quirkian2new,
With what version of Fatdog64 did you run editsfs?
I'm not familiar with editsfs and I can't find it in the Fatfog64-710 base SFS. Is it an extra package or pet that I can install or download? Can you please provide links? Thank you.
With what version of Fatdog64 did you run editsfs?
I'm not familiar with editsfs and I can't find it in the Fatfog64-710 base SFS. Is it an extra package or pet that I can install or download? Can you please provide links? Thank you.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
minor bug
Hi, all.
I can't praise version 710 enough, really. You guys are geniuses.
It must load at least twice as fast as 702. Lots of little bugs no longer occur.
Great jobs, guys!
The only bug I've found occurs after updating with Gslapt. Afterwards it is hard to get the Pmount/Unmount Drives program on the start menu to bring up the drive panel that shows the drives.
The notice that says it's reading the drives briefly pops up, then disappears. No panel showing the drives appears. This does not happen unless I update everything with Gslapt.
If I right click on the drive icon on the desktop, it will work sometimes and sometimes not. After perhaps three tries, it will usually work.
I haven't ever had it not work at all, just takes effort and patience, so not a critical concern.
Gslapt updates should be the same as everyone else's, since I boot from the original ISO on a DVD.
I then go to Gslapt, update everything, set up the sound, reinstall Chrome, and add my Bookmarks from a USB drive, basically a clean install every time. (I'm very fond of security and love the fact that Fatdog64 run only in memory. There is nothing else like it.)
I can't praise version 710 enough, really. You guys are geniuses.
It must load at least twice as fast as 702. Lots of little bugs no longer occur.
Great jobs, guys!
The only bug I've found occurs after updating with Gslapt. Afterwards it is hard to get the Pmount/Unmount Drives program on the start menu to bring up the drive panel that shows the drives.
The notice that says it's reading the drives briefly pops up, then disappears. No panel showing the drives appears. This does not happen unless I update everything with Gslapt.
If I right click on the drive icon on the desktop, it will work sometimes and sometimes not. After perhaps three tries, it will usually work.
I haven't ever had it not work at all, just takes effort and patience, so not a critical concern.
Gslapt updates should be the same as everyone else's, since I boot from the original ISO on a DVD.
I then go to Gslapt, update everything, set up the sound, reinstall Chrome, and add my Bookmarks from a USB drive, basically a clean install every time. (I'm very fond of security and love the fact that Fatdog64 run only in memory. There is nothing else like it.)
minor bug
I forgot to mention that this did not occur when I first used 710.
It has begun to happen over about the last couple of months only. Before that everything seemed to work perfectly.
Was the system changed so that updating it could cause this bug?
I would like to be able to update every time, as I used to, and start with all up to date programs.
It has begun to happen over about the last couple of months only. Before that everything seemed to work perfectly.
Was the system changed so that updating it could cause this bug?
I would like to be able to update every time, as I used to, and start with all up to date programs.
-
- Posts: 152
- Joined: Tue 06 Oct 2015, 14:10
- Location: on the inter-planet train
edit_sfs-2.16
@step
I am running edit_sfs-2.16 on FD701 and FD702. But I "think" FD710 may also give the same result. With physical ram 4 GB, seems only 1.8gb or so can be used by edit_sfs. When the sfs file size is under 280MB, the operation is successful. While file of sfs file is approaching 350 MB, it failed without any error message.
I cant remember the actual download link. Attached is a copy (to remove the .gz at the end)
I am running edit_sfs-2.16 on FD701 and FD702. But I "think" FD710 may also give the same result. With physical ram 4 GB, seems only 1.8gb or so can be used by edit_sfs. When the sfs file size is under 280MB, the operation is successful. While file of sfs file is approaching 350 MB, it failed without any error message.
I cant remember the actual download link. Attached is a copy (to remove the .gz at the end)
- Attachments
-
- edit_sfs-2.16-x86_64-PET.txz.gz
- (7.87 KiB) Downloaded 91 times
Smoky01 says
Is there a 'startup file' somewhere that including 'wpa_gui' will initiate the widget with each bootup?
That worked fine, but it does not survive terminal closure or a reboot.eowens2 wrote:
I seem to have to lost the 'bullseye' widget in the tray beneath the screen, clicking on which leads one thru the wi-fi setup (fortunately my wi-fi is still connected).
I can't find it! How can I get it back?
click on wpa_gui or type it in a terminal should put it back in the tray.
Is there a 'startup file' somewhere that including 'wpa_gui' will initiate the widget with each bootup?
@eowens2, Look in /etc/xdg/Startup
It will work in /root/Startup as well.
It will work in /root/Startup as well.
Last edited by smokey01 on Sun 11 Jun 2017, 23:19, edited 2 times in total.
@quickian2new
I read in the edit-sfs OP here that the first time you run it you need to give it the path of a working dir, in a Linux volume, and optionally you can set a RAM disk. I take it to mean that you can also not run with a RAM disk at all. That makes sense, so edit-sfs should be able to handle very large SFS files entirely in the working dir, if there's enough free space.
As for only 1.8 GB RAM available out of 4 GB total, that seems about right. By default Fatdog64 sets /tmp as a RAM file system, which takes about 50% of available RAM. That leaves no more than 2 GB free for applications, including for when edit-sfs wants to create its RAM disk.
I read in the edit-sfs OP here that the first time you run it you need to give it the path of a working dir, in a Linux volume, and optionally you can set a RAM disk. I take it to mean that you can also not run with a RAM disk at all. That makes sense, so edit-sfs should be able to handle very large SFS files entirely in the working dir, if there's enough free space.
As for only 1.8 GB RAM available out of 4 GB total, that seems about right. By default Fatdog64 sets /tmp as a RAM file system, which takes about 50% of available RAM. That leaves no more than 2 GB free for applications, including for when edit-sfs wants to create its RAM disk.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
In Fatdog, spot can't list root but he can list other directories with the same permissions (755) as /root. For example, when running Sylpheed as spot, I can't attach a file from /root: "Could not read the contents of root: permission denied"
Could someone explain why this is so? In Tahr and Slacko, spot can list /root. The only difference I see is that root folder in fd64.sfs is 711, although "ls -ld /root" shows 755.
Thanks in advance
-----------------------
EDIT: OK, that was it. Repack fd64.sfs after "chmod 755 root" and problem is "solved". What new problems have I created? Is it expected for directory to have inherited permissions from a lower layer?
Could someone explain why this is so? In Tahr and Slacko, spot can list /root. The only difference I see is that root folder in fd64.sfs is 711, although "ls -ld /root" shows 755.
Thanks in advance
-----------------------
EDIT: OK, that was it. Repack fd64.sfs after "chmod 755 root" and problem is "solved". What new problems have I created? Is it expected for directory to have inherited permissions from a lower layer?
Re: minor bug
Hi evereman, thanks for reporting this issue. Updates involving disk mounting occurred on May 8 and 13. However, I doubt that they get installed with a gslapt upgrade operation. In a system that's affected by this issue can you please run these commands in a terminal and post the results:evereman wrote:I forgot to mention that this did not occur when I first used 710.
It has begun to happen over about the last couple of months only. Before that everything seemed to work perfectly.
Was the system changed so that updating it could cause this bug?
I would like to be able to update every time, as I used to, and start with all up to date programs.
Code: Select all
ls -l /usr/sbin/mountmon /var/slapt-get/*
pidof mountmon
Does it still happen? If so, can you please run the pmount command in a terminal window and see if there are any error messages?
This issue could even depend on the specific disk models in your system, and be difficult to reproduce on other systems. When it happens, you could check the kernel log for error messages and hints - use command dmesg.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
hey step, if you may help me one last time.. : -)
I'm trying to install one package from npm (yo), but it complains it has no permission to write to the node folders (pup_ro is obviously mounted Read-Only).
Problem is, apparently it requires the -g flag (global), 'cause when I try to install it locally, to work around this (and it does install), the yo command itself never appears.
So my question is either, how to find the command (can't seem to find, maybe it just doesn't install correctly without the -g or maybe it's a symlink to something named something else? glancing over github didn't help much); OR how to re-mount pup_ro as rw?
Any suggestions?
I'm trying to install one package from npm (yo), but it complains it has no permission to write to the node folders (pup_ro is obviously mounted Read-Only).
Problem is, apparently it requires the -g flag (global), 'cause when I try to install it locally, to work around this (and it does install), the yo command itself never appears.
So my question is either, how to find the command (can't seem to find, maybe it just doesn't install correctly without the -g or maybe it's a symlink to something named something else? glancing over github didn't help much); OR how to re-mount pup_ro as rw?
Any suggestions?
Greetings, all. I have two issues lately and a question.
First, on both my HP and a recently acquired Dell laptops, suspend is sometimes slow to respond, sometimes doesn't at all, and is not predictable in it's variety. This may occur whether I close the lid or use the button in the start menu. I may have induced it in the HP with the Control Panel automatic updates (I don't know), but I have avoided doing that on the new Dell. A previous Dell laptop suspends well and predictably.
Second, on the new Dell, flSynclient keeps reverting my touchpad sensitivity setting to the original level. All other settings stay as I have set them. Any suggestions?
The question is whether the Fatdog System Updater package updater method is reliable.
Thank you!
Dan
First, on both my HP and a recently acquired Dell laptops, suspend is sometimes slow to respond, sometimes doesn't at all, and is not predictable in it's variety. This may occur whether I close the lid or use the button in the start menu. I may have induced it in the HP with the Control Panel automatic updates (I don't know), but I have avoided doing that on the new Dell. A previous Dell laptop suspends well and predictably.
Second, on the new Dell, flSynclient keeps reverting my touchpad sensitivity setting to the original level. All other settings stay as I have set them. Any suggestions?
The question is whether the Fatdog System Updater package updater method is reliable.
Thank you!
Dan
minor bug (resolved)
To: Step
All ways of selecting Pmount are working perfectly now. Not sure what happened.
When I went to upgrade with Gslapt to check for the previous bug, I got an error:
Failed to download pfilesearch: HTTP response code said error
My uptime was 56 days, so I decided to shut everything down & reboot.
After a reboot and Gslapt updates, the Pmount display popped up instantly.
Sorry for any inconvenience. Will definitely check everything out (to the best of my limited ability ;^) next time before posting.
Thanks for your help, anyway.
All ways of selecting Pmount are working perfectly now. Not sure what happened.
When I went to upgrade with Gslapt to check for the previous bug, I got an error:
Failed to download pfilesearch: HTTP response code said error
My uptime was 56 days, so I decided to shut everything down & reboot.
After a reboot and Gslapt updates, the Pmount display popped up instantly.
Sorry for any inconvenience. Will definitely check everything out (to the best of my limited ability ;^) next time before posting.
Thanks for your help, anyway.
Chrome not starting SOLVED
SFR
Oh crap, they moved to GTK+3...
You need to install gtk3 (+ its deps) via Gslapt and this should make it working.
Thanks, SFR. I don't reboot very often & was up 56 days this time before rebooting, & when I did, Chrome would not start. Found your post and fixed it.
Love FD64! Thanks to all who unselfishly support it!
jake29 wrote:Chrome 59.0.3071.86 (64bit) not starting in Fatdog64-710
Oh crap, they moved to GTK+3...
You need to install gtk3 (+ its deps) via Gslapt and this should make it working.
Thanks, SFR. I don't reboot very often & was up 56 days this time before rebooting, & when I did, Chrome would not start. Found your post and fixed it.
Love FD64! Thanks to all who unselfishly support it!
Last edited by evereman on Wed 14 Jun 2017, 06:23, edited 1 time in total.
Wine
Does anyone here use Wine 2.0? I need it to install a trading platform (Metatrader 4) that only run on Windows or OSX.
Although I have Windows 7, I haven't used it in a couple of years & really, really don't want to wrestle with it (ever again).
I tried installing from Gslapt & it says it's installed, but will not start.
I've rebooted since, so that installation is no longer on my computer.
Would installing from the repository be any better, do you think?
Thanks in advance for any help anyone can provide.
Although I have Windows 7, I haven't used it in a couple of years & really, really don't want to wrestle with it (ever again).
I tried installing from Gslapt & it says it's installed, but will not start.
I've rebooted since, so that installation is no longer on my computer.
Would installing from the repository be any better, do you think?
Thanks in advance for any help anyone can provide.
@ evereman
To install Wine you need to load a SFS.
Go to the control panel -> System -> SFS Manager then choose Wine from the list (the last item in my view).
After the download, go to the SFS loader (same place), pick wine and move it to the right. If you want it to load automatically every boot, it will ask for confirmation after you leave the window.
To install Wine you need to load a SFS.
Go to the control panel -> System -> SFS Manager then choose Wine from the list (the last item in my view).
After the download, go to the SFS loader (same place), pick wine and move it to the right. If you want it to load automatically every boot, it will ask for confirmation after you leave the window.
Greetings to all,
Does anyone know of a small but capable tablet device small enough to fit into a pocket and that will boot FD? For pocket carry, I presently use a GSM smartphone with no SIM. However, I would like to drop the Android system and go with FD not only for my regular notebook but for the future use FD in my handheld as well.
Traveling with a conventional notebook/laptop will probably only become more inconvenient in the future, and handheld devices have developed capably.
TIA
Does anyone know of a small but capable tablet device small enough to fit into a pocket and that will boot FD? For pocket carry, I presently use a GSM smartphone with no SIM. However, I would like to drop the Android system and go with FD not only for my regular notebook but for the future use FD in my handheld as well.
Traveling with a conventional notebook/laptop will probably only become more inconvenient in the future, and handheld devices have developed capably.
TIA