/usr/lib/tls: (hwcap: 0x8000000000000000)
Okay! That's the one which is hidden and generated in some mysterious way. It either has to do with CPU specs and is generated at runtime or it has to do with configure options to glibc and is being determined at glibc compile-time. The key is the 'hwcap' part.

I have asked about this all over at linuxquestions.org -but no takers yet.

Aha! Just found an LKML thread where The Man(Roland McGrath) himself talks about this:
https://lkml.org/lkml/2007/4/24/3

He seems to be saying that these paths are generated at runtime -using entires in /etc/ld.so.conf.d, and/or they depend on options used at glibc compile-time.

On my self-built system here, I don't get any of those extra paths. Guess the upshot is that you need to be using Gilbert's super-duper KISS linux -where most of the nonsense is missing... Or maybe you'd like to roll your own glibc -even BK doesn't do that.

"libs provided with standard Puppy 412" The problem is that that still doesn't tell us where they came from or who built them! The output of `/lib/libc.so.6` will help a little bit -did you know that trick? Here's another 2 which will tell you some things -sometimes clearing up questions about compiling/linking problems:
gcc -dumpspecs
gcc -dumpmachine

Here's another link with tips to the location(s) in the sources.
http://www.unixresources.net/linux/clf/linuxK/archive/00/00/58/83/588306.html

Quote:

If this stuff is causing you a problem, you can turn it off by patching dl-procinfo.h in glibc

amigo: Thanks for all this info! A lot to test and think about. For now only the output of /lib/libc.so.6

Quote:

GNU C Library stable release version 2.6.1, by Roland McGrath et al.
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 4.2.2.
Compiled on a Linux >>2.6.21.7<< system on 2007-10-18.
Available extensions:
crypt add-on version 2.1 by Michael Glad and others
Native POSIX Threads Library by Ulrich Drepper et al
BIND-8.2.3-T5B
For bug reporting instructions, please see:
<http://www.gnu.org/software/libc/bugs.html>.

Created a static build of Xorg (X11R-6.7.0) - pet-package including xorgwizard, ddcprobe & dmidecode for easy configuration - can be downloaded here
Its quite big (7,7Mb uncompressed) but I can run it on machinery with 36Mb ram. It seems to display fonts OK. It holds a lot of display drivers so if you have problems getting pupngo2012 running on you hardware this might solve the problem.

When I boot the standard pupngo2012 on a Toshiba TE2100 the display starts up in 800x600 and everything looks correct. (I can change the res if I need to, but Im just testing in 800x600 for the purposes of this problem..)

When I use the same CD to boot on an older Toshiba (2180CDT) which only has an 800x600 capable screen the display is clear, but all drive icons and program icons are missing unless I start xorg. Also, if I click "file manager" in the menus it does nothing, but if I locate the rox icon and click it, filemanager starts up ok.

Q1) Any ideas why the icons are not displaying under xvesa?
Q2) Is there a cli method of listing running processes?
Q3) Is rox different to rox-filer, and is there a rox-pinboard running on pupngo? Is thats whats not running on my older system?
Q4) Which file describes the position location for the drive icons on pupngo?

View running processes in CLI: ps (or top for the top ones)
Try look in /tmp/xerrors.log - should report problems - maybe ROX fails to start?
Pinboard should run in pupngo. The geometry is determined at startup and placement of icons set in root/Choices/ROX-Filer/puppupin
Best guess is that ROX are having problems at startup.

Thanks for the answers - that is very helpful. As part of this troubleshooting I am changing the desktop layout, and have put the jwm tray at the top (instead of the bottom) and I want to move the drive icons towards the top aswell. I can move these drive icons successfully by changing the puppypin file, but after I do that I notice that new usb drives I plug in still display at the bottom of the screen.

It appears as if maybe Rox has a predetermined positioning for anything that is not specifically mentioned yet in the puppypin file?

It seems to me that the tray which holds new drive icons is probably specified in the file .create_jwmrc_drives.sh by the line:

but I have not succeeded in changing the behaviour/location of the drives tray (for example I tried changing "horizontal" to vertical, and also tried changing the x and y values but never saw any change)

Does every possible drive icon HAVE to be listed in puppypin?? What if I don't know how many drives the end user might have?

Is there some way to change the drive_icon_positioning_behaviour without specifying it in puppypin?

Is far as I remember the drive icons are generated in /sbin/pup_event_frontend_d. The .create_jwmrc_drives.sh is a left over from time when no ROX present and desktop icons were made via jwm alone. Try look into /sbin/pup_event_frontend_d - most things are explained there.

The problem with rox is that it doesnt accept negative values for placement (distance from right or bottom) like jwm does, so it is a little harder to get exactly right. It probably wouldn't be a difficult thing to patch but then compatibility issues arise. it would look like:
if (x<0) x+=gdk_screen_get_widthgdk_screen_get_default());
//similar for y_________________Web Programming - Pet Packaging 100 & 101

Thanks for the clues. I have made some alterations to pupngo2012 so that the menu and drive icon display functions are referenced to the top left corner instead of the "calculated" bottom_of_screen and my 2180cdt is now booting correctly. I plan to try this approach on some of my other machines that struggle to boot/display puppy correctly, and have started a thread here:
http://www.murga-linux.com/puppy/viewtopic.php?p=683684#683684

I am working on getting icewm running in pupngo - and almost done with a draft. I am using xli as desktop background setter, have a pm-icewm-menu/winoptions done and modified smaller things in xinitrc and xwin. One problem remains though: How to swallow the freememapplet or other applets in icewm? Ohh - I think the solution is icewmtray!

Happy to hear that IceWM might be in the works ... It's my favorite WM. Puppy Xtreme (420) is still one of my favorite Puppies ... no pinboard or wallpaper just a black screen with my most used apps on a double height taskbar (quick launch) plus battery, eth0 or wlan0, and CPU monitors (no tray). 13 basic running processes including eth0, 15 with wifi up. JWM work too but you do not have system monitors.

I've been playing around with PuPnGo2012, Plus and TLC for a few days now on my older acer lappy. All are running from a single USB flashdrive booting from Grub4DOS. PiPnGo2012 works well .... Only problem noted is that freememapplet doesn't report free RAM or savefile correctly.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum