Muppy 008.4c (final release)

[MU]

recycler

Something I found useful on Puppy 4 series is the option to change the foler where the save file goes. Helpful when putting several frugal installs into one partition.

If you run Muppy frugal, you can use "psubdir" in Grubs menu.lst.
Here is an example:

Code: Select all

  title Muppy 0084 Mini english
  root (hd0,5)
  kernel /muppy0084en/vmlinuz acpi=force pmedia=idehd pdev1=sda7 psubdir=muppy0084miniEN
  initrd /muppy0084en/initrd.gz

  title Muppy 0084 Live deutsch
  root (hd0,5)
  kernel /muppy0084/vmlinuz acpi=force pmedia=idehd pdev1=sda7 psubdir=muppy0084
  initrd /muppy0084/initrd.gz

It will create/look for the savefile defined by "psubdir=" on the drive defined by "pdev1=".
If you put more than one savefile there, you get a menu at startup, to choose one.
So I usually create a second "dummy" savefile, to show this menu:
msy_save-DUMMY.2fs
This can be a empty textfile. It cannot be loaded, but forces the menu to be shown.

In the menu, you now can use the first option "0 - boot to ram".
Then you can shutdown to create a new, valid savefile with a new name.

Mark

[Béèm]

Can Mupppy be installed as a full installation on HDD?

[MU]

Can Mupppy be installed as a full installation on HDD?

Yes.
I recommend to use Live or DVD for that.
If you use Mini, you must copy the kernel modules by hand from zmsy_084.sfs (equivalent to zdrv_300.sfs).

Mark

[MU]

zgp152

If I understand corretly, you want to boot from harddisk, but use the msy_084.sfs from the CD.
I might be wrong, but I think that will not work.

You can try something like this:

Code: Select all

title Muppy 008 
rootnoverify (hd0,0) 
kernel /Muppy/vmlinuz pdev1=sda1
initrd /Muppy/initrd.gz 
boot

Mark

[Béèm]

Can Mupppy be installed as a full installation on HDD?

Yes.
I recommend to use Live or DVD for that.
If you use Mini, you must copy the kernel modules by hand from zmsy_084.sfs (equivalent to zdrv_300.sfs).

Mark

Thank you Mark, but I should have read the initial post first. I would have known.

[MU]

there was a question concerning KDEin this thread:
http://www.murga-linux.com/puppy/viewto ... &start=120

Hi. I would like to start by saying that I hope I am posting this in the correct area. Second, I am so thankful that I found the greatest distro ever; Muppy 008. As an elementary music teacher, I finally found my solution to what I need day-to-day (using different school computers via ram, USB drive and boot CD).

Running a KDE sfs has given me Amarok. I depend on this for quick categorization of my music library. Whohooo!!

Amarok is broke, however, in the newest version of KDE 3.10 sfs. So I have gone back to 3.58 sfs. Is there something I need to adjust to fix Amarok in the new KDE sfs?

Thanks to all that is involved in this project!

Brian

I had a look now.
I used Muppy Mini 008.4c3-DE-k2.6.25.16.
The german version, with addons-DE_084.sfs, and kde3510_084.sfs.

If I type in a consolewindow:
amarok
then this player launches fine.

Please tell me more about your setup.
Do you use Mini or Live?

Please also run amarok from a console.
Look, if you get lines containing "ERROR".
Please copy&paste them here.
Ignore lines with "warnings".
KDE spits many warnings, but they do not matter here.

Mark

[recycler]

Hi Mark, thanks for the tip. I always do frugal installs now and move my save files into the directory where Muppy or Puppy is installed. The correct save file is then loaded for each installation. Puppy 4 series allows me to change the folder when I first shutdown and create a save file which is helpful. I was more curious about why Muppy saves into the root directory except on this one occasion when the save file was created in the puppy084 directory.

[Jim1911]

Mark,

Attached are the test files you requested regarding the network not being recognized without a save file. Hope this helps.

Jim

[MU]

Jim,

fine.
Ok, without savefile just a handfull of modules is loaded.
This indicates, that zmsy_084.sfs is not used.

So why?
Maybe it loaded an old one from the harddrive.
Please post the content of the files:
/etc/rc.d/BOOTCONFIG
and:
/etc/rc.d/PUPSTATE
They contain infos, where files were located.

Mark

[Jim1911]

Mark,

Here are the files you requested. You are right about it picking up an old file which it ignores when there is a save file on the seperate partition. However, I thought that 4.09 used AUFS.

Jim

1. BOOTCONFIG

LASTUNIONRECORD=''

2. PUPSTATE

PUPMODE=5
PDEV1='sr0'
DEV1FS='iso9660'
PUPSFS='sdb6,ext3,/muppy084/msy_084.sfs'
PUPSAVE=''
PMEDIA='usbcd'
SATADRIVES='sda sdb '
#these directories are unionfs layers in /initrd...
SAVE_LAYER=''
PUP_LAYER='/pup_ro2'
#The partition that has the msy_save file is mounted here...
PUP_HOME=''
#(in /initrd) ...note, /mnt/home is a link to it.
#this file has extra kernel drivers and firmware...
ZDRV='sdb6,ext3,/zmsy_084.sfs'
PSWAPFILE=''

[MU]

ZDRV='sdb6,ext3,/zmsy_084.sfs'

I think that will be an old one, from Muppy with the OLD kernel.
So it loads that, but finds no modules for the new Kernel in it.

But when you have a savefile, it uses it from a different location... hmm..

At least we now know, that the modules-loading mechanism work correctly.
We just must take care concerning version conflicts.

Mark

[MU]

yes I see, if you start from a seperate partition, you use a grub option like:
pdev1=sda4

In that case, Muppy searches only on that drive, and ignores all others.
That explains, why it works then.

Mark

[Jim1911]

Mark,

Here is the file you requested. Hope this helps.

Jim


PUPMODE=12
PDEV1='sr0'
DEV1FS='iso9660'
PUPSFS='sdb7,ext3,/muppy084/msy_084.sfs'
PUPSAVE='sdb7,ext3,/muppy084/msy_save-test.2fs'
PMEDIA='usbcd'
SATADRIVES='sda sdb '
#these directories are unionfs layers in /initrd...
SAVE_LAYER='/pup_rw'
PUP_LAYER='/pup_ro2'
#The partition that has the msy_save file is mounted here...
PUP_HOME='/mnt/dev_save'
#(in /initrd) ...note, /mnt/home is a link to it.
#this file has extra kernel drivers and firmware...
ZDRV='sdb7,ext3,/muppy084/zmsy_084.sfs'
PSWAPFILE=''

[MU]

hey, you are fast!
I just had removed my request.
thanks, yes, that confirms my conclusion from my last post

Mark

[zgp152]

zgp152

If I understand corretly, you want to boot from harddisk, but use the msy_084.sfs from the CD.
I might be wrong, but I think that will not work.

You can try something like this:

Code: Select all

title Muppy 008 
rootnoverify (hd0,0) 
kernel /Muppy/vmlinuz pdev1=sda1
initrd /Muppy/initrd.gz 
boot

Mark

I wanted the save file on the HD to control the operation, once the OS is loaded, while keeping the sfs file on DVD.

You are right, it did not work as I expected. Menu.lst has no effect, if Muppy DVD is present, since Muppy bypasses the start-up scheme and starts always.

Puppy 4.00 obeys the controls of menu.lst if Muppy DVD is away.

Muppy itself works fine and uses the save file! Thanks, I am eagerly waiting for a new release based on 4.1, since in all likelihood it will fix my remaining wireless problem (MAC must be entered manually)

Timo

[MU]

zgp152

To avoid, that the computer boots from CD, you must enter the BIOS-Setup at startup.
Immedeatly after the computer starts, you can press a key (there is a small hint on the screen).
There you can change the "boot sequence" from CDROM , Harddisk, to: Harddisk.
The exact options differ a bit, depending on the manufacturer.

Alternatively, copy the files from the CD to disk, then burn a new CD from them.
So you burn not a ISO, but just the files as data CD.
Like that, the CD is not bootable.
You need these: msy_084.sfs, zmsy_084.sfs, vmlinuz, initrd.gz.
Ignore all others.

But I did not try yet, if that really works with Grub.
I was too busy with the wireless drivers, the Fritz! made so much trouble again
*bad Fritz, go Puppy, bite him...*

Muppy itself works fine and uses the save file! Thanks, I am eagerly waiting for a new release based on 4.1, since in all likelihood it will fix my remaining wireless problem (MAC must be entered manually)

There will be no version based on 4.1.
Muppy is a "fork", it applied many custom patches to the original Puppy.
Replacing the base with Puppy again, we would lose these patches.
For example, the "update check" when using additional SFS files, is much faster in Muppy, than in Puppy 4.1rc.
But I try to port new improvements from Puppy 4.

The new kernel 2.6.25.16, and the new network-wizard are such improvements.
I start losing the overview - which is the version, that you use now?
008.4c (Kernel 2.6.21.7)
or
008.4c3(Kernel 2.6.25.16)
?
You can see it in conky, the big status area on the desktop.

Mark

[zgp152]

I had created a LiveDVD, contents are below.
(You may recognize DOS DIR output, hurrah old faithful).

D:\

18.09.2008 17:38 > 2 048 BOOT.CAT
18.09.2008 17:38 > 958 BOOT.MSG
14.09.2008 20:31 > 1 236 973 INITRD.GZ
18.09.2008 03:51 > 10 648 ISOLINUX.BIN
04.06.2008 10:20 > 125 ISOLINUX.CFG
18.09.2008 11:00 > 2 010 927 104 MSY_084.SFS
15.10.2007 03:22 > 1 741 240 VMLINUZ
04.07.2008 13:07 > 4 096 ZMSY_084.SFS
8 files > 2 013 923 192 bytes

I have CD/DVD in boot priority before HD.
I had copied vmlinuz and initrd.gz to HD.

The menu.lst is created according to Lin'n Win instructions.
It does control the boot sequence quite well as long as the DVD station is not closed. And how this combinations misbehaves, you can check from past messages. (If I select Muppy and the DVD is not there, it leads to problems, so perhaps I must eliminate that choice from menu.lst.)

Mark wrote:

Muppy itself works fine and uses the save file! Thanks, I am eagerly waiting for a new release based on 4.1, since in all likelihood it will fix my remaining wireless problem (MAC must be entered manually)

There will be no version based on 4.1.
Muppy is a "fork", it applied many custom patches to the original Puppy.
Replacing the base with Puppy again, we would lose these patches.
For example, the "update check" when using additional SFS files, is much faster in Muppy, than in Puppy 4.1rc.
But I try to port new improvements from Puppy 4.

The new kernel 2.6.25.16, and the new network-wizard are such improvements.
I start losing the overview - which is the version, that you use now?
008.4c (Kernel 2.6.21.7)
or
008.4c3(Kernel 2.6.25.16)
?
You can see it in conky, the big status area on the desktop.

Mark

I downloaded version C. Maybe the dates also help you identify the release (since I am not running Muppy just now)? I guess C3 means that it is still being tested?

With this informaton you provided, I could wait for a major release if there is any such forthcoming in a couple of weeks. The downloading takes such a long time, actually hours. I would rather download an upgrade from C if a marginal (tested) file were available. But since that includes kernel upgrade I understand, if marginal files are out of question.

Timo

[MU]

I plan an update in october, but it will not be dramatic.
Basically include the servicepacks, updated pburn, and networkwizard, and OpenOffice 3 final, and a new Minisys.

c3 has the new kernel with newer/more networkmodules, but seems to work pretty well.
So I will release it as second, alternative version.
Apart from that, it is like the normal Muppy.
It does not include other new experimental software.

I meanwhile use it as my main system, works fine.
Just minor issues, e.g. my DVD drive is listed twice on the desktop.
But those are just small cosmetic issues.

If you have trouble with some hardware with the normal Muppy (008.4c), I recommend to try 008.4c3 instead.
My Fritz Wlan Stick works only in 008.4c.
My Linksys Wlan Stick works only in 008.4c3.
So the c3 version is intended as option, if the other one fails.

The officially updated version will get names like
Muppy-Mini-008.4d-DE-K2.6.21.7.iso (now c)
Muppy-Mini-008.4d-DE-K2.6.25.16.iso (now c3)



Mark

[Jim1911]

Mark,

Glad that you are planning to keep c3 as an alternative version. I have found it to be stable, also faster on startup and shutdown, and have already stopped using the c version. Favorite desktops are your standard Muppy or Gnome. I keep the Gnome, KDE, and a combo OpenOffice/Addons sfs files loaded as I like to use some applications from each of these.

Have found a few more minor issues i.e. the menu bar hides the top bar of some applications and the ICE+KDE-Panel(Kicker) desktop cannot log out, although a rightclick on the desktop gives you exit options from that desktop, also one of my dvd drives is listed twice.

Jim

[zgp152]

I have two DVDs to be used in frugal installation, both are 008.4c. One is nearly 2G and the other is without development tools. I had used the larger one and created the savefile in a few sessions. Everything has been smooth with it.

When I used the smaller one for the first time, everything was normal but I got a warning that the savefile was becoming small. As I closed without increasing the savefile before that, the system did not close as usual but I had to cut power. The savefile was perhaps damaged since the next boots went wrong.

Now I'm a bit confused which were causes and which were inevitable consequences. I had a backup of the save file so that I am back with no loss, luckily.

POSTSCRIPT IN PARENTHESIS [ I cleaned up the menu.lst and a few redundant files from Muppy directory, and this prevents booting in a funny way that does not find the savefile etc. I guess the problem of poweroff etc were somehow linked to this. Now I have booted a few times without hiccup, the savefile is found etc. Yet I wonder how is it possible that Muppy autostarts if the DVD station is closed and I just keep my hands off the keyboard after reboot command.]

Is it mandatory that the expansion takes place in an environment where there are no other files in nearby sectors? For instance I could move the savefile to a stick and expand there. I have currently savefile on HD (ntfs).

Rgds Timo