Fatdog64-710 Final [4 Dec 2016]

A home for all kinds of Puppy related projects
Message
Author
Sage
Posts: 5536
Joined: Tue 04 Oct 2005, 08:34
Location: GB

T-bird

#421 Post by Sage »

Is anyone using Thunderbird Version 52.1.0 with Fatdog64_710-Final?
Try Claws instead - more of a generic program, whereas, I've found some versions of T-bird seem to depend on particular versions of Firefox loaded.

User avatar
bpuppy
Posts: 14
Joined: Tue 25 Apr 2017, 13:03
Location: Quebec

#422 Post by bpuppy »

@step:

It works great now!

Thanks

FanDog
Posts: 30
Joined: Thu 25 May 2017, 18:13

#423 Post by FanDog »

Hello all, great project!

I've posted a few bugs/headaches in the following thread:

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

Fixed those but now trying to install a more up to date nodejs, it complains that GLIBCXX isn't 3.4.20, when I run "strings" on libstdc++.so.6 the last GLIBCXX goes only to 3.4.19

it comes from the "alien" repo, is there a way to get a quick hack of gcc there just for node? : )

Any suggestions on how should I proceed? Maybe there are other repos?

Thanks!

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

#424 Post by step »

Hello FanDog and welcome to the forum. I built Node.js 6 snd 7 packages a while ago. Here's a link to my shared folder, help yourself.
link
I prefer loading the Node 6 SFS package rather than installing the TXZ archive permanently, as I need Node only occasionally. I made Node 7 but I don't use it (incompatible with some Node packages).
To make my packages I simply downloaded and re-packaged the files on nodejs.org, i.e. https://nodejs.org/dist/v6.9.2/node-v6. ... x64.tar.xz
[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]

FanDog
Posts: 30
Joined: Thu 25 May 2017, 18:13

#425 Post by FanDog »

Thanks! and thanks for the packages too! : )

So the txz in your drive are unchanged from node's site and then you repackaged with some wizardry? cool! I got the node 7 there, just in case but, I guess 3 is the charm 'cause I tried now and the thing worked:

It wasn't compiling node itself that was problematic, even the "alien" repo's node6 installed ok. But some package inside which was complaining it needed 6.. then got some other errors that suggested even almost a Gig of extra space on the savefile wasn't enough! (it never reached low levels nor got the red warning.. it probably tried to create some huge file there and all the installing was silent about it!)

So I resized it and this time it went through without complaints. (except for deprecated things and, failed, an optional dep) So at least I got it working, so I'm not messing with that house of cards until I absolutely need to update it. :-/

Here's a "bug" I suggest is really dangerous.. I tried to resize the savefile back a bit (gave a lot extra, just to see if that would solve it), almost destroyed the whole thing lol.. great thing I recalled the exact number I typed and the tool managed to force the check (it wouldn't proceed with a manual check!) and didn't halt on the part that it had nothing to do. (the 4k part.. sector size I think.. probably filesystem sectors(size) versus partition size)

I suggest you check for negative numbers there ^__________^' ' ' ' (any way to reduce the size.. safely? hee hee hee)

Speaking of undoing things.. Firefox update warns it may not work from the non-fatdog specific one.. how do I get back to this working version were it not to work?

again, thank you.

s243a
Posts: 2580
Joined: Tue 02 Sep 2014, 04:48
Contact:

#426 Post by s243a »

jamesbond wrote:Glad that it works :D
Sadly, Fatdog is still on DW's waiting list, although it was submitted over 2 years ago ...
It looks like it is on distro watch now but the site seems down so I only found a cached version:https://webcache.googleusercontent.com/ ... eamonkey-a

rankings varying between 164 and 270.

s243a
Posts: 2580
Joined: Tue 02 Sep 2014, 04:48
Contact:

#427 Post by s243a »

the iputils package is quite out of date. It looks like you have the 2012 release. This matters to me because I'm trying to use traceroute6 from inside a virtual box. For this to work I need the following option:

Code: Select all

 -I      Use ICMP6 ECHO instead of UDP datagrams.
http://www.manpagez.com/man/8/traceroute6/

which isn't supported in the 2012 release.

I'll try compiling a newer version.

On another note, I've installed the miredo package which gives me IPv6 connectivity when using virtualbox, with networking set to NAT. However, if I put in an internet hostname into the traceroute6 command it tells me the host is unknown. I resume this is because I'm not connecting to any IPv6 name server. I did find a function on fatdog64 called udhcp6. Maybe this tool can connect me to the name server. I wonder if this is similar to dhcpd.

edit: so I looked, at both the official fork, and the unofficial fork as noted on the linux foundations website. In the official fork traceroute6 hasn't been updated since 2012. In the unofficial fork traceroute6 has been updated as recently as one moth ago.

However, the offical fork has something called tracepath6 which has been updated as recently as Jully 2016. Perhaps this is a replacement for traceroute6 in the official fork.

s243a
Posts: 2580
Joined: Tue 02 Sep 2014, 04:48
Contact:

#428 Post by s243a »

s243a wrote:
edit: so I looked, at both the official fork, and the unofficial fork as noted on the linux foundations website. In the official fork traceroute6 hasn't been updated since 2012. In the unofficial fork traceroute6 has been updated as recently as one moth ago.

However, the offical fork has something called tracepath6 which has been updated as recently as Jully 2016. Perhaps this is a replacement for traceroute6 in the official fork.
I tried compiling the unofficial fork at it didn't support the -I option either. However, I noticed that the BSD version does:
https://github.com/freebsd/freebsd/blob ... ceroute6.c

I tried replacing the BSD version of traceroute6 in the unofficial for in iputils. I didn't have the header as.h

https://www.gnu.org/software/binutils/
https://github.com/freebsd/freebsd/tree ... nutils/gas
https://en.wikipedia.org/wiki/GNU_Assembler
https://en.wikibooks.org/wiki/X86_Assembly/GAS_Syntax

fatdog actually has the program "as" it is just missing the c header.

I'm not actually sure that there is anything wrong with the traceroute6 that comes with fatdog64 because it worked for google.com. However, the -I syntax was helpful for the IPv4 version of traceroute, so I think I'll continue with my mutant BSD fatdog experiment.

Some more notes:
I coppied the following two files into user/include:
/gas/as.h
/include/alloca-conf.h

alloca-conf.h is asksing for config.h

AA bit of research tells me that config.h was removed from the linux kernal.

So I'll try commenting out that statment in alloca-conf.h and see what happens.

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

#429 Post by step »

FanDog wrote: I suggest you check for negative numbers there ^__________^' ' ' '
Thank you, noted.
(any way to reduce the size.. safely? hee hee hee)
I've never done this, but I guess you could use file copy, simply drag-and-drop files from a larger savefile to a smaller one. Let's call them old-large.ext4 and new-small.ext4. old-large.ext4 exists by definition in some folder. Reboot with savefile=none as a kernel boot line option. Open a rox window in the folder where old-large.ext4 is located, usually /mnt/home - you'll need to dig around your discs until you find it. Click the old-large.ext4 icon. It should open in a new rox window and reveal its contents. Select the new rox window and press ` (backtick), which opens a terminal window in that folder. Type "df -hs ." and note the size you get. Don't do anything else in this window nor in the rox window. The number you noted is an estimate of the minimum size the new-large.ext4 savefile will need to be. Close the terminal and click again the old-large.ext4 icon, which closes its corresponding rox window. Close the initial rox window then shutdown. When Fatdog prompts you for savefile options create the new-small.ext4 savefile. Now reboot with savefile=none again, open a ROX-Filer window in the folder where you saved the two savefiles and click the two savefile folder icons, which opens their contents in two new rox windows. You can copy files between the two windows. When you're done don't forget to click the savefile icons to unmount the savefiles. Again, I've never done this, but conceivably it should work. I have no experience with encrypted savefiles. I don't know if this procedure would work in that case.
Speaking of undoing things.. Firefox update warns it may not work from the non-fatdog specific one.. how do I get back to this working version were it not to work?
If you want to experiment with different programs and be able to go back to a known state you could either boot with different throw-away savefiles, one for each experiment, or you could use a single savefile but run your experiments in sandboxes. Try sandbox.sh or rw-sandbox.sh in a terminal window. I think sandboxes are also discussed in the Fatdog64 FAQ (included in the Help system).
[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]

FanDog
Posts: 30
Joined: Thu 25 May 2017, 18:13

#430 Post by FanDog »

Thanks. It should work.. I'll take a rest from the risk for the moment tho :)

> sandbox

cool! okay, it asked me which sfs to load.. It can't find node though. I loaded your .sfs (version 7), it can't find outside of the sandbox either (where does it go?)

soo.. assuming something writes to a system directory, only the sandbox would see it?

I uninstalled node version 4.3 (by gslapt) btw. If I could find v7 I could symlink to it...

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

#431 Post by step »

It asks which of the currently loaded SFS files you want to be able to access from within the sandbox. Untick the ones you don't want. Pre-load the ones you want and leave them ticked.
This kind of sandboxing is based on the chroot command: man chroot.
GUI isn't available from within the sandbox. There's another kind of sanbox, {rw-}sandbox-lxc.sh which allows for GUI interaction (in a sandboxed display).
[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]

User avatar
smokey01
Posts: 2813
Joined: Sat 30 Dec 2006, 23:15
Location: South Australia :-(
Contact:

#432 Post by smokey01 »

step wrote:It asks which of the currently loaded SFS files you want to be able to access from within the sandbox. Untick the ones you don't want. Pre-load the ones you want and leave them ticked.
This kind of sandboxing is based on the chroot command: man chroot.
GUI isn't available from within the sandbox. There's another kind of sanbox, {rw-}sandbox-lxc.sh which allows for GUI interaction (in a sandboxed display).
@step, I usually just type xwin in the sandbox terminal and get the full x window environment, or is this something different.

s243a
Posts: 2580
Joined: Tue 02 Sep 2014, 04:48
Contact:

#433 Post by s243a »

smokey01 wrote:
step wrote:It asks which of the currently loaded SFS files you want to be able to access from within the sandbox. Untick the ones you don't want. Pre-load the ones you want and leave them ticked.
This kind of sandboxing is based on the chroot command: man chroot.
GUI isn't available from within the sandbox. There's another kind of sanbox, {rw-}sandbox-lxc.sh which allows for GUI interaction (in a sandboxed display).
@step, I usually just type xwin in the sandbox terminal and get the full x window environment, or is this something different.
Well....if you try to use this procedure to build a package you might end up with a bunch of files that you don't need for the pet....although I haven't tried this so perhaps I'm wrong. Maybe the trimfat toll will remove the junk.

FanDog
Posts: 30
Joined: Thu 25 May 2017, 18:13

#434 Post by FanDog »

Yes but I can't seem to find node 7. Neither in or outside the sandbox.

Once it's loaded, shouldn't it be added to /usr/bin or somewhere in the path?

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

#435 Post by step »

@FanDog, it works for me, see the transcript below, which also exemplifies a potential pitfall, links. The symlink "inspect-process" is broken, because it points outside the sandbox. That's by design. From within the sandbox you're seeing the link name file "inspect-process", but you're forbidden to see its target, "/mnt/D/usr/..." because the mount doesn't transfer into the sandbox.

Something like that could be the cause for a sandboxed shell not to find a command, like typing "node" and getting a "node isn't a valid command" in response. Try "readlink -f /usr/bin/node" and you should get "/usr/bin/node" back.

Code: Select all

# load_sfs.sh --load node-7.3.0-x86_64-1.sfs
# sandbox.sh  # accept all ticked SFS items

Starting sandbox now.
sandbox# which node
/usr/bin/node

sandbox# ls -l /usr/lib/node_modules/
total 0
lrwxrwxrwx  1 root root  48 Dec 24 00:38 inspect-process -> /mnt/D/usr/lib/node_modules/inspect-process
drwxrwxr-x 11 root root 421 Dec 20 20:34 npm

sandbox# exit
exit
Leaving sandbox.
[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]

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

#436 Post by step »

smokey01 wrote:... I usually just type xwin in the sandbox terminal and get the full x window environment, or is this something different.
I stand corrected :) you're right, I can run xwin from within sandbox.sh just like I can from within sandbox-lxc.sh. I had always assumed that only the latter was possible.

s243a has a good point, if you're using sandbox.sh to build packages you need to clean the package from the extra files that get added to the sandbox for its mere existence and operation, such as some files in /usr/bin, hidden "whiteout" files, etc. The more you do inside the sandbox.sh, including running xwin, the more extra stuff gets added. But if you aren't concerned with building packages inside sandbox.sh, you don't need to worry.

It is safer to build packages using the Fatdog64 build environment, found at /usr/src/pkgbuild when the devx.sfs is loaded. That build system also uses sandboxes, but not sandbox.sh.

If you run xwin from sandbox.sh remember that you're subject to the same limitations that I described in my previous post; not all mounts transfer into the sandbox, and symlinks that point outside the sandbox don't work. This isn't bad; it serves the purpose of insulating the sandboxed shell so you can experiment without doing damage outside the sandbox.
[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]

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#437 Post by jamesbond »

step wrote:s243a has a good point, if you're using sandbox.sh to build packages you need to clean the package from the extra files that get added to the sandbox for its mere existence and operation, such as some files in /usr/bin, hidden "whiteout" files, etc. The more you do inside the sandbox.sh, including running xwin, the more extra stuff gets added. But if you aren't concerned with building packages inside sandbox.sh, you don't need to worry.
To add: Inside sandbox.sh (or its variants), you can build and compile packages and even to "make install" step.

Then, from **outside**, while the sandbox.sh is still running, you can open a new terminal and run "sb2dir.sh". This is "sandbox-to-directory" (similar to new2dir) which will copy the files inside sandbox to /tmp, while attempting to remove all the sandbox-related files.

You can then inspect that directory, and clean additional files as you need; and then run "makepkg" to build a package.

To test it, you can launch another sandbox.sh and install the newly created package and see if it works (yes, you can launch multiple sandboxes at the same time, provided your memory allows).

Rinse and repeat as needed.
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]

FanDog
Posts: 30
Joined: Thu 25 May 2017, 18:13

#438 Post by FanDog »

@step

I'd be happy to access it even from OUTSIDE any sandbox!

This also happened when I installed the version from gslapt (4.3 I think).. maybe it has the same cause, but I had to manually create the symlink.

How can I find where your SFS packaged was loaded in? "whereis node" doesn't seem to find anything. :(

purple379
Posts: 157
Joined: Sat 04 Oct 2014, 22:23

AMD mobo with FatDog

#439 Post by purple379 »

I wonder if any of you have used this hardware combination, and can save me time of trying all the options. I have booted with FatDog 710, and I have did verify the ISO.

FatDog starts off working pretty well with this hardware, but sound does not work. I tried to go through the options of trying other Sound Cards. After a few hours.

I tried Mint Linux, which has sound. Using Netflix, the screen blinks every once in a while.

Guessing the common denominator is the Video Chip and Card. That I need to load proprietary drivers.

Windows 10, Belarc shows the hardware as this.

main processor
3.10 gigahertz AMD A8-7600 Radeon R7, 10 Compute Cores 4C+6G
256 kilobyte primary memory cache
4096 kilobyte secondary memory cache
64-bit ready
Multi-core (2 total)
Hyper-threaded (4 total)

display

AMD Radeon R9 200 Series [Display adapter]
AMD Radeon(TM) R7 Graphics [Display adapter]

multimedia

AMD High Definition Audio Device (2x)
High Definition Audio Device

Other

1 - SAMSUNG (2- AMD High Definition Audio Device)
Digital Audio (S/PDIF) (High Definition Audio Device) (2x)

Main Board;

Board: Gigabyte Technology Co., Ltd. F2A88XM-D3H
Bus Clock: 100 megahertz
UEFI: American Megatrends Inc. F9 12/25/2015


This has 8 GB of RAM, and Mint Linux is using an SSD for its drive now.
______________________________________________________________

AMD has a driver set called Crimson, which has an install package with Ubuntu. RHEL,

Mint Linux says the sound driver it has is ATI Radeon, not sure whether that is for the chip or the Video Card.

Last year I was trying to get Linux to work, and FGLRX only crashed with Debian.

I am guessing the screen blips with streaming video might be related to the way Cache is now setup with Firefox, and Google Chrome, both of which work with Mint Linux and Netflix. Although first I should try to make sure all the better drivers before I start messing with Browser Cache size.

As I am not really knowledgeable about fiddling with hardware drivers, I wondered if someone else had wrestled this alligator to the ground.

Thanks for reading and for any help.

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

#440 Post by step »

@FanDog

Code: Select all

# load_sfs.sh --load /mnt/home/710/node-7.3.0-x86_64-1.sfs
# whereis node
node: /usr/bin/node /usr/include/node /usr/share/man/man1/node.1
# losetup -a
/dev/loop0: 0 /kernel-modules.sfs
/dev/loop1: 0 /aufs/devbase/710/fd64.sfs
/dev/loop10: 0 /mnt/home/710/fd64-devx.sfs
/dev/loop11: 0 /mnt/home/710/node-7.3.0-x86_64-1.sfs
      ^^ 11 mark down this number (11) - could be different in your system

# rox /aufs/pup_ro11 # open rox window in the layered node folder

# find /aufs/pup_ro11 -maxdepth 3
/aufs/pup_ro11
/aufs/pup_ro11/usr
/aufs/pup_ro11/usr/bin
/aufs/pup_ro11/usr/bin/node
/aufs/pup_ro11/usr/bin/npm
/aufs/pup_ro11/usr/include
/aufs/pup_ro11/usr/include/node
/aufs/pup_ro11/usr/lib
/aufs/pup_ro11/usr/lib/node_modules
/aufs/pup_ro11/usr/share
/aufs/pup_ro11/usr/share/doc
/aufs/pup_ro11/usr/share/man
/aufs/pup_ro11/usr/share/systemtap
find should list a similar folder structure. If it doesn't then we need to figure out why the SFS file isn't loading in your system.

It could also be that the SFS is loading, but it isn't added to the layered file system for some strange reason. Do you mind performing similar steps to the above in a terminal window and posting the output you get?
If the SFS is correctly loading and is being added to the layered file system, then you should find all the paths that are rooted in /aufs/pup_ro11 also rooted in /, for instance /aufs/pup_ro11/usr/bin/node and /usr/bin/node.

It could also be - as I think I mentioned in a previous post - that something is masking /usr/bin/node and turning it into a non-executable file. In that case typing "node" to a shell prompt would yield a "not an executable file or command" error message.

The SFS doesn't include any icons for node; it's all for working at the shell prompt.
[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]

Post Reply