Fatdog64-710 Final [4 Dec 2016]
Stuck on make Install command.
I am not able to get "make install" command working. All dependencies are already installed. I am trying to share my USB LTE modem's connection to my Android phone. It works in Windows 7.Have attached a screenshot. Would appreciate any help. Thanks.
stemsee wrote:Hi
I have spent sometime searching for a solution to sharing internet on FD. i found a solution on github that worked first time! It's called create_ap-master.
Unzip and cd into the create_ap-master directory checkout the readme and install the dependencies. Then 'make install'. In term type 'create_ap' to see a list of commands for a variety of hotspot modes.
I used and testedWhat this does is create a wifi hotspot (AP) using the same device which connects to the internet. Laptop and android devices have internet!Code: Select all
create_ap wlan0 wlan0 stemsee 66669999
i am using a usb dongle.
Must have a wifi card that supports master mode.
Might be a worthy addition to FD.
- Attachments
-
- 1.jpg
- (46.81 KiB) Downloaded 1173 times
amn87,
You didn't say whether you had the devx sfs installed. If not, that is where Puppy (and Fatdog) keeps all the tools for compiling.
Not sure if you are using 710 or 720 (I haven't kept up with last few months of changes), but the sfs file you need is here.
http://distro.ibiblio.org/fatdog/sfs/720/
If you need help with how to use sfs files, look here:
http://distro.ibiblio.org/fatdog/web/ about 2/3's down the page.
Dan
You didn't say whether you had the devx sfs installed. If not, that is where Puppy (and Fatdog) keeps all the tools for compiling.
Not sure if you are using 710 or 720 (I haven't kept up with last few months of changes), but the sfs file you need is here.
http://distro.ibiblio.org/fatdog/sfs/720/
If you need help with how to use sfs files, look here:
http://distro.ibiblio.org/fatdog/web/ about 2/3's down the page.
Dan
Thanks for replying. No I did not have the devx sfs installed. I was not aware it was needed. I am on 721. So this one http://distro.ibiblio.org/fatdog/sfs/72 ... vx_721.sfs?
P.S. The Nvidia SFS link http://distro.ibiblio.org/fatdog/sfs/72 ... 4.14.6.sfs is not working. Same issue with the mirrors as well. Anywhere else I can get it? I have PMed jamesbond in this regard but have not heard from him yet.
Edit: Nvidia drivers issue fixed.
P.S. The Nvidia SFS link http://distro.ibiblio.org/fatdog/sfs/72 ... 4.14.6.sfs is not working. Same issue with the mirrors as well. Anywhere else I can get it? I have PMed jamesbond in this regard but have not heard from him yet.
Edit: Nvidia drivers issue fixed.
dancytron wrote:amn87,
You didn't say whether you had the devx sfs installed. If not, that is where Puppy (and Fatdog) keeps all the tools for compiling.
Not sure if you are using 710 or 720 (I haven't kept up with last few months of changes), but the sfs file you need is here.
http://distro.ibiblio.org/fatdog/sfs/720/
If you need help with how to use sfs files, look here:
http://distro.ibiblio.org/fatdog/web/ about 2/3's down the page.
Dan
In my opinion, since I didn't write Fatdog control panel, loading applets makes the panel extensible and customizable. For instance, the optional nvidia driver package for Fatdog-720 adds the nvidia control panel applet to Fatdog control panel.Anniekin wrote:Fatdog control panel is too slow!
Why does it have to load applets?
Why not just make them static links
I think the script changed a bit between Fatdog-710 and 720. In 720 applets are defined in /etc/control-panel-applets and $HOME/.fatdog/control-panel-applets, and in files inside /etc/control-panel-applets.dir and $HOME/.fatdog/control-panel-applets.dir. This is a very flexible, albeit redundant, system that probably aims at being backwards-compatible. Could it be replaced by static links? Probably, but it would be new code for an existing function that isn't broken, so the motivation to do it would be low, I think.
In my informal testing on my hardware, the applet-loading phase takes about 50% of the perceived control panel start time. That is a lot. Interaction with the control panel, once it's running, also feels slow to me. And sometimes double-click are lost on an applet icon.
In the past, forum members offered a couple of alternatives to the Fatdog control panel. Smokey's menu comes to mind (search the forum). If you like that kind of approach - a menu based system - you could take a look at my own script, gmenu2-fdcp in my repo. I takes 152 msec to load the applets on a Core Duo PC.
[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 my opinion, since I didn't write Fatdog control panel, loading applets makes the panel extensible and customizable. For instance, the optional nvidia driver package for Fatdog-720 adds the nvidia control panel applet to Fatdog control panel.Anniekin wrote:Fatdog control panel is too slow!
Why does it have to load applets?
Why not just make them static links
I think the script changed a bit between Fatdog-710 and 720. In 720 applets are defined in /etc/control-panel-applets and $HOME/.fatdog/control-panel-applets, and in files inside /etc/control-panel-applets.dir and $HOME/.fatdog/control-panel-applets.dir. This is a very flexible, albeit redundant, system that probably aims at being backwards-compatible. Could it be replaced by static links? Probably, but it would be new code for an existing function that isn't broken, so the motivation to do it would be low, I think.
In my informal testing on my hardware, the applet-loading phase takes about 50% of the perceived control panel start time. That is a lot. Interaction with the control panel, once it's running, also feels slow to me. And sometimes double-clicks are lost on an applet icon.
In the past, forum members offered a couple of alternatives to the Fatdog control panel. Smokey's menu comes to mind (search the forum). If you like that kind of approach - a menu based system - you could take a look at my own script, gmenu2-fdcp in my repo. It takes 152 msec to load the control panel applets on a Core Duo PC.
Last edited by step on Sun 15 Jul 2018, 07:30, edited 1 time in total.
[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]
I too avoid using the control panel, because of speed issues!
A quick and convenient way to access any application with .desktop file. By creating alternative directories with required desktop files (maybe links will work) provides a faster mechanism.
A quick and convenient way to access any application with .desktop file
Code: Select all
yad --read-dir=/usr/share/applications --icons &
Yes he's an absolute tool. All he had to do was read the help instead of bagging something he knew nothing about. I was very dissapointed in him after reading his review of Fatdog64.Anniekin wrote:i replace the control panel with direct launchers on the lxpanel
unrelated by the way:
i love how this guy confuses his own linux inexperience with percieved shortcomings of fatdog
Yes Fatdog64 has some differences but most of them are improvements.
too funny
Speaking of inexperience i used the fatdog installer and choose the MBR boot option.
It didn't automatically add a boot menu option for the existing Windows 10 OS.
Should I have used the fatdog UEFI installer?
I added the usual root 0,0 chainloader +1 option but it doesn't work.
I need to change it to UEFI format don't I?
Even though I have BIOS set to legacy boot...
Speaking of inexperience i used the fatdog installer and choose the MBR boot option.
It didn't automatically add a boot menu option for the existing Windows 10 OS.
Should I have used the fatdog UEFI installer?
I added the usual root 0,0 chainloader +1 option but it doesn't work.
I need to change it to UEFI format don't I?
Even though I have BIOS set to legacy boot...
Boot settings
@Anniekin: This is my Windows 7 section in syslinux.cfg, in case it helps:
MBR works fine for me, but I realize W10 may be a wee bit different. (Note, I do not have a recovery partition for W7, but it boots and runs quite happily, even if that is usually just to demonstrate that it will. My son-in-law taught me that pressing F8 just after selecting W7 would take me to the diagnostic boot screen, recovery partition or no.)
In regards to the review you pointed out, it is on at least 4 different Linux news type sites. He seems to have much more experience using Linux than I have, but in my ignorance I read as many instructions as I could find, and have had very good results overall. Sad that many will likely believe what they read and dismiss Fatdog64 without trying it.
Dan
Code: Select all
menu separator
label Windows 7
com32 chain.c32
append hd0,1
text help
Start Windows 7 normally
endtext
In regards to the review you pointed out, it is on at least 4 different Linux news type sites. He seems to have much more experience using Linux than I have, but in my ignorance I read as many instructions as I could find, and have had very good results overall. Sad that many will likely believe what they read and dismiss Fatdog64 without trying it.
Dan