Author |
Message |
technosaurus

Joined: 18 May 2008 Posts: 4787 Location: Kingwood, TX
|
Posted: Sat 24 Apr 2010, 09:20 Post subject:
|
|
I only included the libs that were required for what is installed.
libsamplerate was statically compiled into mhwaveedit (the only installed program that needed it)
this is how I look for library dependencies to remove unneeded ones
Code: | ldd /*in/* /lib/* /usr/*in/* /usr/lib/* /usr/X11R7/bin/* /usr/X11R7/lib/*
|grep = |cut -s -d "." -f 1 |sort |uniq -c |sort |tr "\n" "," |tr "\t" " " >libs |
and this is how to tell how many programs depend on each lib to determine whether to statically compile them or not (larger size with few dependent binaries)
Code: |
ldd /*in/* /lib/* /usr/*in/* /usr/lib/* /usr/X11R7/bin/* /usr/X11R7/lib/* |cut -s -d . -f 1 |sort |uniq -c |sort -n >deps |
_________________ Check out my github repositories. I may eventually get around to updating my blogspot.
|
Back to top
|
|
 |
jpeps
Joined: 31 May 2008 Posts: 3217
|
Posted: Sat 24 Apr 2010, 12:29 Post subject:
|
|
Any idea why ldd doesn't work with /usr/bin programs like gnumeric?
(compression??)
|
Back to top
|
|
 |
technosaurus

Joined: 18 May 2008 Posts: 4787 Location: Kingwood, TX
|
Posted: Sat 24 Apr 2010, 13:26 Post subject:
|
|
they are upx'd (after I verified all dependencies)
_________________ Check out my github repositories. I may eventually get around to updating my blogspot.
|
Back to top
|
|
 |
kkoceski
Joined: 04 Mar 2010 Posts: 11
|
Posted: Sat 24 Apr 2010, 17:15 Post subject:
|
|
I can't get wireless to work on my new Dell Latitude E6500. It has a "Dell Wireless 1510 Wireless-N WLAN Mini-Card" (according to Windows XP Device Manager). This same laptop worked fine with the previous pre-alpha version that came out a couple months ago.
Still works :
1398318d72c3e1f744f68b6cd708503c *pup-431-2.iso
No Wireless:
caf22e9658134778897066f4ad570620 *pup44-a1.iso
So, I tried the new one (burned to CD) - no wireless. Went back to the old one (burned to CD), and wireless works fine. Now I tried the new one again, but with a USB stick, and wireless still fails.
The problem is that the card is never "seen". I always get something that says "no wireless networks found". In all these cases, I never "saved" anything to the hard drive.
Thanks, Kurt
|
Back to top
|
|
 |
jpeps
Joined: 31 May 2008 Posts: 3217
|
Posted: Sat 24 Apr 2010, 18:42 Post subject:
|
|
technosaurus wrote: | they are upx'd (after I verified all dependencies) |
Thanks...ldd works after upx -d
|
Back to top
|
|
 |
technosaurus

Joined: 18 May 2008 Posts: 4787 Location: Kingwood, TX
|
Posted: Sat 24 Apr 2010, 20:04 Post subject:
|
|
Drivers: I will merge the /lib/modules from before and any others that are posted in the drivers section for the full zdrv (There may be some stuff in etc/modules that needs updated as well - from rerwins post in the bugs thread and from tempestuous in the drivers section)
_________________ Check out my github repositories. I may eventually get around to updating my blogspot.
|
Back to top
|
|
 |
zigbert

Joined: 29 Mar 2006 Posts: 6541 Location: Valåmoen, Norway
|
Posted: Sun 25 Apr 2010, 04:42 Post subject:
|
|
technosaurus
I see you use your own configuration of Stardust. Would it be easier for you if I made the changes to the DuDE pack. I am sure we could agree on something
Puppy 4.4 looks good, and I am very impressed by the content of the kilobytes. Even smaller than Vary - where will this end
This post contains some background information about Stardust.
If you need any help, please ask.
Sigmund
_________________ Stardust resources
|
Back to top
|
|
 |
zigbert

Joined: 29 Mar 2006 Posts: 6541 Location: Valåmoen, Norway
|
Posted: Sun 25 Apr 2010, 06:56 Post subject:
|
|
Galculator doesn't start
Code: | # galculator
[galculator] configuration file: couldn't open configuration file /root/.galculator for reading. Nothing to worry about if you are starting galculator for the first time. Using defaults.
Segmentation fault |
_________________ Stardust resources
|
Back to top
|
|
 |
zigbert

Joined: 29 Mar 2006 Posts: 6541 Location: Valåmoen, Norway
|
Posted: Sun 25 Apr 2010, 06:58 Post subject:
|
|
While testing DuDE-0.2, I tried Puppy 4.3.1, Puppy 4.4 alpha, Vary 020 and Lucid Puppy 009. The only place where xlock worked was here - Puppy 4.4 alpha1........
Sigmund
_________________ Stardust resources
|
Back to top
|
|
 |
zigbert

Joined: 29 Mar 2006 Posts: 6541 Location: Valåmoen, Norway
|
Posted: Sun 25 Apr 2010, 07:04 Post subject:
|
|
Maybe you have done it by purpose, but retrovol is missing in the menu. I completely agree with you, using alsamixer as defaultaudiomixer
Sigmund
_________________ Stardust resources
|
Back to top
|
|
 |
zigbert

Joined: 29 Mar 2006 Posts: 6541 Location: Valåmoen, Norway
|
Posted: Sun 25 Apr 2010, 07:10 Post subject:
|
|
Please consider to replace pStopwatch and Ptimer with some of these apps. pStopwatch is a horrible script consuming every tiny piece of cpu-power floating around. The creator of pStopwatch must be an idiot when it comes to coding
Sigmund
_________________ Stardust resources
|
Back to top
|
|
 |
zigbert

Joined: 29 Mar 2006 Posts: 6541 Location: Valåmoen, Norway
|
Posted: Sun 25 Apr 2010, 07:14 Post subject:
|
|
Does Puppy 4.4 alpha1 include your stripped libsamplerate? If so, I don't see any problems as long as I can record in 16-bit 44100 hz.
_________________ Stardust resources
|
Back to top
|
|
 |
zigbert

Joined: 29 Mar 2006 Posts: 6541 Location: Valåmoen, Norway
|
Posted: Sun 25 Apr 2010, 07:16 Post subject:
|
|
mhWaveEdit launches retrovol as its mixer. Maybe better to use the same as defaultaudiomixer
_________________ Stardust resources
|
Back to top
|
|
 |
zigbert

Joined: 29 Mar 2006 Posts: 6541 Location: Valåmoen, Norway
|
Posted: Sun 25 Apr 2010, 07:18 Post subject:
|
|
Pburn in Puppy 4.4 is version 3.2.0 while the latest is 3.2.3.
_________________ Stardust resources
|
Back to top
|
|
 |
zigbert

Joined: 29 Mar 2006 Posts: 6541 Location: Valåmoen, Norway
|
Posted: Sun 25 Apr 2010, 07:30 Post subject:
|
|
I have removed the dark/bright backgrounding of apps from pcc in DuDE-0.2. I think it is a too ambitious project for a control center. Your new configuration of geany has white background, while abiword has the darker alternative from Stardust. I would personally made abiword white as default, but kept rxvt black to simulate the command line.
Many users reacted on my dark environment in Stardust, but for me it is logical. During the dark winter in northern Norway, a too bright contrast from my screen hurted my eyes. - Now when the times are lighter for some months, a brighter environment is preferred. That is one of the reasons for the MoodButtons idea. I use the light flat-gray theme as long as it is enough light in my surrounding, when it's getting darker, I switch to dark-orange.
Sigmund
_________________ Stardust resources
|
Back to top
|
|
 |
|