Puppy Linux Discussion Forum

[starhawk]

Got the *.tar.gz working -- apparently 7zip was flagging the .tar file as a directory in Windows (or Windows was making a very incorrect assumption!). I un-*.gz'd it using GZip (found on the 'net) and did the untarring with 7zip and it worked.

Gaah another reason to switch, albeit a small one. Either way: not your archive, my extracting methods.

I'll take a look at the Xorg pet you provided, as I've too little knowledge of how things work to know safely what to strip from a package.

EDIT: *.pet does not work. Install from within GUI = black screen, X cursor, nothing useful present. I think you cut out a little too much

I'll take a look at the original *.pet and see what I can do.

[starhawk]

I installed xorg 7.3-1 base, server, and drivers-full from the Puppy4 ibiblio repository, and "stole" (borrowed) the shell scripts xorgwizard, xrandrshell, xserverwizard, and input-wizard, from Puppy 412 not-retro.

I try to run xorgwizard and it doesn't work -- crashes instantly. xserverwizard says that gtkdialog2 is missing. My guess (although I can't read that fast) is that xorgwizard needs the same.

Is this something I can fix with a symlink, or do I need to learn to code something here?

[technosaurus]

[goingnuts]

I haven't tested the xorg-pet in all the past pupngo versions but it works here in my test bench.... Try running xorgwizard from outside X (command prompt) that way you wont get the missing gtkdialog2 stuff. xorgwizard need some helpers to function (ddcprobe and dmidecode) although you can configure xorg via xorgwizard without if. Also some long options are used for grep and sort which the busybox version does not understand.
The xorg pet contains a xorgwizard modified to use gtkdialog1 (you can use the static versions provided in the programming area) - and with the described changes mentioned above.

After installing the xorg pet try starting X from command prompt with "xinit". If Xorg is symlinked to X and jwm startup is described in /root/.xinitrc - Xorg and jwm should start up ...

[starhawk]

Thanks, I'll try that.

BTW, a couple of general questions probably better for the Programming forum...

(1) what does it mean to "statically" compile something? (I know you don't rub it with Cling Wrap! )
(2) when you strip things down, how is that done? Do you delete unnecessary files out of *.pets, or do you actually rewrite lines of code? or both?

I'm a total n00b with this stuff.

EDIT: might want to take a look at the referred thread -- the two *.gz files (of which I need one) won't gunzip. I posted my troubles in that thread.

[goingnuts]

1. static linked executables hold everything needed for it to run as a stand alone binary - that is: No external shared libraries needed. Many of the younger pUPnGO versions are composed of totally static linked binaries - that means the main sfs has no need for any shared libraries.
2. strip in the compiling sense - is removing everything unneeded for the binary to run (comments in the code, bypassed code-snippets etc.). Normally done by using the strip-program.

When I speak of stripping the xorg-packages for all unneeded stuff its a removal (delete) of files from the packages which is something different. Other names it "cut-the-fat"...

[starhawk]

"strip-program"...? What program? Where do I get it?

I want to learn this stuff too

[Ibidem]

[Ibidem]

[RetroTechGuy]

[goingnuts]

I wonder...if I stripped goingnuts...would it be the going or the nuts that got smaller..?

[starhawk]

Probably it would just take out the vowels and you'd be gngnts

[technosaurus]

[RetroTechGuy]

[goingnuts]

Thank you for your support for the above strictly hypothetic question about stripping and goingnuts...
Hard to pickup with some boring stuff but I will give it a try:
Some time ago I made a mcb holding the following programs