Fatdog64-630 & 631 Final (May 12 2014)

A home for all kinds of Puppy related projects
Message
Author
jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#196 Post by jamesbond »

Atle wrote:Hi...

Have installed Scribus 1.4.1 from PPM.

Then it requested libpython 2.6.so.0.1, but there is just python 2.7.5
There is python 2.6.6 (which is the python from devx) in the FPM. Unfortunately they are listed in two different categories so it is not so obvious: so click "hide categories" checkbox at the bottom of the FPM then search for python. You will then see both versions.

Wognath, I never install debs myself. The script that install debs are old. Let me check it later.
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]

Atle
Posts: 596
Joined: Wed 19 Nov 2008, 12:38
Location: Oslo, Norway
Contact:

#197 Post by Atle »

Thanks JamesBond...

Worked PERFECTLY.. :D [/quote]

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

Re: Bibletime

#198 Post by jamesbond »

Jim1911 wrote:Hi Kirk and James,

Your latest Fatdog64-630 is working great, however my favorite program, Bibletime, has numerous updates since your last update of it. Please consider updating it for Fatdog64-630. We Bibletime users really appreciate your continued support for this fine program with your great operating system.
Hi Jim,
I've just uploaded Bibletime 2.10.0 (latest as of today) to the repo. If you already run the previous version, uninstall:
- older bibletime
- older sword.
- but keep the clucene.

I have bundled the sword library together with the bibletime package. I have only done minimal testing (ie it launch and I can download the BBE bible and read it). Let me know if you have any problems with it.
sunny wrote:I would note that the files in these pixbuf subdirectories are not the same. Which are the right ones?
Both are the correct ones. They are part of gdk-pixbuf (generic pixbuf interface and the Xlib-specific implementation). As for which ones to you - that depends on what you want to do with it.

@prehistoric, thanks for the note.

DrDeaf, I don't use Easy2Boot so I can't really tell why. Nothing seriously changed between 621 and 630 in terms of booting scripts or anything.

cheers!
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]

User avatar
neerajkolte
Posts: 516
Joined: Mon 10 Feb 2014, 07:05
Location: Pune, India.

#199 Post by neerajkolte »

DrDeaf wrote:I have to say that I don't feel that spot (or not) is really a problem. I have never encountered anything that I could not fix by just changing what I am doing. Having a choice is nice.

When something just suddenly doesn't run though, it is more difficult. Here's an example...

I always boot my notebook off of USB one of two ways. One is to use Grub4Dos, and just choose the partition I want to boot. Never a problem with this, with any Pup I have tried. "It just works".

The second way is to install Easy2Boot and simply toss the freshly downloaded ISO to it and go! It doesn't get any cleaner than this.

A problem with Easy2Boot is that some Pups hang in the middle of bootup. LH64 does this ("LH64-602.sfs not found"). However, until 630, FD has always booted with Easy2Boot. Now with 630, it hangs a bit earlier than other Pups.

Using 630, Easy2Boot works as usual, copies to RAM and then hangs with this line: Booting the kernel.

What changed to cause this in 630? Can it be fixed?
Thanks in advance!
I have installed Fatdog64-630 on my usb stick using many methods( yummi, universal installer, fatdogs own installer, even have used dd.) never had problem in booting.
After reading your comment I downloaded easy2boot and installed it on my usb.
I have successfully booted both Fatdog64-630 and precise puppy from it.
Also I have made e2b usb from both windows7 and my fatdog64. Both times it worked and boots fine. Are you using latest version of e2b. Because I even didn't have to worry about .mnu file I just placed my ISOs in mainmenu folder. I have also tested them by placing in Linux folder.
I didn't encounter any prob.
Last edited by neerajkolte on Fri 07 Mar 2014, 15:38, edited 1 time in total.
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson

“We tend to overestimate the effect of a technology in the short run and underestimate the effect in the long run.â€￾
- Amara’s Law.

Sunny
Posts: 35
Joined: Tue 20 Oct 2009, 23:11

Question on fd64-devx_630.sfs

#200 Post by Sunny »

Both are the correct ones. They are part of gdk-pixbuf (generic pixbuf interface and the Xlib-specific implementation). As for which ones to you - that depends on what you want to do with it.
Thanks for that reply jamesbond, but I understood that part of it. What seems to be the problem is that the subdirectories gdk-pixbuf and gdk-pixbuf-xlib are included in /usr/include/gtk-2.0 ... but they are also in /usr/include/gdk-pixbuf-2.0

For example, the individual files in /usr/include/gtk-2.0/gdk-pixbuf have the same names as the files in /usr/include/gdk-pixbuf-2.0/gdk-pixbuf ... but the files are different.

If I had to hazard a guess, it seems to me like the subdirectories (gdk-pixbuf & gdk-pixbuf-xlib) should not be in the directory /usr/include/gtk-2.0 (I believe this is where the old versions of gdk-pixbuf put them, but the newer versions are putting them in /usr/include/gdk-pixbuf-2.0)

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

Re: Question on fd64-devx_630.sfs

#201 Post by jamesbond »

Sunny wrote:Thanks for that reply jamesbond, but I understood that part of it. What seems to be the problem is that the subdirectories gdk-pixbuf and gdk-pixbuf-xlib are included in /usr/include/gtk-2.0 ... but they are also in /usr/include/gdk-pixbuf-2.0
Thank you for the clarification. Of course I had to miss the original question - doh! :(
For example, the individual files in /usr/include/gtk-2.0/gdk-pixbuf have the same names as the files in /usr/include/gdk-pixbuf-2.0/gdk-pixbuf ... but the files are different.

If I had to hazard a guess, it seems to me like the subdirectories (gdk-pixbuf & gdk-pixbuf-xlib) should not be in the directory /usr/include/gtk-2.0 (I believe this is where the old versions of gdk-pixbuf put them, but the newer versions are putting them in /usr/include/gdk-pixbuf-2.0)
You're right. The ones in gtk-2.0 are the old ones and can safely be ignored (or deleted). I checked against devx for 521. Thanks for pointing this out; did you ever have problems because of them?
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]

Sunny
Posts: 35
Joined: Tue 20 Oct 2009, 23:11

Question on fd64-devx_630.sfs

#202 Post by Sunny »

I did run into a problem when compiling one of the dependencies for osmgpsmap. The way the library path was set up in FatDog (I did not change any paths when I configured it), the compiler decided to use the old gdk-pixbuf files. All I had to do was delete the gdk-pixbuf and gdk-pixbuf-xlib subdirectories in /usr/include/gtk-2.0 ... the compiler then used the correct versions in /usr/include/gdk-pixbuf-2.0

DrDeaf
Posts: 69
Joined: Sat 30 Dec 2006, 14:10

#203 Post by DrDeaf »

neerajkolte wrote: After reading your comment I downloaded easy2boot and installed it on my usb.
I have successfully booted both Fatdog64-630 and precise puppy from it.
Also I have made e2b usb from both windows7 and my fatdog64. Both times it worked and boots fine. Are you using latest version of e2b. Because I even didn't have to worry about .mnu file I just placed my ISOs in mainmenu folder. I have also tested them by placing in Linux folder.
I didn't encounter any prob.
Yes, the mainmenu method is the only one for me! The mnu examples varied widely from OS to OS (linux) and with no example for FD, I decided to pass. I discarded that option when I first began to figure out how I wanted to handle my boot.media.
However, congratulations on your successes! Although I keep my USB locked "RO" and a corruption is unlikely I am trying to get a fresh download. It keeps stalling out after a few hundred KB however and I may not be able to get it until I return to "First World" internet quality. in April
One item of interest: While repeating the download efforts I was looking around the site and I saw a notice posted yesterday of a forthcoming ISOPUP extension for us! Perhaps there have been others with problems.

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#204 Post by nooby »

Not to derail this fine thread could you give a link to isopup?
I failed to find it. Send me PM if that suites you.
I use Google Search on Puppy Forum
not an ideal solution though

DrDeaf
Posts: 69
Joined: Sat 30 Dec 2006, 14:10

#205 Post by DrDeaf »

nooby wrote:Not to derail this fine thread could you give a link to isopup?
I failed to find it. Send me PM if that suites you.
Hello there, nooby! You are always a fun read.... Well, if you hit the word "notice" in my post above you should reach the URL for the "isopup" news. I just tested it and it worked for me :) However, YMMV (never know what will happen). So, here is the link:

http://www.easy2boot.com/news/e2b-v-130-coming-soon-/

Cheers!

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#206 Post by nooby »

Thanks my imagination failed me. You talk about
E2B v.1.30 coming soon!

I had better luck with rcrsn51 and his isobooter.

I guess E2B is a good program too butmy poor brain
did know what to do reading the instructions for isobooter
and failed to remember all the details of how to set up
E2B versions.

So I derailed and will step back.

I only use frugal install of FatDog
and will try to use it on the UEFI machine within some months :)
I use Google Search on Puppy Forum
not an ideal solution though

User avatar
Ted Dog
Posts: 3965
Joined: Wed 14 Sep 2005, 02:35
Location: Heart of Texas

Fatdog64 630 fixed 8G boundaries issues

#207 Post by Ted Dog »

Unexpected surprise multisession now works past 8G which it did not before on last versions of Fatdog64. I am really sure it was not my retooling of remaster and fast methods on my box for the fastdog project that could have accounted for the improvements.. Just did not test it since last version looked as if the 8G was a legacy style bug to growisofs ie unfixed due to age.

So the sky is the limit.. or at least to end of logical size of normal el cheapo 25G BD media which is 23.54G in real world terms.

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

Re: Fatdog64 630 fixed 8G boundaries issues

#208 Post by jamesbond »

Ted Dog wrote:Unexpected surprise multisession now works past 8G which it did not before on last versions of Fatdog64. I am really sure it was not my retooling of remaster and fast methods on my box for the fastdog project that could have accounted for the improvements.. Just did not test it since last version looked as if the 8G was a legacy style bug to growisofs ie unfixed due to age.

So the sky is the limit.. or at least to end of logical size of normal el cheapo 25G BD media which is 23.54G in real world terms.
It was fixed thanks to rcrsn51. He got a bluray drive just for this purpose and tested all combinations of burns and fixes; and he finally found the fix, which is incorporated in 630.

Speaking of which, I haven't seen him around, I hope he's okay.

cheers!
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]

gcmartin

#209 Post by gcmartin »

Speaking of missing; We haven't seen much of @Pemasu, or @TaZoC this year either. Hope they, along with @Rcrsn51, are still around. They have contributed so much to this community.

Peace be with you

User avatar
neerajkolte
Posts: 516
Joined: Mon 10 Feb 2014, 07:05
Location: Pune, India.

Running Windows in Virtualbox 4.2.4

#210 Post by neerajkolte »

Hello everyone,
I have downloaded virtualbox4.2.4 sfs from sfs manager in control panel and loaded it.
But I could not start virtualbox from it's menu entry under system section.
So I ran it from urvxt and got

Code: Select all

#virtualbox
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
         available for the current kernel (3.12.9) or it failed to
         load. Please recompile the kernel module and install it by

           sudo /etc/init.d/vboxdrv setup

         You will not be able to start VMs until this problem is fixed.
The program started but showed this error. I could create virtual machine but could't start it.
So I ran

Code: Select all

# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules ...done.
Recompiling VirtualBox kernel modules ...failed!
  (Look at /var/log/vbox-install.log to find out what went wrong)
Looking at log I got
/opt/VirtualBox/src/vboxhost/build_in_tmp: line 62: make: command not found
So I downloaded fd64-devx_630.sfs and loaded it.
But again "vboxdrv setup" failed and log reads
Makefile:181: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
I got from system info that my kernel is 3.12.9.
But in sfs manager I couldn't find its kernel source sfs.
There are sfs for 3.11.4 and 3.8.7.
Could anyone tell me where to find it.
Thanks in advance...
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson

“We tend to overestimate the effect of a technology in the short run and underestimate the effect in the long run.â€￾
- Amara’s Law.

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

#211 Post by smokey01 »

I got from system info that my kernel is 3.12.9.
But in sfs manager I couldn't find its kernel source sfs.
There are sfs for 3.11.4 and 3.8.7.
Could anyone tell me where to find it.
Thanks in advance...
http://ftp.nluug.nl/ftp/pub/os/Linux/di ... 3.12.9.sfs

User avatar
neerajkolte
Posts: 516
Joined: Mon 10 Feb 2014, 07:05
Location: Pune, India.

#212 Post by neerajkolte »

Thanks Smokey,
I will download it n report back.

Hmm.. 99mb this will take almost 2hrs on my android's slow 2G net connection
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson

“We tend to overestimate the effect of a technology in the short run and underestimate the effect in the long run.â€￾
- Amara’s Law.

sys64738
Posts: 1
Joined: Sat 15 Mar 2014, 10:46
Location: Hanau Germany

Clonezilla in FD64?

#213 Post by sys64738 »

Hi all,
I like FD64_630 and this forum !

In FD64 i've found some clone/partition tools (gparted, ntfsclone ...)
My favorite tool "clonezilla" is missing, but perhaps i can load/install a working PET/SFS.
Is there a ready package out, i can't find it anywhere.

THX in advance.

User avatar
neerajkolte
Posts: 516
Joined: Mon 10 Feb 2014, 07:05
Location: Pune, India.

Running Windows in Virtualbox 4.2.4

#214 Post by neerajkolte »

Thanks Snokey.
I downloaded kernel-source-3.12.9.sfs and loaded it.
now when I run "/etc/init.d/vboxdrv" setup it again say failed. And log file reads as....
make KBUILD_VERBOSE=1 SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 CONFIG_MODULE_SIG= -C /lib/modules/3.12.9/build modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
echo >&2; \
echo >&2 " ERROR: Kernel configuration is invalid."; \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo >&2 ; \
/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f scripts/Makefile.build obj=/tmp/vbox.0
gcc -Wp,-MD,/tmp/vbox.0/linux/.SUPDrv-linux.o.d -nostdinc -isystem /usr/lib64/gcc/x86_64-t2-linux-gnu/4.6.2/include -I/usr/src/linux-3.12.9/arch/x86/include -Iarch/x86/include/generated -Iinclude -I/usr/src/linux-3.12.9/arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I/usr/src/linux-3.12.9/include/uapi -Iinclude/generated/uapi -include /usr/src/linux-3.12.9/include/linux/kconfig.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m64 -mno-mmx -mno-sse -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_AVX=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -Wframe-larger-than=1024 -fno-stack-protector -Wno-unused-but-set-variable -fomit-frame-pointer -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -DCC_HAVE_ASM_GOTO -include /tmp/vbox.0/include/VBox/SUPDrvMangling.h -I/lib/modules/3.12.9/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -I/tmp/vbox.0/vboxdrv/ -I/tmp/vbox.0/vboxdrv/include -I/tmp/vbox.0/vboxdrv/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DCONFIG_VBOXDRV_AS_MISC -DRT_ARCH_AMD64 -DVBOX_WITH_64_BITS_GUESTS -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(SUPDrv_linux)" -D"KBUILD_MODNAME=KBUILD_STR(vboxdrv)" -c -o /tmp/vbox.0/linux/.tmp_SUPDrv-linux.o /tmp/vbox.0/linux/SUPDrv-linux.c
/tmp/vbox.0/linux/SUPDrv-linux.c: In function 'vboxdrvLinuxUid':
/tmp/vbox.0/linux/SUPDrv-linux.c:226:5: error: incompatible types when returning type 'kuid_t' but 'RTUID' was expected
/tmp/vbox.0/linux/SUPDrv-linux.c: In function 'vboxdrvLinuxGid':
/tmp/vbox.0/linux/SUPDrv-linux.c:235:5: error: incompatible types when returning type 'kgid_t' but 'RTGID' was expected
/tmp/vbox.0/linux/SUPDrv-linux.c: In function 'vboxdrvLinuxEuid':
/tmp/vbox.0/linux/SUPDrv-linux.c:244:5: error: incompatible types when returning type 'kuid_t' but 'RTUID' was expected
/tmp/vbox.0/linux/SUPDrv-linux.c:248:1: warning: control reaches end of non-void function [-Wreturn-type]
/tmp/vbox.0/linux/SUPDrv-linux.c: In function 'vboxdrvLinuxUid':
/tmp/vbox.0/linux/SUPDrv-linux.c:230:1: warning: control reaches end of non-void function [-Wreturn-type]
/tmp/vbox.0/linux/SUPDrv-linux.c: In function 'vboxdrvLinuxGid':
/tmp/vbox.0/linux/SUPDrv-linux.c:239:1: warning: control reaches end of non-void function [-Wreturn-type]
make[2]: *** [/tmp/vbox.0/linux/SUPDrv-linux.o] Error 1
make[1]: *** [_module_/tmp/vbox.0] Error 2
make: *** [vboxdrv] Error 2
I don't have expertise to interpret that. (In plain text "It all went over my head") :wink: :D

Any idea what should I do next....
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson

“We tend to overestimate the effect of a technology in the short run and underestimate the effect in the long run.â€￾
- Amara’s Law.

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

#215 Post by smokey01 »

You should be able to start vbox from the menu under system.

There should also be a script in /usr/local/bin/vbox:

!/bin/sh
depmod
/etc/init.d/vboxdrv start
VirtualBox &

Try this script. It also might be worth a reboot if it doesn't run.

Good luck.

Post Reply