"So it appears that legacy GRUB can't load the new large initrd file out of ext4."

See that did lurk somewhere in the dark corner of my poor brain.
the Instant that I saw that FatDog had ext4 savefile then my body told me.
Something goes wrong with ext4 use ext3 instead. Now we know why
I reacted to that term ext4

Ahaha yeah, related problem but not exactly the same. The problem is not about ext4 in savefile, but booting the system from ext4 partition (Fatdog doesn't offer any automated way to create ext4 partition - this must be done consciously when one uses gparted). Legacy grub has not been updated for a long time anyway; its replacement, grub2, supports ext4 and other more exotic filesystems (e.g. btrfs) which has no hope of ever being supported in legacy grub. That being said, grub2 has its own share of problems ...

01micko wrote:

You've seen the one I made in Slacko? Just layered the puppy icon over the binary icon.. lazy as it gets! (But effective )

Right! We did that one with the samba share, should probably do that for these icons too ..._________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.

"So it appears that legacy GRUB can't load the new large initrd file out of ext4."

See that did lurk somewhere in the dark corner of my poor brain.
the Instant that I saw that FatDog had ext4 savefile then my body told me.
Something goes wrong with ext4 use ext3 instead. Now we know why
I reacted to that term ext4

Today I wanted to boot a previous version which was put aside together with some other on a DVD as data so it wasn't bootable anymore .
To make it bootable again I realized how useful is ' ISOMASTER ' which I found it in Lighthouse 64 5.14 B2.
I think at least a pet if not inside a future release , could be a useful tool .
Installing fron fatdog 500 repo the FB Reader pet seemed OK , but it does not start.

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.

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

The above assumes your files are in sd3 and the directory is fd64b1_________________Puppy Software <-> Distros <-> Puppy Linux TipsLast edited by smokey01 on Sat 30 Jun 2012, 18:36; edited 2 times in total

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

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.

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

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 ....

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 ....

DC wrote:

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

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._________________I use Google Search on Puppy Forum
not an ideal solution though

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum