Fatdog64-600b2

[kickstart]

OK I now have FD600 booting successfully from its own directory on a ext4 partition. However the savefile no longer has the option to be created within a subdirectory, only directly into the partition. I have tried moving the savefile into the fd600 directory as I have with other frugal installs but the system cannot find it on boot up. I have attempted to edit the /etc/rc.d/rc.sysinit file to point to the savefile location but I don't really know what I'm doing and it doesn't work. Any changes made disappear on reboot. Anybody have any advice or do I just have to accept this stray savefile in the partition.

[smokey01]

Have you tried this:
savefile=direct:device:sda3:/fd64b1/fd64save.ext4

The above assumes your files are in sd3 and the directory is fd64b1

[capicoso]

Hey. I compiled a program, puredata, that needs libc 2.15. And fatdog comes with < 2.14. Would it be safe to update it myself? Or is there any chance that you could include an uptated version of it for the final release? thanks

[kickstart]

Have you tried this:
savefile=direct:device:sda3:/fd64b1/fd64save.ext4

The above assumes your files are in sd3 and the directory is fd64b1

Tried it with directory name changed to suit but system still couldn't find it at boot. I'm not sure I am inserting the line in the correct location as I'm inexperienced in writing scripts, editing files etc. I'll have another look later, got an early start for a classic bike run in the morning.

[rcrsn51]

I'm not sure I am inserting the line in the correct location

In your menu.lst entry:

Code: Select all

kernel /fd64b1/vmlinuz savefile=direct:device:sda3:/fd64b1/fd64save.ext4

Please post the entry you have now.

[DC]

Hi,

booting the system from a ext4 partition with legacy grub

All my frugals are in a ext4 partition and have been for months.
Before my problem with Fatdog600b1 and Fatdog600b2.
Fatdog600A2 was quite happily booting from my frugal partition using legacy grub.
So maybe legacy grub might be the main problem but I think one other little thing pushed it over the edge.
I'm happy with grub4dos as I never got on with grub2

best regards

DC

[jamesbond]

I have compiled geeqie in fd64-600b1.

It's a great little graphics viewer / photo manager but unfortunately it doesn't have a function to send photos by email.

It's fast and what I really like about it, it doesn't created a lot of thumbnails, taking up additional disk space and it's a single binary.

Works very well in Fatdog.

Many thanks, I stripped the binary and uploaded this to the pet repo.

[jamesbond]

Hey. I compiled a program, puredata, that needs libc 2.15. And fatdog comes with < 2.14. Would it be safe to update it myself? Or is there any chance that you could include an uptated version of it for the final release? thanks

Hi,

Sorry, it would be unlikely to update glibc. Glibc is the foundation used by *almost all* programs and updating it can have unforeseen consequences. The safest way to update glibc is to get a new glibc and re-build everything.
That being said, some have successfully compiled latest glibc and just plug it in to their system and everything seems fine ... so take the warning above is a grain of salt; it is just a warning.

I've never done puredata before. I know it is a music app, I wonder though what is its business requiring the latest glibc? It could perhaps be hacked to compile with earlier glibc too ....

I'm happy with grub4dos as I never got on with grub2

That makes two of us.

[capicoso]

Hey. I compiled a program, puredata, that needs libc 2.15. And fatdog comes with < 2.14. Would it be safe to update it myself? Or is there any chance that you could include an uptated version of it for the final release? thanks

Hi,

Sorry, it would be unlikely to update glibc. Glibc is the foundation used by *almost all* programs and updating it can have unforeseen consequences. The safest way to update glibc is to get a new glibc and re-build everything.
That being said, some have successfully compiled latest glibc and just plug it in to their system and everything seems fine ... so take the warning above is a grain of salt; it is just a warning.

I've never done puredata before. I know it is a music app, I wonder though what is its business requiring the latest glibc? It could perhaps be hacked to compile with earlier glibc too ....

I'm happy with grub4dos as I never got on with grub2

That makes two of us.

Re build all programs? ouch. I tried updating it, somethings got broken like, i couldn't configure anything(gcc can't make executables!), And my system suddenly was at 70% cpu.
Puredata is a graphical programming language. The user connects objects with other objects, those objects do things, like fft, convert signals. They're programmed on C. Maybe for that... Why the latest glibc i don't know(they always work with latest ubuntu, and latest ubuntu has latest glibc, maybe that's why) ... It's not the official PD i want to use tho. It's one named pd-l2ork. That's only available for linux and is the best so far(that's one of the reasons i moved 100% to linux)...The problem is that they delete older versions from the webpage. Maybe i could email them to give me an older one... The older ones i have are for 32bit... How do you think i could make it work with earlier glibc?
The worst part(for me) is that it's the main program i use.

BTW. Puredata relies on tk and tcl. They're in the fatdog repo, i downloaded them but puredata still couldn't see them. Puredata was looking for tk8.5.so.0 and the lib was named tk8.5.so. I had to add .0 to the lib and got fixed. I don't know if it's a puredata problem or the libs...
Thhanks

BTW2. I'm also happy with grub4DOS!

edit: Loaded my savefile before attempting to update glibc and did it again paying more attention and all... Now everything works fine... at least it looks like it... I'm a bit scared though, what programs can i run to see if i didn't corrupt them?
thanks again

[nooby]

This ibibilio is too slow. Took 30 minutes or more despite fast LAN.
Sure I should wait for the mirrors but them take days to get
the files. Should I send money to Smokey or somebody else so they
accept to have a FatDog in their Kennel

Anyway being lazy I reused the old savefile from B2 for this RC
version and it just works. AFAIK have not tested much.

[Billtoo]

Booting from dvd with savefile.

Computer
Processor 2x Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz
Memory 4045MB (158MB used)
Machine Type Physical machine
Operating System Fatdog64 [54d320f566]
User Name root (root)
Date/Time Sun Jul 1 07:02:20 2012

Operating System
Version
Kernel Linux 3.4.4 (x86_64)
Version #1 SMP Sat Jun 23 18:31:59 GMT 2012
C Library GNU C Library version 2.13 (stable)
Distribution Fatdog64 [54d320f566]

Display
Resolution 1440x900 pixels
Vendor The X.Org Foundation
Version 1.11.4

OpenGL
Vendor NVIDIA Corporation
Renderer GeForce GT 220/PCIe/SSE2
Version 3.3.0 NVIDIA 295.59
Direct Rendering Yes

The pvr is working in VLC, thanks for that.

Just started but no problems so far.

[rcrsn51]

Has anyone been able to make a bootable flash drive with b2? Mine never get past

Code: Select all

Loading initrd.....................................

[jamesbond]

Has anyone been able to make a bootable flash drive with b2? Mine never get past

Code: Select all

Loading initrd.....................................

I did. I didn't do anything special. Flash drive booting is very flaky and depends on the BIOS. Anyway, perhaps your system doesn't like the huge initrd. You can try to use the small initrd - use the installer for that and choose "small initrd" when asked. This will basically take the fd64-600.sfs outside initrd and make the initrd a lot smaller (like, 4 MB instead o 196MB). By default it won't load fd64-600.sfs to RAM, if you want that you can add "base2ram=yes" as boot parameter.

Billtoo - you're fast

[01micko]

Posting from freshly downloaded Iron browser through SFS Manager, no hitches ..apart from slow internet!

<rant>c'mon Julia... it's 2012 already.. we pay Carbon Tax!</rant>

Used the installer for a change, done what I told it! That's exactly what it's supposed to do. Manually adjusted menu.lst (grub4dos been there for awhile)

More as I test. Looking nice.

[rcrsn51]

choose "small initrd" when asked.

I can't find this option.

[01micko]

choose "small initrd" when asked.

I can't find this option.

It's in the installer, I just saw it, a checkbox.

[jamesbond]

choose "small initrd" when asked.

I can't find this option.

You may not have enough memory (the operation uses /tmp and /tmp must be at least 800MB) ... just run this from terminal:

Code: Select all

fatdog-split-initrd.sh /path/to/your/original/initrd /output/path [/path/to/optional/tmp/dir]

.
The operation will decompress the entire fatdog and recompress it, it takes quite a while and also a lot of memory on the /tmp/dir. By default it uses /tmp, but if your /tmp is less than 800MB you'd better specify it elsewhere (e.g /mnt/sda3/tmp, etc).

The original initrd is unchanged, the output dir will be filled in with "small initrd" and "fd64-600.sfs". Why the need to decompress the entire stuff? Because we need to move/merge kernel modules from initrd to the main sfs. By doing this, you are reverting fatdog back to the standard puppy 3-files format: vmlinuz, initrd, fd64-600.sfs. Keep your original initrd, there is no way get it back once the splitting is done

[jamesbond]

PS:
- isomaster is in the package repository.
- fbreader is in the package repository (the desktop version is stuck at version 0.12.10? They are focusing on android now? !@#%$#)
- miredo (as discussed here) is in the package repository.

[jamesbond]

Puredata is a graphical programming language. The user connects objects with other objects, those objects do things, like fft, convert signals. They're programmed on C. Maybe for that... Why the latest glibc i don't know(they always work with latest ubuntu, and latest ubuntu has latest glibc, maybe that's why) ... It's not the official PD i want to use tho. It's one named pd-l2ork. That's only available for linux and is the best so far(that's one of the reasons i moved 100% to linux)...

Interesting, I need to check it out sometime.

The problem is that they delete older versions from the webpage. Maybe i could email them to give me an older one...

They are not the only ones. Try for example find the older sources for Fotoxx ... which doesn't use gtk3

The older ones i have are for 32bit... How do you think i could make it work with earlier glibc?

If you have the sources you can try to hack the autoconf/configure files to allow building with earlier version of glibc; when the compile fails then find the offending functions and find a replacement which is available in earlier glibc. Sorry I can't go further than that unless I look at the source.

The worst part(for me) is that it's the main program i use.

Ouch!

BTW. Puredata relies on tk and tcl. They're in the fatdog repo, i downloaded them but puredata still couldn't see them. Puredata was looking for tk8.5.so.0 and the lib was named tk8.5.so. I had to add .0 to the lib and got fixed. I don't know if it's a puredata problem or the libs...

Libs problem. All libs should have something that ends with so.0 or so.1 etc, and there a symlink from .so to .so.0.

edit: Loaded my savefile before attempting to update glibc and did it again paying more attention and all... Now everything works fine... at least it looks like it... I'm a bit scared though, what programs can i run to see if i didn't corrupt them?

Well if you system can boot to desktop, the usual apps works (e.g geany, abiword, qtractor, libreoffice etc) then you should be safe enough. As usual, no guarantee

[jamesbond]

600rc release announcement here: http://murga-linux.com/puppy/viewtopic.php?t=79424.