Page 2 of 7

Posted: Fri 30 Jan 2009, 12:49
by WhoDo
aragon wrote:Booting problem with the cd might be a problem of isomaster. Some people (me too) have had problems to 'remaster' a puppy-iso (what means to substitute pup_***.sfs) with isomaster. maybe the actual problem is just another bug.
As a test, would someone unpack syslinux.cfg from the ISO, rename it isolinux.cfg and pack it back in. Then do a burn to CD and let me know if the problem is resolved. It shouldn't be, but renaming the config file is the only change I made to the way Alpha2 is configured vs Alpha1, which had both the syslinux and isolinux versions in the one file. Of course I'm grasping at straws.

I know the underlying build is ok. It boots fine from a frugal install on a partition and on a USB stick.

Let me know how you go.

Re: Not booting

Posted: Fri 30 Jan 2009, 12:54
by WhoDo
tom4jesus wrote:Is it possible to have a good md5sum and the burn go fine and still have a bad disc?
I suppose I would think it is, but I just wanted to be sure it was just me and not the iso.
At this point with all the boot problems others are having, it's probably the iso. You should compare md5sum's at two points in the process - once on the iso after download and once on the LiveCD after burning the iso to the cd. Pburn will allow you to do that as a matter of course.

The file list and syslinux.cfg file seem fine. Try unpacking the iso to a directory and making a bootable CD with those files on manually, rather than burning directly from the iso.

Hope that helps.

Posted: Fri 30 Jan 2009, 13:33
by ttuuxxx
Hey WhoDo, I've been thinking about the icon problem we are having.
Wouldn't it be better to have 3 icon folders and in each theme folder is 2 tar.gz files mini-icons.tar.gz and pixmaps.tar.gz that gets extracted to
/usr/local/lib/X11/mini-icons
/usr/local/lib/X11/pixmaps
That way, nothing is left behind, so when the tar.gz extracts, it replaces the previous images 100% and Jwm,IceWM can't messup.

Or maybe just kill the icon switcher, and extra icon themes, until its a stable program, the way it works now, is alpha quality and shouldn't be in a main release, well thats how I look at it, not putting down the great work that went into it, but if its really buggy. It should get more testing and fixes before entering mainstream Puppy.
ttuuxxx

Ps WhoDo anything on your wish list you would like me to tackle now? Just sitting here thinking hmmmmmm looks like I have everything done that I could do for now. Should I start something new?
ttuuxxx

Posted: Fri 30 Jan 2009, 14:01
by HairyWill
<major edit>post no longer necessary</edit>
If you supply software compiled from GPL code you must be able to supply the source on request. This is part of the reason for the success of linux. Every time you modify something, someone else can look at your changes and learn/hack/patch to their hearts content.

Being able to supply the source does not mean it has to be included in the iso.

Live-CD not recognised as bootable

Posted: Fri 30 Jan 2009, 14:13
by Terryphi
WhoDo wrote: As a test, would someone unpack syslinux.cfg from the ISO, rename it isolinux.cfg and pack it back in. Then do a burn to CD and let me know if the problem is resolved.
I tried that - it didn't work. However, I can confirm that it works as a frugal install.

Posted: Fri 30 Jan 2009, 14:18
by ttuuxxx
Ok Hairy what your saying is that I have to supply the 3 source files that I used to create firepup, right FF 1.5,2,3
Why would I have to suppy FF sources when they are already being hosted by FF and the 1.5 by redhat, How about 3 links and tell them go fetch.
ttuuxxx

Posted: Fri 30 Jan 2009, 14:57
by ttuuxxx
Ok Hairy I changed my post on page 2, does that follow GPL now?
ttuuxxx

Plus I made a GPL statement
http://www.murga-linux.com/puppy/viewto ... h&id=14493

Posted: Fri 30 Jan 2009, 15:38
by HairyWill
ttuuxxx
thank you
Earlier versions of your post gave the impression that you had modified the source code, I suspected that you hadn't.

Before anyone else points it out firefox is MPL not GPL. I don't think the difference is important here.

I don't think technosaurus is being a PITA.

Posted: Fri 30 Jan 2009, 15:44
by ttuuxxx
Yes Hairy I'm not much of a coder, but I'm a hell of tester/mixer of things, I can do simple code, but its veryyyyy limited. And source code well thats a whole new ballpark for me, most I can do with source code is alter the config file to use lower version numbers or change exit 1 to exit 0 lol
ttuuxxx

Posted: Fri 30 Jan 2009, 15:48
by ttuuxxx
Oh but what I do understand that helps me out with Firefox code after its compiled is the markup language its very similar to web pages, and that I understand very well.
ttuuxxx

Firepup

Posted: Fri 30 Jan 2009, 16:49
by Terryphi
ttuuxxx: I am really pleased of the chance to road-test your Firepup in Alpha2. Although I use Opera as my primary browser I like to have a Firefox version too and your derivative is great. Well done!

Is there an icon for it somewhere in the build?

Posted: Fri 30 Jan 2009, 17:04
by ttuuxxx
Thanks for the nice comments the icon is located in
/usr/lib/FirePupv4/icons/default.xpm
Thanks
ttuuxxx

Posted: Fri 30 Jan 2009, 20:24
by WhoDo
ttuuxxx wrote:Hey WhoDo, I've been thinking about the icon problem we are having.
Wouldn't it be better to have 3 icon folders and in each theme folder is 2 tar.gz files mini-icons.tar.gz and pixmaps.tar.gz that gets extracted to
/usr/local/lib/X11/mini-icons
/usr/local/lib/X11/pixmaps
That way, nothing is left behind, so when the tar.gz extracts, it replaces the previous images 100% and Jwm,IceWM can't messup.
That won't solve the problem, Jeff. The various icon themes use different names for the same icon. With different names, the icon with the wrong name doesn't get overwritten, yes, and your tgz solution will fix that part. However, it's a problem in two parts; the name of the icon that is used for the symlink is also dependent on which theme was in use when it was created. PuppyPin and globicons will still refer to the old icon and if it's not there you'll just get a blank symlink either on the desktop or in the menu.
ttuuxxx wrote:Or maybe just kill the icon switcher, and extra icon themes, until its a stable program, the way it works now, is alpha quality and shouldn't be in a main release, well thats how I look at it, not putting down the great work that went into it, but if its really buggy. It should get more testing and fixes before entering mainstream Puppy.
The icon switcher is stable. It's the raw icon data that's the problem. Garbage in/Garbage out. It's a tedious task but at least two themes need to match to each other and the PuppyPin/globicons pair. Any theme that doesn't can then be dumped and the icon switcher will work like it's supposed to do.
ttuuxxx wrote:Ps WhoDo anything on your wish list you would like me to tackle now? Just sitting here thinking hmmmmmm looks like I have everything done that I could do for now. Should I start something new?
Catdude has given us grub-gfxboot graphical boot system. I didn't have time to work through the configuration settings so it will be the default system installed when grub is loaded from the script.

The system needs to be modified so the graphical boot is what comes up whenever grub is installed as part of the Puppy Universal Installer process. It's just about config files and where they go. If I could get the lot in an Unleashed-ready pet package that would save me heaps of time in configuring the next release.

Also, has the Ctrl+Alt+Delete shutdown menu been finalised? That isn't in Alpha2, but I'd like to see it in the next release. :?

Finally, I need a ttuuxxx build of Seamonkey-1.1.14 with the Mail/News option included. Even if it doesn't go in the standard build, it should be in the PETget repository for those who need email compatibility with their existing system.

Thanks for all you've done, ttuuxxx. I really appreciate what you guys are contributing to this build. If it was just me alone, nothing would change I can assure you! :P

Re: Live-CD not recognised as bootable

Posted: Fri 30 Jan 2009, 20:30
by WhoDo
Terryphi wrote:
WhoDo wrote:As a test, would someone unpack syslinux.cfg from the ISO, rename it isolinux.cfg and pack it back in. Then do a burn to CD and let me know if the problem is resolved.
I tried that - it didn't work. However, I can confirm that it works as a frugal install.
Ok, that confirms two things:

1. The underlying release is fine - otherwise the frugal install wouldn't run.

2. The syslinux boot system is fine - otherwise my USB installs wouldn't boot.

The problem is therefore in the original iso creation as bootable. I changed the way I created the iso because the normal makeiso script in my unleashed tree isn't working for some reason.

I'll revisit the makeiso script to see if I can work out why it is creating the iso shell but not adding any files. I'll try and have that fixed for the next release. I'll also go back and see if I can create a properly bootable iso for this release, if I have enough time.

Thanks for doing the test, Terryphi.

Posted: Fri 30 Jan 2009, 21:08
by aragon
hi whodo,

maybe try this simple script for the iso:
http://www.murga-linux.com/puppy/viewtopic.php?t=36573

cheers
aragon

Posted: Fri 30 Jan 2009, 21:19
by aragon
now some reporting from a first test:

- chat deskicon does not work => defaultchat is wrong
- browse deskicon opens netsurf => defaultbrowser is set wrong?
- zip-deskicon does not work => we have xarchiver not xarchive
- deskicon for edit is not good, it'n not a notecase
- play deskicon does not work => gxineshell is missing
- dark menuicons old do not work well with dark background

- add ldconfig, so user don't need to reboot, if a lib installs to /usr/local/lib (this needs an entry in /etc/ld.so.conf)
- create defaultmusicplayer (with pmusic) and change the defaultaction for mimetypes that work with pmusic
- update libgphoto2 to support more cam's
- add new mtpaintsnapshot-gui
- add htop it's much better than top
- are gfontsel and xfontsel needed?
- cleanup setup submenu (remove the ones which are in the wizard?)
- show desktop should not be in in autohide section

cheers
aragon

Posted: Fri 30 Jan 2009, 21:19
by WhoDo
aragon wrote:maybe try this simple script for the iso:
http://www.murga-linux.com/puppy/viewtopic.php?t=36573
Thanks for the thought, aragon, but the makeiso script in Unleashed gets this far. It just fails to add the files, which is also a limitation of your script. Maybe you could look at the makeiso script Barry created and get your calls to add the other files from there?

Posted: Fri 30 Jan 2009, 21:23
by WhoDo
aragon wrote:now some reporting from a first test:

- chat deskicon does not work => defaultchat is wrong
- browse deskicon opens netsurf => defaultbrowser is set wrong?
- zip-deskicon does not work => we have xarchiver not xarchive
- deskicon for edit is not good, it'n not a notecase
- play deskicon does not work => gxineshell is missing
- dark menuicons old do not work well with dark background

- add ldconfig, so user don't need to reboot, if a lib installs to /usr/local/lib (this needs an entry in /etc/ld.so.conf)
- create defaultmusicplayer (with pmusic) and change the defaultaction for mimetypes that work with pmusic
- update libgphoto2 to support more cam's
- add new mtpaintsnapshot-gui
- add htop it's much better than top
- are gfontsel and xfontsel needed?
- cleanup setup submenu (remove the ones which are in the wizard?)
- show desktop should not be in in autohide section
Great report, aragon! 8) I have captured it for the next release, thanks!

Posted: Fri 30 Jan 2009, 21:52
by aragon
Maybe you could look at the makeiso script Barry created and get your calls to add the other files from there?
sorry, that far beyond what i'm able to atm? for the script i just combined the part from remaster and the part from dir2sfs...

but i've compared the alpha2 with other puppy-isos. the difference is, that the boot.cat is missing in the alpha2. might this be the problem (i don't know what boot.cat is...).

cheers
aragon

Re: Not booting

Posted: Fri 30 Jan 2009, 22:29
by tom4jesus
WhoDo wrote: The file list and syslinux.cfg file seem fine. Try unpacking the iso to a directory and making a bootable CD with those files on manually, rather than burning directly from the iso.
Hope that helps.
I was not sure how to make a bootable CD from the files unless it is already an iso (still learning), but I did make a directory with the files and a grub entry for it (frugal install) and it booted up with no problems.

I will report back any unreported bugs if I find any.
It is looking real nice and I am posting this on Firepup from within it. :)

Tom