Muppy 008.4c (final release)

[Fishy]

Same Problem as Ray had. Downloaded DVD-EN twice, verified it both times, burned on different DVD media with same result.

ASUS P5K
Samsung DVD Burner
4 gig of ram

[MU]

Fishy, please copy msy_084.sfs to your harddrive.
Muppy should find and mount it there then, not from the DVD.

Does that work?
Mark

[PaulBx1]

Hello Mark, I am fishing around for another distro again, time to take another look at Muppy.

Question. I have read that packages installed should be installed on the same kernel version that they were compiled with, for best compatibility. Since you have made Muppy compatible with Slackware 12.1 (which uses kernel 2.6.24.5), shouldn't Muppy use kernel 2..6.24.5?

What sorts of encryption support are here? Scramdisk? Truecrypt? Dm-crypt? Enigmail? Gnupg? I guess I should download and have a look. I'll do that...

I have not read all through this 15-page thread.

[MU]

Paul,

Question. I have read that packages installed should be installed on the same kernel version that they were compiled with, for best compatibility.

This concerns Kernelmodules.
For example, you could not use wifi drivers (that use Kernelmodules) from Slackware.
I prefer to stay with Puppys Kernel here, as there is a lot of support for them in the Forum.
Also I would have to recompile the slackware Kernel, as we need aufs and squashfs, what requires a patched kernel.
So even such a patched kernel would bear the risk of incompatibility.

But as we have to decide now for one new alternative to the old 2.6.21.7 (because it lacks support for modern hardware like some netbooks), I took the newest (2.6.27), and made a Puppy Test Iso available:
http://www.murga-linux.com/puppy/viewto ... 771#239771

If for that one I would get reports, that it works fine, I would use that.
We then would have a selfcompiled one with everything required included to compile custom modules if needed.
But out of the box it already comes with a wide hardware support, that had to be added as 3rd partymodule in older versions.

Concerning encryption: please look it up, you have more experience.
The new Kernel has many encryption modules, so the next Muppy should fulfill all your needs, if the current misses some.

Mark

[zgp152]

Muppybackup requires a patched initrd.gz, so it cannot be installed as a pet.

There is just a version with reduced functionality for other Puppys:

http://www.murga-linux.com/puppy/viewto ... 368#222368

But that can not backupp/restore at startup, just backup the running system.

Mark

Thanks for the link. I have a problem however. I have put a description of it to the above cited thread. Rgds ZGP152

[MU]

... removed...

[Béèm]

is Puppy also so slow?
Of course it takes a while to copy 2 gig of data.
And qemu is slow.
But that now looks really extreme.
I have not enough experience with qemu, but as it emulates a whole computer I would think, that there is a driver issue.

No puppy 406 and now 410 didn't have that issue. I could boot the CD and do the Puppy Installer. Not at the same speed as the native installs, but still good performance. So now I know when extracting, the hda1 will have some 2GB. At this point it is I have 2.1GB and the last file is zmsy_84.sfs

Normal drives sometimes can be made faster using "hdparm".
That can set up DMA modes.
So maybe qemus drives cannot use DMA, and so run in a very slow defaultmode.

Mark

Nor K&Ubuntu and Suse 10.3 with their 700MB CD's extracted to some 2GB as well had this issue. I think it took less then an hour to do the respective full installs.

I'll look into hdparm as well.

[Béèm]

In order for the 'report' not being too big I copied the link here of what reported already.

As I left the PC running while I was asleep, I don't know when exactly the copy process stopped and if it did.
I have now 21h running and 2120MB copied and there seems not to be more movement. The last file being copied is the zmsy_084.sfs, so therefor I suppose the copying is done.
As the install script disappeared, I don't have further indications, but I think the only to do still is the grubconfig, which I can do by hand.

Also I see there are 374 processes of which one running. Normal?

After that, the big bang (boot)

[Béèm]

In order for the 'report' not being too big I copied the link here of what reported already.

As I left the PC running while I was asleep, I don't know when exactly the copy process stopped and if it did.
I have now 21h running and 2120MB copied and there seems not to be more movement. The last file being copied is the zmsy_084.sfs, so therefor I suppose the copying is done.
As the install script disappeared, I don't have further indications, but I think the only to do still is the grubconfig, which I can do by hand.

Also I see there are 374 processes of which one running. Normal?

After that, the big bang (boot)

So I wanted to open a console to execute the grubconfig, but the system didn't move. (frozen or too slow), so I pulled the (virtual) plug.
I booted from the Live-CD again, but after 15 minutes it was still at the stage of making the filesystem usable and stopped the booting.
I booted puppy 410 CD (took only 2 minutes) with the muppy HDD available and installed grub on it.
Booted muppy but got the file not found (15) msg.
Booted puppy 410 CD with the muppy HDD available and indeed vmlinuz wasn't there. Copied it from the 410 CD (don't know if it's suitable for muppy)
Booted from muppy now and got the grub menu, selected to boot muppy, but got an empty black screen.

I think my muppy Live-CD adventure is over.

But I still might try the mini in the same way.

[recycler]

Thought I would share my experience with Muppy Live on a USB pen (2gig capacity). Install went fine. Formatted as fat16. Booted up ok on a 2gig pentium4 processor with 1gig of ram. However, always froze quite quickly. I formatted a second usb pen as swap - 360mb. It was used 100% straight away. System wouldn't reboot until I reformatted the swap. This time I gave it 1gig of swap. Used approx 700mb of swap. Would start up ok but then the system would not power down. Forcibly powered down and it would reboot ok. Maybe this is my hardware?

Conclusion. I copied all the files onto a 40gig ide hard drive and it is running perfectly on there (changed the marker file to IDE of course and gave it a 1gig swap file). Incidentaly this usb installation is the only one so far on which I have found wine to work. I have not tested every one though (out of approximately 15)

[Béèm]

With earlier versions of muppy, installed on my thinkpad 256mb ram and as frugal, I had indeed have to make a swap otherwise muppy froze.

Just to confirm.

[PaulBx1]

This concerns Kernelmodules.
For example, you could not use wifi drivers (that use Kernelmodules) from Slackware.

I didn't understand there was some distinction there, between kernelmodules and some other kind of modules (loadable modules?). In fact I thought that modules were just the linux name for drivers. I guess I am far from understanding the jargon, or the implications here. I don't know what "3rd party drivers" means either. Where this came up was when I was trying to get scramdisk to work with Puppy 4.1, which I have failed at so far.

I did try the standard Muppy on my Dell Inspiron 1525 and did not have much luck with it. In Puppy 4.1 I have to use ndiswrapper and the XP windows driver for the network. When I tried the same thing in Muppy it recognized the network hardware (strangely only wlan0 showed up, not eth0) but it would not communicate with my AP. I tried the latest network wizard with the same result.

Then when I tried to shut down, the screen just went to a blank green, even though the computer was doing the usual shutdown stuff of asking whether I wanted to create a pupsave. I know this because when I hit return enough it finally shut down and I had a pupsave and the sfs files on hda1.

I will try your test iso, even though I don't know if the driver situation with it will make my wifi work.

<later>
Woops, maybe I won't; it is Puppy, not Muppy. I guess I don't see the point; I already have Puppy working on this machine.

[Béèm]

So back to square one and now with mini sys.
Booted from the CD and it works much better.
But I have still issues.
Gparted died serveral times on me, but I succeeded finally to have the hda1 prepared to receive the full install.

I started the Puppy Install and came to the point I had that little window saying 'copying files to hda1)
All of a sudden after a while, this little window vanished.

I can see doing a df -h that files are still copied to hda1. Now after 1:24 I am at 395,8 MB.
I don't know how much I should have.
In rox I see the last directory made is /usr, so I should expect to have /var and the zdrv.sfs file.

I hope I can now at least do the grubconfig from within muppy.

See you later.

[MU]

yes, check with "top" or "ps" that it still copies.
When all is copied, a new message should pop up.
Mark

[Béèm]

Is it the puppyinstaller process I should watch?

In any case, mini sys runs at about the same performance as puppy 4.10 full. So that's positive.

EDIT
I see a cp process now. that should be the one to watch then.

[MU]

I see a cp process now. that should be the one to watch then

.
yes.

[Béèm]

I see a cp process now. that should be the one to watch then

.
yes.

Got finally the rc update and grubconfig and install is complete after 2:15

[Béèm]

I see a cp process now. that should be the one to watch then

.
yes.

Got finally the rc update and grubconfig and install is complete after 2:15

No joy to boot from the hda1 full install of the mini sys.
Like yesterday for the live, after selecting to boot from hda1 in grub, I get a black screen.
Don't know how to diagnose.

[Béèm]

.
yes.

Got finally the rc update and grubconfig and install is complete after 2:15

No joy to boot from the hda1 full install of the mini sys.
Like yesterday for the live, after selecting to boot from hda1 in grub, I get a black screen.
Don't know how to diagnose.

Success finaly.
Saw when booted again from CD, that ther was a vga=791 option on the kernel line from the boot of the full install.
Removed that and I have the desktop now at a little under 2 minutes.

Internet isn't working yet, as I have to find the ne2k_pci module.

So far so good then.

Scrolling in a windows is almost at native install speed.
Starting a program takes somewhat longer but still very acceptable.

[Béèm]

When I did the full install of puppy 4.1 in qemu, I got in grub on the kernel line ro
I thought how odd, but it seems to work.

Now having done the full install of muppy mini sys in qemu, I got on the kernel line rw.
I thought probably logical.

But now I am confused, what should be there ro or rw?