1.0.5rc: PCCC bugs (partitions, menus, etc)
1.0.5rc: PCCC bugs (partitions, menus, etc)
I am running 1.0.5rc & eagerly tried the anticipated PCCC - am very keen to bare-bones my puppy down (to reduce clutter & give me a little bit more space back to assist with OpenOffice)
However, the partition-checker doesn't like my system :/
I have 3 partitions mounted, all of which have plenty of space for the 700Mb that I need to build the new .iso with:
/dev/hdb1 288451232 216337700 57461052 79% /mnt/home
/dev/hda10 19228276 12119780 6131748 66% /mnt/home/hda10
/dev/hda11 19228276 11930980 6320548 65% /mnt/home/hda11
This is what PCCC says:
"Puppy is currently defaulting to mount point /mnt/home, on
which partition /dev/hdb1
/dev/hda10
/dev/hda11 is mounted, and it is type ext3
ext3
ext3,
which is fine. The free space in the partition is 57461052
6131748
6320548 Kbytes.
However, that size is too small. You have to quit..."
I get no joy with anything I try from the 'Change' button so ultimately am forced to 'Exit', which is most disappointing
Am very happy to provide any additional debugging &/or Beta-test any revised versions...
F
However, the partition-checker doesn't like my system :/
I have 3 partitions mounted, all of which have plenty of space for the 700Mb that I need to build the new .iso with:
/dev/hdb1 288451232 216337700 57461052 79% /mnt/home
/dev/hda10 19228276 12119780 6131748 66% /mnt/home/hda10
/dev/hda11 19228276 11930980 6320548 65% /mnt/home/hda11
This is what PCCC says:
"Puppy is currently defaulting to mount point /mnt/home, on
which partition /dev/hdb1
/dev/hda10
/dev/hda11 is mounted, and it is type ext3
ext3
ext3,
which is fine. The free space in the partition is 57461052
6131748
6320548 Kbytes.
However, that size is too small. You have to quit..."
I get no joy with anything I try from the 'Change' button so ultimately am forced to 'Exit', which is most disappointing
Am very happy to provide any additional debugging &/or Beta-test any revised versions...
F
Last edited by flavour on Fri 16 Sep 2005, 22:07, edited 1 time in total.
Another PCCC bug:
When I remove apps, the menu entries aren't removed (which is even more important than diskspace/RAM for me )
- need a call to fixmenus? (using root-fs/root0)
A good thing is that the removed apps are now available as PupGets
I love the chance to make manual tweaks to the filesystem
- for me this involves:
(1) updating mktemp to the full version (to support Mozilla builds), which can't be done within pup003 since UNIONFS prefers the original version?
(2) replacing jwm with a version compiled with --no-load (doesn't save diskspace but gives me some screen real estate & is less distracting)
(3) putting a custom icon in place by copying to filesystem & amending /root0/.jwmrc
F
When I remove apps, the menu entries aren't removed (which is even more important than diskspace/RAM for me )
- need a call to fixmenus? (using root-fs/root0)
A good thing is that the removed apps are now available as PupGets
I love the chance to make manual tweaks to the filesystem
- for me this involves:
(1) updating mktemp to the full version (to support Mozilla builds), which can't be done within pup003 since UNIONFS prefers the original version?
(2) replacing jwm with a version compiled with --no-load (doesn't save diskspace but gives me some screen real estate & is less distracting)
(3) putting a custom icon in place by copying to filesystem & amending /root0/.jwmrc
F
NB Although PCCC told me that mrxvt would stay within pup003, it had actually been uninstalled from there!flavour wrote:Is the fact that my mrxvt DotPup isn't going to get burnt to the new LiveCD a bug in my DotPup, or is this to be expected?
- gone from the 'Remove Packages' & also from the filesystem...
I can't be sure whether it arrived onto the CD, since it didn't work...not sure if a duff CD, or I accidentally uninstalled something critical...
F
Another PCCC bug :/
- I did a further remaster from my previous one, adding in an application (XChat) & removing various others (leafpad, uXplor, etc). I also updated JWM to 0.24 (just copied the binary over)
XChat is installed just fine, however the ones that I'd requested to be uninstalled are still present.
- I'll do some more testing to see whether it's because of adding in a new app, or the 'remaster from remaster' or both
I wanted to tweak the default applications using the files /usr/local/bin/default*
- however these all seem to be blank inside 'rootfs-complete'
Hhere do these get populated?
- is there some inteliigence based on which apps are installed?
F
- I did a further remaster from my previous one, adding in an application (XChat) & removing various others (leafpad, uXplor, etc). I also updated JWM to 0.24 (just copied the binary over)
XChat is installed just fine, however the ones that I'd requested to be uninstalled are still present.
- I'll do some more testing to see whether it's because of adding in a new app, or the 'remaster from remaster' or both
I wanted to tweak the default applications using the files /usr/local/bin/default*
- however these all seem to be blank inside 'rootfs-complete'
Hhere do these get populated?
- is there some inteliigence based on which apps are installed?
F
remaster from remaster didn't attempt to download any missing packages into my Unleashed folder, which a remaster from original did (& I spotted the msg warning this would happen this time ).
NB Would be great if additional packages that are downloaded are installed into the puppy-unleashed folder as well as those that are removed - especially OpenOffice as it's a fairly hefty download...
My new remaster failed to boot, though - not sure if I accidentally removed something critical or whether it's a duff burn:
mkdir: cannot create directory '/new_root': No space left on device
which then causes all sorts of failures through the boot sequence..
F
NB Would be great if additional packages that are downloaded are installed into the puppy-unleashed folder as well as those that are removed - especially OpenOffice as it's a fairly hefty download...
My new remaster failed to boot, though - not sure if I accidentally removed something critical or whether it's a duff burn:
mkdir: cannot create directory '/new_root': No space left on device
which then causes all sorts of failures through the boot sequence..
F
I tried adding my mrxvt DotPup to my latest Remaster & it did indeed make it onto the CD, so it was correct to uninstall from pup003.
It was just the message that was wrong...wonder why it did that?
Seems like my error above must have been a duff burn, since I removed all the same stuff succesfully (just didn't add XChat/OpenOffice)
F
It was just the message that was wrong...wonder why it did that?
Seems like my error above must have been a duff burn, since I removed all the same stuff succesfully (just didn't add XChat/OpenOffice)
F
Last edited by flavour on Sun 25 Sep 2005, 14:19, edited 1 time in total.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
PCCC is such a complicated script that there are bound to be problems,
and some of them won't get fixed right now.
I did fix the one reported at the very start of this thread.
I appreciate the "inefficiency" of downloading packages that are actually
being removed. This is a stop-gap technique for now.
Any packages removed are also supposed to be removed from the menu.
If that isn't happening ...well, I'll see if I can test it some more tomorrow.
and some of them won't get fixed right now.
I did fix the one reported at the very start of this thread.
I appreciate the "inefficiency" of downloading packages that are actually
being removed. This is a stop-gap technique for now.
Any packages removed are also supposed to be removed from the menu.
If that isn't happening ...well, I'll see if I can test it some more tomorrow.
Great, thanks for looking at PCCC - this & usr_devx.sfs make such a great customisation platform
1 more tweak to PCCC's removal of apps that could be done is to remove the configs from /root0 when the app is removed:
e.g. .AbiSuite,.bluefish,.eznet,.gaby,.sylpheed
PS If u want someone to beta-test any revised PCCC scripts, then I'm an eager-beaver
Cheers,
F
1 more tweak to PCCC's removal of apps that could be done is to remove the configs from /root0 when the app is removed:
e.g. .AbiSuite,.bluefish,.eznet,.gaby,.sylpheed
PS If u want someone to beta-test any revised PCCC scripts, then I'm an eager-beaver
Cheers,
F
I still get this error when remastering from 1.0.5final - if I had OpenOffice to try & make a chubby:
"mkdir: cannot create directory '/new_root': No space left on device"
which then causes all sorts of failures through the boot sequence..
Seems like the size is a problem.
It tells me to set ramdisk_size=12614 in isolinux.cfg since it's 12288 max
I tried this but to no avail.
I looked at Chubby 1.0.4 & that doesn't have any such entry in isolinux.cfg.
It doesn't seem to have much bigger files either:
Chubby_1.0.4: 6.8Mb image.gz & 92Mb usr_cram.fs
1.0.5+OO.o PupGet via PCCC: 7.2 Mb image.gz & 74 Mb usr_cram.fs
Am I doing something wrong?
How did you create the real Chubby?
- via unleashed, I guess?
- so this is probably my only option...
Would be good to know what's going on here, though...
F
"mkdir: cannot create directory '/new_root': No space left on device"
which then causes all sorts of failures through the boot sequence..
Seems like the size is a problem.
It tells me to set ramdisk_size=12614 in isolinux.cfg since it's 12288 max
I tried this but to no avail.
I looked at Chubby 1.0.4 & that doesn't have any such entry in isolinux.cfg.
It doesn't seem to have much bigger files either:
Chubby_1.0.4: 6.8Mb image.gz & 92Mb usr_cram.fs
1.0.5+OO.o PupGet via PCCC: 7.2 Mb image.gz & 74 Mb usr_cram.fs
Am I doing something wrong?
How did you create the real Chubby?
- via unleashed, I guess?
- so this is probably my only option...
Would be good to know what's going on here, though...
F
It fails even with ramdisk_size=15000
I see that the sizes of the 1.0.5 Chubby (which I'm seeding now) are:
image.gz 7.4Mb
usr_cram.fs 87Mb
What determines the size needed for the ramdisk?
Just size of image.gz?
- uncompressed, rather than compressed?
I see that the 1.0.5 chubby has an uncompresed image of 13631 - same size as ramdisk.
My failed image was 12916, so the calculation seems correct...but a ramdisk_size of 15000 is insufficient Can it be too large as well as too small?
F
I see that the sizes of the 1.0.5 Chubby (which I'm seeding now) are:
image.gz 7.4Mb
usr_cram.fs 87Mb
What determines the size needed for the ramdisk?
Just size of image.gz?
- uncompressed, rather than compressed?
I see that the 1.0.5 chubby has an uncompresed image of 13631 - same size as ramdisk.
My failed image was 12916, so the calculation seems correct...but a ramdisk_size of 15000 is insufficient Can it be too large as well as too small?
F
I'm having the same problem. I added xine extra codecs, nmap, monkey web server dot pup, and abiword us-dict dot pup. I added a couple printers using the printer wizard and ran the ethernet wizard. Then I ran PCCC. everything seemed to go fine, it said to set ramdisk_size = 13147. I set it to 18000. When I tried to boot the CD it gave the message "/new_root': No space left on device". I'll try it again, maybe I had a typo with the ramdisk_size or could I have made it too big? I put the ramdisk_size on a line right before the line with "say 2 no APCI ....".
Almost forgot,on the boot screen, right before the line with the boot options it posts this message twice "Missing parameter in config file."
Almost forgot,on the boot screen, right before the line with the boot options it posts this message twice "Missing parameter in config file."