Fatdog 111

[jamesbond]

The link produced a download limit. I guess I will try later :p

[hayagix]

It is great to see these derivatives with newish kernels.

Fatdog is very good. So good, in fact, I've remastered it with a whack of goodies for a neighbour who has shown interest in replacing Vista on a new laptop.

Well done!

[jamesbond]

No the Firefox headers aren't in there, I grabbed the binary from Mozilla. ....

Actually, all those is not needed as I don't need to recompile. I don't even have to install seamonkey. I got pidgin from the official repos working by doing this after installing it.

Code: Select all

ldconfig /usr/lib/firefox

That automagically fixes it. So, I'm happy

Unfortunately the OOO is still not accessible.

[jamesbond]

For the benefit of others...

I'm very surprised and pleased that Virtualbox 2.1.4 install straight away here. I was expecting to have a few problems ... but the installer ("All Distributions i386") worked straight away, not a single error message.

All I needed to do was to add a group named vboxusers (addgroup vboxusers) and assign "root" as its members, and then restart.

Note: Need devx installed as the installer needs to compile vboxdrv kernel module.

Thanks for this release kirk, this fatdog really kicks butt. I'm starting to consider to replace my venerable 2.15CE with this one.

[kirk]

I'm planning on updating Fatdog to 112 next week. If anyone has any bug fixes please post them. Here's what I've got so far:

* upgrade firefox to 3.0.7. (compiled from source this time)
* upgrade Flash 10 to the latest version.
* Grabbed Joe's nightly build of JWM. This will be the default now that fullscreen problems are gone.
* Xine-ui replaces Gxine.
* added /usr/lib/firefox to the LD path.
* include SDL headers.
* upgraded Dougal's network wizard to latest version with Jamesbond's mods.
* upgraded Pburn
* removed module ssb from the initrd.gz, no idea why it was there and it causes problems with bcm43xx and wl.
* upgrade Pfind

I'll be out of town for a few days so there may be a delay in responding.

Thanks!

[techtype]

I'm planning on updating Fatdog to 112 next week. If anyone has any bug fixes please post them. Here's what I've got so far:

* upgrade firefox to 3.0.7.
* upgrade Flash 10 to the latest version.
* Grabbed Joe's nightly build of JWM. This will be the default now that fullscreen problems are gone.
* Xine-ui replaces Gxine.
* added /usr/lib/firefox to the LD path.
* include SDL headers.
* upgraded Dougal's network wizard to latest version with Jamesbond's mods.
* upgraded Pburn
* removed module ssb from the initrd.gz, no idea why it was there and it causes problems with bcm43xx and wl.

I'll be out of town for a few days so there may be a delay in responding.

Thanks!

Firefox 3 is not stable on your pup. You need to add the gtk-core-update and glib-2.20.0-i386-stripped pets to fix this as discussed on this forum. Abiword is updated to at least 2.6.6. Pfind is updated to v4.7.
It would be wonderful if you could see your way to add grey's xfce-4.6 pet and his associated plugins!! I think you would love the resulting look and functionality.

[WhoDo]

* removed module ssb from the initrd.gz, no idea why it was there and it causes problems with bcm43xx and wl.

I'll be out of town for a few days so there may be a delay in responding.

Removed from where exactly? Puppy-4.2RC4 users are complaining about this problem and I'd like to fix it for Final due out this Saturday.

Thanks

[kirk]

Firefox 3 is not stable on your pup. You need to add the gtk-core-update and glib-2.20.0-i386-stripped pets to fix this as discussed on this forum. Abiword is updated to at least 2.6.6. Pfind is updated to v4.7.
It would be wonderful if you could see your way to add grey's xfce-4.6 pet and his associated plugins!! I think you would love the resulting look and functionality.

I haven't had many crashes with Firefox in fatdog. I just compiled Firefox 3.0.7 from source in Fatdog, it will be in 112. Changing glibc doesn't seem like a good idea since everything is compiled against it.

I'll look into compiling the latest abiword.

I'll update Pfind.

Xfce is nice, but Fatdog has two window managers now and I like JWM since it's been fixed, so I'll have to say no on that.

Thanks for your help techtype.


WhoDo,

The ssb module I'm removing is in the initrd.gz. I don't know why it's there, I think ssb is a wifi module and with it there you would not be able to blacklist it. You can expand the initrd.gz like this:

# gunzip initrd.gz
# mkdir puppy-init
# cd puppy-init
# cat ../initrd | cpio -d -i

Then look in ./puppy-init/lib/modules/<kernel version>/kernel/drivers/ssb and delete it. Then do :

# depmod -b <path to the root of your expanded initrd.gz>

You'll need to be running the same kernel version that the modules where built for before running the above depmod command.

Then to re-compress everything:

# cd puppy-init
# find . | cpio -o -H newc | gzip -9 > ../initrd.gz

You might want to ask Barry if there's any reason he put it there.

EDIT: WhoDo, if you delete the ssb module from the initrd.gz, make sure it's in the main sfs file. Barry might have cut it to save some space.

[techtype]

OK, but before you dismiss my report on Firefox --- try this:

There is a quick check that can be performed for Firefox stability on any pup or other Linux release: go to the my.yahoo.com page (assuming you have it set up to include lots of news headlines), then run the cursor up and down over the news stories for several seconds, pausing sometimes to trigger the javascript that displays more of the story. If Firefox is unstable, the browser will disappear without a trace. If Firefox is stable, you can do this all day without a problem. Mark's final Muppy releases are stable and so is the "Unnamed Pup" and releases built from it. (like Newyears pup) Many releases that include Firefox 2 are stable, but most that include Firefox 3 are not.

Your pup fails this test. This will happen on other javascript pages but is not so easily tested.

[kirk]

Techtype,

Your right. Firefox 3.0.7 I just compiled crashes on that page. If the problem is really glibc, that's a big problem. If it's replaced, all the other libraries should be recompiled. If you just change glibc and the GTK libraries, you may fix Firefox, but have other things become unstable. I did a T2 build a few months ago, but I wasn't happy with Xorg 7.4. I'll have to give this some thought. Might just switch to another browser. I left Seamonkey because Openbox didn't handle it's download dialogs correctly. But now that I'm back with JWM by default that's not as big of a problem. I like Opera 10a too, though it's got it's problems.

[jamesbond]

I run Fatdog 111 with FF 3.0.7 binaries I got from mozilla.
Deleted the original 3.0.6 (rm -rf /usr/lib/firefox) and untar the 3.0.7 to the same location.

I went to my.yahoo.com doesn't crash my firefox and it works ok, I can page up and down several times.

[jamesbond]

Based on information from MU, wow and others much smarter than me, I have modified my init script.

Kirk if you are interested I can pass you my updated init script which allow up to 13 SFS to be mounted (instead of 3).

It's just a simple modification and I extend the loop (rather than be start and autodetect the number of SFS...) ... but that does the job for me.

For this to work, the kernel parameter max_loop=18 must be added when you install. Also need to create the extra loop devices inside initrd.

@Whodo - assuming that Fatdog 111, 4.1.2 and 4.2 inherits the same init script, this change will instantly allow 4.2 to use up to 13 SFS. But if you have changed the init script meanwhile, then better stick with what you've already got.

[techtype]

I went to my.yahoo.com doesn't crash my firefox and it works ok, I can page up and down several times.

Paging up and down has nothing to do with the test for crashing.

[jamesbond]

I went to my.yahoo.com doesn't crash my firefox and it works ok, I can page up and down several times.

Paging up and down has nothing to do with the test for crashing.

Ok, I also tried to cursor up and down. No crash either.

[techtype]

I went to my.yahoo.com doesn't crash my firefox and it works ok, I can page up and down several times.

Paging up and down has nothing to do with the test for crashing.

Ok, I also tried to cursor up and down. No crash either.

That sounds very promising then!!! Let's hope you have identified another route to a fix. (':D')

[jamesbond]

More updates:

1. mount.cifs is missing. So mount to CIFS share can only use the older protocol smbfs. (got a warning in dmesg that smbfs is deprecated and will be removed in kernel 2.6.27 - but we're already in 2.6.28 and it's still working?)

2. missing symlink /sbin/mount.smbfs . Without this, mount -t smbfs will fail, it forces you to use smbmount.

[jamesbond]

That sounds very promising then!!! Let's hope you have identified another route to a fix. (':D')

I definitely hope so

[jamesbond]

More updates:

2. missing symlink /sbin/mount.smbfs . Without this, mount -t smbfs will fail, it forces you to use smbmount.

Actually when I tried with smbmount, that doesn't connect to my CIFS share (which is a WD Mybook World Edition). smbclient works ok.

Got to test it with other CIFS shares ...

[jamesbond]

Test with W2003 CIFS shares - didn't work - it says smb signing is required (only cifs supposed signing, not smbmount)

I guess we need mount.cifs ...

[jamesbond]

I got mount.cifs source from here: http://mirrors.ibiblio.org/pub/mirrors/ ... unt.cifs.c

Do a compile, put it to /sbin and we fly !
I've tested it with my CIFS share with WD and it works.

Attached is the source and the compiled mount.cifs in tar.gz, and a dotpet for easy install.

cheers!