From: Diego T. <dt...@co...> - 2003-10-28 18:51:14
|
Q: is there any reason for not doing this? scripts/functions strip_debug() { echo "removing debug symbols from binaries" - find ./ -type f -exec strip -p --strip-debug '{}' ';' 1> /dev/null 2>/dev/null + find ./ -type f -exec strip -p --strip-all '{}' ';' 1> /dev/null 2>/dev/null } -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
From: Diego T. <dt...@co...> - 2003-10-28 19:02:08
|
On Tue, Oct 28, 2003 at 07:50:14PM +0100, Diego Torres wrote: > - find ./ -type f -exec strip -p --strip-debug '{}' ';' 1> /dev/null 2>/dev/null > + find ./ -type f -exec strip -p --strip-all '{}' ';' 1> /dev/null 2>/dev/null btw: great improve over binaries that waste 3'5Mb... for example, ldconfig. (after a strip it goes down to 3xxKbs) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
From: Heiko Z. <he...@zu...> - 2003-10-28 19:49:50
|
> On Tue, Oct 28, 2003 at 07:50:14PM +0100, Diego Torres wrote: >> - find ./ -type f -exec strip -p --strip-debug '{}' ';' 1> /dev/null >> 2>/dev/null >> + find ./ -type f -exec strip -p --strip-all '{}' ';' 1> /dev/null >> 2>/dev/null > > btw: great improve over binaries that waste 3'5Mb... for example, > ldconfig. (after a strip it goes down to 3xxKbs) Did you check what "strip-all" removes? -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Diego T. <dt...@co...> - 2003-10-28 20:06:08
|
On Tue, Oct 28, 2003 at 02:41:28PM -0500, Heiko Zuerker wrote: > > > > btw: great improve over binaries that waste 3'5Mb... for example, > > ldconfig. (after a strip it goes down to 3xxKbs) > > Did you check what "strip-all" removes? #man strip -s --strip-all Remove all symbols. That's the default option for strip. -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
From: Bruce S. <bw...@ar...> - 2003-10-28 20:11:36
|
> > > btw: great improve over binaries that waste 3'5Mb... for example, > > > ldconfig. (after a strip it goes down to 3xxKbs) > > > > Did you check what "strip-all" removes? > > #man strip > -s > --strip-all > Remove all symbols. > > That's the default option for strip. How about creating a new function called "strip_all" in addition to "strip_debug", then change all the scripts to use "strip_all"? If any have problems with any packages, then we can change individual scripts back to use "strip_debug". Also check to make sure all the scripts are calling "strip_all". - BS |
From: Heiko Z. <he...@zu...> - 2003-10-28 20:23:07
|
>> > > btw: great improve over binaries that waste 3'5Mb... for example, >> > > ldconfig. (after a strip it goes down to 3xxKbs) >> > >> > Did you check what "strip-all" removes? >> >> #man strip >> -s >> --strip-all >> Remove all symbols. >> >> That's the default option for strip. > > How about creating a new function called "strip_all" in addition to > "strip_debug", then change all the scripts to use "strip_all"? > > If any have problems with any packages, then we can change individual > scripts back to use "strip_debug". > > Also check to make sure all the scripts are calling "strip_all". That's even better ! Let's see how much space we gain. -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Diego T. <dt...@co...> - 2003-10-29 22:45:27
|
On Tue, Oct 28, 2003 at 03:10:43PM -0500, Bruce Smith wrote: > > #man strip > > -s > > --strip-all > > Remove all symbols. > > > > That's the default option for strip. > > How about creating a new function called "strip_all" in addition to > "strip_debug", then change all the scripts to use "strip_all"? no go, if i use strip -s, gcc won't compile. So i've just take another aproach :) btw: on the install-on-usb, why there is a nice? nice -n19 cp -dpR ./tmp/mnt1/* ./tmp/mnt2/ || return 1 -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
From: Heiko Z. <he...@zu...> - 2003-10-29 23:01:19
|
Diego Torres wrote: >On Tue, Oct 28, 2003 at 03:10:43PM -0500, Bruce Smith wrote: > > >>>#man strip >>>-s >>>--strip-all >>> Remove all symbols. >>> >>>That's the default option for strip. >>> >>> >>How about creating a new function called "strip_all" in addition to >>"strip_debug", then change all the scripts to use "strip_all"? >> >> > >no go, if i use strip -s, gcc won't compile. So i've just take another aproach :) > > > But you still can use it for other programs, or? >btw: on the install-on-usb, why there is a nice? > >nice -n19 cp -dpR ./tmp/mnt1/* ./tmp/mnt2/ || return 1 > > > I didn't do it ! ;-) cya Heiko |
From: Diego T. <dt...@co...> - 2003-10-29 23:15:38
|
On Wed, Oct 29, 2003 at 06:00:20PM -0500, Heiko Zuerker wrote: > But you still can use it for other programs, or? yes, i strip everything that's on /usr/bin, /usr/sbin, /sbin and /bin. 138 -> 105Mb :) sounds good to me. > >btw: on the install-on-usb, why there is a nice? > > > >nice -n19 cp -dpR ./tmp/mnt1/* ./tmp/mnt2/ || return 1 > > > I didn't do it ! ;-) nice -n19 is supposed to lower the priority of the process. Quite useful if we are using 1.1 usb devices. i've checked in a few cosmetical changes (show the partition table on the device before asking for using fdisk, etc). also, the '!=' change on devildoc was a bugfix. I think you made a mistake when writting that line, and documentation was erased when "copy documentation to cd" option was checked. and more and more and more :) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
From: Heiko Z. <he...@zu...> - 2003-10-29 23:41:16
|
Diego Torres wrote: >On Wed, Oct 29, 2003 at 06:00:20PM -0500, Heiko Zuerker wrote: > > > >>But you still can use it for other programs, or? >> >> > >yes, i strip everything that's on /usr/bin, /usr/sbin, /sbin and /bin. > >138 -> 105Mb :) sounds good to me. > > It's quite a difference. You could also try /usr/lib, /usr/libexec and /lib (not the modules !!!) >>>btw: on the install-on-usb, why there is a nice? >>> >>>nice -n19 cp -dpR ./tmp/mnt1/* ./tmp/mnt2/ || return 1 >>> >>> >>> >>I didn't do it ! ;-) >> >> > >nice -n19 is supposed to lower the priority of the process. Quite useful if we are using 1.1 usb devices. > >i've checked in a few cosmetical changes (show the partition table on the device before asking for using fdisk, etc). > >also, the '!=' change on devildoc was a bugfix. I think you made a mistake when writting that line, and documentation was erased when "copy documentation to cd" option was checked. > > I think I better check the 1.0 ISOs >and more and more and more :) > yeah yeah Can't be that much. ;-) cya Heiko |
From: Diego T. <dt...@co...> - 2003-10-30 00:15:03
|
On Wed, Oct 29, 2003 at 06:39:07PM -0500, Heiko Zuerker wrote: > >when writting that line, and documentation was erased when "copy > >documentation to cd" option was checked. > > > I think I better check the 1.0 ISOs they must be wrong :)) > >and more and more and more :) > > > yeah yeah > Can't be that much. ;-) i was planning to add proftpd, but after seeing vsftpd i will stay cool and don't touch anything :) next upgrade -> buy an usb2.0 stick, so this boots faster. memtest86 and grub are working ok, even when using /dev/scsi/lun0... stuff. btw: maybe we need badblocks, a program for checking the hds surface with lots of read/writes. btw2: yeah, i now, but i've 20 empty mb on my usb stick, and i was thinking... what if we include alsa? it could be included as a package... opinions? -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
From: Heiko Z. <he...@zu...> - 2003-10-30 00:36:18
|
Diego Torres wrote: >On Wed, Oct 29, 2003 at 06:39:07PM -0500, Heiko Zuerker wrote: > > > >>>when writting that line, and documentation was erased when "copy >>>documentation to cd" option was checked. >>> >>> >>> >>I think I better check the 1.0 ISOs >> >> > >they must be wrong :)) > > Nope their fine, since it was the wrong directory anyway. ;-) >>>and more and more and more :) >>> >>> >>> >>yeah yeah >>Can't be that much. ;-) >> >> > >i was planning to add proftpd, but after seeing vsftpd i will stay cool and don't touch anything :) > vsftpd is very good and secure. >next upgrade -> buy an usb2.0 stick, so this boots faster. memtest86 and grub are working ok, even when using /dev/scsi/lun0... stuff. > >btw: maybe we need badblocks, a program for checking the hds surface with lots of read/writes. > Somebody else was asking me via personal mail, if we could add more hardware-testing tools to DL, because it would also make a perfect test distro. It would be great if you could add the stuff you want to the sourceforge feature requests and just assign it to yourself. Then we avoid duplicates and know what's in the queue. >btw2: yeah, i now, but i've 20 empty mb on my usb stick, and i was thinking... what if we include alsa? it could be included as a package... opinions? > > Hmm..... Firewall with Soundcard ? I actually was thinking about that too, a while ago. When you add it do it please in a way that everything can be turned of via menuconfig. cya Heiko |
From: Heiko Z. <he...@zu...> - 2003-10-30 00:06:18
|
Diego Torres wrote: >also, the '!=' change on devildoc was a bugfix. I think you made a mistake when writting that line, and documentation was erased when "copy documentation to cd" option was checked. > >and more and more and more :) > > > That one didn't work either, the pathnames were wrong. That's the reason why this bug never came up. ;-) Corrected in CVS Heiko |
From: Bruce S. <bw...@ar...> - 2003-10-30 01:55:57
|
> >btw: on the install-on-usb, why there is a nice? Just being nice. ;-) > I didn't do it ! ;-) Unlike Heiko! :-) Actually, heavy USB usage really bogs down my machine, so I was running the copy at the lowest priority. - BS |
From: Heiko Z. <he...@zu...> - 2003-10-28 20:19:49
|
> On Tue, Oct 28, 2003 at 02:41:28PM -0500, Heiko Zuerker wrote: >> > >> > btw: great improve over binaries that waste 3'5Mb... for example, >> > ldconfig. (after a strip it goes down to 3xxKbs) >> >> Did you check what "strip-all" removes? > > #man strip > -s > --strip-all > Remove all symbols. > > That's the default option for strip. Do we have any "real" developers here, who can tell us the implications ? I would say we just give it a try, if nobody complains. -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Heiko Z. <he...@zu...> - 2003-10-30 02:10:18
|
Bruce Smith wrote: >>>btw: on the install-on-usb, why there is a nice? >>> >>> > >Just being nice. ;-) > > > >>I didn't do it ! ;-) >> >> > >Unlike Heiko! :-) > > >Actually, heavy USB usage really bogs down my machine, >so I was running the copy at the lowest priority. > > Shouldn't you do the same with the "sync' command then ? Heiko |
From: Bruce S. <bw...@ar...> - 2003-10-31 19:55:06
|
> >>>btw: on the install-on-usb, why there is a nice? > > > >Actually, heavy USB usage really bogs down my machine, > >so I was running the copy at the lowest priority. > > > Shouldn't you do the same with the "sync' command then ? It's the cp command that locks up my system while it's running. Does anyone else have that problem? It's like all hardware with a lower priority IRQ than USB won't work until it's done. My USB mouse works really slow, and my PS/2 keyboard is completely dead until the cp is done. It's really weird, because I can copy/paste characters into a terminal window with the mouse while it's cp'ing, and the commands run in the xterm, BUT the keyboard doesn't do anything until the cp is done. I have a suspicion that it's a bug in my desktop kernel (Redhat 2.4.20). - BS |
From: Heiko Z. <he...@zu...> - 2003-10-28 19:07:42
|
> > Q: is there any reason for not doing this? > > scripts/functions > > strip_debug() > { > echo "removing debug symbols from binaries" > - find ./ -type f -exec strip -p --strip-debug '{}' ';' 1> /dev/null > 2>/dev/null > + find ./ -type f -exec strip -p --strip-all '{}' ';' 1> /dev/null > 2>/dev/null > } I think there was, but I can't remember what. We could give it a try for the 1.1 version, then we got enough time to see if it causes problems. So go ahead and change it. -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Diego T. <dt...@co...> - 2003-10-28 20:50:15
|
On Tue, Oct 28, 2003 at 03:10:43PM -0500, Bruce Smith wrote: > > #man strip > > -s > > --strip-all > > Remove all symbols. > > > > That's the default option for strip. > > How about creating a new function called "strip_all" in addition to > "strip_debug", then change all the scripts to use "strip_all"? I've never seen any problems once a file has been stripped. Symbols are used for debugging and relocating purpouses, and any executable file could live without them. > If any have problems with any packages, then we can change individual > scripts back to use "strip_debug". > > Also check to make sure all the scripts are calling "strip_all". From: http://www.linuxfromscratch.org/view/cvs/chapter09/theend.html Having said that, the --strip-debug option we use to strip is quite harmless under normal circumstances. It doesn't strip anything vital from the files. It also is quite safe to use --strip-all on regular programs (don't use that on libraries - they will be destroyed), but it's not as safe, and the space you gain is not all that much. But if you're tight on disk space every little bit helps, so decide for yourself. Please refer to the strip man page for other strip options you can use. The general idea is to not run strip on libraries (other than --strip-debug), just to be on the safe side. So, new proposed patch: strip_debug() { echo "removing debug symbols from binaries" find ./ -type f -iregex ".*\.[^a]" -exec strip -p --strip-all '{}' ';' 1> /dev/null 2>/dev/null find ./ -type f -iregex ".*\.[a]" -exec strip -p --strip-debug '{}' ';' 1> /dev/null 2>/dev/null } Shared objetcs (.so) are always stripped (at least, on debian) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
From: Heiko Z. <he...@zu...> - 2003-10-28 21:31:40
|
That sounds very promising ! Heiko > On Tue, Oct 28, 2003 at 03:10:43PM -0500, Bruce Smith wrote: >> > #man strip >> > -s >> > --strip-all >> > Remove all symbols. >> > >> > That's the default option for strip. >> >> How about creating a new function called "strip_all" in addition to >> "strip_debug", then change all the scripts to use "strip_all"? > > I've never seen any problems once a file has been stripped. > > Symbols are used for debugging and relocating purpouses, and any > executable file could live without them. > >> If any have problems with any packages, then we can change individual >> scripts back to use "strip_debug". >> >> Also check to make sure all the scripts are calling "strip_all". > > From: http://www.linuxfromscratch.org/view/cvs/chapter09/theend.html > > Having said that, the --strip-debug option we use to strip is quite > harmless under normal circumstances. It doesn't strip anything vital from > the files. It also is quite safe to use --strip-all on regular programs > (don't use that on libraries - they will be destroyed), but it's not as > safe, and the space you gain is not all that much. But if you're tight on > disk space every little bit helps, so decide for yourself. Please refer to > the strip man page for other strip options you can use. The general idea > is to not run strip on libraries (other than --strip-debug), just to be on > the safe side. > > So, new proposed patch: > > strip_debug() > { > echo "removing debug symbols from binaries" > find ./ -type f -iregex ".*\.[^a]" -exec strip -p --strip-all '{}' ';' > 1> /dev/null 2>/dev/null > find ./ -type f -iregex ".*\.[a]" -exec strip -p --strip-debug '{}' > ';' 1> /dev/null 2>/dev/null > } > > Shared objetcs (.so) are always stripped (at least, on debian) > > -- > -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D > 5799 > -- Use of a keyboard or mouse may be linked to serious injuries or > disorders. > Diego Torres - dt...@co... - Madrid / España > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop > > > -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Diego T. <dt...@co...> - 2003-10-28 23:15:01
|
On Tue, Oct 28, 2003 at 04:28:59PM -0500, Heiko Zuerker wrote: > That sounds very promising ! find ./ -type f -exec strip -p --strip-all '{}' ';' This one, doesn't work. Gcc fails in the build stage. Going for the second atempt :) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
From: Heiko Z. <he...@zu...> - 2003-10-28 23:27:36
|
Diego Torres wrote: >On Tue, Oct 28, 2003 at 04:28:59PM -0500, Heiko Zuerker wrote: > > >>That sounds very promising ! >> >> > >find ./ -type f -exec strip -p --strip-all '{}' ';' > >This one, doesn't work. Gcc fails in the build stage. Going for the second atempt :) > > > Use this command: find ./ -type f -iregex ".*\.[^a]" -exec strip -p --strip-all '{}' ';' 1> /dev/null 2>/dev/null You probably striped the libraries. Heiko |
From: Diego T. <dt...@co...> - 2003-10-28 23:34:18
|
On Tue, Oct 28, 2003 at 06:24:42PM -0500, Heiko Zuerker wrote: > > > >This one, doesn't work. Gcc fails in the build stage. Going for the second > >atempt :) > > > Use this command: find ./ -type f -iregex ".*\.[^a]" -exec strip -p > --strip-all '{}' ';' 1> /dev/null 2>/dev/null That's what i call a second atempt :) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |