Fatdog64 700 alpha1

[neerajkolte]

@neeraj - set "prompt 0" and it will not stop to prompt you - it will only prompt you if you press shift/alt-key.

Hi I tried that.
It boots quickly, but I couldn't get prompt when i pressed shift/alt-key.
Syslinux wiki says caps lock or scroll lock can also be used.

I tried press n hold and continuous tapping also, can't get the prompt.

I must be doing something wrong or my timing might be wrong.

Thanks.

- Neeraj.

[jamesbond]

@Billtoo - sounds good. On next release you can actually convert it to a package that you can install. The tool is already there, so is the right-click menu - but it doesn't work yet

@Neeraj - yes, the key requires precise timing, but it does work. At least on earlier version of syslinux, I haven't tested with the one that comes with 700a1 ...

@mavrothal, zarfy settings is stored in $HOME/.zarfy. Zarfy sometimes can be fickle too, it stores the setting based on the value of $DISPLAY. In my machine, depending on how I boot it up, sometimes I've got ":0" as $DISPLAY, sometimes ":0.0". Of course, the settings set when I was at the other DISPLAY won't work with the other one ... so what I did was delete one of them, and symlink it

cheers!

[neerajkolte]

@Neeraj - yes, the key requires precise timing, but it does work. At least on earlier version of syslinux, I haven't tested with the one that comes with 700a1 ...
cheers!

No worries, Cheers.

I noticed xterm is also included with urxvt.

Any special reasons or advantages of it.

[GKM]

Hi ,

@jamesbond or @kirk

In the first post I read that you compiled everything by hand, but you also mentioned a build system. Actually I hope your build system consists of a few bash scripts in order to easily reproduce the whole alpha build, and facilitate the production of the improved 700 candidate. If so, are those scripts available somewhere? I would like to try my hand at building a Fatdog tailored to my personal needs, but was unable to locate such scripts on ibiblio.

Keep up the good work!

Regards,

GKM

[jamesbond]

@neeraj - xterm you see in the basesfs will start urxvt - it's just a compatibility wrapper. If you want the REAL xterm you need to get it from the repo.

@GKM - some of the build scripts are already inside devx. All packages build with in Fatdog has their "build recipes" (ie how they were configured and built) in /usr/src/pkgbuild/pkg (in devx.sfs); and they can be rebuilt using the build scripts in /usr/src/pkgbuild too (this is indeed the 3rd way to build packages I talked about in the 2nd post of this thread - but I haven't gotten the time to document it further).

The build script to make a complete Fatdog ISO is not ready for release yet. However, since Fatdog64 uses Slackware-style packages, you can look at Woof-CE (the "next" branch) that contain build scripts for Slackware-based puppy.

cheers!

[GKM]

Hi jamesbond,

Thanks for the info and pointers to scripts. I suppose kirk and yourself will be so busy with fatdog development and your lives outside fatdog that you'll probably recommend against waiting for the complete fatdog iso build script you mentioned. I'll see what I can do with the currently available info.

By the way, I am grateful for the option to remove built-in packages, so maybe I'll do that instead.

Regards,

GKM

[rcrsn51]

Deleted due to lack of interest.

[Gobbi]

Thank you for updating and adding the Skype sfs to the 700-repo
It works fine
I had problems connecting on older versions of Fatdog

rcrsn51 - I installed your PPET and it works . Thank you
I could install cpufreq-ppower-0.0.1.pet . Running it made me observe the CPU ran less without it - it must be an improovment on the new Fatdog 700 . I also installed FBReader with PPET but it doesn't fit into the new Fatdog 700 .

[rcrsn51]

[Removed]

[eowens2]

I have downloaded fd64-devx_700a1.sfs and kernel-source-3.15.5.sfs to my Downloads directory.

Right-clicking the kernel SFS then "Load" seems to load it, it shows up in the System SFS Loader, and the content shows up in /usr/src/.

Right-clicking the devx SFS then "Load" seems to mount the SFS, but it does not show up in the System SFS Loader, and “make

[jamesbond]

Thank you rcrsn51. 700a1 comes with a tool to convert pet to txz by right-clicking but it isn't working at the moment (fixed for next release) - so yours will be a good interim solution.

Gobbi - credit for skype belongs to Catdude, OscarTalks, watchdog, and others in this skype thread: http://murga-linux.com/puppy/viewtopic.php?t=94807. I just repackaged it.

eowens2 - devx.sfs is loaded in the same way as kernel sfs. If it fails to load, then perhaps the file is bad - did you check the md5sum?

[eowens2]

[quote]Right-clicking the devx SFS then "Load" seems to mount the SFS, but it does not show up in the System SFS Loader, and “make

[jamesbond]

Thanks to CatDude and others in the skype 4.3 thread, I updated skype.sfs to be able to show avatars.

[gcmartin]

As FATDOG progresses I would like to request a directory be added to the /root. @JamesBond has been our community key for remote booting PUP distros on any LAN PC that a home user uses. His work has been useful to many of us over the years. Thus, thanks to him, It allow FATDOG to support booting other FATDOGs and other PUPs on PCs without any need to burn ISOs to do so.

As FATDOG moves from its Alpha state into GA, I request to have a tftpboot directory in its /root structure with the following attached Readme. It offer no system impact, but has benefit.

One view is that by doing so, it allow "reboot boot" to be procedural with no need to make filesystem changes or subsystem additions by users.

Thanks in advance for any consideration to support this FATDOG facility.

[Billtoo]

Installed to a 32gb usb 3.0 flash drive:

[OldChap]

Maybe I am a bit ambitious but I am a windows refugee with a few months of Mint under my belt and having only dabbled with fatdog before I am attempting to run Boinc on 700a1 as this seems right for the future.

A few months back trying this on 630 it became clear that I needed 32bit libraries. Trying again today I have added these having been guided to sfs manager and sfs loader.

Boinc itself is 32bit but the science projects it runs are often 64bit hence my preference for fatdog.

Boinc has a client and a manager started within the bonc folder by a couple of scripts. Boinc client seems to be running OK having changed permissins but the manager not.

I have BOINC (folder) still in /root/spot/Downloads/BOINC where run manager looks like this (according to Geany):

cd "/root/spot/Downloads/BOINC" && exec ./boincmgr $@

I have read other threads indicating 32 bit programs need to be started with start32

Q1. am I good leaving the folder where it is?

Q2. Should I change run manager to include start32 ??

Once this is running it will have no other tasks or other programs running although I am hoping to adapt Boinc to run entirely in memory at some stage.

It is possible to circumvent running the manager by entering required info via CLI but, for me at least, graphically, using the manager, is easier.

A little guidance for a noob from one of you adepts would be much appreciated.

[kirk]

OldChap, you're referring to http://boinc.berkeley.edu/ ? If so I don't see where it needs 32bit libraries, but it does need wxwidgets and it's compiled against some older libraries. Wxwidgets is not in the repo yet. I'll get one in there this week along with a package for Bonic.

[Rangan Masti]

Hi, sorry i dont find glibc-2.19 in 32bit-slacko-3.sfs for Fatdog64 700 alpha1.

[jamesbond]

@Rangan Masti - the 32bit sfs is still the old sfs from the 600 series, based on slacko 5.3.3 so it won't have the latest glibc etc. It's just a temporary measure so people migrating from 631 can use 32-bit software.

Going forward, we will probably adopt the latest slacko (6.0 at the time of writing) and convert it into 32-bit library. Alternatively we can also build our own 32-bit library from scratch the way that Fatdog64 is build from scratch - but due to resource constraint this isn't likely. If you really really need the latest library *NOW*, then consider this method instead.

@gcmartin, I will consider that adding the pre-defined structure, but those will never live in /root/tftpd again; it will go elsewhere (either /var/lib/tftp or /srv/tftp - haven't decided yet).

[jamesbond]

Note to package/SFS contributors: the contribution upload page for 700 is now open. Use "upload700.cgi" to upload to 700 packages (and SFS). The original "upload.cgi" will stay for uploading 600 packages. Same userid and password for either 600 and 700 uploads.

Checking of uploaded packages is done in "contrib700". The original "contrib" directory will stay to check uploaded package for 600.

Uploaded 700 packages will go here: http://distro.ibiblio.org/fatdog/contrib/packages/700/.
Uploaded 600 packages will go here: http://distro.ibiblio.org/fatdog/contrib/sfs/700/.