FatdogArm Beta1/2/3/4- 16 April 2016

[don570]

I solved the problem of reading html files stored on disk.

Method:

1) I made a desktop file called seamonkey-reader.desktop
in applications folder.

This will execute --->

Code: Select all

Exec=/usr/lib/seamonkey-2.33.1/seamonkey-bin

Note that there is no mention of a document.

2) Make a link in SendTo folder named 'Seamonkey Reader'

The right click menu will now open html files reliably when I am root user.

_______________________________________________________

[don570]

To connect with a server (Windows or Linux) using Ethernet...

fatdog_connect-1.7.tbz

Available www.mydrive.ch
User: porteus@don570
Password: porteus
_________________________________________

[don570]

I described how to use fatdog connect
http://www.murga-linux.com/puppy/viewto ... 289#900289

I haven't tested it with a wireless yet.
________________________________

I also uploaded to mydrive.ch

slock --> screensaver and lock app
uextract 3.21
mtpaint 3.49.10
gifsicle 1.8.8 --> newest version

[don570]

I'm continuing to improve fatdog connect to version 1.8

I now disconnects and scans for more addresses.

mtpaint version 3.49.11
______________________________

[keniv]

I can't get bookmark.html files to import. I am importing from a file which I exported from firefox. If I try to import from a mounted flash drive via seamonkey when I get to the end of setting the path then press "open" I get "cannot import from sdc1 permission denied". However, mounting this drive outside seamonkey does not give any problems. I moved the file to home. This time seamonkey appears to import the .html file but no information is transfered. I'll spend some more time on this.

Found a sort of solution to importing bookmarks. I used pfind to find any seamonkey files. I noticed for some there were two of a number of files the only difference in the name was that one of the two ended in -spot. I then checked the .desktop file for seamonkey and the exec was seamonkey-spot.
I assumed I was running seamonkey as spot and this was why I did not have permission to read the .html file from the flash drive while in seamonkey. I then ran seamonkey as root and had no problem importing the bookmarks. I know this is less secure but I have run browsers in other puppies as root so far without a problem. If anybody has a solution to the importing of bookmarks while running as spot I would love to know how its done and I would then go back to running as spot.

Hello All
The above quotes come from this thead [/url]http://murga-linux.com/puppy/viewtopic. ... 900979[url]

It was suggested I post on the problem I had with importing bookmarks.html to seamonkey here. I hope somebody has at least seen this before.

Regards,

Ken.

[don570]

The quick way to switch between spot and root is CTRL ALT arrow

mount-helper mounts drive with this permission: root:$USER, permission is 770/007

I wonder what the 'umount' command permissions are???


There's some facts about permissions here
http://distro.ibiblio.org/fatdog/web/faqs/login.html

Hopefully James has some better advice.

__________________________________________

[don570]

Here is James' explanation

http://distro.ibiblio.org/fatdog/web/fa ... -spot.html
______________________________________

[keniv]

Here is James' explanation

http://distro.ibiblio.org/fatdog/web/fa ... -spot.html

Thanks for the link. I'll go back to running seamonkey as spot and import the the bookmarks from the downloads folder and see how it goes.

Thanks again,

Ken.

[keniv]

Tried running seamonkey as spot. Moved the bookmarks file to downloads. Attempted to import from here. Everything seems to work except when checking bookmarks or manage bookmarks they have not been imported. I also appeared to have lost the link to my bookmarks folder in spot. I was left with a yellow triangle and text telling me it was missing or did not exist. I got it back by making a link from /aufs/devbase/Downloads to /spot. I presume this is OK. I think I will stick with running seamonkey as root for the moment. I have another 8GB micro sd. I might try a new install on this in case there is something wrong with this installation.

Ken.

[don570]

It looks like fatdog connect doesn't work when a wireless network is
used ( a limitation of mount-FULL ). I'll put in a warning screen.

________________________________________

[don570]

I made a fatdogarm right click utility to find image info
imageinfo-fatdogarm-1.3.tbz


http://www.murga-linux.com/puppy/viewtopic.php?t=106709
___________________________________________________

[mikeslr]

Hi All,

You may know from my prior posts that my interest in FatDogArm is the possibility of porting it to various Tablets.

The most significant obstacle to pursuing my interest are my lack of knowledge and experience. Suffice to say, I have to wait for those who know what they are doing to do it.

The second most significant obstacle is that those who know what they are doing can only do it on the few devises they have access to and are willing to risk.

So I wonder if this information may help spur development.

Following up on a thread by kalimorphe, http://www.murga-linux.com/puppy/viewto ... 945#901945 I decided to update my android-sdk. While doing so, I was offered the opportunity to download the system images shown in the attached screenshot.

I'm just guessing, but these may be used in Virtualbox. Kalimorphe's post links to http://highteckblog.blogspot.com/2016/0 ... lling.html which calls for the use of Virtualbox.

mikesLr

[don570]

Tip: You mustn't put

Code: Select all

net=wired:eth0:dhcp

in cmdline.txt if you haven't connected your board to a router or another computer.
The booting procedure will just stall.

[don570]

I came across this strange behaviour.

When using xdialog with a text box.

The box automatically opens wide enough for text when
raspberry pi version of fd-arm.sfs is used.

beta4 version of fd-arm.sfs --> the window must be open wide by user

Code: Select all

Xdialog --title "'$(gettext 'List')'"  --left --wrap   --ok-label "'$(gettext 'Close')'"  --no-cancel  --textbox "/root/address" 0 0 &

___________________________________________________________

[don570]

Some good news!!

I was able to use a Netgear Wn111 N300 wireless USB adapter
to work with Raspberry pi.

It uses carl9170 driver . Here's how I did it.

I installed firmware https://packages.debian.org/wheezy/firmware-linux-free

( I made into firmware-linux-free-3.2.tbz)

Then I took the wireless drivers out of Barry's berryboot package

https://sourceforge.net/projects/berryb ... 4/download

( I made into wireless-drivers-fatdogarm.tbz)
available at mydrive.ch

EDIT: Install of wireless drivers wasn't needed because they are already
in fatdog arm!!! Just the firmware is needed


I booted up and typed in terminal

Code: Select all

dmesg  | more

I saw...
usbcore: registered new interface driver carl9170

Next I connected to network
control panel > network > Network Setup

I could enter a windows server with fatdog_connect.sh

_____________________________________________________

[don570]

I then connected to my Cisco router using fatdog built-in software



_______________________________________________________

[don570]

Control Panel->System->Manage Servers and Services

Both dropbear and mongoose worked!

I can now use Putty program in Windows XP to contact the raspberry pi board.

_____________________________________

[don570]

Fatdog uses an old and buggy version of leafpad
Here is is the improved version

http://www.filewatcher.com/d/FreeBSD/di ... 89079.html
___________________________________________

[don570]

The best way to solve the missing icons problem is to make the .DirIcon
in /usr/local/apps/ and use links.
http://puppylinux.org/wikka/RoxApplicationDirectory

-------------------------------------------------

Instructions to make changes to fd-arm.sfs

Read....
http://lightofdawn.org/wiki/wiki.cgi/-w ... gFatdogArm

Customising FatdogArm (the old way)

The old way of customising/adopting FatdogArm is similar to the above: one would still need to prepare a bootloader, a kernel, a kernel modules, and modify the initrd. The only difference is on how to prepare fd-arm.sfs - instead of building fd-arm.sfs from scratch using FatdogArm's meta-distribution, one uses and modifies an existing fd-arm.sfs from an existing FatdogArm image.


1.Get the fd-arm.sfs from the disk image as explained previously.

2.Extract the fd-arm.sfs by issuing this command.
It will create a new directory called squashfs-root containing all the files inside fd-arm.sfs in the current directory.
unsquashfs fd-arm.sfs


3.Add/remove packages as needed.
When you do this you must be inside the squashfs-root; thus the commands below is always preceeded by cd squashfs-root.


◦Adding a package:
( cd squashfs-root; ROOT=$(pwd) sbin/installpkg /path/to/your/package.tbz )


◦Remove package:
( cd squashfs-root; ROOT=$(pwd) sbin/removepkg name-of-package-to-remove )

4.Modify other files/scripts/configuration files as needed.

5.Re-pack (re-generate) the sfs by issuing this command:
mksquashfs squashfs-root fd-arm.sfs -comp xz -Xbcj arm -noappend


6.Done.

[don570]

In the previous post the method of installing an app is
( cd squashfs-root; ROOT=$(pwd) sbin/installpkg /path/to/your/package.tbz )

This works well from my experience. It will even install .DirIcon files
and links.

__________________________________________________________

The making of the package with dir2pkg

Warning ---> there are problems when using dir2pkg utility when the folder package has .DirIcons inside


Here are instructions for making a package with right click menu items.

1) Remove the .DirIcons from the Application Directories (see image for example)



2) you must not have links inside an Application Directories. So you will
make these in the doinst.sh script

Here's an example of a doinst.sh script.
Note the final line where a link is made named .DirIcon inside the Application Directory

Code: Select all

#!/bin/sh
mkdir -p /root/.config/rox.sourceforge.net/SendTo/.text_html
mkdir -p /root/.config/rox.sourceforge.net/SendTo/.text_plain
mkdir -p /root/.config/rox.sourceforge.net/SendTo/.application_x-shellscript
mkdir -p /root/.config/rox.sourceforge.net/SendTo/.application_x-executable
mkdir -p /root/.config/rox.sourceforge.net/SendTo/.application_x-desktop
mkdir -p /root/.config/rox.sourceforge.net/SendTo/.application_xml
mkdir -p /root/.config/rox.sourceforge.net/SendTo/.text_css
mkdir -p /root/.config/rox.sourceforge.net/SendTo/.text_x-bacon
mkdir -p /root/.config/rox.sourceforge.net/SendTo/.text_x-gettext-translation
mkdir -p /root/.config/rox.sourceforge.net/SendTo/.text_x-gettext-translation-template
mkdir -p /root/.config/rox.sourceforge.net/SendTo/.text_x-patch


# links for Leafpad
ln -fs "/usr/local/apps/Leafpad"  /root/.config/rox.sourceforge.net/SendTo/.application_x-desktop/"Edit with Leafpad"
ln -fs "/usr/local/apps/Leafpad" /root/.config/rox.sourceforge.net/SendTo/.application_x-executable/"Edit with Leafpad"
ln -fs "/usr/local/apps/Leafpad" /root/.config/rox.sourceforge.net/SendTo/.application_xml/"Edit with Leafpad"
ln -fs "/usr/local/apps/Leafpad" /root/.config/rox.sourceforge.net/SendTo/.application_x-shellscript/"Edit with Leafpad"
ln -fs "/usr/local/apps/Leafpad" /root/.config/rox.sourceforge.net/SendTo/.text_css/"Edit with Leafpad"
ln -fs "/usr/local/apps/Leafpad" /root/.config/rox.sourceforge.net/SendTo/.text_html/"Edit with Leafpad"
ln -fs "/usr/local/apps/Leafpad" /root/.config/rox.sourceforge.net/SendTo/.text_plain/"Edit with Leafpad"
ln -fs "/usr/local/apps/Leafpad" /root/.config/rox.sourceforge.net/SendTo/.text_x-bacon/"Edit with Leafpad"
ln -fs "/usr/local/apps/Leafpad" /root/.config/rox.sourceforge.net/SendTo/.text_x-gettext-translation/"Edit with Leafpad"
ln -fs "/usr/local/apps/Leafpad" /root/.config/rox.sourceforge.net/SendTo/.text_x-gettext-translation-template/"Edit with Leafpad"
ln -fs "/usr/local/apps/Leafpad" /root/.config/rox.sourceforge.net/SendTo/.text_x-patch/"Edit with Leafpad"
ln -fs "/usr/local/apps/Leafpad" /root/.config/rox.sourceforge.net/SendTo/.application_x-zerosize/"Edit with Leafpad"


ln -fs  /usr/share/pixmaps/leafpad.png  "/usr/local/apps/Leafpad/.DirIcon"

3) Now the right click menu item 'dir2pkg' will work correctly to make an
acceptable fatdog app package. The package will show the right clicks correctly
with an icon.
__________________________________________________________